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>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
11 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
13 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
14 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
15 to be a slight challenge. Here is the recipe if I ever need to do it
16 again. It all started by me wanting to try the recipe to set up
17 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
18 hardened Android installation
</a
> from the Tor project blog on a
19 device I had access to. It is a old mobile phone with a broken
20 microphone The initial idea had been to just
21 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
22 CyanogenMod on it
</a
>, but did not quite find time to start on it
23 until a few days ago.
</p
>
25 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
26 loader (press volume down and power at the same time), (
2) select
27 'fastboot
' before (
3) connecting the device via USB to a Linux
28 machine, (
4) request the device identifier token by running
'fastboot
29 oem get_identifier_token
', (
5) request the device unlocking key using
30 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
31 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
33 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
34 or newer, and the device I was working on had
2.00.0027. This
35 apparently can be easily fixed by downloading a Windows program and
36 running it on your Windows machine, if you accept the terms Microsoft
37 require you to accept to use Windows - which I do not. So I had to
38 come up with a different approach. I got a lot of help from AndyCap
39 on #nuug, and would not have been able to get this working without
42 <p
>First I needed to extract the hboot firmware from
43 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
44 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
45 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
46 project named unruu
</a
> using libunshield. The unshield tool did not
47 recognise the file format, but unruu worked and extracted rom.zip,
48 containing the new hboot firmware and a text file describing which
49 devices it would work for.
</p
>
51 <p
>Next, I needed to get the new firmware into the device. For this I
52 followed some instructions
53 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
54 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
55 machine with Debian testing:
</p
>
59 fastboot oem rebootRUU
60 fastboot flash zip rom.zip
61 fastboot flash zip rom.zip
63 </pre
></p
>
65 <p
>The flash command apparently need to be done twice to take effect,
66 as the first is just preparations and the second one do the flashing.
67 The adb command is just to get to the boot loader menu, so turning the
68 device on while holding volume down and the power button should work
71 <p
>With the new hboot version in place I could start following the
72 instructions on the HTC developer web site. I got the device token
76 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
79 <p
>And once I got the unlock code via email, I could use it like
83 fastboot flash unlocktoken Unlock_code.bin
84 </pre
></p
>
86 <p
>And with that final step in place, the phone was unlocked and I
87 could start stuffing the software of my own choosing into the device.
88 So far I only inserted a replacement recovery image to wipe the phone
89 before I start. We will see what happen next. Perhaps I should
90 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
95 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
96 <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>
97 <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>
98 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
99 <description><p
>For a while now, I have wanted to test
100 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
101 said to provide end to end encrypted communication and several of my
102 friends and family are already using it. As I by choice do not own a
103 mobile phone, this proved to be harder than expected. And I wanted to
104 have the source of the client and know that it was the code used on my
105 machine. But yesterday I managed to get it working. I used the
106 Github source, compared it to the source in
107 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
108 Signal Chrome app
</a
> available from the Chrome web store, applied
109 patches to use the production Signal servers, started the app and
110 asked for the hidden
"register without a smart phone
" form. Here is
111 the recipe how I did it.
</p
>
113 <p
>First, I fetched the Signal desktop source from Github, using
116 git clone https://github.com/WhisperSystems/Signal-Desktop.git
119 <p
>Next, I patched the source to use the production servers, to be
120 able to talk to other Signal users:
</p
>
123 cat
&lt;
&lt;EOF | patch -p0
124 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
125 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
126 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
131 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
132 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
133 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
134 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
136 window.getSocketStatus = function() {
137 if (messageReceiver) {
138 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
139 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
140 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
143 'use strict
';
144 - var BUILD_EXPIRATION =
0;
145 + var BUILD_EXPIRATION =
1474492690000;
147 window.extension = window.extension || {};
152 <p
>The first part is changing the servers, and the second is updating
153 an expiration timestamp. This timestamp need to be updated regularly.
154 It is set
90 days in the future by the build process (Gruntfile.js).
155 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
157 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
158 script to launch Signal in Chromium.
</p
>
165 --proxy-server=
"socks://localhost:
9050" \
166 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
169 <p
> The script start the app and configure Chromium to use the Tor
170 SOCKS5 proxy to make sure those controlling the Signal servers (today
171 Amazon and Whisper Systems) as well as those listening on the lines
172 will have a harder time location my laptop based on the Signal
173 connections if they use source IP address.
</p
>
175 <p
>When the script starts, one need to follow the instructions under
176 "Standalone Registration
" in the CONTRIBUTING.md file in the git
177 repository. I right clicked on the Signal window to get up the
178 Chromium debugging tool, visited the
'Console
' tab and wrote
179 'extension.install(
"standalone
")
' on the console prompt to get the
180 registration form. Then I entered by land line phone number and
181 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
182 repeated the verification code three times. After entering the number
183 into the verification code field in the form, I could start using
184 Signal from my laptop.
186 <p
>As far as I can tell, The Signal app will leak who is talking to
187 whom and thus who know who to those controlling the central server,
188 but such leakage is hard to avoid with a centrally controlled server
189 setup. It is something to keep in mind when using Signal - the
190 content of your chats are harder to intercept, but the meta data
191 exposing your contact network is available to people you do not know.
192 So better than many options, but not great. And sadly the usage is
193 connected to my land line, thus allowing those controlling the server
194 to associate it to my home and person. I would prefer it if only
195 those I knew could tell who I was on Signal. There are options
196 avoiding such information leakage, but most of my friends are not
197 using them, so I am stuck with Signal for now.
</p
>
202 <title>The new
"best
" multimedia player in Debian?
</title>
203 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
204 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
205 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
206 <description><p
>When I set out a few weeks ago to figure out
207 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
208 multimedia player in Debian claimed to support most file formats /
209 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
210 the various players claimed support for. The range was from
55 to
130
211 MIME types. I suspect most media formats are supported by all
212 players, but this is not really reflected in the MimeTypes values in
213 their desktop files. There are probably also some bogus MIME types
214 listed, but it is hard to identify which one this is.
</p
>
216 <p
>Anyway, in the mean time I got in touch with upstream for some of
217 the players suggesting to add more MIME types to their desktop files,
218 and decided to spend some time myself improving the situation for my
219 favorite media player VLC. The fixes for VLC entered Debian unstable
220 yesterday. The complete list of MIME types can be seen on the
221 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
222 player MIME type support status
</a
> Debian wiki page.
</p
>
224 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
225 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
226 kmplayer. I am sure some of the other players desktop files support
227 several of the formats currently listed as working only with vlc,
228 toten and parole.
</p
>
230 <p
>A sad observation is that only
14 MIME types are listed as
231 supported by all the tested multimedia players in Debian in their
232 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
233 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
234 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
235 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
236 it sad that video/ogg and video/webm is not supported by all the media
237 players in Debian. As far as I can tell, all of them can handle both
243 <title>A program should be able to open its own files on Linux
</title>
244 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
245 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
246 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
247 <description><p
>Many years ago, when koffice was fresh and with few users, I
248 decided to test its presentation tool when making the slides for a
249 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
250 wrote the first draft of the slides, saved the result and went to bed
251 the day before I would give the talk. The next day I took a plane to
252 the location where the meeting should take place, and on the plane I
253 started up koffice again to polish the talk a bit, only to discover
254 that kpresenter refused to load its own data file. I cursed a bit and
255 started making the slides again from memory, to have something to
256 present when I arrived. I tested that the saved files could be
257 loaded, and the day seemed to be rescued. I continued to polish the
258 slides until I suddenly discovered that the saved file could no longer
259 be loaded into kpresenter. In the end I had to rewrite the slides
260 three times, condensing the content until the talk became shorter and
261 shorter. After the talk I was able to pinpoint the problem
&ndash;
262 kpresenter wrote inline images in a way itself could not understand.
263 Eventually that bug was fixed and kpresenter ended up being a great
264 program to make slides. The point I
'm trying to make is that we
265 expect a program to be able to load its own data files, and it is
266 embarrassing to its developers if it can
't.
</p
>
268 <p
>Did you ever experience a program failing to load its own data
269 files from the desktop file browser? It is not a uncommon problem. A
270 while back I discovered that the screencast recorder
271 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
272 browser would refuse to open. No video player claimed to understand
273 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
274 returning the application/ogg MIME type, which no video player I had
275 installed listed as a MIME type they would understand. I asked for
276 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
277 behavour
</a
> and use the MIME type video/ogg instead. I also asked
278 several video players to add video/ogg to their desktop files, to give
279 the file browser an idea what to do about Ogg Theora files. After a
280 while, the desktop file browsers in Debian started to handle the
281 output from gtk-recordmydesktop properly.
</p
>
283 <p
>But history repeats itself. A few days ago I tested the music
284 system Rosegarden again, and I discovered that the KDE and xfce file
285 browsers did not know what to do with the Rosegarden project files
286 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
287 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
288 included in the next upload. To increase the chance of me remembering
289 how to fix the problem next time some program fail to load its files
290 from the file browser, here are some notes on how to fix it.
</p
>
292 <p
>The file browsers in Debian in general operates on MIME types.
293 There are two sources for the MIME type of a given file. The output from
294 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
295 shared MIME type registry (under /usr/share/mime/). The file MIME
296 type is mapped to programs supporting the MIME type, and this
297 information is collected from
298 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
299 desktop files
</a
> available in /usr/share/applications/. If there is
300 one desktop file claiming support for the MIME type of the file, it is
301 activated when asking to open a given file. If there are more, one
302 can normally select which one to use by right-clicking on the file and
303 selecting the wanted one using
'Open with
' or similar. In general
304 this work well. But it depend on each program picking a good MIME
306 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
307 MIME type registered with IANA
</a
>), file and/or the shared MIME
308 registry recognizing the file and the desktop file to list the MIME
309 type in its list of supported MIME types.
</p
>
311 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
312 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
313 Shared MIME database
</a
> look like this:
</p
>
315 <p
><blockquote
><pre
>
316 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
317 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
318 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
319 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
320 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
321 &lt;glob pattern=
"*.rg
"/
&gt;
322 &lt;/mime-type
&gt;
323 &lt;/mime-info
&gt;
324 </pre
></blockquote
></p
>
326 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
327 (it is a gzipped XML file). Note, it is much better to use an
328 official MIME type registered with IANA than it is to make up ones own
329 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
331 <p
>The desktop file of the rosegarden program failed to list
332 audio/x-rosegarden in its list of supported MIME types, causing the
333 file browsers to have no idea what to do with *.rg files:
</p
>
335 <p
><blockquote
><pre
>
336 % grep Mime /usr/share/applications/rosegarden.desktop
337 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
338 X-KDE-NativeMimeType=audio/x-rosegarden-composition
340 </pre
></blockquote
></p
>
342 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
343 MimeType= line.
</p
>
345 <p
>If you run into a file which fail to open the correct program when
346 selected from the file browser, please check out the output from
347 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
348 MIME type is registered somewhere under /usr/share/mime/ and check
349 that some desktop file under /usr/share/applications/ is claiming
350 support for this MIME type. If not, please report a bug to have it
356 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
357 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
358 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
359 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
360 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
361 system
</a
> is a user-focused solution in Debian for handling hardware
362 related packages. The idea is to have a database of mappings between
363 hardware and packages, and pop up a dialog suggesting for the user to
364 install the packages to use a given hardware dongle. Some use cases
365 are when you insert a Yubikey, it proposes to install the software
366 needed to control it; when you insert a braille reader list it
367 proposes to install the packages needed to send text to the reader;
368 and when you insert a ColorHug screen calibrator it suggests to
369 install the driver for it. The system work well, and even have a few
370 command line tools to install firmware packages and packages for the
371 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
373 <p
>The system was initially written using aptdaemon, because I found
374 good documentation and example code on how to use it. But aptdaemon
375 is going away and is generally being replaced by
376 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
377 so Isenkram needed a rewrite. And today, thanks to the great patch
378 from my college Sunil Mohan Adapa in the FreedomBox project, the
379 rewrite finally took place. I
've just uploaded a new version of
380 Isenkram into Debian Unstable with the patch included, and the default
381 for the background daemon is now to use PackageKit. To check it out,
382 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
383 and see if it is recognised.
</p
>
385 <p
>If you want to know what kind of packages isenkram would propose for
386 the machine it is running on, you can check out the isenkram-lookup
387 program. This is what it look like on a Thinkpad X230:
</p
>
389 <p
><blockquote
><pre
>
405 </pre
></blockquote
></p
>
407 <p
>The hardware mappings come from several places. The preferred way
408 is for packages to announce their hardware support using
409 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
410 cross distribution appstream system
</a
>.
412 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
413 blog posts about isenkram
</a
> to learn how to do that.
</p
>
418 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
419 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
420 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
421 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
422 <description><p
>Yesterday I updated the
423 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
424 package in Debian
</a
> with a few patches sent to me by skilled and
425 enterprising users. There were some nice user and visible changes.
426 First of all, both desktop menu entries now work. A design flaw in
427 one of the script made the history graph fail to show up (its PNG was
428 dumped in ~/.xsession-errors) if no controlling TTY was available.
429 The script worked when called from the command line, but not when
430 called from the desktop menu. I changed this to look for a DISPLAY
431 variable or a TTY before deciding where to draw the graph, and now the
432 graph window pop up as expected.
</p
>
434 <p
>The next new feature is a discharge rate estimator in one of the
435 graphs (the one showing the last few hours). New is also the user of
436 colours showing charging in blue and discharge in red. The percentages
437 of this graph is relative to last full charge, not battery design
440 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
442 <p
>The other graph show the entire history of the collected battery
443 statistics, comparing it to the design capacity of the battery to
444 visualise how the battery life time get shorter over time. The red
445 line in this graph is what the previous graph considers
100 percent:
447 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
449 <p
>In this graph you can see that I only charge the battery to
80
450 percent of last full capacity, and how the capacity of the battery is
451 shrinking. :(
</p
>
453 <p
>The last new feature is in the collector, which now will handle
454 more hardware models. On some hardware, Linux power supply
455 information is stored in /sys/class/power_supply/ACAD/, while the
456 collector previously only looked in /sys/class/power_supply/AC/. Now
457 both are checked to figure if there is power connected to the
460 <p
>If you are interested in how your laptop battery is doing, please
462 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
463 in Debian unstable, or rebuild it on Jessie to get it working on
464 Debian stable. :) The upstream source is available from
<a
465 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
466 Patches are very welcome.
</p
>
468 <p
>As usual, if you use Bitcoin and want to show your support of my
469 activities, please send Bitcoin donations to my address
470 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
475 <title>Debian now with ZFS on Linux included
</title>
476 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
477 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
478 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
479 <description><p
>Today, after many years of hard work from many people,
480 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
481 Debian. The package status can be seen on
482 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
483 for zfs-linux
</a
>. and
484 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
485 team status page
</a
>. If you want to help out, please join us.
486 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
487 source code
</a
> is available via git on Alioth. It would also be
488 great if you could help out with
489 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
490 it is an important piece of the puzzle to get ZFS working.
</p
>
495 <title>What is the best multimedia player in Debian?
</title>
496 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
497 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
498 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
499 <description><p
><strong
>Where I set out to figure out which multimedia player in
500 Debian claim support for most file formats.
</strong
></p
>
502 <p
>A few years ago, I had a look at the media support for Browser
503 plugins in Debian, to get an idea which plugins to include in Debian
504 Edu. I created a script to extract the set of supported MIME types
505 for each plugin, and used this to find out which multimedia browser
506 plugin supported most file formats / media types.
507 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
508 result
</a
> can still be seen on the Debian wiki, even though it have
509 not been updated for a while. But browser plugins are less relevant
510 these days, so I thought it was time to look at standalone
513 <p
>A few days ago I was tired of VLC not being listed as a viable
514 player when I wanted to play videos from the Norwegian National
515 Broadcasting Company, and decided to investigate why. The cause is a
516 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
517 desktop file
</a
>. In the process I wrote a script to compare the set
518 of MIME types announced in the desktop file and the browser plugin,
519 only to discover that there is quite a large difference between the
520 two for VLC. This discovery made me dig up the script I used to
521 compare browser plugins, and adjust it to compare desktop files
522 instead, to try to figure out which multimedia player in Debian
523 support most file formats.
</p
>
525 <p
>The result can be seen on the Debian Wiki, as
526 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
527 table listing all MIME types supported by one of the packages included
528 in the table
</a
>, with the package supporting most MIME types being
529 listed first in the table.
</p
>
531 </p
>The best multimedia player in Debian? It is totem, followed by
532 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
533 kmplayer. Time for the other players to update their announced MIME
539 <title>The Pyra - handheld computer with Debian preinstalled
</title>
540 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
541 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
542 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
543 <description>A friend of mine made me aware of
544 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
545 handheld computer which will be delivered with Debian preinstalled. I
546 would love to get one of those for my birthday. :)
</p
>
548 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
549 plugs and many others connectors, and include a full keyboard and a
5"
550 LCD touch screen. The
6000mAh battery is claimed to provide a whole
551 day of battery life time, but I have not seen any independent tests
552 confirming this. The vendor is still collecting preorders, and the
553 last I heard last night was that
22 more orders were needed before
554 production started.
</p
>
556 <p
>As far as I know, this is the first handheld preinstalled with
557 Debian. Please let me know if you know of any others. Is it the
558 first computer being sold with Debian preinstalled?
</p
>
563 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
564 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
565 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
566 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
567 <description><p
>During this weekends
568 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
569 squashing party and developer gathering
</a
>, we decided to do our part
570 to make sure there are good books about Debian available in Norwegian
571 Bokmål, and got in touch with the people behind the
572 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
573 project
</a
> to get started. If you want to help out, please start
575 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
576 hosted weblate project page
</a
>, and get in touch using
577 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
578 translators mailing list
</a
>. Please also check out
579 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
580 contributors
</a
>.
</p
>
582 <p
>The book is already available on paper in English, French and
583 Japanese, and our goal is to get it available on paper in Norwegian
584 Bokmål too. In addition to the paper edition, there are also EPUB and
585 Mobi versions available. And there are incomplete translations
586 available for many more languages.
</p
>
591 <title>One in two hundred Debian users using ZFS on Linux?
</title>
592 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
593 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
594 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
595 <description><p
>Just for fun I had a look at the popcon number of ZFS related
596 packages in Debian, and was quite surprised with what I found. I use
597 ZFS myself at home, but did not really expect many others to do so.
598 But I might be wrong.
</p
>
600 <p
>According to
601 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
602 results for spl-linux
</a
>, there are
1019 Debian installations, or
603 0.53% of the population, with the package installed. As far as I know
604 the only use of the spl-linux package is as a support library for ZFS
605 on Linux, so I use it here as proxy for measuring the number of ZFS
606 installation on Linux in Debian. In the kFreeBSD variant of Debian
607 the ZFS feature is already available, and there
608 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
609 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
610 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
612 <p
>But even though the Debian project leader Lucas Nussbaum
613 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
614 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
615 cleared, the package is still not in Debian. The package is again in
616 the NEW queue. Several uploads have been rejected so far because the
617 debian/copyright file was incomplete or wrong, but there is no reason
618 to give up. The current status can be seen on
619 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
620 team status page
</a
>, and
621 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
622 source code
</a
> is available on Alioth.
</p
>
624 <p
>As I want ZFS to be included in next version of Debian to make sure
625 my home server can function in the future using only official Debian
626 packages, and the current blocker is to get the debian/copyright file
627 accepted by the FTP masters in Debian, I decided a while back to try
628 to help out the team. This was the background for my blog post about
629 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
630 updating and checking debian/copyright semi-automatically
</a
>, and I
631 used the techniques I explored there to try to find any errors in the
632 copyright file. It is not very easy to check every one of the around
633 2000 files in the source package, but I hope we this time got it
634 right. If you want to help out, check out the git source and try to
635 find missing entries in the debian/copyright file.
</p
>
640 <title>Full battery stats collector is now available in Debian
</title>
641 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
642 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
643 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
644 <description><p
>Since this morning, the battery-stats package in Debian include an
645 extended collector that will collect the complete battery history for
646 later processing and graphing. The original collector store the
647 battery level as percentage of last full level, while the new
648 collector also record battery vendor, model, serial number, design
649 full level, last full level and current battery level. This make it
650 possible to predict the lifetime of the battery as well as visualise
651 the energy flow when the battery is charging or discharging.
</p
>
653 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
654 in the version
0.5.1 package in unstable. Get the new battery level graph
655 and lifetime prediction by running:
658 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
659 </pre
></p
>
661 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
663 <p
>The flow in/out of the battery can be seen by running (no menu
664 entry yet):
</p
>
667 /usr/share/battery-stats/battery-stats-graph-flow
668 </pre
></p
>
670 <p
>I
'm not quite happy with the way the data is visualised, at least
671 when there are few data points. The graphs look a bit better with a
672 few years of data.
</p
>
674 <p
>A while back one important feature I use in the battery stats
675 collector broke in Debian. The scripts in
676 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
677 suspect it happened when Jessie started using systemd, but I do not
678 know. The issue is reported as
679 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
680 pm-utils. I managed to work around it by adding an udev rule to call
681 the collector script every time the power connector is connected and
682 disconnected. With this fix in place it was finally time to make a
683 new release of the package, and get it into Debian.
</p
>
685 <p
>If you are interested in how your laptop battery is doing, please
687 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
688 in Debian unstable, or rebuild it on Jessie to get it working on
689 Debian stable. :) The upstream source is available from
690 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
691 As always, patches are very welcome.
</p
>
696 <title>Making battery measurements a little easier in Debian
</title>
697 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
698 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
699 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
700 <description><p
>Back in September, I blogged about
701 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
702 system I wrote to collect statistics about my laptop battery
</a
>, and
703 how it showed the decay and death of this battery (now replaced). I
704 created a simple deb package to handle the collection and graphing,
705 but did not want to upload it to Debian as there were already
706 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
707 package in Debian
</a
> that should do the same thing, and I did not see
708 a point of uploading a competing package when battery-stats could be
709 fixed instead. I reported a few bugs about its non-function, and
710 hoped someone would step in and fix it. But no-one did.
</p
>
712 <p
>I got tired of waiting a few days ago, and took matters in my own
713 hands. The end result is that I am now the new upstream developer of
714 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
715 battery-stats in Debian, and the package in Debian unstable is finally
716 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
717 information provided by the Linux kernel. If you install the
718 battery-stats package from unstable now, you will be able to get a
719 graph of the current battery fill level, to get some idea about the
720 status of the battery. The source package build and work just fine in
721 Debian testing and stable (and probably oldstable too, but I have not
722 tested). The default graph you get for that system look like this:
</p
>
724 <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
>
726 <p
>My plans for the future is to merge my old scripts into the
727 battery-stats package, as my old scripts collected a lot more details
728 about the battery. The scripts are merged into the upstream
729 battery-stats git repository already, but I am not convinced they work
730 yet, as I changed a lot of paths along the way. Will have to test a
731 bit more before I make a new release.
</p
>
733 <p
>I will also consider changing the file format slightly, as I
734 suspect the way I combine several values into one field might make it
735 impossible to know the type of the value when using it for processing
736 and graphing.
</p
>
738 <p
>If you would like I would like to keep an close eye on your laptop
739 battery, check out the battery-stats package in
740 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
742 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
743 I would love some help to improve the system further.
</p
>
748 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
749 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
750 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
751 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
752 <description><p
>Making packages for Debian requires quite a lot of attention to
753 details. And one of the details is the content of the
754 debian/copyright file, which should list all relevant licenses used by
755 the code in the package in question, preferably in
756 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
757 readable DEP5 format
</a
>.
</p
>
759 <p
>For large packages with lots of contributors it is hard to write
760 and update this file manually, and if you get some detail wrong, the
761 package is normally rejected by the ftpmasters. So getting it right
762 the first time around get the package into Debian faster, and save
763 both you and the ftpmasters some work.. Today, while trying to figure
764 out what was wrong with
765 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
766 zfsonlinux copyright file
</a
>, I decided to spend some time on
767 figuring out the options for doing this job automatically, or at least
768 semi-automatically.
</p
>
770 <p
>Lucikly, there are at least two tools available for generating the
771 file based on the code in the source package,
772 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
773 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
774 not sure which one of them came first, but both seem to be able to
775 create a sensible draft file. As far as I can tell, none of them can
776 be trusted to get the result just right, so the content need to be
777 polished a bit before the file is OK to upload. I found the debmake
779 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
780 blog posts from
2014</a
>.
782 <p
>To generate using debmake, use the -cc option:
785 debmake -cc
> debian/copyright
786 </pre
></p
>
788 <p
>Note there are some problems with python and non-ASCII names, so
789 this might not be the best option.
</p
>
791 <p
>The cme option is based on a config parsing library, and I found
793 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
794 blog post from
2015</a
>. To generate using cme, use the
'update
795 dpkg-copyright
' option:
798 cme update dpkg-copyright
799 </pre
></p
>
801 <p
>This will create or update debian/copyright. The cme tool seem to
802 handle UTF-
8 names better than debmake.
</p
>
804 <p
>When the copyright file is created, I would also like some help to
805 check if the file is correct. For this I found two good options,
806 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
807 to focus on license types and file matching, and is able to detect
808 ineffective blocks in the copyright file. The latter reports missing
809 copyright holders and years, but was confused by inconsistent license
810 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
811 fix all issues reported by them before uploading. But I do not know
812 if the tools and the ftpmasters agree on what is important to fix in a
813 copyright file, so the package might still be rejected.
</p
>
815 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
816 will read through the source and try to find all copyright statements.
817 It is not comparing the result to the content of debian/copyright, but
818 can be useful when verifying the content of the copyright file.
</p
>
820 <p
>Are you aware of better tools in Debian to create and update
821 debian/copyright file. Please let me know, or blog about it on
822 planet.debian.org.
</p
>
824 <p
>As usual, if you use Bitcoin and want to show your support of my
825 activities, please send Bitcoin donations to my address
826 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
828 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
829 on how to use licensecheck and cdbs to create a draft copyright file
832 licensecheck --copyright -r `find * -type f` | \
833 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
834 </pre
></p
>
836 <p
>He mentioned that he normally check the generated file into the
837 version control system to make it easier to discover license and
838 copyright changes in the upstream source. I will try to do the same
839 with my packages in the future.
</p
>
841 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
842 against using -quiet for new users, so I removed it from the proposed
843 command line.
</p
>
848 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
849 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
850 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
851 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
852 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
853 is taking shape in Debian, and one provided feature is a very
854 convenient way to tell you which package to install to make a given
855 firmware file available when the kernel is looking for it. This can
856 be done using apt-file too, but that is for someone else to blog
859 <p
>Here is a small recipe to find the package with a given firmware
860 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
861 picked from the set of firmware announced using appstream in Debian
862 unstable. In general you would be looking for the firmware requested
863 by the kernel during kernel module loading. To find the package
864 providing the example file, do like this:
</p
>
866 <blockquote
><pre
>
867 % apt install appstream
871 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
872 awk
'/Package:/ {print $
2}
'
875 </pre
></blockquote
>
877 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
878 appstream wiki
</a
> page to learn how to embed the package metadata in
879 a way appstream can use.
</p
>
881 <p
>This same approach can be used to find any package supporting a
882 given MIME type. This is very useful when you get a file you do not
883 know how to handle. First find the mime type using
<tt
>file
884 --mime-type
</tt
>, and next look up the package providing support for
885 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
886 and you can find all packages handling this type like this:
</p
>
888 <blockquote
><pre
>
889 % apt install appstream
893 % appstreamcli what-provides mimetype image/svg+xml | \
894 awk
'/Package:/ {print $
2}
'
916 </pre
></blockquote
>
918 <p
>I believe the MIME types are fetched from the desktop file for
919 packages providing appstream metadata.
</p
>
924 <title>Creepy, visualise geotagged social media information - nice free software
</title>
925 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
926 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
927 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
928 <description><p
>Most people seem not to realise that every time they walk around
929 with the computerised radio beacon known as a mobile phone their
930 position is tracked by the phone company and often stored for a long
931 time (like every time a SMS is received or sent). And if their
932 computerised radio beacon is capable of running programs (often called
933 mobile apps) downloaded from the Internet, these programs are often
934 also capable of tracking their location (if the app requested access
935 during installation). And when these programs send out information to
936 central collection points, the location is often included, unless
937 extra care is taken to not send the location. The provided
938 information is used by several entities, for good and bad (what is
939 good and bad, depend on your point of view). What is certain, is that
940 the private sphere and the right to free movement is challenged and
941 perhaps even eradicated for those announcing their location this way,
942 when they share their whereabouts with private and public
945 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
947 <p
>The phone company logs provide a register of locations to check out
948 when one want to figure out what the tracked person was doing. It is
949 unavailable for most of us, but provided to selected government
950 officials, company staff, those illegally buying information from
951 unfaithful servants and crackers stealing the information. But the
952 public information can be collected and analysed, and a free software
953 tool to do so is called
954 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
955 discovered it when I read
956 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
957 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
958 November
2014, and decided to check if it was available in Debian.
959 The python program was in Debian, but
960 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
961 Debian
</a
> was completely broken and practically unmaintained. I
962 uploaded a new version which did not work quite right, but did not
963 have time to fix it then. This Christmas I decided to finally try to
964 get Creepy operational in Debian. Now a fixed version is available in
965 Debian unstable and testing, and almost all Debian specific patches
967 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
969 <p
>The Creepy program visualises geolocation information fetched from
970 Twitter, Instagram, Flickr and Google+, and allow one to get a
971 complete picture of every social media message posted recently in a
972 given area, or track the movement of a given individual across all
973 these services. Earlier it was possible to use the search API of at
974 least some of these services without identifying oneself, but these
975 days it is impossible. This mean that to use Creepy, you need to
976 configure it to log in as yourself on these services, and provide
977 information to them about your search interests. This should be taken
978 into account when using Creepy, as it will also share information
979 about yourself with the services.
</p
>
981 <p
>The picture above show the twitter messages sent from (or at least
982 geotagged with a position from) the city centre of Oslo, the capital
983 of Norway. One useful way to use Creepy is to first look at
984 information tagged with an area of interest, and next look at all the
985 information provided by one or more individuals who was in the area.
986 I tested it by checking out which celebrity provide their location in
987 twitter messages by checkout out who sent twitter messages near a
988 Norwegian TV station, and next could track their position over time,
989 making it possible to locate their home and work place, among other
990 things. A similar technique have been
991 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
992 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
993 tool to discover lying governments, and a useful tool to help people
994 understand the value of the private information they provide to the
997 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
998 it depend on several python modules currently missing in Jessie (at
999 least python-instagram, python-flickrapi and
1000 python-requests-toolbelt).
</p
>
1002 <p
>(I have uploaded
1003 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
1004 screenshots.debian.net
</a
> and licensed it under the same terms as the
1005 Creepy program in Debian.)
</p
>
1010 <title>Always download Debian packages using Tor - the simple recipe
</title>
1011 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
1012 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
1013 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
1014 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
1015 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
1016 that those listening on the Internet lines would have good reason to
1017 believe a computer have a given security hole
</a
> if it download a
1018 security fix from a Debian mirror. This is a good reason to always
1019 use encrypted connections to the Debian mirror, to make sure those
1020 listening do not know which IP address to attack. In August, Richard
1021 Hartmann observed that encryption was not enough, when it was possible
1022 to interfere download size to security patches or the fact that
1023 download took place shortly after a security fix was released, and
1024 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
1025 to always use Tor to download packages from the Debian mirror
</a
>. He
1026 was not the first to propose this, as the
1027 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
1028 package by Tim Retout already existed to make it easy to convince apt
1029 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
1030 aware of that package when I read the blog post from Richard.
</p
>
1032 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
1033 sysadmins, and he set up a Tor hidden service on one of the central
1034 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
1035 it possible to download packages directly between two tor nodes,
1036 making sure the network traffic always were encrypted.
</p
>
1038 <p
>Here is a short recipe for enabling this on your machine, by
1039 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
1040 urls with tor+http and tor+https, and using the hidden service instead
1041 of the official Debian mirror site. I recommend installing
1042 <tt
>etckeeper
</tt
> before you start to have a history of the changes
1043 done in /etc/.
</p
>
1045 <blockquote
><pre
>
1046 apt install apt-transport-tor
1047 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
1048 sed -i
's% http% tor+http%
' /etc/apt/sources.list
1049 </pre
></blockquote
>
1051 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
1052 the sed commands for these too. The sed command is assuming your are
1053 using the ftp.debian.org Debian mirror. Adjust the command (or just
1054 edit the file manually) to match your mirror.
</p
>
1056 <p
>This work in Debian Jessie and later. Note that tools like
1057 <tt
>apt-file
</tt
> only recently started using the apt transport
1058 system, and do not work with these tor+http URLs. For
1059 <tt
>apt-file
</tt
> you need the version currently in experimental,
1060 which need a recent apt version currently only in unstable. So if you
1061 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
1063 <p
>Another advantage from this change is that your machine will start
1064 using Tor regularly and at fairly random intervals (every time you
1065 update the package lists or upgrade or install a new package), thus
1066 masking other Tor traffic done from the same machine. Using Tor will
1067 become normal for the machine in question.
</p
>
1069 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
1070 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
1071 enabled. It would be great if it was the default on any Debian
1077 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
1078 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
1079 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
1080 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
1081 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
1082 call the car license plate numbers in those days. I would write the
1083 numbers down in my little book and compare notes with the other kids
1084 to see how many region codes we had seen and if we had seen some
1085 exotic or special region codes and numbers. It was a fun game to pass
1086 time, as we kids have plenty of it.
</p
>
1088 <p
>A few days I came across
1089 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
1090 project
</a
>, a free software project to automatically discover and
1091 report license plates in images and video streams, and provide the
1092 "car numbers
" in a machine readable format. I
've been looking for
1093 such system for a while now, because I believe it is a bad idea that the
1094 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
1095 number plate recognition
</a
> tool only is available in the hands of
1096 the powerful, and want it to be available also for the powerless to
1097 even the score when it comes to surveillance and sousveillance. I
1098 discovered the developer
1099 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
1100 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
1101 help him get it into shape to get the package uploaded into the Debian
1104 <p
>Today we finally managed to get the package into shape and uploaded
1105 it into Debian, where it currently
1106 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
1107 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
1109 <p
>I guess you are wondering why on earth such tool would be useful
1110 for the common folks, ie those not running a large government
1111 surveillance system? Well, I plan to put it in a computer on my bike
1112 and in my car, tracking the cars nearby and allowing me to be notified
1113 when number plates on my watch list are discovered. Another use case
1114 was suggested by a friend of mine, who wanted to set it up at his home
1115 to open the car port automatically when it discovered the plate on his
1116 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1117 capable of placing his license plate number of a piece of cardboard to
1118 open his car port, men replied that it was always unlocked anyway. I
1119 guess for such use case it make sense. I am sure there are other use
1120 cases too, for those with imagination and a vision.
</p
>
1122 <p
>If you want to build your own version of the Debian package, check
1123 out the upstream git source and symlink ./distros/debian to ./debian/
1124 before running
"debuild
" to build the source. Or wait a bit until the
1125 package show up in unstable.
</p
>
1130 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
1131 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
1132 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
1133 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
1134 <description><p
>Around three years ago, I created
1135 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
1136 system
</a
> to get a more practical solution in Debian for handing
1137 hardware related packages. A GUI system in the isenkram package will
1138 present a pop-up dialog when some hardware dongle supported by
1139 relevant packages in Debian is inserted into the machine. The same
1140 lookup mechanism to detect packages is available as command line
1141 tools in the isenkram-cli package. In addition to mapping hardware,
1142 it will also map kernel firmware files to packages and make it easy to
1143 install needed firmware packages automatically. The key for this
1144 system to work is a good way to map hardware to packages, in other
1145 words, allow packages to announce what hardware they will work
1148 <p
>I started by providing data files in the isenkram source, and
1149 adding code to download the latest version of these data files at run
1150 time, to ensure every user had the most up to date mapping available.
1151 I also added support for storing the mapping in the Packages file in
1152 the apt repositories, but did not push this approach because while I
1153 was trying to figure out how to best store hardware/package mappings,
1154 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
1155 appstream system
</a
> was announced. I got in touch and suggested to
1156 add the hardware mapping into that data set to be able to use
1157 appstream as a data source, and this was accepted at least for the
1158 Debian version of appstream.
</p
>
1160 <p
>A few days ago using appstream in Debian for this became possible,
1161 and today I uploaded a new version
0.20 of isenkram adding support for
1162 appstream as a data source for mapping hardware to packages. The only
1163 package so far using appstream to announce its hardware support is my
1164 pymissile package. I got help from Matthias Klumpp with figuring out
1165 how do add the required
1166 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
1167 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
1168 this content:
</p
>
1170 <blockquote
><pre
>
1171 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1172 &lt;component
&gt;
1173 &lt;id
&gt;pymissile
&lt;/id
&gt;
1174 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
1175 &lt;name
&gt;pymissile
&lt;/name
&gt;
1176 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
1177 &lt;description
&gt;
1179 Pymissile provides a curses interface to control an original
1180 Marks and Spencer / Striker USB Missile Launcher, as well as a
1181 motion control script to allow a webcamera to control the
1184 &lt;/description
&gt;
1185 &lt;provides
&gt;
1186 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
1187 &lt;/provides
&gt;
1188 &lt;/component
&gt;
1189 </pre
></blockquote
>
1191 <p
>The key for isenkram is the component/provides/modalias value,
1192 which is a glob style match rule for hardware specific strings
1193 (modalias strings) provided by the Linux kernel. In this case, it
1194 will map to all USB devices with vendor code
1130 and product code
1197 <p
>Note, it is important that the license of all the metadata files
1198 are compatible to have permissions to aggregate them into archive wide
1199 appstream files. Matthias suggested to use MIT or BSD licenses for
1200 these files. A challenge is figuring out a good id for the data, as
1201 it is supposed to be globally unique and shared across distributions
1202 (in other words, best to coordinate with upstream what to use). But
1203 it can be changed later or, so we went with the package name as
1204 upstream for this project is dormant.
</p
>
1206 <p
>To get the metadata file installed in the correct location for the
1207 mirror update scripts to pick it up and include its content the
1208 appstream data source, the file must be installed in the binary
1209 package under /usr/share/appdata/. I did this by adding the following
1210 line to debian/pymissile.install:
</p
>
1212 <blockquote
><pre
>
1213 debian/pymissile.metainfo.xml usr/share/appdata
1214 </pre
></blockquote
>
1216 <p
>With that in place, the command line tool isenkram-lookup will list
1217 all packages useful on the current computer automatically, and the GUI
1218 pop-up handler will propose to install the package not already
1219 installed if a hardware dongle is inserted into the machine in
1222 <p
>Details of the modalias field in appstream is available from the
1223 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
1225 <p
>To locate the modalias values of all hardware present in a machine,
1226 try running this command on the command line:
</p
>
1228 <blockquote
><pre
>
1229 cat $(find /sys/devices/|grep modalias)
1230 </pre
></blockquote
>
1232 <p
>To learn more about the isenkram system, please check out
1233 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1234 blog posts tagged isenkram
</a
>.
</p
>
1239 <title>The GNU General Public License is not magic pixie dust
</title>
1240 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
1241 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
1242 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
1243 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
1244 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
1245 GPL is not magic pixie dust
</a
>" explain the importance of making sure
1246 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
1247 I quote the blog post from Paul in full here with his permission:
<p
>
1251 <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
>
1254 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
1256 The first step is to choose a
1257 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
1260 The next step is, when someone fails to follow that copyleft license,
1261 <b
>it must be enforced
</b
><br/
>
1263 and its a simple fact of our modern society that such type of
1266 is incredibly expensive to do and incredibly difficult to do.
1269 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
1270 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
1271 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
1272 0x57</a
></small
></p
>
1274 <p
>As the Debian Website
1275 <a href=
"https://bugs.debian.org/
794116">used
</a
>
1276 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
1277 imply, public domain and permissively licensed software can lead to
1278 the production of more proprietary software as people discover useful
1279 software, extend it and or incorporate it into their hardware or
1280 software products. Copyleft licenses such as the GNU GPL were created
1281 to close off this avenue to the production of proprietary software but
1282 such licenses are not enough. With the ongoing adoption of Free
1283 Software by individuals and groups, inevitably the community
's
1284 expectations of license compliance are violated, usually out of
1285 ignorance of the way Free Software works, but not always. As Karen
1286 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
1287 Freedom
">FaiF
</a
>
1288 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
1289 copyleft is nothing if no-one is willing and able to stand up in court
1290 to protect it. The reality of today
's world is that legal
1291 representation is expensive, difficult and time consuming. With
1292 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
1293 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
1294 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
1295 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
1296 of the Linux project, Debian and other groups against GPL violations.
1297 In March the SFC supported a
1298 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
1299 by Christoph Hellwig
</a
> against VMware for refusing to
1300 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
1301 with the GPL
</a
> in relation to their use of parts of the Linux
1302 kernel. Since then two of their sponsors pulled corporate funding and
1304 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
1305 or cancelled their talks
</a
>. As a result they have decided to rely
1306 less on corporate funding and more on the broad community of
1307 individuals who support Free Software and copyleft. So the SFC has
1308 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
1309 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
1310 a community of folks who stand up for copyleft and the GPL by
1311 supporting their work on promoting and supporting copyleft and Free
1314 <p
>If you support Free Software,
1315 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
1316 what the SFC do, agree with their
1317 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
1318 principles
</a
>, are happy about their
1319 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
1320 work on a project that is an SFC
1321 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
1322 just want to stand up for copyleft, please join
1323 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
1324 Allan Webber
</a
>,
1325 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
1327 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
1328 Bacon
</a
>, myself and
1329 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
1331 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
1332 next week your donation will be
1333 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
1334 by an anonymous donor. Please also consider asking your employer to
1335 match your donation or become a sponsor of SFC. Don
't forget to
1336 spread the word about your support for SFC via email, your blog and or
1337 social media accounts.
</p
>
1341 <p
>I agree with Paul on this topic and just signed up as a Supporter
1342 of Software Freedom Conservancy myself. Perhaps you should be a
1343 supporter too?
</p
>
1348 <title>PGP key transition statement for key EE4E02F9
</title>
1349 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
1350 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
1351 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
1352 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
1353 set it up properly. I wanted to generate it offline and have it
1354 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
1355 smart card
</a
> for daily use, and learning how to do it and finding
1356 time to sit down with an offline machine almost took forever. But
1357 finally I
've been able to complete the process, and have now moved
1358 from my old GPG key to a new GPG key. See
1359 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
1360 full transition statement, signed with both my old and new key
</a
> for
1361 the details. This is my new key:
</p
>
1364 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
1365 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
1366 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
1367 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
1368 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
1369 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
1370 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
1373 <p
>The key can be downloaded from the OpenPGP key servers, signed by
1374 my old key.
</p
>
1376 <p
>If you signed my old key
1377 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
1378 I
'd very much appreciate a signature on my new key, details and
1379 instructions in the transition statement. I m happy to reciprocate if
1380 you have a similarly signed transition statement to present.
</p
>
1385 <title>The life and death of a laptop battery
</title>
1386 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
1387 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
1388 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
1389 <description><p
>When I get a new laptop, the battery life time at the start is OK.
1390 But this do not last. The last few laptops gave me a feeling that
1391 within a year, the life time is just a fraction of what it used to be,
1392 and it slowly become painful to use the laptop without power connected
1393 all the time. Because of this, when I got a new Thinkpad X230 laptop
1394 about two years ago, I decided to monitor its battery state to have
1395 more hard facts when the battery started to fail.
</p
>
1397 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
1399 <p
>First I tried to find a sensible Debian package to record the
1400 battery status, assuming that this must be a problem already handled
1401 by someone else. I found
1402 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
1403 which collects statistics from the battery, but it was completely
1404 broken. I sent a few suggestions to the maintainer, but decided to
1405 write my own collector as a shell script while I waited for feedback
1407 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
1408 blog post about the battery development on a MacBook Air
</a
> I also
1410 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
1411 available in Debian.
</p
>
1413 <p
>I started my collector
2013-
07-
15, and it has been collecting
1414 battery stats ever since. Now my
1415 /var/log/hjemmenett-battery-status.log file contain around
115,
000
1416 measurements, from the time the battery was working great until now,
1417 when it is unable to charge above
7% of original capacity. My
1418 collector shell script is quite simple and look like this:
</p
>
1423 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
1425 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
1426 logfile=/var/log/hjemmenett-battery-status.log
1428 files=
"manufacturer model_name technology serial_number \
1429 energy_full energy_full_design energy_now cycle_count status
"
1431 if [ ! -e
"$logfile
" ] ; then
1433 printf
"timestamp,
"
1435 printf
"%s,
" $f
1438 )
> "$logfile
"
1442 # Print complete message in one echo call, to avoid race condition
1443 # when several log processes run in parallel.
1444 msg=$(printf
"%s,
" $(date +%s); \
1445 for f in $files; do \
1446 printf
"%s,
" $(cat $f); \
1448 echo
"$msg
"
1451 cd /sys/class/power_supply
1454 (cd $bat
&& log_battery
>> "$logfile
")
1458 <p
>The script is called when the power management system detect a
1459 change in the power status (power plug in or out), and when going into
1460 and out of hibernation and suspend. In addition, it collect a value
1461 every
10 minutes. This make it possible for me know when the battery
1462 is discharging, charging and how the maximum charge change over time.
1463 The code for the Debian package
1464 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
1465 available on github
</a
>.
</p
>
1467 <p
>The collected log file look like this:
</p
>
1470 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
1471 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
1473 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1474 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1477 <p
>I wrote a small script to create a graph of the charge development
1478 over time. This graph depicted above show the slow death of my laptop
1481 <p
>But why is this happening? Why are my laptop batteries always
1482 dying in a year or two, while the batteries of space probes and
1483 satellites keep working year after year. If we are to believe
1484 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
1485 University
</a
>, the cause is me charging the battery whenever I have a
1486 chance, and the fix is to not charge the Lithium-ion batteries to
100%
1487 all the time, but to stay below
90% of full charge most of the time.
1488 I
've been told that the Tesla electric cars
1489 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
1490 the charge of their batteries to
80%
</a
>, with the option to charge to
1491 100% when preparing for a longer trip (not that I would want a car
1492 like Tesla where rights to privacy is abandoned, but that is another
1493 story), which I guess is the option we should have for laptops on
1494 Linux too.
</p
>
1496 <p
>Is there a good and generic way with Linux to tell the battery to
1497 stop charging at
80%, unless requested to charge to
100% once in
1498 preparation for a longer trip? I found
1499 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
1500 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
1501 80%
</a
>, but could not get it to work (kernel module refused to
1504 <p
>I wonder why the battery capacity was reported to be more than
100%
1505 at the start. I also wonder why the
"full capacity
" increases some
1506 times, and if it is possible to repeat the process to get the battery
1507 back to design capacity. And I wonder if the discharge and charge
1508 speed change over time, or if this stay the same. I did not yet try
1509 to write a tool to calculate the derivative values of the battery
1510 level, but suspect some interesting insights might be learned from
1513 <p
>Update
2015-
09-
24: I got a tip to install the packages
1514 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
1515 packages instead of the tp-smapi-dkms package I had tried to use
1516 initially, and use
'tlp setcharge
40 80' to change when charging start
1517 and stop. I
've done so now, but expect my existing battery is toast
1518 and need to be replaced. The proposal is unfortunately Thinkpad
1524 <title>New laptop - some more clues and ideas based on feedback
</title>
1525 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
1526 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
1527 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
1528 <description><p
>Several people contacted me after my previous blog post about my
1529 need for a new laptop, and provided very useful feedback. I wish to
1530 thank every one of these. Several pointed me to the possibility of
1531 fixing my X230, and I am already in the process of getting Lenovo to
1532 do so thanks to the on site, next day support contract covering the
1533 machine. But the battery is almost useless (I expect to replace it
1534 with a non-official battery) and I do not expect the machine to live
1535 for many more years, so it is time to plan its replacement. If I did
1536 not have a support contract, it was suggested to find replacement parts
1537 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
1538 might present a language barrier as I do not understand French.
</p
>
1540 <p
>One tip I got was to use the
1541 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
1542 compare laptop models. It seem to have more models available than
1543 prisjakt.no. Another tip I got from someone I know have similar
1544 keyboard preferences was that the HP EliteBook
840 keyboard is not
1545 very good, and this matches my experience with earlier EliteBook
1546 keyboards I tested. Because of this, I will not consider it any further.
1548 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
1549 newest Thinkpad X model. The keyboard reintroduces mouse buttons
1550 (which is missing from the X240), and is working fairly well with
1551 Debian Sid/Unstable according to
1552 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
1553 got on the keyboard quality are not consistent. Some say the keyboard
1554 is good, others say it is ok, while others say it is not very good.
1555 Those with experience from X41 and and X60 agree that the X250
1556 keyboard is not as good as those trusty old laptops, and suggest I
1557 keep and fix my X230 instead of upgrading, or get a used X230 to
1558 replace it. I
'm also told that the X250 lack leds for caps lock, disk
1559 activity and battery status, which is very convenient on my X230. I
'm
1560 also told that the CPU fan is running very often, making it a bit
1561 noisy. In any case, the X250 do not work out of the box with Debian
1562 Stable/Jessie, one of my requirements.
</p
>
1564 <p
>I have also gotten a few vendor proposals, one was
1565 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
1566 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
1567 The latter look very attractive to me.
</p
>
1569 <p
>Again, thank you all for the very useful feedback. It help a lot
1570 as I keep looking for a replacement.
</p
>
1572 <p
>Update
2015-
07-
06: I was recommended to check out the
1573 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
1575 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
1576 thinkpad X models
</a
>, and provide one year warranty.
</p
>
1581 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
1582 <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>
1583 <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>
1584 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
1585 <description><p
>My primary work horse laptop is failing, and will need a
1586 replacement soon. The left
5 cm of the screen on my Thinkpad X230
1587 started flickering yesterday, and I suspect the cause is a broken
1588 cable, as changing the angle of the screen some times get rid of the
1589 flickering.
</p
>
1591 <p
>My requirements have not really changed since I bought it, and is
1593 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
1594 described them in
2013</a
>. The last time I bought a laptop, I had
1596 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
1597 where I could select at least a few of the requirements (mouse pin,
1598 wifi, weight) and go through the rest manually. Three button mouse
1599 and a good keyboard is not available as an option, and all the three
1600 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
1601 G2) lack three mouse buttons). It is also unclear to me how good the
1602 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
1603 the keyboard, even if the quality and robustness in the X series have
1604 deteriorated since X41.
</p
>
1606 <p
>I wonder how I can find a sensible laptop when none of the options
1607 seem sensible to me? Are there better services around to search the
1608 set of available laptops for features? Please send me an email if you
1609 have suggestions.
</p
>
1611 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
1612 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
1613 of endorsed hardware
</a
>, which is useful background information.
</p
>
1618 <title>How to stay with sysvinit in Debian Jessie
</title>
1619 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
1620 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
1621 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
1622 <description><p
>By now, it is well known that Debian Jessie will not be using
1623 sysvinit as its boot system by default. But how can one keep using
1624 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
1626 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
1627 Schubert
</a
> and
1628 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
1631 <p
>If you already are using Wheezy and want to upgrade to Jessie and
1632 keep sysvinit as your boot system, create a file
1633 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
1634 you upgrade:
</p
>
1636 <p
><blockquote
><pre
>
1637 Package: systemd-sysv
1638 Pin: release o=Debian
1640 </pre
></blockquote
><p
>
1642 <p
>This file content will tell apt and aptitude to not consider
1643 installing systemd-sysv as part of any installation and upgrade
1644 solution when resolving dependencies, and thus tell it to avoid
1645 systemd as a default boot system. The end result should be that the
1646 upgraded system keep using sysvinit.
</p
>
1648 <p
>If you are installing Jessie for the first time, there is no way to
1649 get sysvinit installed by default (debootstrap used by
1650 debian-installer have no option for this), but one can tell the
1651 installer to switch to sysvinit before the first boot. Either by
1652 using a kernel argument to the installer, or by adding a line to the
1653 preseed file used. First, the kernel command line argument:
1655 <p
><blockquote
><pre
>
1656 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
1657 </pre
></blockquote
><p
>
1659 <p
>Next, the line to use in a preseed file:
</p
>
1661 <p
><blockquote
><pre
>
1662 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
1663 </pre
></blockquote
><p
>
1665 <p
>One can of course also do this after the first boot by installing
1666 the sysvinit-core package.
</p
>
1668 <p
>I recommend only using sysvinit if you really need it, as the
1669 sysvinit boot sequence in Debian have several hardware specific bugs
1670 on Linux caused by the fact that it is unpredictable when hardware
1671 devices show up during boot. But on the other hand, the new default
1672 boot system still have a few rough edges I hope will be fixed before
1673 Jessie is released.
</p
>
1675 <p
>Update
2014-
11-
26: Inspired by
1676 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
1677 blog post by Torsten Glaser
</a
>, added --purge to the preseed
1683 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
1684 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
1685 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
1686 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
1687 <description><p
>The right to communicate with your friends and family in private,
1688 without anyone snooping, is a right every citicen have in a liberal
1689 democracy. But this right is under serious attack these days.
</p
>
1691 <p
>A while back it occurred to me that one way to make the dragnet
1692 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
1693 the whisleblower Snowden) more expensive for Internet email,
1694 is to deliver all email using SMTP via Tor. Such SMTP option would be
1695 a nice addition to the FreedomBox project if we could send email
1696 between FreedomBox machines without leaking metadata about the emails
1697 to the people peeking on the wire. I
1698 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
1699 this on the FreedomBox project mailing list in October
</a
> and got a
1700 lot of useful feedback and suggestions. It also became obvious to me
1701 that this was not a novel idea, as the same idea was tested and
1702 documented by Johannes Berg as early as
2006, and both
1703 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
1704 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
1705 propose a similar method / protocol to pass emails between users.
</p
>
1707 <p
>To implement such system one need to set up a Tor hidden service
1708 providing the SMTP protocol on port
25, and use email addresses
1709 looking like username@hidden-service-name.onion. With such addresses
1710 the connections to port
25 on hidden-service-name.onion using Tor will
1711 go to the correct SMTP server. To do this, one need to configure the
1712 Tor daemon to provide the hidden service and the mail server to accept
1713 emails for this .onion domain. To learn more about Exim configuration
1714 in Debian and test the design provided by Johannes Berg in his FAQ, I
1715 set out yesterday to create a Debian package for making it trivial to
1716 set up such SMTP over Tor service based on Debian. Getting it to work
1717 were fairly easy, and
1718 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
1719 source code for the Debian package
</a
> is available from github. I
1720 plan to move it into Debian if further testing prove this to be a
1721 useful approach.
</p
>
1723 <p
>If you want to test this, set up a blank Debian machine without any
1724 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
1725 get rid of exim4). Install tor, clone the git repository mentioned
1726 above, build the deb and install it on the machine. Next, run
1727 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
1728 the instructions to get the service up and running. Restart tor and
1729 exim when it is done, and test mail delivery using swaks like
1732 <p
><blockquote
><pre
>
1733 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
1734 --to fbx@dutlqrrmjhtfa3vp.onion
1735 </pre
></blockquote
></p
>
1737 <p
>This will test the SMTP delivery using tor. Replace the email
1738 address with your own address to test your server. :)
</p
>
1740 <p
>The setup procedure is still to complex, and I hope it can be made
1741 easier and more automatic. Especially the tor setup need more work.
1742 Also, the package include a tor-smtp tool written in C, but its task
1743 should probably be rewritten in some script language to make the deb
1744 architecture independent. It would probably also make the code easier
1745 to review. The tor-smtp tool currently need to listen on a socket for
1746 exim to talk to it and is started using xinetd. It would be better if
1747 no daemon and no socket is needed. I suspect it is possible to get
1748 exim to run a command line tool for delivery instead of talking to a
1749 socket, and hope to figure out how in a future version of this
1752 <p
>Until I wipe my test machine, I can be reached using the
1753 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
1754 SMTorP. :)
</p
>
1759 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
1760 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
1761 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
1762 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
1763 <description><p
>If you ever had to moderate a mailman list, like the ones on
1764 alioth.debian.org, you know the web interface is fairly slow to
1765 operate. First you visit one web page, enter the moderation password
1766 and get a new page shown with a list of all the messages to moderate
1767 and various options for each email address. This take a while for
1768 every list you moderate, and you need to do it regularly to do a good
1769 job as a list moderator. But there is a quick alternative,
1770 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
1771 listadmin program
</a
>. It allow you to check lists for new messages
1772 to moderate in a fraction of a second. Here is a test run on two
1773 lists I recently took over:
</p
>
1775 <p
><blockquote
><pre
>
1776 % time listadmin xiph
1777 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1778 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1784 </pre
></blockquote
></p
>
1786 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
1787 there are no message in the moderation queue. Every morning I
1788 currently moderate
68 mailman lists, and it normally take around two
1789 minutes. When I took over the two pkg-xiph lists above a few days
1790 ago, there were
400 emails waiting in the moderator queue. It took me
1791 less than
15 minutes to process them all using the listadmin
1794 <p
>If you install
1795 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
1796 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
1797 with content like this, the moderation task is a breeze:
</p
>
1799 <p
><blockquote
><pre
>
1800 username username@example.org
1803 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
1806 adminurl https://{domain}/mailman/admindb/{list}
1807 mailman-list@lists.example.com
1810 other-list@otherserver.example.org
1811 </pre
></blockquote
></p
>
1813 <p
>There are other options to set as well. Check the manual page to
1814 learn the details.
</p
>
1816 <p
>If you are forced to moderate lists on a mailman installation where
1817 the SSL certificate is self signed or not properly signed by a
1818 generally accepted signing authority, you can set a environment
1819 variable when calling listadmin to disable SSL verification:
</p
>
1821 <p
><blockquote
><pre
>
1822 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
1823 </pre
></blockquote
></p
>
1825 <p
>If you want to moderate a subset of the lists you take care of, you
1826 can provide an argument to the listadmin script like I do in the
1827 initial screen dump (the xiph argument). Using an argument, only
1828 lists matching the argument string will be processed. This make it
1829 quick to accept messages if you notice the moderation request in your
1832 <p
>Without the listadmin program, I would never be the moderator of
68
1833 mailing lists, as I simply do not have time to spend on that if the
1834 process was any slower. The listadmin program have saved me hours of
1835 time I could spend elsewhere over the years. It truly is nice free
1838 <p
>As usual, if you use Bitcoin and want to show your support of my
1839 activities, please send Bitcoin donations to my address
1840 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1842 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
1843 configuration example. Also, I
've been told that the
1844 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
1850 <title>Debian Jessie, PXE and automatic firmware installation
</title>
1851 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
1852 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
1853 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
1854 <description><p
>When PXE installing laptops with Debian, I often run into the
1855 problem that the WiFi card require some firmware to work properly.
1856 And it has been a pain to fix this using preseeding in Debian.
1857 Normally something more is needed. But thanks to
1858 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
1859 package
</a
> and its recent tasksel extension, it has now become easy
1860 to do this using simple preseeding.
</p
>
1862 <p
>The isenkram-cli package provide tasksel tasks which will install
1863 firmware for the hardware found in the machine (actually, requested by
1864 the kernel modules for the hardware). (It can also install user space
1865 programs supporting the hardware detected, but that is not the focus
1866 of this story.)
</p
>
1868 <p
>To get this working in the default installation, two preeseding
1869 values are needed. First, the isenkram-cli package must be installed
1870 into the target chroot (aka the hard drive) before tasksel is executed
1871 in the pkgsel step of the debian-installer system. This is done by
1872 preseeding the base-installer/includes debconf value to include the
1873 isenkram-cli package. The package name is next passed to debootstrap
1874 for installation. With the isenkram-cli package in place, tasksel
1875 will automatically use the isenkram tasks to detect hardware specific
1876 packages for the machine being installed and install them, because
1877 isenkram-cli contain tasksel tasks.
</p
>
1879 <p
>Second, one need to enable the non-free APT repository, because
1880 most firmware unfortunately is non-free. This is done by preseeding
1881 the apt-mirror-setup step. This is unfortunate, but for a lot of
1882 hardware it is the only option in Debian.
</p
>
1884 <p
>The end result is two lines needed in your preseeding file to get
1885 firmware installed automatically by the installer:
</p
>
1887 <p
><blockquote
><pre
>
1888 base-installer base-installer/includes string isenkram-cli
1889 apt-mirror-setup apt-setup/non-free boolean true
1890 </pre
></blockquote
></p
>
1892 <p
>The current version of isenkram-cli in testing/jessie will install
1893 both firmware and user space packages when using this method. It also
1894 do not work well, so use version
0.15 or later. Installing both
1895 firmware and user space packages might give you a bit more than you
1896 want, so I decided to split the tasksel task in two, one for firmware
1897 and one for user space programs. The firmware task is enabled by
1898 default, while the one for user space programs is not. This split is
1899 implemented in the package currently in unstable.
</p
>
1901 <p
>If you decide to give this a go, please let me know (via email) how
1902 this recipe work for you. :)
</p
>
1904 <p
>So, I bet you are wondering, how can this work. First and
1905 foremost, it work because tasksel is modular, and driven by whatever
1906 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1907 isenkram-cli package place two files for tasksel to find. First there
1908 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
1910 <p
><blockquote
><pre
>
1911 Task: isenkram-packages
1913 Description: Hardware specific packages (autodetected by isenkram)
1914 Based on the detected hardware various hardware specific packages are
1916 Test-new-install: show show
1918 Packages: for-current-hardware
1920 Task: isenkram-firmware
1922 Description: Hardware specific firmware packages (autodetected by isenkram)
1923 Based on the detected hardware various hardware specific firmware
1924 packages are proposed.
1925 Test-new-install: mark show
1927 Packages: for-current-hardware-firmware
1928 </pre
></blockquote
></p
>
1930 <p
>The key parts are Test-new-install which indicate how the task
1931 should be handled and the Packages line referencing to a script in
1932 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1933 list of packages to install. The for-current-hardware-firmware script
1934 look like this to list relevant firmware for the machine:
1936 <p
><blockquote
><pre
>
1939 PATH=/usr/sbin:$PATH
1941 isenkram-autoinstall-firmware -l
1942 </pre
></blockquote
></p
>
1944 <p
>With those two pieces in place, the firmware is installed by
1945 tasksel during the normal d-i run. :)
</p
>
1947 <p
>If you want to test what tasksel will install when isenkram-cli is
1948 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
1949 --new-install
</tt
> to get the list of packages that tasksel would
1952 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
1953 pilots in testing this feature, as isenkram is used there now to
1954 install firmware, replacing the earlier scripts.
</p
>
1959 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
1960 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
1961 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
1962 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
1963 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
1964 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1965 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
1966 on a screen normally showing the bread types and prizes:
</p
>
1968 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
1970 <p
>If it had booted as it was supposed to, I would never had known
1971 about this hidden Linux installation. It is interesting what
1972 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
1977 <title>New lsdvd release version
0.17 is ready
</title>
1978 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
1979 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
1980 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
1981 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
1982 got a new set of developers a few weeks ago, after the original
1983 developer decided to step down and pass the project to fresh blood.
1984 This project is now maintained by Petter Reinholdtsen and Steve
1987 <p
>I just wrapped up
1988 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
1989 new lsdvd release
</a
>, available in git or from
1990 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
1991 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
1996 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
1997 <li
>Check for garbage in the program chains, which indicate that a track is
1998 non-existant, to work around additional copy protection
</li
>
1999 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
2000 <li
>Fix pallete display of first entry
</li
>
2001 <li
>Fix include orders
</li
>
2002 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
2003 <li
>Fix the chapter count
</li
>
2004 <li
>Make sure the array size and the array limit used when initialising
2005 the palette size is the same.
</li
>
2006 <li
>Fix array printing.
</li
>
2007 <li
>Correct subsecond calculations.
</li
>
2008 <li
>Add sector information to the output format.
</li
>
2009 <li
>Clean up code to be closer to ANSI C and compile without warnings
2010 with more GCC compiler warnings.
</li
>
2014 <p
>This change bring together patches for lsdvd in use in various
2015 Linux and Unix distributions, as well as patches submitted to the
2016 project the last nine years. Please check it out. :)
</p
>
2021 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
2022 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
2023 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
2024 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
2025 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2026 project
</a
> provide a Linux solution for schools, including a
2027 powerful desktop with education software, a central server providing
2028 web pages, user database, user home directories, central login and PXE
2029 boot of both clients without disk and the installation to install Debian
2030 Edu on machines with disk (and a few other services perhaps to small
2031 to mention here). We in the Debian Edu team are currently working on
2032 the Jessie based version, trying to get everything in shape before the
2033 freeze, to avoid having to maintain our own package repository in the
2035 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
2036 status
</a
> can be seen on the Debian wiki, and there is still heaps of
2037 work left. Some fatal problems block testing, breaking the installer,
2038 but it is possible to work around these to get anyway. Here is a
2039 recipe on how to get the installation limping along.
</p
>
2041 <p
>First, download the test ISO via
2042 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
2043 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
2045 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
2046 The ISO build was broken on Tuesday, so we do not get a new ISO every
2047 12 hours or so, but thankfully the ISO we already got we are able to
2048 install with some tweaking.
</p
>
2050 <p
>When you get to the Debian Edu profile question, go to tty2
2051 (use Alt-Ctrl-F2), run
</p
>
2053 <p
><blockquote
><pre
>
2054 nano /usr/bin/edu-eatmydata-install
2055 </pre
></blockquote
></p
>
2057 <p
>and add
'exit
0' as the second line, disabling the eatmydata
2058 optimization. Return to the installation, select the profile you want
2059 and continue. Without this change, exim4-config will fail to install
2060 due to a known bug in eatmydata.
</p
>
2062 <p
>When you get the grub question at the end, answer /dev/sda (or if
2063 this do not work, figure out what your correct value would be. All my
2064 test machines need /dev/sda, so I have no advice if it do not fit
2065 your need.
</p
>
2067 <p
>If you installed a profile including a graphical desktop, log in as
2068 root after the initial boot from hard drive, and install the
2069 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
2070 or mate. If you want several desktop options, install more than one
2071 metapackage. Once this is done, reboot and you should have a working
2072 graphical login screen. This workaround should no longer be needed
2073 once the education-tasks package version
1.801 enter testing in two
2076 <p
>I believe the ISO build will start working on two days when the new
2077 tasksel package enter testing and Steve McIntyre get a chance to
2078 update the debian-cd git repository. The eatmydata, grub and desktop
2079 issues are already fixed in unstable and testing, and should show up
2080 on the ISO as soon as the ISO build start working again. Well the
2081 eatmydata optimization is really just disabled. The proper fix
2082 require an upload by the eatmydata maintainer applying the patch
2083 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
2084 The rest have proper fixes in unstable.
</p
>
2086 <p
>I hope this get you going with the installation testing, as we are
2087 quickly running out of time trying to get our Jessie based
2088 installation ready before the distribution freeze in a month.
</p
>
2093 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
2094 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
2095 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
2096 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
2097 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
2098 to handle my fairly large DVD collection. It is a nice command line
2099 tool to get details about a DVD, like title, tracks, track length,
2100 etc, in XML, Perl or human readable format. But lsdvd have not seen
2101 any new development since
2006 and had a few irritating bugs affecting
2102 its use with some DVDs. Upstream seemed to be dead, and in January I
2103 sent a small probe asking for a version control repository for the
2104 project, without any reply. But I use it regularly and would like to
2105 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
2106 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
2107 the project admin, and after getting a reply from him explaining that
2108 he was no longer interested in the project, I asked if I could take
2109 over. And yesterday, I became project admin.
</p
>
2111 <p
>I
've been in touch with a Gentoo developer and the Debian
2112 maintainer interested in joining forces to maintain the upstream
2113 project, and I hope we can get a new release out fairly quickly,
2114 collecting the patches spread around on the internet into on place.
2115 I
've added the relevant Debian patches to the freshly created git
2116 repository, and expect the Gentoo patches to make it too. If you got
2117 a DVD collection and care about command line tools, check out
2118 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
2119 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
2120 list
</a
>. :)
</p
>
2125 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
2126 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
2127 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
2128 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
2129 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
2130 a lot quicker. When we install more than
2000 packages in
2131 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
2132 tasksel in the installer, unpacking the binary packages take forever.
2133 A part of the slow I/O issue was discussed in
2134 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
2135 much file system sync-ing done by dpkg, which is the package
2136 responsible for unpacking the binary packages. Other parts (like code
2137 executed by postinst scripts) might also sync to disk during
2138 installation. All this sync-ing to disk do not really make sense to
2139 me. If the machine crash half-way through, I start over, I do not try
2140 to salvage the half installed system. So the failure sync-ing is
2141 supposed to protect against, hardware or system crash, is not really
2142 relevant while the installer is running.
</p
>
2144 <p
>A few days ago, I thought of a way to get rid of all the file
2145 system sync()-ing in a fairly non-intrusive way, without the need to
2146 change the code in several packages. The idea is not new, but I have
2147 not heard anyone propose the approach using dpkg-divert before. It
2148 depend on the small and clever package
2149 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
2150 uses LD_PRELOAD to replace the system functions for syncing data to
2151 disk with functions doing nothing, thus allowing programs to live
2152 dangerous while speeding up disk I/O significantly. Instead of
2153 modifying the implementation of dpkg, apt and tasksel (which are the
2154 packages responsible for selecting, fetching and installing packages),
2155 it occurred to me that we could just divert the programs away, replace
2156 them with a simple shell wrapper calling
2157 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
2158 Two days ago I decided to test the idea, and wrapped up a simple
2159 implementation for the Debian Edu udeb.
</p
>
2161 <p
>The effect was stunning. In my first test it reduced the running
2162 time of the pkgsel step (installing tasks) from
64 to less than
44
2163 minutes (
20 minutes shaved off the installation) on an old Dell
2164 Latitude D505 machine. I am not quite sure what the optimised time
2165 would have been, as I messed up the testing a bit, causing the debconf
2166 priority to get low enough for two questions to pop up during
2167 installation. As soon as I saw the questions I moved the installation
2168 along, but do not know how long the question were holding up the
2169 installation. I did some more measurements using Debian Edu Jessie,
2170 and got these results. The time measured is the time stamp in
2171 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
2172 "pkgsel: finishing up
" lines, if you want to do the same measurement
2173 yourself. In Debian Edu, the tasksel dialog do not show up, and the
2174 timing thus do not depend on how quickly the user handle the tasksel
2177 <p
><table
>
2180 <th
>Machine/setup
</th
>
2181 <th
>Original tasksel
</th
>
2182 <th
>Optimised tasksel
</th
>
2183 <th
>Reduction
</th
>
2187 <td
>Latitude D505 Main+LTSP LXDE
</td
>
2188 <td
>64 min (
07:
46-
08:
50)
</td
>
2189 <td
><44 min (
11:
27-
12:
11)
</td
>
2190 <td
>>20 min
18%
</td
>
2194 <td
>Latitude D505 Roaming LXDE
</td
>
2195 <td
>57 min (
08:
48-
09:
45)
</td
>
2196 <td
>34 min (
07:
43-
08:
17)
</td
>
2197 <td
>23 min
40%
</td
>
2201 <td
>Latitude D505 Minimal
</td
>
2202 <td
>22 min (
10:
37-
10:
59)
</td
>
2203 <td
>11 min (
11:
16-
11:
27)
</td
>
2204 <td
>11 min
50%
</td
>
2208 <td
>Thinkpad X200 Minimal
</td
>
2209 <td
>6 min (
08:
19-
08:
25)
</td
>
2210 <td
>4 min (
08:
04-
08:
08)
</td
>
2211 <td
>2 min
33%
</td
>
2215 <td
>Thinkpad X200 Roaming KDE
</td
>
2216 <td
>19 min (
09:
21-
09:
40)
</td
>
2217 <td
>15 min (
10:
25-
10:
40)
</td
>
2218 <td
>4 min
21%
</td
>
2221 </table
></p
>
2223 <p
>The test is done using a netinst ISO on a USB stick, so some of the
2224 time is spent downloading packages. The connection to the Internet
2225 was
100Mbit/s during testing, so downloading should not be a
2226 significant factor in the measurement. Download typically took a few
2227 seconds to a few minutes, depending on the amount of packages being
2228 installed.
</p
>
2230 <p
>The speedup is implemented by using two hooks in
2231 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
2232 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
2233 finish-install.d hook to remove the divert at the end of the
2234 installation. I picked the pre-pkgsel.d hook instead of the
2235 post-base-installer.d hook because I test using an ISO without the
2236 eatmydata package included, and the post-base-installer.d hook in
2237 Debian Edu can only operate on packages included in the ISO. The
2238 negative effect of this is that I am unable to activate this
2239 optimization for the kernel installation step in d-i. If the code is
2240 moved to the post-base-installer.d hook, the speedup would be larger
2241 for the entire installation.
</p
>
2243 <p
>I
've implemented this in the
2244 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
2245 git repository, and plan to provide the optimization as part of the
2246 Debian Edu installation. If you want to test this yourself, you can
2247 create two files in the installer (or in an udeb). One shell script
2248 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
2250 <p
><blockquote
><pre
>
2253 . /usr/share/debconf/confmodule
2255 logger -t my-pkgsel
"info: $*
"
2258 logger -t my-pkgsel
"error: $*
"
2260 override_install() {
2261 apt-install eatmydata || true
2262 if [ -x /target/usr/bin/eatmydata ] ; then
2263 for bin in dpkg apt-get aptitude tasksel ; do
2265 # Test that the file exist and have not been diverted already.
2266 if [ -f /target$file ] ; then
2267 info
"diverting $file using eatmydata
"
2268 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
2269 > /target$file.edu
2270 chmod
755 /target$file.edu
2271 in-target dpkg-divert --package debian-edu-config \
2272 --rename --quiet --add $file
2273 ln -sf ./$bin.edu /target$file
2275 error
"unable to divert $file, as it is missing.
"
2279 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
2284 </pre
></blockquote
></p
>
2286 <p
>To clean up, another shell script should go into
2287 /usr/lib/finish-install.d/ with code like this:
2289 <p
><blockquote
><pre
>
2291 . /usr/share/debconf/confmodule
2293 logger -t my-finish-install
"error: $@
"
2295 remove_install_override() {
2296 for bin in dpkg apt-get aptitude tasksel ; do
2298 if [ -x /target$file.edu ] ; then
2300 in-target dpkg-divert --package debian-edu-config \
2301 --rename --quiet --remove $file
2304 error
"Missing divert for $file.
"
2307 sync # Flush file buffers before continuing
2310 remove_install_override
2311 </pre
></blockquote
></p
>
2313 <p
>In Debian Edu, I placed both code fragments in a separate script
2314 edu-eatmydata-install and call it from the pre-pkgsel.d and
2315 finish-install.d scripts.
</p
>
2317 <p
>By now you might ask if this change should get into the normal
2318 Debian installer too? I suspect it should, but am not sure the
2319 current debian-installer coordinators find it useful enough. It also
2320 depend on the side effects of the change. I
'm not aware of any, but I
2321 guess we will see if the change is safe after some more testing.
2322 Perhaps there is some package in Debian depending on sync() and
2323 fsync() having effect? Perhaps it should go into its own udeb, to
2324 allow those of us wanting to enable it to do so without affecting
2327 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
2328 will break installation of all programs using gnutls because of
2329 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
2330 eatmydata package in Debian will solve it.
</p
>
2332 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
2333 the optimization work again. And I have discovered that the
2334 dpkg-divert trick is not really needed and implemented a slightly
2335 simpler approach as part of the debian-edu-install package. See
2336 tools/edu-eatmydata-install in the source package.
</p
>
2338 <p
>Update
2014-
11-
11: Unfortunately, a new
2339 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
2340 triggering on i386 made it into testing, and broke this installation
2341 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
2342 request
768893</a
> is accepted, it should be working again.
</p
>
2347 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
2348 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
2349 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
2350 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
2351 <description><p
>Yesterday, I had the pleasure of attending a talk with the
2352 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
2353 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
2354 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
2355 learn that there is a large set of publicly available key servers to
2356 use when looking for peoples public key. So far I have used
2357 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
2358 were misbehaving, but those days are ended. The servers I have used
2359 up until yesterday have been slow and some times unavailable. I hope
2360 those problems are gone now.
</p
>
2362 <p
>Behind the round robin DNS entry of the
2363 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
2364 there is a pool of more than
100 keyservers which are checked every
2365 day to ensure they are well connected and up to date. It must be
2366 better than what I have used so far. :)
</p
>
2368 <p
>Yesterdays speaker told me that the service is the default
2369 keyserver provided by the default configuration in GnuPG, but this do
2370 not seem to be used in Debian. Perhaps it should?
</p
>
2372 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
2375 <p
><blockquote
><pre
>
2376 keyserver pool.sks-keyservers.net
2377 </pre
></blockquote
></p
>
2379 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
2380 entries in DNS. Just for fun, I did just that at work, so now every
2381 user of GnuPG at the University of Oslo should find a OpenGPG
2382 keyserver automatically should their need it:
</p
>
2384 <p
><blockquote
><pre
>
2385 % host -t srv _pgpkey-http._tcp.uio.no
2386 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
2388 </pre
></blockquote
></p
>
2390 <p
>Now if only
2391 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
2392 HKP lookup protocol
</a
> supported finding signature paths, I would be
2393 very happy. It can look up a given key or search for a user ID, but I
2394 normally do not want that, but to find a trust path from my key to
2395 another key. Given a user ID or key ID, I would like to find (and
2396 download) the keys representing a signature path from my key to the
2397 key in question, to be able to get a trust path between the two keys.
2398 This is as far as I can tell not possible today. Perhaps something
2399 for a future version of the protocol?
</p
>
2404 <title>From English wiki to translated PDF and epub via Docbook
</title>
2405 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
2406 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
2407 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
2408 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2409 project
</a
> provide an instruction manual for teachers, system
2410 administrators and other users that contain useful tips for setting up
2411 and maintaining a Debian Edu installation. This text is about how the
2412 text processing of this manual is handled in the project.
</p
>
2414 <p
>One goal of the project is to provide information in the native
2415 language of its users, and for this we need to handle translations.
2416 But we also want to make sure each language contain the same
2417 information, so for this we need a good way to keep the translations
2418 in sync. And we want it to be easy for our users to improve the
2419 documentation, avoiding the need to learn special formats or tools to
2420 contribute, and the obvious way to do this is to make it possible to
2421 edit the documentation using a web browser. We also want it to be
2422 easy for translators to keep the translation up to date, and give them
2423 help in figuring out what need to be translated. Here is the list of
2424 tools and the process we have found trying to reach all these
2427 <p
>We maintain the authoritative source of our manual in the
2428 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
2429 wiki
</a
>, as several wiki pages written in English. It consist of one
2430 front page with references to the different chapters, several pages
2431 for each chapter, and finally one
"collection page
" gluing all the
2432 chapters together into one large web page (aka
2433 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
2434 AllInOne page
</a
>). The AllInOne page is the one used for further
2435 processing and translations. Thanks to the fact that the
2436 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
2437 wiki.debian.org support exporting pages in
2438 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
2439 the list of pages to export using the raw version of the AllInOne
2440 page, loop over each of them to generate a Docbook XML version of the
2441 manual. This process also download images and transform image
2442 references to use the locally downloaded images. The generated
2443 Docbook XML files are slightly broken, so some post-processing is done
2444 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
2445 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
2446 a handfull of images. The XML file can now be used to generate PDF, HTML
2447 and epub versions of the English manual. This is the basic step of
2448 our process, making PDF (using dblatex), HTML (using xsltproc) and
2449 epub (using dbtoepub) version from Docbook XML, and the resulting files
2450 are placed in the debian-edu-doc-en binary package.
</p
>
2452 <p
>But English documentation is not enough for us. We want translated
2453 documentation too, and we want to make it easy for translators to
2454 track the English original. For this we use the
2455 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
2456 which allow us to transform the English Docbook XML file into a
2457 translation file (a .pot file), usable with the normal gettext based
2458 translation tools used by those translating free software. The pot
2459 file is used to create and maintain translation files (several .po
2460 files), which the translations update with the native language
2461 translations of all titles, paragraphs and blocks of text in the
2462 original. The next step is combining the original English Docbook XML
2463 and the translation file (say debian-edu-wheezy-manual.nb.po), to
2464 create a translated Docbook XML file (in this case
2465 debian-edu-wheezy-manual.nb.xml). This translated (or partly
2466 translated, if the translation is not complete) Docbook XML file can
2467 then be used like the original to create a PDF, HTML and epub version
2468 of the documentation.
</p
>
2470 <p
>The translators use different tools to edit the .po files. We
2472 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
2473 while some use emacs and vi, others can use web based editors like
2474 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
2475 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
2476 is where the .po file end up, in our git repository. Updated
2477 translations can either be committed directly to git, or submitted as
2478 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
2479 against the debian-edu-doc package
</a
>.
</p
>
2481 <p
>One challenge is images, which both might need to be translated (if
2482 they show translated user applications), and are needed in different
2483 formats when creating PDF and HTML versions (epub is a HTML version in
2484 this regard). For this we transform the original PNG images to the
2485 needed density and format during build, and have a way to provide
2486 translated images by storing translated versions in
2487 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
2488 package maintainers know more.
</p
>
2490 <p
>If you wonder what the result look like, we provide
2491 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
2492 of the documentation packages on the web
</a
>. See for example the
2493 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
2494 PDF version
</a
> or the
2495 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
2496 HTML version
</a
>. We do not yet build the epub version by default,
2497 but perhaps it will be done in the future.
</p
>
2499 <p
>To learn more, check out
2500 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
2501 debian-edu-doc package
</a
>,
2502 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
2503 manual on the wiki
</a
> and
2504 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
2505 translation instructions
</a
> in the manual.
</p
>
2510 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
2511 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
2512 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
2513 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
2514 <description><p
>It would be nice if it was easier in Debian to get all the hardware
2515 related packages relevant for the computer installed automatically.
2516 So I implemented one, using
2517 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
2518 package
</a
>. To use it, install the tasksel and isenkram packages and
2519 run tasksel as user root. You should be presented with a new option,
2520 "Hardware specific packages (autodetected by isenkram)
". When you
2521 select it, tasksel will install the packages isenkram claim is fit for
2522 the current hardware, hot pluggable or not.
<p
>
2524 <p
>The implementation is in two files, one is the tasksel menu entry
2525 description, and the other is the script used to extract the list of
2526 packages to install. The first part is in
2527 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
2530 <p
><blockquote
><pre
>
2533 Description: Hardware specific packages (autodetected by isenkram)
2534 Based on the detected hardware various hardware specific packages are
2536 Test-new-install: mark show
2538 Packages: for-current-hardware
2539 </pre
></blockquote
></p
>
2541 <p
>The second part is in
2542 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
2545 <p
><blockquote
><pre
>
2550 isenkram-autoinstall-firmware -l
2552 </pre
></blockquote
></p
>
2554 <p
>All in all, a very short and simple implementation making it
2555 trivial to install the hardware dependent package we all may want to
2556 have installed on our machines. I
've not been able to find a way to
2557 get tasksel to tell you exactly which packages it plan to install
2558 before doing the installation. So if you are curious or careful,
2559 check the output from the isenkram-* command line tools first.
</p
>
2561 <p
>The information about which packages are handling which hardware is
2562 fetched either from the isenkram package itself in
2563 /usr/share/isenkram/, from git.debian.org or from the APT package
2564 database (using the Modaliases header). The APT package database
2565 parsing have caused a nasty resource leak in the isenkram daemon (bugs
2566 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
2567 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
2568 the python-apt code (bug
2569 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
2570 workaround I was able to get rid of the file descriptor leak and
2571 reduce the memory leak from ~
30 MiB per hardware detection down to
2572 around
2 MiB per hardware detection. It should make the desktop
2573 daemon a lot more useful. The fix is in version
0.7 uploaded to
2574 unstable today.
</p
>
2576 <p
>I believe the current way of mapping hardware to packages in
2577 Isenkram is is a good draft, but in the future I expect isenkram to
2578 use the AppStream data source for this. A proposal for getting proper
2579 AppStream support into Debian is floating around as
2580 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
2581 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
2582 project
</a
> will take place this summer to improve the situation. I
2583 look forward to seeing the result, and welcome patches for isenkram to
2584 start using the information when it is ready.
</p
>
2586 <p
>If you want your package to map to some specific hardware, either
2587 add a
"Xb-Modaliases
" header to your control file like I did in
2588 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
2589 package
</a
> or submit a bug report with the details to the isenkram
2591 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
2592 blog posts tagged isenkram
</a
> for details on the notation. I expect
2593 the information will be migrated to AppStream eventually, but for the
2594 moment I got no better place to store it.
</p
>
2599 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
2600 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
2601 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
2602 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
2603 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
2604 project
</a
> is working on providing the software and hardware to make
2605 it easy for non-technical people to host their data and communication
2606 at home, and being able to communicate with their friends and family
2607 encrypted and away from prying eyes. It is still going strong, and
2608 today a major mile stone was reached.
</p
>
2610 <p
>Today, the last of the packages currently used by the project to
2611 created the system images were accepted into Debian Unstable. It was
2612 the freedombox-setup package, which is used to configure the images
2613 during build and on the first boot. Now all one need to get going is
2614 the build code from the freedom-maker git repository and packages from
2615 Debian. And once the freedombox-setup package enter testing, we can
2616 build everything directly from Debian. :)
</p
>
2618 <p
>Some key packages used by Freedombox are
2619 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
2620 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
2621 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
2622 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
2623 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
2624 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
2625 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
2626 are plans to integrate more packages into the setup. User
2627 documentation is maintained on the Debian wiki. Please
2628 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
2629 the manual
</a
> and help us improve it.
</p
>
2631 <p
>To test for yourself and create boot images with the FreedomBox
2632 setup, run this on a Debian machine using a user with sudo rights to
2633 become root:
</p
>
2635 <p
><pre
>
2636 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2637 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2639 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2641 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2642 </pre
></p
>
2644 <p
>Root access is needed to run debootstrap and mount loopback
2645 devices. See the README in the freedom-maker git repo for more
2646 details on the build. If you do not want all three images, trim the
2647 make line. Note that the virtualbox-image target is not really
2648 virtualbox specific. It create a x86 image usable in kvm, qemu,
2649 vmware and any other x86 virtual machine environment. You might need
2650 the version of vmdebootstrap in Jessie to get the build working, as it
2651 include fixes for a race condition with kpartx.
</p
>
2653 <p
>If you instead want to install using a Debian CD and the preseed
2654 method, boot a Debian Wheezy ISO and use this boot argument to load
2655 the preseed values:
</p
>
2657 <p
><pre
>
2658 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
2659 </pre
></p
>
2661 <p
>I have not tested it myself the last few weeks, so I do not know if
2662 it still work.
</p
>
2664 <p
>If you wonder how to help, one task you could look at is using
2665 systemd as the boot system. It will become the default for Linux in
2666 Jessie, so we need to make sure it is usable on the Freedombox. I did
2667 a simple test a few weeks ago, and noticed dnsmasq failed to start
2668 during boot when using systemd. I suspect there are other problems
2669 too. :) To detect problems, there is a test suite included, which can
2670 be run from the plinth web interface.
</p
>
2672 <p
>Give it a go and let us know how it goes on the mailing list, and help
2673 us get the new release published. :) Please join us on
2674 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
2675 irc.debian.org)
</a
> and
2676 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2677 mailing list
</a
> if you want to help make this vision come true.
</p
>
2682 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
2683 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
2684 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
2685 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
2686 <description><p
>For a while now, I have been looking for a sensible offsite backup
2687 solution for use at home. My requirements are simple, it must be
2688 cheap and locally encrypted (in other words, I keep the encryption
2689 keys, the storage provider do not have access to my private files).
2690 One idea me and my friends had many years ago, before the cloud
2691 storage providers showed up, was to use Google mail as storage,
2692 writing a Linux block device storing blocks as emails in the mail
2693 service provided by Google, and thus get heaps of free space. On top
2694 of this one can add encryption, RAID and volume management to have
2695 lots of (fairly slow, I admit that) cheap and encrypted storage. But
2696 I never found time to implement such system. But the last few weeks I
2697 have looked at a system called
2698 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
2699 mounted network backed file system with the features I need.
</p
>
2701 <p
>S3QL is a fuse file system with a local cache and cloud storage,
2702 handling several different storage providers, any with Amazon S3,
2703 Google Drive or OpenStack API. There are heaps of such storage
2704 providers. S3QL can also use a local directory as storage, which
2705 combined with sshfs allow for file storage on any ssh server. S3QL
2706 include support for encryption, compression, de-duplication, snapshots
2707 and immutable file systems, allowing me to mount the remote storage as
2708 a local mount point, look at and use the files as if they were local,
2709 while the content is stored in the cloud as well. This allow me to
2710 have a backup that should survive fire. The file system can not be
2711 shared between several machines at the same time, as only one can
2712 mount it at the time, but any machine with the encryption key and
2713 access to the storage service can mount it if it is unmounted.
</p
>
2715 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
2716 package is included already. So to get started, run
<tt
>apt-get
2717 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
2718 Greenqloud, after reading their nice recipe on
2719 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
2720 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
2721 in Iceland more than those in USA when it come to keeping my personal
2722 data safe and private, and thus would rather spend money on a company
2723 in Iceland. Another nice recipe is available from the article
2724 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
2725 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
2726 Admin magazine. When the provider is picked, figure out how to get
2727 the API key needed to connect to the storage API. With Greencloud,
2728 the key did not show up until I had added payment details to my
2731 <p
>Armed with the API access details, it is time to create the file
2732 system. First, create a new bucket in the cloud. This bucket is the
2733 file system storage area. I picked a bucket name reflecting the
2734 machine that was going to store data there, but any name will do.
2735 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
2736 the API login and password, and a locally created password. Store it
2737 all in ~root/.s3ql/authinfo2 like this:
2739 <p
><blockquote
><pre
>
2741 storage-url: s3c://s.greenqloud.com:
443/bucket-name
2742 backend-login: API-login
2743 backend-password: API-password
2744 fs-passphrase: local-password
2745 </pre
></blockquote
></p
>
2747 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
2748 but any sensible way to create a fairly random password should do it.
2749 Armed with these details, it is now time to run mkfs, entering the API
2750 details and password to create it:
</p
>
2752 <p
><blockquote
><pre
>
2753 # mkdir -m
700 /var/lib/s3ql-cache
2754 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2755 --ssl s3c://s.greenqloud.com:
443/bucket-name
2756 Enter backend login:
2757 Enter backend password:
2758 Before using S3QL, make sure to read the user
's guide, especially
2759 the
'Important Rules to Avoid Loosing Data
' section.
2760 Enter encryption password:
2761 Confirm encryption password:
2762 Generating random encryption key...
2763 Creating metadata tables...
2773 Compressing and uploading metadata...
2774 Wrote
0.00 MB of compressed metadata.
2775 #
</pre
></blockquote
></p
>
2777 <p
>The next step is mounting the file system to make the storage available.
2779 <p
><blockquote
><pre
>
2780 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2781 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2782 Using
4 upload threads.
2783 Downloading and decompressing metadata...
2793 Mounting filesystem...
2795 Filesystem Size Used Avail Use% Mounted on
2796 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
2798 </pre
></blockquote
></p
>
2800 <p
>The file system is now ready for use. I use rsync to store my
2801 backups in it, and as the metadata used by rsync is downloaded at
2802 mount time, no network traffic (and storage cost) is triggered by
2803 running rsync. To unmount, one should not use the normal umount
2804 command, as this will not flush the cache to the cloud storage, but
2805 instead running the umount.s3ql command like this:
2807 <p
><blockquote
><pre
>
2810 </pre
></blockquote
></p
>
2812 <p
>There is a fsck command available to check the file system and
2813 correct any problems detected. This can be used if the local server
2814 crashes while the file system is mounted, to reset the
"already
2815 mounted
" flag. This is what it look like when processing a working
2816 file system:
</p
>
2818 <p
><blockquote
><pre
>
2819 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
2820 Using cached metadata.
2821 File system seems clean, checking anyway.
2822 Checking DB integrity...
2823 Creating temporary extra indices...
2824 Checking lost+found...
2825 Checking cached objects...
2826 Checking names (refcounts)...
2827 Checking contents (names)...
2828 Checking contents (inodes)...
2829 Checking contents (parent inodes)...
2830 Checking objects (reference counts)...
2831 Checking objects (backend)...
2832 ..processed
5000 objects so far..
2833 ..processed
10000 objects so far..
2834 ..processed
15000 objects so far..
2835 Checking objects (sizes)...
2836 Checking blocks (referenced objects)...
2837 Checking blocks (refcounts)...
2838 Checking inode-block mapping (blocks)...
2839 Checking inode-block mapping (inodes)...
2840 Checking inodes (refcounts)...
2841 Checking inodes (sizes)...
2842 Checking extended attributes (names)...
2843 Checking extended attributes (inodes)...
2844 Checking symlinks (inodes)...
2845 Checking directory reachability...
2846 Checking unix conventions...
2847 Checking referential integrity...
2848 Dropping temporary indices...
2849 Backing up old metadata...
2859 Compressing and uploading metadata...
2860 Wrote
0.89 MB of compressed metadata.
2862 </pre
></blockquote
></p
>
2864 <p
>Thanks to the cache, working on files that fit in the cache is very
2865 quick, about the same speed as local file access. Uploading large
2866 amount of data is to me limited by the bandwidth out of and into my
2867 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
2868 which is very close to my upload speed, and downloading the same
2869 Debian installation ISO gave me
610 kiB/s, close to my download speed.
2870 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
2871 network, not the file system code. I do not know what a good cache
2872 size would be, but suspect that the cache should e larger than your
2873 working set.
</p
>
2875 <p
>I mentioned that only one machine can mount the file system at the
2876 time. If another machine try, it is told that the file system is
2879 <p
><blockquote
><pre
>
2880 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2881 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2882 Using
8 upload threads.
2883 Backend reports that fs is still mounted elsewhere, aborting.
2885 </pre
></blockquote
></p
>
2887 <p
>The file content is uploaded when the cache is full, while the
2888 metadata is uploaded once every
24 hour by default. To ensure the
2889 file system content is flushed to the cloud, one can either umount the
2890 file system, or ask S3QL to flush the cache and metadata using
2893 <p
><blockquote
><pre
>
2894 # s3qlctrl upload-meta /s3ql
2895 # s3qlctrl flushcache /s3ql
2897 </pre
></blockquote
></p
>
2899 <p
>If you are curious about how much space your data uses in the
2900 cloud, and how much compression and deduplication cut down on the
2901 storage usage, you can use s3qlstat on the mounted file system to get
2904 <p
><blockquote
><pre
>
2906 Directory entries:
9141
2909 Total data size:
22049.38 MB
2910 After de-duplication:
21955.46 MB (
99.57% of total)
2911 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
2912 Database size:
2.39 MB (uncompressed)
2913 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2915 </pre
></blockquote
></p
>
2917 <p
>I mentioned earlier that there are several possible suppliers of
2918 storage. I did not try to locate them all, but am aware of at least
2919 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
2920 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
2921 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
2922 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
2923 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
2924 accept payment in Bitcoin. Pick one that suit your need. Some of
2925 them provide several GiB of free storage, but the prize models are
2926 quite different and you will have to figure out what suits you
2929 <p
>While researching this blog post, I had a look at research papers
2930 and posters discussing the S3QL file system. There are several, which
2931 told me that the file system is getting a critical check by the
2932 science community and increased my confidence in using it. One nice
2934 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
2935 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2936 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
2937 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2938 and Pamela Smith. Please have a look.
</p
>
2940 <p
>Given my problems with different file systems earlier, I decided to
2941 check out the mounted S3QL file system to see if it would be usable as
2942 a home directory (in other word, that it provided POSIX semantics when
2943 it come to locking and umask handling etc). Running
2944 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
2945 test code to check file system semantics
</a
>, I was happy to discover that
2946 no error was found. So the file system can be used for home
2947 directories, if one chooses to do so.
</p
>
2949 <p
>If you do not want a locally file system, and want something that
2950 work without the Linux fuse file system, I would like to mention the
2951 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
2952 provide locally encrypted backup using a command line client. It have
2953 a nicer access control system, where one can split out read and write
2954 access, allowing some systems to write to the backup and others to
2955 only read from it.
</p
>
2957 <p
>As usual, if you use Bitcoin and want to show your support of my
2958 activities, please send Bitcoin donations to my address
2959 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2964 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
2965 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
2966 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
2967 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
2968 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
2969 project
</a
> is working on providing the software and hardware for
2970 making it easy for non-technical people to host their data and
2971 communication at home, and being able to communicate with their
2972 friends and family encrypted and away from prying eyes. It has been
2973 going on for a while, and is slowly progressing towards a new test
2974 release (
0.2).
</p
>
2976 <p
>And what day could be better than the Pi day to announce that the
2977 new version will provide
"hard drive
" / SD card / USB stick images for
2978 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2979 system), and can also be installed using a Debian installer preseed
2980 file. The Debian based Freedombox is now based on Debian Jessie,
2981 where most of the needed packages used are already present. Only one,
2982 the freedombox-setup package, is missing. To try to build your own
2983 boot image to test the current status, fetch the freedom-maker scripts
2985 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
2986 with a user with sudo access to become root:
2989 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2991 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2992 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2994 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2997 <p
>Root access is needed to run debootstrap and mount loopback
2998 devices. See the README for more details on the build. If you do not
2999 want all three images, trim the make line. But note that thanks to
<a
3000 href=
"https://bugs.debian.org/
741407">a race condition in
3001 vmdebootstrap
</a
>, the build might fail without the patch to the
3002 kpartx call.
</p
>
3004 <p
>If you instead want to install using a Debian CD and the preseed
3005 method, boot a Debian Wheezy ISO and use this boot argument to load
3006 the preseed values:
</p
>
3009 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3012 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
3013 recently introduced bug in apt in Jessie
</a
>, the installer will
3014 currently hang while setting up APT sources. Killing the
3015 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
3016 installation will get the installation going. This affect all
3017 installations in Jessie, and I expect it will be fixed soon.
</p
>
3019 <p
>Give it a go and let us know how it goes on the mailing list, and help
3020 us get the new release published. :) Please join us on
3021 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3022 irc.debian.org)
</a
> and
3023 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3024 mailing list
</a
> if you want to help make this vision come true.
</p
>
3029 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
3030 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
3031 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
3032 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
3033 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
3034 innetgr tools, because I needed them in
3035 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
3036 ng-utils, and it has served me well. I placed the project under the
3037 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
3038 repository. But many years ago, the CVS repository was dropped (lost,
3039 not migrated to new hardware, not sure), and the project have lacked a
3040 proper home since then.
</p
>
3042 <p
>Last summer, I had a look at the package and made a new release
3043 fixing a irritating crash bug, but was unable to store the changes in
3044 a proper source control system. I applied for a project on
3045 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
3046 to follow up on it. Until today. :)
</p
>
3048 <p
>After many hours of cleaning and migration, the ng-utils project
3049 now have a new home, and a git repository with the highlight of the
3050 history of the project. I published all release tarballs and imported
3051 them into the git repository. As the project is really stable and not
3052 expected to gain new features any time soon, I decided to make a new
3053 release and call it
1.0. Visit the new project home on
3054 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
3055 if you want to check it out. The new version is also uploaded into
3056 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
3061 <title>Testing sysvinit from experimental in Debian Hurd
</title>
3062 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
3063 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
3064 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
3065 <description><p
>A few days ago I decided to try to help the Hurd people to get
3066 their changes into sysvinit, to allow them to use the normal sysvinit
3067 boot system instead of their old one. This follow up on the
3068 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
3069 Google Summer of Code work
</a
> done last summer by Justus Winter to
3070 get Debian on Hurd working more like Debian on Linux. To get started,
3071 I downloaded a prebuilt hard disk image from
3072 <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
>,
3073 and started it using virt-manager.
</p
>
3075 <p
>The first think I had to do after logging in (root without any
3076 password) was to get the network operational. I followed
3077 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
3078 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
3079 commands as root to get the machine to accept a IP address from the
3080 kvm internal DHCP server:
</p
>
3082 <p
><blockquote
><pre
>
3083 settrans -fgap /dev/netdde /hurd/netdde
3084 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
3085 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
3087 </pre
></blockquote
></p
>
3089 <p
>After this, the machine had internet connectivity, and I could
3090 upgrade it and install the sysvinit packages from experimental and
3091 enable it as the default boot system in Hurd.
</p
>
3093 <p
>But before I did that, I set a password on the root user, as ssh is
3094 running on the machine it for ssh login to work a password need to be
3095 set. Also, note that a bug somewhere in openssh on Hurd block
3096 compression from working. Remember to turn that off on the client
3099 <p
>Run these commands as root to upgrade and test the new sysvinit
3102 <p
><blockquote
><pre
>
3103 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
3104 deb http://http.debian.net/debian/ experimental main
3107 apt-get dist-upgrade
3108 apt-get install -t experimental initscripts sysv-rc sysvinit \
3109 sysvinit-core sysvinit-utils
3110 update-alternatives --config runsystem
3111 </pre
></blockquote
></p
>
3113 <p
>To reboot after switching boot system, you have to use
3114 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
3115 yet a sysvinit process able to receive the signals from the normal
3116 'reboot
' command. After switching to sysvinit as the boot system,
3117 upgrading every package and rebooting, the network come up with DHCP
3118 after boot as it should, and the settrans/pkill hack mentioned at the
3119 start is no longer needed. But for some strange reason, there are no
3120 longer any login prompt in the virtual console, so I logged in using
3123 <p
>Note that there are some race conditions in Hurd making the boot
3124 fail some times. No idea what the cause is, but hope the Hurd porters
3125 figure it out. At least Justus said on IRC (#debian-hurd on
3126 irc.debian.org) that they are aware of the problem. A way to reduce
3127 the impact is to upgrade to the Hurd packages built by Justus by
3128 adding this repository to the machine:
</p
>
3130 <p
><blockquote
><pre
>
3131 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
3132 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3134 </pre
></blockquote
></p
>
3136 <p
>At the moment the prebuilt virtual machine get some packages from
3137 http://ftp.debian-ports.org/debian, because some of the packages in
3138 unstable do not yet include the required patches that are lingering in
3139 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
3141 <p
><blockquote
><pre
>
3142 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
3143 i emacs - GNU Emacs editor (metapackage)
3144 i gdb - GNU Debugger
3145 i hurd-recommended - Miscellaneous translators
3146 i isc-dhcp-client - ISC DHCP client
3147 i isc-dhcp-common - common files used by all the isc-dhcp* packages
3148 i libc-bin - Embedded GNU C Library: Binaries
3149 i libc-dev-bin - Embedded GNU C Library: Development binaries
3150 i libc0.3 - Embedded GNU C Library: Shared libraries
3151 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
3152 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
3153 i multiarch-support - Transitional package to ensure multiarch compatibilit
3154 i A x11-common - X Window System (X.Org) infrastructure
3155 i xorg - X.Org X Window System
3156 i A xserver-xorg - X.Org X server
3157 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
3159 </pre
></blockquote
></p
>
3161 <p
>All in all, testing hurd has been an interesting experience. :)
3162 X.org did not work out of the box and I never took the time to follow
3163 the porters instructions to fix it. This time I was interested in the
3164 command line stuff.
<p
>
3169 <title>New chrpath release
0.16</title>
3170 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
3171 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
3172 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
3173 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
3174 find problems in C, C++ and Java code using static source code
3175 analysis. It can detect a lot of different problems, and is very
3176 useful to find memory and locking bugs in the error handling part of
3177 the source. The company behind it provide
3178 <a href=
"https://scan.coverity.com/
">check of free software projects as
3179 a community service
</a
>, and many hundred free software projects are
3180 already checked. A few days ago I decided to have a closer look at
3181 the Coverity system, and discovered that the
3182 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
3183 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
3184 projects I am involved with was already registered. But these are
3185 fairly big, and I would also like to have a small and easy project to
3186 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
3187 checking of the chrpath project
</a
>. It was
3188 added to the checker and discovered seven potential defects. Six of
3189 these were real, mostly resource
"leak
" when the program detected an
3190 error. Nothing serious, as the resources would be released a fraction
3191 of a second later when the program exited because of the error, but it
3192 is nice to do it right in case the source of the program some time in
3193 the future end up in a library. Having fixed all defects and added
3194 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
3195 mailing list for the chrpath developers
</a
>, I decided it was time to
3196 publish a new release. These are the release notes:
</p
>
3198 <p
>New in
0.16 released
2014-
01-
14:
</p
>
3202 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
3203 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
3204 <li
>Mention new project mailing list in the documentation.
</li
>
3209 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3210 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
3211 project if something is wrong with the new release. The test suite
3212 did not discover any old errors, so if you find a new one, please also
3213 include a test suite check.
</p
>
3218 <title>New chrpath release
0.15</title>
3219 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
3220 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
3221 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
3222 <description><p
>After many years break from the package and a vain hope that
3223 development would be continued by someone else, I finally pulled my
3224 acts together this morning and wrapped up a new release of chrpath,
3225 the command line tool to modify the rpath and runpath of already
3226 compiled ELF programs. The update was triggered by the persistence of
3227 Isha Vishnoi at IBM, which needed a new config.guess file to get
3228 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
3229 is working on. I checked the
3230 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
3231 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
3232 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
3233 packages for interesting patches (failed to find the source from
3234 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
3235 These are the release notes:
</p
>
3237 <p
>New in
0.15 released
2013-
11-
24:
</p
>
3241 <li
>Updated config.sub and config.guess from the GNU project to work
3242 with newer architectures. Thanks to isha vishnoi for the heads
3245 <li
>Updated README with current URLs.
</li
>
3247 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
3248 Matthias Klose.
</li
>
3250 <li
>Added missing help for -k|--keepgoing option, using patch by
3251 Petr Machata found in Fedora.
</li
>
3253 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
3254 .dynamic is a NULL terminated string. Based on patch found in
3255 Fedora credited Axel Thimm and Christian Krause.
</li
>
3260 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3261 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
3262 project if something is wrong with the new release. The test suite
3263 did not discover any old errors, so if you find a new one, please also
3264 include a testsuite check.
</p
>
3269 <title>Debian init.d boot script example for rsyslog
</title>
3270 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
3271 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
3272 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
3273 <description><p
>If one of the points of switching to a new init system in Debian is
3274 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
3275 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
3276 init.d scripts at all. Here is an example init.d script, ie a rewrite
3277 of /etc/init.d/rsyslog:
</p
>
3279 <p
><pre
>
3280 #!/lib/init/init-d-script
3283 # Required-Start: $remote_fs $time
3284 # Required-Stop: umountnfs $time
3285 # X-Stop-After: sendsigs
3286 # Default-Start:
2 3 4 5
3287 # Default-Stop:
0 1 6
3288 # Short-Description: enhanced syslogd
3289 # Description: Rsyslog is an enhanced multi-threaded syslogd.
3290 # It is quite compatible to stock sysklogd and can be
3291 # used as a drop-in replacement.
3293 DESC=
"enhanced syslogd
"
3294 DAEMON=/usr/sbin/rsyslogd
3295 </pre
></p
>
3297 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
3298 script was
137 lines, and the above is just
15 lines, most of it meta
3299 info/comments.
</p
>
3301 <p
>How to do this, you ask? Well, one create a new script
3302 /lib/init/init-d-script looking something like this:
3304 <p
><pre
>
3307 # Define LSB log_* functions.
3308 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
3309 # and status_of_proc is working.
3310 . /lib/lsb/init-functions
3313 # Function that starts the daemon/service
3319 #
0 if daemon has been started
3320 #
1 if daemon was already running
3321 #
2 if daemon could not be started
3322 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
3324 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
3327 # Add code here, if necessary, that waits for the process to be ready
3328 # to handle requests from services started subsequently which depend
3329 # on this one. As a last resort, sleep for some time.
3333 # Function that stops the daemon/service
3338 #
0 if daemon has been stopped
3339 #
1 if daemon was already stopped
3340 #
2 if daemon could not be stopped
3341 # other if a failure occurred
3342 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
3343 RETVAL=
"$?
"
3344 [
"$RETVAL
" =
2 ]
&& return
2
3345 # Wait for children to finish too if this is a daemon that forks
3346 # and if the daemon is only ever run from this initscript.
3347 # If the above conditions are not satisfied then add some other code
3348 # that waits for the process to drop all resources that could be
3349 # needed by services started subsequently. A last resort is to
3350 # sleep for some time.
3351 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
3352 [
"$?
" =
2 ]
&& return
2
3353 # Many daemons don
't delete their pidfiles when they exit.
3355 return
"$RETVAL
"
3359 # Function that sends a SIGHUP to the daemon/service
3363 # If the daemon can reload its configuration without
3364 # restarting (for example, when it is sent a SIGHUP),
3365 # then implement that here.
3367 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
3372 scriptbasename=
"$(basename $
1)
"
3373 echo
"SN: $scriptbasename
"
3374 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
3375 script=
"$
1"
3382 NAME=$(basename $DAEMON)
3383 PIDFILE=/var/run/$NAME.pid
3385 # Exit if the package is not installed
3386 #[ -x
"$DAEMON
" ] || exit
0
3388 # Read configuration variable file if it is present
3389 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
3391 # Load the VERBOSE setting and other rcS variables
3394 case
"$
1" in
3396 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
3398 case
"$?
" in
3399 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3400 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3404 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
3406 case
"$?
" in
3407 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3408 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3412 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
3414 #reload|force-reload)
3416 # If do_reload() is not implemented then leave this commented out
3417 # and leave
'force-reload
' as an alias for
'restart
'.
3419 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
3423 restart|force-reload)
3425 # If the
"reload
" option is implemented then remove the
3426 #
'force-reload
' alias
3428 log_daemon_msg
"Restarting $DESC
" "$NAME
"
3430 case
"$?
" in
3433 case
"$?
" in
3435 1) log_end_msg
1 ;; # Old process is still running
3436 *) log_end_msg
1 ;; # Failed to start
3446 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
3452 </pre
></p
>
3454 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
3455 lot. I did not really polish the approach, so it might not always
3456 work out of the box, but you get the idea. I did not try very hard to
3457 optimize it nor make it more robust either.
</p
>
3459 <p
>A better argument for switching init system in Debian than reducing
3460 the size of init scripts (which is a good thing to do anyway), is to
3461 get boot system that is able to handle the kernel events sensibly and
3462 robustly, and do not depend on the boot to run sequentially. The boot
3463 and the kernel have not behaved sequentially in years.
</p
>
3468 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
3469 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
3470 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
3471 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
3472 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
3473 remote display access is the preferred solution with oVirt and RedHat
3474 Enterprise Virtualization, and I was sad to discover the other day
3475 that the browser plugin needed to use these systems seamlessly was
3476 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
3477 for a package
</a
> was from
2012-
04-
10 with no progress since
3478 2013-
04-
01, so I decided to wrap up a package based on the great work
3479 from Cajus Pollmeier and put it in a collab-maint maintained git
3480 repository to get a package I could use. I would very much like
3481 others to help me maintain the package (or just take over, I do not
3482 mind), but as no-one had volunteered so far, I just uploaded it to
3483 NEW. I hope it will be available in Debian in a few days.
</p
>
3485 <p
>The source is now available from
3486 <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
>
3491 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
3492 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
3493 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
3494 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
3495 <description><p
>The
3496 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
3497 program is a a very nice system to create virtual machine images. It
3498 create a image file, add a partition table, mount it and run
3499 debootstrap in the mounted directory to create a Debian system on a
3500 stick. Yesterday, I decided to try to teach it how to make images for
3501 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
3502 of a plan to simplify the build system for
3503 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
3504 project
</a
>. The FreedomBox project already uses vmdebootstrap for
3505 the virtualbox images, but its current build system made multistrap
3506 based system for Dreamplug images, and it is lacking support for
3507 Raspberry Pi.
</p
>
3509 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
3510 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
3511 code and adjusted it to be able to build armel images on my amd64
3512 Debian laptop. I ended up giving vmdebootstrap five new options,
3513 allowing me to replicate the image creation process I use to make
3514 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
3515 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
3516 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
3517 call debootstrap with --foreign and to copy the handler into the
3518 generated chroot before running the second stage. This allow
3519 vmdebootstrap to create armel images on an amd64 host. Next I added
3520 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
3521 fstype
</tt
> to teach it to create a separate /boot/ partition with the
3522 given file system type, allowing me to create an image with a vfat
3523 partition for the /boot/ stuff. I also added a
<tt
>--variant
3524 variant
</tt
> option to allow me to create smaller images without the
3525 Debian base system packages installed. Finally, I added an option
3526 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
3527 as a boot loader. It is not needed on the Raspberry Pi and probably
3528 most other non-x86 architectures. The changes were accepted by the
3529 upstream author of vmdebootstrap yesterday and today, and is now
3531 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
3532 upstream project page
</a
>.
</p
>
3534 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
3535 create a small script (the customize script) to add the non-free
3536 binary blob needed to boot the Raspberry Pi and the APT source
3539 <p
><pre
>
3541 set -e # Exit on first error
3542 rootdir=
"$
1"
3543 cd
"$rootdir
"
3544 cat
&lt;
&lt;EOF
> etc/apt/sources.list
3545 deb http://http.debian.net/debian/ jessie main contrib non-free
3547 # Install non-free binary blob needed to boot Raspberry Pi. This
3548 # install a kernel somewhere too.
3549 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
3550 -O $rootdir/usr/bin/rpi-update
3551 chmod a+x $rootdir/usr/bin/rpi-update
3552 mkdir -p $rootdir/lib/modules
3553 touch $rootdir/boot/start.elf
3554 chroot $rootdir rpi-update
3555 </pre
></p
>
3557 <p
>Next, fetch the latest vmdebootstrap script and call it like this
3558 to build the image:
</p
>
3561 sudo ./vmdebootstrap \
3564 --distribution jessie \
3565 --mirror http://http.debian.net/debian \
3574 --root-password raspberry \
3575 --hostname raspberrypi \
3576 --foreign /usr/bin/qemu-arm-static \
3577 --customize `pwd`/customize \
3579 --package git-core \
3580 --package binutils \
3581 --package ca-certificates \
3584 </pre
></p
>
3586 <p
>The list of packages being installed are the ones needed by
3587 rpi-update to make the image bootable on the Raspberry Pi, with the
3588 exception of netbase, which is needed by debootstrap to find
3589 /etc/hosts with the minbase variant. I really wish there was a way to
3590 set up an Raspberry Pi using only packages in the Debian archive, but
3591 that is not possible as far as I know, because it boots from the GPU
3592 using a non-free binary blob.
</p
>
3594 <p
>The build host need debootstrap, kpartx and qemu-user-static and
3595 probably a few others installed. I have not checked the complete
3596 build dependency list.
</p
>
3598 <p
>The resulting image will not use the hardware floating point unit
3599 on the Raspberry PI, because the armel architecture in Debian is not
3600 optimized for that use. So the images created will be a bit slower
3601 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
3606 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
3607 <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>
3608 <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>
3609 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
3610 <description><p
>The last few days I came across a few good causes that should get
3611 wider attention. I recommend signing and donating to each one of
3614 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
3615 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
3616 Women program which is a Google Summer of Code like initiative to get
3617 more women involved in free software. One debian sponsor has offered
3618 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
3619 earmarked
</a
> for this initiative. I donated a few minutes ago, and
3620 hope you will to. :)
</p
>
3622 <p
>And the Electronic Frontier Foundation just announced plans to
3623 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
3624 documentaries about the excessive spying
</a
> on every Internet user that
3625 take place these days, and their need to fund the work. I
've already
3626 donated. Are you next?
</p
>
3628 <p
>For my Norwegian audience, the organisation Studentenes og
3629 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
3630 statement under the heading
3631 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
3632 Access
</a
> for those of us asking for more focus on open access in the
3633 Norwegian government. So far
499 signatures. I hope you will sign it
3639 <title>Videos about the Freedombox project - for inspiration and learning
</title>
3640 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
3641 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
3642 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
3643 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
3644 project
</a
> have been going on for a while, and have presented the
3645 vision, ideas and solution several places. Here is a little
3646 collection of videos of talks and presentation of the project.
</p
>
3650 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
3651 2,
5 minute marketing film
</a
> (Youtube)
</li
>
3653 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
3654 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
3656 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
3657 Freedom in the Cloud - Software Freedom, Privacy and and Security for
3658 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
3659 (Youtube)
</li
>
3661 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
3662 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
3664 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
3665 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
3667 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
3668 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
3669 York City in
2012</a
> (Youtube)
</li
>
3671 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
3672 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
3673 (Youtube)
</li
>
3675 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
3676 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
3678 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
3679 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
3681 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
3682 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
3683 2013</a
> (Youtube)
</li
>
3687 <p
>A larger list is available from
3688 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
3689 Freedombox Wiki
</a
>.
</p
>
3691 <p
>On other news, I am happy to report that Freedombox based on Debian
3692 Jessie is coming along quite well, and soon both Owncloud and using
3693 Tor should be available for testers of the Freedombox solution. :) In
3694 a few weeks I hope everything needed to test it is included in Debian.
3695 The withsqlite package is already in Debian, and the plinth package is
3696 pending in NEW. The third and vital part of that puzzle is the
3697 metapackage/setup framework, which is still pending an upload. Join
3698 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
3699 (#freedombox on irc.debian.org)
</a
> and
3700 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3701 mailing list
</a
> if you want to help make this vision come true.
</p
>
3706 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
3707 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
3708 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
3709 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
3710 <description><p
>I was introduced to the
3711 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
3712 in
2010, when Eben Moglen presented his vision about serving the need
3713 of non-technical people to keep their personal information private and
3714 within the legal protection of their own homes. The idea is to give
3715 people back the power over their network and machines, and return
3716 Internet back to its intended peer-to-peer architecture. Instead of
3717 depending on a central service, the Freedombox will give everyone
3718 control over their own basic infrastructure.
</p
>
3720 <p
>I
've intended to join the effort since then, but other tasks have
3721 taken priority. But this summers nasty news about the misuse of trust
3722 and privilege exercised by the
"western
" intelligence gathering
3723 communities increased my eagerness to contribute to a point where I
3724 actually started working on the project a while back.
</p
>
3726 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
3727 Debian initiative
</a
> based on the vision from Eben Moglen, is to
3728 create a simple and cheap Debian based appliance that anyone can hook
3729 up in their home and get access to secure and private services and
3730 communication. The initial deployment platform have been the
3731 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
3732 which is a piece of hardware I do not own. So to be able to test what
3733 the current Freedombox setup look like, I had to come up with a way to install
3734 it on some hardware I do have access to. I have rewritten the
3735 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
3736 image build framework to use .deb packages instead of only copying
3737 setup into the boot images, and thanks to this rewrite I am able to
3738 set up any machine supported by Debian Wheezy as a Freedombox, using
3739 the previously mentioned deb (and a few support debs for packages
3740 missing in Debian).
</p
>
3742 <p
>The current Freedombox setup consist of a set of bootstrapping
3744 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
3745 and a administrative web interface
3746 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
3747 withsqlite), as well as a privacy enhancing proxy based on
3748 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
3749 (freedombox-privoxy). There is also a web/javascript based XMPP
3750 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
3751 trying (unsuccessfully so far) to talk to the XMPP server
3752 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
3753 web interface is pluggable, and the goal is to use it to enable OpenID
3754 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3755 this is really working yet, see
3756 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
3757 project TODO
</a
> for links to GIT repositories. Most of the code is
3758 on github at the moment. The HTTP proxy is operational out of the
3759 box, and the admin web interface can be used to add/remove plinth
3760 users. I
've not been able to do anything else with it so far, but
3761 know there are several branches spread around github and other places
3762 with lots of half baked features.
</p
>
3764 <p
>Anyway, if you want to have a look at the current state, the
3765 following recipes should work to give you a test machine to poke
3768 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
3772 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
3773 <li
>Boot from it, either as CD or USB stick.
</li
>
3774 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
3775 to the Debian installer:
<p
>
3776 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
3778 <li
>Answer the few language/region/password questions and pick disk to
3779 install on.
</li
>
3781 <li
>When the installation is finished and the machine have rebooted a
3782 few times, your Freedombox is ready for testing.
</li
>
3786 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
3790 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
3791 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
3792 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
3794 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
3795 </pre
></li
>
3796 <li
><p
>Run this as root:
</p
>
3798 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3801 apt-get install freedombox-setup
3802 /usr/lib/freedombox/setup
3803 </pre
></li
>
3804 <li
>Reboot into your freshly created Freedombox.
</li
>
3808 <p
>You can test it on other architectures too, but because the
3809 freedombox-privoxy package is binary, it will only work as intended on
3810 the architectures where I have had time to build the binary and put it
3811 in my APT repository. But do not let this stop you. It is only a
3812 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
3814 <p
>Note that by default Freedombox is a DHCP server on the
3815 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
3816 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
3817 disable
</tt
>" as root.
</p
>
3819 <p
>Please let me know if this works for you, or if you have any
3820 problems. We gather on the IRC channel
3821 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
3822 irc.debian.org and the
3823 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
3824 mailing list
</a
>.
</p
>
3826 <p
>Once you get your freedombox operational, you can visit
3827 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
3828 welcome screen (dead end - do not be surprised if you are unable to
3829 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
3830 to look at the rest of plinth. The default user is
'admin
' and the
3831 default password is
'secret
'.
</p
>
3836 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
3837 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
3838 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
3839 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
3840 <description><p
>Earlier, I reported about
3841 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
3842 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
3843 told by IBM that the original disk should be thrown away. And as
3844 there no longer was a problem if I bricked the firmware, I decided
3845 today to try to install Intel firmware to replace the Lenovo firmware
3846 currently on the disk.
</p
>
3848 <p
>I searched the Intel site for firmware, and found
3849 <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
>
3850 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3851 according to the site should contain the latest firmware for SSD
3852 disks. I inserted the broken disk in one of my spare laptops and
3853 booted the ISO from a USB stick. The disk was recognized, but the
3854 program claimed the newest firmware already were installed and refused
3855 to insert any Intel firmware. So no change, and the disk is still
3856 unable to handle write load. :( I guess the only way to get them
3857 working would be if Lenovo releases new firmware. No idea how likely
3858 that is. Anyway, just blogging about this test for completeness. I
3859 got a working Samsung disk, and see no point in spending more time on
3860 the broken disks.
</p
>
3865 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
3866 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
3867 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
3868 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
3869 <description><p
>Today I switched to
3870 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
3871 new laptop
</a
>. I
've previously written about the problems I had with
3872 my new Thinkpad X230, which was delivered with an
3873 <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
3874 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
3875 sustained writes. My hardware supplier have been very forthcoming in
3876 trying to find a solution, and after first trying with another
3877 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
3878 disk instead to fix it once and for all. The Samsung disk survived
3879 the installation of Debian with encrypted disks (filling the disk with
3880 random data during installation killed the first two), and I thus
3881 decided to trust it with my data. I have installed it as a Debian Edu
3882 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3883 server at home using Kerberos and LDAP, and will use it as my work
3884 station from now on.
</p
>
3886 <p
>As this is a solid state disk with no moving parts, I believe the
3887 Debian Wheezy default installation need to be tuned a bit to increase
3888 performance and increase life time of the disk. The Linux kernel and
3889 user space applications do not yet adjust automatically to such
3890 environment. To make it easier for my self, I created a draft Debian
3891 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
3892 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
3893 for the ssd-setup package
</a
> is available from collab-maint, and it
3894 is set up to adjust the setup of the machine by just installing the
3895 package. If there is any non-SSD disk in the machine, the package
3896 will refuse to install, as I did not try to write any logic to sort
3897 file systems in SSD and non-SSD file systems.
</p
>
3899 <p
>I consider the package a draft, as I am a bit unsure how to best
3900 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3901 where I set up the machine with one large encrypted partition (in
3902 addition to /boot), put LVM on top of this and set up partitions on
3903 top of this again. See the README file in the package source for the
3904 references I used to pick the settings. At the moment these
3905 parameters are tuned:
</p
>
3909 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
3910 (adding discard to /etc/crypttab)
</li
>
3912 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
3913 this case a cryptsetup partition) by changing issue_discards from
3914 0 to
1 in /etc/lvm/lvm.conf.
</li
>
3916 <li
>Set relatime as a file system option for ext3 and ext4 file
3919 <li
>Tell swap to use TRIM commands by adding
'discard
' to
3920 /etc/fstab.
</li
>
3922 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
3924 <li
>Run fstrim on every ext3 and ext4 file system every night (from
3925 cron.daily).
</li
>
3927 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
3928 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
3932 <p
>During installation, I cancelled the part where the installer fill
3933 the disk with random data, as this would kill the SSD performance for
3934 little gain. My goal with the encrypted file system is to ensure
3935 those stealing my laptop end up with a brick and not a working
3936 computer. I have no hope in keeping the really resourceful people
3937 from getting the data on the disk (see
3938 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
3939 Thus I concluded that adding the discard option to crypttab is the
3940 right thing to do.
</p
>
3942 <p
>I considered using the noop I/O scheduler, as several recommended
3943 it for SSD, but others recommended deadline and a benchmark I found
3944 indicated that deadline might be better for interactive use.
</p
>
3946 <p
>I also considered using the
'discard
' file system option for ext3
3947 and ext4, but read that it would give a performance hit ever time a
3948 file is removed, and thought it best to that that slowdown once a day
3949 instead of during my work.
</p
>
3951 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3952 this is already done by Debian Edu.
</p
>
3954 <p
>I have not yet started on the user space tuning. I expect
3955 iceweasel need some tuning, and perhaps other applications too, but
3956 have not yet had time to investigate those parts.
</p
>
3958 <p
>The package should work on Ubuntu too, but I have not yet tested it
3961 <p
>As for the answer to the question in the title of this blog post,
3962 as far as I know, the only solution I know about is to replace the
3963 disk. It might be possible to flash it with Intel firmware instead of
3964 the Lenovo firmware. But I have not tried and did not want to do so
3965 without approval from Lenovo as I wanted to keep the warranty on the
3966 disk until a solution was found and they wanted the broken disks
3972 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
3973 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
3974 <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>
3975 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
3976 <description><p
>A few days ago, I wrote about
3977 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
3978 problems I experienced with my new X230 and its SSD disk
</a
>, which
3979 was dying during installation because it is unable to cope with
3980 sustained write. My supplier is in contact with
3981 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
3982 replacement disk to try to fix the problem. They decided to send an
3983 identical model, so my hopes for a permanent fix was slim.
</p
>
3985 <p
>Anyway, today I got the replacement disk and tried to install
3986 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3987 same firmware version as the original. This time my hope raised
3988 slightly as the installation progressed, as the original disk used to
3989 die after
4-
7% of the disk was written to, while this time it kept
3990 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
3991 died again and I was back on square one. I still do not have a new
3992 laptop with a disk I can trust. I can not live with a disk that might
3993 lock up when I download a new
3994 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
3995 other large files. I look forward to hearing from my supplier with
3996 the next proposal from Lenovo.
</p
>
3998 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
3999 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
4000 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4001 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
4002 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4003 P/N
45N8295, P0C38732.
</p
>
4005 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
4006 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
4007 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4008 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
4009 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4010 P/N
45N8295, P0C38732.
</p
>
4012 <p
>The only difference is in the first number (serial number?), ISN,
4013 SA, date and WNPP values. Mentioning all the details here in case
4014 someone is able to use the information to find a way to identify the
4015 failing disk among working ones (if any such working disk actually
4021 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
4022 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
4023 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
4024 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
4025 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
4026 Debian Edu developer gathering and Debian and Ubuntu bug squashing
4027 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
4028 member assosiation NUUG
</a
> and
4029 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
4030 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
4031 Bitraf
</a
>.
</p
>
4033 <p
>It starts
10:
00 and continue until late evening. Everyone is
4034 welcome, and there is no fee to participate. There is on the other
4035 hand limited space, and only room for
30 people. Please put your name
4036 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
4037 wiki page
</a
> if you plan to join us.
</p
>
4042 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
4043 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
4044 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
4045 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
4046 <description><p
>Half a year ago, I reported that I had to find a
4047 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
4048 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
4049 time to spend on it, and it took a while to find a model I believe
4050 will do the job, but two days ago the replacement finally arrived. I
4052 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
4053 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
4054 a roaming workstation, and it seemed to work flawlessly. But my
4055 second installation with encrypted disk was not as successful. More
4056 on that below.
</p
>
4058 <p
>I had a hard time trying to track down a good laptop, as my most
4059 important requirements (robust and with a good keyboard) are never
4060 listed in the feature list. But I did get good help from the search
4061 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4062 allowed me to limit the list of interesting laptops based on my other
4063 requirements. A bit surprising that SSD disk are not disks according
4064 to that search interface, so I had to drop specifying the number of
4065 disks from my search parameters. I also asked around among friends to
4066 get their impression on keyboards and robustness.
</p
>
4068 <p
>So the new laptop arrived, and it is quite a lot wider than the
4069 X41. I am not quite convinced about the keyboard, as it is
4070 significantly wider than my old keyboard, and I have to stretch my
4071 hand a lot more to reach the edges. But the key response is fairly
4072 good and the individual key shape is fairly easy to handle, so I hope
4073 I will get used to it. My old X40 was starting to fail, and I really
4074 needed a new laptop now. :)
</p
>
4076 <p
>Turning off the touch pad was simple. All it took was a quick
4077 visit to the BIOS during boot it disable it.
</p
>
4079 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
4080 lock up during load. And this happen when installing Debian Wheezy
4081 with encrypted disk, while the disk is being filled with random data.
4082 I also tested to install Ubuntu Raring, and it happen there too if I
4083 reenable the code to fill the disk with random data (it is disabled by
4084 default in Ubuntu). And the bug with is already known. It was
4085 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
4086 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
4087 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4088 kernel developers as
4089 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
4090 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
4091 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4092 Lenovo forums, both for
4093 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
4094 2012-
11-
10</a
> and for
4095 <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
4096 03-
20-
2013</a
>. The problem do not only affect installation. The
4097 reports state that the disk lock up during use if many writes are done
4098 on the disk, so it is much no use to work around the installation
4099 problem and end up with a computer that can lock up at any moment.
4101 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
4102 available
</a
> that will lock up the hard drive after running a few
4103 minutes by writing to a file.
</p
>
4105 <p
>I
've contacted my supplier and asked how to handle this, and after
4106 contacting PCHELP Norway (request
01D1FDP) which handle support
4107 requests for Lenovo, his first suggestion was to upgrade the disk
4108 firmware. Unfortunately there is no newer firmware available from
4109 Lenovo, as my disk already have the most recent one (version LF1i). I
4110 hope to hear more from him today and hope the problem can be
4116 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
4117 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
4118 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
4119 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
4120 <description><p
>Half a year ago, I reported that I had to find a replacement for my
4121 trusty old Thinkpad X41. Unfortunately I did not have much time to
4122 spend on it, but today the replacement finally arrived. I ended up
4123 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
4124 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
4125 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4126 this, it is installing what I hope will be a more final installation,
4127 with a encrypted hard drive to ensure any dope head stealing it end up
4128 with an expencive door stop.
</p
>
4130 <p
>I had a hard time trying to track down a good laptop, as my most
4131 important requirements (robust and with a good keyboard) are never
4132 listed in the feature list. But I did get good help from the search
4133 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4134 allowed me to limit the list of interesting laptops based on my other
4135 requirements. A bit surprising that SSD disk are not disks, so I had
4136 to drop number of disks from my search parameters.
</p
>
4138 <p
>I am not quite convinced about the keyboard, as it is significantly
4139 wider than my old keyboard, and I have to stretch my hand a lot more
4140 to reach the edges. But the key response is fairly good and the
4141 individual key shape is fairly easy to handle, so I hope I will get
4142 used to it. My old X40 was starting to fail, and I really needed a
4143 new laptop now. :)
</p
>
4145 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
4150 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
4151 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
4152 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
4153 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
4154 <description><p
>It annoys me when the computer fail to do automatically what it is
4155 perfectly capable of, and I have to do it manually to get things
4156 working. One such task is to find out what firmware packages are
4157 needed to get the hardware on my computer working. Most often this
4158 affect the wifi card, but some times it even affect the RAID
4159 controller or the ethernet card. Today I pushed version
0.4 of the
4160 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
4161 including a new script isenkram-autoinstall-firmware handling the
4162 process of asking all the loaded kernel modules what firmware files
4163 they want, find debian packages providing these files and install the
4164 debian packages. Here is a test run on my laptop:
</p
>
4166 <p
><pre
>
4167 # isenkram-autoinstall-firmware
4168 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
4169 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
4170 info: locating packages with the requested firmware files
4171 info: Updating APT sources after adding non-free APT source
4172 info: trying to install firmware-ipw2x00
4175 Preconfiguring packages ...
4176 Selecting previously deselected package firmware-ipw2x00.
4177 (Reading database ...
259727 files and directories currently installed.)
4178 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
4179 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
4181 </pre
></p
>
4183 <p
>When all the requested firmware is present, a simple message is
4184 printed instead:
</p
>
4186 <p
><pre
>
4187 # isenkram-autoinstall-firmware
4188 info: did not find any firmware files requested by loaded kernel modules. exiting
4190 </pre
></p
>
4192 <p
>It could use some polish, but it is already working well and saving
4193 me some time when setting up new machines. :)
</p
>
4195 <p
>So, how does it work? It look at the set of currently loaded
4196 kernel modules, and look up each one of them using modinfo, to find
4197 the firmware files listed in the module meta-information. Next, it
4198 download the Contents file from a nearby APT mirror, and search for
4199 the firmware files in this file to locate the package with the
4200 requested firmware file. If the package is in the non-free section, a
4201 non-free APT source is added and the package is installed using
4202 <tt
>apt-get install
</tt
>. The end result is a slightly better working
4205 <p
>I hope someone find time to implement a more polished version of
4206 this script as part of the hw-detect debian-installer module, to
4207 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
4208 #
655507</a
>. There really is no need to insert USB sticks with
4209 firmware during a PXE install when the packages already are available
4210 from the nearby Debian mirror.
</p
>
4215 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
4216 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
4217 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
4218 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
4219 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
4220 the screen just turn black when Linux boot, either during installation
4221 or on first boot from the hard disk. I
've seen it once in a while the
4222 last few years, but only recently understood the cause. I
've seen it
4223 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
4224 The reason seem to be in the wiring of some laptops. The system to
4225 control the screen background light is inverted, so when Linux try to
4226 turn the brightness fully on, it end up turning it off instead. I do
4227 not know which Linux drivers are affected, but this post is about the
4228 i915 driver used by the
4229 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4230 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
4232 <p
>The problem can be worked around two ways. Either by adding
4233 i915.invert_brightness=
1 as a kernel option, or by adding a file in
4234 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
4235 option when it load the i915 kernel module. On Debian and Ubuntu, it
4236 can be done by running these commands as root:
</p
>
4239 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
4240 update-initramfs -u -k all
4243 <p
>Since March
2012 there is
4244 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
4245 mechanism in the Linux kernel
</a
> to tell the i915 driver which
4246 hardware have this problem, and get the driver to invert the
4247 brightness setting automatically. To use it, one need to add a row in
4248 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
4249 intel_quirks array
</a
> in the driver source
4250 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
4251 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
4252 number (vendor number
8086 is assumed) and subdevice vendor and device
4255 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
4256 -vvnn
</tt
> for the video card in question:
</p
>
4258 <p
><pre
>
4259 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
4260 3rd Gen Core processor Graphics Controller [
8086:
0156] \
4261 (rev
09) (prog-if
00 [VGA controller])
4262 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
4263 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
4264 ParErr- Stepping- SE RR- FastB2B- DisINTx+
4265 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
4266 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
4268 Interrupt: pin A routed to IRQ
42
4269 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
4270 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
4271 Region
4: I/O ports at
4000 [size=
64]
4272 Expansion ROM at
<unassigned
> [disabled]
4273 Capabilities:
<access denied
>
4274 Kernel driver in use: i915
4275 </pre
></p
>
4277 <p
>The resulting intel_quirks entry would then look like this:
</p
>
4279 <p
><pre
>
4280 struct intel_quirk intel_quirks[] = {
4282 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
4283 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
4286 </pre
></p
>
4288 <p
>According to the kernel module instructions (as seen using
4289 <tt
>modinfo i915
</tt
>), information about hardware needing the
4290 invert_brightness flag should be sent to the
4291 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
4292 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
4293 developers. But my email about the laptop sent
2013-
06-
03 have not
4295 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
4296 web archive for the mailing list
</a
>, so I suspect they do not accept
4297 emails from non-subscribers. Because of this, I sent my patch also to
4298 the Debian bug tracking system instead as
4299 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
4300 sure the patch is not lost.
</p
>
4302 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
4303 with this problem working properly with Linux. If you use Gnome, your
4304 worries should be over at this point. But if you use KDE, there is
4305 something in KDE ignoring the invert_brightness setting and turning on
4306 the screen during login. I
've reported it to Debian as
4307 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
4308 have no idea yet how to figure out exactly what subsystem is doing
4309 this. Perhaps you can help? Perhaps you know what the Gnome
4310 developers did to handle this, and this can give a clue to the KDE
4311 developers? Or you know where in KDE the screen brightness is changed
4312 during login? If so, please update the BTS report (or get in touch if
4313 you do not know how to update BTS).
</p
>
4315 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
4316 acpi_backlight=vendor, to disable ACPI backlight support completely,
4317 as the ACPI information on the machine is trash and it is better to
4318 leave it to the intel video driver to control the screen
4319 backlight.
</p
>
4324 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
4325 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
4326 <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>
4327 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
4328 <description><p
>Two days ago, I asked
4329 <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
4330 I could install Linux on a Packard Bell EasyNote LV computer
4331 preinstalled with Windows
8</a
>. I found a solution, but am horrified
4332 with the obstacles put in the way of Linux users on a laptop with UEFI
4333 and Windows
8.
</p
>
4335 <p
>I never found out if the cause of my problems were the use of UEFI
4336 secure booting or fast boot. I suspect fast boot was the problem,
4337 causing the firmware to boot directly from HD without considering any
4338 key presses and alternative devices, but do not know UEFI settings
4339 enough to tell.
</p
>
4341 <p
>There is no way to install Linux on the machine in question without
4342 opening the box and disconnecting the hard drive! This is as far as I
4343 can tell, the only way to get access to the firmware setup menu
4344 without accepting the Windows
8 license agreement. I am told (and
4345 found description on how to) that it is possible to configure the
4346 firmware setup once booted into Windows
8. But as I believe the terms
4347 of that agreement are completely unacceptable, accepting the license
4348 was never an alternative. I do not enter agreements I do not intend
4349 to follow.
</p
>
4351 <p
>I feared I had to return the laptops and ask for a refund, and
4352 waste many hours on this, but luckily there was a way to get it to
4353 work. But I would not recommend it to anyone planning to run Linux on
4354 it, and I have become sceptical to Windows
8 certified laptops. Is
4355 this the way Linux will be forced out of the market place, by making
4356 it close to impossible for
"normal
" users to install Linux without
4357 accepting the Microsoft Windows license terms? Or at least not
4358 without risking to loose the warranty?
</p
>
4360 <p
>I
've updated the
4361 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
4362 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
4363 do not have to struggle as much as I did to get Linux into the
4366 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
4367 Michael Tokarev and others for feedback and ideas.
</p
>
4372 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
4373 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
4374 <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>
4375 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
4376 <description><p
>I
've run into quite a problem the last few days. I bought three
4377 new laptops for my parents and a few others. I bought Packard Bell
4378 Easynote LV to run Kubuntu on and use as their home computer. But I
4379 am completely unable to figure out how to install Linux on it. The
4380 computer is preinstalled with Windows
8, and I suspect it uses UEFI
4381 instead of a BIOS to boot.
</p
>
4383 <p
>The problem is that I am unable to get it to PXE boot, and unable
4384 to get it to boot the Linux installer from my USB stick. I have yet
4385 to try the DVD install, and still hope it will work. when I turn on
4386 the computer, there is no information on what buttons to press to get
4387 the normal boot menu. I expect to get some boot menu to select PXE or
4388 USB stick booting. When booting, it first ask for the language to
4389 use, then for some regional settings, and finally if I will accept the
4390 Windows
8 terms of use. As these terms are completely unacceptable to
4391 me, I have no other choice but to turn off the computer and try again
4392 to get it to boot the Linux installer.
</p
>
4394 <p
>I have gathered my findings so far on a Linlap page about the
4395 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4396 EasyNote LV
</a
> model. If you have any idea how to get Linux
4397 installed on this machine, please get in touch or update that wiki
4398 page. If I can
't find a way to install Linux, I will have to return
4399 the laptop to the seller and find another machine for my parents.
</p
>
4401 <p
>I wonder, is this the way Linux will be forced out of the market
4402 using UEFI and
"secure boot
" by making it impossible to install Linux
4403 on new Laptops?
</p
>
4408 <title>How to transform a Debian based system to a Debian Edu installation
</title>
4409 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
4410 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
4411 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
4412 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
4413 an operating system based on Debian intended for use in schools. It
4414 contain a turn-key solution for the computer network provided to
4415 pupils in the primary schools. It provide both the central server,
4416 network boot servers and desktop environments with heaps of
4417 educational software. The project was founded almost
12 years ago,
4418 2001-
07-
02. If you want to support the project, which is in need for
4419 cash to fund developer gatherings and other project related activity,
4420 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
4421 donate some money
</a
>.
4423 <p
>A topic that come up again and again on the Debian Edu mailing
4424 lists and elsewhere, is the question on how to transform a Debian or
4425 Ubuntu installation into a Debian Edu installation. It isn
't very
4426 hard, and last week I wrote a script to replicate the steps done by
4427 the Debian Edu installer.
</p
>
4429 <p
>The script,
4430 <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/
>
4431 in the debian-edu-config package, will go through these six steps and
4432 transform an existing Debian Wheezy or Ubuntu (untested) installation
4433 into a Debian Edu Workstation:
</p
>
4437 <li
>Add skolelinux related APT sources.
</li
>
4438 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
4439 <li
>Install debian-edu-install to load preseeding values and pull in
4440 our configuration.
</li
>
4441 <li
>Preseed debconf database with profile setup in
4442 /etc/debian-edu/config, and run tasksel to install packages
4443 according to the profile specified in the config above,
4444 overriding some of the Debian automation machinery.
</li
>
4445 <li
>Run debian-edu-cfengine-D installation to configure everything
4446 that could not be done using preseeding.
</li
>
4447 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
4451 <p
>There are some steps in the Debian Edu installation that can not be
4452 replicated like this. Disk partitioning and LVM setup, for example.
4453 So this script just assume there is enough disk space to install all
4454 the needed packages.
</p
>
4456 <p
>The script was created to help a Debian Edu student working on
4457 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
4458 Debian Edu client, and using it he can take the existing
4459 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
4460 transform it into a fully functioning Debian Edu Workstation (or
4461 Roaming Workstation, or whatever :).
</p
>
4463 <p
>The default setting in the script is to create a KDE Workstation.
4464 If a LXDE based Roaming workstation is wanted instead, modify the
4465 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
4467 <p
><pre
>
4468 PROFILE=
"Roaming-Workstation
"
4469 DESKTOP=
"lxde
"
4470 </pre
></p
>
4472 <p
>The script could even become useful to set up Debian Edu servers in
4473 the cloud, by starting with a virtual Debian installation at some
4474 virtual hosting service and setting up all the services on first
4480 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
4481 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
4482 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
4483 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
4484 <description><P
>In January,
4485 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
4486 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
4487 channel #debian-lego
</a
>, for those of us in the Debian and Linux
4488 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
4489 marvellous construction system from Denmark. We also created
4490 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
4491 a place to take notes and write down our plans and hopes. And several
4492 people showed up to help. I was very happy to see the effect of my
4493 call. Since the small start, we have a debtags tag
4494 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
4495 tag for LEGO related packages, and now count
10 packages related to
4496 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
4498 <p
><table
>
4499 <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
>
4500 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
4501 <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
>
4502 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
4503 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
4504 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
4505 <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
>
4506 <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
>
4507 <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
>
4508 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
4509 </table
></p
>
4511 <p
>Some of these are available in Wheezy, and all but one are
4512 currently available in Jessie/testing. leocad is so far only
4513 available in experimental.
</p
>
4515 <p
>If you care about LEGO in Debian, please join us on IRC and help
4516 adding the rest of the great free software tools available on Linux
4517 for LEGO designers.
</p
>
4522 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
4523 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
4524 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
4525 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
4526 <description><p
>When I woke up this morning, I was very happy to see that the
4527 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
4528 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
4529 Debian release, and I expect to move my machines at home over to it fairly
4532 <p
>The new debian release contain heaps of new stuff, and one program
4533 in particular make me very happy to see included. The
4534 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
4535 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
4536 included for the first time. Alongside similar programs like
4537 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
4538 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
4539 it allow for visual programming where syntax errors can not happen,
4540 and a friendly programming environment for learning to control the
4541 computer. Scratch will also be included in the next release of Debian
4544 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
4545 Edu/Skolelinux release too. The
4546 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
4547 alpha release
</a
> went out last week, and the next should soon
4553 <title>Isenkram
0.2 finally in the Debian archive
</title>
4554 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
4555 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
4556 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
4557 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
4558 package
</a
> finally made it into the archive, after lingering in NEW
4559 for many months. I uploaded it to the Debian experimental suite
4560 2013-
01-
27, and today it was accepted into the archive.
</p
>
4562 <p
>Isenkram is a system for suggesting to users what packages to
4563 install to work with a pluggable hardware device. The suggestion pop
4564 up when the device is plugged in. For example if a Lego Mindstorm NXT
4565 is inserted, it will suggest to install the program needed to program
4566 the NXT controller. Give it a go, and report bugs and suggestions to
4572 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
4573 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
4574 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
4575 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
4576 <description><p
>My
4577 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
4578 bitcoin related blog post
</a
> mentioned that the new
4579 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
4580 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
4581 2013-
01-
19, and have been available in unstable since then. It was
4582 automatically copied to Ubuntu, and is available in their Raring
4583 version too.
</p
>
4585 <p
>But there is a strange problem with the build that block this new
4586 version from being available on the i386 and kfreebsd-i386
4587 architectures. For some strange reason, the autobuilders in Debian
4588 for these architectures fail to run the test suite on these
4589 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
4590 We are so far unable to reproduce it when building it manually, and
4591 no-one have been able to propose a fix. If you got an idea what is
4592 failing, please let us know via the BTS.
</p
>
4594 <p
>One feature that is annoying me with of the bitcoin client, because
4595 I often run low on disk space, is the fact that the client will exit
4596 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
4597 #
696715</a
>). So make sure you have enough disk space when you run
4600 <p
>As usual, if you use bitcoin and want to show your support of my
4601 activities, please send Bitcoin donations to my address
4602 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4607 <title>Welcome to the world, Isenkram!
</title>
4608 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
4609 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
4610 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
4611 <description><p
>Yesterday, I
4612 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
4613 for testers
</a
> for my prototype for making Debian better at handling
4614 pluggable hardware devices, which I
4615 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
4616 out to create
</a
> earlier this month. Several valuable testers showed
4617 up, and caused me to really want to to open up the development to more
4618 people. But before I did this, I want to come up with a sensible name
4619 for this project. Today I finally decided on a new name, and I have
4620 renamed the project from hw-support-handler to this new name. In the
4621 process, I moved the source to git and made it available as a
4622 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
4623 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
4624 To fetch and build the latest version of the source, use
</p
>
4627 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
4628 cd isenkram
&& git-buildpackage -us -uc
4631 <p
>I have not yet adjusted all files to use the new name yet. If you
4632 want to hack on the source or improve the package, please go ahead.
4633 But please talk to me first on IRC or via email before you do major
4634 changes, to make sure we do not step on each others toes. :)
</p
>
4636 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
4637 stuff, typically meaning tools, nails, screws, etc. Typical hardware
4638 stuff, in other words. I
've been told it is the Norwegian variant of
4639 the German word eisenkram, for those that are familiar with that
4642 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
4643 instructions, to avoid confusing people with an error from the signing
4646 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
4647 clone argument to avoid the need for authentication.
</p
>
4652 <title>First prototype ready making hardware easier to use in Debian
</title>
4653 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
4654 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
4655 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
4656 <description><p
>Early this month I set out to try to
4657 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
4658 the Debian support for pluggable hardware devices
</a
>. Now my
4659 prototype is working, and it is ready for a larger audience. To test
4661 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
4662 from the Debian Edu subversion repository
</a
>, build and install the
4663 package. You might have to log out and in again activate the
4664 autostart script.
</p
>
4666 <p
>The design is simple:
</p
>
4670 <li
>Add desktop entry in /usr/share/autostart/ causing a program
4671 hw-support-handlerd to start when the user log in.
</li
>
4673 <li
>This program listen for kernel events about new hardware (directly
4674 from the kernel like udev does), not using HAL dbus events as I
4675 initially did.
</li
>
4677 <li
>When new hardware is inserted, look up the hardware modalias in
4678 the APT database, a database
4679 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
4680 via HTTP
</a
> and a database available as part of the package.
</li
>
4682 <li
>If a package is mapped to the hardware in question, the package
4683 isn
't installed yet and this is the first time the hardware was
4684 plugged in, show a desktop notification suggesting to install the
4685 package or packages.
</li
>
4687 <li
>If the user click on the
'install package now
' button, ask
4688 aptdaemon via the PackageKit API to install the requrired package.
</li
>
4690 <li
>aptdaemon ask for root password or sudo password, and install the
4691 package while showing progress information in a window.
</li
>
4695 <p
>I still need to come up with a better name for the system. Here
4696 are some screen shots showing the prototype in action. First the
4697 notification, then the password request, and finally the request to
4698 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
4700 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
4701 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
4702 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
4703 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
4704 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
4706 <p
>The prototype still need to be improved with longer timeouts, but
4707 is already useful. The database of hardware to package mappings also
4708 need more work. It is currently compatible with the Ubuntu way of
4709 storing such information in the package control file, but could be
4710 changed to use other formats instead or in addition to the current
4711 method. I
've dropped the use of discover for this mapping, as the
4712 modalias approach is more flexible and easier to use on Linux as long
4713 as the Linux kernel expose its modalias strings directly.
</p
>
4715 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
4716 here is the command required to check out and build the source: Use
4717 '<tt
>svn checkout
4718 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
4719 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
4720 devscripts package.
</p
>
4722 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
4723 renamed to Isenkram and the source moved from the Debian Edu
4724 subversion repository to a Debian collab-maint git repository. See
4725 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
4726 instructions
</a
> for details.
</p
>
4731 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
4732 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
4733 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
4734 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
4735 <description><p
>This Christmas my trusty old laptop died. It died quietly and
4736 suddenly in bed. With a quiet whimper, it went completely quiet and
4737 black. The power button was no longer able to turn it on. It was a
4738 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4739 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4740 Compaq I had before that. Now I need to find a replacement. To keep
4741 going during Christmas, I moved the one year old SSD disk to my old
4742 X40 where it fitted (only one I had left that could use it), but it is
4743 not a durable solution.
4745 <p
>My laptop needs are fairly modest. This is my wishlist from when I
4746 got a new one more than
10 years ago. It still holds true.:)
</p
>
4750 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
4751 than A4).
</li
>
4752 <li
>Robust, it will be in my backpack every day.
</li
>
4753 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
4754 <li
>Long battery life time. Preferable a week.
</li
>
4755 <li
>Internal WIFI network card.
</li
>
4756 <li
>Internal Twisted Pair network card.
</li
>
4757 <li
>Some USB slots (
2-
3 is plenty)
</li
>
4758 <li
>Good keyboard - similar to the Thinkpad.
</li
>
4759 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
4761 <li
>Hardware supported by Debian Stable, ie the default kernel and
4762 X.org packages.
</li
>
4763 <li
>Quiet, preferably fan free (or at least not using the fan most of
4768 <p
>You will notice that there are no RAM and CPU requirements in the
4769 list. The reason is simply that the specifications on laptops the
4770 last
10-
15 years have been sufficient for my needs, and I have to look
4771 at other features to choose my laptop. But are there still made as
4772 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4773 robust, and Thinkpads seem to be heading in the wrong direction since
4774 Lenovo took over. But I
've been told that X220 and X1 Carbon might
4775 still be useful.
</p
>
4777 <p
>Perhaps I should rethink my needs, and look for a pad with an
4778 external keyboard? I
'll have to check the
4779 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
4780 well-supported laptops, or perhaps just buy one preinstalled from one
4781 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
4782 Pre-loaded site
</a
>.
</p
>
4787 <title>How to find a browser plugin supporting a given MIME type
</title>
4788 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
4789 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
4790 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
4791 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
4792 install to get support for a given MIME type. Thanks to
4793 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
4794 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
4795 Unfortunately, not very many packages provide the needed meta
4796 information, Anyway, here is a small script to look up all browser
4797 plugin packages announcing ther MIME support using this specification:
</p
>
4803 def pkgs_handling_mimetype(mimetype):
4808 version = pkg.candidate
4810 version = pkg.installed
4813 record = version.record
4814 if not record.has_key(
'Npp-MimeType
'):
4816 mime_types = record[
'Npp-MimeType
'].split(
',
')
4817 for t in mime_types:
4818 t = t.rstrip().strip()
4820 thepkgs.append(pkg.name)
4822 mimetype =
"audio/ogg
"
4823 if
1 < len(sys.argv):
4824 mimetype = sys.argv[
1]
4825 print
"Browser plugin packages supporting %s:
" % mimetype
4826 for pkg in pkgs_handling_mimetype(mimetype):
4827 print
" %s
" %pkg
4830 <p
>It can be used like this to look up a given MIME type:
</p
>
4833 % ./apt-find-browserplug-for-mimetype
4834 Browser plugin packages supporting audio/ogg:
4836 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4837 Browser plugin packages supporting application/x-shockwave-flash:
4838 browser-plugin-gnash
4842 <p
>In Ubuntu this mechanism is combined with support in the browser
4843 itself to query for plugins and propose to install the needed
4844 packages. It would be great if Debian supported such feature too. Is
4845 anyone working on adding it?
</p
>
4847 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
4848 request for icweasel support for this feature is
4849 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
4850 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
4851 of manpower and wish for a different design is the reason thus feature
4852 is not yet in iceweasel from Debian.
</p
>
4857 <title>What is the most supported MIME type in Debian?
</title>
4858 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
4859 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
4860 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
4861 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
4862 proposal to add AppStream information to the Debian archive
</a
>, is a
4863 proposal to make it possible for a Desktop application to propose to
4864 the user some package to install to gain support for a given MIME
4865 type, font, library etc. that is currently missing. With such
4866 mechanism in place, it would be possible for the desktop to
4867 automatically propose and install leocad if some LDraw file is
4868 downloaded by the browser.
</p
>
4870 <p
>To get some idea about the current content of the archive, I decided
4871 to write a simple program to extract all .desktop files from the
4872 Debian archive and look up the claimed MIME support there. The result
4874 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
4875 site
</a
>. Using the collected information, it become possible to
4876 answer the question in the title. Here are the
20 most supported MIME
4877 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4878 The complete list is available from the link above.
</p
>
4880 <p
><strong
>Debian Stable:
</strong
></p
>
4884 ----- -----------------------
4900 18 application/x-ogg
4907 <p
><strong
>Debian Testing:
</strong
></p
>
4911 ----- -----------------------
4927 18 application/x-ogg
4934 <p
><strong
>Debian Unstable:
</strong
></p
>
4938 ----- -----------------------
4955 18 application/x-ogg
4961 <p
>I am told that PackageKit can provide an API to access the kind of
4962 information mentioned in DEP-
11. I have not yet had time to look at
4963 it, but hope the PackageKit people in Debian are on top of these
4966 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
4967 discovering a typo in my script.
</p
>
4972 <title>Using modalias info to find packages handling my hardware
</title>
4973 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
4974 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
4975 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
4976 <description><p
>Yesterday, I wrote about the
4977 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
4978 values provided by the Linux kernel
</a
> following my hope for
4979 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
4980 dongle support in Debian
</a
>. Using this knowledge, I have tested how
4981 modalias values attached to package names can be used to map packages
4982 to hardware. This allow the system to look up and suggest relevant
4983 packages when I plug in some new hardware into my machine, and replace
4984 discover and discover-data as the database used to map hardware to
4987 <p
>I create a modaliases file with entries like the following,
4988 containing package name, kernel module name (if relevant, otherwise
4989 the package name) and globs matching the relevant hardware
4992 <p
><blockquote
>
4993 Package: package-name
4994 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
4995 </blockquote
></p
>
4997 <p
>It is fairly trivial to write code to find the relevant packages
4998 for a given modalias value using this file.
</p
>
5000 <p
>An entry like this would suggest the video and picture application
5001 cheese for many USB web cameras (interface bus class
0E01):
</p
>
5003 <p
><blockquote
>
5005 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
5006 </blockquote
></p
>
5008 <p
>An entry like this would suggest the pcmciautils package when a
5009 CardBus bridge (bus class
0607) PCI device is present:
</p
>
5011 <p
><blockquote
>
5012 Package: pcmciautils
5013 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
5014 </blockquote
></p
>
5016 <p
>An entry like this would suggest the package colorhug-client when
5017 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
5019 <p
><blockquote
>
5020 Package: colorhug-client
5021 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
5022 </blockquote
></p
>
5024 <p
>I believe the format is compatible with the format of the Packages
5025 file in the Debian archive. Ubuntu already uses their Packages file
5026 to store their mappings from packages to hardware.
</p
>
5028 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
5029 announce the hardware it support in a way my prototype understand.
5030 This allow those publishing packages in an APT source outside the
5031 Debian archive as well as those backporting packages to make sure the
5032 hardware mapping are included in the package meta information. I
've
5033 tested such header in the pymissile package, and its modalias mapping
5034 is working as it should with my prototype. It even made it to Ubuntu
5037 <p
>To test if it was possible to look up supported hardware using only
5038 the shell tools available in the Debian installer, I wrote a shell
5039 implementation of the lookup code. The idea is to create files for
5040 each modalias and let the shell do the matching. Please check out and
5042 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
5043 shell script. It run without any extra dependencies and fetch the
5044 hardware mappings from the Debian archive and the subversion
5045 repository where I currently work on my prototype.
</p
>
5047 <p
>When I use it on a machine with a yubikey inserted, it suggest to
5048 install yubikey-personalization:
</p
>
5050 <p
><blockquote
>
5051 % ./hw-support-lookup
5052 <br
>yubikey-personalization
5054 </blockquote
></p
>
5056 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
5057 propose to install the pcmciautils package:
</p
>
5059 <p
><blockquote
>
5060 % ./hw-support-lookup
5061 <br
>pcmciautils
5063 </blockquote
></p
>
5065 <p
>If you know of any hardware-package mapping that should be added to
5066 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
5067 database
</a
>, please tell me about it.
</p
>
5069 <p
>It could be possible to generate several of the mappings between
5070 packages and hardware. One source would be to look at packages with
5071 kernel modules, ie packages with *.ko files in /lib/modules/, and
5072 extract their modalias information. Another would be to look at
5073 packages with udev rules, ie packages with files in
5074 /lib/udev/rules.d/, and extract their vendor/model information to
5075 generate a modalias matching rule. I have not tested any of these to
5076 see if it work.
</p
>
5078 <p
>If you want to help implementing a system to let us propose what
5079 packages to install when new hardware is plugged into a Debian
5080 machine, please send me an email or talk to me on
5081 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5086 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
5087 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
5088 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
5089 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
5090 <description><p
>While looking into how to look up Debian packages based on hardware
5091 information, to find the packages that support a given piece of
5092 hardware, I refreshed my memory regarding modalias values, and decided
5093 to document the details. Here are my findings so far, also available
5095 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5096 Debian Edu subversion repository
</a
>:
5098 <p
><strong
>Modalias decoded
</strong
></p
>
5100 <p
>This document try to explain what the different types of modalias
5101 values stands for. It is in part based on information from
5102 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
5103 &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;,
5104 &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
5105 &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;.
5107 <p
>The modalias entries for a given Linux machine can be found using
5108 this shell script:
</p
>
5111 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
5114 <p
>The supported modalias globs for a given kernel module can be found
5115 using modinfo:
</p
>
5118 % /sbin/modinfo psmouse | grep alias:
5119 alias: serio:ty05pr*id*ex*
5120 alias: serio:ty01pr*id*ex*
5124 <p
><strong
>PCI subtype
</strong
></p
>
5126 <p
>A typical PCI entry can look like this. This is an Intel Host
5127 Bridge memory controller:
</p
>
5129 <p
><blockquote
>
5130 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5131 </blockquote
></p
>
5133 <p
>This represent these values:
</p
>
5138 sv
00001028 (subvendor)
5139 sd
000001AD (subdevice)
5141 sc
00 (bus subclass)
5145 <p
>The vendor/device values are the same values outputted from
'lspci
5146 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
5147 0600. The
0600 class is a host bridge. Other useful bus values are
5148 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
5150 <p
>Not sure how to figure out the interface value, nor what it
5153 <p
><strong
>USB subtype
</strong
></p
>
5155 <p
>Some typical USB entries can look like this. This is an internal
5156 USB hub in a laptop:
</p
>
5158 <p
><blockquote
>
5159 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
5160 </blockquote
></p
>
5162 <p
>Here is the values included in this alias:
</p
>
5165 v
1D6B (device vendor)
5166 p
0001 (device product)
5168 dc
09 (device class)
5169 dsc
00 (device subclass)
5170 dp
00 (device protocol)
5171 ic
09 (interface class)
5172 isc
00 (interface subclass)
5173 ip
00 (interface protocol)
5176 <p
>The
0900 device class/subclass means hub. Some times the relevant
5177 class is in the interface class section. For a simple USB web camera,
5178 these alias entries show up:
</p
>
5180 <p
><blockquote
>
5181 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
5182 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
5183 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
5184 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
5185 </blockquote
></p
>
5187 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
5188 camera),
0101 is audio control device and
0102 is audio streaming (aka
5189 microphone). Thus this is a camera with microphone included.
</p
>
5191 <p
><strong
>ACPI subtype
</strong
></p
>
5193 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
5194 receiver in a Thinkpad X40:
</p
>
5196 <p
><blockquote
>
5197 acpi:IBM0071:PNP0511:
5198 </blockquote
></p
>
5200 <p
>The values between the colons are IDs.
</p
>
5202 <p
><strong
>DMI subtype
</strong
></p
>
5204 <p
>The DMI table contain lots of information about the computer case
5205 and model. This is an entry for a IBM Thinkpad X40, fetched from
5206 /sys/devices/virtual/dmi/id/modalias:
</p
>
5208 <p
><blockquote
>
5209 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
5210 </blockquote
></p
>
5212 <p
>The values present are
</p
>
5215 bvn IBM (BIOS vendor)
5216 bvr
1UETB
6WW(
1.66) (BIOS version)
5217 bd
06/
15/
2005 (BIOS date)
5218 svn IBM (system vendor)
5219 pn
2371H4G (product name)
5220 pvr ThinkPadX40 (product version)
5221 rvn IBM (board vendor)
5222 rn
2371H4G (board name)
5223 rvr NotAvailable (board version)
5224 cvn IBM (chassis vendor)
5225 ct
10 (chassis type)
5226 cvr NotAvailable (chassis version)
5229 <p
>The chassis type
10 is Notebook. Other interesting values can be
5230 found in the dmidecode source:
</p
>
5234 4 Low Profile Desktop
5247 17 Main Server Chassis
5248 18 Expansion Chassis
5250 20 Bus Expansion Chassis
5251 21 Peripheral Chassis
5253 23 Rack Mount Chassis
5262 <p
>The chassis type values are not always accurately set in the DMI
5263 table. For example my home server is a tower, but the DMI modalias
5264 claim it is a desktop.
</p
>
5266 <p
><strong
>SerIO subtype
</strong
></p
>
5268 <p
>This type is used for PS/
2 mouse plugs. One example is from my
5269 test machine:
</p
>
5271 <p
><blockquote
>
5272 serio:ty01pr00id00ex00
5273 </blockquote
></p
>
5275 <p
>The values present are
</p
>
5284 <p
>This type is supported by the psmouse driver. I am not sure what
5285 the valid values are.
</p
>
5287 <p
><strong
>Other subtypes
</strong
></p
>
5289 <p
>There are heaps of other modalias subtypes according to
5290 file2alias.c. There is the rest of the list from that source: amba,
5291 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
5292 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
5293 vmbus, x86cpu and zorro. I did not spend time documenting all of
5294 these, as they do not seem relevant for my intended use with mapping
5295 hardware to packages when new stuff is inserted during run time.
</p
>
5297 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
5299 <p
>To check which kernel modules provide support for a given modalias,
5300 one can use the following shell script:
</p
>
5303 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
5304 echo
"$id
" ; \
5305 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
5309 <p
>The output can look like this (only the first few entries as the
5310 list is very long on my test machine):
</p
>
5314 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
5316 FATAL: Module acpi:device: not found.
5318 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
5319 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
5320 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
5321 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
5322 acpi:IBM0071:PNP0511:
5323 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
5324 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
5325 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
5329 <p
>If you want to help implementing a system to let us propose what
5330 packages to install when new hardware is plugged into a Debian
5331 machine, please send me an email or talk to me on
5332 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5334 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
5335 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
5336 in /sys/ with space in them.
</p
>
5341 <title>Moved the pymissile Debian packaging to collab-maint
</title>
5342 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
5343 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
5344 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
5345 <description><p
>As part of my investigation on how to improve the support in Debian
5346 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
5347 Launcher and updated the Debian package
5348 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
5349 sure udev will fix the device permissions when it is plugged in. I
5350 also added a
"Modaliases
" header to test it in the Debian archive and
5351 hopefully make the package be proposed by jockey in Ubuntu when a user
5352 plug in his rocket launcher. In the process I moved the source to a
5353 git repository under collab-maint, to make it easier for any DD to
5354 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
5355 is not very active, but the software still work for me even after five
5356 years of relative silence. The new git repository is not listed in
5357 the uploaded package yet, because I want to test the other changes a
5358 bit more before I upload the new version. If you want to check out
5359 the new version with a .desktop file included, visit the
5360 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
5361 view
</a
> or use
"<tt
>git clone
5362 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
5367 <title>Lets make hardware dongles easier to use in Debian
</title>
5368 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
5369 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
5370 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
5371 <description><p
>One thing that annoys me with Debian and Linux distributions in
5372 general, is that there is a great package management system with the
5373 ability to automatically install software packages by downloading them
5374 from the distribution mirrors, but no way to get it to automatically
5375 install the packages I need to use the hardware I plug into my
5376 machine. Even if the package to use it is easily available from the
5377 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
5378 suggest to automatically install the python-nxt, nbc and t2n packages
5379 I need to talk to it. When I plug in a Yubikey, it could propose the
5380 yubikey-personalization package. The information required to do this
5381 is available, but no-one have pulled all the pieces together.
</p
>
5383 <p
>Some years ago, I proposed to
5384 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
5385 the discover subsystem to implement this
</a
>. The idea is fairly
5390 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
5391 starting when a user log in.
</li
>
5393 <li
>Set this program up to listen for kernel events emitted when new
5394 hardware is inserted into the computer.
</li
>
5396 <li
>When new hardware is inserted, look up the hardware ID in a
5397 database mapping to packages, and take note of any non-installed
5398 packages.
</li
>
5400 <li
>Show a message to the user proposing to install the discovered
5401 package, and make it easy to install it.
</li
>
5405 <p
>I am not sure what the best way to implement this is, but my
5406 initial idea was to use dbus events to discover new hardware, the
5407 discover database to find packages and
5408 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
5411 <p
>Yesterday, I found time to try to implement this idea, and the
5412 draft package is now checked into
5413 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5414 Debian Edu subversion repository
</a
>. In the process, I updated the
5415 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
5416 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
5417 the relevant packages in Debian, and uploaded a new version
5418 2.2013.01.09 to unstable. I also discovered that the current
5419 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
5420 package in Debian no longer discovered any USB devices, because
5421 /proc/bus/usb/devices is no longer present. I ported it to use
5422 libusb as a fall back option to get it working. The fixed package
5423 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
5424 because of the freeze).
</p
>
5426 <p
>With this prototype in place, I can insert my Yubikey, and get this
5427 desktop notification to show up (only once, the first time it is
5428 inserted):
</p
>
5430 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
5432 <p
>For this prototype to be really useful, some way to automatically
5433 install the proposed packages by pressing the
"Please install
5434 program(s)
" button should to be implemented.
</p
>
5436 <p
>If this idea seem useful to you, and you want to help make it
5437 happen, please help me update the discover-data database with mappings
5438 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
5439 list the package you would like to have installed when a given
5440 hardware device is inserted into your computer, and report bugs using
5441 reportbug if it isn
't. Or, if you know of a better way to provide
5442 such mapping, please let me know.
</p
>
5444 <p
>This prototype need more work, and there are several questions that
5445 should be considered before it is ready for production use. Is dbus
5446 the correct way to detect new hardware? At the moment I look for HAL
5447 dbus events on the system bus, because that is the events I could see
5448 on my Debian Squeeze KDE desktop. Are there better events to use?
5449 How should the user be notified? Is the desktop notification
5450 mechanism the best option, or should the background daemon raise a
5451 popup instead? How should packages be installed? When should they
5452 not be installed?
</p
>
5454 <p
>If you want to help getting such feature implemented in Debian,
5455 please send me an email. :)
</p
>
5460 <title>New IRC channel for LEGO designers using Debian
</title>
5461 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
5462 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
5463 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
5464 <description><p
>During Christmas, I have worked a bit on the Debian support for
5465 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
5466 NXT
</a
>. My son and I have played a bit with my NXT set, and I
5467 discovered I had to build all the tools myself because none were
5468 already in Debian Squeeze. If Debian support for LEGO is something
5469 you care about, please join me on the IRC channel
5470 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
5471 irc.debian.org). There is a lot that could be done to improve the
5472 Debian support for LEGO designers. For example both CAD software
5473 and Mindstorm compilers are missing. :)
</p
>
5475 <p
>Update
2012-
01-
03: A
5476 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
5477 including links to Lego related packages is now available.
</p
>
5482 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
5483 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
5484 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
5485 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
5486 <description><p
>Let me start by wishing you all marry Christmas and a happy new
5487 year! I hope next year will prove to be a good year.
</p
>
5489 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
5490 decentralised
"currency
" that allow people to transfer bitcoins
5491 between each other with minimal overhead, is a very interesting
5492 experiment. And as I wrote a few days ago, the bitcoin situation in
5493 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
5494 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
5495 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
5496 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
5497 for one of the ftpmasters to approve the new bitcoin-qt package
5500 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
5501 team in Debian, you can easily test the package in Debian Squeeze
5502 using the following steps to get a set of working packages:
</p
>
5504 <blockquote
><pre
>
5505 git clone git://git.debian.org/git/collab-maint/bitcoin
5507 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
5508 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
5509 </pre
></blockquote
>
5511 <p
>You might have to install some build dependencies as well. The
5512 list of commands should give you two packages, bitcoind and
5513 bitcoin-qt, ready for use in a Squeeze environment. Note that the
5514 client will download the complete set of bitcoin
"blocks
", which need
5515 around
5.6 GiB of data on my machine at the moment. Make sure your
5516 ~/.bitcoin/ directory have lots of spare room if you want to download
5517 all the blocks. The client will warn if the disk is getting full, so
5518 there is not really a problem if you got too little room, but you will
5519 not be able to get all the features out of the client.
</p
>
5521 <p
>As usual, if you use bitcoin and want to show your support of my
5522 activities, please send Bitcoin donations to my address
5523 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5528 <title>A word on bitcoin support in Debian
</title>
5529 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
5530 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
5531 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
5532 <description><p
>It has been a while since I wrote about
5533 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
5534 peer-to-peer based crypto-currency, and the reason is simply that I
5535 have been busy elsewhere. But two days ago, I started looking at the
5536 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
5537 Debian
</a
> again to try to recover my old bitcoin wallet. The package
5538 is now maintained by a
5539 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
5540 people
</a
>, and the grunt work had already been done by this team. We
5541 owe a huge thank you to all these team members. :)
5542 But I was sad to discover that the bitcoin client is missing in
5543 Wheezy. It is only available in Sid (and an outdated client from
5544 backports). The client had several RC bugs registered in BTS blocking
5545 it from entering testing. To try to help the team and improve the
5546 situation, I spent some time providing patches and triaging the bug
5547 reports. I also had a look at the bitcoin package available from Matt
5549 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
5550 Ubuntu
</a
>, and moved the useful pieces from that version into the
5551 Debian package.
</p
>
5553 <p
>After checking with the main package maintainer Jonas Smedegaard on
5554 IRC, I pushed several patches into the collab-maint git repository to
5555 improve the package. It now contains fixes for the RC issues (not from
5556 me, but fixed by Scott Howard), build rules for a Qt GUI client
5557 package, konqueror support for the bitcoin: URI and bash completion
5558 setup. As I work on Debian Squeeze, I also created
5559 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
5560 patch to backport
</a
> the latest version. Jonas is going to look at
5561 it and try to integrate it into the git repository before uploading a
5562 new version to unstable.
5564 <p
>I would very much like bitcoin to succeed, to get rid of the
5565 centralized control currently exercised in the monetary system. I
5566 find it completely unacceptable that the USA government is collecting
5567 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
5568 that the major credit card companies can block legal money
5569 transactions to Wikileaks. But for bitcoin to succeed, more people
5570 need to use bitcoins, and more people need to accept bitcoins when
5571 they sell products and services. Improving the bitcoin support in
5572 Debian is a small step in the right direction, but not enough.
5573 Unfortunately the user experience when browsing the web and wanting to
5574 pay with bitcoin is still not very good. The bitcoin: URI is a step
5575 in the right direction, but need to work in most or every browser in
5576 use. Also the bitcoin-qt client is too heavy to fire up to do a
5577 quick transaction. I believe there are other clients available, but
5578 have not tested them.
</p
>
5581 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
5582 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
5583 I received
20.15 BTC so far on the address I provided in my blog two
5584 years ago, as can be
5585 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
5586 on the blockexplorer service
</a
>. Thank you everyone for your
5587 donation. The blockexplorer service demonstrates quite well that
5588 bitcoin is not quite anonymous and untracked. :) I wonder if the
5589 number of users have gone up since then. If you use bitcoin and want
5590 to show your support of my activity, please send Bitcoin donations to
5591 the same address as last time,
5592 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5597 <title>Git repository for song book for Computer Scientists
</title>
5598 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
5599 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
5600 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
5601 <description><p
>As I
5602 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
5603 this summer
</a
>, I have created a Computer Science song book a few
5604 years ago, and today I finally found time to create a public
5605 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
5606 repository for the project
</a
>.
</p
>
5608 <p
>If you want to help out, please clone the source and submit patches
5609 to the HTML version. To generate the PDF and PostScript version,
5610 please use prince XML, or let me know about a useful free software
5611 processor capable of creating a good looking PDF from the HTML.
</p
>
5613 <p
>Want to sing? You can still find the song book in HTML, PDF and
5614 PostScript formats at
5615 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
5616 Science Songbook
</a
>.
</p
>
5621 <title>Gratulerer med
19-årsdagen, Debian!
</title>
5622 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
5623 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
5624 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
5625 <description><p
>I dag fyller
5626 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
5627 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
5628 si gratulerer med dagen, Debian!
</p
>
5633 <title>Song book for Computer Scientists
</title>
5634 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
5635 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
5636 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
5637 <description><p
>Many years ago, while studying Computer Science at the
5638 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
5639 collecting computer related songs for use at parties. The original
5640 version was written in LaTeX, but a few years ago I got help from
5641 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
5642 while keeping the ability to create a nice book in PDF format. I have
5643 not had time to maintain the book for a while now, and guess I should
5644 put it up on some public version control repository where others can
5645 help me extend and update the book. If anyone is volunteering to help
5646 me with this, send me an email. Also let me know if there are songs
5647 missing in my book.
</p
>
5649 <p
>I have not mentioned the book on my blog so far, and it occured to
5650 me today that I really should let all my readers share the joys of
5651 singing out load about programming, computers and computer networks.
5652 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
5653 12</a
> is about to start (and I am not going). Want to sing? Check
5654 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
5655 Computer Science Songbook
</a
>.
5660 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
5661 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
5662 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
5663 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
5664 <description><p
>At work we have heaps of servers. I believe the total count is
5665 around
1000 at the moment. To be able to get help from the vendors
5666 when something go wrong, we want to keep the firmware on the servers
5667 up to date. If the firmware isn
't the latest and greatest, the
5668 vendors typically refuse to start debugging any problems until the
5669 firmware is upgraded. So before every reboot, we want to upgrade the
5670 firmware, and we would really like everyone handling servers at the
5671 university to do this themselves when they plan to reboot a machine.
5672 For that to happen we at the unix server admin group need to provide
5673 the tools to do so.
</p
>
5675 <p
>To make firmware upgrading easier, I am working on a script to
5676 fetch and install the latest firmware for the servers we got. Most of
5677 our hardware are from Dell and HP, so I have focused on these servers
5678 so far. This blog post is about the Dell part.
</P
>
5680 <p
>On the Dell FTP site I was lucky enough to find
5681 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
5682 with firmware information for all
11th generation servers, listing
5683 which firmware should be used on a given model and where on the FTP
5684 site I can find it. Using a simple perl XML parser I can then
5685 download the shell scripts Dell provides to do firmware upgrades from
5686 within Linux and reboot when all the firmware is primed and ready to
5687 be activated on the first reboot.
</p
>
5689 <p
>This is the Dell related fragment of the perl code I am working on.
5690 Are there anyone working on similar tools for firmware upgrading all
5691 servers at a site? Please get in touch and lets share resources.
</p
>
5693 <p
><pre
>
5697 use File::Temp qw(tempdir);
5699 # Install needed RHEL packages if missing
5701 'XML::Simple
' =
> 'perl-XML-Simple
',
5703 for my $module (keys %rhelmodules) {
5704 eval
"use $module;
";
5706 my $pkg = $rhelmodules{$module};
5707 system(
"yum install -y $pkg
");
5708 eval
"use $module;
";
5712 my $errorsto =
'pere@hungry.com
';
5718 sub run_firmware_script {
5719 my ($opts, $script) = @_;
5721 print STDERR
"fail: missing script name\n
";
5724 print STDERR
"Running $script\n\n
";
5726 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
5727 print STDERR
"success: firmware script ran succcessfully\n
";
5729 print STDERR
"fail: firmware script returned error\n
";
5733 sub run_firmware_scripts {
5734 my ($opts, @dirs) = @_;
5735 # Run firmware packages
5736 for my $dir (@dirs) {
5737 print STDERR
"info: Running scripts in $dir\n
";
5738 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
5739 while (my $s = readdir $dh) {
5740 next if $s =~ m/^\.\.?/;
5741 run_firmware_script($opts,
"$dir/$s
");
5749 print STDERR
"info: Downloading $url\n
";
5750 system(
"wget --quiet \
"$url\
"");
5755 my $product = `dmidecode -s system-product-name`;
5758 if ($product =~ m/PowerEdge/) {
5760 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5761 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
5763 my $tmpdir = tempdir(
5767 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
5768 system(
'gunzip Catalog.xml.gz
');
5769 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
5770 # -q is quiet, disabling interactivity and reducing console output
5771 my $fwopts =
"-q
";
5773 for my $url (@paths) {
5774 fetch_dell_fw($url);
5776 run_firmware_scripts($fwopts, $tmpdir);
5778 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5779 print STDERR
"error: Please report to $errorsto.\n
";
5783 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5784 print STDERR
"error: Please report to $errorsto.\n
";
5790 my $url =
"ftp://ftp.us.dell.com/$path
";
5794 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5795 # firmware packages to download from Dell. Only work for Linux
5796 # machines and
11th generation Dell servers.
5797 sub fetch_dell_fw_list {
5798 my $filename = shift;
5800 my $product = `dmidecode -s system-product-name`;
5802 my ($mybrand, $mymodel) = split(/\s+/, $product);
5804 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
5806 my $xml = XMLin($filename);
5808 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
5809 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
5810 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
5812 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
5813 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
5815 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
5817 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
5819 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
5822 for my $component (@{$xml-
>{SoftwareComponent}}) {
5823 my $componenttype = $component-
>{ComponentType}-
>{value};
5825 # Drop application packages, only firmware and BIOS
5826 next if
'APAC
' eq $componenttype;
5828 my $cpath = $component-
>{path};
5829 for my $path (@paths) {
5830 if ($cpath =~ m%/$path$%) {
5831 push(@paths, $cpath);
5839 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
5840 it could work on other platforms with some tweaking. Anyone know a
5841 index like Catalog.xml is available from HP for HP servers? At the
5842 moment I maintain a similar list manually and it is quickly getting
5848 <title>How is booting into runlevel
1 different from single user boots?
</title>
5849 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
5850 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
5851 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
5852 <description><p
>Wouter Verhelst have some
5853 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
5854 comments and opinions
</a
> on my blog post on
5855 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
5856 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
5857 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
5858 default KDE desktop in Debian
</a
>. I only have time to address one
5859 small piece of his comment now, and though it best to address the
5860 misunderstanding he bring forward:
</p
>
5862 <p
><blockquote
>
5863 Currently, a system admin has four options: [...] boot to a
5864 single-user system (by adding
'single
' to the kernel command line;
5865 this runs rcS and rc1 scripts)
5866 </blockquote
></p
>
5868 <p
>This make me believe Wouter believe booting into single user mode
5869 and booting into runlevel
1 is the same. I am not surprised he
5870 believe this, because it would make sense and is a quite sensible
5871 thing to believe. But because the boot in Debian is slightly broken,
5872 runlevel
1 do not work properly and it isn
't the same as single user
5873 mode. I
'll try to explain what is actually happing, but it is a bit
5874 hard to explain.
</p
>
5876 <p
>Single user mode is defined like this in /etc/inittab:
5877 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
5878 executed in single user mode is sulogin. Single user mode is a boot
5879 state
"between
" the runlevels, and when booting into single user mode,
5880 only the scripts in /etc/rcS.d/ are executed before the init process
5881 enters the single user state. When switching to runlevel
1, the state
5882 is in fact not ending in runlevel
1, but it passes through runlevel
1
5883 and end up in the single user mode (see /etc/rc1.d/S03single, which
5884 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
5885 1. It is confusing that the
'S
' (single user) init mode is not the
5886 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5889 <p
>This summary might make it clearer. When booting for the first
5890 time into single user mode, the following commands are executed:
5891 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
5892 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
5893 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
5894 trying to continue after visiting single user mode. Not all services
5895 are started again as they should, causing the machine to end up in an
5896 unpredicatble state. This is why Debian admins recommend rebooting
5897 after visiting single user mode.
</p
>
5899 <p
>A similar problem with runlevel
1 is caused by the amount of
5900 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
5901 to runlevel
1, the services started from /etc/rcS.d/ are not properly
5902 stopped when passing through the scripts in /etc/rc1.d/, and not
5903 started again when switching away from runlevel
1 to the runlevels
5904 2-
5. I believe the problem is best fixed by moving all the scripts
5905 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
5906 functioning single user mode during boot.
</p
>
5908 <p
>I have spent several years investigating the Debian boot system,
5909 and discovered this problem a few years ago. I suspect it originates
5910 from when sysvinit was introduced into Debian, a long time ago.
</p
>
5915 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
5916 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
5917 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
5918 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
5919 <description><p
>In the Debian boot system, several packages include scripts that
5920 are started from /etc/rcS.d/. In fact, there is a bite more of them
5921 than make sense, and this causes a few problems. What kind of
5922 problems, you might ask. There are at least two problems. The first
5923 is that it is not possible to recover a machine after switching to
5924 runlevel
1. One need to actually reboot to get the machine back to
5925 the expected state. The other is that single user boot will sometimes
5926 run into problems because some of the subsystems are activated before
5927 the root login is presented, causing problems when trying to recover a
5928 machine from a problem in that subsystem. A minor additional point is
5929 that moving more scripts out of rcS.d/ and into the other rc#.d/
5930 directories will increase the amount of scripts that can run in
5931 parallel during boot, and thus decrease the boot time.
</p
>
5933 <p
>So, which scripts should start from rcS.d/. In short, only the
5934 scripts that _have_ to execute before the root login prompt is
5935 presented during a single user boot should go there. Everything else
5936 should go into the numeric runlevels. This means things like
5937 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5938 the numeric runlevels. Today in Debian, there are around
115 init.d
5939 scripts that are started from rcS.d/, and most of them should be moved
5940 out. Do your package have one of them? Please help us make single
5941 user and runlevel
1 better by moving it.
</p
>
5943 <p
>Scripts setting up the screen, keyboard, system partitions
5944 etc. should still be started from rcS.d/, but there is for example no
5945 need to have the network enabled before the single user login prompt
5946 is presented.
</p
>
5948 <p
>As always, things are not so easy to fix as they sound. To keep
5949 Debian systems working while scripts migrate and during upgrades, the
5950 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5951 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5952 and the next ones can only be moved when their dependencies have been
5953 moved first. This migration must be done sequentially while we ensure
5954 that the package system upgrade packages in the right order to keep
5955 the system state correct. This will require some coordination when it
5956 comes to network related packages, but most of the packages with
5957 scripts that should migrate do not have anything in rcS.d/ depending
5958 on them. Some packages have already been updated, like the sudo
5959 package, while others are still left to do. I wish I had time to work
5960 on this myself, but real live constrains make it unlikely that I will
5961 find time to push this forward.
</p
>
5966 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
5967 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
5968 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
5969 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
5970 <description><p
>While at Debconf11, I have several times during discussions
5971 mentioned the issues I believe should be improved in Debian for its
5972 desktop to be useful for more people. The use case for this is my
5973 parents, which are currently running Kubuntu which solve the
5976 <p
>I suspect these four missing features are not very hard to
5977 implement. After all, they are present in Ubuntu, so if we wanted to
5978 do this in Debian we would have a source.
</p
>
5982 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
5983 are new packages available for upgrades, a icon in the KDE status bar
5984 indicate this, and clicking on it will activate the simple upgrade
5985 tool to handle it. I have no problem guiding both of my parents
5986 through the process over the phone. If a kernel reboot is required,
5987 this too is indicated by the status bars and the upgrade tool. Last
5988 time I checked, nothing with the same features was working in KDE in
5991 <li
><strong
>Simple handling of missing Firefox browser
5992 plugins.
</strong
> When the browser encounter a MIME type it do not
5993 currently have a handler for, it will ask the user if the system
5994 should search for a package that would add support for this MIME type,
5995 and if the user say yes, the APT sources will be searched for packages
5996 advertising the MIME type in their control file (visible in the
5997 Packages file in the APT archive). If one or more packages are found,
5998 it is a simple click of the mouse to add support for the missing mime
5999 type. If the package require the user to accept some non-free
6000 license, this is explained to the user. The entire process make it
6001 more clear to the user why something do not work in the browser, and
6002 make the chances higher for the user to blame the web page authors and
6003 not the browser for any missing features.
</li
>
6005 <li
><strong
>Simple handling of missing multimedia codec/format
6006 handlers.
</strong
> When the media players encounter a format or codec
6007 it is not supporting, a dialog pop up asking the user if the system
6008 should search for a package that would add support for it. This
6009 happen with things like MP3, Windows Media or H
.264. The selection
6010 and installation procedure is very similar to the Firefox browser
6011 plugin handling. This is as far as I know implemented using a
6012 gstreamer hook. The end result is that the user easily get access to
6013 the codecs that are present from the APT archives available, while
6014 explaining more on why a given format is unsupported by Ubuntu.
</li
>
6016 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
6017 displaying a text/plain file in my Debian browser, it will propose to
6018 start emacs to show it. If I remember correctly, when doing the same
6019 in Kunbutu it show the file as a text file in the browser. At least I
6020 know Opera will show text files within the browser. I much prefer the
6021 latter behaviour.
</li
>
6025 <p
>There are other nice features as well, like the simplified suite
6026 upgrader, but given that I am the one mostly doing the dist-upgrade,
6027 it do not matter much.
</p
>
6029 <p
>I really hope we could get these features in place for the next
6030 Debian release. It would require the coordinated effort of several
6031 maintainers, but would make the end user experience a lot better.
</p
>
6036 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
6037 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
6038 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
6039 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
6040 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
6041 site is build on Debian/Squeeze, and this platform was chosen because
6042 I am most familiar with Debian (being a Debian Developer for around
10
6043 years) because it is the latest stable Debian release which should get
6044 security support for a few years.
</p
>
6046 <p
>The web service is written in Perl, and depend on some perl modules
6047 that are missing in Debian at the moment. It would be great if these
6048 modules were added to the Debian archive, allowing anyone to set up
6049 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
6050 in their own country using only Debian packages. The list of modules
6051 missing in Debian/Squeeze isn
't very long, and I hope the perl group
6052 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
6053 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
6054 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
6055 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
6056 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
6057 easier in the future.
</p
>
6059 <p
>Thanks to the great tools in Debian, getting the missing modules
6060 installed on my server was a simple call to
'cpan2deb Module::Name
'
6061 and
'dpkg -i
' to install the resulting package. But this leave me
6062 with the responsibility of tracking security problems, which I really
6063 do not have time for.
</p
>
6068 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
6069 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
6070 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
6071 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
6072 <description><p
>Here is a small update for my English readers. Most of my blog
6073 posts have been in Norwegian the last few weeks, so here is a short
6074 update in English.
</p
>
6076 <p
>The kids still keep me too busy to get much free software work
6077 done, but I did manage to organise a project to get a Norwegian port
6078 of the British service
6079 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
6080 and it has been running for a month now. The entire project has been
6081 organised by me and two others. Around Christmas we gathered sponsors
6082 to fund the development work. In January I drafted a contract with
6083 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
6084 and in February the development took place. Most of it involved
6085 converting the source to use GPS coordinates instead of British
6086 easting/northing, and the resulting code should be a lot easier to get
6087 running in any country by now. The Norwegian
6088 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
6089 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
6090 source and the source for administrative borders in Norway, and
6091 support for this had to be added/fixed.
</p
>
6093 <p
>The Norwegian version went live March
3th, and we spent the weekend
6094 polishing the system before we announced it March
7th. The system is
6095 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
6096 problem reports in a few weeks. Soon we hope to announce the Android
6097 and iPhone versions making it even easier to report problems with the
6098 public infrastructure.
</p
>
6100 <p
>Perhaps something to consider for those of you in countries without
6101 such service?
</p
>
6106 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
6107 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
6108 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
6109 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
6110 <description><p
>The last few days I have looked at ways to track open security
6111 issues here at my work with the University of Oslo. My idea is that
6112 it should be possible to use the information about security issues
6113 available on the Internet, and check our locally
6114 maintained/distributed software against this information. It should
6115 allow us to verify that no known security issues are forgotten. The
6116 CVE database listing vulnerabilities seem like a great central point,
6117 and by using the package lists from Debian mapped to CVEs provided by
6118 the testing security team, I believed it should be possible to figure
6119 out which security holes were present in our free software
6120 collection.
</p
>
6122 <p
>After reading up on the topic, it became obvious that the first
6123 building block is to be able to name software packages in a unique and
6124 consistent way across data sources. I considered several ways to do
6125 this, for example coming up with my own naming scheme like using URLs
6126 to project home pages or URLs to the Freshmeat entries, or using some
6127 existing naming scheme. And it seem like I am not the first one to
6128 come across this problem, as MITRE already proposed and implemented a
6129 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
6130 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
6131 software, hardware and other platform components. The CPE ids are
6132 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
6133 Vulnerability Database
</a
>, allowing me to look up know security
6134 issues for any CPE name. With this in place, all I need to do is to
6135 locate the CPE id for the software packages we use at the university.
6136 This is fairly trivial (I google for
'cve cpe $package
' and check the
6137 NVD entry if a CVE for the package exist).
</p
>
6139 <p
>To give you an example. The GNU gzip source package have the CPE
6140 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
6141 check out, one could look up
6142 <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
6143 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
6144 The most recent one is
6145 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
6146 and at the bottom of the NVD page for this vulnerability the complete
6147 list of affected versions is provided.
</p
>
6149 <p
>The NVD database of CVEs is also available as a XML dump, allowing
6150 for offline processing of issues. Using this dump, I
've written a
6151 small script taking a list of CPEs as input and list all CVEs
6152 affecting the packages represented by these CPEs. One give it CPEs
6153 with version numbers as specified above and get a list of open
6154 security issues out.
</p
>
6156 <p
>Of course for this approach to be useful, the quality of the NVD
6157 information need to be high. For that to happen, I believe as many as
6158 possible need to use and contribute to the NVD database. I notice
6160 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
6161 map from CVE to CPE
</a
>, indicating that they are using the CPE
6162 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
6164 <p
>To get an idea about the quality for free software, I spent some
6165 time making it possible to compare the CVE database from Debian with
6166 the CVE database in NVD. The result look fairly good, but there are
6167 some inconsistencies in NVD (same software package having several
6168 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
6169 Debian believe are affected by a CVE). Hope to find time to improve
6170 the quality of NVD, but that require being able to get in touch with
6171 someone maintaining it. So far my three emails with questions and
6172 corrections have not seen any reply, but I hope contact can be
6173 established soon.
</p
>
6175 <p
>An interesting application for CPEs is cross platform package
6176 mapping. It would be useful to know which packages in for example
6177 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
6178 this would be trivial if all linux distributions provided CPE entries
6179 for their packages.
</p
>
6184 <title>Which module is loaded for a given PCI and USB device?
</title>
6185 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
6186 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
6187 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
6188 <description><p
>In the
6189 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
6190 package in Debian, there is a script to report useful information
6191 about the running hardware for use when people report missing
6192 information. One part of this script that I find very useful when
6193 debugging hardware problems, is the part mapping loaded kernel module
6194 to the PCI device it claims. It allow me to quickly see if the kernel
6195 module I expect is driving the hardware I am struggling with. To see
6196 the output, make sure discover-data is installed and run
6197 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
6198 one of my machines like this:
</p
>
6202 10de:
03eb i2c_nforce2
6205 10de:
03f0 snd_hda_intel
6214 <p
>The code in question look like this, slightly modified for
6215 readability and to drop the output to file descriptor
3:
</p
>
6218 if [ -d /sys/bus/pci/devices/ ] ; then
6219 echo loaded pci modules:
6221 cd /sys/bus/pci/devices/
6222 for address in * ; do
6223 if [ -d
"$address/driver/module
" ] ; then
6224 module=`cd $address/driver/module ; pwd -P | xargs basename`
6225 if grep -q
"^$module
" /proc/modules ; then
6226 address=$(echo $address |sed s/
0000://)
6227 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
6228 echo
"$id $module
"
6237 <p
>Similar code could be used to extract USB device module
6241 if [ -d /sys/bus/usb/devices/ ] ; then
6242 echo loaded usb modules:
6244 cd /sys/bus/usb/devices/
6245 for address in * ; do
6246 if [ -d
"$address/driver/module
" ] ; then
6247 module=`cd $address/driver/module ; pwd -P | xargs basename`
6248 if grep -q
"^$module
" /proc/modules ; then
6249 address=$(echo $address |sed s/
0000://)
6250 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
6251 if [
"$id
" ] ; then
6252 echo
"$id $module
"
6262 <p
>This might perhaps be something to include in other tools as
6268 <title>How to test if a laptop is working with Linux
</title>
6269 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
6270 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
6271 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
6272 <description><p
>The last few days I have spent at work here at the
<a
6273 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
6274 batch of computers will work with Linux. Every year for the last few
6275 years the university have organised shared bid of a few thousand
6276 computers, and this year HP won the bid. Two different desktops and
6277 five different laptops are on the list this year. We in the UNIX
6278 group want to know which one of these computers work well with RHEL
6279 and Ubuntu, the two Linux distributions we currently handle at the
6280 university.
</p
>
6282 <p
>My test method is simple, and I share it here to get feedback and
6283 perhaps inspire others to test hardware as well. To test, I PXE
6284 install the OS version of choice, and log in as my normal user and run
6285 a few applications and plug in selected pieces of hardware. When
6286 something fail, I make a note about this in the test matrix and move
6287 on. If I have some spare time I try to report the bug to the OS
6288 vendor, but as I only have the machines for a short time, I rarely
6289 have the time to do this for all the problems I find.
</p
>
6291 <p
>Anyway, to get to the point of this post. Here is the simple tests
6292 I perform on a new model.
</p
>
6296 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
6297 and Ubuntu Maverik at the moment. If I feel like it, I also test with
6298 RHEL5 and Debian Edu/Squeeze.
</li
>
6300 <li
>Is X.org working? If the graphical login screen show up after
6301 installation, X.org is working.
</li
>
6303 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
6304 package mesa-utils on Ubuntu) and writing down the frames per second
6305 reported by the program.
</li
>
6307 <li
>Is sound working? With Gnome and KDE, a sound is played when
6308 logging in, and if I can hear this the test is successful. If there
6309 are several audio exits on the machine, I try them all and check if
6310 the Gnome/KDE audio mixer can control where to send the sound. I
6311 normally test this by playing
6312 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
6313 video
</a
> in Firefox/Iceweasel.
</li
>
6315 <li
>Is the USB subsystem working? I test this by plugging in a USB
6316 memory stick and see if Gnome/KDE notices this.
</li
>
6318 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
6319 I have lying around, and see if Gnome/KDE notices this.
</li
>
6321 <li
>Is any built in camera working? Test using cheese, and see if a
6322 picture from the v4l device show up.
</li
>
6324 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
6325 any bluetooth devices are discovered. In my office, I normally see a
6328 <li
>For laptops, is the SD or Compaq Flash reader working. I have
6329 memory modules lying around, and stick them in and see if Gnome/KDE
6330 notice this.
</li
>
6332 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
6333 special button work, and if the laptop continue to work after
6336 <li
>For laptops, is the extra buttons working, like audio level,
6337 adjusting background light, switching on/off external video output,
6338 switching on/off wifi, bluetooth, etc? The set of buttons differ from
6339 laptop to laptop, so I just write down which are working and which are
6342 <li
>Some laptops have smart card readers, finger print readers,
6343 acceleration sensors etc. I rarely test these, as I do not know how
6344 to quickly test if they are working or not, so I only document their
6345 existence.
</li
>
6349 <p
>By now I suspect you are really curious what the test results are
6350 for the HP machines I am testing. I
'm not done yet, so I will report
6351 the test results later. For now I can report that HP
8100 Elite work
6352 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
6353 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
6354 can see, I have most machines left to test. One interesting
6355 observation is that Ubuntu Lucid has almost twice the frame rate than
6356 RHEL6 with glxgears. No idea why.
</p
>
6361 <title>Some thoughts on BitCoins
</title>
6362 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
6363 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
6364 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
6365 <description><p
>As I continue to explore
6366 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
6367 what properties the system have, and how it will be affected by laws
6368 and regulations here in Norway. Here are some random notes.
</p
>
6370 <p
>One interesting thing to note is that since the transactions are
6371 verified using a peer to peer network, all details about a transaction
6372 is known to everyone. This means that if a BitCoin address has been
6373 published like I did with mine in my initial post about BitCoin, it is
6374 possible for everyone to see how many BitCoins have been transfered to
6375 that address. There is even a web service to look at the details for
6376 all transactions. There I can see that my address
6377 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
6378 have received
16.06 Bitcoin, the
6379 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
6380 address of Simon Phipps have received
181.97 BitCoin and the address
6381 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
6382 of EFF have received
2447.38 BitCoins so far. Thank you to each and
6383 every one of you that donated bitcoins to support my activity. The
6384 fact that anyone can see how much money was transfered to a given
6385 address make it more obvious why the BitCoin community recommend to
6386 generate and hand out a new address for each transaction. I
'm told
6387 there is no way to track which addresses belong to a given person or
6388 organisation without the person or organisation revealing it
6389 themselves, as Simon, EFF and I have done.
</p
>
6391 <p
>In Norway, and in most other countries, there are laws and
6392 regulations limiting how much money one can transfer across the border
6393 without declaring it. There are money laundering, tax and accounting
6394 laws and regulations I would expect to apply to the use of BitCoin.
6395 If the Skolelinux foundation
6396 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
6397 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
6398 normal bank transfers like EFF is doing, how should this be accounted?
6399 Given that it is impossible to know if money can cross the border or
6400 not, should everything or nothing be declared? What exchange rate
6401 should be used when calculating taxes? Would receivers have to pay
6402 income tax if the foundation were to pay Skolelinux contributors in
6403 BitCoin? I have no idea, but it would be interesting to know.
</p
>
6405 <p
>For a currency to be useful and successful, it must be trusted and
6406 accepted by a lot of users. It must be possible to get easy access to
6407 the currency (as a wage or using currency exchanges), and it must be
6408 easy to spend it. At the moment BitCoin seem fairly easy to get
6409 access to, but there are very few places to spend it. I am not really
6410 a regular user of any of the vendor types currently accepting BitCoin,
6411 so I wonder when my kind of shop would start accepting BitCoins. I
6412 would like to buy electronics, travels and subway tickets, not herbs
6413 and books. :) The currency is young, and this will improve over time
6414 if it become popular, but I suspect regular banks will start to lobby
6415 to get BitCoin declared illegal if it become popular. I
'm sure they
6416 will claim it is helping fund terrorism and money laundering (which
6417 probably would be true, as is any currency in existence), but I
6418 believe the problems should be solved elsewhere and not by blaming
6419 currencies.
</p
>
6421 <p
>The process of creating new BitCoins is called mining, and it is
6422 CPU intensive process that depend on a bit of luck as well (as one is
6423 competing against all the other miners currently spending CPU cycles
6424 to see which one get the next lump of cash). The
"winner
" get
50
6425 BitCoin when this happen. Yesterday I came across the obvious way to
6426 join forces to increase ones changes of getting at least some coins,
6427 by coordinating the work on mining BitCoins across several machines
6428 and people, and sharing the result if one is lucky and get the
50
6430 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
6431 if this sounds interesting. I have not had time to try to set up a
6432 machine to participate there yet, but have seen that running on ones
6433 own for a few days have not yield any BitCoins througth mining
6436 <p
>Update
2010-
12-
15: Found an
<a
6437 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
6438 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
6439 it was interesting to read. The arguments presented seem to be
6440 equally valid for gold, which was used as a currency for many years.
</p
>
6445 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
6446 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
6447 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
6448 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
6449 <description><p
>With this weeks lawless
6450 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
6451 attacks
</a
> on Wikileak and
6452 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
6453 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
6454 not be trusted to handle money transactions.
6456 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
6457 Phipps on bitcoin
</a
> reminded me about a project that a friend of
6458 mine mentioned earlier. I decided to follow Simon
's example, and get
6459 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
6460 some help from my friend to get it all running, and he even handed me
6461 some bitcoins to get started. I even donated a few bitcoins to Simon
6462 for helping me remember BitCoin.
</p
>
6464 <p
>So, what is bitcoins, you probably wonder? It is a digital
6465 crypto-currency, decentralised and handled using peer-to-peer
6466 networks. It allows anonymous transactions and prohibits central
6467 control over the transactions, making it impossible for governments
6468 and companies alike to block donations and other transactions. The
6469 source is free software, and while the key dependency wxWidgets
2.9
6470 for the graphical user interface is missing in Debian, the command
6471 line client builds just fine. Hopefully Jonas
6472 <a href=
"http://bugs.debian.org/
578157">will get the package into
6473 Debian
</a
> soon.
</p
>
6475 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
6476 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
6477 bitcoins
</a
> when selling services and goods, and there are even
6478 currency
"stock
" markets where the exchange rate is decided. There
6479 are not many users so far, but the concept seems promising. If you
6480 want to get started and lack a friend with any bitcoins to spare,
6482 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
6483 bitcoin at the time of writing). Use
6484 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
6485 on the current exchange rates.
</p
>
6487 <p
>As an experiment, I have decided to set up bitcoind on one of my
6488 machines. If you want to support my activity, please send Bitcoin
6489 donations to the address
6490 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
6495 <title>Why isn
't Debian Edu using VLC?
</title>
6496 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
6497 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
6498 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
6499 <description><p
>In the latest issue of Linux Journal, the readers choices were
6500 presented, and the winner among the multimedia player were VLC.
6501 Personally, I like VLC, and it is my player of choice when I first try
6502 to play a video file or stream. Only if VLC fail will I drag out
6503 gmplayer to see if it can do better. The reason is mostly the failure
6504 model and trust. When VLC fail, it normally pop up a error message
6505 reporting the problem. When mplayer fail, it normally segfault or
6506 just hangs. The latter failure mode drain my trust in the program.
<p
>
6508 <p
>But even if VLC is my player of choice, we have choosen to use
6509 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
6510 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
6511 plugin to play web videos seamlessly, and the VLC browser plugin is
6512 not very good. For example, it lack in-line control buttons, so there
6513 is no way for the user to pause the video. Also, when I
6514 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
6515 tested the browser plugins
</a
> available in Debian, the VLC plugin
6516 failed on several video pages where mplayer based plugins worked. If
6517 the browser plugin for VLC was as good as the gecko-mediaplayer
6518 package (which uses mplayer), we would switch.
</P
>
6520 <p
>While VLC is a good player, its user interface is slightly
6521 annoying. The most annoying feature is its inconsistent use of
6522 keyboard shortcuts. When the player is in full screen mode, its
6523 shortcuts are different from when it is playing the video in a window.
6524 For example, space only work as pause when in full screen mode. I
6525 wish it had consisten shortcuts and that space also would work when in
6526 window mode. Another nice shortcut in gmplayer is [enter] to restart
6527 the current video. It is very nice when playing short videos from the
6528 web and want to restart it when new people arrive to have a look at
6529 what is going on.
</p
>
6534 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
6535 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
6536 <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>
6537 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
6538 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
6539 upgrade testing of the
6540 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
6541 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
6542 This seem like a very good idea, so I adjusted by test scripts and
6543 can now present the updated result from today:
</p
>
6545 <p
>This is for Gnome:
</p
>
6547 <p
>Installed using apt-get, missing with aptitude
</p
>
6549 <blockquote
><p
>
6554 browser-plugin-gnash
6561 freedesktop-sound-theme
6563 gconf-defaults-service
6578 gnome-desktop-environment
6582 gnome-session-canberra
6587 gstreamer0.10-fluendo-mp3
6593 libapache2-mod-dnssd
6596 libaprutil1-dbd-sqlite3
6599 libboost-date-time1.42
.0
6600 libboost-python1.42
.0
6601 libboost-thread1.42
.0
6603 libchamplain-gtk-
0.4-
0
6605 libclutter-gtk-
0.10-
0
6612 libfreerdp-plugins-standard
6627 libgnomepanel2.24-cil
6632 libgtksourceview2.0-common
6633 libmono-addins-gui0.2-cil
6634 libmono-addins0.2-cil
6635 libmono-cairo2.0-cil
6636 libmono-corlib2.0-cil
6637 libmono-i18n-west2.0-cil
6638 libmono-posix2.0-cil
6639 libmono-security2.0-cil
6640 libmono-sharpzip2.84-cil
6641 libmono-system2.0-cil
6644 libndesk-dbus-glib1.0-cil
6645 libndesk-dbus1.0-cil
6655 libtelepathy-farsight0
6664 nautilus-sendto-empathy
6668 python-aptdaemon-gtk
6670 python-beautifulsoup
6685 python-gtksourceview2
6696 python-pkg-resources
6703 python-twisted-conch
6709 python-zope.interface
6714 rhythmbox-plugin-cdrecorder
6721 system-config-printer-udev
6723 telepathy-mission-control-
5
6734 </p
></blockquote
>
6736 <p
>Installed using apt-get, removed with aptitude
</p
>
6738 <blockquote
><p
>
6744 fast-user-switch-applet
6763 libgtksourceview2.0-
0
6765 libsdl1.2debian-alsa
6771 system-config-printer
6776 </p
></blockquote
>
6778 <p
>Installed using aptitude, missing with apt-get
</p
>
6780 <blockquote
><p
>
6781 gstreamer0.10-gnomevfs
6782 </p
></blockquote
>
6784 <p
>Installed using aptitude, removed with apt-get
</p
>
6786 <blockquote
><p
>
6788 </p
></blockquote
>
6790 <p
>This is for KDE:
</p
>
6792 <p
>Installed using apt-get, missing with aptitude
</p
>
6794 <blockquote
><p
>
6796 </p
></blockquote
>
6798 <p
>Installed using apt-get, removed with aptitude
</p
>
6800 <blockquote
><p
>
6803 </p
></blockquote
>
6805 <p
>Installed using aptitude, missing with apt-get
</p
>
6807 <blockquote
><p
>
6821 kdeartwork-emoticons
6823 kdeartwork-theme-icon
6827 kdebase-workspace-bin
6828 kdebase-workspace-data
6842 kscreensaver-xsavers
6857 plasma-dataengines-workspace
6859 plasma-desktopthemes-artwork
6860 plasma-runners-addons
6861 plasma-scriptengine-googlegadgets
6862 plasma-scriptengine-python
6863 plasma-scriptengine-qedje
6864 plasma-scriptengine-ruby
6865 plasma-scriptengine-webkit
6866 plasma-scriptengines
6867 plasma-wallpapers-addons
6868 plasma-widget-folderview
6869 plasma-widget-networkmanagement
6873 xscreensaver-data-extra
6875 xscreensaver-gl-extra
6876 xscreensaver-screensaver-bsod
6877 </p
></blockquote
>
6879 <p
>Installed using aptitude, removed with apt-get
</p
>
6881 <blockquote
><p
>
6883 google-gadgets-common
6901 libggadget-qt-
1.0-
0b
6906 libkonqsidebarplugin4a
6915 libplasma-geolocation-interface4
6917 libplasmagenericshell4
6931 libsmokeknewstuff2-
3
6932 libsmokeknewstuff3-
3
6934 libsmokektexteditor3
6942 libsmokeqtnetwork4-
3
6948 libsmokeqtuitools4-
3
6960 plasma-dataengines-addons
6961 plasma-scriptengine-superkaramba
6962 plasma-widget-lancelot
6963 plasma-widgets-addons
6964 plasma-widgets-workspace
6968 update-notifier-common
6969 </p
></blockquote
>
6971 <p
>Running apt-get autoremove made the results using apt-get and
6972 aptitude a bit more similar, but there are still quite a lott of
6973 differences. I have no idea what packages should be installed after
6974 the upgrade, but hope those that do can have a look.
</p
>
6979 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
6980 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
6981 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
6982 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
6983 <description><p
>Most of the computers in use by the
6984 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
6985 are virtual machines. And they have been Xen machines running on a
6986 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
6987 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
6988 bit harder that it could have been, because we set up the Xen virtual
6989 machines to get the virtual partitions from LVM, which as far as I
6990 know is not supported by KVM. So to migrate, we had to convert
6991 several LVM logical volumes to partitions on a virtual disk file.
</p
>
6994 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
6995 nice recipe
</a
> to do this, and wrote the following script to do the
6996 migration. It uses qemu-img from the qemu package to make the disk
6997 image, parted to partition it, losetup and kpartx to present the disk
6998 image partions as devices, and dd to copy the data. I NFS mounted the
6999 new servers storage area on the old server to do the migration.
</p
>
7005 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
7010 if [ -z
"$
1" ] ; then
7011 echo
"Usage: $
0 &lt;hostname
&gt;
"
7017 if [ ! -e /dev/vg_data/$host-disk ] ; then
7018 echo
"error: unable to find LVM volume for $host
"
7022 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
7023 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7024 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7025 totalsize=$(( ( $disksize + $swapsize ) ))
7028 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
7029 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
7031 parted $img mklabel msdos
7032 parted $img mkpart primary linux-swap
0 $disksize
7033 parted $img mkpart primary ext2 $disksize $totalsize
7034 parted $img set
1 boot on
7037 losetup /dev/loop0 $img
7038 kpartx -a /dev/loop0
7040 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
7041 fsck.ext3 -f /dev/mapper/loop0p1 || true
7042 mkswap /dev/mapper/loop0p2
7044 kpartx -d /dev/loop0
7045 losetup -d /dev/loop0
7048 <p
>The script is perhaps so simple that it is not copyrightable, but
7049 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
7051 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
7052 the new disk image attached, installed grub-pc and linux-image-
686 and
7053 set up grub to boot from the disk image. After this, the KVM machines
7054 seem to work just fine.
</p
>
7059 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
7060 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
7061 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
7062 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
7063 <description><p
>I
'm still running upgrade testing of the
7064 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7065 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
7066 status. Here is a short update based on a test I ran
20101118.
</p
>
7068 <p
>I still do not know what a correct migration should look like, so I
7069 report any differences between apt and aptitude and hope someone else
7070 can see if anything should be changed.
</p
>
7072 <p
>This is for Gnome:
</p
>
7074 <p
>Installed using apt-get, missing with aptitude
</p
>
7076 <blockquote
><p
>
7077 apache2.2-bin aptdaemon at-spi baobab binfmt-support
7078 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
7079 dmz-cursor-theme empathy empathy-common finger
7080 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
7081 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
7082 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
7083 gnome-cards-data gnome-codec-install gnome-core
7084 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7085 gnome-search-tool gnome-session-canberra gnome-spell
7086 gnome-system-log gnome-themes-extras gnome-themes-more
7087 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7088 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7089 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7090 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7091 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
7092 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
7093 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
7094 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
7095 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
7096 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7097 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
7098 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7099 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7100 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7101 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7102 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7103 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7104 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7105 libmono-security2.0-cil libmono-sharpzip2.84-cil
7106 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
7107 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
7108 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
7109 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
7110 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
7111 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
7112 libxalan2-java libxerces2-java media-player-info mesa-utils
7113 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
7114 nautilus-sendto-empathy openoffice.org-writer2latex
7115 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
7116 python-aptdaemon python-aptdaemon-gtk python-axiom
7117 python-beautifulsoup python-bugbuddy python-clientform
7118 python-coherence python-configobj python-crypto python-cupshelpers
7119 python-cupsutils python-eggtrayicon python-elementtree
7120 python-epsilon python-evolution python-feedparser python-gdata
7121 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7122 python-gtksourceview2 python-httplib2 python-louie python-mako
7123 python-markupsafe python-mechanize python-nevow python-notify
7124 python-opengl python-openssl python-pam python-pkg-resources
7125 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7126 python-tagpy python-twisted-bin python-twisted-conch
7127 python-twisted-core python-twisted-web python-utidylib python-webkit
7128 python-xdg python-zope.interface remmina remmina-plugin-data
7129 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7130 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7131 software-center svgalibg1 system-config-printer-udev
7132 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
7133 totem totem-coherence totem-mozilla totem-plugins
7134 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7136 </p
></blockquote
>
7138 Installed using apt-get, removed with aptitude
7140 <blockquote
><p
>
7141 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
7142 epiphany-extensions epiphany-gecko evolution-exchange
7143 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
7144 gedit-common gnome-app-install gnome-games gnome-games-data
7145 gnome-nettool gnome-system-tools gnome-themes gnome-utils
7146 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
7147 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
7148 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
7149 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
7150 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
7151 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
7152 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7153 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7154 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7155 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
7156 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
7157 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
7158 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
7159 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
7160 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
7161 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
7162 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
7163 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
7164 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
7165 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
7166 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
7167 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
7168 sound-juicer swfdec-gnome system-config-printer totem-common
7169 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
7170 </p
></blockquote
>
7172 <p
>Installed using aptitude, missing with apt-get
</p
>
7174 <blockquote
><p
>
7175 gstreamer0.10-gnomevfs
7176 </p
></blockquote
>
7178 <p
>Installed using aptitude, removed with apt-get
</p
>
7180 <blockquote
><p
>
7182 </p
></blockquote
>
7184 <p
>This is for KDE:
</p
>
7186 <p
>Installed using apt-get, missing with aptitude
</p
>
7188 <blockquote
><p
>
7189 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
7190 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
7191 ghostscript-x git gnome-audio gnugo granatier gs-common
7192 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
7193 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
7194 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
7195 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7196 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
7197 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
7198 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7199 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
7200 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
7201 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
7202 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
7203 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
7204 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
7205 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
7206 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
7207 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
7208 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
7209 libkrossui4 libmailtools-perl libmime-tools-perl
7210 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
7211 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
7212 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
7213 lirc luatex marble networkstatus noatun-plugins
7214 openoffice.org-writer2latex palapeli palapeli-data parley
7215 parley-data poster psutils pulseaudio pulseaudio-esound-compat
7216 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
7217 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
7219 </p
></blockquote
>
7221 <p
>Installed using apt-get, removed with aptitude
</p
>
7223 <blockquote
><p
>
7224 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
7225 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
7226 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
7227 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
7228 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
7229 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
7230 kitchensync kiten kjumpingcube klatin klettres klickety klines
7231 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
7232 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
7233 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
7234 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
7235 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
7236 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
7237 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
7238 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
7239 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7240 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
7241 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
7242 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7243 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
7244 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
7245 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
7246 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
7247 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7248 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
7249 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
7250 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
7251 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
7252 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
7253 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
7254 mpeglib network-manager-kde noatun pmount tex-common texlive-base
7255 texlive-common texlive-doc-base texlive-fonts-recommended tidy
7256 ttf-dustin ttf-kochi-gothic ttf-sjfonts
7257 </p
></blockquote
>
7259 <p
>Installed using aptitude, missing with apt-get
</p
>
7261 <blockquote
><p
>
7262 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
7263 kdeartwork kdebase kdebase-apps kdebase-workspace
7264 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
7265 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
7266 netpbm plasma-widget-folderview plasma-widget-networkmanagement
7267 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
7268 xscreensaver-screensaver-bsod
7269 </p
></blockquote
>
7271 <p
>Installed using aptitude, removed with apt-get
</p
>
7273 <blockquote
><p
>
7274 kdebase-bin konq-plugins konqueror
7275 </p
></blockquote
>
7280 <title>Gnash buildbot slave and Debian kfreebsd
</title>
7281 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
7282 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
7283 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
7284 <description><p
>Answering
7285 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
7286 call from the Gnash project
</a
> for
7287 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
7288 current source, I have set up a virtual KVM machine on the Debian
7289 Edu/Skolelinux virtualization host to test the git source on
7290 Debian/Squeeze. I hope this can help the developers in getting new
7291 releases out more often.
</p
>
7293 <p
>As the developers want less main-stream build platforms tested to,
7294 I have considered setting up a
<a
7295 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
7296 machine as well. I have also considered using the kfreebsd
7297 architecture in Debian as a file server in NUUG to get access to the
5
7298 TB zfs volume we currently use to store DV video. Because of this, I
7299 finally got around to do a test installation of Debian/Squeeze with
7300 kfreebsd. Installation went fairly smooth, thought I noticed some
7301 visual glitches in the cdebconf dialogs (black cursor left on the
7302 screen at random locations). Have not gotten very far with the
7303 testing. Noticed cfdisk did not work, but fdisk did so it was not a
7304 fatal problem. Have to spend some more time on it to see if it is
7305 useful as a file server for NUUG. Will try to find time to set up a
7306 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
7311 <title>Debian in
3D
</title>
7312 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
7313 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
7314 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
7315 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
7317 <p
>3D printing is just great. I just came across this Debian logo in
7319 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
7320 thingiverse blog
</a
>.
</p
>
7325 <title>Software updates
2010-
10-
24</title>
7326 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
7327 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
7328 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
7329 <description><p
>Some updates.
</p
>
7331 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
7332 raise money for the project is going well. The lower limit of
10
7333 signers was reached in
24 hours, and so far
13 people have signed it.
7334 More signers and more funding is most welcome, and I am really curious
7335 how far we can get before the time limit of December
24 is reached.
7338 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
7339 about what appear to be a great code coverage tool capable of
7340 generating code coverage stats without any changes to the source code.
7342 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
7343 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
7344 It is missing in Debian, but the git source built just fine in Squeeze
7345 after I installed libelf-dev, libdwarf-dev, pkg-config and
7346 libglib2.0-dev. Failed to build in Lenny, but suspect that is
7347 solvable. I hope kcov make it into Debian soon.
</p
>
7349 <p
>Finally found time to wrap up the release notes for
<a
7350 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
7351 new alpha release of Debian Edu
</a
>, and just published the second
7352 alpha test release of the Squeeze based Debian Edu /
7353 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
7354 release. Give it a try if you need a complete linux solution for your
7355 school, including central infrastructure server, workstations, thin
7356 client servers and diskless workstations. A nice touch added
7357 yesterday is RDP support on the thin client servers, for windows
7358 clients to get a Linux desktop on request.
</p
>
7363 <title>Some notes on Flash in Debian and Debian Edu
</title>
7364 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
7365 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
7366 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
7367 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
7368 popularity-contest numbers
</a
>, the adobe-flashplugin package the
7369 second most popular used package that is missing in Debian. The sixth
7370 most popular is flashplayer-mozilla. This is a clear indication that
7371 working flash is important for Debian users. Around
10 percent of the
7372 users submitting data to popcon.debian.org have this package
7373 installed.
</p
>
7375 <p
>In the report written by Lars Risan in August
2008
7376 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
7377 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
7378 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
7379 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
7380 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
7381 web sites require Flash to work, and lacking working Flash support in
7382 the web browser and the problems with installing it was perceived as a
7383 good reason to stay with Windows.
</p
>
7385 <p
>I once saw a funny and sad comment in a web forum, where Linux was
7386 said to be the retarded cousin that did not really understand
7387 everything you told him but could work fairly well. This was a
7388 comment regarding the problems Linux have with proprietary formats and
7389 non-standard web pages, and is sad because it exposes a fairly common
7390 understanding of whose fault it is if web pages that only work in for
7391 example Internet Explorer
6 fail to work on Firefox, and funny because
7392 it explain very well how annoying it is for users when Linux
7393 distributions do not work with the documents they receive or the web
7394 pages they want to visit.
</p
>
7396 <p
>This is part of the reason why I believe it is important for Debian
7397 and Debian Edu to have a well working Flash implementation in the
7398 distribution, to get at least popular sites as Youtube and Google
7399 Video to working out of the box. For Squeeze, Debian have the chance
7400 to include the latest version of Gnash that will make this happen, as
7401 the new release
0.8.8 was published a few weeks ago and is resting in
7402 unstable. The new version work with more sites that version
0.8.7.
7403 The Gnash maintainers have asked for a freeze exception, but the
7404 release team have not had time to reply to it yet. I hope they agree
7405 with me that Flash is important for the Debian desktop users, and thus
7406 accept the new package into Squeeze.
</p
>
7411 <title>Circular package dependencies harms apt recovery
</title>
7412 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
7413 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
7414 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
7415 <description><p
>I discovered this while doing
7416 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
7417 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
7418 in Debian still got circular dependencies, and it is often claimed
7419 that apt and aptitude should be able to handle this just fine, but
7420 some times these dependency loops causes apt to fail.
</p
>
7422 <p
>An example is from todays
7423 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
7424 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
7425 causes perl-modules to fail to upgrade. The cause is simple. If a
7426 package fail to unpack, then only part of packages with the circular
7427 dependency might end up being unpacked when unpacking aborts, and the
7428 ones already unpacked will fail to configure in the recovery phase
7429 because its dependencies are unavailable.
</p
>
7431 <p
>In this log, the problem manifest itself with this error:
</p
>
7433 <blockquote
><pre
>
7434 dpkg: dependency problems prevent configuration of perl-modules:
7435 perl-modules depends on perl (
>=
5.10.1-
1); however:
7436 Version of perl on system is
5.10.0-
19lenny
2.
7437 dpkg: error processing perl-modules (--configure):
7438 dependency problems - leaving unconfigured
7439 </pre
></blockquote
>
7441 <p
>The perl/perl-modules circular dependency is already
7442 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
7443 hopefully be solved as soon as possible, but it is not the only one,
7444 and each one of these loops in the dependency tree can cause similar
7445 failures. Of course, they only occur when there are bugs in other
7446 packages causing the unpacking to fail, but it is rather nasty when
7447 the failure of one package causes the problem to become worse because
7448 of dependency loops.
</p
>
7451 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
7452 tireless effort by Bill Allombert
</a
>, the number of circular
7454 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
7455 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
7457 <p
>Todays testing also exposed a bug in
7458 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
7459 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
7460 apt-get and aptitude, the latter possibly caused by some circular
7461 dependency. Reported both to BTS to try to get someone to look at
7467 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
7468 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
7469 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
7470 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
7471 <description><p
>This is a
7472 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
7474 <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
7476 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
7477 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
7479 <p
>As a step to try to see if it possible to merge the DNS and DHCP
7480 LDAP objects, I have had a look at how the packages pdns-backend-ldap
7481 and dhcp3-server-ldap in Debian use the LDAP server. The two
7482 implementations are quite different in how they use LDAP.
</p
>
7484 To get this information, I started slapd with debugging enabled and
7485 dumped the debug output to a file to get the LDAP searches performed
7486 on a Debian Edu main-server. Here is a summary.
7488 <p
><strong
>powerdns
</strong
></p
>
7490 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
7491 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
7494 <p
>PowerDNS have two modes of operation using LDAP as its backend.
7495 One
"strict
" mode where the forward and reverse DNS lookups are done
7496 using the same LDAP objects, and a
"tree
" mode where the forward and
7497 reverse entries are in two different subtrees in LDAP with a structure
7498 based on the DNS names, as in tjener.intern and
7499 2.2.0.10.in-addr.arpa.
</p
>
7501 <p
>In tree mode, the server is set up to use a LDAP subtree as its
7502 base, and uses a
"base
" scoped search for the DNS name by adding
7503 "dc=tjener,dc=intern,
" to the base with a filter for
7504 "(associateddomain=tjener.intern)
" for the forward entry and
7505 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
7506 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
7507 forward entries, it is looking for attributes named dnsttl, arecord,
7508 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
7509 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
7510 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
7511 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
7512 spfrecord and modifytimestamp. For reverse entries it is looking for
7513 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
7514 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
7515 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
7516 ldapsearch commands could look like this:
</p
>
7518 <blockquote
><pre
>
7519 ldapsearch -h ldap \
7520 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7521 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7522 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7523 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7524 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7525 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7527 ldapsearch -h ldap \
7528 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7529 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
7530 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
7531 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
7532 srvrecord naptrrecord modifytimestamp
7533 </pre
></blockquote
>
7535 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
7536 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
7537 example LDAP objects used there. In addition to these objects, the
7538 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
7539 also exist.
</p
>
7541 <blockquote
><pre
>
7542 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
7544 objectclass: dnsdomain
7545 objectclass: domainrelatedobject
7548 associateddomain: tjener.intern
7550 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
7552 objectclass: dnsdomain2
7553 objectclass: domainrelatedobject
7555 ptrrecord: tjener.intern
7556 associateddomain:
2.2.0.10.in-addr.arpa
7557 </pre
></blockquote
>
7559 <p
>In strict mode, the server behaves differently. When looking for
7560 forward DNS entries, it is doing a
"subtree
" scoped search with the
7561 same base as in the tree mode for a object with filter
7562 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
7563 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
7564 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
7565 naptrrecord and modifytimestamp. For reverse entires it also do a
7566 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
7567 and the requested attributes are associateddomain, dnsttl and
7568 modifytimestamp. In short, in strict mode the objects with ptrrecord
7569 go away, and the arecord attribute in the forward object is used
7572 <p
>The forward and reverse searches can be simulated using ldapsearch
7573 like this:
</p
>
7575 <blockquote
><pre
>
7576 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7577 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7578 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7579 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7580 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7581 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7583 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7584 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
7585 </pre
></blockquote
>
7587 <p
>In addition to the forward and reverse searches , there is also a
7588 search for SOA records, which behave similar to the forward and
7589 reverse lookups.
</p
>
7591 <p
>A thing to note with the PowerDNS behaviour is that it do not
7592 specify any objectclass names, and instead look for the attributes it
7593 need to generate a DNS reply. This make it able to work with any
7594 objectclass that provide the needed attributes.
</p
>
7596 <p
>The attributes are normally provided in the cosine (RFC
1274) and
7597 dnsdomain2 schemas. The latter is used for reverse entries like
7598 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
7600 <p
>In Debian Edu, we have created DNS objects using the object classes
7601 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
7602 attributes) and domainrelatedobject (for associatedDomain). The use
7603 of structural object classes make it impossible to combine these
7604 classes with the object classes used by DHCP.
</p
>
7606 <p
>There are other schemas that could be used too, for example the
7607 dnszone structural object class used by Gosa and bind-sdb for the DNS
7608 attributes combined with the domainrelatedobject object class, but in
7609 this case some unused attributes would have to be included as well
7610 (zonename and relativedomainname).
</p
>
7612 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
7613 mode and not use any of the existing objectclasses (dnsdomain,
7614 dnsdomain2 and dnszone) when one want to combine the DNS information
7615 with DHCP information, and instead create a auxiliary object class
7616 defined something like this (using the attributes defined for
7617 dnsdomain and dnsdomain2 or dnszone):
</p
>
7619 <blockquote
><pre
>
7620 objectclass ( some-oid NAME
'dnsDomainAux
'
7623 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
7624 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
7625 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
7626 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
7627 A6Record $ DNAMERecord
7629 </pre
></blockquote
>
7631 <p
>This will allow any object to become a DNS entry when combined with
7632 the domainrelatedobject object class, and allow any entity to include
7633 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
7634 developers asking for their view on this schema and if they are
7635 interested in providing such schema with PowerDNS, and I hope my
7636 message will be accepted into their mailing list soon.
</p
>
7638 <p
><strong
>ISC dhcp
</strong
></p
>
7640 <p
>The DHCP server searches for specific objectclass and requests all
7641 the object attributes, and then uses the attributes it want. This
7642 make it harder to figure out exactly what attributes are used, but
7643 thanks to the working example in Debian Edu I can at least get an idea
7644 what is needed without having to read the source code.
</p
>
7646 <p
>In the DHCP server configuration, the LDAP base to use and the
7647 search filter to use to locate the correct dhcpServer entity is
7648 stored. These are the relevant entries from
7649 /etc/dhcp3/dhcpd.conf:
</p
>
7651 <blockquote
><pre
>
7652 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
7653 ldap-dhcp-server-cn
"dhcp
";
7654 </pre
></blockquote
>
7656 <p
>The DHCP server uses this information to nest all the DHCP
7657 configuration it need. The cn
"dhcp
" is located using the given LDAP
7658 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
7659 search result is this entry:
</p
>
7661 <blockquote
><pre
>
7662 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
7665 objectClass: dhcpServer
7666 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7667 </pre
></blockquote
>
7669 <p
>The content of the dhcpServiceDN attribute is next used to locate the
7670 subtree with DHCP configuration. The DHCP configuration subtree base
7671 is located using a base scope search with base
"cn=DHCP
7672 Config,dc=skole,dc=skolelinux,dc=no
" and filter
7673 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
7674 The search result is this entry:
</p
>
7676 <blockquote
><pre
>
7677 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7680 objectClass: dhcpService
7681 objectClass: dhcpOptions
7682 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
7683 dhcpStatements: ddns-update-style none
7684 dhcpStatements: authoritative
7685 dhcpOption: smtp-server code
69 = array of ip-address
7686 dhcpOption: www-server code
72 = array of ip-address
7687 dhcpOption: wpad-url code
252 = text
7688 </pre
></blockquote
>
7690 <p
>Next, the entire subtree is processed, one level at the time. When
7691 all the DHCP configuration is loaded, it is ready to receive requests.
7692 The subtree in Debian Edu contain objects with object classes
7693 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
7694 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
7695 and information about netmasks, dynamic range etc. Leaving out the
7696 details here because it is not relevant for the focus of my
7697 investigation, which is to see if it is possible to merge dns and dhcp
7698 related computer objects.
</p
>
7700 <p
>When a DHCP request come in, LDAP is searched for the MAC address
7701 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
7702 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
7703 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
7704 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
7707 <blockquote
><pre
>
7708 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7711 objectClass: dhcpHost
7712 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7713 dhcpStatements: fixed-address hostname
7714 </pre
></blockquote
>
7716 <p
>There is less flexiblity in the way LDAP searches are done here.
7717 The object classes need to have fixed names, and the configuration
7718 need to be stored in a fairly specific LDAP structure. On the
7719 positive side, the invidiual dhcpHost entires can be anywhere without
7720 the DN pointed to by the dhcpServer entries. The latter should make
7721 it possible to group all host entries in a subtree next to the
7722 configuration entries, and this subtree can also be shared with the
7723 DNS server if the schema proposed above is combined with the dhcpHost
7724 structural object class.
7726 <p
><strong
>Conclusion
</strong
></p
>
7728 <p
>The PowerDNS implementation seem to be very flexible when it come
7729 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
7730 come to the the LDAP structure, the
"strict
" mode is very flexible,
7731 allowing DNS objects to be stored anywhere under the base cn specified
7732 in the configuration.
</p
>
7734 <p
>The DHCP implementation on the other hand is very inflexible, both
7735 regarding which LDAP schemas to use and which LDAP structure to use.
7736 I guess one could implement ones own schema, as long as the
7737 objectclasses and attributes have the names used, but this do not
7738 really help when the DHCP subtree need to have a fairly fixed
7739 structure.
</p
>
7741 <p
>Based on the observed behaviour, I suspect a LDAP structure like
7742 this might work for Debian Edu:
</p
>
7744 <blockquote
><pre
>
7746 cn=machine-info (dhcpService) - dhcpServiceDN points here
7747 cn=dhcp (dhcpServer)
7748 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7749 cn=
10.0.2.0 (dhcpSubnet)
7750 cn=group1 (dhcpGroup/dhcpOptions)
7751 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7752 cn=
192.168.0.0 (dhcpSubnet)
7753 cn=group1 (dhcpGroup/dhcpOptions)
7754 ou=machines - PowerDNS base points here
7755 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7756 </pre
></blockquote
>
7758 <P
>This is not tested yet. If the DHCP server require the dhcpHost
7759 entries to be in the dhcpGroup subtrees, the entries can be stored
7760 there instead of a common machines subtree, and the PowerDNS base
7761 would have to be moved one level up to the machine-info subtree.
</p
>
7763 <p
>The combined object under the machines subtree would look something
7764 like this:
</p
>
7766 <blockquote
><pre
>
7767 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7770 objectClass: dhcpHost
7771 objectclass: domainrelatedobject
7772 objectclass: dnsDomainAux
7773 associateddomain: hostname.intern
7774 arecord:
10.11.12.13
7775 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7776 dhcpStatements: fixed-address hostname.intern
7777 </pre
></blockquote
>
7779 </p
>One could even add the LTSP configuration associated with a given
7780 machine, as long as the required attributes are available in a
7781 auxiliary object class.
</p
>
7786 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
7787 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
7788 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
7789 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
7790 <description><p
>For a while now, I have wanted to find a way to change the DNS and
7791 DHCP services in Debian Edu to use the same LDAP objects for a given
7792 computer, to avoid the possibility of having a inconsistent state for
7793 a computer in LDAP (as in DHCP but no DNS entry or the other way
7794 around) and make it easier to add computers to LDAP.
</p
>
7796 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
7797 information finally found a solution that seem to work.
</p
>
7799 <p
>The old setup required three LDAP objects for a given computer.
7800 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7801 we switch powerdns to use its strict LDAP method (ldap-method=strict
7802 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7803 merged into one while making it impossible to transfer the reverse map
7804 to a slave DNS server.
</p
>
7806 <p
>If we also replace the object class used to get the DNS related
7807 attributes to one allowing these attributes to be combined with the
7808 dhcphost object class, we can merge the DNS and DHCP entries into one.
7809 I
've written such object class in the dnsdomainaux.schema file (need
7810 proper OIDs, but that is a minor issue), and tested the setup. It
7811 seem to work.
</p
>
7813 <p
>With this test setup in place, we can get away with one LDAP object
7814 for both DNS and DHCP, and even the LTSP configuration I suggested in
7815 an earlier email. The combined LDAP object will look something like
7818 <blockquote
><pre
>
7819 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7821 objectClass: dhcphost
7822 objectclass: domainrelatedobject
7823 objectclass: dnsdomainaux
7824 associateddomain: hostname.intern
7825 arecord:
10.11.12.13
7826 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
7827 dhcpstatements: fixed-address hostname
7829 </pre
></blockquote
>
7831 <p
>The DNS server uses the associateddomain and arecord entries, while
7832 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7833 before asking DNS to resolve the fixed-adddress. LTSP will use
7834 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
7836 <p
>I am not yet sure if I can get the DHCP server to look for its
7837 dhcphost in a different location, to allow us to put the objects
7838 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
7839 that. If I can
't figure out a way to do that, we can still get rid of
7840 the hosts subtree and move all its content into the DHCP Config tree
7841 (which probably should be renamed to be more related to the new
7842 content. I suspect cn=dnsdhcp,ou=services or something like that
7843 might be a good place to put it.
</p
>
7845 <p
>If you want to help out with implementing this for Debian Edu,
7846 please contact us on debian-edu@lists.debian.org.
</p
>
7851 <title>Idea for storing LTSP configuration in LDAP
</title>
7852 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
7853 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
7854 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
7855 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
7856 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7857 clients, and that this can be used to fetch configuration from LDAP if
7858 Debian Edu choose to store configuration there.
</p
>
7860 <p
>Armed with this information, I got inspired and wrote a test module
7861 to get configuration from LDAP. The idea is to look up the MAC
7862 address of the client in LDAP, and look for attributes on the form
7863 ltspconfigsetting=value, and use this to export SETTING=value to the
7864 LTSP clients.
</p
>
7866 <p
>The goal is to be able to store the LTSP configuration attributes
7867 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
7868 allowing us to store all information about a computer in one place.
</p
>
7870 <p
>This is a untested draft implementation, and I welcome feedback on
7871 this approach. A real LDAP schema for the ltspClientAux objectclass
7872 need to be written. Comments, suggestions, etc?
</p
>
7874 <blockquote
><pre
>
7875 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7877 # Fetch LTSP client settings from LDAP based on MAC address
7879 # Uses ethernet address as stored in the dhcpHost objectclass using
7880 # the dhcpHWAddress attribute or ethernet address stored in the
7881 # ieee802Device objectclass with the macAddress attribute.
7883 # This module is written to be schema agnostic, and only depend on the
7884 # existence of attribute names.
7886 # The LTSP configuration variables are saved directly using a
7887 # ltspConfig prefix and uppercasing the rest of the attribute name.
7888 # To set the SERVER variable, set the ltspConfigServer attribute.
7890 # Some LDAP schema should be created with all the relevant
7891 # configuration settings. Something like this should work:
7893 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
7896 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7898 LDAPSERVER=$(debian-edu-ldapserver)
7899 if [
"$LDAPSERVER
" ] ; then
7900 LDAPBASE=$(debian-edu-ldapserver -b)
7901 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
7902 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
7903 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
7904 grep
'^ltspConfig
' | while read attr value ; do
7905 # Remove prefix and convert to upper case
7906 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
7907 # bass value on to clients
7908 eval
"$attr=$value; export $attr
"
7912 </pre
></blockquote
>
7914 <p
>I
'm not sure this shell construction will work, because I suspect
7915 the while block might end up in a subshell causing the variables set
7916 there to not show up in ltsp-config, but if that is the case I am sure
7917 the code can be restructured to make sure the variables are passed on.
7918 I expect that can be solved with some testing. :)
</p
>
7920 <p
>If you want to help out with implementing this for Debian Edu,
7921 please contact us on debian-edu@lists.debian.org.
</p
>
7923 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
7924 configuration in LDAP that was created around year
2000 by
7925 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
7926 Xperience, Inc.,
2000</a
>. I found its
7927 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
7928 personal home page over at redhat.com.
</p
>
7933 <title>jXplorer, a very nice LDAP GUI
</title>
7934 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
7935 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
7936 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
7937 <description><p
>Since
7938 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
7939 last post
</a
> about available LDAP tools in Debian, I was told about a
7940 LDAP GUI that is even better than luma. The java application
7941 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
7942 moving LDAP objects and subtrees using drag-and-drop, and can
7943 authenticate using Kerberos. I have only tested the Kerberos
7944 authentication, but do not have a LDAP setup allowing me to rewrite
7945 LDAP with my test user yet. It is
7946 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
7947 Debian
</a
> testing and unstable at the moment. The only problem I
7948 have with it is how it handle errors. If something go wrong, its
7949 non-intuitive behaviour require me to go through some query work list
7950 and remove the failing query. Nothing big, but very annoying.
</p
>
7955 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
7956 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
7957 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
7958 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
7959 <description><p
>Here is a short update on my
<a
7960 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
7961 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
7962 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
7963 not reporting the status for KDE, because the upgrade crashes when
7964 aptitude try because of missing conflicts
7965 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
7966 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
7968 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
7969 complete list of the installed packages. Based on this I see these
7970 differences when I did a test run today. As usual, I do not really
7971 know what the correct set of packages would be, but thought it best to
7972 publish the difference.
</p
>
7974 <p
>Installed using apt-get, missing with aptitude
</p
>
7976 <blockquote
><p
>
7977 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
7978 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
7979 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7980 libgtksourceview-common libpt-
1.10.10-plugins-alsa
7981 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7982 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7983 python-
4suite-xml python-eggtrayicon python-gtkhtml2
7984 python-gtkmozembed svgalibg1 xserver-xephyr zip
7985 </p
></blockquote
>
7987 <p
>Installed using apt-get, removed with aptitude
</p
>
7989 <blockquote
><p
>
7990 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7991 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7992 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
7993 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
7994 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
7995 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
7996 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7997 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7998 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7999 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
8000 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
8001 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
8002 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
8003 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
8004 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
8005 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
8006 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
8007 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
8008 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
8009 mysql-common swfdec-gnome totem-gstreamer wodim
8010 </p
></blockquote
>
8012 <p
>Installed using aptitude, missing with apt-get
</p
>
8014 <blockquote
><p
>
8015 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
8016 python-gnomekeyring python-wnck rhythmbox-plugins xorg
8017 xserver-xorg-input-all xserver-xorg-input-evdev
8018 xserver-xorg-input-kbd xserver-xorg-input-mouse
8019 xserver-xorg-input-synaptics xserver-xorg-video-all
8020 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
8021 xserver-xorg-video-chips xserver-xorg-video-cirrus
8022 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8023 xserver-xorg-video-glint xserver-xorg-video-i128
8024 xserver-xorg-video-i740 xserver-xorg-video-mach64
8025 xserver-xorg-video-mga xserver-xorg-video-neomagic
8026 xserver-xorg-video-nouveau xserver-xorg-video-nv
8027 xserver-xorg-video-r128 xserver-xorg-video-radeon
8028 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
8029 xserver-xorg-video-s3 xserver-xorg-video-s3virge
8030 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
8031 xserver-xorg-video-sis xserver-xorg-video-sisusb
8032 xserver-xorg-video-tdfx xserver-xorg-video-tga
8033 xserver-xorg-video-trident xserver-xorg-video-tseng
8034 xserver-xorg-video-vesa xserver-xorg-video-vmware
8035 xserver-xorg-video-voodoo
8036 </p
></blockquote
>
8038 <p
>Installed using aptitude, removed with apt-get
</p
>
8040 <blockquote
><p
>
8041 deskbar-applet xserver-xorg xserver-xorg-core
8042 xserver-xorg-input-wacom xserver-xorg-video-intel
8043 xserver-xorg-video-openchrome
8044 </p
></blockquote
>
8046 <p
>I was told on IRC that the xorg-xserver package was
8047 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
8048 in git
</a
> today to try to get apt-get to not remove xorg completely.
8049 No idea when it hits Squeeze, but when it does I hope it will reduce
8050 the difference somewhat.
8055 <title>LUMA, a very nice LDAP GUI
</title>
8056 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
8057 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
8058 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
8059 <description><p
>The last few days I have been looking into the status of the LDAP
8060 directory in Debian Edu, and in the process I started to miss a GUI
8061 tool to browse the LDAP tree. The only one I was able to find in
8062 Debian/Squeeze and Lenny is
8063 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
8064 be a great tool to get a overview of the current LDAP directory
8065 populated by default in Skolelinux. Thanks to it, I have been able to
8066 find empty and obsolete subtrees, misplaced objects and duplicate
8067 objects. It will be installed by default in Debian/Squeeze. If you
8068 are working with LDAP, give it a go. :)
</p
>
8070 <p
>I did notice one problem with it I have not had time to report to
8071 the BTS yet. There is no .desktop file in the package, so the tool do
8072 not show up in the Gnome and KDE menus, but only deep down in in the
8073 Debian submenu in KDE. I hope that can be fixed before Squeeze is
8076 <p
>I have not yet been able to get it to modify the tree yet. I would
8077 like to move objects and remove subtrees directly in the GUI, but have
8078 not found a way to do that with LUMA yet. So in the mean time, I use
8079 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
8081 <p
>If you have tips on other GUI tools for LDAP that might be useful
8082 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
8084 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
8085 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
8086 useful GUI alternative. It seem like a good tool, but is unmaintained
8087 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8088 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
8093 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
8094 <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>
8095 <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>
8096 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
8097 <description><p
>A while back, I
8098 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
8099 about the fact
</a
> that it is not possible with the provided schemas
8100 for storing DNS and DHCP information in LDAP to combine the two sets
8101 of information into one LDAP object representing a computer.
</p
>
8103 <p
>In the mean time, I discovered that a simple fix would be to make
8104 the dhcpHost object class auxiliary, to allow it to be combined with
8105 the dNSDomain object class, and thus forming one object for one
8106 computer when storing both DHCP and DNS information in LDAP.
</p
>
8108 <p
>If I understand this correctly, it is not safe to do this change
8109 without also changing the assigned number for the object class, and I
8110 do not know enough about LDAP schema design to do that properly for
8111 Debian Edu.
</p
>
8113 <p
>Anyway, for future reference, this is how I believe we could change
8115 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
8116 schema
</a
> to solve at least part of the problem with the LDAP schemas
8117 available today from IETF.
</p
>
8120 --- dhcp.schema (revision
65192)
8121 +++ dhcp.schema (working copy)
8123 objectclass (
2.16.840.1.113719.1.203.6.6
8124 NAME
'dhcpHost
'
8125 DESC
'This represents information about a particular client
'
8129 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8130 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
8133 <p
>I very much welcome clues on how to do this properly for Debian
8134 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8135 package, and should thus be free to rewrite it as we see fit.
</p
>
8137 <p
>If you want to help out with implementing this for Debian Edu,
8138 please contact us on debian-edu@lists.debian.org.
</p
>
8143 <title>Calling tasksel like the installer, while still getting useful output
</title>
8144 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
8145 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
8146 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
8147 <description><p
>A few times I have had the need to simulate the way tasksel
8148 installs packages during the normal debian-installer run. Until now,
8149 I have ended up letting tasksel do the work, with the annoying problem
8150 of not getting any feedback at all when something fails (like a
8151 conffile question from dpkg or a download that fails), using code like
8154 <blockquote
><pre
>
8155 export DEBIAN_FRONTEND=noninteractive
8156 tasksel --new-install
8157 </pre
></blockquote
>
8159 This would invoke tasksel, let its automatic task selection pick the
8160 tasks to install, and continue to install the requested tasks without
8161 any output what so ever.
8163 Recently I revisited this problem while working on the automatic
8164 package upgrade testing, because tasksel would some times hang without
8165 any useful feedback, and I want to see what is going on when it
8166 happen. Then it occured to me, I can parse the output from tasksel
8167 when asked to run in test mode, and use that aptitude command line
8168 printed by tasksel then to simulate the tasksel run. I ended up using
8171 <blockquote
><pre
>
8172 export DEBIAN_FRONTEND=noninteractive
8173 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
8175 </pre
></blockquote
>
8177 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
8178 --without-recommends -o APT::Install-Recommends=no -y install
8179 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
8180 ~pimportant
</tt
>", which will install the gnome desktop task, the
8181 laptop task and all packages with priority standard , required and
8182 important, just like tasksel would have done it during
8183 installation.
</p
>
8185 <p
>A better approach is probably to extend tasksel to be able to
8186 install packages without using debconf-apt-progress, for use cases
8187 like this.
</p
>
8192 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
8193 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
8194 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
8195 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
8196 <description><p
>My
8197 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
8198 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
8199 finally made the upgrade logs available from
8200 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
8201 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
8202 apt and aptitude, and found their differences interesting. This time
8203 I will only focus on their removal plans.
</p
>
8205 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
8206 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
8207 surprising part is that it want to remove xorg and all
8208 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
8209 sure why. When asking aptitude to do the same, it want to remove
129
8210 packages, but most of them are library packages I suspect are no
8211 longer needed. Both of them want to remove bluetooth packages, which
8212 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
8214 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
8215 which seem like a bad idea and xorg the same way as with Gnome. Asking
8216 aptitude for the same, it wants to remove
192 packages, none which are
8217 too surprising.
</p
>
8219 <p
>I guess the removal of xorg during upgrades should be investigated
8220 and avoided, and perhaps others as well. Here are the complete list
8221 of planned removals. The complete logs is available from the URL
8222 above. Note if you want to repeat these tests, that the upgrade test
8223 for kde+apt-get hung in the tasksel setup because of dpkg asking
8224 conffile questions. No idea why. I worked around it by using
8225 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
8228 <p
><b
>apt-get gnome
72</b
>
8229 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
8230 gnome-desktop-environment gnome-network-admin gtkhtml3.14
8231 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
8232 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
8233 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
8234 serpentine swfdec-mozilla update-manager xorg xserver-xorg
8235 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8236 xserver-xorg-input-kbd xserver-xorg-input-mouse
8237 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8238 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8239 xserver-xorg-video-ati xserver-xorg-video-chips
8240 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8241 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8242 xserver-xorg-video-glint xserver-xorg-video-i128
8243 xserver-xorg-video-i740 xserver-xorg-video-imstt
8244 xserver-xorg-video-intel xserver-xorg-video-mach64
8245 xserver-xorg-video-mga xserver-xorg-video-neomagic
8246 xserver-xorg-video-nsc xserver-xorg-video-nv
8247 xserver-xorg-video-openchrome xserver-xorg-video-r128
8248 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8249 xserver-xorg-video-rendition xserver-xorg-video-s3
8250 xserver-xorg-video-s3virge xserver-xorg-video-savage
8251 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8252 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8253 xserver-xorg-video-tga xserver-xorg-video-trident
8254 xserver-xorg-video-tseng xserver-xorg-video-v4l
8255 xserver-xorg-video-vesa xserver-xorg-video-vga
8256 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
8257 xulrunner-
1.9-gnome-support
</p
>
8259 <p
><b
>aptitude gnome
129</b
>
8261 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
8262 djvulibre-desktop finger gnome-app-install gnome-mount
8263 gnome-network-admin gnome-spell gnome-vfs-obexftp
8264 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
8265 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
8266 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
8267 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
8268 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
8269 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
8270 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
8271 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
8272 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
8273 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
8274 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
8275 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
8276 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
8277 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
8278 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
8279 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
8280 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
8281 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
8282 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
8283 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
8284 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
8285 openoffice.org-writer2latex openssl-blacklist p7zip
8286 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
8287 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
8288 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
8289 swfdec-mozilla totem-gstreamer update-manager wodim
8290 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8291 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8294 <p
><b
>apt-get kde
82</b
>
8296 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
8297 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
8298 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
8299 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
8300 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
8301 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
8302 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8303 xserver-xorg-input-kbd xserver-xorg-input-mouse
8304 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8305 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8306 xserver-xorg-video-ati xserver-xorg-video-chips
8307 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8308 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8309 xserver-xorg-video-glint xserver-xorg-video-i128
8310 xserver-xorg-video-i740 xserver-xorg-video-imstt
8311 xserver-xorg-video-intel xserver-xorg-video-mach64
8312 xserver-xorg-video-mga xserver-xorg-video-neomagic
8313 xserver-xorg-video-nsc xserver-xorg-video-nv
8314 xserver-xorg-video-openchrome xserver-xorg-video-r128
8315 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8316 xserver-xorg-video-rendition xserver-xorg-video-s3
8317 xserver-xorg-video-s3virge xserver-xorg-video-savage
8318 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8319 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8320 xserver-xorg-video-tga xserver-xorg-video-trident
8321 xserver-xorg-video-tseng xserver-xorg-video-v4l
8322 xserver-xorg-video-vesa xserver-xorg-video-vga
8323 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
8325 <p
><b
>aptitude kde
192</b
>
8326 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
8327 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
8328 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
8329 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
8330 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8331 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
8332 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
8333 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8334 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
8335 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
8336 kghostview khelpcenter khexedit kiconedit kitchensync klatin
8337 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
8338 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
8339 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
8340 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
8341 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
8342 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
8343 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8344 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
8345 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
8346 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8347 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
8348 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
8349 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
8350 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8351 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
8352 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
8353 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
8354 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
8355 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
8356 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
8357 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
8358 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
8359 texlive-common texlive-doc-base texlive-fonts-recommended
8360 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8361 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8362 xulrunner-
1.9</p
>
8368 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
8369 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
8370 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
8371 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
8372 <description><p
>The last few days I have done some upgrade testing in Debian, to
8373 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
8374 have been discovered and reported in the process
8375 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
8376 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
8377 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
8378 kdebase-workspace-data), and to get a more regular testing going on, I
8379 am working on a script to automate the test.
</p
>
8381 <p
>The idea is to create a Lenny chroot and use tasksel to install a
8382 Gnome or KDE desktop installation inside the chroot before upgrading
8383 it. To ensure no services are started in the chroot, a policy-rc.d
8384 script is inserted. To make sure tasksel believe it is to install a
8385 desktop on a laptop, the tasksel tests are replaced in the chroot
8386 (only acceptable because this is a throw-away chroot).
</p
>
8388 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
8389 currently always fail because udev refuses to upgrade with the kernel
8390 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
8391 is created. The bug report
8392 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
8393 this problem do not trigger in a chroot, but I touch the file anyway
8394 to make sure the upgrade go well. Testing on virtual and real
8395 hardware have failed me because of udev so far, and creating this file
8396 do the trick in such settings anyway. This is a
8397 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
8398 issue
</a
> and the current udev behaviour is intended by the udev
8399 maintainer because he lack the resources to rewrite udev to keep
8400 working with old kernels or something like that. I really wish the
8401 udev upstream would keep udev backwards compatible, to avoid such
8402 upgrade problem, but given that they fail to do so, I guess
8403 documenting the way out of this mess is the best option we got for
8404 Debian Squeeze.
</p
>
8406 <p
>Anyway, back to the task at hand, testing upgrades. This test
8407 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
8410 <blockquote
><pre
>
8414 if [
"$
1" ] ; then
8423 exec
&lt; /dev/null
8425 mirror=http://ftp.skolelinux.org/debian
8426 tmpdir=chroot-$from-upgrade-$to-$desktop
8428 debootstrap $from $tmpdir $mirror
8429 chroot $tmpdir aptitude update
8430 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
8434 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
8438 mount -t proc proc $tmpdir/proc
8439 # Make sure proc is unmounted also on failure
8440 trap exit_cleanup EXIT INT
8442 chroot $tmpdir aptitude -y install debconf-utils
8444 # Make sure tasksel autoselection trigger. It need the test scripts
8445 # to return the correct answers.
8446 echo tasksel tasksel/desktop multiselect $desktop | \
8447 chroot $tmpdir debconf-set-selections
8449 # Include the desktop and laptop task
8450 for test in desktop laptop ; do
8451 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
8455 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
8458 DEBIAN_FRONTEND=noninteractive
8459 DEBIAN_PRIORITY=critical
8460 export DEBIAN_FRONTEND DEBIAN_PRIORITY
8461 chroot $tmpdir tasksel --new-install
8463 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
8464 chroot $tmpdir aptitude update
8465 touch $tmpdir/etc/udev/kernel-upgrade
8466 chroot $tmpdir aptitude -y dist-upgrade
8468 </pre
></blockquote
>
8470 <p
>I suspect it would be useful to test upgrades with both apt-get and
8471 with aptitude, but I have not had time to look at how they behave
8472 differently so far. I hope to get a cron job running to do the test
8473 regularly and post the result on the web. The Gnome upgrade currently
8474 work, while the KDE upgrade fail because of the bug in
8475 kdebase-workspace-data
</p
>
8477 <p
>I am not quite sure what kind of extract from the huge upgrade logs
8478 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
8479 post, so I will refrain from trying. I can report that for Gnome,
8480 aptitude report
760 packages upgraded,
448 newly installed,
129 to
8481 remove and
1 not upgraded and
1024MB need to be downloaded while for
8482 KDE the same numbers are
702 packages upgraded,
507 newly installed,
8483 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
8485 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
8486 is able to migrate to dependency based boot sequencing and parallel
8487 booting without a hitch. Was unsure if there were still bugs with
8488 packages failing to clean up their obsolete init.d script during
8489 upgrades, and no such problem seem to affect the Gnome desktop+laptop
8495 <title>Upstart or sysvinit - as init.d scripts see it
</title>
8496 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
8497 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
8498 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
8499 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
8500 scripts to migrate (some of) their operations to upstart job while
8501 keeping the init.d for hurd and kfreebsd. The packages with such
8502 needs will need a way to get their init.d scripts to behave
8503 differently when used with sysvinit and with upstart. Because of
8504 this, I had a look at the environment variables set when a init.d
8505 script is running under upstart, and when it is not.
</p
>
8507 <p
>With upstart, I notice these environment variables are set when a
8508 script is started from rcS.d/ (ignoring some irrelevant ones like
8511 <blockquote
><pre
>
8517 UPSTART_EVENTS=startup
8519 UPSTART_JOB=rc-sysinit
8520 </pre
></blockquote
>
8522 <p
>With sysvinit, these environment variables are set for the same
8525 <blockquote
><pre
>
8526 INIT_VERSION=sysvinit-
2.88
8531 </pre
></blockquote
>
8533 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
8534 sysvinit are not set by upstart. Not sure if it is intentional or not
8535 to not be compatible with sysvinit in this regard.
</p
>
8537 <p
>For scripts needing to behave differently when upstart is used,
8538 looking for the UPSTART_JOB environment variable seem to be a good
8544 <title>A manual for standards wars...
</title>
8545 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
8546 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
8547 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
8548 <description><p
>Via the
8549 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
8550 of Rob Weir
</a
> I came across the very interesting essay named
8551 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
8552 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
8553 following the standards wars of today.
</p
>
8558 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
8559 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
8560 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
8561 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
8562 <description><p
>When using sitesummary at a site to track machines, it is possible
8563 to get a list of the machine types in use thanks to the DMI
8564 information extracted from each machine. The script to do so is
8565 included in the sitesummary package, and here is example output from
8566 the Skolelinux build servers:
</p
>
8568 <blockquote
><pre
>
8569 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
8571 Dell Computer Corporation
1
8574 eserver xSeries
345 -[
8670M1X]-
1
8578 </pre
></blockquote
>
8580 <p
>The quality of the report depend on the quality of the DMI tables
8581 provided in each machine. Here there are Intel machines without model
8582 information listed with Intel as vendor and no model, and virtual Xen
8583 machines listed as [no-dmi-info]. One can add -l as a command line
8584 option to list the individual machines.
</p
>
8586 <p
>A larger list is
8587 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
8588 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
8589 provide the basic sitesummary report publicly. In their report there
8590 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
8591 their machines, and as sitesummary is available in both distributions,
8592 it is trivial to get all of them to report to the same central
8593 collector.
</p
>
8598 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
8599 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
8600 <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>
8601 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
8602 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
8603 start at boot when an NVidia video card is used is handled. The
8604 problem seem to be that the nvidia X.org driver uses a long time to
8605 initialize, and this duration is longer than kdm is configured to
8608 <p
>I came across two bugs related to this issue,
8609 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
8610 against initscripts and passed on to nvidia-glx when it became obvious
8611 that the nvidia drivers were involved, and
8612 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
8613 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
8615 <p
>To me, it seem that no-one is interested in actually solving the
8616 problem nvidia video card owners experience and make sure the Debian
8617 distribution work out of the box for these users. The nvidia driver
8618 maintainers expect kdm to be set up to wait longer, while kdm expect
8619 the nvidia driver maintainers to fix the driver to start faster, and
8620 while they wait for each other I guess the users end up switching to a
8621 distribution that work for them. I have no idea what the solution is,
8622 but I am pretty sure that waiting for each other is not it.
</p
>
8624 <p
>I wonder why we end up handling bugs this way.
</p
>
8629 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
8630 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
8631 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
8632 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
8633 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
8634 The feature seem to hold up pretty well, but three fairly serious
8635 issues are known and should be solved:
8639 <li
>The wicd package seen to
8640 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
8641 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
8642 parallel booting is enabled. No idea why, but the wicd maintainer
8643 seem to be on the case.
</li
>
8645 <li
>The nvidia X driver seem to
8646 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
8647 triggered more easily when parallel booting is in effect. The
8648 maintainer is on the case.
</li
>
8650 <li
>The sysv-rc package fail to properly enable dependency based boot
8651 sequencing (the shutdown is broken) when old file-rc users
8652 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
8653 sysv-rc. One way to solve it would be for file-rc to create
8654 /etc/init.d/.legacy-bootordering, and another is to try to make
8655 sysv-rc more robust. Will investigate some more and probably upload a
8656 workaround in sysv-rc to help those trying to move from file-rc to
8657 sysv-rc get a working shutdown.
</li
>
8659 </ul
></p
>
8661 <p
>All in all not many surprising issues, and all of them seem
8662 solvable before Squeeze is released. In addition to these there are
8663 some packages with bugs in their dependencies and run level settings,
8664 which I expect will be fixed in a reasonable time span.
</p
>
8666 <p
>If you report any problems with dependencies in init.d scripts to
8667 the BTS, please usertag the report to get it to show up at
8668 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8669 list of usertagged bugs related to this
</a
>.
</p
>
8671 <p
>Update: Correct bug number to file-rc issue.
</p
>
8676 <title>More flexible firmware handling in debian-installer
</title>
8677 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
8678 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
8679 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
8680 <description><p
>After a long break from debian-installer development, I finally
8681 found time today to return to the project. Having to spend less time
8682 working dependency based boot in debian, as it is almost complete now,
8683 definitely helped freeing some time.
</p
>
8685 <p
>A while back, I ran into a problem while working on Debian Edu. We
8686 include some firmware packages on the Debian Edu CDs, those needed to
8687 get disk and network controllers working. Without having these
8688 firmware packages available during installation, it is impossible to
8689 install Debian Edu on the given machine, and because our target group
8690 are non-technical people, asking them to provide firmware packages on
8691 an external medium is a support pain. Initially, I expected it to be
8692 enough to include the firmware packages on the CD to get
8693 debian-installer to find and use them. This proved to be wrong.
8694 Next, I hoped it was enough to symlink the relevant firmware packages
8695 to some useful location on the CD (tried /cdrom/ and
8696 /cdrom/firmware/). This also proved to not work, and at this point I
8697 found time to look at the debian-installer code to figure out what was
8698 going to work.
</p
>
8700 <p
>The firmware loading code is in the hw-detect package, and a closer
8701 look revealed that it would only look for firmware packages outside
8702 the installation media, so the CD was never checked for firmware
8703 packages. It would only check USB sticks, floppies and other
8704 "external
" media devices. Today I changed it to also look in the
8705 /cdrom/firmware/ directory on the mounted CD or DVD, which should
8706 solve the problem I ran into with Debian edu. I also changed it to
8707 look in /firmware/, to make sure the installer also find firmware
8708 provided in the initrd when booting the installer via PXE, to allow us
8709 to provide the same feature in the PXE setup included in Debian
8712 <p
>To make sure firmware deb packages with a license questions are not
8713 activated without asking if the license is accepted, I extended
8714 hw-detect to look for preinst scripts in the firmware packages, and
8715 run these before activating the firmware during installation. The
8716 license question is asked using debconf in the preinst, so this should
8717 solve the issue for the firmware packages I have looked at so far.
</p
>
8719 <p
>If you want to discuss the details of these features, please
8720 contact us on debian-boot@lists.debian.org.
</p
>
8725 <title>Parallellized boot is now the default in Debian/unstable
</title>
8726 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
8727 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
8728 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
8729 <description><p
>Since this evening, parallel booting is the default in
8730 Debian/unstable for machines using dependency based boot sequencing.
8731 Apparently the testing of concurrent booting has been wider than
8732 expected, if I am to believe the
8733 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
8734 on debian-devel@
</a
>, and I concluded a few days ago to move forward
8735 with the feature this weekend, to give us some time to detect any
8736 remaining problems before Squeeze is frozen. If serious problems are
8737 detected, it is simple to change the default back to sequential boot.
8738 The upload of the new sysvinit package also activate a new upstream
8741 More information about
8742 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8743 based boot sequencing
</a
> is available from the Debian wiki. It is
8744 currently possible to disable parallel booting when one run into
8745 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
8747 <blockquote
><pre
>
8749 </pre
></blockquote
>
8751 <p
>If you report any problems with dependencies in init.d scripts to
8752 the BTS, please usertag the report to get it to show up at
8753 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8754 list of usertagged bugs related to this
</a
>.
</p
>
8759 <title>Sitesummary tip: Listing MAC address of all clients
</title>
8760 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
8761 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
8762 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
8763 <description><p
>In the recent Debian Edu versions, the
8764 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
8765 system
</a
> is used to keep track of the machines in the school
8766 network. Each machine will automatically report its status to the
8767 central server after boot and once per night. The network setup is
8768 also reported, and using this information it is possible to get the
8769 MAC address of all network interfaces in the machines. This is useful
8770 to update the DHCP configuration.
</p
>
8772 <p
>To give some idea how to use sitesummary, here is a one-liner to
8773 ist all MAC addresses of all machines reporting to sitesummary. Run
8774 this on the collector host:
</p
>
8776 <blockquote
><pre
>
8777 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
8778 </pre
></blockquote
>
8780 <p
>This will list all MAC addresses assosiated with all machine, one
8781 line per machine and with space between the MAC addresses.
</p
>
8783 <p
>To allow system administrators easier job at adding static DHCP
8784 addresses for hosts, it would be possible to extend this to fetch
8785 machine information from sitesummary and update the DHCP and DNS
8786 tables in LDAP using this information. Such tool is unfortunately not
8787 written yet.
</p
>
8792 <title>systemd, an interesting alternative to upstart
</title>
8793 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
8794 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
8795 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
8796 <description><p
>The last few days a new boot system called
8797 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
8799 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
8801 to the free software world. I have not yet had time to play around
8802 with it, but it seem to be a very interesting alternative to
8803 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
8804 a good alternative for Debian when we are able to switch to an event
8805 based boot system. Tollef is
8806 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
8807 systemd into Debian, and I look forward to seeing how well it work. I
8808 like the fact that systemd handles init.d scripts with dependency
8809 information natively, allowing them to run in parallel where upstart
8810 at the moment do not.
</p
>
8812 <p
>Unfortunately do systemd have the same problem as upstart regarding
8813 platform support. It only work on recent Linux kernels, and also need
8814 some new kernel features enabled to function properly. This means
8815 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8816 system. Not sure how that will be handled if systemd proves to be the
8817 way forward.
</p
>
8819 <p
>In the mean time, based on the
8820 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
8821 on debian-devel@
</a
> regarding parallel booting in Debian, I have
8822 decided to enable full parallel booting as the default in Debian as
8823 soon as possible (probably this weekend or early next week), to see if
8824 there are any remaining serious bugs in the init.d dependencies. A
8825 new version of the sysvinit package implementing this change is
8826 already in experimental. If all go well, Squeeze will be released
8827 with parallel booting enabled by default.
</p
>
8832 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
8833 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
8834 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
8835 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
8836 <description><p
>These days, the init.d script dependencies in Squeeze are quite
8837 complete, so complete that it is actually possible to run all the
8838 init.d scripts in parallell based on these dependencies. If you want
8839 to test your Squeeze system, make sure
8840 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8841 based boot sequencing
</a
> is enabled, and add this line to
8842 /etc/default/rcS:
</p
>
8844 <blockquote
><pre
>
8845 CONCURRENCY=makefile
8846 </pre
></blockquote
>
8848 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
8849 scripts in parallel using the dependency information stored in
8850 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8851 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8852 to try to start the kdm and gdm scripts as early as possible, and will
8853 start the facilities required by kdm or gdm as early as possible to
8854 make this happen.
</p
>
8856 <p
>Give it a try, and see if you like the result. If some services
8857 fail to start properly, it is most likely because they have incomplete
8858 init.d script dependencies in their startup script (or some of their
8859 dependent scripts have incomplete dependencies). Report bugs and get
8860 the package maintainers to fix it. :)
</p
>
8862 <p
>Running scripts in parallel could be the default in Debian when we
8863 manage to get the init.d script dependencies complete and correct. I
8864 expect we will get there in Squeeze+
1, if we get manage to test and
8865 fix the remaining issues.
</p
>
8867 <p
>If you report any problems with dependencies in init.d scripts to
8868 the BTS, please usertag the report to get it to show up at
8869 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8870 list of usertagged bugs related to this
</a
>.
</p
>
8875 <title>Debian has switched to dependency based boot sequencing
</title>
8876 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
8877 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
8878 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
8879 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
8880 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
8881 have been migrated to using dependency based boot sequencing. This
8882 conclude work me and others have been doing for the last three days.
8883 It feels great to see this finally part of the default Debian
8884 installation. Now we just need to weed out the last few problems that
8885 are bound to show up, to get everything ready for Squeeze.
</p
>
8887 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
8888 fixing the more fundamental problem of handing the event based
8889 non-predictable kernel in the early boot.
</p
>
8894 <title>Taking over sysvinit development
</title>
8895 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
8896 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
8897 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
8898 <description><p
>After several years of frustration with the lack of activity from
8899 the existing sysvinit upstream developer, I decided a few weeks ago to
8900 take over the package and become the new upstream. The number of
8901 patches to track for the Debian package was becoming a burden, and the
8902 lack of synchronization between the distribution made it hard to keep
8903 the package up to date.
</p
>
8905 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8906 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
8907 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
8908 and Fedora), based on the patches currently in use in these
8909 distributions. We Debian maintainers plan to move to this tarball as
8910 the new upstream as soon as we find time to do the merge. Since the
8911 new tarball was created, we agreed with Werner at SuSe to make a new
8912 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
8913 development there. The project is registered and currently waiting
8914 for approval by the Savannah administrators, and as soon as it is
8915 approved, we will import the old versions from svn and continue
8916 working on the future release.
</p
>
8918 <p
>It is a bit ironic that this is done now, when some of the involved
8919 distributions are moving to upstart as a syvinit replacement.
</p
>
8924 <title>Debian boots quicker and quicker
</title>
8925 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
8926 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
8927 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
8928 <description><p
>I spent Monday and tuesday this week in London with a lot of the
8929 people involved in the boot system on Debian and Ubuntu, to see if we
8930 could find more ways to speed up the boot system. This was an Ubuntu
8932 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
8933 gathering
</a
>. It was quite productive. We also discussed the future
8934 of boot systems, and ways to handle the increasing number of boot
8935 issues introduced by the Linux kernel becoming more and more
8936 asynchronous and event base. The Ubuntu approach using udev and
8937 upstart might be a good way forward. Time will show.
</p
>
8939 <p
>Anyway, there are a few ways at the moment to speed up the boot
8940 process in Debian. All of these should be applied to get a quick
8945 <li
>Use dash as /bin/sh.
</li
>
8947 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
8948 clock is in UTC.
</li
>
8950 <li
>Install and activate the insserv package to enable
8951 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8952 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
8956 These points are based on the Google summer of code work done by
8957 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
8960 <p
>Support for makefile-style concurrency during boot was uploaded to
8961 unstable yesterday. When we tested it, we were able to cut
6 seconds
8962 from the boot sequence. It depend on very correct dependency
8963 declaration in all init.d scripts, so I expect us to find edge cases
8964 where the dependences in some scripts are slightly wrong when we start
8965 using this.
</p
>
8967 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8968 introduced by Raphael Geissert today, one that could affect the
8969 startup speed as well. Instead of starting some scripts concurrently
8970 from rcS.d/ and another set of scripts from rc2.d/, it would be
8971 possible to run a of them in the same process. A quick way to test
8972 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
8973 insserv
'. Will need to test if that work. :)
</p
>
8978 <title>BSAs påstander om piratkopiering møter motstand
</title>
8979 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
8980 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
8981 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
8982 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
8983 programvareselskapene som Microsoft og Apple, publisert en rapport der
8984 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8985 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8987 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
8988 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
8989 dagene. Et spesielt interessant kommentar fra Sverige,
8990 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
8991 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
8994 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
8995 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8996 företag.
"Man bör nog kanske inte se de här siffrorna som helt
8997 exakta
", säger BSAs Sverigechef John Hugosson.
9000 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
9001 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
9002 piracy figures need a shot of reality
</a
> og
<a
9003 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
9004 Copyright Treaty Work?
</a
></p
>
9006 <p
>Fant lenkene via
<a
9007 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
9008 på Slashdot
</a
>.
</p
>
9013 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
9014 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
9015 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
9016 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
9017 <description><p
>Kom over
9018 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
9019 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
9020 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
9021 jobber til daglig. En rask opptelling forteller meg at vi har
490
9022 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
9023 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
9024 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
9029 <title>Kryptert harddisk - naturligvis
</title>
9030 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
9031 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
9032 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
9033 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
9034 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
9035 når en tar tap av arbeidstid, fortrolige dokumenter,
9036 personopplysninger og alt annet det innebærer. Det er ingen tvil om
9037 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
9038 til at jeg har kryptert harddisken på både kontormaskinen og min
9039 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
9040 komme på avveie, den første informasjon relatert til jobben min ved
9041 Universitetet i Oslo, og den andre relatert til blant annet
9042 foreningsarbeide. Kryptering av diskene gjør at det er lite
9043 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
9044 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
9045 og en reboot vil gjøre at de ber om passord før de vil starte opp.
9046 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
9047 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
9048 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
9049 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
9050 det er gjort slik jeg gjør det er minimale, og gevinstene er
9051 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
9052 maskinen reinstalleres og alt er tapt.
</p
>
9054 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
9055 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
9056 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
9057 er for min del høyere enn gevinsten. Jeg tror oddsene for at
9058 f.eks. etteretningsorganisasjoner har glede av å titte på mine
9059 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
9060 gjøre det vanskeligere for angripere med kompetanse og ressurser er
9061 betydelige.
</p
>
9066 <title>Two projects that have improved the quality of free software a lot
</title>
9067 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
9068 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
9069 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
9070 <description><p
>There are two software projects that have had huge influence on the
9071 quality of free software, and I wanted to mention both in case someone
9072 do not yet know them.
</p
>
9074 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
9075 tool to detect and expose errors in the memory handling of programs.
9076 It is easy to use, all one need to do is to run
'valgrind program
',
9077 and it will report any problems on stdout. It is even better if the
9078 program include debug information. With debug information, it is able
9079 to report the source file name and line number where the problem
9080 occurs. It can report things like
'reading past memory block in file
9081 X line N, the memory block was allocated in file Y, line M
', and
9082 'using uninitialised value in control logic
'. This tool has made it
9083 trivial to investigate reproducible crash bugs in programs, and have
9084 reduced the number of this kind of bugs in free software a lot.
9086 <p
>The second one is
9087 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
9088 a source code checker. It is able to process the source of a program
9089 and find problems in the logic without running the program. It
9090 started out as the Stanford Checker and became well known when it was
9091 used to find bugs in the Linux kernel. It is now a commercial tool
9092 and the company behind it is running
9093 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
9094 free software community, where a lot of free software projects get
9095 their source checked for free. Several thousand defects have been
9096 found and fixed so far. It can find errors like
'lock L taken in file
9097 X line N is never released if exiting in line M
', or
'the code in file
9098 Y lines O to P can never be executed
'. The projects included in the
9099 community service project have managed to get rid of a lot of
9100 reliability problems thanks to Coverity.
</p
>
9102 <p
>I believe tools like this, that are able to automatically find
9103 errors in the source, are vital to improve the quality of software and
9104 make sure we can get rid of the crashing and failing software we are
9105 surrounded by today.
</p
>
9110 <title>No patch is not better than a useless patch
</title>
9111 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
9112 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
9113 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
9114 <description><p
>Julien Blache
9115 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
9116 patch is better than a useless patch
</a
>. I completely disagree, as a
9117 patch allow one to discuss a concrete and proposed solution, and also
9118 prove that the issue at hand is important enough for someone to spent
9119 time on fixing it. No patch do not provide any of these positive
9120 properties.
</p
>
9125 <title>Standardize on protocols and formats, not vendors and applications
</title>
9126 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
9127 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
9128 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
9129 <description><p
>Where I work at the University of Oslo, one decision stand out as a
9130 very good one to form a long lived computer infrastructure. It is the
9131 simple one, lost by many in todays computer industry: Standardize on
9132 open network protocols and open exchange/storage formats, not applications.
9133 Applications come and go, while protocols and files tend to stay, and
9134 thus one want to make it easy to change application and vendor, while
9135 avoiding conversion costs and locking users to a specific platform or
9136 application.
</p
>
9138 <p
>This approach make it possible to replace the client applications
9139 independently of the server applications. One can even allow users to
9140 use several different applications as long as they handle the selected
9141 protocol and format. In the normal case, only one client application
9142 is recommended and users only get help if they choose to use this
9143 application, but those that want to deviate from the easy path are not
9144 blocked from doing so.
</p
>
9146 <p
>It also allow us to replace the server side without forcing the
9147 users to replace their applications, and thus allow us to select the
9148 best server implementation at any moment, when scale and resouce
9149 requirements change.
</p
>
9151 <p
>I strongly recommend standardizing - on open network protocols and
9152 open formats, but I would never recommend standardizing on a single
9153 application that do not use open network protocol or open formats.
</p
>
9158 <title>Returning from Skolelinux developer gathering
</title>
9159 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
9160 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
9161 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
9162 <description><p
>I
'm sitting on the train going home from this weekends Debian
9163 Edu/Skolelinux development gathering. I got a bit done tuning the
9164 desktop, and looked into the dynamic service location protocol
9165 implementation avahi. It look like it could be useful for us. Almost
9166 30 people participated, and I believe it was a great environment to
9167 get to know the Skolelinux system. Walter Bender, involved in the
9168 development of the Sugar educational platform, presented his stuff and
9169 also helped me improve my OLPC installation. He also showed me that
9170 his Turtle Art application can be used in standalone mode, and we
9171 agreed that I would help getting it packaged for Debian. As a
9172 standalone application it would be great for Debian Edu. We also
9173 tried to get the video conferencing working with two OLPCs, but that
9174 proved to be too hard for us. The application seem to need more work
9175 before it is ready for me. I look forward to getting home and relax
9181 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
9182 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
9183 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
9184 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
9185 <description><p
>The state of standardized LDAP schemas on Linux is far from
9186 optimal. There is RFC
2307 documenting one way to store NIS maps in
9187 LDAP, and a modified version of this normally called RFC
2307bis, with
9188 some modifications to be compatible with Active Directory. The RFC
9189 specification handle the content of a lot of system databases, but do
9190 not handle DNS zones and DHCP configuration.
</p
>
9192 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
9193 we would like to store information about users, SMB clients/hosts,
9194 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
9195 and LTSP configuration in LDAP. These objects have a lot in common,
9196 but with the current LDAP schemas it is not possible to have one
9197 object per entity. For example, one need to have at least three LDAP
9198 objects for a given computer, one with the SMB related stuff, one with
9199 DNS information and another with DHCP information. The schemas
9200 provided for DNS and DHCP are impossible to combine into one LDAP
9201 object. In addition, it is impossible to implement quick queries for
9202 netgroup membership, because of the way NIS triples are implemented.
9203 It just do not scale. I believe it is time for a few RFC
9204 specifications to cleam up this mess.
</p
>
9206 <p
>I would like to have one LDAP object representing each computer in
9207 the network, and this object can then keep the SMB (ie host key), DHCP
9208 (mac address/name) and DNS (name/IP address) settings in one place.
9209 It need to be efficently stored to make sure it scale well.
</p
>
9211 <p
>I would also like to have a quick way to map from a user or
9212 computer and to the net group this user or computer is a member.
</p
>
9214 <p
>Active Directory have done a better job than unix heads like myself
9215 in this regard, and the unix side need to catch up. Time to start a
9216 new IETF work group?
</p
>
9221 <title>Endelig er Debian Lenny gitt ut
</title>
9222 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
9223 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
9224 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
9225 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
9226 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
9227 Et langt steg videre for Debian-prosjektet, og en rekke nye
9228 programpakker blir nå tilgjengelig for de av oss som bruker den
9229 stabile utgaven av Debian. Neste steg er nå å få
9230 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
9231 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
9232 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
9233 slippes løs på skolene. Takk til alle debian-utviklerne som har
9234 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
9235 bootsekvens tilgjengelig i stabil utgave, vha pakken
9236 <tt
>insserv
</tt
>.
</p
>
9241 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
9242 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
9243 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
9244 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
9245 <description><p
>This weekend we had a small developer gathering for Debian Edu in
9246 Oslo. Most of Saturday was used for the general assemly for the
9247 member organization, but the rest of the weekend I used to tune the
9248 LTSP installation. LTSP now work out of the box on the
10-network.
9249 Acer Aspire One proved to be a very nice thin client, with both
9250 screen, mouse and keybard in a small box. Was working on getting the
9251 diskless workstation setup configured out of the box, but did not
9252 finish it before the weekend was up.
</p
>
9254 <p
>Did not find time to look at the
4 VGA cards in one box we got from
9255 the Brazilian group, so that will have to wait for the next
9256 development gathering. Would love to have the Debian Edu installer
9257 automatically detect and configure a multiseat setup when it find one
9258 of these cards.
</p
>
9263 <title>The sorry state of multimedia browser plugins in Debian
</title>
9264 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
9265 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
9266 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
9267 <description><p
>Recently I have spent some time evaluating the multimedia browser
9268 plugins available in Debian Lenny, to see which one we should use by
9269 default in Debian Edu. We need an embedded video playing plugin with
9270 control buttons to pause or stop the video, and capable of streaming
9271 all the multimedia content available on the web. The test results and
9272 notes are available on
9273 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
9274 Debian wiki
</a
>. I was surprised how few of the plugins are able to
9275 fill this need. My personal video player favorite, VLC, has a really
9276 bad plugin which fail on a lot of the test pages. A lot of the MIME
9277 types I would expect to work with any free software player (like
9278 video/ogg), just do not work. And simple formats like the
9279 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
9280 totem and vlc plugins. I hope the situation will improve soon. No
9281 wonder sites use the proprietary Adobe flash to play video.
</p
>
9283 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
9284 be the only one fitting our needs. :/
</p
>