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>The new
"best
" multimedia player in Debian?
</title>
11 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
13 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
14 <description><p
>When I set out a few weeks ago to figure out
15 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
16 multimedia player in Debian claimed to support most file formats /
17 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
18 the various players claimed support for. The range was from
55 to
130
19 MIME types. I suspect most media formats are supported by all
20 players, but this is not really reflected in the MimeTypes values in
21 their desktop files. There are probably also some bogus MIME types
22 listed, but it is hard to identify which one this is.
</p
>
24 <p
>Anyway, in the mean time I got in touch with upstream for some of
25 the players suggesting to add more MIME types to their desktop files,
26 and decided to spend some time myself improving the situation for my
27 favorite media player VLC. The fixes for VLC entered Debian unstable
28 yesterday. The complete list of MIME types can be seen on the
29 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
30 player MIME type support status
</a
> Debian wiki page.
</p
>
32 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
33 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
34 kmplayer. I am sure some of the other players desktop files support
35 several of the formats currently listed as working only with vlc,
36 toten and parole.
</p
>
38 <p
>A sad observation is that only
14 MIME types are listed as
39 supported by all the tested multimedia players in Debian in their
40 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
41 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
42 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
43 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
44 it sad that video/ogg and video/webm is not supported by all the media
45 players in Debian. As far as I can tell, all of them can handle both
51 <title>A program should be able to open its own files on Linux
</title>
52 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
53 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
54 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
55 <description><p
>Many years ago, when koffice was fresh and with few users, I
56 decided to test its presentation tool when making the slides for a
57 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
58 wrote the first draft of the slides, saved the result and went to bed
59 the day before I would give the talk. The next day I took a plane to
60 the location where the meeting should take place, and on the plane I
61 started up koffice again to polish the talk a bit, only to discover
62 that kpresenter refused to load its own data file. I cursed a bit and
63 started making the slides again from memory, to have something to
64 present when I arrived. I tested that the saved files could be
65 loaded, and the day seemed to be rescued. I continued to polish the
66 slides until I suddenly discovered that the saved file could no longer
67 be loaded into kpresenter. In the end I had to rewrite the slides
68 three times, condensing the content until the talk became shorter and
69 shorter. After the talk I was able to pinpoint the problem
&ndash;
70 kpresenter wrote inline images in a way itself could not understand.
71 Eventually that bug was fixed and kpresenter ended up being a great
72 program to make slides. The point I
'm trying to make is that we
73 expect a program to be able to load its own data files, and it is
74 embarrassing to its developers if it can
't.
</p
>
76 <p
>Did you ever experience a program failing to load its own data
77 files from the desktop file browser? It is not a uncommon problem. A
78 while back I discovered that the screencast recorder
79 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
80 browser would refuse to open. No video player claimed to understand
81 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
82 returning the application/ogg MIME type, which no video player I had
83 installed listed as a MIME type they would understand. I asked for
84 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
85 behavour
</a
> and use the MIME type video/ogg instead. I also asked
86 several video players to add video/ogg to their desktop files, to give
87 the file browser an idea what to do about Ogg Theora files. After a
88 while, the desktop file browsers in Debian started to handle the
89 output from gtk-recordmydesktop properly.
</p
>
91 <p
>But history repeats itself. A few days ago I tested the music
92 system Rosegarden again, and I discovered that the KDE and xfce file
93 browsers did not know what to do with the Rosegarden project files
94 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
95 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
96 included in the next upload. To increase the chance of me remembering
97 how to fix the problem next time some program fail to load its files
98 from the file browser, here are some notes on how to fix it.
</p
>
100 <p
>The file browsers in Debian in general operates on MIME types.
101 There are two sources for the MIME type of a given file. The output from
102 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
103 shared MIME type registry (under /usr/share/mime/). The file MIME
104 type is mapped to programs supporting the MIME type, and this
105 information is collected from
106 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
107 desktop files
</a
> available in /usr/share/applications/. If there is
108 one desktop file claiming support for the MIME type of the file, it is
109 activated when asking to open a given file. If there are more, one
110 can normally select which one to use by right-clicking on the file and
111 selecting the wanted one using
'Open with
' or similar. In general
112 this work well. But it depend on each program picking a good MIME
114 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
115 MIME type registered with IANA
</a
>), file and/or the shared MIME
116 registry recognizing the file and the desktop file to list the MIME
117 type in its list of supported MIME types.
</p
>
119 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
120 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
121 Shared MIME database
</a
> look like this:
</p
>
123 <p
><blockquote
><pre
>
124 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
125 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
126 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
127 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
128 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
129 &lt;glob pattern=
"*.rg
"/
&gt;
130 &lt;/mime-type
&gt;
131 &lt;/mime-info
&gt;
132 </pre
></blockquote
></p
>
134 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
135 (it is a gzipped XML file). Note, it is much better to use an
136 official MIME type registered with IANA than it is to make up ones own
137 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
139 <p
>The desktop file of the rosegarden program failed to list
140 audio/x-rosegarden in its list of supported MIME types, causing the
141 file browsers to have no idea what to do with *.rg files:
</p
>
143 <p
><blockquote
><pre
>
144 % grep Mime /usr/share/applications/rosegarden.desktop
145 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
146 X-KDE-NativeMimeType=audio/x-rosegarden-composition
148 </pre
></blockquote
></p
>
150 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
151 MimeType= line.
</p
>
153 <p
>If you run into a file which fail to open the correct program when
154 selected from the file browser, please check out the output from
155 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
156 MIME type is registered somewhere under /usr/share/mime/ and check
157 that some desktop file under /usr/share/applications/ is claiming
158 support for this MIME type. If not, please report a bug to have it
164 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
165 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
166 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
167 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
168 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
169 system
</a
> is a user-focused solution in Debian for handling hardware
170 related packages. The idea is to have a database of mappings between
171 hardware and packages, and pop up a dialog suggesting for the user to
172 install the packages to use a given hardware dongle. Some use cases
173 are when you insert a Yubikey, it proposes to install the software
174 needed to control it; when you insert a braille reader list it
175 proposes to install the packages needed to send text to the reader;
176 and when you insert a ColorHug screen calibrator it suggests to
177 install the driver for it. The system work well, and even have a few
178 command line tools to install firmware packages and packages for the
179 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
181 <p
>The system was initially written using aptdaemon, because I found
182 good documentation and example code on how to use it. But aptdaemon
183 is going away and is generally being replaced by
184 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
185 so Isenkram needed a rewrite. And today, thanks to the great patch
186 from my college Sunil Mohan Adapa in the FreedomBox project, the
187 rewrite finally took place. I
've just uploaded a new version of
188 Isenkram into Debian Unstable with the patch included, and the default
189 for the background daemon is now to use PackageKit. To check it out,
190 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
191 and see if it is recognised.
</p
>
193 <p
>If you want to know what kind of packages isenkram would propose for
194 the machine it is running on, you can check out the isenkram-lookup
195 program. This is what it look like on a Thinkpad X230:
</p
>
197 <p
><blockquote
><pre
>
213 </pre
></blockquote
></p
>
215 <p
>The hardware mappings come from several places. The preferred way
216 is for packages to announce their hardware support using
217 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
218 cross distribution appstream system
</a
>.
220 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
221 blog posts about isenkram
</a
> to learn how to do that.
</p
>
226 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
227 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
228 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
229 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
230 <description><p
>Yesterday I updated the
231 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
232 package in Debian
</a
> with a few patches sent to me by skilled and
233 enterprising users. There were some nice user and visible changes.
234 First of all, both desktop menu entries now work. A design flaw in
235 one of the script made the history graph fail to show up (its PNG was
236 dumped in ~/.xsession-errors) if no controlling TTY was available.
237 The script worked when called from the command line, but not when
238 called from the desktop menu. I changed this to look for a DISPLAY
239 variable or a TTY before deciding where to draw the graph, and now the
240 graph window pop up as expected.
</p
>
242 <p
>The next new feature is a discharge rate estimator in one of the
243 graphs (the one showing the last few hours). New is also the user of
244 colours showing charging in blue and discharge in red. The percentages
245 of this graph is relative to last full charge, not battery design
248 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
250 <p
>The other graph show the entire history of the collected battery
251 statistics, comparing it to the design capacity of the battery to
252 visualise how the battery life time get shorter over time. The red
253 line in this graph is what the previous graph considers
100 percent:
255 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
257 <p
>In this graph you can see that I only charge the battery to
80
258 percent of last full capacity, and how the capacity of the battery is
259 shrinking. :(
</p
>
261 <p
>The last new feature is in the collector, which now will handle
262 more hardware models. On some hardware, Linux power supply
263 information is stored in /sys/class/power_supply/ACAD/, while the
264 collector previously only looked in /sys/class/power_supply/AC/. Now
265 both are checked to figure if there is power connected to the
268 <p
>If you are interested in how your laptop battery is doing, please
270 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
271 in Debian unstable, or rebuild it on Jessie to get it working on
272 Debian stable. :) The upstream source is available from
<a
273 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
274 Patches are very welcome.
</p
>
276 <p
>As usual, if you use Bitcoin and want to show your support of my
277 activities, please send Bitcoin donations to my address
278 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
283 <title>Debian now with ZFS on Linux included
</title>
284 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
285 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
286 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
287 <description><p
>Today, after many years of hard work from many people,
288 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
289 Debian. The package status can be seen on
290 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
291 for zfs-linux
</a
>. and
292 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
293 team status page
</a
>. If you want to help out, please join us.
294 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
295 source code
</a
> is available via git on Alioth. It would also be
296 great if you could help out with
297 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
298 it is an important piece of the puzzle to get ZFS working.
</p
>
303 <title>What is the best multimedia player in Debian?
</title>
304 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
305 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
306 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
307 <description><p
><strong
>Where I set out to figure out which multimedia player in
308 Debian claim support for most file formats.
</strong
></p
>
310 <p
>A few years ago, I had a look at the media support for Browser
311 plugins in Debian, to get an idea which plugins to include in Debian
312 Edu. I created a script to extract the set of supported MIME types
313 for each plugin, and used this to find out which multimedia browser
314 plugin supported most file formats / media types.
315 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
316 result
</a
> can still be seen on the Debian wiki, even though it have
317 not been updated for a while. But browser plugins are less relevant
318 these days, so I thought it was time to look at standalone
321 <p
>A few days ago I was tired of VLC not being listed as a viable
322 player when I wanted to play videos from the Norwegian National
323 Broadcasting Company, and decided to investigate why. The cause is a
324 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
325 desktop file
</a
>. In the process I wrote a script to compare the set
326 of MIME types announced in the desktop file and the browser plugin,
327 only to discover that there is quite a large difference between the
328 two for VLC. This discovery made me dig up the script I used to
329 compare browser plugins, and adjust it to compare desktop files
330 instead, to try to figure out which multimedia player in Debian
331 support most file formats.
</p
>
333 <p
>The result can be seen on the Debian Wiki, as
334 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
335 table listing all MIME types supported by one of the packages included
336 in the table
</a
>, with the package supporting most MIME types being
337 listed first in the table.
</p
>
339 </p
>The best multimedia player in Debian? It is totem, followed by
340 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
341 kmplayer. Time for the other players to update their announced MIME
347 <title>The Pyra - handheld computer with Debian preinstalled
</title>
348 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
349 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
350 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
351 <description>A friend of mine made me aware of
352 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
353 handheld computer which will be delivered with Debian preinstalled. I
354 would love to get one of those for my birthday. :)
</p
>
356 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
357 plugs and many others connectors, and include a full keyboard and a
5"
358 LCD touch screen. The
6000mAh battery is claimed to provide a whole
359 day of battery life time, but I have not seen any independent tests
360 confirming this. The vendor is still collecting preorders, and the
361 last I heard last night was that
22 more orders were needed before
362 production started.
</p
>
364 <p
>As far as I know, this is the first handheld preinstalled with
365 Debian. Please let me know if you know of any others. Is it the
366 first computer being sold with Debian preinstalled?
</p
>
371 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
372 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
373 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
374 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
375 <description><p
>During this weekends
376 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
377 squashing party and developer gathering
</a
>, we decided to do our part
378 to make sure there are good books about Debian available in Norwegian
379 Bokmål, and got in touch with the people behind the
380 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
381 project
</a
> to get started. If you want to help out, please start
383 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
384 hosted weblate project page
</a
>, and get in touch using
385 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
386 translators mailing list
</a
>. Please also check out
387 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
388 contributors
</a
>.
</p
>
390 <p
>The book is already available on paper in English, French and
391 Japanese, and our goal is to get it available on paper in Norwegian
392 Bokmål too. In addition to the paper edition, there are also EPUB and
393 Mobi versions available. And there are incomplete translations
394 available for many more languages.
</p
>
399 <title>One in two hundred Debian users using ZFS on Linux?
</title>
400 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
401 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
402 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
403 <description><p
>Just for fun I had a look at the popcon number of ZFS related
404 packages in Debian, and was quite surprised with what I found. I use
405 ZFS myself at home, but did not really expect many others to do so.
406 But I might be wrong.
</p
>
408 <p
>According to
409 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
410 results for spl-linux
</a
>, there are
1019 Debian installations, or
411 0.53% of the population, with the package installed. As far as I know
412 the only use of the spl-linux package is as a support library for ZFS
413 on Linux, so I use it here as proxy for measuring the number of ZFS
414 installation on Linux in Debian. In the kFreeBSD variant of Debian
415 the ZFS feature is already available, and there
416 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
417 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
418 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
420 <p
>But even though the Debian project leader Lucas Nussbaum
421 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
422 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
423 cleared, the package is still not in Debian. The package is again in
424 the NEW queue. Several uploads have been rejected so far because the
425 debian/copyright file was incomplete or wrong, but there is no reason
426 to give up. The current status can be seen on
427 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
428 team status page
</a
>, and
429 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
430 source code
</a
> is available on Alioth.
</p
>
432 <p
>As I want ZFS to be included in next version of Debian to make sure
433 my home server can function in the future using only official Debian
434 packages, and the current blocker is to get the debian/copyright file
435 accepted by the FTP masters in Debian, I decided a while back to try
436 to help out the team. This was the background for my blog post about
437 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
438 updating and checking debian/copyright semi-automatically
</a
>, and I
439 used the techniques I explored there to try to find any errors in the
440 copyright file. It is not very easy to check every one of the around
441 2000 files in the source package, but I hope we this time got it
442 right. If you want to help out, check out the git source and try to
443 find missing entries in the debian/copyright file.
</p
>
448 <title>Full battery stats collector is now available in Debian
</title>
449 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
450 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
451 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
452 <description><p
>Since this morning, the battery-stats package in Debian include an
453 extended collector that will collect the complete battery history for
454 later processing and graphing. The original collector store the
455 battery level as percentage of last full level, while the new
456 collector also record battery vendor, model, serial number, design
457 full level, last full level and current battery level. This make it
458 possible to predict the lifetime of the battery as well as visualise
459 the energy flow when the battery is charging or discharging.
</p
>
461 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
462 in the version
0.5.1 package in unstable. Get the new battery level graph
463 and lifetime prediction by running:
466 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
467 </pre
></p
>
469 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
471 <p
>The flow in/out of the battery can be seen by running (no menu
472 entry yet):
</p
>
475 /usr/share/battery-stats/battery-stats-graph-flow
476 </pre
></p
>
478 <p
>I
'm not quite happy with the way the data is visualised, at least
479 when there are few data points. The graphs look a bit better with a
480 few years of data.
</p
>
482 <p
>A while back one important feature I use in the battery stats
483 collector broke in Debian. The scripts in
484 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
485 suspect it happened when Jessie started using systemd, but I do not
486 know. The issue is reported as
487 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
488 pm-utils. I managed to work around it by adding an udev rule to call
489 the collector script every time the power connector is connected and
490 disconnected. With this fix in place it was finally time to make a
491 new release of the package, and get it into Debian.
</p
>
493 <p
>If you are interested in how your laptop battery is doing, please
495 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
496 in Debian unstable, or rebuild it on Jessie to get it working on
497 Debian stable. :) The upstream source is available from
498 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
499 As always, patches are very welcome.
</p
>
504 <title>Making battery measurements a little easier in Debian
</title>
505 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
506 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
507 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
508 <description><p
>Back in September, I blogged about
509 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
510 system I wrote to collect statistics about my laptop battery
</a
>, and
511 how it showed the decay and death of this battery (now replaced). I
512 created a simple deb package to handle the collection and graphing,
513 but did not want to upload it to Debian as there were already
514 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
515 package in Debian
</a
> that should do the same thing, and I did not see
516 a point of uploading a competing package when battery-stats could be
517 fixed instead. I reported a few bugs about its non-function, and
518 hoped someone would step in and fix it. But no-one did.
</p
>
520 <p
>I got tired of waiting a few days ago, and took matters in my own
521 hands. The end result is that I am now the new upstream developer of
522 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
523 battery-stats in Debian, and the package in Debian unstable is finally
524 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
525 information provided by the Linux kernel. If you install the
526 battery-stats package from unstable now, you will be able to get a
527 graph of the current battery fill level, to get some idea about the
528 status of the battery. The source package build and work just fine in
529 Debian testing and stable (and probably oldstable too, but I have not
530 tested). The default graph you get for that system look like this:
</p
>
532 <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
>
534 <p
>My plans for the future is to merge my old scripts into the
535 battery-stats package, as my old scripts collected a lot more details
536 about the battery. The scripts are merged into the upstream
537 battery-stats git repository already, but I am not convinced they work
538 yet, as I changed a lot of paths along the way. Will have to test a
539 bit more before I make a new release.
</p
>
541 <p
>I will also consider changing the file format slightly, as I
542 suspect the way I combine several values into one field might make it
543 impossible to know the type of the value when using it for processing
544 and graphing.
</p
>
546 <p
>If you would like I would like to keep an close eye on your laptop
547 battery, check out the battery-stats package in
548 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
550 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
551 I would love some help to improve the system further.
</p
>
556 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
557 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
558 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
559 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
560 <description><p
>Making packages for Debian requires quite a lot of attention to
561 details. And one of the details is the content of the
562 debian/copyright file, which should list all relevant licenses used by
563 the code in the package in question, preferably in
564 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
565 readable DEP5 format
</a
>.
</p
>
567 <p
>For large packages with lots of contributors it is hard to write
568 and update this file manually, and if you get some detail wrong, the
569 package is normally rejected by the ftpmasters. So getting it right
570 the first time around get the package into Debian faster, and save
571 both you and the ftpmasters some work.. Today, while trying to figure
572 out what was wrong with
573 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
574 zfsonlinux copyright file
</a
>, I decided to spend some time on
575 figuring out the options for doing this job automatically, or at least
576 semi-automatically.
</p
>
578 <p
>Lucikly, there are at least two tools available for generating the
579 file based on the code in the source package,
580 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
581 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
582 not sure which one of them came first, but both seem to be able to
583 create a sensible draft file. As far as I can tell, none of them can
584 be trusted to get the result just right, so the content need to be
585 polished a bit before the file is OK to upload. I found the debmake
587 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
588 blog posts from
2014</a
>.
590 <p
>To generate using debmake, use the -cc option:
593 debmake -cc
> debian/copyright
594 </pre
></p
>
596 <p
>Note there are some problems with python and non-ASCII names, so
597 this might not be the best option.
</p
>
599 <p
>The cme option is based on a config parsing library, and I found
601 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
602 blog post from
2015</a
>. To generate using cme, use the
'update
603 dpkg-copyright
' option:
606 cme update dpkg-copyright
607 </pre
></p
>
609 <p
>This will create or update debian/copyright. The cme tool seem to
610 handle UTF-
8 names better than debmake.
</p
>
612 <p
>When the copyright file is created, I would also like some help to
613 check if the file is correct. For this I found two good options,
614 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
615 to focus on license types and file matching, and is able to detect
616 ineffective blocks in the copyright file. The latter reports missing
617 copyright holders and years, but was confused by inconsistent license
618 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
619 fix all issues reported by them before uploading. But I do not know
620 if the tools and the ftpmasters agree on what is important to fix in a
621 copyright file, so the package might still be rejected.
</p
>
623 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
624 will read through the source and try to find all copyright statements.
625 It is not comparing the result to the content of debian/copyright, but
626 can be useful when verifying the content of the copyright file.
</p
>
628 <p
>Are you aware of better tools in Debian to create and update
629 debian/copyright file. Please let me know, or blog about it on
630 planet.debian.org.
</p
>
632 <p
>As usual, if you use Bitcoin and want to show your support of my
633 activities, please send Bitcoin donations to my address
634 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
636 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
637 on how to use licensecheck and cdbs to create a draft copyright file
640 licensecheck --copyright -r `find * -type f` | \
641 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
642 </pre
></p
>
644 <p
>He mentioned that he normally check the generated file into the
645 version control system to make it easier to discover license and
646 copyright changes in the upstream source. I will try to do the same
647 with my packages in the future.
</p
>
649 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
650 against using -quiet for new users, so I removed it from the proposed
651 command line.
</p
>
656 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
657 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
658 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
659 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
660 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
661 is taking shape in Debian, and one provided feature is a very
662 convenient way to tell you which package to install to make a given
663 firmware file available when the kernel is looking for it. This can
664 be done using apt-file too, but that is for someone else to blog
667 <p
>Here is a small recipe to find the package with a given firmware
668 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
669 picked from the set of firmware announced using appstream in Debian
670 unstable. In general you would be looking for the firmware requested
671 by the kernel during kernel module loading. To find the package
672 providing the example file, do like this:
</p
>
674 <blockquote
><pre
>
675 % apt install appstream
679 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
680 awk
'/Package:/ {print $
2}
'
683 </pre
></blockquote
>
685 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
686 appstream wiki
</a
> page to learn how to embed the package metadata in
687 a way appstream can use.
</p
>
689 <p
>This same approach can be used to find any package supporting a
690 given MIME type. This is very useful when you get a file you do not
691 know how to handle. First find the mime type using
<tt
>file
692 --mime-type
</tt
>, and next look up the package providing support for
693 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
694 and you can find all packages handling this type like this:
</p
>
696 <blockquote
><pre
>
697 % apt install appstream
701 % appstreamcli what-provides mimetype image/svg+xml | \
702 awk
'/Package:/ {print $
2}
'
724 </pre
></blockquote
>
726 <p
>I believe the MIME types are fetched from the desktop file for
727 packages providing appstream metadata.
</p
>
732 <title>Creepy, visualise geotagged social media information - nice free software
</title>
733 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
734 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
735 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
736 <description><p
>Most people seem not to realise that every time they walk around
737 with the computerised radio beacon known as a mobile phone their
738 position is tracked by the phone company and often stored for a long
739 time (like every time a SMS is received or sent). And if their
740 computerised radio beacon is capable of running programs (often called
741 mobile apps) downloaded from the Internet, these programs are often
742 also capable of tracking their location (if the app requested access
743 during installation). And when these programs send out information to
744 central collection points, the location is often included, unless
745 extra care is taken to not send the location. The provided
746 information is used by several entities, for good and bad (what is
747 good and bad, depend on your point of view). What is certain, is that
748 the private sphere and the right to free movement is challenged and
749 perhaps even eradicated for those announcing their location this way,
750 when they share their whereabouts with private and public
753 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
755 <p
>The phone company logs provide a register of locations to check out
756 when one want to figure out what the tracked person was doing. It is
757 unavailable for most of us, but provided to selected government
758 officials, company staff, those illegally buying information from
759 unfaithful servants and crackers stealing the information. But the
760 public information can be collected and analysed, and a free software
761 tool to do so is called
762 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
763 discovered it when I read
764 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
765 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
766 November
2014, and decided to check if it was available in Debian.
767 The python program was in Debian, but
768 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
769 Debian
</a
> was completely broken and practically unmaintained. I
770 uploaded a new version which did not work quite right, but did not
771 have time to fix it then. This Christmas I decided to finally try to
772 get Creepy operational in Debian. Now a fixed version is available in
773 Debian unstable and testing, and almost all Debian specific patches
775 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
777 <p
>The Creepy program visualises geolocation information fetched from
778 Twitter, Instagram, Flickr and Google+, and allow one to get a
779 complete picture of every social media message posted recently in a
780 given area, or track the movement of a given individual across all
781 these services. Earlier it was possible to use the search API of at
782 least some of these services without identifying oneself, but these
783 days it is impossible. This mean that to use Creepy, you need to
784 configure it to log in as yourself on these services, and provide
785 information to them about your search interests. This should be taken
786 into account when using Creepy, as it will also share information
787 about yourself with the services.
</p
>
789 <p
>The picture above show the twitter messages sent from (or at least
790 geotagged with a position from) the city centre of Oslo, the capital
791 of Norway. One useful way to use Creepy is to first look at
792 information tagged with an area of interest, and next look at all the
793 information provided by one or more individuals who was in the area.
794 I tested it by checking out which celebrity provide their location in
795 twitter messages by checkout out who sent twitter messages near a
796 Norwegian TV station, and next could track their position over time,
797 making it possible to locate their home and work place, among other
798 things. A similar technique have been
799 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
800 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
801 tool to discover lying governments, and a useful tool to help people
802 understand the value of the private information they provide to the
805 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
806 it depend on several python modules currently missing in Jessie (at
807 least python-instagram, python-flickrapi and
808 python-requests-toolbelt).
</p
>
810 <p
>(I have uploaded
811 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
812 screenshots.debian.net
</a
> and licensed it under the same terms as the
813 Creepy program in Debian.)
</p
>
818 <title>Always download Debian packages using Tor - the simple recipe
</title>
819 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
820 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
821 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
822 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
823 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
824 that those listening on the Internet lines would have good reason to
825 believe a computer have a given security hole
</a
> if it download a
826 security fix from a Debian mirror. This is a good reason to always
827 use encrypted connections to the Debian mirror, to make sure those
828 listening do not know which IP address to attack. In August, Richard
829 Hartmann observed that encryption was not enough, when it was possible
830 to interfere download size to security patches or the fact that
831 download took place shortly after a security fix was released, and
832 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
833 to always use Tor to download packages from the Debian mirror
</a
>. He
834 was not the first to propose this, as the
835 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
836 package by Tim Retout already existed to make it easy to convince apt
837 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
838 aware of that package when I read the blog post from Richard.
</p
>
840 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
841 sysadmins, and he set up a Tor hidden service on one of the central
842 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
843 it possible to download packages directly between two tor nodes,
844 making sure the network traffic always were encrypted.
</p
>
846 <p
>Here is a short recipe for enabling this on your machine, by
847 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
848 urls with tor+http and tor+https, and using the hidden service instead
849 of the official Debian mirror site. I recommend installing
850 <tt
>etckeeper
</tt
> before you start to have a history of the changes
851 done in /etc/.
</p
>
853 <blockquote
><pre
>
854 apt install apt-transport-tor
855 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
856 sed -i
's% http% tor+http%
' /etc/apt/sources.list
857 </pre
></blockquote
>
859 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
860 the sed commands for these too. The sed command is assuming your are
861 using the ftp.debian.org Debian mirror. Adjust the command (or just
862 edit the file manually) to match your mirror.
</p
>
864 <p
>This work in Debian Jessie and later. Note that tools like
865 <tt
>apt-file
</tt
> only recently started using the apt transport
866 system, and do not work with these tor+http URLs. For
867 <tt
>apt-file
</tt
> you need the version currently in experimental,
868 which need a recent apt version currently only in unstable. So if you
869 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
871 <p
>Another advantage from this change is that your machine will start
872 using Tor regularly and at fairly random intervals (every time you
873 update the package lists or upgrade or install a new package), thus
874 masking other Tor traffic done from the same machine. Using Tor will
875 become normal for the machine in question.
</p
>
877 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
878 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
879 enabled. It would be great if it was the default on any Debian
885 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
886 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
887 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
888 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
889 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
890 call the car license plate numbers in those days. I would write the
891 numbers down in my little book and compare notes with the other kids
892 to see how many region codes we had seen and if we had seen some
893 exotic or special region codes and numbers. It was a fun game to pass
894 time, as we kids have plenty of it.
</p
>
896 <p
>A few days I came across
897 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
898 project
</a
>, a free software project to automatically discover and
899 report license plates in images and video streams, and provide the
900 "car numbers
" in a machine readable format. I
've been looking for
901 such system for a while now, because I believe it is a bad idea that the
902 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
903 number plate recognition
</a
> tool only is available in the hands of
904 the powerful, and want it to be available also for the powerless to
905 even the score when it comes to surveillance and sousveillance. I
906 discovered the developer
907 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
908 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
909 help him get it into shape to get the package uploaded into the Debian
912 <p
>Today we finally managed to get the package into shape and uploaded
913 it into Debian, where it currently
914 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
915 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
917 <p
>I guess you are wondering why on earth such tool would be useful
918 for the common folks, ie those not running a large government
919 surveillance system? Well, I plan to put it in a computer on my bike
920 and in my car, tracking the cars nearby and allowing me to be notified
921 when number plates on my watch list are discovered. Another use case
922 was suggested by a friend of mine, who wanted to set it up at his home
923 to open the car port automatically when it discovered the plate on his
924 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
925 capable of placing his license plate number of a piece of cardboard to
926 open his car port, men replied that it was always unlocked anyway. I
927 guess for such use case it make sense. I am sure there are other use
928 cases too, for those with imagination and a vision.
</p
>
930 <p
>If you want to build your own version of the Debian package, check
931 out the upstream git source and symlink ./distros/debian to ./debian/
932 before running
"debuild
" to build the source. Or wait a bit until the
933 package show up in unstable.
</p
>
938 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
939 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
940 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
941 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
942 <description><p
>Around three years ago, I created
943 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
944 system
</a
> to get a more practical solution in Debian for handing
945 hardware related packages. A GUI system in the isenkram package will
946 present a pop-up dialog when some hardware dongle supported by
947 relevant packages in Debian is inserted into the machine. The same
948 lookup mechanism to detect packages is available as command line
949 tools in the isenkram-cli package. In addition to mapping hardware,
950 it will also map kernel firmware files to packages and make it easy to
951 install needed firmware packages automatically. The key for this
952 system to work is a good way to map hardware to packages, in other
953 words, allow packages to announce what hardware they will work
956 <p
>I started by providing data files in the isenkram source, and
957 adding code to download the latest version of these data files at run
958 time, to ensure every user had the most up to date mapping available.
959 I also added support for storing the mapping in the Packages file in
960 the apt repositories, but did not push this approach because while I
961 was trying to figure out how to best store hardware/package mappings,
962 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
963 appstream system
</a
> was announced. I got in touch and suggested to
964 add the hardware mapping into that data set to be able to use
965 appstream as a data source, and this was accepted at least for the
966 Debian version of appstream.
</p
>
968 <p
>A few days ago using appstream in Debian for this became possible,
969 and today I uploaded a new version
0.20 of isenkram adding support for
970 appstream as a data source for mapping hardware to packages. The only
971 package so far using appstream to announce its hardware support is my
972 pymissile package. I got help from Matthias Klumpp with figuring out
973 how do add the required
974 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
975 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
976 this content:
</p
>
978 <blockquote
><pre
>
979 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
980 &lt;component
&gt;
981 &lt;id
&gt;pymissile
&lt;/id
&gt;
982 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
983 &lt;name
&gt;pymissile
&lt;/name
&gt;
984 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
985 &lt;description
&gt;
987 Pymissile provides a curses interface to control an original
988 Marks and Spencer / Striker USB Missile Launcher, as well as a
989 motion control script to allow a webcamera to control the
992 &lt;/description
&gt;
993 &lt;provides
&gt;
994 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
995 &lt;/provides
&gt;
996 &lt;/component
&gt;
997 </pre
></blockquote
>
999 <p
>The key for isenkram is the component/provides/modalias value,
1000 which is a glob style match rule for hardware specific strings
1001 (modalias strings) provided by the Linux kernel. In this case, it
1002 will map to all USB devices with vendor code
1130 and product code
1005 <p
>Note, it is important that the license of all the metadata files
1006 are compatible to have permissions to aggregate them into archive wide
1007 appstream files. Matthias suggested to use MIT or BSD licenses for
1008 these files. A challenge is figuring out a good id for the data, as
1009 it is supposed to be globally unique and shared across distributions
1010 (in other words, best to coordinate with upstream what to use). But
1011 it can be changed later or, so we went with the package name as
1012 upstream for this project is dormant.
</p
>
1014 <p
>To get the metadata file installed in the correct location for the
1015 mirror update scripts to pick it up and include its content the
1016 appstream data source, the file must be installed in the binary
1017 package under /usr/share/appdata/. I did this by adding the following
1018 line to debian/pymissile.install:
</p
>
1020 <blockquote
><pre
>
1021 debian/pymissile.metainfo.xml usr/share/appdata
1022 </pre
></blockquote
>
1024 <p
>With that in place, the command line tool isenkram-lookup will list
1025 all packages useful on the current computer automatically, and the GUI
1026 pop-up handler will propose to install the package not already
1027 installed if a hardware dongle is inserted into the machine in
1030 <p
>Details of the modalias field in appstream is available from the
1031 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
1033 <p
>To locate the modalias values of all hardware present in a machine,
1034 try running this command on the command line:
</p
>
1036 <blockquote
><pre
>
1037 cat $(find /sys/devices/|grep modalias)
1038 </pre
></blockquote
>
1040 <p
>To learn more about the isenkram system, please check out
1041 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1042 blog posts tagged isenkram
</a
>.
</p
>
1047 <title>The GNU General Public License is not magic pixie dust
</title>
1048 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
1049 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
1050 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
1051 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
1052 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
1053 GPL is not magic pixie dust
</a
>" explain the importance of making sure
1054 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
1055 I quote the blog post from Paul in full here with his permission:
<p
>
1059 <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
>
1062 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
1064 The first step is to choose a
1065 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
1068 The next step is, when someone fails to follow that copyleft license,
1069 <b
>it must be enforced
</b
><br/
>
1071 and its a simple fact of our modern society that such type of
1074 is incredibly expensive to do and incredibly difficult to do.
1077 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
1078 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
1079 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
1080 0x57</a
></small
></p
>
1082 <p
>As the Debian Website
1083 <a href=
"https://bugs.debian.org/
794116">used
</a
>
1084 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
1085 imply, public domain and permissively licensed software can lead to
1086 the production of more proprietary software as people discover useful
1087 software, extend it and or incorporate it into their hardware or
1088 software products. Copyleft licenses such as the GNU GPL were created
1089 to close off this avenue to the production of proprietary software but
1090 such licenses are not enough. With the ongoing adoption of Free
1091 Software by individuals and groups, inevitably the community
's
1092 expectations of license compliance are violated, usually out of
1093 ignorance of the way Free Software works, but not always. As Karen
1094 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
1095 Freedom
">FaiF
</a
>
1096 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
1097 copyleft is nothing if no-one is willing and able to stand up in court
1098 to protect it. The reality of today
's world is that legal
1099 representation is expensive, difficult and time consuming. With
1100 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
1101 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
1102 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
1103 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
1104 of the Linux project, Debian and other groups against GPL violations.
1105 In March the SFC supported a
1106 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
1107 by Christoph Hellwig
</a
> against VMware for refusing to
1108 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
1109 with the GPL
</a
> in relation to their use of parts of the Linux
1110 kernel. Since then two of their sponsors pulled corporate funding and
1112 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
1113 or cancelled their talks
</a
>. As a result they have decided to rely
1114 less on corporate funding and more on the broad community of
1115 individuals who support Free Software and copyleft. So the SFC has
1116 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
1117 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
1118 a community of folks who stand up for copyleft and the GPL by
1119 supporting their work on promoting and supporting copyleft and Free
1122 <p
>If you support Free Software,
1123 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
1124 what the SFC do, agree with their
1125 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
1126 principles
</a
>, are happy about their
1127 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
1128 work on a project that is an SFC
1129 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
1130 just want to stand up for copyleft, please join
1131 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
1132 Allan Webber
</a
>,
1133 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
1135 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
1136 Bacon
</a
>, myself and
1137 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
1139 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
1140 next week your donation will be
1141 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
1142 by an anonymous donor. Please also consider asking your employer to
1143 match your donation or become a sponsor of SFC. Don
't forget to
1144 spread the word about your support for SFC via email, your blog and or
1145 social media accounts.
</p
>
1149 <p
>I agree with Paul on this topic and just signed up as a Supporter
1150 of Software Freedom Conservancy myself. Perhaps you should be a
1151 supporter too?
</p
>
1156 <title>PGP key transition statement for key EE4E02F9
</title>
1157 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
1158 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
1159 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
1160 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
1161 set it up properly. I wanted to generate it offline and have it
1162 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
1163 smart card
</a
> for daily use, and learning how to do it and finding
1164 time to sit down with an offline machine almost took forever. But
1165 finally I
've been able to complete the process, and have now moved
1166 from my old GPG key to a new GPG key. See
1167 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
1168 full transition statement, signed with both my old and new key
</a
> for
1169 the details. This is my new key:
</p
>
1172 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
1173 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
1174 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
1175 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
1176 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
1177 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
1178 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
1181 <p
>The key can be downloaded from the OpenPGP key servers, signed by
1182 my old key.
</p
>
1184 <p
>If you signed my old key
1185 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
1186 I
'd very much appreciate a signature on my new key, details and
1187 instructions in the transition statement. I m happy to reciprocate if
1188 you have a similarly signed transition statement to present.
</p
>
1193 <title>The life and death of a laptop battery
</title>
1194 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
1195 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
1196 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
1197 <description><p
>When I get a new laptop, the battery life time at the start is OK.
1198 But this do not last. The last few laptops gave me a feeling that
1199 within a year, the life time is just a fraction of what it used to be,
1200 and it slowly become painful to use the laptop without power connected
1201 all the time. Because of this, when I got a new Thinkpad X230 laptop
1202 about two years ago, I decided to monitor its battery state to have
1203 more hard facts when the battery started to fail.
</p
>
1205 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
1207 <p
>First I tried to find a sensible Debian package to record the
1208 battery status, assuming that this must be a problem already handled
1209 by someone else. I found
1210 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
1211 which collects statistics from the battery, but it was completely
1212 broken. I sent a few suggestions to the maintainer, but decided to
1213 write my own collector as a shell script while I waited for feedback
1215 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
1216 blog post about the battery development on a MacBook Air
</a
> I also
1218 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
1219 available in Debian.
</p
>
1221 <p
>I started my collector
2013-
07-
15, and it has been collecting
1222 battery stats ever since. Now my
1223 /var/log/hjemmenett-battery-status.log file contain around
115,
000
1224 measurements, from the time the battery was working great until now,
1225 when it is unable to charge above
7% of original capacity. My
1226 collector shell script is quite simple and look like this:
</p
>
1231 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
1233 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
1234 logfile=/var/log/hjemmenett-battery-status.log
1236 files=
"manufacturer model_name technology serial_number \
1237 energy_full energy_full_design energy_now cycle_count status
"
1239 if [ ! -e
"$logfile
" ] ; then
1241 printf
"timestamp,
"
1243 printf
"%s,
" $f
1246 )
> "$logfile
"
1250 # Print complete message in one echo call, to avoid race condition
1251 # when several log processes run in parallel.
1252 msg=$(printf
"%s,
" $(date +%s); \
1253 for f in $files; do \
1254 printf
"%s,
" $(cat $f); \
1256 echo
"$msg
"
1259 cd /sys/class/power_supply
1262 (cd $bat
&& log_battery
>> "$logfile
")
1266 <p
>The script is called when the power management system detect a
1267 change in the power status (power plug in or out), and when going into
1268 and out of hibernation and suspend. In addition, it collect a value
1269 every
10 minutes. This make it possible for me know when the battery
1270 is discharging, charging and how the maximum charge change over time.
1271 The code for the Debian package
1272 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
1273 available on github
</a
>.
</p
>
1275 <p
>The collected log file look like this:
</p
>
1278 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
1279 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
1281 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1282 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1285 <p
>I wrote a small script to create a graph of the charge development
1286 over time. This graph depicted above show the slow death of my laptop
1289 <p
>But why is this happening? Why are my laptop batteries always
1290 dying in a year or two, while the batteries of space probes and
1291 satellites keep working year after year. If we are to believe
1292 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
1293 University
</a
>, the cause is me charging the battery whenever I have a
1294 chance, and the fix is to not charge the Lithium-ion batteries to
100%
1295 all the time, but to stay below
90% of full charge most of the time.
1296 I
've been told that the Tesla electric cars
1297 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
1298 the charge of their batteries to
80%
</a
>, with the option to charge to
1299 100% when preparing for a longer trip (not that I would want a car
1300 like Tesla where rights to privacy is abandoned, but that is another
1301 story), which I guess is the option we should have for laptops on
1302 Linux too.
</p
>
1304 <p
>Is there a good and generic way with Linux to tell the battery to
1305 stop charging at
80%, unless requested to charge to
100% once in
1306 preparation for a longer trip? I found
1307 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
1308 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
1309 80%
</a
>, but could not get it to work (kernel module refused to
1312 <p
>I wonder why the battery capacity was reported to be more than
100%
1313 at the start. I also wonder why the
"full capacity
" increases some
1314 times, and if it is possible to repeat the process to get the battery
1315 back to design capacity. And I wonder if the discharge and charge
1316 speed change over time, or if this stay the same. I did not yet try
1317 to write a tool to calculate the derivative values of the battery
1318 level, but suspect some interesting insights might be learned from
1321 <p
>Update
2015-
09-
24: I got a tip to install the packages
1322 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
1323 packages instead of the tp-smapi-dkms package I had tried to use
1324 initially, and use
'tlp setcharge
40 80' to change when charging start
1325 and stop. I
've done so now, but expect my existing battery is toast
1326 and need to be replaced. The proposal is unfortunately Thinkpad
1332 <title>New laptop - some more clues and ideas based on feedback
</title>
1333 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
1334 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
1335 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
1336 <description><p
>Several people contacted me after my previous blog post about my
1337 need for a new laptop, and provided very useful feedback. I wish to
1338 thank every one of these. Several pointed me to the possibility of
1339 fixing my X230, and I am already in the process of getting Lenovo to
1340 do so thanks to the on site, next day support contract covering the
1341 machine. But the battery is almost useless (I expect to replace it
1342 with a non-official battery) and I do not expect the machine to live
1343 for many more years, so it is time to plan its replacement. If I did
1344 not have a support contract, it was suggested to find replacement parts
1345 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
1346 might present a language barrier as I do not understand French.
</p
>
1348 <p
>One tip I got was to use the
1349 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
1350 compare laptop models. It seem to have more models available than
1351 prisjakt.no. Another tip I got from someone I know have similar
1352 keyboard preferences was that the HP EliteBook
840 keyboard is not
1353 very good, and this matches my experience with earlier EliteBook
1354 keyboards I tested. Because of this, I will not consider it any further.
1356 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
1357 newest Thinkpad X model. The keyboard reintroduces mouse buttons
1358 (which is missing from the X240), and is working fairly well with
1359 Debian Sid/Unstable according to
1360 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
1361 got on the keyboard quality are not consistent. Some say the keyboard
1362 is good, others say it is ok, while others say it is not very good.
1363 Those with experience from X41 and and X60 agree that the X250
1364 keyboard is not as good as those trusty old laptops, and suggest I
1365 keep and fix my X230 instead of upgrading, or get a used X230 to
1366 replace it. I
'm also told that the X250 lack leds for caps lock, disk
1367 activity and battery status, which is very convenient on my X230. I
'm
1368 also told that the CPU fan is running very often, making it a bit
1369 noisy. In any case, the X250 do not work out of the box with Debian
1370 Stable/Jessie, one of my requirements.
</p
>
1372 <p
>I have also gotten a few vendor proposals, one was
1373 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
1374 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
1375 The latter look very attractive to me.
</p
>
1377 <p
>Again, thank you all for the very useful feedback. It help a lot
1378 as I keep looking for a replacement.
</p
>
1380 <p
>Update
2015-
07-
06: I was recommended to check out the
1381 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
1383 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
1384 thinkpad X models
</a
>, and provide one year warranty.
</p
>
1389 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
1390 <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>
1391 <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>
1392 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
1393 <description><p
>My primary work horse laptop is failing, and will need a
1394 replacement soon. The left
5 cm of the screen on my Thinkpad X230
1395 started flickering yesterday, and I suspect the cause is a broken
1396 cable, as changing the angle of the screen some times get rid of the
1397 flickering.
</p
>
1399 <p
>My requirements have not really changed since I bought it, and is
1401 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
1402 described them in
2013</a
>. The last time I bought a laptop, I had
1404 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
1405 where I could select at least a few of the requirements (mouse pin,
1406 wifi, weight) and go through the rest manually. Three button mouse
1407 and a good keyboard is not available as an option, and all the three
1408 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
1409 G2) lack three mouse buttons). It is also unclear to me how good the
1410 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
1411 the keyboard, even if the quality and robustness in the X series have
1412 deteriorated since X41.
</p
>
1414 <p
>I wonder how I can find a sensible laptop when none of the options
1415 seem sensible to me? Are there better services around to search the
1416 set of available laptops for features? Please send me an email if you
1417 have suggestions.
</p
>
1419 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
1420 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
1421 of endorsed hardware
</a
>, which is useful background information.
</p
>
1426 <title>How to stay with sysvinit in Debian Jessie
</title>
1427 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
1428 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
1429 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
1430 <description><p
>By now, it is well known that Debian Jessie will not be using
1431 sysvinit as its boot system by default. But how can one keep using
1432 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
1434 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
1435 Schubert
</a
> and
1436 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
1439 <p
>If you already are using Wheezy and want to upgrade to Jessie and
1440 keep sysvinit as your boot system, create a file
1441 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
1442 you upgrade:
</p
>
1444 <p
><blockquote
><pre
>
1445 Package: systemd-sysv
1446 Pin: release o=Debian
1448 </pre
></blockquote
><p
>
1450 <p
>This file content will tell apt and aptitude to not consider
1451 installing systemd-sysv as part of any installation and upgrade
1452 solution when resolving dependencies, and thus tell it to avoid
1453 systemd as a default boot system. The end result should be that the
1454 upgraded system keep using sysvinit.
</p
>
1456 <p
>If you are installing Jessie for the first time, there is no way to
1457 get sysvinit installed by default (debootstrap used by
1458 debian-installer have no option for this), but one can tell the
1459 installer to switch to sysvinit before the first boot. Either by
1460 using a kernel argument to the installer, or by adding a line to the
1461 preseed file used. First, the kernel command line argument:
1463 <p
><blockquote
><pre
>
1464 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
1465 </pre
></blockquote
><p
>
1467 <p
>Next, the line to use in a preseed file:
</p
>
1469 <p
><blockquote
><pre
>
1470 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
1471 </pre
></blockquote
><p
>
1473 <p
>One can of course also do this after the first boot by installing
1474 the sysvinit-core package.
</p
>
1476 <p
>I recommend only using sysvinit if you really need it, as the
1477 sysvinit boot sequence in Debian have several hardware specific bugs
1478 on Linux caused by the fact that it is unpredictable when hardware
1479 devices show up during boot. But on the other hand, the new default
1480 boot system still have a few rough edges I hope will be fixed before
1481 Jessie is released.
</p
>
1483 <p
>Update
2014-
11-
26: Inspired by
1484 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
1485 blog post by Torsten Glaser
</a
>, added --purge to the preseed
1491 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
1492 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
1493 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
1494 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
1495 <description><p
>The right to communicate with your friends and family in private,
1496 without anyone snooping, is a right every citicen have in a liberal
1497 democracy. But this right is under serious attack these days.
</p
>
1499 <p
>A while back it occurred to me that one way to make the dragnet
1500 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
1501 the whisleblower Snowden) more expensive for Internet email,
1502 is to deliver all email using SMTP via Tor. Such SMTP option would be
1503 a nice addition to the FreedomBox project if we could send email
1504 between FreedomBox machines without leaking metadata about the emails
1505 to the people peeking on the wire. I
1506 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
1507 this on the FreedomBox project mailing list in October
</a
> and got a
1508 lot of useful feedback and suggestions. It also became obvious to me
1509 that this was not a novel idea, as the same idea was tested and
1510 documented by Johannes Berg as early as
2006, and both
1511 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
1512 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
1513 propose a similar method / protocol to pass emails between users.
</p
>
1515 <p
>To implement such system one need to set up a Tor hidden service
1516 providing the SMTP protocol on port
25, and use email addresses
1517 looking like username@hidden-service-name.onion. With such addresses
1518 the connections to port
25 on hidden-service-name.onion using Tor will
1519 go to the correct SMTP server. To do this, one need to configure the
1520 Tor daemon to provide the hidden service and the mail server to accept
1521 emails for this .onion domain. To learn more about Exim configuration
1522 in Debian and test the design provided by Johannes Berg in his FAQ, I
1523 set out yesterday to create a Debian package for making it trivial to
1524 set up such SMTP over Tor service based on Debian. Getting it to work
1525 were fairly easy, and
1526 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
1527 source code for the Debian package
</a
> is available from github. I
1528 plan to move it into Debian if further testing prove this to be a
1529 useful approach.
</p
>
1531 <p
>If you want to test this, set up a blank Debian machine without any
1532 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
1533 get rid of exim4). Install tor, clone the git repository mentioned
1534 above, build the deb and install it on the machine. Next, run
1535 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
1536 the instructions to get the service up and running. Restart tor and
1537 exim when it is done, and test mail delivery using swaks like
1540 <p
><blockquote
><pre
>
1541 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
1542 --to fbx@dutlqrrmjhtfa3vp.onion
1543 </pre
></blockquote
></p
>
1545 <p
>This will test the SMTP delivery using tor. Replace the email
1546 address with your own address to test your server. :)
</p
>
1548 <p
>The setup procedure is still to complex, and I hope it can be made
1549 easier and more automatic. Especially the tor setup need more work.
1550 Also, the package include a tor-smtp tool written in C, but its task
1551 should probably be rewritten in some script language to make the deb
1552 architecture independent. It would probably also make the code easier
1553 to review. The tor-smtp tool currently need to listen on a socket for
1554 exim to talk to it and is started using xinetd. It would be better if
1555 no daemon and no socket is needed. I suspect it is possible to get
1556 exim to run a command line tool for delivery instead of talking to a
1557 socket, and hope to figure out how in a future version of this
1560 <p
>Until I wipe my test machine, I can be reached using the
1561 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
1562 SMTorP. :)
</p
>
1567 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
1568 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
1569 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
1570 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
1571 <description><p
>If you ever had to moderate a mailman list, like the ones on
1572 alioth.debian.org, you know the web interface is fairly slow to
1573 operate. First you visit one web page, enter the moderation password
1574 and get a new page shown with a list of all the messages to moderate
1575 and various options for each email address. This take a while for
1576 every list you moderate, and you need to do it regularly to do a good
1577 job as a list moderator. But there is a quick alternative,
1578 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
1579 listadmin program
</a
>. It allow you to check lists for new messages
1580 to moderate in a fraction of a second. Here is a test run on two
1581 lists I recently took over:
</p
>
1583 <p
><blockquote
><pre
>
1584 % time listadmin xiph
1585 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1586 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1592 </pre
></blockquote
></p
>
1594 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
1595 there are no message in the moderation queue. Every morning I
1596 currently moderate
68 mailman lists, and it normally take around two
1597 minutes. When I took over the two pkg-xiph lists above a few days
1598 ago, there were
400 emails waiting in the moderator queue. It took me
1599 less than
15 minutes to process them all using the listadmin
1602 <p
>If you install
1603 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
1604 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
1605 with content like this, the moderation task is a breeze:
</p
>
1607 <p
><blockquote
><pre
>
1608 username username@example.org
1611 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
1614 adminurl https://{domain}/mailman/admindb/{list}
1615 mailman-list@lists.example.com
1618 other-list@otherserver.example.org
1619 </pre
></blockquote
></p
>
1621 <p
>There are other options to set as well. Check the manual page to
1622 learn the details.
</p
>
1624 <p
>If you are forced to moderate lists on a mailman installation where
1625 the SSL certificate is self signed or not properly signed by a
1626 generally accepted signing authority, you can set a environment
1627 variable when calling listadmin to disable SSL verification:
</p
>
1629 <p
><blockquote
><pre
>
1630 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
1631 </pre
></blockquote
></p
>
1633 <p
>If you want to moderate a subset of the lists you take care of, you
1634 can provide an argument to the listadmin script like I do in the
1635 initial screen dump (the xiph argument). Using an argument, only
1636 lists matching the argument string will be processed. This make it
1637 quick to accept messages if you notice the moderation request in your
1640 <p
>Without the listadmin program, I would never be the moderator of
68
1641 mailing lists, as I simply do not have time to spend on that if the
1642 process was any slower. The listadmin program have saved me hours of
1643 time I could spend elsewhere over the years. It truly is nice free
1646 <p
>As usual, if you use Bitcoin and want to show your support of my
1647 activities, please send Bitcoin donations to my address
1648 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1650 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
1651 configuration example. Also, I
've been told that the
1652 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
1658 <title>Debian Jessie, PXE and automatic firmware installation
</title>
1659 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
1660 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
1661 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
1662 <description><p
>When PXE installing laptops with Debian, I often run into the
1663 problem that the WiFi card require some firmware to work properly.
1664 And it has been a pain to fix this using preseeding in Debian.
1665 Normally something more is needed. But thanks to
1666 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
1667 package
</a
> and its recent tasksel extension, it has now become easy
1668 to do this using simple preseeding.
</p
>
1670 <p
>The isenkram-cli package provide tasksel tasks which will install
1671 firmware for the hardware found in the machine (actually, requested by
1672 the kernel modules for the hardware). (It can also install user space
1673 programs supporting the hardware detected, but that is not the focus
1674 of this story.)
</p
>
1676 <p
>To get this working in the default installation, two preeseding
1677 values are needed. First, the isenkram-cli package must be installed
1678 into the target chroot (aka the hard drive) before tasksel is executed
1679 in the pkgsel step of the debian-installer system. This is done by
1680 preseeding the base-installer/includes debconf value to include the
1681 isenkram-cli package. The package name is next passed to debootstrap
1682 for installation. With the isenkram-cli package in place, tasksel
1683 will automatically use the isenkram tasks to detect hardware specific
1684 packages for the machine being installed and install them, because
1685 isenkram-cli contain tasksel tasks.
</p
>
1687 <p
>Second, one need to enable the non-free APT repository, because
1688 most firmware unfortunately is non-free. This is done by preseeding
1689 the apt-mirror-setup step. This is unfortunate, but for a lot of
1690 hardware it is the only option in Debian.
</p
>
1692 <p
>The end result is two lines needed in your preseeding file to get
1693 firmware installed automatically by the installer:
</p
>
1695 <p
><blockquote
><pre
>
1696 base-installer base-installer/includes string isenkram-cli
1697 apt-mirror-setup apt-setup/non-free boolean true
1698 </pre
></blockquote
></p
>
1700 <p
>The current version of isenkram-cli in testing/jessie will install
1701 both firmware and user space packages when using this method. It also
1702 do not work well, so use version
0.15 or later. Installing both
1703 firmware and user space packages might give you a bit more than you
1704 want, so I decided to split the tasksel task in two, one for firmware
1705 and one for user space programs. The firmware task is enabled by
1706 default, while the one for user space programs is not. This split is
1707 implemented in the package currently in unstable.
</p
>
1709 <p
>If you decide to give this a go, please let me know (via email) how
1710 this recipe work for you. :)
</p
>
1712 <p
>So, I bet you are wondering, how can this work. First and
1713 foremost, it work because tasksel is modular, and driven by whatever
1714 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1715 isenkram-cli package place two files for tasksel to find. First there
1716 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
1718 <p
><blockquote
><pre
>
1719 Task: isenkram-packages
1721 Description: Hardware specific packages (autodetected by isenkram)
1722 Based on the detected hardware various hardware specific packages are
1724 Test-new-install: show show
1726 Packages: for-current-hardware
1728 Task: isenkram-firmware
1730 Description: Hardware specific firmware packages (autodetected by isenkram)
1731 Based on the detected hardware various hardware specific firmware
1732 packages are proposed.
1733 Test-new-install: mark show
1735 Packages: for-current-hardware-firmware
1736 </pre
></blockquote
></p
>
1738 <p
>The key parts are Test-new-install which indicate how the task
1739 should be handled and the Packages line referencing to a script in
1740 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1741 list of packages to install. The for-current-hardware-firmware script
1742 look like this to list relevant firmware for the machine:
1744 <p
><blockquote
><pre
>
1747 PATH=/usr/sbin:$PATH
1749 isenkram-autoinstall-firmware -l
1750 </pre
></blockquote
></p
>
1752 <p
>With those two pieces in place, the firmware is installed by
1753 tasksel during the normal d-i run. :)
</p
>
1755 <p
>If you want to test what tasksel will install when isenkram-cli is
1756 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
1757 --new-install
</tt
> to get the list of packages that tasksel would
1760 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
1761 pilots in testing this feature, as isenkram is used there now to
1762 install firmware, replacing the earlier scripts.
</p
>
1767 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
1768 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
1769 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
1770 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
1771 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
1772 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1773 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
1774 on a screen normally showing the bread types and prizes:
</p
>
1776 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
1778 <p
>If it had booted as it was supposed to, I would never had known
1779 about this hidden Linux installation. It is interesting what
1780 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
1785 <title>New lsdvd release version
0.17 is ready
</title>
1786 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
1787 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
1788 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
1789 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
1790 got a new set of developers a few weeks ago, after the original
1791 developer decided to step down and pass the project to fresh blood.
1792 This project is now maintained by Petter Reinholdtsen and Steve
1795 <p
>I just wrapped up
1796 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
1797 new lsdvd release
</a
>, available in git or from
1798 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
1799 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
1804 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
1805 <li
>Check for garbage in the program chains, which indicate that a track is
1806 non-existant, to work around additional copy protection
</li
>
1807 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
1808 <li
>Fix pallete display of first entry
</li
>
1809 <li
>Fix include orders
</li
>
1810 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
1811 <li
>Fix the chapter count
</li
>
1812 <li
>Make sure the array size and the array limit used when initialising
1813 the palette size is the same.
</li
>
1814 <li
>Fix array printing.
</li
>
1815 <li
>Correct subsecond calculations.
</li
>
1816 <li
>Add sector information to the output format.
</li
>
1817 <li
>Clean up code to be closer to ANSI C and compile without warnings
1818 with more GCC compiler warnings.
</li
>
1822 <p
>This change bring together patches for lsdvd in use in various
1823 Linux and Unix distributions, as well as patches submitted to the
1824 project the last nine years. Please check it out. :)
</p
>
1829 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
1830 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
1831 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
1832 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
1833 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
1834 project
</a
> provide a Linux solution for schools, including a
1835 powerful desktop with education software, a central server providing
1836 web pages, user database, user home directories, central login and PXE
1837 boot of both clients without disk and the installation to install Debian
1838 Edu on machines with disk (and a few other services perhaps to small
1839 to mention here). We in the Debian Edu team are currently working on
1840 the Jessie based version, trying to get everything in shape before the
1841 freeze, to avoid having to maintain our own package repository in the
1843 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
1844 status
</a
> can be seen on the Debian wiki, and there is still heaps of
1845 work left. Some fatal problems block testing, breaking the installer,
1846 but it is possible to work around these to get anyway. Here is a
1847 recipe on how to get the installation limping along.
</p
>
1849 <p
>First, download the test ISO via
1850 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
1851 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
1853 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
1854 The ISO build was broken on Tuesday, so we do not get a new ISO every
1855 12 hours or so, but thankfully the ISO we already got we are able to
1856 install with some tweaking.
</p
>
1858 <p
>When you get to the Debian Edu profile question, go to tty2
1859 (use Alt-Ctrl-F2), run
</p
>
1861 <p
><blockquote
><pre
>
1862 nano /usr/bin/edu-eatmydata-install
1863 </pre
></blockquote
></p
>
1865 <p
>and add
'exit
0' as the second line, disabling the eatmydata
1866 optimization. Return to the installation, select the profile you want
1867 and continue. Without this change, exim4-config will fail to install
1868 due to a known bug in eatmydata.
</p
>
1870 <p
>When you get the grub question at the end, answer /dev/sda (or if
1871 this do not work, figure out what your correct value would be. All my
1872 test machines need /dev/sda, so I have no advice if it do not fit
1873 your need.
</p
>
1875 <p
>If you installed a profile including a graphical desktop, log in as
1876 root after the initial boot from hard drive, and install the
1877 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1878 or mate. If you want several desktop options, install more than one
1879 metapackage. Once this is done, reboot and you should have a working
1880 graphical login screen. This workaround should no longer be needed
1881 once the education-tasks package version
1.801 enter testing in two
1884 <p
>I believe the ISO build will start working on two days when the new
1885 tasksel package enter testing and Steve McIntyre get a chance to
1886 update the debian-cd git repository. The eatmydata, grub and desktop
1887 issues are already fixed in unstable and testing, and should show up
1888 on the ISO as soon as the ISO build start working again. Well the
1889 eatmydata optimization is really just disabled. The proper fix
1890 require an upload by the eatmydata maintainer applying the patch
1891 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
1892 The rest have proper fixes in unstable.
</p
>
1894 <p
>I hope this get you going with the installation testing, as we are
1895 quickly running out of time trying to get our Jessie based
1896 installation ready before the distribution freeze in a month.
</p
>
1901 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
1902 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
1903 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
1904 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
1905 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
1906 to handle my fairly large DVD collection. It is a nice command line
1907 tool to get details about a DVD, like title, tracks, track length,
1908 etc, in XML, Perl or human readable format. But lsdvd have not seen
1909 any new development since
2006 and had a few irritating bugs affecting
1910 its use with some DVDs. Upstream seemed to be dead, and in January I
1911 sent a small probe asking for a version control repository for the
1912 project, without any reply. But I use it regularly and would like to
1913 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
1914 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
1915 the project admin, and after getting a reply from him explaining that
1916 he was no longer interested in the project, I asked if I could take
1917 over. And yesterday, I became project admin.
</p
>
1919 <p
>I
've been in touch with a Gentoo developer and the Debian
1920 maintainer interested in joining forces to maintain the upstream
1921 project, and I hope we can get a new release out fairly quickly,
1922 collecting the patches spread around on the internet into on place.
1923 I
've added the relevant Debian patches to the freshly created git
1924 repository, and expect the Gentoo patches to make it too. If you got
1925 a DVD collection and care about command line tools, check out
1926 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
1927 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
1928 list
</a
>. :)
</p
>
1933 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
1934 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
1935 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
1936 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
1937 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
1938 a lot quicker. When we install more than
2000 packages in
1939 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
1940 tasksel in the installer, unpacking the binary packages take forever.
1941 A part of the slow I/O issue was discussed in
1942 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
1943 much file system sync-ing done by dpkg, which is the package
1944 responsible for unpacking the binary packages. Other parts (like code
1945 executed by postinst scripts) might also sync to disk during
1946 installation. All this sync-ing to disk do not really make sense to
1947 me. If the machine crash half-way through, I start over, I do not try
1948 to salvage the half installed system. So the failure sync-ing is
1949 supposed to protect against, hardware or system crash, is not really
1950 relevant while the installer is running.
</p
>
1952 <p
>A few days ago, I thought of a way to get rid of all the file
1953 system sync()-ing in a fairly non-intrusive way, without the need to
1954 change the code in several packages. The idea is not new, but I have
1955 not heard anyone propose the approach using dpkg-divert before. It
1956 depend on the small and clever package
1957 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
1958 uses LD_PRELOAD to replace the system functions for syncing data to
1959 disk with functions doing nothing, thus allowing programs to live
1960 dangerous while speeding up disk I/O significantly. Instead of
1961 modifying the implementation of dpkg, apt and tasksel (which are the
1962 packages responsible for selecting, fetching and installing packages),
1963 it occurred to me that we could just divert the programs away, replace
1964 them with a simple shell wrapper calling
1965 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
1966 Two days ago I decided to test the idea, and wrapped up a simple
1967 implementation for the Debian Edu udeb.
</p
>
1969 <p
>The effect was stunning. In my first test it reduced the running
1970 time of the pkgsel step (installing tasks) from
64 to less than
44
1971 minutes (
20 minutes shaved off the installation) on an old Dell
1972 Latitude D505 machine. I am not quite sure what the optimised time
1973 would have been, as I messed up the testing a bit, causing the debconf
1974 priority to get low enough for two questions to pop up during
1975 installation. As soon as I saw the questions I moved the installation
1976 along, but do not know how long the question were holding up the
1977 installation. I did some more measurements using Debian Edu Jessie,
1978 and got these results. The time measured is the time stamp in
1979 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
1980 "pkgsel: finishing up
" lines, if you want to do the same measurement
1981 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1982 timing thus do not depend on how quickly the user handle the tasksel
1985 <p
><table
>
1988 <th
>Machine/setup
</th
>
1989 <th
>Original tasksel
</th
>
1990 <th
>Optimised tasksel
</th
>
1991 <th
>Reduction
</th
>
1995 <td
>Latitude D505 Main+LTSP LXDE
</td
>
1996 <td
>64 min (
07:
46-
08:
50)
</td
>
1997 <td
><44 min (
11:
27-
12:
11)
</td
>
1998 <td
>>20 min
18%
</td
>
2002 <td
>Latitude D505 Roaming LXDE
</td
>
2003 <td
>57 min (
08:
48-
09:
45)
</td
>
2004 <td
>34 min (
07:
43-
08:
17)
</td
>
2005 <td
>23 min
40%
</td
>
2009 <td
>Latitude D505 Minimal
</td
>
2010 <td
>22 min (
10:
37-
10:
59)
</td
>
2011 <td
>11 min (
11:
16-
11:
27)
</td
>
2012 <td
>11 min
50%
</td
>
2016 <td
>Thinkpad X200 Minimal
</td
>
2017 <td
>6 min (
08:
19-
08:
25)
</td
>
2018 <td
>4 min (
08:
04-
08:
08)
</td
>
2019 <td
>2 min
33%
</td
>
2023 <td
>Thinkpad X200 Roaming KDE
</td
>
2024 <td
>19 min (
09:
21-
09:
40)
</td
>
2025 <td
>15 min (
10:
25-
10:
40)
</td
>
2026 <td
>4 min
21%
</td
>
2029 </table
></p
>
2031 <p
>The test is done using a netinst ISO on a USB stick, so some of the
2032 time is spent downloading packages. The connection to the Internet
2033 was
100Mbit/s during testing, so downloading should not be a
2034 significant factor in the measurement. Download typically took a few
2035 seconds to a few minutes, depending on the amount of packages being
2036 installed.
</p
>
2038 <p
>The speedup is implemented by using two hooks in
2039 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
2040 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
2041 finish-install.d hook to remove the divert at the end of the
2042 installation. I picked the pre-pkgsel.d hook instead of the
2043 post-base-installer.d hook because I test using an ISO without the
2044 eatmydata package included, and the post-base-installer.d hook in
2045 Debian Edu can only operate on packages included in the ISO. The
2046 negative effect of this is that I am unable to activate this
2047 optimization for the kernel installation step in d-i. If the code is
2048 moved to the post-base-installer.d hook, the speedup would be larger
2049 for the entire installation.
</p
>
2051 <p
>I
've implemented this in the
2052 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
2053 git repository, and plan to provide the optimization as part of the
2054 Debian Edu installation. If you want to test this yourself, you can
2055 create two files in the installer (or in an udeb). One shell script
2056 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
2058 <p
><blockquote
><pre
>
2061 . /usr/share/debconf/confmodule
2063 logger -t my-pkgsel
"info: $*
"
2066 logger -t my-pkgsel
"error: $*
"
2068 override_install() {
2069 apt-install eatmydata || true
2070 if [ -x /target/usr/bin/eatmydata ] ; then
2071 for bin in dpkg apt-get aptitude tasksel ; do
2073 # Test that the file exist and have not been diverted already.
2074 if [ -f /target$file ] ; then
2075 info
"diverting $file using eatmydata
"
2076 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
2077 > /target$file.edu
2078 chmod
755 /target$file.edu
2079 in-target dpkg-divert --package debian-edu-config \
2080 --rename --quiet --add $file
2081 ln -sf ./$bin.edu /target$file
2083 error
"unable to divert $file, as it is missing.
"
2087 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
2092 </pre
></blockquote
></p
>
2094 <p
>To clean up, another shell script should go into
2095 /usr/lib/finish-install.d/ with code like this:
2097 <p
><blockquote
><pre
>
2099 . /usr/share/debconf/confmodule
2101 logger -t my-finish-install
"error: $@
"
2103 remove_install_override() {
2104 for bin in dpkg apt-get aptitude tasksel ; do
2106 if [ -x /target$file.edu ] ; then
2108 in-target dpkg-divert --package debian-edu-config \
2109 --rename --quiet --remove $file
2112 error
"Missing divert for $file.
"
2115 sync # Flush file buffers before continuing
2118 remove_install_override
2119 </pre
></blockquote
></p
>
2121 <p
>In Debian Edu, I placed both code fragments in a separate script
2122 edu-eatmydata-install and call it from the pre-pkgsel.d and
2123 finish-install.d scripts.
</p
>
2125 <p
>By now you might ask if this change should get into the normal
2126 Debian installer too? I suspect it should, but am not sure the
2127 current debian-installer coordinators find it useful enough. It also
2128 depend on the side effects of the change. I
'm not aware of any, but I
2129 guess we will see if the change is safe after some more testing.
2130 Perhaps there is some package in Debian depending on sync() and
2131 fsync() having effect? Perhaps it should go into its own udeb, to
2132 allow those of us wanting to enable it to do so without affecting
2135 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
2136 will break installation of all programs using gnutls because of
2137 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
2138 eatmydata package in Debian will solve it.
</p
>
2140 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
2141 the optimization work again. And I have discovered that the
2142 dpkg-divert trick is not really needed and implemented a slightly
2143 simpler approach as part of the debian-edu-install package. See
2144 tools/edu-eatmydata-install in the source package.
</p
>
2146 <p
>Update
2014-
11-
11: Unfortunately, a new
2147 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
2148 triggering on i386 made it into testing, and broke this installation
2149 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
2150 request
768893</a
> is accepted, it should be working again.
</p
>
2155 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
2156 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
2157 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
2158 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
2159 <description><p
>Yesterday, I had the pleasure of attending a talk with the
2160 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
2161 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
2162 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
2163 learn that there is a large set of publicly available key servers to
2164 use when looking for peoples public key. So far I have used
2165 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
2166 were misbehaving, but those days are ended. The servers I have used
2167 up until yesterday have been slow and some times unavailable. I hope
2168 those problems are gone now.
</p
>
2170 <p
>Behind the round robin DNS entry of the
2171 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
2172 there is a pool of more than
100 keyservers which are checked every
2173 day to ensure they are well connected and up to date. It must be
2174 better than what I have used so far. :)
</p
>
2176 <p
>Yesterdays speaker told me that the service is the default
2177 keyserver provided by the default configuration in GnuPG, but this do
2178 not seem to be used in Debian. Perhaps it should?
</p
>
2180 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
2183 <p
><blockquote
><pre
>
2184 keyserver pool.sks-keyservers.net
2185 </pre
></blockquote
></p
>
2187 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
2188 entries in DNS. Just for fun, I did just that at work, so now every
2189 user of GnuPG at the University of Oslo should find a OpenGPG
2190 keyserver automatically should their need it:
</p
>
2192 <p
><blockquote
><pre
>
2193 % host -t srv _pgpkey-http._tcp.uio.no
2194 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
2196 </pre
></blockquote
></p
>
2198 <p
>Now if only
2199 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
2200 HKP lookup protocol
</a
> supported finding signature paths, I would be
2201 very happy. It can look up a given key or search for a user ID, but I
2202 normally do not want that, but to find a trust path from my key to
2203 another key. Given a user ID or key ID, I would like to find (and
2204 download) the keys representing a signature path from my key to the
2205 key in question, to be able to get a trust path between the two keys.
2206 This is as far as I can tell not possible today. Perhaps something
2207 for a future version of the protocol?
</p
>
2212 <title>From English wiki to translated PDF and epub via Docbook
</title>
2213 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
2214 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
2215 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
2216 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2217 project
</a
> provide an instruction manual for teachers, system
2218 administrators and other users that contain useful tips for setting up
2219 and maintaining a Debian Edu installation. This text is about how the
2220 text processing of this manual is handled in the project.
</p
>
2222 <p
>One goal of the project is to provide information in the native
2223 language of its users, and for this we need to handle translations.
2224 But we also want to make sure each language contain the same
2225 information, so for this we need a good way to keep the translations
2226 in sync. And we want it to be easy for our users to improve the
2227 documentation, avoiding the need to learn special formats or tools to
2228 contribute, and the obvious way to do this is to make it possible to
2229 edit the documentation using a web browser. We also want it to be
2230 easy for translators to keep the translation up to date, and give them
2231 help in figuring out what need to be translated. Here is the list of
2232 tools and the process we have found trying to reach all these
2235 <p
>We maintain the authoritative source of our manual in the
2236 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
2237 wiki
</a
>, as several wiki pages written in English. It consist of one
2238 front page with references to the different chapters, several pages
2239 for each chapter, and finally one
"collection page
" gluing all the
2240 chapters together into one large web page (aka
2241 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
2242 AllInOne page
</a
>). The AllInOne page is the one used for further
2243 processing and translations. Thanks to the fact that the
2244 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
2245 wiki.debian.org support exporting pages in
2246 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
2247 the list of pages to export using the raw version of the AllInOne
2248 page, loop over each of them to generate a Docbook XML version of the
2249 manual. This process also download images and transform image
2250 references to use the locally downloaded images. The generated
2251 Docbook XML files are slightly broken, so some post-processing is done
2252 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
2253 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
2254 a handfull of images. The XML file can now be used to generate PDF, HTML
2255 and epub versions of the English manual. This is the basic step of
2256 our process, making PDF (using dblatex), HTML (using xsltproc) and
2257 epub (using dbtoepub) version from Docbook XML, and the resulting files
2258 are placed in the debian-edu-doc-en binary package.
</p
>
2260 <p
>But English documentation is not enough for us. We want translated
2261 documentation too, and we want to make it easy for translators to
2262 track the English original. For this we use the
2263 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
2264 which allow us to transform the English Docbook XML file into a
2265 translation file (a .pot file), usable with the normal gettext based
2266 translation tools used by those translating free software. The pot
2267 file is used to create and maintain translation files (several .po
2268 files), which the translations update with the native language
2269 translations of all titles, paragraphs and blocks of text in the
2270 original. The next step is combining the original English Docbook XML
2271 and the translation file (say debian-edu-wheezy-manual.nb.po), to
2272 create a translated Docbook XML file (in this case
2273 debian-edu-wheezy-manual.nb.xml). This translated (or partly
2274 translated, if the translation is not complete) Docbook XML file can
2275 then be used like the original to create a PDF, HTML and epub version
2276 of the documentation.
</p
>
2278 <p
>The translators use different tools to edit the .po files. We
2280 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
2281 while some use emacs and vi, others can use web based editors like
2282 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
2283 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
2284 is where the .po file end up, in our git repository. Updated
2285 translations can either be committed directly to git, or submitted as
2286 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
2287 against the debian-edu-doc package
</a
>.
</p
>
2289 <p
>One challenge is images, which both might need to be translated (if
2290 they show translated user applications), and are needed in different
2291 formats when creating PDF and HTML versions (epub is a HTML version in
2292 this regard). For this we transform the original PNG images to the
2293 needed density and format during build, and have a way to provide
2294 translated images by storing translated versions in
2295 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
2296 package maintainers know more.
</p
>
2298 <p
>If you wonder what the result look like, we provide
2299 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
2300 of the documentation packages on the web
</a
>. See for example the
2301 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
2302 PDF version
</a
> or the
2303 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
2304 HTML version
</a
>. We do not yet build the epub version by default,
2305 but perhaps it will be done in the future.
</p
>
2307 <p
>To learn more, check out
2308 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
2309 debian-edu-doc package
</a
>,
2310 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
2311 manual on the wiki
</a
> and
2312 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
2313 translation instructions
</a
> in the manual.
</p
>
2318 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
2319 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
2320 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
2321 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
2322 <description><p
>It would be nice if it was easier in Debian to get all the hardware
2323 related packages relevant for the computer installed automatically.
2324 So I implemented one, using
2325 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
2326 package
</a
>. To use it, install the tasksel and isenkram packages and
2327 run tasksel as user root. You should be presented with a new option,
2328 "Hardware specific packages (autodetected by isenkram)
". When you
2329 select it, tasksel will install the packages isenkram claim is fit for
2330 the current hardware, hot pluggable or not.
<p
>
2332 <p
>The implementation is in two files, one is the tasksel menu entry
2333 description, and the other is the script used to extract the list of
2334 packages to install. The first part is in
2335 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
2338 <p
><blockquote
><pre
>
2341 Description: Hardware specific packages (autodetected by isenkram)
2342 Based on the detected hardware various hardware specific packages are
2344 Test-new-install: mark show
2346 Packages: for-current-hardware
2347 </pre
></blockquote
></p
>
2349 <p
>The second part is in
2350 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
2353 <p
><blockquote
><pre
>
2358 isenkram-autoinstall-firmware -l
2360 </pre
></blockquote
></p
>
2362 <p
>All in all, a very short and simple implementation making it
2363 trivial to install the hardware dependent package we all may want to
2364 have installed on our machines. I
've not been able to find a way to
2365 get tasksel to tell you exactly which packages it plan to install
2366 before doing the installation. So if you are curious or careful,
2367 check the output from the isenkram-* command line tools first.
</p
>
2369 <p
>The information about which packages are handling which hardware is
2370 fetched either from the isenkram package itself in
2371 /usr/share/isenkram/, from git.debian.org or from the APT package
2372 database (using the Modaliases header). The APT package database
2373 parsing have caused a nasty resource leak in the isenkram daemon (bugs
2374 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
2375 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
2376 the python-apt code (bug
2377 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
2378 workaround I was able to get rid of the file descriptor leak and
2379 reduce the memory leak from ~
30 MiB per hardware detection down to
2380 around
2 MiB per hardware detection. It should make the desktop
2381 daemon a lot more useful. The fix is in version
0.7 uploaded to
2382 unstable today.
</p
>
2384 <p
>I believe the current way of mapping hardware to packages in
2385 Isenkram is is a good draft, but in the future I expect isenkram to
2386 use the AppStream data source for this. A proposal for getting proper
2387 AppStream support into Debian is floating around as
2388 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
2389 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
2390 project
</a
> will take place this summer to improve the situation. I
2391 look forward to seeing the result, and welcome patches for isenkram to
2392 start using the information when it is ready.
</p
>
2394 <p
>If you want your package to map to some specific hardware, either
2395 add a
"Xb-Modaliases
" header to your control file like I did in
2396 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
2397 package
</a
> or submit a bug report with the details to the isenkram
2399 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
2400 blog posts tagged isenkram
</a
> for details on the notation. I expect
2401 the information will be migrated to AppStream eventually, but for the
2402 moment I got no better place to store it.
</p
>
2407 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
2408 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
2409 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
2410 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
2411 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
2412 project
</a
> is working on providing the software and hardware to make
2413 it easy for non-technical people to host their data and communication
2414 at home, and being able to communicate with their friends and family
2415 encrypted and away from prying eyes. It is still going strong, and
2416 today a major mile stone was reached.
</p
>
2418 <p
>Today, the last of the packages currently used by the project to
2419 created the system images were accepted into Debian Unstable. It was
2420 the freedombox-setup package, which is used to configure the images
2421 during build and on the first boot. Now all one need to get going is
2422 the build code from the freedom-maker git repository and packages from
2423 Debian. And once the freedombox-setup package enter testing, we can
2424 build everything directly from Debian. :)
</p
>
2426 <p
>Some key packages used by Freedombox are
2427 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
2428 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
2429 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
2430 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
2431 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
2432 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
2433 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
2434 are plans to integrate more packages into the setup. User
2435 documentation is maintained on the Debian wiki. Please
2436 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
2437 the manual
</a
> and help us improve it.
</p
>
2439 <p
>To test for yourself and create boot images with the FreedomBox
2440 setup, run this on a Debian machine using a user with sudo rights to
2441 become root:
</p
>
2443 <p
><pre
>
2444 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2445 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2447 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2449 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2450 </pre
></p
>
2452 <p
>Root access is needed to run debootstrap and mount loopback
2453 devices. See the README in the freedom-maker git repo for more
2454 details on the build. If you do not want all three images, trim the
2455 make line. Note that the virtualbox-image target is not really
2456 virtualbox specific. It create a x86 image usable in kvm, qemu,
2457 vmware and any other x86 virtual machine environment. You might need
2458 the version of vmdebootstrap in Jessie to get the build working, as it
2459 include fixes for a race condition with kpartx.
</p
>
2461 <p
>If you instead want to install using a Debian CD and the preseed
2462 method, boot a Debian Wheezy ISO and use this boot argument to load
2463 the preseed values:
</p
>
2465 <p
><pre
>
2466 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
2467 </pre
></p
>
2469 <p
>I have not tested it myself the last few weeks, so I do not know if
2470 it still work.
</p
>
2472 <p
>If you wonder how to help, one task you could look at is using
2473 systemd as the boot system. It will become the default for Linux in
2474 Jessie, so we need to make sure it is usable on the Freedombox. I did
2475 a simple test a few weeks ago, and noticed dnsmasq failed to start
2476 during boot when using systemd. I suspect there are other problems
2477 too. :) To detect problems, there is a test suite included, which can
2478 be run from the plinth web interface.
</p
>
2480 <p
>Give it a go and let us know how it goes on the mailing list, and help
2481 us get the new release published. :) Please join us on
2482 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
2483 irc.debian.org)
</a
> and
2484 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2485 mailing list
</a
> if you want to help make this vision come true.
</p
>
2490 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
2491 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
2492 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
2493 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
2494 <description><p
>For a while now, I have been looking for a sensible offsite backup
2495 solution for use at home. My requirements are simple, it must be
2496 cheap and locally encrypted (in other words, I keep the encryption
2497 keys, the storage provider do not have access to my private files).
2498 One idea me and my friends had many years ago, before the cloud
2499 storage providers showed up, was to use Google mail as storage,
2500 writing a Linux block device storing blocks as emails in the mail
2501 service provided by Google, and thus get heaps of free space. On top
2502 of this one can add encryption, RAID and volume management to have
2503 lots of (fairly slow, I admit that) cheap and encrypted storage. But
2504 I never found time to implement such system. But the last few weeks I
2505 have looked at a system called
2506 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
2507 mounted network backed file system with the features I need.
</p
>
2509 <p
>S3QL is a fuse file system with a local cache and cloud storage,
2510 handling several different storage providers, any with Amazon S3,
2511 Google Drive or OpenStack API. There are heaps of such storage
2512 providers. S3QL can also use a local directory as storage, which
2513 combined with sshfs allow for file storage on any ssh server. S3QL
2514 include support for encryption, compression, de-duplication, snapshots
2515 and immutable file systems, allowing me to mount the remote storage as
2516 a local mount point, look at and use the files as if they were local,
2517 while the content is stored in the cloud as well. This allow me to
2518 have a backup that should survive fire. The file system can not be
2519 shared between several machines at the same time, as only one can
2520 mount it at the time, but any machine with the encryption key and
2521 access to the storage service can mount it if it is unmounted.
</p
>
2523 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
2524 package is included already. So to get started, run
<tt
>apt-get
2525 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
2526 Greenqloud, after reading their nice recipe on
2527 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
2528 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
2529 in Iceland more than those in USA when it come to keeping my personal
2530 data safe and private, and thus would rather spend money on a company
2531 in Iceland. Another nice recipe is available from the article
2532 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
2533 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
2534 Admin magazine. When the provider is picked, figure out how to get
2535 the API key needed to connect to the storage API. With Greencloud,
2536 the key did not show up until I had added payment details to my
2539 <p
>Armed with the API access details, it is time to create the file
2540 system. First, create a new bucket in the cloud. This bucket is the
2541 file system storage area. I picked a bucket name reflecting the
2542 machine that was going to store data there, but any name will do.
2543 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
2544 the API login and password, and a locally created password. Store it
2545 all in ~root/.s3ql/authinfo2 like this:
2547 <p
><blockquote
><pre
>
2549 storage-url: s3c://s.greenqloud.com:
443/bucket-name
2550 backend-login: API-login
2551 backend-password: API-password
2552 fs-passphrase: local-password
2553 </pre
></blockquote
></p
>
2555 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
2556 but any sensible way to create a fairly random password should do it.
2557 Armed with these details, it is now time to run mkfs, entering the API
2558 details and password to create it:
</p
>
2560 <p
><blockquote
><pre
>
2561 # mkdir -m
700 /var/lib/s3ql-cache
2562 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2563 --ssl s3c://s.greenqloud.com:
443/bucket-name
2564 Enter backend login:
2565 Enter backend password:
2566 Before using S3QL, make sure to read the user
's guide, especially
2567 the
'Important Rules to Avoid Loosing Data
' section.
2568 Enter encryption password:
2569 Confirm encryption password:
2570 Generating random encryption key...
2571 Creating metadata tables...
2581 Compressing and uploading metadata...
2582 Wrote
0.00 MB of compressed metadata.
2583 #
</pre
></blockquote
></p
>
2585 <p
>The next step is mounting the file system to make the storage available.
2587 <p
><blockquote
><pre
>
2588 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2589 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2590 Using
4 upload threads.
2591 Downloading and decompressing metadata...
2601 Mounting filesystem...
2603 Filesystem Size Used Avail Use% Mounted on
2604 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
2606 </pre
></blockquote
></p
>
2608 <p
>The file system is now ready for use. I use rsync to store my
2609 backups in it, and as the metadata used by rsync is downloaded at
2610 mount time, no network traffic (and storage cost) is triggered by
2611 running rsync. To unmount, one should not use the normal umount
2612 command, as this will not flush the cache to the cloud storage, but
2613 instead running the umount.s3ql command like this:
2615 <p
><blockquote
><pre
>
2618 </pre
></blockquote
></p
>
2620 <p
>There is a fsck command available to check the file system and
2621 correct any problems detected. This can be used if the local server
2622 crashes while the file system is mounted, to reset the
"already
2623 mounted
" flag. This is what it look like when processing a working
2624 file system:
</p
>
2626 <p
><blockquote
><pre
>
2627 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
2628 Using cached metadata.
2629 File system seems clean, checking anyway.
2630 Checking DB integrity...
2631 Creating temporary extra indices...
2632 Checking lost+found...
2633 Checking cached objects...
2634 Checking names (refcounts)...
2635 Checking contents (names)...
2636 Checking contents (inodes)...
2637 Checking contents (parent inodes)...
2638 Checking objects (reference counts)...
2639 Checking objects (backend)...
2640 ..processed
5000 objects so far..
2641 ..processed
10000 objects so far..
2642 ..processed
15000 objects so far..
2643 Checking objects (sizes)...
2644 Checking blocks (referenced objects)...
2645 Checking blocks (refcounts)...
2646 Checking inode-block mapping (blocks)...
2647 Checking inode-block mapping (inodes)...
2648 Checking inodes (refcounts)...
2649 Checking inodes (sizes)...
2650 Checking extended attributes (names)...
2651 Checking extended attributes (inodes)...
2652 Checking symlinks (inodes)...
2653 Checking directory reachability...
2654 Checking unix conventions...
2655 Checking referential integrity...
2656 Dropping temporary indices...
2657 Backing up old metadata...
2667 Compressing and uploading metadata...
2668 Wrote
0.89 MB of compressed metadata.
2670 </pre
></blockquote
></p
>
2672 <p
>Thanks to the cache, working on files that fit in the cache is very
2673 quick, about the same speed as local file access. Uploading large
2674 amount of data is to me limited by the bandwidth out of and into my
2675 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
2676 which is very close to my upload speed, and downloading the same
2677 Debian installation ISO gave me
610 kiB/s, close to my download speed.
2678 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
2679 network, not the file system code. I do not know what a good cache
2680 size would be, but suspect that the cache should e larger than your
2681 working set.
</p
>
2683 <p
>I mentioned that only one machine can mount the file system at the
2684 time. If another machine try, it is told that the file system is
2687 <p
><blockquote
><pre
>
2688 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2689 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2690 Using
8 upload threads.
2691 Backend reports that fs is still mounted elsewhere, aborting.
2693 </pre
></blockquote
></p
>
2695 <p
>The file content is uploaded when the cache is full, while the
2696 metadata is uploaded once every
24 hour by default. To ensure the
2697 file system content is flushed to the cloud, one can either umount the
2698 file system, or ask S3QL to flush the cache and metadata using
2701 <p
><blockquote
><pre
>
2702 # s3qlctrl upload-meta /s3ql
2703 # s3qlctrl flushcache /s3ql
2705 </pre
></blockquote
></p
>
2707 <p
>If you are curious about how much space your data uses in the
2708 cloud, and how much compression and deduplication cut down on the
2709 storage usage, you can use s3qlstat on the mounted file system to get
2712 <p
><blockquote
><pre
>
2714 Directory entries:
9141
2717 Total data size:
22049.38 MB
2718 After de-duplication:
21955.46 MB (
99.57% of total)
2719 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
2720 Database size:
2.39 MB (uncompressed)
2721 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2723 </pre
></blockquote
></p
>
2725 <p
>I mentioned earlier that there are several possible suppliers of
2726 storage. I did not try to locate them all, but am aware of at least
2727 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
2728 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
2729 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
2730 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
2731 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
2732 accept payment in Bitcoin. Pick one that suit your need. Some of
2733 them provide several GiB of free storage, but the prize models are
2734 quite different and you will have to figure out what suits you
2737 <p
>While researching this blog post, I had a look at research papers
2738 and posters discussing the S3QL file system. There are several, which
2739 told me that the file system is getting a critical check by the
2740 science community and increased my confidence in using it. One nice
2742 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
2743 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2744 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
2745 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2746 and Pamela Smith. Please have a look.
</p
>
2748 <p
>Given my problems with different file systems earlier, I decided to
2749 check out the mounted S3QL file system to see if it would be usable as
2750 a home directory (in other word, that it provided POSIX semantics when
2751 it come to locking and umask handling etc). Running
2752 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
2753 test code to check file system semantics
</a
>, I was happy to discover that
2754 no error was found. So the file system can be used for home
2755 directories, if one chooses to do so.
</p
>
2757 <p
>If you do not want a locally file system, and want something that
2758 work without the Linux fuse file system, I would like to mention the
2759 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
2760 provide locally encrypted backup using a command line client. It have
2761 a nicer access control system, where one can split out read and write
2762 access, allowing some systems to write to the backup and others to
2763 only read from it.
</p
>
2765 <p
>As usual, if you use Bitcoin and want to show your support of my
2766 activities, please send Bitcoin donations to my address
2767 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2772 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
2773 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
2774 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
2775 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
2776 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
2777 project
</a
> is working on providing the software and hardware for
2778 making it easy for non-technical people to host their data and
2779 communication at home, and being able to communicate with their
2780 friends and family encrypted and away from prying eyes. It has been
2781 going on for a while, and is slowly progressing towards a new test
2782 release (
0.2).
</p
>
2784 <p
>And what day could be better than the Pi day to announce that the
2785 new version will provide
"hard drive
" / SD card / USB stick images for
2786 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2787 system), and can also be installed using a Debian installer preseed
2788 file. The Debian based Freedombox is now based on Debian Jessie,
2789 where most of the needed packages used are already present. Only one,
2790 the freedombox-setup package, is missing. To try to build your own
2791 boot image to test the current status, fetch the freedom-maker scripts
2793 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
2794 with a user with sudo access to become root:
2797 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2799 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2800 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2802 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2805 <p
>Root access is needed to run debootstrap and mount loopback
2806 devices. See the README for more details on the build. If you do not
2807 want all three images, trim the make line. But note that thanks to
<a
2808 href=
"https://bugs.debian.org/
741407">a race condition in
2809 vmdebootstrap
</a
>, the build might fail without the patch to the
2810 kpartx call.
</p
>
2812 <p
>If you instead want to install using a Debian CD and the preseed
2813 method, boot a Debian Wheezy ISO and use this boot argument to load
2814 the preseed values:
</p
>
2817 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
2820 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
2821 recently introduced bug in apt in Jessie
</a
>, the installer will
2822 currently hang while setting up APT sources. Killing the
2823 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
2824 installation will get the installation going. This affect all
2825 installations in Jessie, and I expect it will be fixed soon.
</p
>
2827 <p
>Give it a go and let us know how it goes on the mailing list, and help
2828 us get the new release published. :) Please join us on
2829 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
2830 irc.debian.org)
</a
> and
2831 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2832 mailing list
</a
> if you want to help make this vision come true.
</p
>
2837 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
2838 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
2839 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
2840 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
2841 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
2842 innetgr tools, because I needed them in
2843 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
2844 ng-utils, and it has served me well. I placed the project under the
2845 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
2846 repository. But many years ago, the CVS repository was dropped (lost,
2847 not migrated to new hardware, not sure), and the project have lacked a
2848 proper home since then.
</p
>
2850 <p
>Last summer, I had a look at the package and made a new release
2851 fixing a irritating crash bug, but was unable to store the changes in
2852 a proper source control system. I applied for a project on
2853 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
2854 to follow up on it. Until today. :)
</p
>
2856 <p
>After many hours of cleaning and migration, the ng-utils project
2857 now have a new home, and a git repository with the highlight of the
2858 history of the project. I published all release tarballs and imported
2859 them into the git repository. As the project is really stable and not
2860 expected to gain new features any time soon, I decided to make a new
2861 release and call it
1.0. Visit the new project home on
2862 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
2863 if you want to check it out. The new version is also uploaded into
2864 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
2869 <title>Testing sysvinit from experimental in Debian Hurd
</title>
2870 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
2871 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
2872 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
2873 <description><p
>A few days ago I decided to try to help the Hurd people to get
2874 their changes into sysvinit, to allow them to use the normal sysvinit
2875 boot system instead of their old one. This follow up on the
2876 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
2877 Google Summer of Code work
</a
> done last summer by Justus Winter to
2878 get Debian on Hurd working more like Debian on Linux. To get started,
2879 I downloaded a prebuilt hard disk image from
2880 <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
>,
2881 and started it using virt-manager.
</p
>
2883 <p
>The first think I had to do after logging in (root without any
2884 password) was to get the network operational. I followed
2885 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
2886 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
2887 commands as root to get the machine to accept a IP address from the
2888 kvm internal DHCP server:
</p
>
2890 <p
><blockquote
><pre
>
2891 settrans -fgap /dev/netdde /hurd/netdde
2892 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
2893 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
2895 </pre
></blockquote
></p
>
2897 <p
>After this, the machine had internet connectivity, and I could
2898 upgrade it and install the sysvinit packages from experimental and
2899 enable it as the default boot system in Hurd.
</p
>
2901 <p
>But before I did that, I set a password on the root user, as ssh is
2902 running on the machine it for ssh login to work a password need to be
2903 set. Also, note that a bug somewhere in openssh on Hurd block
2904 compression from working. Remember to turn that off on the client
2907 <p
>Run these commands as root to upgrade and test the new sysvinit
2910 <p
><blockquote
><pre
>
2911 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
2912 deb http://http.debian.net/debian/ experimental main
2915 apt-get dist-upgrade
2916 apt-get install -t experimental initscripts sysv-rc sysvinit \
2917 sysvinit-core sysvinit-utils
2918 update-alternatives --config runsystem
2919 </pre
></blockquote
></p
>
2921 <p
>To reboot after switching boot system, you have to use
2922 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
2923 yet a sysvinit process able to receive the signals from the normal
2924 'reboot
' command. After switching to sysvinit as the boot system,
2925 upgrading every package and rebooting, the network come up with DHCP
2926 after boot as it should, and the settrans/pkill hack mentioned at the
2927 start is no longer needed. But for some strange reason, there are no
2928 longer any login prompt in the virtual console, so I logged in using
2931 <p
>Note that there are some race conditions in Hurd making the boot
2932 fail some times. No idea what the cause is, but hope the Hurd porters
2933 figure it out. At least Justus said on IRC (#debian-hurd on
2934 irc.debian.org) that they are aware of the problem. A way to reduce
2935 the impact is to upgrade to the Hurd packages built by Justus by
2936 adding this repository to the machine:
</p
>
2938 <p
><blockquote
><pre
>
2939 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
2940 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2942 </pre
></blockquote
></p
>
2944 <p
>At the moment the prebuilt virtual machine get some packages from
2945 http://ftp.debian-ports.org/debian, because some of the packages in
2946 unstable do not yet include the required patches that are lingering in
2947 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
2949 <p
><blockquote
><pre
>
2950 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
2951 i emacs - GNU Emacs editor (metapackage)
2952 i gdb - GNU Debugger
2953 i hurd-recommended - Miscellaneous translators
2954 i isc-dhcp-client - ISC DHCP client
2955 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2956 i libc-bin - Embedded GNU C Library: Binaries
2957 i libc-dev-bin - Embedded GNU C Library: Development binaries
2958 i libc0.3 - Embedded GNU C Library: Shared libraries
2959 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2960 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2961 i multiarch-support - Transitional package to ensure multiarch compatibilit
2962 i A x11-common - X Window System (X.Org) infrastructure
2963 i xorg - X.Org X Window System
2964 i A xserver-xorg - X.Org X server
2965 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2967 </pre
></blockquote
></p
>
2969 <p
>All in all, testing hurd has been an interesting experience. :)
2970 X.org did not work out of the box and I never took the time to follow
2971 the porters instructions to fix it. This time I was interested in the
2972 command line stuff.
<p
>
2977 <title>New chrpath release
0.16</title>
2978 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
2979 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
2980 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
2981 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
2982 find problems in C, C++ and Java code using static source code
2983 analysis. It can detect a lot of different problems, and is very
2984 useful to find memory and locking bugs in the error handling part of
2985 the source. The company behind it provide
2986 <a href=
"https://scan.coverity.com/
">check of free software projects as
2987 a community service
</a
>, and many hundred free software projects are
2988 already checked. A few days ago I decided to have a closer look at
2989 the Coverity system, and discovered that the
2990 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
2991 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
2992 projects I am involved with was already registered. But these are
2993 fairly big, and I would also like to have a small and easy project to
2994 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
2995 checking of the chrpath project
</a
>. It was
2996 added to the checker and discovered seven potential defects. Six of
2997 these were real, mostly resource
"leak
" when the program detected an
2998 error. Nothing serious, as the resources would be released a fraction
2999 of a second later when the program exited because of the error, but it
3000 is nice to do it right in case the source of the program some time in
3001 the future end up in a library. Having fixed all defects and added
3002 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
3003 mailing list for the chrpath developers
</a
>, I decided it was time to
3004 publish a new release. These are the release notes:
</p
>
3006 <p
>New in
0.16 released
2014-
01-
14:
</p
>
3010 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
3011 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
3012 <li
>Mention new project mailing list in the documentation.
</li
>
3017 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3018 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
3019 project if something is wrong with the new release. The test suite
3020 did not discover any old errors, so if you find a new one, please also
3021 include a test suite check.
</p
>
3026 <title>New chrpath release
0.15</title>
3027 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
3028 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
3029 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
3030 <description><p
>After many years break from the package and a vain hope that
3031 development would be continued by someone else, I finally pulled my
3032 acts together this morning and wrapped up a new release of chrpath,
3033 the command line tool to modify the rpath and runpath of already
3034 compiled ELF programs. The update was triggered by the persistence of
3035 Isha Vishnoi at IBM, which needed a new config.guess file to get
3036 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
3037 is working on. I checked the
3038 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
3039 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
3040 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
3041 packages for interesting patches (failed to find the source from
3042 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
3043 These are the release notes:
</p
>
3045 <p
>New in
0.15 released
2013-
11-
24:
</p
>
3049 <li
>Updated config.sub and config.guess from the GNU project to work
3050 with newer architectures. Thanks to isha vishnoi for the heads
3053 <li
>Updated README with current URLs.
</li
>
3055 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
3056 Matthias Klose.
</li
>
3058 <li
>Added missing help for -k|--keepgoing option, using patch by
3059 Petr Machata found in Fedora.
</li
>
3061 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
3062 .dynamic is a NULL terminated string. Based on patch found in
3063 Fedora credited Axel Thimm and Christian Krause.
</li
>
3068 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3069 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
3070 project if something is wrong with the new release. The test suite
3071 did not discover any old errors, so if you find a new one, please also
3072 include a testsuite check.
</p
>
3077 <title>Debian init.d boot script example for rsyslog
</title>
3078 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
3079 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
3080 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
3081 <description><p
>If one of the points of switching to a new init system in Debian is
3082 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
3083 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
3084 init.d scripts at all. Here is an example init.d script, ie a rewrite
3085 of /etc/init.d/rsyslog:
</p
>
3087 <p
><pre
>
3088 #!/lib/init/init-d-script
3091 # Required-Start: $remote_fs $time
3092 # Required-Stop: umountnfs $time
3093 # X-Stop-After: sendsigs
3094 # Default-Start:
2 3 4 5
3095 # Default-Stop:
0 1 6
3096 # Short-Description: enhanced syslogd
3097 # Description: Rsyslog is an enhanced multi-threaded syslogd.
3098 # It is quite compatible to stock sysklogd and can be
3099 # used as a drop-in replacement.
3101 DESC=
"enhanced syslogd
"
3102 DAEMON=/usr/sbin/rsyslogd
3103 </pre
></p
>
3105 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
3106 script was
137 lines, and the above is just
15 lines, most of it meta
3107 info/comments.
</p
>
3109 <p
>How to do this, you ask? Well, one create a new script
3110 /lib/init/init-d-script looking something like this:
3112 <p
><pre
>
3115 # Define LSB log_* functions.
3116 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
3117 # and status_of_proc is working.
3118 . /lib/lsb/init-functions
3121 # Function that starts the daemon/service
3127 #
0 if daemon has been started
3128 #
1 if daemon was already running
3129 #
2 if daemon could not be started
3130 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
3132 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
3135 # Add code here, if necessary, that waits for the process to be ready
3136 # to handle requests from services started subsequently which depend
3137 # on this one. As a last resort, sleep for some time.
3141 # Function that stops the daemon/service
3146 #
0 if daemon has been stopped
3147 #
1 if daemon was already stopped
3148 #
2 if daemon could not be stopped
3149 # other if a failure occurred
3150 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
3151 RETVAL=
"$?
"
3152 [
"$RETVAL
" =
2 ]
&& return
2
3153 # Wait for children to finish too if this is a daemon that forks
3154 # and if the daemon is only ever run from this initscript.
3155 # If the above conditions are not satisfied then add some other code
3156 # that waits for the process to drop all resources that could be
3157 # needed by services started subsequently. A last resort is to
3158 # sleep for some time.
3159 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
3160 [
"$?
" =
2 ]
&& return
2
3161 # Many daemons don
't delete their pidfiles when they exit.
3163 return
"$RETVAL
"
3167 # Function that sends a SIGHUP to the daemon/service
3171 # If the daemon can reload its configuration without
3172 # restarting (for example, when it is sent a SIGHUP),
3173 # then implement that here.
3175 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
3180 scriptbasename=
"$(basename $
1)
"
3181 echo
"SN: $scriptbasename
"
3182 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
3183 script=
"$
1"
3190 NAME=$(basename $DAEMON)
3191 PIDFILE=/var/run/$NAME.pid
3193 # Exit if the package is not installed
3194 #[ -x
"$DAEMON
" ] || exit
0
3196 # Read configuration variable file if it is present
3197 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
3199 # Load the VERBOSE setting and other rcS variables
3202 case
"$
1" in
3204 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
3206 case
"$?
" in
3207 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3208 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3212 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
3214 case
"$?
" in
3215 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3216 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3220 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
3222 #reload|force-reload)
3224 # If do_reload() is not implemented then leave this commented out
3225 # and leave
'force-reload
' as an alias for
'restart
'.
3227 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
3231 restart|force-reload)
3233 # If the
"reload
" option is implemented then remove the
3234 #
'force-reload
' alias
3236 log_daemon_msg
"Restarting $DESC
" "$NAME
"
3238 case
"$?
" in
3241 case
"$?
" in
3243 1) log_end_msg
1 ;; # Old process is still running
3244 *) log_end_msg
1 ;; # Failed to start
3254 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
3260 </pre
></p
>
3262 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
3263 lot. I did not really polish the approach, so it might not always
3264 work out of the box, but you get the idea. I did not try very hard to
3265 optimize it nor make it more robust either.
</p
>
3267 <p
>A better argument for switching init system in Debian than reducing
3268 the size of init scripts (which is a good thing to do anyway), is to
3269 get boot system that is able to handle the kernel events sensibly and
3270 robustly, and do not depend on the boot to run sequentially. The boot
3271 and the kernel have not behaved sequentially in years.
</p
>
3276 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
3277 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
3278 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
3279 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
3280 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
3281 remote display access is the preferred solution with oVirt and RedHat
3282 Enterprise Virtualization, and I was sad to discover the other day
3283 that the browser plugin needed to use these systems seamlessly was
3284 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
3285 for a package
</a
> was from
2012-
04-
10 with no progress since
3286 2013-
04-
01, so I decided to wrap up a package based on the great work
3287 from Cajus Pollmeier and put it in a collab-maint maintained git
3288 repository to get a package I could use. I would very much like
3289 others to help me maintain the package (or just take over, I do not
3290 mind), but as no-one had volunteered so far, I just uploaded it to
3291 NEW. I hope it will be available in Debian in a few days.
</p
>
3293 <p
>The source is now available from
3294 <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
>
3299 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
3300 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
3301 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
3302 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
3303 <description><p
>The
3304 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
3305 program is a a very nice system to create virtual machine images. It
3306 create a image file, add a partition table, mount it and run
3307 debootstrap in the mounted directory to create a Debian system on a
3308 stick. Yesterday, I decided to try to teach it how to make images for
3309 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
3310 of a plan to simplify the build system for
3311 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
3312 project
</a
>. The FreedomBox project already uses vmdebootstrap for
3313 the virtualbox images, but its current build system made multistrap
3314 based system for Dreamplug images, and it is lacking support for
3315 Raspberry Pi.
</p
>
3317 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
3318 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
3319 code and adjusted it to be able to build armel images on my amd64
3320 Debian laptop. I ended up giving vmdebootstrap five new options,
3321 allowing me to replicate the image creation process I use to make
3322 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
3323 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
3324 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
3325 call debootstrap with --foreign and to copy the handler into the
3326 generated chroot before running the second stage. This allow
3327 vmdebootstrap to create armel images on an amd64 host. Next I added
3328 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
3329 fstype
</tt
> to teach it to create a separate /boot/ partition with the
3330 given file system type, allowing me to create an image with a vfat
3331 partition for the /boot/ stuff. I also added a
<tt
>--variant
3332 variant
</tt
> option to allow me to create smaller images without the
3333 Debian base system packages installed. Finally, I added an option
3334 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
3335 as a boot loader. It is not needed on the Raspberry Pi and probably
3336 most other non-x86 architectures. The changes were accepted by the
3337 upstream author of vmdebootstrap yesterday and today, and is now
3339 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
3340 upstream project page
</a
>.
</p
>
3342 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
3343 create a small script (the customize script) to add the non-free
3344 binary blob needed to boot the Raspberry Pi and the APT source
3347 <p
><pre
>
3349 set -e # Exit on first error
3350 rootdir=
"$
1"
3351 cd
"$rootdir
"
3352 cat
&lt;
&lt;EOF
> etc/apt/sources.list
3353 deb http://http.debian.net/debian/ jessie main contrib non-free
3355 # Install non-free binary blob needed to boot Raspberry Pi. This
3356 # install a kernel somewhere too.
3357 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
3358 -O $rootdir/usr/bin/rpi-update
3359 chmod a+x $rootdir/usr/bin/rpi-update
3360 mkdir -p $rootdir/lib/modules
3361 touch $rootdir/boot/start.elf
3362 chroot $rootdir rpi-update
3363 </pre
></p
>
3365 <p
>Next, fetch the latest vmdebootstrap script and call it like this
3366 to build the image:
</p
>
3369 sudo ./vmdebootstrap \
3372 --distribution jessie \
3373 --mirror http://http.debian.net/debian \
3382 --root-password raspberry \
3383 --hostname raspberrypi \
3384 --foreign /usr/bin/qemu-arm-static \
3385 --customize `pwd`/customize \
3387 --package git-core \
3388 --package binutils \
3389 --package ca-certificates \
3392 </pre
></p
>
3394 <p
>The list of packages being installed are the ones needed by
3395 rpi-update to make the image bootable on the Raspberry Pi, with the
3396 exception of netbase, which is needed by debootstrap to find
3397 /etc/hosts with the minbase variant. I really wish there was a way to
3398 set up an Raspberry Pi using only packages in the Debian archive, but
3399 that is not possible as far as I know, because it boots from the GPU
3400 using a non-free binary blob.
</p
>
3402 <p
>The build host need debootstrap, kpartx and qemu-user-static and
3403 probably a few others installed. I have not checked the complete
3404 build dependency list.
</p
>
3406 <p
>The resulting image will not use the hardware floating point unit
3407 on the Raspberry PI, because the armel architecture in Debian is not
3408 optimized for that use. So the images created will be a bit slower
3409 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
3414 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
3415 <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>
3416 <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>
3417 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
3418 <description><p
>The last few days I came across a few good causes that should get
3419 wider attention. I recommend signing and donating to each one of
3422 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
3423 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
3424 Women program which is a Google Summer of Code like initiative to get
3425 more women involved in free software. One debian sponsor has offered
3426 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
3427 earmarked
</a
> for this initiative. I donated a few minutes ago, and
3428 hope you will to. :)
</p
>
3430 <p
>And the Electronic Frontier Foundation just announced plans to
3431 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
3432 documentaries about the excessive spying
</a
> on every Internet user that
3433 take place these days, and their need to fund the work. I
've already
3434 donated. Are you next?
</p
>
3436 <p
>For my Norwegian audience, the organisation Studentenes og
3437 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
3438 statement under the heading
3439 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
3440 Access
</a
> for those of us asking for more focus on open access in the
3441 Norwegian government. So far
499 signatures. I hope you will sign it
3447 <title>Videos about the Freedombox project - for inspiration and learning
</title>
3448 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
3449 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
3450 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
3451 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
3452 project
</a
> have been going on for a while, and have presented the
3453 vision, ideas and solution several places. Here is a little
3454 collection of videos of talks and presentation of the project.
</p
>
3458 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
3459 2,
5 minute marketing film
</a
> (Youtube)
</li
>
3461 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
3462 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
3464 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
3465 Freedom in the Cloud - Software Freedom, Privacy and and Security for
3466 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
3467 (Youtube)
</li
>
3469 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
3470 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
3472 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
3473 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
3475 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
3476 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
3477 York City in
2012</a
> (Youtube)
</li
>
3479 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
3480 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
3481 (Youtube)
</li
>
3483 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
3484 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
3486 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
3487 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
3489 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
3490 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
3491 2013</a
> (Youtube)
</li
>
3495 <p
>A larger list is available from
3496 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
3497 Freedombox Wiki
</a
>.
</p
>
3499 <p
>On other news, I am happy to report that Freedombox based on Debian
3500 Jessie is coming along quite well, and soon both Owncloud and using
3501 Tor should be available for testers of the Freedombox solution. :) In
3502 a few weeks I hope everything needed to test it is included in Debian.
3503 The withsqlite package is already in Debian, and the plinth package is
3504 pending in NEW. The third and vital part of that puzzle is the
3505 metapackage/setup framework, which is still pending an upload. Join
3506 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
3507 (#freedombox on irc.debian.org)
</a
> and
3508 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3509 mailing list
</a
> if you want to help make this vision come true.
</p
>
3514 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
3515 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
3516 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
3517 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
3518 <description><p
>I was introduced to the
3519 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
3520 in
2010, when Eben Moglen presented his vision about serving the need
3521 of non-technical people to keep their personal information private and
3522 within the legal protection of their own homes. The idea is to give
3523 people back the power over their network and machines, and return
3524 Internet back to its intended peer-to-peer architecture. Instead of
3525 depending on a central service, the Freedombox will give everyone
3526 control over their own basic infrastructure.
</p
>
3528 <p
>I
've intended to join the effort since then, but other tasks have
3529 taken priority. But this summers nasty news about the misuse of trust
3530 and privilege exercised by the
"western
" intelligence gathering
3531 communities increased my eagerness to contribute to a point where I
3532 actually started working on the project a while back.
</p
>
3534 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
3535 Debian initiative
</a
> based on the vision from Eben Moglen, is to
3536 create a simple and cheap Debian based appliance that anyone can hook
3537 up in their home and get access to secure and private services and
3538 communication. The initial deployment platform have been the
3539 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
3540 which is a piece of hardware I do not own. So to be able to test what
3541 the current Freedombox setup look like, I had to come up with a way to install
3542 it on some hardware I do have access to. I have rewritten the
3543 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
3544 image build framework to use .deb packages instead of only copying
3545 setup into the boot images, and thanks to this rewrite I am able to
3546 set up any machine supported by Debian Wheezy as a Freedombox, using
3547 the previously mentioned deb (and a few support debs for packages
3548 missing in Debian).
</p
>
3550 <p
>The current Freedombox setup consist of a set of bootstrapping
3552 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
3553 and a administrative web interface
3554 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
3555 withsqlite), as well as a privacy enhancing proxy based on
3556 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
3557 (freedombox-privoxy). There is also a web/javascript based XMPP
3558 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
3559 trying (unsuccessfully so far) to talk to the XMPP server
3560 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
3561 web interface is pluggable, and the goal is to use it to enable OpenID
3562 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3563 this is really working yet, see
3564 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
3565 project TODO
</a
> for links to GIT repositories. Most of the code is
3566 on github at the moment. The HTTP proxy is operational out of the
3567 box, and the admin web interface can be used to add/remove plinth
3568 users. I
've not been able to do anything else with it so far, but
3569 know there are several branches spread around github and other places
3570 with lots of half baked features.
</p
>
3572 <p
>Anyway, if you want to have a look at the current state, the
3573 following recipes should work to give you a test machine to poke
3576 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
3580 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
3581 <li
>Boot from it, either as CD or USB stick.
</li
>
3582 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
3583 to the Debian installer:
<p
>
3584 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
3586 <li
>Answer the few language/region/password questions and pick disk to
3587 install on.
</li
>
3589 <li
>When the installation is finished and the machine have rebooted a
3590 few times, your Freedombox is ready for testing.
</li
>
3594 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
3598 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
3599 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
3600 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
3602 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
3603 </pre
></li
>
3604 <li
><p
>Run this as root:
</p
>
3606 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3609 apt-get install freedombox-setup
3610 /usr/lib/freedombox/setup
3611 </pre
></li
>
3612 <li
>Reboot into your freshly created Freedombox.
</li
>
3616 <p
>You can test it on other architectures too, but because the
3617 freedombox-privoxy package is binary, it will only work as intended on
3618 the architectures where I have had time to build the binary and put it
3619 in my APT repository. But do not let this stop you. It is only a
3620 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
3622 <p
>Note that by default Freedombox is a DHCP server on the
3623 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
3624 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
3625 disable
</tt
>" as root.
</p
>
3627 <p
>Please let me know if this works for you, or if you have any
3628 problems. We gather on the IRC channel
3629 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
3630 irc.debian.org and the
3631 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
3632 mailing list
</a
>.
</p
>
3634 <p
>Once you get your freedombox operational, you can visit
3635 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
3636 welcome screen (dead end - do not be surprised if you are unable to
3637 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
3638 to look at the rest of plinth. The default user is
'admin
' and the
3639 default password is
'secret
'.
</p
>
3644 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
3645 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
3646 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
3647 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
3648 <description><p
>Earlier, I reported about
3649 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
3650 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
3651 told by IBM that the original disk should be thrown away. And as
3652 there no longer was a problem if I bricked the firmware, I decided
3653 today to try to install Intel firmware to replace the Lenovo firmware
3654 currently on the disk.
</p
>
3656 <p
>I searched the Intel site for firmware, and found
3657 <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
>
3658 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3659 according to the site should contain the latest firmware for SSD
3660 disks. I inserted the broken disk in one of my spare laptops and
3661 booted the ISO from a USB stick. The disk was recognized, but the
3662 program claimed the newest firmware already were installed and refused
3663 to insert any Intel firmware. So no change, and the disk is still
3664 unable to handle write load. :( I guess the only way to get them
3665 working would be if Lenovo releases new firmware. No idea how likely
3666 that is. Anyway, just blogging about this test for completeness. I
3667 got a working Samsung disk, and see no point in spending more time on
3668 the broken disks.
</p
>
3673 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
3674 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
3675 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
3676 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
3677 <description><p
>Today I switched to
3678 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
3679 new laptop
</a
>. I
've previously written about the problems I had with
3680 my new Thinkpad X230, which was delivered with an
3681 <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
3682 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
3683 sustained writes. My hardware supplier have been very forthcoming in
3684 trying to find a solution, and after first trying with another
3685 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
3686 disk instead to fix it once and for all. The Samsung disk survived
3687 the installation of Debian with encrypted disks (filling the disk with
3688 random data during installation killed the first two), and I thus
3689 decided to trust it with my data. I have installed it as a Debian Edu
3690 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3691 server at home using Kerberos and LDAP, and will use it as my work
3692 station from now on.
</p
>
3694 <p
>As this is a solid state disk with no moving parts, I believe the
3695 Debian Wheezy default installation need to be tuned a bit to increase
3696 performance and increase life time of the disk. The Linux kernel and
3697 user space applications do not yet adjust automatically to such
3698 environment. To make it easier for my self, I created a draft Debian
3699 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
3700 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
3701 for the ssd-setup package
</a
> is available from collab-maint, and it
3702 is set up to adjust the setup of the machine by just installing the
3703 package. If there is any non-SSD disk in the machine, the package
3704 will refuse to install, as I did not try to write any logic to sort
3705 file systems in SSD and non-SSD file systems.
</p
>
3707 <p
>I consider the package a draft, as I am a bit unsure how to best
3708 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3709 where I set up the machine with one large encrypted partition (in
3710 addition to /boot), put LVM on top of this and set up partitions on
3711 top of this again. See the README file in the package source for the
3712 references I used to pick the settings. At the moment these
3713 parameters are tuned:
</p
>
3717 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
3718 (adding discard to /etc/crypttab)
</li
>
3720 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
3721 this case a cryptsetup partition) by changing issue_discards from
3722 0 to
1 in /etc/lvm/lvm.conf.
</li
>
3724 <li
>Set relatime as a file system option for ext3 and ext4 file
3727 <li
>Tell swap to use TRIM commands by adding
'discard
' to
3728 /etc/fstab.
</li
>
3730 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
3732 <li
>Run fstrim on every ext3 and ext4 file system every night (from
3733 cron.daily).
</li
>
3735 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
3736 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
3740 <p
>During installation, I cancelled the part where the installer fill
3741 the disk with random data, as this would kill the SSD performance for
3742 little gain. My goal with the encrypted file system is to ensure
3743 those stealing my laptop end up with a brick and not a working
3744 computer. I have no hope in keeping the really resourceful people
3745 from getting the data on the disk (see
3746 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
3747 Thus I concluded that adding the discard option to crypttab is the
3748 right thing to do.
</p
>
3750 <p
>I considered using the noop I/O scheduler, as several recommended
3751 it for SSD, but others recommended deadline and a benchmark I found
3752 indicated that deadline might be better for interactive use.
</p
>
3754 <p
>I also considered using the
'discard
' file system option for ext3
3755 and ext4, but read that it would give a performance hit ever time a
3756 file is removed, and thought it best to that that slowdown once a day
3757 instead of during my work.
</p
>
3759 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3760 this is already done by Debian Edu.
</p
>
3762 <p
>I have not yet started on the user space tuning. I expect
3763 iceweasel need some tuning, and perhaps other applications too, but
3764 have not yet had time to investigate those parts.
</p
>
3766 <p
>The package should work on Ubuntu too, but I have not yet tested it
3769 <p
>As for the answer to the question in the title of this blog post,
3770 as far as I know, the only solution I know about is to replace the
3771 disk. It might be possible to flash it with Intel firmware instead of
3772 the Lenovo firmware. But I have not tried and did not want to do so
3773 without approval from Lenovo as I wanted to keep the warranty on the
3774 disk until a solution was found and they wanted the broken disks
3780 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
3781 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
3782 <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>
3783 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
3784 <description><p
>A few days ago, I wrote about
3785 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
3786 problems I experienced with my new X230 and its SSD disk
</a
>, which
3787 was dying during installation because it is unable to cope with
3788 sustained write. My supplier is in contact with
3789 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
3790 replacement disk to try to fix the problem. They decided to send an
3791 identical model, so my hopes for a permanent fix was slim.
</p
>
3793 <p
>Anyway, today I got the replacement disk and tried to install
3794 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3795 same firmware version as the original. This time my hope raised
3796 slightly as the installation progressed, as the original disk used to
3797 die after
4-
7% of the disk was written to, while this time it kept
3798 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
3799 died again and I was back on square one. I still do not have a new
3800 laptop with a disk I can trust. I can not live with a disk that might
3801 lock up when I download a new
3802 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
3803 other large files. I look forward to hearing from my supplier with
3804 the next proposal from Lenovo.
</p
>
3806 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
3807 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3808 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
3809 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
3810 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
3811 P/N
45N8295, P0C38732.
</p
>
3813 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
3814 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
3815 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
3816 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
3817 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
3818 P/N
45N8295, P0C38732.
</p
>
3820 <p
>The only difference is in the first number (serial number?), ISN,
3821 SA, date and WNPP values. Mentioning all the details here in case
3822 someone is able to use the information to find a way to identify the
3823 failing disk among working ones (if any such working disk actually
3829 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
3830 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
3831 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
3832 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
3833 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
3834 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3835 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
3836 member assosiation NUUG
</a
> and
3837 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
3838 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
3839 Bitraf
</a
>.
</p
>
3841 <p
>It starts
10:
00 and continue until late evening. Everyone is
3842 welcome, and there is no fee to participate. There is on the other
3843 hand limited space, and only room for
30 people. Please put your name
3844 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
3845 wiki page
</a
> if you plan to join us.
</p
>
3850 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
3851 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
3852 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
3853 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
3854 <description><p
>Half a year ago, I reported that I had to find a
3855 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
3856 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
3857 time to spend on it, and it took a while to find a model I believe
3858 will do the job, but two days ago the replacement finally arrived. I
3860 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
3861 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3862 a roaming workstation, and it seemed to work flawlessly. But my
3863 second installation with encrypted disk was not as successful. More
3864 on that below.
</p
>
3866 <p
>I had a hard time trying to track down a good laptop, as my most
3867 important requirements (robust and with a good keyboard) are never
3868 listed in the feature list. But I did get good help from the search
3869 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
3870 allowed me to limit the list of interesting laptops based on my other
3871 requirements. A bit surprising that SSD disk are not disks according
3872 to that search interface, so I had to drop specifying the number of
3873 disks from my search parameters. I also asked around among friends to
3874 get their impression on keyboards and robustness.
</p
>
3876 <p
>So the new laptop arrived, and it is quite a lot wider than the
3877 X41. I am not quite convinced about the keyboard, as it is
3878 significantly wider than my old keyboard, and I have to stretch my
3879 hand a lot more to reach the edges. But the key response is fairly
3880 good and the individual key shape is fairly easy to handle, so I hope
3881 I will get used to it. My old X40 was starting to fail, and I really
3882 needed a new laptop now. :)
</p
>
3884 <p
>Turning off the touch pad was simple. All it took was a quick
3885 visit to the BIOS during boot it disable it.
</p
>
3887 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
3888 lock up during load. And this happen when installing Debian Wheezy
3889 with encrypted disk, while the disk is being filled with random data.
3890 I also tested to install Ubuntu Raring, and it happen there too if I
3891 reenable the code to fill the disk with random data (it is disabled by
3892 default in Ubuntu). And the bug with is already known. It was
3893 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
3894 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
3895 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3896 kernel developers as
3897 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
3898 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
3899 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3900 Lenovo forums, both for
3901 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
3902 2012-
11-
10</a
> and for
3903 <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
3904 03-
20-
2013</a
>. The problem do not only affect installation. The
3905 reports state that the disk lock up during use if many writes are done
3906 on the disk, so it is much no use to work around the installation
3907 problem and end up with a computer that can lock up at any moment.
3909 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
3910 available
</a
> that will lock up the hard drive after running a few
3911 minutes by writing to a file.
</p
>
3913 <p
>I
've contacted my supplier and asked how to handle this, and after
3914 contacting PCHELP Norway (request
01D1FDP) which handle support
3915 requests for Lenovo, his first suggestion was to upgrade the disk
3916 firmware. Unfortunately there is no newer firmware available from
3917 Lenovo, as my disk already have the most recent one (version LF1i). I
3918 hope to hear more from him today and hope the problem can be
3924 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
3925 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
3926 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
3927 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
3928 <description><p
>Half a year ago, I reported that I had to find a replacement for my
3929 trusty old Thinkpad X41. Unfortunately I did not have much time to
3930 spend on it, but today the replacement finally arrived. I ended up
3931 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
3932 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
3933 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3934 this, it is installing what I hope will be a more final installation,
3935 with a encrypted hard drive to ensure any dope head stealing it end up
3936 with an expencive door stop.
</p
>
3938 <p
>I had a hard time trying to track down a good laptop, as my most
3939 important requirements (robust and with a good keyboard) are never
3940 listed in the feature list. But I did get good help from the search
3941 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
3942 allowed me to limit the list of interesting laptops based on my other
3943 requirements. A bit surprising that SSD disk are not disks, so I had
3944 to drop number of disks from my search parameters.
</p
>
3946 <p
>I am not quite convinced about the keyboard, as it is significantly
3947 wider than my old keyboard, and I have to stretch my hand a lot more
3948 to reach the edges. But the key response is fairly good and the
3949 individual key shape is fairly easy to handle, so I hope I will get
3950 used to it. My old X40 was starting to fail, and I really needed a
3951 new laptop now. :)
</p
>
3953 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
3958 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
3959 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
3960 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
3961 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
3962 <description><p
>It annoys me when the computer fail to do automatically what it is
3963 perfectly capable of, and I have to do it manually to get things
3964 working. One such task is to find out what firmware packages are
3965 needed to get the hardware on my computer working. Most often this
3966 affect the wifi card, but some times it even affect the RAID
3967 controller or the ethernet card. Today I pushed version
0.4 of the
3968 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
3969 including a new script isenkram-autoinstall-firmware handling the
3970 process of asking all the loaded kernel modules what firmware files
3971 they want, find debian packages providing these files and install the
3972 debian packages. Here is a test run on my laptop:
</p
>
3974 <p
><pre
>
3975 # isenkram-autoinstall-firmware
3976 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3977 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3978 info: locating packages with the requested firmware files
3979 info: Updating APT sources after adding non-free APT source
3980 info: trying to install firmware-ipw2x00
3983 Preconfiguring packages ...
3984 Selecting previously deselected package firmware-ipw2x00.
3985 (Reading database ...
259727 files and directories currently installed.)
3986 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3987 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
3989 </pre
></p
>
3991 <p
>When all the requested firmware is present, a simple message is
3992 printed instead:
</p
>
3994 <p
><pre
>
3995 # isenkram-autoinstall-firmware
3996 info: did not find any firmware files requested by loaded kernel modules. exiting
3998 </pre
></p
>
4000 <p
>It could use some polish, but it is already working well and saving
4001 me some time when setting up new machines. :)
</p
>
4003 <p
>So, how does it work? It look at the set of currently loaded
4004 kernel modules, and look up each one of them using modinfo, to find
4005 the firmware files listed in the module meta-information. Next, it
4006 download the Contents file from a nearby APT mirror, and search for
4007 the firmware files in this file to locate the package with the
4008 requested firmware file. If the package is in the non-free section, a
4009 non-free APT source is added and the package is installed using
4010 <tt
>apt-get install
</tt
>. The end result is a slightly better working
4013 <p
>I hope someone find time to implement a more polished version of
4014 this script as part of the hw-detect debian-installer module, to
4015 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
4016 #
655507</a
>. There really is no need to insert USB sticks with
4017 firmware during a PXE install when the packages already are available
4018 from the nearby Debian mirror.
</p
>
4023 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
4024 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
4025 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
4026 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
4027 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
4028 the screen just turn black when Linux boot, either during installation
4029 or on first boot from the hard disk. I
've seen it once in a while the
4030 last few years, but only recently understood the cause. I
've seen it
4031 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
4032 The reason seem to be in the wiring of some laptops. The system to
4033 control the screen background light is inverted, so when Linux try to
4034 turn the brightness fully on, it end up turning it off instead. I do
4035 not know which Linux drivers are affected, but this post is about the
4036 i915 driver used by the
4037 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4038 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
4040 <p
>The problem can be worked around two ways. Either by adding
4041 i915.invert_brightness=
1 as a kernel option, or by adding a file in
4042 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
4043 option when it load the i915 kernel module. On Debian and Ubuntu, it
4044 can be done by running these commands as root:
</p
>
4047 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
4048 update-initramfs -u -k all
4051 <p
>Since March
2012 there is
4052 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
4053 mechanism in the Linux kernel
</a
> to tell the i915 driver which
4054 hardware have this problem, and get the driver to invert the
4055 brightness setting automatically. To use it, one need to add a row in
4056 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
4057 intel_quirks array
</a
> in the driver source
4058 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
4059 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
4060 number (vendor number
8086 is assumed) and subdevice vendor and device
4063 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
4064 -vvnn
</tt
> for the video card in question:
</p
>
4066 <p
><pre
>
4067 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
4068 3rd Gen Core processor Graphics Controller [
8086:
0156] \
4069 (rev
09) (prog-if
00 [VGA controller])
4070 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
4071 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
4072 ParErr- Stepping- SE RR- FastB2B- DisINTx+
4073 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
4074 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
4076 Interrupt: pin A routed to IRQ
42
4077 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
4078 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
4079 Region
4: I/O ports at
4000 [size=
64]
4080 Expansion ROM at
<unassigned
> [disabled]
4081 Capabilities:
<access denied
>
4082 Kernel driver in use: i915
4083 </pre
></p
>
4085 <p
>The resulting intel_quirks entry would then look like this:
</p
>
4087 <p
><pre
>
4088 struct intel_quirk intel_quirks[] = {
4090 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
4091 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
4094 </pre
></p
>
4096 <p
>According to the kernel module instructions (as seen using
4097 <tt
>modinfo i915
</tt
>), information about hardware needing the
4098 invert_brightness flag should be sent to the
4099 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
4100 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
4101 developers. But my email about the laptop sent
2013-
06-
03 have not
4103 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
4104 web archive for the mailing list
</a
>, so I suspect they do not accept
4105 emails from non-subscribers. Because of this, I sent my patch also to
4106 the Debian bug tracking system instead as
4107 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
4108 sure the patch is not lost.
</p
>
4110 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
4111 with this problem working properly with Linux. If you use Gnome, your
4112 worries should be over at this point. But if you use KDE, there is
4113 something in KDE ignoring the invert_brightness setting and turning on
4114 the screen during login. I
've reported it to Debian as
4115 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
4116 have no idea yet how to figure out exactly what subsystem is doing
4117 this. Perhaps you can help? Perhaps you know what the Gnome
4118 developers did to handle this, and this can give a clue to the KDE
4119 developers? Or you know where in KDE the screen brightness is changed
4120 during login? If so, please update the BTS report (or get in touch if
4121 you do not know how to update BTS).
</p
>
4123 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
4124 acpi_backlight=vendor, to disable ACPI backlight support completely,
4125 as the ACPI information on the machine is trash and it is better to
4126 leave it to the intel video driver to control the screen
4127 backlight.
</p
>
4132 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
4133 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
4134 <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>
4135 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
4136 <description><p
>Two days ago, I asked
4137 <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
4138 I could install Linux on a Packard Bell EasyNote LV computer
4139 preinstalled with Windows
8</a
>. I found a solution, but am horrified
4140 with the obstacles put in the way of Linux users on a laptop with UEFI
4141 and Windows
8.
</p
>
4143 <p
>I never found out if the cause of my problems were the use of UEFI
4144 secure booting or fast boot. I suspect fast boot was the problem,
4145 causing the firmware to boot directly from HD without considering any
4146 key presses and alternative devices, but do not know UEFI settings
4147 enough to tell.
</p
>
4149 <p
>There is no way to install Linux on the machine in question without
4150 opening the box and disconnecting the hard drive! This is as far as I
4151 can tell, the only way to get access to the firmware setup menu
4152 without accepting the Windows
8 license agreement. I am told (and
4153 found description on how to) that it is possible to configure the
4154 firmware setup once booted into Windows
8. But as I believe the terms
4155 of that agreement are completely unacceptable, accepting the license
4156 was never an alternative. I do not enter agreements I do not intend
4157 to follow.
</p
>
4159 <p
>I feared I had to return the laptops and ask for a refund, and
4160 waste many hours on this, but luckily there was a way to get it to
4161 work. But I would not recommend it to anyone planning to run Linux on
4162 it, and I have become sceptical to Windows
8 certified laptops. Is
4163 this the way Linux will be forced out of the market place, by making
4164 it close to impossible for
"normal
" users to install Linux without
4165 accepting the Microsoft Windows license terms? Or at least not
4166 without risking to loose the warranty?
</p
>
4168 <p
>I
've updated the
4169 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
4170 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
4171 do not have to struggle as much as I did to get Linux into the
4174 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
4175 Michael Tokarev and others for feedback and ideas.
</p
>
4180 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
4181 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
4182 <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>
4183 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
4184 <description><p
>I
've run into quite a problem the last few days. I bought three
4185 new laptops for my parents and a few others. I bought Packard Bell
4186 Easynote LV to run Kubuntu on and use as their home computer. But I
4187 am completely unable to figure out how to install Linux on it. The
4188 computer is preinstalled with Windows
8, and I suspect it uses UEFI
4189 instead of a BIOS to boot.
</p
>
4191 <p
>The problem is that I am unable to get it to PXE boot, and unable
4192 to get it to boot the Linux installer from my USB stick. I have yet
4193 to try the DVD install, and still hope it will work. when I turn on
4194 the computer, there is no information on what buttons to press to get
4195 the normal boot menu. I expect to get some boot menu to select PXE or
4196 USB stick booting. When booting, it first ask for the language to
4197 use, then for some regional settings, and finally if I will accept the
4198 Windows
8 terms of use. As these terms are completely unacceptable to
4199 me, I have no other choice but to turn off the computer and try again
4200 to get it to boot the Linux installer.
</p
>
4202 <p
>I have gathered my findings so far on a Linlap page about the
4203 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4204 EasyNote LV
</a
> model. If you have any idea how to get Linux
4205 installed on this machine, please get in touch or update that wiki
4206 page. If I can
't find a way to install Linux, I will have to return
4207 the laptop to the seller and find another machine for my parents.
</p
>
4209 <p
>I wonder, is this the way Linux will be forced out of the market
4210 using UEFI and
"secure boot
" by making it impossible to install Linux
4211 on new Laptops?
</p
>
4216 <title>How to transform a Debian based system to a Debian Edu installation
</title>
4217 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
4218 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
4219 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
4220 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
4221 an operating system based on Debian intended for use in schools. It
4222 contain a turn-key solution for the computer network provided to
4223 pupils in the primary schools. It provide both the central server,
4224 network boot servers and desktop environments with heaps of
4225 educational software. The project was founded almost
12 years ago,
4226 2001-
07-
02. If you want to support the project, which is in need for
4227 cash to fund developer gatherings and other project related activity,
4228 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
4229 donate some money
</a
>.
4231 <p
>A topic that come up again and again on the Debian Edu mailing
4232 lists and elsewhere, is the question on how to transform a Debian or
4233 Ubuntu installation into a Debian Edu installation. It isn
't very
4234 hard, and last week I wrote a script to replicate the steps done by
4235 the Debian Edu installer.
</p
>
4237 <p
>The script,
4238 <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/
>
4239 in the debian-edu-config package, will go through these six steps and
4240 transform an existing Debian Wheezy or Ubuntu (untested) installation
4241 into a Debian Edu Workstation:
</p
>
4245 <li
>Add skolelinux related APT sources.
</li
>
4246 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
4247 <li
>Install debian-edu-install to load preseeding values and pull in
4248 our configuration.
</li
>
4249 <li
>Preseed debconf database with profile setup in
4250 /etc/debian-edu/config, and run tasksel to install packages
4251 according to the profile specified in the config above,
4252 overriding some of the Debian automation machinery.
</li
>
4253 <li
>Run debian-edu-cfengine-D installation to configure everything
4254 that could not be done using preseeding.
</li
>
4255 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
4259 <p
>There are some steps in the Debian Edu installation that can not be
4260 replicated like this. Disk partitioning and LVM setup, for example.
4261 So this script just assume there is enough disk space to install all
4262 the needed packages.
</p
>
4264 <p
>The script was created to help a Debian Edu student working on
4265 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
4266 Debian Edu client, and using it he can take the existing
4267 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
4268 transform it into a fully functioning Debian Edu Workstation (or
4269 Roaming Workstation, or whatever :).
</p
>
4271 <p
>The default setting in the script is to create a KDE Workstation.
4272 If a LXDE based Roaming workstation is wanted instead, modify the
4273 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
4275 <p
><pre
>
4276 PROFILE=
"Roaming-Workstation
"
4277 DESKTOP=
"lxde
"
4278 </pre
></p
>
4280 <p
>The script could even become useful to set up Debian Edu servers in
4281 the cloud, by starting with a virtual Debian installation at some
4282 virtual hosting service and setting up all the services on first
4288 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
4289 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
4290 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
4291 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
4292 <description><P
>In January,
4293 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
4294 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
4295 channel #debian-lego
</a
>, for those of us in the Debian and Linux
4296 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
4297 marvellous construction system from Denmark. We also created
4298 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
4299 a place to take notes and write down our plans and hopes. And several
4300 people showed up to help. I was very happy to see the effect of my
4301 call. Since the small start, we have a debtags tag
4302 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
4303 tag for LEGO related packages, and now count
10 packages related to
4304 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
4306 <p
><table
>
4307 <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
>
4308 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
4309 <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
>
4310 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
4311 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
4312 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
4313 <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
>
4314 <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
>
4315 <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
>
4316 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
4317 </table
></p
>
4319 <p
>Some of these are available in Wheezy, and all but one are
4320 currently available in Jessie/testing. leocad is so far only
4321 available in experimental.
</p
>
4323 <p
>If you care about LEGO in Debian, please join us on IRC and help
4324 adding the rest of the great free software tools available on Linux
4325 for LEGO designers.
</p
>
4330 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
4331 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
4332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
4333 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
4334 <description><p
>When I woke up this morning, I was very happy to see that the
4335 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
4336 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
4337 Debian release, and I expect to move my machines at home over to it fairly
4340 <p
>The new debian release contain heaps of new stuff, and one program
4341 in particular make me very happy to see included. The
4342 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
4343 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
4344 included for the first time. Alongside similar programs like
4345 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
4346 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
4347 it allow for visual programming where syntax errors can not happen,
4348 and a friendly programming environment for learning to control the
4349 computer. Scratch will also be included in the next release of Debian
4352 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
4353 Edu/Skolelinux release too. The
4354 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
4355 alpha release
</a
> went out last week, and the next should soon
4361 <title>Isenkram
0.2 finally in the Debian archive
</title>
4362 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
4363 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
4364 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
4365 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
4366 package
</a
> finally made it into the archive, after lingering in NEW
4367 for many months. I uploaded it to the Debian experimental suite
4368 2013-
01-
27, and today it was accepted into the archive.
</p
>
4370 <p
>Isenkram is a system for suggesting to users what packages to
4371 install to work with a pluggable hardware device. The suggestion pop
4372 up when the device is plugged in. For example if a Lego Mindstorm NXT
4373 is inserted, it will suggest to install the program needed to program
4374 the NXT controller. Give it a go, and report bugs and suggestions to
4380 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
4381 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
4382 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
4383 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
4384 <description><p
>My
4385 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
4386 bitcoin related blog post
</a
> mentioned that the new
4387 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
4388 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
4389 2013-
01-
19, and have been available in unstable since then. It was
4390 automatically copied to Ubuntu, and is available in their Raring
4391 version too.
</p
>
4393 <p
>But there is a strange problem with the build that block this new
4394 version from being available on the i386 and kfreebsd-i386
4395 architectures. For some strange reason, the autobuilders in Debian
4396 for these architectures fail to run the test suite on these
4397 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
4398 We are so far unable to reproduce it when building it manually, and
4399 no-one have been able to propose a fix. If you got an idea what is
4400 failing, please let us know via the BTS.
</p
>
4402 <p
>One feature that is annoying me with of the bitcoin client, because
4403 I often run low on disk space, is the fact that the client will exit
4404 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
4405 #
696715</a
>). So make sure you have enough disk space when you run
4408 <p
>As usual, if you use bitcoin and want to show your support of my
4409 activities, please send Bitcoin donations to my address
4410 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4415 <title>Welcome to the world, Isenkram!
</title>
4416 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
4417 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
4418 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
4419 <description><p
>Yesterday, I
4420 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
4421 for testers
</a
> for my prototype for making Debian better at handling
4422 pluggable hardware devices, which I
4423 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
4424 out to create
</a
> earlier this month. Several valuable testers showed
4425 up, and caused me to really want to to open up the development to more
4426 people. But before I did this, I want to come up with a sensible name
4427 for this project. Today I finally decided on a new name, and I have
4428 renamed the project from hw-support-handler to this new name. In the
4429 process, I moved the source to git and made it available as a
4430 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
4431 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
4432 To fetch and build the latest version of the source, use
</p
>
4435 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
4436 cd isenkram
&& git-buildpackage -us -uc
4439 <p
>I have not yet adjusted all files to use the new name yet. If you
4440 want to hack on the source or improve the package, please go ahead.
4441 But please talk to me first on IRC or via email before you do major
4442 changes, to make sure we do not step on each others toes. :)
</p
>
4444 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
4445 stuff, typically meaning tools, nails, screws, etc. Typical hardware
4446 stuff, in other words. I
've been told it is the Norwegian variant of
4447 the German word eisenkram, for those that are familiar with that
4450 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
4451 instructions, to avoid confusing people with an error from the signing
4454 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
4455 clone argument to avoid the need for authentication.
</p
>
4460 <title>First prototype ready making hardware easier to use in Debian
</title>
4461 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
4462 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
4463 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
4464 <description><p
>Early this month I set out to try to
4465 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
4466 the Debian support for pluggable hardware devices
</a
>. Now my
4467 prototype is working, and it is ready for a larger audience. To test
4469 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
4470 from the Debian Edu subversion repository
</a
>, build and install the
4471 package. You might have to log out and in again activate the
4472 autostart script.
</p
>
4474 <p
>The design is simple:
</p
>
4478 <li
>Add desktop entry in /usr/share/autostart/ causing a program
4479 hw-support-handlerd to start when the user log in.
</li
>
4481 <li
>This program listen for kernel events about new hardware (directly
4482 from the kernel like udev does), not using HAL dbus events as I
4483 initially did.
</li
>
4485 <li
>When new hardware is inserted, look up the hardware modalias in
4486 the APT database, a database
4487 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
4488 via HTTP
</a
> and a database available as part of the package.
</li
>
4490 <li
>If a package is mapped to the hardware in question, the package
4491 isn
't installed yet and this is the first time the hardware was
4492 plugged in, show a desktop notification suggesting to install the
4493 package or packages.
</li
>
4495 <li
>If the user click on the
'install package now
' button, ask
4496 aptdaemon via the PackageKit API to install the requrired package.
</li
>
4498 <li
>aptdaemon ask for root password or sudo password, and install the
4499 package while showing progress information in a window.
</li
>
4503 <p
>I still need to come up with a better name for the system. Here
4504 are some screen shots showing the prototype in action. First the
4505 notification, then the password request, and finally the request to
4506 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
4508 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
4509 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
4510 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
4511 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
4512 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
4514 <p
>The prototype still need to be improved with longer timeouts, but
4515 is already useful. The database of hardware to package mappings also
4516 need more work. It is currently compatible with the Ubuntu way of
4517 storing such information in the package control file, but could be
4518 changed to use other formats instead or in addition to the current
4519 method. I
've dropped the use of discover for this mapping, as the
4520 modalias approach is more flexible and easier to use on Linux as long
4521 as the Linux kernel expose its modalias strings directly.
</p
>
4523 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
4524 here is the command required to check out and build the source: Use
4525 '<tt
>svn checkout
4526 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
4527 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
4528 devscripts package.
</p
>
4530 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
4531 renamed to Isenkram and the source moved from the Debian Edu
4532 subversion repository to a Debian collab-maint git repository. See
4533 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
4534 instructions
</a
> for details.
</p
>
4539 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
4540 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
4541 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
4542 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
4543 <description><p
>This Christmas my trusty old laptop died. It died quietly and
4544 suddenly in bed. With a quiet whimper, it went completely quiet and
4545 black. The power button was no longer able to turn it on. It was a
4546 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4547 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4548 Compaq I had before that. Now I need to find a replacement. To keep
4549 going during Christmas, I moved the one year old SSD disk to my old
4550 X40 where it fitted (only one I had left that could use it), but it is
4551 not a durable solution.
4553 <p
>My laptop needs are fairly modest. This is my wishlist from when I
4554 got a new one more than
10 years ago. It still holds true.:)
</p
>
4558 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
4559 than A4).
</li
>
4560 <li
>Robust, it will be in my backpack every day.
</li
>
4561 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
4562 <li
>Long battery life time. Preferable a week.
</li
>
4563 <li
>Internal WIFI network card.
</li
>
4564 <li
>Internal Twisted Pair network card.
</li
>
4565 <li
>Some USB slots (
2-
3 is plenty)
</li
>
4566 <li
>Good keyboard - similar to the Thinkpad.
</li
>
4567 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
4569 <li
>Hardware supported by Debian Stable, ie the default kernel and
4570 X.org packages.
</li
>
4571 <li
>Quiet, preferably fan free (or at least not using the fan most of
4576 <p
>You will notice that there are no RAM and CPU requirements in the
4577 list. The reason is simply that the specifications on laptops the
4578 last
10-
15 years have been sufficient for my needs, and I have to look
4579 at other features to choose my laptop. But are there still made as
4580 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4581 robust, and Thinkpads seem to be heading in the wrong direction since
4582 Lenovo took over. But I
've been told that X220 and X1 Carbon might
4583 still be useful.
</p
>
4585 <p
>Perhaps I should rethink my needs, and look for a pad with an
4586 external keyboard? I
'll have to check the
4587 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
4588 well-supported laptops, or perhaps just buy one preinstalled from one
4589 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
4590 Pre-loaded site
</a
>.
</p
>
4595 <title>How to find a browser plugin supporting a given MIME type
</title>
4596 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
4597 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
4598 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
4599 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
4600 install to get support for a given MIME type. Thanks to
4601 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
4602 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
4603 Unfortunately, not very many packages provide the needed meta
4604 information, Anyway, here is a small script to look up all browser
4605 plugin packages announcing ther MIME support using this specification:
</p
>
4611 def pkgs_handling_mimetype(mimetype):
4616 version = pkg.candidate
4618 version = pkg.installed
4621 record = version.record
4622 if not record.has_key(
'Npp-MimeType
'):
4624 mime_types = record[
'Npp-MimeType
'].split(
',
')
4625 for t in mime_types:
4626 t = t.rstrip().strip()
4628 thepkgs.append(pkg.name)
4630 mimetype =
"audio/ogg
"
4631 if
1 < len(sys.argv):
4632 mimetype = sys.argv[
1]
4633 print
"Browser plugin packages supporting %s:
" % mimetype
4634 for pkg in pkgs_handling_mimetype(mimetype):
4635 print
" %s
" %pkg
4638 <p
>It can be used like this to look up a given MIME type:
</p
>
4641 % ./apt-find-browserplug-for-mimetype
4642 Browser plugin packages supporting audio/ogg:
4644 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4645 Browser plugin packages supporting application/x-shockwave-flash:
4646 browser-plugin-gnash
4650 <p
>In Ubuntu this mechanism is combined with support in the browser
4651 itself to query for plugins and propose to install the needed
4652 packages. It would be great if Debian supported such feature too. Is
4653 anyone working on adding it?
</p
>
4655 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
4656 request for icweasel support for this feature is
4657 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
4658 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
4659 of manpower and wish for a different design is the reason thus feature
4660 is not yet in iceweasel from Debian.
</p
>
4665 <title>What is the most supported MIME type in Debian?
</title>
4666 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
4667 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
4668 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
4669 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
4670 proposal to add AppStream information to the Debian archive
</a
>, is a
4671 proposal to make it possible for a Desktop application to propose to
4672 the user some package to install to gain support for a given MIME
4673 type, font, library etc. that is currently missing. With such
4674 mechanism in place, it would be possible for the desktop to
4675 automatically propose and install leocad if some LDraw file is
4676 downloaded by the browser.
</p
>
4678 <p
>To get some idea about the current content of the archive, I decided
4679 to write a simple program to extract all .desktop files from the
4680 Debian archive and look up the claimed MIME support there. The result
4682 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
4683 site
</a
>. Using the collected information, it become possible to
4684 answer the question in the title. Here are the
20 most supported MIME
4685 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4686 The complete list is available from the link above.
</p
>
4688 <p
><strong
>Debian Stable:
</strong
></p
>
4692 ----- -----------------------
4708 18 application/x-ogg
4715 <p
><strong
>Debian Testing:
</strong
></p
>
4719 ----- -----------------------
4735 18 application/x-ogg
4742 <p
><strong
>Debian Unstable:
</strong
></p
>
4746 ----- -----------------------
4763 18 application/x-ogg
4769 <p
>I am told that PackageKit can provide an API to access the kind of
4770 information mentioned in DEP-
11. I have not yet had time to look at
4771 it, but hope the PackageKit people in Debian are on top of these
4774 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
4775 discovering a typo in my script.
</p
>
4780 <title>Using modalias info to find packages handling my hardware
</title>
4781 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
4782 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
4783 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
4784 <description><p
>Yesterday, I wrote about the
4785 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
4786 values provided by the Linux kernel
</a
> following my hope for
4787 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
4788 dongle support in Debian
</a
>. Using this knowledge, I have tested how
4789 modalias values attached to package names can be used to map packages
4790 to hardware. This allow the system to look up and suggest relevant
4791 packages when I plug in some new hardware into my machine, and replace
4792 discover and discover-data as the database used to map hardware to
4795 <p
>I create a modaliases file with entries like the following,
4796 containing package name, kernel module name (if relevant, otherwise
4797 the package name) and globs matching the relevant hardware
4800 <p
><blockquote
>
4801 Package: package-name
4802 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
4803 </blockquote
></p
>
4805 <p
>It is fairly trivial to write code to find the relevant packages
4806 for a given modalias value using this file.
</p
>
4808 <p
>An entry like this would suggest the video and picture application
4809 cheese for many USB web cameras (interface bus class
0E01):
</p
>
4811 <p
><blockquote
>
4813 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
4814 </blockquote
></p
>
4816 <p
>An entry like this would suggest the pcmciautils package when a
4817 CardBus bridge (bus class
0607) PCI device is present:
</p
>
4819 <p
><blockquote
>
4820 Package: pcmciautils
4821 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4822 </blockquote
></p
>
4824 <p
>An entry like this would suggest the package colorhug-client when
4825 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
4827 <p
><blockquote
>
4828 Package: colorhug-client
4829 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
4830 </blockquote
></p
>
4832 <p
>I believe the format is compatible with the format of the Packages
4833 file in the Debian archive. Ubuntu already uses their Packages file
4834 to store their mappings from packages to hardware.
</p
>
4836 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
4837 announce the hardware it support in a way my prototype understand.
4838 This allow those publishing packages in an APT source outside the
4839 Debian archive as well as those backporting packages to make sure the
4840 hardware mapping are included in the package meta information. I
've
4841 tested such header in the pymissile package, and its modalias mapping
4842 is working as it should with my prototype. It even made it to Ubuntu
4845 <p
>To test if it was possible to look up supported hardware using only
4846 the shell tools available in the Debian installer, I wrote a shell
4847 implementation of the lookup code. The idea is to create files for
4848 each modalias and let the shell do the matching. Please check out and
4850 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
4851 shell script. It run without any extra dependencies and fetch the
4852 hardware mappings from the Debian archive and the subversion
4853 repository where I currently work on my prototype.
</p
>
4855 <p
>When I use it on a machine with a yubikey inserted, it suggest to
4856 install yubikey-personalization:
</p
>
4858 <p
><blockquote
>
4859 % ./hw-support-lookup
4860 <br
>yubikey-personalization
4862 </blockquote
></p
>
4864 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4865 propose to install the pcmciautils package:
</p
>
4867 <p
><blockquote
>
4868 % ./hw-support-lookup
4869 <br
>pcmciautils
4871 </blockquote
></p
>
4873 <p
>If you know of any hardware-package mapping that should be added to
4874 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
4875 database
</a
>, please tell me about it.
</p
>
4877 <p
>It could be possible to generate several of the mappings between
4878 packages and hardware. One source would be to look at packages with
4879 kernel modules, ie packages with *.ko files in /lib/modules/, and
4880 extract their modalias information. Another would be to look at
4881 packages with udev rules, ie packages with files in
4882 /lib/udev/rules.d/, and extract their vendor/model information to
4883 generate a modalias matching rule. I have not tested any of these to
4884 see if it work.
</p
>
4886 <p
>If you want to help implementing a system to let us propose what
4887 packages to install when new hardware is plugged into a Debian
4888 machine, please send me an email or talk to me on
4889 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
4894 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
4895 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
4896 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
4897 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
4898 <description><p
>While looking into how to look up Debian packages based on hardware
4899 information, to find the packages that support a given piece of
4900 hardware, I refreshed my memory regarding modalias values, and decided
4901 to document the details. Here are my findings so far, also available
4903 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
4904 Debian Edu subversion repository
</a
>:
4906 <p
><strong
>Modalias decoded
</strong
></p
>
4908 <p
>This document try to explain what the different types of modalias
4909 values stands for. It is in part based on information from
4910 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
4911 &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;,
4912 &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
4913 &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;.
4915 <p
>The modalias entries for a given Linux machine can be found using
4916 this shell script:
</p
>
4919 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
4922 <p
>The supported modalias globs for a given kernel module can be found
4923 using modinfo:
</p
>
4926 % /sbin/modinfo psmouse | grep alias:
4927 alias: serio:ty05pr*id*ex*
4928 alias: serio:ty01pr*id*ex*
4932 <p
><strong
>PCI subtype
</strong
></p
>
4934 <p
>A typical PCI entry can look like this. This is an Intel Host
4935 Bridge memory controller:
</p
>
4937 <p
><blockquote
>
4938 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4939 </blockquote
></p
>
4941 <p
>This represent these values:
</p
>
4946 sv
00001028 (subvendor)
4947 sd
000001AD (subdevice)
4949 sc
00 (bus subclass)
4953 <p
>The vendor/device values are the same values outputted from
'lspci
4954 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
4955 0600. The
0600 class is a host bridge. Other useful bus values are
4956 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
4958 <p
>Not sure how to figure out the interface value, nor what it
4961 <p
><strong
>USB subtype
</strong
></p
>
4963 <p
>Some typical USB entries can look like this. This is an internal
4964 USB hub in a laptop:
</p
>
4966 <p
><blockquote
>
4967 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4968 </blockquote
></p
>
4970 <p
>Here is the values included in this alias:
</p
>
4973 v
1D6B (device vendor)
4974 p
0001 (device product)
4976 dc
09 (device class)
4977 dsc
00 (device subclass)
4978 dp
00 (device protocol)
4979 ic
09 (interface class)
4980 isc
00 (interface subclass)
4981 ip
00 (interface protocol)
4984 <p
>The
0900 device class/subclass means hub. Some times the relevant
4985 class is in the interface class section. For a simple USB web camera,
4986 these alias entries show up:
</p
>
4988 <p
><blockquote
>
4989 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4990 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4991 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4992 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4993 </blockquote
></p
>
4995 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
4996 camera),
0101 is audio control device and
0102 is audio streaming (aka
4997 microphone). Thus this is a camera with microphone included.
</p
>
4999 <p
><strong
>ACPI subtype
</strong
></p
>
5001 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
5002 receiver in a Thinkpad X40:
</p
>
5004 <p
><blockquote
>
5005 acpi:IBM0071:PNP0511:
5006 </blockquote
></p
>
5008 <p
>The values between the colons are IDs.
</p
>
5010 <p
><strong
>DMI subtype
</strong
></p
>
5012 <p
>The DMI table contain lots of information about the computer case
5013 and model. This is an entry for a IBM Thinkpad X40, fetched from
5014 /sys/devices/virtual/dmi/id/modalias:
</p
>
5016 <p
><blockquote
>
5017 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
5018 </blockquote
></p
>
5020 <p
>The values present are
</p
>
5023 bvn IBM (BIOS vendor)
5024 bvr
1UETB
6WW(
1.66) (BIOS version)
5025 bd
06/
15/
2005 (BIOS date)
5026 svn IBM (system vendor)
5027 pn
2371H4G (product name)
5028 pvr ThinkPadX40 (product version)
5029 rvn IBM (board vendor)
5030 rn
2371H4G (board name)
5031 rvr NotAvailable (board version)
5032 cvn IBM (chassis vendor)
5033 ct
10 (chassis type)
5034 cvr NotAvailable (chassis version)
5037 <p
>The chassis type
10 is Notebook. Other interesting values can be
5038 found in the dmidecode source:
</p
>
5042 4 Low Profile Desktop
5055 17 Main Server Chassis
5056 18 Expansion Chassis
5058 20 Bus Expansion Chassis
5059 21 Peripheral Chassis
5061 23 Rack Mount Chassis
5070 <p
>The chassis type values are not always accurately set in the DMI
5071 table. For example my home server is a tower, but the DMI modalias
5072 claim it is a desktop.
</p
>
5074 <p
><strong
>SerIO subtype
</strong
></p
>
5076 <p
>This type is used for PS/
2 mouse plugs. One example is from my
5077 test machine:
</p
>
5079 <p
><blockquote
>
5080 serio:ty01pr00id00ex00
5081 </blockquote
></p
>
5083 <p
>The values present are
</p
>
5092 <p
>This type is supported by the psmouse driver. I am not sure what
5093 the valid values are.
</p
>
5095 <p
><strong
>Other subtypes
</strong
></p
>
5097 <p
>There are heaps of other modalias subtypes according to
5098 file2alias.c. There is the rest of the list from that source: amba,
5099 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
5100 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
5101 vmbus, x86cpu and zorro. I did not spend time documenting all of
5102 these, as they do not seem relevant for my intended use with mapping
5103 hardware to packages when new stuff is inserted during run time.
</p
>
5105 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
5107 <p
>To check which kernel modules provide support for a given modalias,
5108 one can use the following shell script:
</p
>
5111 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
5112 echo
"$id
" ; \
5113 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
5117 <p
>The output can look like this (only the first few entries as the
5118 list is very long on my test machine):
</p
>
5122 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
5124 FATAL: Module acpi:device: not found.
5126 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
5127 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
5128 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
5129 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
5130 acpi:IBM0071:PNP0511:
5131 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
5132 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
5133 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
5137 <p
>If you want to help implementing a system to let us propose what
5138 packages to install when new hardware is plugged into a Debian
5139 machine, please send me an email or talk to me on
5140 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5142 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
5143 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
5144 in /sys/ with space in them.
</p
>
5149 <title>Moved the pymissile Debian packaging to collab-maint
</title>
5150 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
5151 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
5152 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
5153 <description><p
>As part of my investigation on how to improve the support in Debian
5154 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
5155 Launcher and updated the Debian package
5156 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
5157 sure udev will fix the device permissions when it is plugged in. I
5158 also added a
"Modaliases
" header to test it in the Debian archive and
5159 hopefully make the package be proposed by jockey in Ubuntu when a user
5160 plug in his rocket launcher. In the process I moved the source to a
5161 git repository under collab-maint, to make it easier for any DD to
5162 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
5163 is not very active, but the software still work for me even after five
5164 years of relative silence. The new git repository is not listed in
5165 the uploaded package yet, because I want to test the other changes a
5166 bit more before I upload the new version. If you want to check out
5167 the new version with a .desktop file included, visit the
5168 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
5169 view
</a
> or use
"<tt
>git clone
5170 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
5175 <title>Lets make hardware dongles easier to use in Debian
</title>
5176 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
5177 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
5178 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
5179 <description><p
>One thing that annoys me with Debian and Linux distributions in
5180 general, is that there is a great package management system with the
5181 ability to automatically install software packages by downloading them
5182 from the distribution mirrors, but no way to get it to automatically
5183 install the packages I need to use the hardware I plug into my
5184 machine. Even if the package to use it is easily available from the
5185 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
5186 suggest to automatically install the python-nxt, nbc and t2n packages
5187 I need to talk to it. When I plug in a Yubikey, it could propose the
5188 yubikey-personalization package. The information required to do this
5189 is available, but no-one have pulled all the pieces together.
</p
>
5191 <p
>Some years ago, I proposed to
5192 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
5193 the discover subsystem to implement this
</a
>. The idea is fairly
5198 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
5199 starting when a user log in.
</li
>
5201 <li
>Set this program up to listen for kernel events emitted when new
5202 hardware is inserted into the computer.
</li
>
5204 <li
>When new hardware is inserted, look up the hardware ID in a
5205 database mapping to packages, and take note of any non-installed
5206 packages.
</li
>
5208 <li
>Show a message to the user proposing to install the discovered
5209 package, and make it easy to install it.
</li
>
5213 <p
>I am not sure what the best way to implement this is, but my
5214 initial idea was to use dbus events to discover new hardware, the
5215 discover database to find packages and
5216 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
5219 <p
>Yesterday, I found time to try to implement this idea, and the
5220 draft package is now checked into
5221 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5222 Debian Edu subversion repository
</a
>. In the process, I updated the
5223 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
5224 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
5225 the relevant packages in Debian, and uploaded a new version
5226 2.2013.01.09 to unstable. I also discovered that the current
5227 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
5228 package in Debian no longer discovered any USB devices, because
5229 /proc/bus/usb/devices is no longer present. I ported it to use
5230 libusb as a fall back option to get it working. The fixed package
5231 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
5232 because of the freeze).
</p
>
5234 <p
>With this prototype in place, I can insert my Yubikey, and get this
5235 desktop notification to show up (only once, the first time it is
5236 inserted):
</p
>
5238 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
5240 <p
>For this prototype to be really useful, some way to automatically
5241 install the proposed packages by pressing the
"Please install
5242 program(s)
" button should to be implemented.
</p
>
5244 <p
>If this idea seem useful to you, and you want to help make it
5245 happen, please help me update the discover-data database with mappings
5246 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
5247 list the package you would like to have installed when a given
5248 hardware device is inserted into your computer, and report bugs using
5249 reportbug if it isn
't. Or, if you know of a better way to provide
5250 such mapping, please let me know.
</p
>
5252 <p
>This prototype need more work, and there are several questions that
5253 should be considered before it is ready for production use. Is dbus
5254 the correct way to detect new hardware? At the moment I look for HAL
5255 dbus events on the system bus, because that is the events I could see
5256 on my Debian Squeeze KDE desktop. Are there better events to use?
5257 How should the user be notified? Is the desktop notification
5258 mechanism the best option, or should the background daemon raise a
5259 popup instead? How should packages be installed? When should they
5260 not be installed?
</p
>
5262 <p
>If you want to help getting such feature implemented in Debian,
5263 please send me an email. :)
</p
>
5268 <title>New IRC channel for LEGO designers using Debian
</title>
5269 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
5270 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
5271 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
5272 <description><p
>During Christmas, I have worked a bit on the Debian support for
5273 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
5274 NXT
</a
>. My son and I have played a bit with my NXT set, and I
5275 discovered I had to build all the tools myself because none were
5276 already in Debian Squeeze. If Debian support for LEGO is something
5277 you care about, please join me on the IRC channel
5278 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
5279 irc.debian.org). There is a lot that could be done to improve the
5280 Debian support for LEGO designers. For example both CAD software
5281 and Mindstorm compilers are missing. :)
</p
>
5283 <p
>Update
2012-
01-
03: A
5284 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
5285 including links to Lego related packages is now available.
</p
>
5290 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
5291 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
5292 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
5293 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
5294 <description><p
>Let me start by wishing you all marry Christmas and a happy new
5295 year! I hope next year will prove to be a good year.
</p
>
5297 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
5298 decentralised
"currency
" that allow people to transfer bitcoins
5299 between each other with minimal overhead, is a very interesting
5300 experiment. And as I wrote a few days ago, the bitcoin situation in
5301 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
5302 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
5303 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
5304 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
5305 for one of the ftpmasters to approve the new bitcoin-qt package
5308 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
5309 team in Debian, you can easily test the package in Debian Squeeze
5310 using the following steps to get a set of working packages:
</p
>
5312 <blockquote
><pre
>
5313 git clone git://git.debian.org/git/collab-maint/bitcoin
5315 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
5316 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
5317 </pre
></blockquote
>
5319 <p
>You might have to install some build dependencies as well. The
5320 list of commands should give you two packages, bitcoind and
5321 bitcoin-qt, ready for use in a Squeeze environment. Note that the
5322 client will download the complete set of bitcoin
"blocks
", which need
5323 around
5.6 GiB of data on my machine at the moment. Make sure your
5324 ~/.bitcoin/ directory have lots of spare room if you want to download
5325 all the blocks. The client will warn if the disk is getting full, so
5326 there is not really a problem if you got too little room, but you will
5327 not be able to get all the features out of the client.
</p
>
5329 <p
>As usual, if you use bitcoin and want to show your support of my
5330 activities, please send Bitcoin donations to my address
5331 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5336 <title>A word on bitcoin support in Debian
</title>
5337 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
5338 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
5339 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
5340 <description><p
>It has been a while since I wrote about
5341 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
5342 peer-to-peer based crypto-currency, and the reason is simply that I
5343 have been busy elsewhere. But two days ago, I started looking at the
5344 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
5345 Debian
</a
> again to try to recover my old bitcoin wallet. The package
5346 is now maintained by a
5347 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
5348 people
</a
>, and the grunt work had already been done by this team. We
5349 owe a huge thank you to all these team members. :)
5350 But I was sad to discover that the bitcoin client is missing in
5351 Wheezy. It is only available in Sid (and an outdated client from
5352 backports). The client had several RC bugs registered in BTS blocking
5353 it from entering testing. To try to help the team and improve the
5354 situation, I spent some time providing patches and triaging the bug
5355 reports. I also had a look at the bitcoin package available from Matt
5357 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
5358 Ubuntu
</a
>, and moved the useful pieces from that version into the
5359 Debian package.
</p
>
5361 <p
>After checking with the main package maintainer Jonas Smedegaard on
5362 IRC, I pushed several patches into the collab-maint git repository to
5363 improve the package. It now contains fixes for the RC issues (not from
5364 me, but fixed by Scott Howard), build rules for a Qt GUI client
5365 package, konqueror support for the bitcoin: URI and bash completion
5366 setup. As I work on Debian Squeeze, I also created
5367 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
5368 patch to backport
</a
> the latest version. Jonas is going to look at
5369 it and try to integrate it into the git repository before uploading a
5370 new version to unstable.
5372 <p
>I would very much like bitcoin to succeed, to get rid of the
5373 centralized control currently exercised in the monetary system. I
5374 find it completely unacceptable that the USA government is collecting
5375 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
5376 that the major credit card companies can block legal money
5377 transactions to Wikileaks. But for bitcoin to succeed, more people
5378 need to use bitcoins, and more people need to accept bitcoins when
5379 they sell products and services. Improving the bitcoin support in
5380 Debian is a small step in the right direction, but not enough.
5381 Unfortunately the user experience when browsing the web and wanting to
5382 pay with bitcoin is still not very good. The bitcoin: URI is a step
5383 in the right direction, but need to work in most or every browser in
5384 use. Also the bitcoin-qt client is too heavy to fire up to do a
5385 quick transaction. I believe there are other clients available, but
5386 have not tested them.
</p
>
5389 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
5390 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
5391 I received
20.15 BTC so far on the address I provided in my blog two
5392 years ago, as can be
5393 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
5394 on the blockexplorer service
</a
>. Thank you everyone for your
5395 donation. The blockexplorer service demonstrates quite well that
5396 bitcoin is not quite anonymous and untracked. :) I wonder if the
5397 number of users have gone up since then. If you use bitcoin and want
5398 to show your support of my activity, please send Bitcoin donations to
5399 the same address as last time,
5400 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5405 <title>Git repository for song book for Computer Scientists
</title>
5406 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
5407 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
5408 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
5409 <description><p
>As I
5410 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
5411 this summer
</a
>, I have created a Computer Science song book a few
5412 years ago, and today I finally found time to create a public
5413 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
5414 repository for the project
</a
>.
</p
>
5416 <p
>If you want to help out, please clone the source and submit patches
5417 to the HTML version. To generate the PDF and PostScript version,
5418 please use prince XML, or let me know about a useful free software
5419 processor capable of creating a good looking PDF from the HTML.
</p
>
5421 <p
>Want to sing? You can still find the song book in HTML, PDF and
5422 PostScript formats at
5423 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
5424 Science Songbook
</a
>.
</p
>
5429 <title>Gratulerer med
19-årsdagen, Debian!
</title>
5430 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
5431 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
5432 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
5433 <description><p
>I dag fyller
5434 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
5435 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
5436 si gratulerer med dagen, Debian!
</p
>
5441 <title>Song book for Computer Scientists
</title>
5442 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
5443 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
5444 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
5445 <description><p
>Many years ago, while studying Computer Science at the
5446 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
5447 collecting computer related songs for use at parties. The original
5448 version was written in LaTeX, but a few years ago I got help from
5449 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
5450 while keeping the ability to create a nice book in PDF format. I have
5451 not had time to maintain the book for a while now, and guess I should
5452 put it up on some public version control repository where others can
5453 help me extend and update the book. If anyone is volunteering to help
5454 me with this, send me an email. Also let me know if there are songs
5455 missing in my book.
</p
>
5457 <p
>I have not mentioned the book on my blog so far, and it occured to
5458 me today that I really should let all my readers share the joys of
5459 singing out load about programming, computers and computer networks.
5460 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
5461 12</a
> is about to start (and I am not going). Want to sing? Check
5462 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
5463 Computer Science Songbook
</a
>.
5468 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
5469 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
5470 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
5471 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
5472 <description><p
>At work we have heaps of servers. I believe the total count is
5473 around
1000 at the moment. To be able to get help from the vendors
5474 when something go wrong, we want to keep the firmware on the servers
5475 up to date. If the firmware isn
't the latest and greatest, the
5476 vendors typically refuse to start debugging any problems until the
5477 firmware is upgraded. So before every reboot, we want to upgrade the
5478 firmware, and we would really like everyone handling servers at the
5479 university to do this themselves when they plan to reboot a machine.
5480 For that to happen we at the unix server admin group need to provide
5481 the tools to do so.
</p
>
5483 <p
>To make firmware upgrading easier, I am working on a script to
5484 fetch and install the latest firmware for the servers we got. Most of
5485 our hardware are from Dell and HP, so I have focused on these servers
5486 so far. This blog post is about the Dell part.
</P
>
5488 <p
>On the Dell FTP site I was lucky enough to find
5489 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
5490 with firmware information for all
11th generation servers, listing
5491 which firmware should be used on a given model and where on the FTP
5492 site I can find it. Using a simple perl XML parser I can then
5493 download the shell scripts Dell provides to do firmware upgrades from
5494 within Linux and reboot when all the firmware is primed and ready to
5495 be activated on the first reboot.
</p
>
5497 <p
>This is the Dell related fragment of the perl code I am working on.
5498 Are there anyone working on similar tools for firmware upgrading all
5499 servers at a site? Please get in touch and lets share resources.
</p
>
5501 <p
><pre
>
5505 use File::Temp qw(tempdir);
5507 # Install needed RHEL packages if missing
5509 'XML::Simple
' =
> 'perl-XML-Simple
',
5511 for my $module (keys %rhelmodules) {
5512 eval
"use $module;
";
5514 my $pkg = $rhelmodules{$module};
5515 system(
"yum install -y $pkg
");
5516 eval
"use $module;
";
5520 my $errorsto =
'pere@hungry.com
';
5526 sub run_firmware_script {
5527 my ($opts, $script) = @_;
5529 print STDERR
"fail: missing script name\n
";
5532 print STDERR
"Running $script\n\n
";
5534 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
5535 print STDERR
"success: firmware script ran succcessfully\n
";
5537 print STDERR
"fail: firmware script returned error\n
";
5541 sub run_firmware_scripts {
5542 my ($opts, @dirs) = @_;
5543 # Run firmware packages
5544 for my $dir (@dirs) {
5545 print STDERR
"info: Running scripts in $dir\n
";
5546 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
5547 while (my $s = readdir $dh) {
5548 next if $s =~ m/^\.\.?/;
5549 run_firmware_script($opts,
"$dir/$s
");
5557 print STDERR
"info: Downloading $url\n
";
5558 system(
"wget --quiet \
"$url\
"");
5563 my $product = `dmidecode -s system-product-name`;
5566 if ($product =~ m/PowerEdge/) {
5568 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5569 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
5571 my $tmpdir = tempdir(
5575 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
5576 system(
'gunzip Catalog.xml.gz
');
5577 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
5578 # -q is quiet, disabling interactivity and reducing console output
5579 my $fwopts =
"-q
";
5581 for my $url (@paths) {
5582 fetch_dell_fw($url);
5584 run_firmware_scripts($fwopts, $tmpdir);
5586 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5587 print STDERR
"error: Please report to $errorsto.\n
";
5591 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5592 print STDERR
"error: Please report to $errorsto.\n
";
5598 my $url =
"ftp://ftp.us.dell.com/$path
";
5602 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5603 # firmware packages to download from Dell. Only work for Linux
5604 # machines and
11th generation Dell servers.
5605 sub fetch_dell_fw_list {
5606 my $filename = shift;
5608 my $product = `dmidecode -s system-product-name`;
5610 my ($mybrand, $mymodel) = split(/\s+/, $product);
5612 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
5614 my $xml = XMLin($filename);
5616 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
5617 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
5618 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
5620 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
5621 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
5623 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
5625 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
5627 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
5630 for my $component (@{$xml-
>{SoftwareComponent}}) {
5631 my $componenttype = $component-
>{ComponentType}-
>{value};
5633 # Drop application packages, only firmware and BIOS
5634 next if
'APAC
' eq $componenttype;
5636 my $cpath = $component-
>{path};
5637 for my $path (@paths) {
5638 if ($cpath =~ m%/$path$%) {
5639 push(@paths, $cpath);
5647 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
5648 it could work on other platforms with some tweaking. Anyone know a
5649 index like Catalog.xml is available from HP for HP servers? At the
5650 moment I maintain a similar list manually and it is quickly getting
5656 <title>How is booting into runlevel
1 different from single user boots?
</title>
5657 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
5658 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
5659 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
5660 <description><p
>Wouter Verhelst have some
5661 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
5662 comments and opinions
</a
> on my blog post on
5663 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
5664 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
5665 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
5666 default KDE desktop in Debian
</a
>. I only have time to address one
5667 small piece of his comment now, and though it best to address the
5668 misunderstanding he bring forward:
</p
>
5670 <p
><blockquote
>
5671 Currently, a system admin has four options: [...] boot to a
5672 single-user system (by adding
'single
' to the kernel command line;
5673 this runs rcS and rc1 scripts)
5674 </blockquote
></p
>
5676 <p
>This make me believe Wouter believe booting into single user mode
5677 and booting into runlevel
1 is the same. I am not surprised he
5678 believe this, because it would make sense and is a quite sensible
5679 thing to believe. But because the boot in Debian is slightly broken,
5680 runlevel
1 do not work properly and it isn
't the same as single user
5681 mode. I
'll try to explain what is actually happing, but it is a bit
5682 hard to explain.
</p
>
5684 <p
>Single user mode is defined like this in /etc/inittab:
5685 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
5686 executed in single user mode is sulogin. Single user mode is a boot
5687 state
"between
" the runlevels, and when booting into single user mode,
5688 only the scripts in /etc/rcS.d/ are executed before the init process
5689 enters the single user state. When switching to runlevel
1, the state
5690 is in fact not ending in runlevel
1, but it passes through runlevel
1
5691 and end up in the single user mode (see /etc/rc1.d/S03single, which
5692 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
5693 1. It is confusing that the
'S
' (single user) init mode is not the
5694 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5697 <p
>This summary might make it clearer. When booting for the first
5698 time into single user mode, the following commands are executed:
5699 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
5700 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
5701 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
5702 trying to continue after visiting single user mode. Not all services
5703 are started again as they should, causing the machine to end up in an
5704 unpredicatble state. This is why Debian admins recommend rebooting
5705 after visiting single user mode.
</p
>
5707 <p
>A similar problem with runlevel
1 is caused by the amount of
5708 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
5709 to runlevel
1, the services started from /etc/rcS.d/ are not properly
5710 stopped when passing through the scripts in /etc/rc1.d/, and not
5711 started again when switching away from runlevel
1 to the runlevels
5712 2-
5. I believe the problem is best fixed by moving all the scripts
5713 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
5714 functioning single user mode during boot.
</p
>
5716 <p
>I have spent several years investigating the Debian boot system,
5717 and discovered this problem a few years ago. I suspect it originates
5718 from when sysvinit was introduced into Debian, a long time ago.
</p
>
5723 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
5724 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
5725 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
5726 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
5727 <description><p
>In the Debian boot system, several packages include scripts that
5728 are started from /etc/rcS.d/. In fact, there is a bite more of them
5729 than make sense, and this causes a few problems. What kind of
5730 problems, you might ask. There are at least two problems. The first
5731 is that it is not possible to recover a machine after switching to
5732 runlevel
1. One need to actually reboot to get the machine back to
5733 the expected state. The other is that single user boot will sometimes
5734 run into problems because some of the subsystems are activated before
5735 the root login is presented, causing problems when trying to recover a
5736 machine from a problem in that subsystem. A minor additional point is
5737 that moving more scripts out of rcS.d/ and into the other rc#.d/
5738 directories will increase the amount of scripts that can run in
5739 parallel during boot, and thus decrease the boot time.
</p
>
5741 <p
>So, which scripts should start from rcS.d/. In short, only the
5742 scripts that _have_ to execute before the root login prompt is
5743 presented during a single user boot should go there. Everything else
5744 should go into the numeric runlevels. This means things like
5745 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5746 the numeric runlevels. Today in Debian, there are around
115 init.d
5747 scripts that are started from rcS.d/, and most of them should be moved
5748 out. Do your package have one of them? Please help us make single
5749 user and runlevel
1 better by moving it.
</p
>
5751 <p
>Scripts setting up the screen, keyboard, system partitions
5752 etc. should still be started from rcS.d/, but there is for example no
5753 need to have the network enabled before the single user login prompt
5754 is presented.
</p
>
5756 <p
>As always, things are not so easy to fix as they sound. To keep
5757 Debian systems working while scripts migrate and during upgrades, the
5758 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5759 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5760 and the next ones can only be moved when their dependencies have been
5761 moved first. This migration must be done sequentially while we ensure
5762 that the package system upgrade packages in the right order to keep
5763 the system state correct. This will require some coordination when it
5764 comes to network related packages, but most of the packages with
5765 scripts that should migrate do not have anything in rcS.d/ depending
5766 on them. Some packages have already been updated, like the sudo
5767 package, while others are still left to do. I wish I had time to work
5768 on this myself, but real live constrains make it unlikely that I will
5769 find time to push this forward.
</p
>
5774 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
5775 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
5776 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
5777 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
5778 <description><p
>While at Debconf11, I have several times during discussions
5779 mentioned the issues I believe should be improved in Debian for its
5780 desktop to be useful for more people. The use case for this is my
5781 parents, which are currently running Kubuntu which solve the
5784 <p
>I suspect these four missing features are not very hard to
5785 implement. After all, they are present in Ubuntu, so if we wanted to
5786 do this in Debian we would have a source.
</p
>
5790 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
5791 are new packages available for upgrades, a icon in the KDE status bar
5792 indicate this, and clicking on it will activate the simple upgrade
5793 tool to handle it. I have no problem guiding both of my parents
5794 through the process over the phone. If a kernel reboot is required,
5795 this too is indicated by the status bars and the upgrade tool. Last
5796 time I checked, nothing with the same features was working in KDE in
5799 <li
><strong
>Simple handling of missing Firefox browser
5800 plugins.
</strong
> When the browser encounter a MIME type it do not
5801 currently have a handler for, it will ask the user if the system
5802 should search for a package that would add support for this MIME type,
5803 and if the user say yes, the APT sources will be searched for packages
5804 advertising the MIME type in their control file (visible in the
5805 Packages file in the APT archive). If one or more packages are found,
5806 it is a simple click of the mouse to add support for the missing mime
5807 type. If the package require the user to accept some non-free
5808 license, this is explained to the user. The entire process make it
5809 more clear to the user why something do not work in the browser, and
5810 make the chances higher for the user to blame the web page authors and
5811 not the browser for any missing features.
</li
>
5813 <li
><strong
>Simple handling of missing multimedia codec/format
5814 handlers.
</strong
> When the media players encounter a format or codec
5815 it is not supporting, a dialog pop up asking the user if the system
5816 should search for a package that would add support for it. This
5817 happen with things like MP3, Windows Media or H
.264. The selection
5818 and installation procedure is very similar to the Firefox browser
5819 plugin handling. This is as far as I know implemented using a
5820 gstreamer hook. The end result is that the user easily get access to
5821 the codecs that are present from the APT archives available, while
5822 explaining more on why a given format is unsupported by Ubuntu.
</li
>
5824 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
5825 displaying a text/plain file in my Debian browser, it will propose to
5826 start emacs to show it. If I remember correctly, when doing the same
5827 in Kunbutu it show the file as a text file in the browser. At least I
5828 know Opera will show text files within the browser. I much prefer the
5829 latter behaviour.
</li
>
5833 <p
>There are other nice features as well, like the simplified suite
5834 upgrader, but given that I am the one mostly doing the dist-upgrade,
5835 it do not matter much.
</p
>
5837 <p
>I really hope we could get these features in place for the next
5838 Debian release. It would require the coordinated effort of several
5839 maintainers, but would make the end user experience a lot better.
</p
>
5844 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
5845 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
5846 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
5847 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
5848 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
5849 site is build on Debian/Squeeze, and this platform was chosen because
5850 I am most familiar with Debian (being a Debian Developer for around
10
5851 years) because it is the latest stable Debian release which should get
5852 security support for a few years.
</p
>
5854 <p
>The web service is written in Perl, and depend on some perl modules
5855 that are missing in Debian at the moment. It would be great if these
5856 modules were added to the Debian archive, allowing anyone to set up
5857 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
5858 in their own country using only Debian packages. The list of modules
5859 missing in Debian/Squeeze isn
't very long, and I hope the perl group
5860 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
5861 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5862 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5863 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5864 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5865 easier in the future.
</p
>
5867 <p
>Thanks to the great tools in Debian, getting the missing modules
5868 installed on my server was a simple call to
'cpan2deb Module::Name
'
5869 and
'dpkg -i
' to install the resulting package. But this leave me
5870 with the responsibility of tracking security problems, which I really
5871 do not have time for.
</p
>
5876 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
5877 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
5878 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
5879 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
5880 <description><p
>Here is a small update for my English readers. Most of my blog
5881 posts have been in Norwegian the last few weeks, so here is a short
5882 update in English.
</p
>
5884 <p
>The kids still keep me too busy to get much free software work
5885 done, but I did manage to organise a project to get a Norwegian port
5886 of the British service
5887 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
5888 and it has been running for a month now. The entire project has been
5889 organised by me and two others. Around Christmas we gathered sponsors
5890 to fund the development work. In January I drafted a contract with
5891 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
5892 and in February the development took place. Most of it involved
5893 converting the source to use GPS coordinates instead of British
5894 easting/northing, and the resulting code should be a lot easier to get
5895 running in any country by now. The Norwegian
5896 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
5897 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
5898 source and the source for administrative borders in Norway, and
5899 support for this had to be added/fixed.
</p
>
5901 <p
>The Norwegian version went live March
3th, and we spent the weekend
5902 polishing the system before we announced it March
7th. The system is
5903 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
5904 problem reports in a few weeks. Soon we hope to announce the Android
5905 and iPhone versions making it even easier to report problems with the
5906 public infrastructure.
</p
>
5908 <p
>Perhaps something to consider for those of you in countries without
5909 such service?
</p
>
5914 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
5915 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
5916 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
5917 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
5918 <description><p
>The last few days I have looked at ways to track open security
5919 issues here at my work with the University of Oslo. My idea is that
5920 it should be possible to use the information about security issues
5921 available on the Internet, and check our locally
5922 maintained/distributed software against this information. It should
5923 allow us to verify that no known security issues are forgotten. The
5924 CVE database listing vulnerabilities seem like a great central point,
5925 and by using the package lists from Debian mapped to CVEs provided by
5926 the testing security team, I believed it should be possible to figure
5927 out which security holes were present in our free software
5928 collection.
</p
>
5930 <p
>After reading up on the topic, it became obvious that the first
5931 building block is to be able to name software packages in a unique and
5932 consistent way across data sources. I considered several ways to do
5933 this, for example coming up with my own naming scheme like using URLs
5934 to project home pages or URLs to the Freshmeat entries, or using some
5935 existing naming scheme. And it seem like I am not the first one to
5936 come across this problem, as MITRE already proposed and implemented a
5937 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
5938 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
5939 software, hardware and other platform components. The CPE ids are
5940 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
5941 Vulnerability Database
</a
>, allowing me to look up know security
5942 issues for any CPE name. With this in place, all I need to do is to
5943 locate the CPE id for the software packages we use at the university.
5944 This is fairly trivial (I google for
'cve cpe $package
' and check the
5945 NVD entry if a CVE for the package exist).
</p
>
5947 <p
>To give you an example. The GNU gzip source package have the CPE
5948 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
5949 check out, one could look up
5950 <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
5951 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
5952 The most recent one is
5953 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
5954 and at the bottom of the NVD page for this vulnerability the complete
5955 list of affected versions is provided.
</p
>
5957 <p
>The NVD database of CVEs is also available as a XML dump, allowing
5958 for offline processing of issues. Using this dump, I
've written a
5959 small script taking a list of CPEs as input and list all CVEs
5960 affecting the packages represented by these CPEs. One give it CPEs
5961 with version numbers as specified above and get a list of open
5962 security issues out.
</p
>
5964 <p
>Of course for this approach to be useful, the quality of the NVD
5965 information need to be high. For that to happen, I believe as many as
5966 possible need to use and contribute to the NVD database. I notice
5968 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
5969 map from CVE to CPE
</a
>, indicating that they are using the CPE
5970 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
5972 <p
>To get an idea about the quality for free software, I spent some
5973 time making it possible to compare the CVE database from Debian with
5974 the CVE database in NVD. The result look fairly good, but there are
5975 some inconsistencies in NVD (same software package having several
5976 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5977 Debian believe are affected by a CVE). Hope to find time to improve
5978 the quality of NVD, but that require being able to get in touch with
5979 someone maintaining it. So far my three emails with questions and
5980 corrections have not seen any reply, but I hope contact can be
5981 established soon.
</p
>
5983 <p
>An interesting application for CPEs is cross platform package
5984 mapping. It would be useful to know which packages in for example
5985 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5986 this would be trivial if all linux distributions provided CPE entries
5987 for their packages.
</p
>
5992 <title>Which module is loaded for a given PCI and USB device?
</title>
5993 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
5994 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
5995 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
5996 <description><p
>In the
5997 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
5998 package in Debian, there is a script to report useful information
5999 about the running hardware for use when people report missing
6000 information. One part of this script that I find very useful when
6001 debugging hardware problems, is the part mapping loaded kernel module
6002 to the PCI device it claims. It allow me to quickly see if the kernel
6003 module I expect is driving the hardware I am struggling with. To see
6004 the output, make sure discover-data is installed and run
6005 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
6006 one of my machines like this:
</p
>
6010 10de:
03eb i2c_nforce2
6013 10de:
03f0 snd_hda_intel
6022 <p
>The code in question look like this, slightly modified for
6023 readability and to drop the output to file descriptor
3:
</p
>
6026 if [ -d /sys/bus/pci/devices/ ] ; then
6027 echo loaded pci modules:
6029 cd /sys/bus/pci/devices/
6030 for address in * ; do
6031 if [ -d
"$address/driver/module
" ] ; then
6032 module=`cd $address/driver/module ; pwd -P | xargs basename`
6033 if grep -q
"^$module
" /proc/modules ; then
6034 address=$(echo $address |sed s/
0000://)
6035 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
6036 echo
"$id $module
"
6045 <p
>Similar code could be used to extract USB device module
6049 if [ -d /sys/bus/usb/devices/ ] ; then
6050 echo loaded usb modules:
6052 cd /sys/bus/usb/devices/
6053 for address in * ; do
6054 if [ -d
"$address/driver/module
" ] ; then
6055 module=`cd $address/driver/module ; pwd -P | xargs basename`
6056 if grep -q
"^$module
" /proc/modules ; then
6057 address=$(echo $address |sed s/
0000://)
6058 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
6059 if [
"$id
" ] ; then
6060 echo
"$id $module
"
6070 <p
>This might perhaps be something to include in other tools as
6076 <title>How to test if a laptop is working with Linux
</title>
6077 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
6078 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
6079 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
6080 <description><p
>The last few days I have spent at work here at the
<a
6081 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
6082 batch of computers will work with Linux. Every year for the last few
6083 years the university have organised shared bid of a few thousand
6084 computers, and this year HP won the bid. Two different desktops and
6085 five different laptops are on the list this year. We in the UNIX
6086 group want to know which one of these computers work well with RHEL
6087 and Ubuntu, the two Linux distributions we currently handle at the
6088 university.
</p
>
6090 <p
>My test method is simple, and I share it here to get feedback and
6091 perhaps inspire others to test hardware as well. To test, I PXE
6092 install the OS version of choice, and log in as my normal user and run
6093 a few applications and plug in selected pieces of hardware. When
6094 something fail, I make a note about this in the test matrix and move
6095 on. If I have some spare time I try to report the bug to the OS
6096 vendor, but as I only have the machines for a short time, I rarely
6097 have the time to do this for all the problems I find.
</p
>
6099 <p
>Anyway, to get to the point of this post. Here is the simple tests
6100 I perform on a new model.
</p
>
6104 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
6105 and Ubuntu Maverik at the moment. If I feel like it, I also test with
6106 RHEL5 and Debian Edu/Squeeze.
</li
>
6108 <li
>Is X.org working? If the graphical login screen show up after
6109 installation, X.org is working.
</li
>
6111 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
6112 package mesa-utils on Ubuntu) and writing down the frames per second
6113 reported by the program.
</li
>
6115 <li
>Is sound working? With Gnome and KDE, a sound is played when
6116 logging in, and if I can hear this the test is successful. If there
6117 are several audio exits on the machine, I try them all and check if
6118 the Gnome/KDE audio mixer can control where to send the sound. I
6119 normally test this by playing
6120 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
6121 video
</a
> in Firefox/Iceweasel.
</li
>
6123 <li
>Is the USB subsystem working? I test this by plugging in a USB
6124 memory stick and see if Gnome/KDE notices this.
</li
>
6126 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
6127 I have lying around, and see if Gnome/KDE notices this.
</li
>
6129 <li
>Is any built in camera working? Test using cheese, and see if a
6130 picture from the v4l device show up.
</li
>
6132 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
6133 any bluetooth devices are discovered. In my office, I normally see a
6136 <li
>For laptops, is the SD or Compaq Flash reader working. I have
6137 memory modules lying around, and stick them in and see if Gnome/KDE
6138 notice this.
</li
>
6140 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
6141 special button work, and if the laptop continue to work after
6144 <li
>For laptops, is the extra buttons working, like audio level,
6145 adjusting background light, switching on/off external video output,
6146 switching on/off wifi, bluetooth, etc? The set of buttons differ from
6147 laptop to laptop, so I just write down which are working and which are
6150 <li
>Some laptops have smart card readers, finger print readers,
6151 acceleration sensors etc. I rarely test these, as I do not know how
6152 to quickly test if they are working or not, so I only document their
6153 existence.
</li
>
6157 <p
>By now I suspect you are really curious what the test results are
6158 for the HP machines I am testing. I
'm not done yet, so I will report
6159 the test results later. For now I can report that HP
8100 Elite work
6160 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
6161 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
6162 can see, I have most machines left to test. One interesting
6163 observation is that Ubuntu Lucid has almost twice the frame rate than
6164 RHEL6 with glxgears. No idea why.
</p
>
6169 <title>Some thoughts on BitCoins
</title>
6170 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
6171 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
6172 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
6173 <description><p
>As I continue to explore
6174 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
6175 what properties the system have, and how it will be affected by laws
6176 and regulations here in Norway. Here are some random notes.
</p
>
6178 <p
>One interesting thing to note is that since the transactions are
6179 verified using a peer to peer network, all details about a transaction
6180 is known to everyone. This means that if a BitCoin address has been
6181 published like I did with mine in my initial post about BitCoin, it is
6182 possible for everyone to see how many BitCoins have been transfered to
6183 that address. There is even a web service to look at the details for
6184 all transactions. There I can see that my address
6185 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
6186 have received
16.06 Bitcoin, the
6187 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
6188 address of Simon Phipps have received
181.97 BitCoin and the address
6189 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
6190 of EFF have received
2447.38 BitCoins so far. Thank you to each and
6191 every one of you that donated bitcoins to support my activity. The
6192 fact that anyone can see how much money was transfered to a given
6193 address make it more obvious why the BitCoin community recommend to
6194 generate and hand out a new address for each transaction. I
'm told
6195 there is no way to track which addresses belong to a given person or
6196 organisation without the person or organisation revealing it
6197 themselves, as Simon, EFF and I have done.
</p
>
6199 <p
>In Norway, and in most other countries, there are laws and
6200 regulations limiting how much money one can transfer across the border
6201 without declaring it. There are money laundering, tax and accounting
6202 laws and regulations I would expect to apply to the use of BitCoin.
6203 If the Skolelinux foundation
6204 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
6205 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
6206 normal bank transfers like EFF is doing, how should this be accounted?
6207 Given that it is impossible to know if money can cross the border or
6208 not, should everything or nothing be declared? What exchange rate
6209 should be used when calculating taxes? Would receivers have to pay
6210 income tax if the foundation were to pay Skolelinux contributors in
6211 BitCoin? I have no idea, but it would be interesting to know.
</p
>
6213 <p
>For a currency to be useful and successful, it must be trusted and
6214 accepted by a lot of users. It must be possible to get easy access to
6215 the currency (as a wage or using currency exchanges), and it must be
6216 easy to spend it. At the moment BitCoin seem fairly easy to get
6217 access to, but there are very few places to spend it. I am not really
6218 a regular user of any of the vendor types currently accepting BitCoin,
6219 so I wonder when my kind of shop would start accepting BitCoins. I
6220 would like to buy electronics, travels and subway tickets, not herbs
6221 and books. :) The currency is young, and this will improve over time
6222 if it become popular, but I suspect regular banks will start to lobby
6223 to get BitCoin declared illegal if it become popular. I
'm sure they
6224 will claim it is helping fund terrorism and money laundering (which
6225 probably would be true, as is any currency in existence), but I
6226 believe the problems should be solved elsewhere and not by blaming
6227 currencies.
</p
>
6229 <p
>The process of creating new BitCoins is called mining, and it is
6230 CPU intensive process that depend on a bit of luck as well (as one is
6231 competing against all the other miners currently spending CPU cycles
6232 to see which one get the next lump of cash). The
"winner
" get
50
6233 BitCoin when this happen. Yesterday I came across the obvious way to
6234 join forces to increase ones changes of getting at least some coins,
6235 by coordinating the work on mining BitCoins across several machines
6236 and people, and sharing the result if one is lucky and get the
50
6238 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
6239 if this sounds interesting. I have not had time to try to set up a
6240 machine to participate there yet, but have seen that running on ones
6241 own for a few days have not yield any BitCoins througth mining
6244 <p
>Update
2010-
12-
15: Found an
<a
6245 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
6246 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
6247 it was interesting to read. The arguments presented seem to be
6248 equally valid for gold, which was used as a currency for many years.
</p
>
6253 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
6254 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
6255 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
6256 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
6257 <description><p
>With this weeks lawless
6258 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
6259 attacks
</a
> on Wikileak and
6260 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
6261 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
6262 not be trusted to handle money transactions.
6264 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
6265 Phipps on bitcoin
</a
> reminded me about a project that a friend of
6266 mine mentioned earlier. I decided to follow Simon
's example, and get
6267 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
6268 some help from my friend to get it all running, and he even handed me
6269 some bitcoins to get started. I even donated a few bitcoins to Simon
6270 for helping me remember BitCoin.
</p
>
6272 <p
>So, what is bitcoins, you probably wonder? It is a digital
6273 crypto-currency, decentralised and handled using peer-to-peer
6274 networks. It allows anonymous transactions and prohibits central
6275 control over the transactions, making it impossible for governments
6276 and companies alike to block donations and other transactions. The
6277 source is free software, and while the key dependency wxWidgets
2.9
6278 for the graphical user interface is missing in Debian, the command
6279 line client builds just fine. Hopefully Jonas
6280 <a href=
"http://bugs.debian.org/
578157">will get the package into
6281 Debian
</a
> soon.
</p
>
6283 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
6284 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
6285 bitcoins
</a
> when selling services and goods, and there are even
6286 currency
"stock
" markets where the exchange rate is decided. There
6287 are not many users so far, but the concept seems promising. If you
6288 want to get started and lack a friend with any bitcoins to spare,
6290 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
6291 bitcoin at the time of writing). Use
6292 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
6293 on the current exchange rates.
</p
>
6295 <p
>As an experiment, I have decided to set up bitcoind on one of my
6296 machines. If you want to support my activity, please send Bitcoin
6297 donations to the address
6298 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
6303 <title>Why isn
't Debian Edu using VLC?
</title>
6304 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
6305 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
6306 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
6307 <description><p
>In the latest issue of Linux Journal, the readers choices were
6308 presented, and the winner among the multimedia player were VLC.
6309 Personally, I like VLC, and it is my player of choice when I first try
6310 to play a video file or stream. Only if VLC fail will I drag out
6311 gmplayer to see if it can do better. The reason is mostly the failure
6312 model and trust. When VLC fail, it normally pop up a error message
6313 reporting the problem. When mplayer fail, it normally segfault or
6314 just hangs. The latter failure mode drain my trust in the program.
<p
>
6316 <p
>But even if VLC is my player of choice, we have choosen to use
6317 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
6318 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
6319 plugin to play web videos seamlessly, and the VLC browser plugin is
6320 not very good. For example, it lack in-line control buttons, so there
6321 is no way for the user to pause the video. Also, when I
6322 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
6323 tested the browser plugins
</a
> available in Debian, the VLC plugin
6324 failed on several video pages where mplayer based plugins worked. If
6325 the browser plugin for VLC was as good as the gecko-mediaplayer
6326 package (which uses mplayer), we would switch.
</P
>
6328 <p
>While VLC is a good player, its user interface is slightly
6329 annoying. The most annoying feature is its inconsistent use of
6330 keyboard shortcuts. When the player is in full screen mode, its
6331 shortcuts are different from when it is playing the video in a window.
6332 For example, space only work as pause when in full screen mode. I
6333 wish it had consisten shortcuts and that space also would work when in
6334 window mode. Another nice shortcut in gmplayer is [enter] to restart
6335 the current video. It is very nice when playing short videos from the
6336 web and want to restart it when new people arrive to have a look at
6337 what is going on.
</p
>
6342 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
6343 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
6344 <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>
6345 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
6346 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
6347 upgrade testing of the
6348 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
6349 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
6350 This seem like a very good idea, so I adjusted by test scripts and
6351 can now present the updated result from today:
</p
>
6353 <p
>This is for Gnome:
</p
>
6355 <p
>Installed using apt-get, missing with aptitude
</p
>
6357 <blockquote
><p
>
6362 browser-plugin-gnash
6369 freedesktop-sound-theme
6371 gconf-defaults-service
6386 gnome-desktop-environment
6390 gnome-session-canberra
6395 gstreamer0.10-fluendo-mp3
6401 libapache2-mod-dnssd
6404 libaprutil1-dbd-sqlite3
6407 libboost-date-time1.42
.0
6408 libboost-python1.42
.0
6409 libboost-thread1.42
.0
6411 libchamplain-gtk-
0.4-
0
6413 libclutter-gtk-
0.10-
0
6420 libfreerdp-plugins-standard
6435 libgnomepanel2.24-cil
6440 libgtksourceview2.0-common
6441 libmono-addins-gui0.2-cil
6442 libmono-addins0.2-cil
6443 libmono-cairo2.0-cil
6444 libmono-corlib2.0-cil
6445 libmono-i18n-west2.0-cil
6446 libmono-posix2.0-cil
6447 libmono-security2.0-cil
6448 libmono-sharpzip2.84-cil
6449 libmono-system2.0-cil
6452 libndesk-dbus-glib1.0-cil
6453 libndesk-dbus1.0-cil
6463 libtelepathy-farsight0
6472 nautilus-sendto-empathy
6476 python-aptdaemon-gtk
6478 python-beautifulsoup
6493 python-gtksourceview2
6504 python-pkg-resources
6511 python-twisted-conch
6517 python-zope.interface
6522 rhythmbox-plugin-cdrecorder
6529 system-config-printer-udev
6531 telepathy-mission-control-
5
6542 </p
></blockquote
>
6544 <p
>Installed using apt-get, removed with aptitude
</p
>
6546 <blockquote
><p
>
6552 fast-user-switch-applet
6571 libgtksourceview2.0-
0
6573 libsdl1.2debian-alsa
6579 system-config-printer
6584 </p
></blockquote
>
6586 <p
>Installed using aptitude, missing with apt-get
</p
>
6588 <blockquote
><p
>
6589 gstreamer0.10-gnomevfs
6590 </p
></blockquote
>
6592 <p
>Installed using aptitude, removed with apt-get
</p
>
6594 <blockquote
><p
>
6596 </p
></blockquote
>
6598 <p
>This is for KDE:
</p
>
6600 <p
>Installed using apt-get, missing with aptitude
</p
>
6602 <blockquote
><p
>
6604 </p
></blockquote
>
6606 <p
>Installed using apt-get, removed with aptitude
</p
>
6608 <blockquote
><p
>
6611 </p
></blockquote
>
6613 <p
>Installed using aptitude, missing with apt-get
</p
>
6615 <blockquote
><p
>
6629 kdeartwork-emoticons
6631 kdeartwork-theme-icon
6635 kdebase-workspace-bin
6636 kdebase-workspace-data
6650 kscreensaver-xsavers
6665 plasma-dataengines-workspace
6667 plasma-desktopthemes-artwork
6668 plasma-runners-addons
6669 plasma-scriptengine-googlegadgets
6670 plasma-scriptengine-python
6671 plasma-scriptengine-qedje
6672 plasma-scriptengine-ruby
6673 plasma-scriptengine-webkit
6674 plasma-scriptengines
6675 plasma-wallpapers-addons
6676 plasma-widget-folderview
6677 plasma-widget-networkmanagement
6681 xscreensaver-data-extra
6683 xscreensaver-gl-extra
6684 xscreensaver-screensaver-bsod
6685 </p
></blockquote
>
6687 <p
>Installed using aptitude, removed with apt-get
</p
>
6689 <blockquote
><p
>
6691 google-gadgets-common
6709 libggadget-qt-
1.0-
0b
6714 libkonqsidebarplugin4a
6723 libplasma-geolocation-interface4
6725 libplasmagenericshell4
6739 libsmokeknewstuff2-
3
6740 libsmokeknewstuff3-
3
6742 libsmokektexteditor3
6750 libsmokeqtnetwork4-
3
6756 libsmokeqtuitools4-
3
6768 plasma-dataengines-addons
6769 plasma-scriptengine-superkaramba
6770 plasma-widget-lancelot
6771 plasma-widgets-addons
6772 plasma-widgets-workspace
6776 update-notifier-common
6777 </p
></blockquote
>
6779 <p
>Running apt-get autoremove made the results using apt-get and
6780 aptitude a bit more similar, but there are still quite a lott of
6781 differences. I have no idea what packages should be installed after
6782 the upgrade, but hope those that do can have a look.
</p
>
6787 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
6788 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
6789 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
6790 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
6791 <description><p
>Most of the computers in use by the
6792 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
6793 are virtual machines. And they have been Xen machines running on a
6794 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
6795 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
6796 bit harder that it could have been, because we set up the Xen virtual
6797 machines to get the virtual partitions from LVM, which as far as I
6798 know is not supported by KVM. So to migrate, we had to convert
6799 several LVM logical volumes to partitions on a virtual disk file.
</p
>
6802 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
6803 nice recipe
</a
> to do this, and wrote the following script to do the
6804 migration. It uses qemu-img from the qemu package to make the disk
6805 image, parted to partition it, losetup and kpartx to present the disk
6806 image partions as devices, and dd to copy the data. I NFS mounted the
6807 new servers storage area on the old server to do the migration.
</p
>
6813 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6818 if [ -z
"$
1" ] ; then
6819 echo
"Usage: $
0 &lt;hostname
&gt;
"
6825 if [ ! -e /dev/vg_data/$host-disk ] ; then
6826 echo
"error: unable to find LVM volume for $host
"
6830 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6831 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
6832 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
6833 totalsize=$(( ( $disksize + $swapsize ) ))
6836 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
6837 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6839 parted $img mklabel msdos
6840 parted $img mkpart primary linux-swap
0 $disksize
6841 parted $img mkpart primary ext2 $disksize $totalsize
6842 parted $img set
1 boot on
6845 losetup /dev/loop0 $img
6846 kpartx -a /dev/loop0
6848 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
6849 fsck.ext3 -f /dev/mapper/loop0p1 || true
6850 mkswap /dev/mapper/loop0p2
6852 kpartx -d /dev/loop0
6853 losetup -d /dev/loop0
6856 <p
>The script is perhaps so simple that it is not copyrightable, but
6857 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
6859 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
6860 the new disk image attached, installed grub-pc and linux-image-
686 and
6861 set up grub to boot from the disk image. After this, the KVM machines
6862 seem to work just fine.
</p
>
6867 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
6868 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
6869 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
6870 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
6871 <description><p
>I
'm still running upgrade testing of the
6872 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
6873 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
6874 status. Here is a short update based on a test I ran
20101118.
</p
>
6876 <p
>I still do not know what a correct migration should look like, so I
6877 report any differences between apt and aptitude and hope someone else
6878 can see if anything should be changed.
</p
>
6880 <p
>This is for Gnome:
</p
>
6882 <p
>Installed using apt-get, missing with aptitude
</p
>
6884 <blockquote
><p
>
6885 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6886 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
6887 dmz-cursor-theme empathy empathy-common finger
6888 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6889 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6890 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6891 gnome-cards-data gnome-codec-install gnome-core
6892 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6893 gnome-search-tool gnome-session-canberra gnome-spell
6894 gnome-system-log gnome-themes-extras gnome-themes-more
6895 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6896 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6897 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6898 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6899 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
6900 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
6901 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
6902 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
6903 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
6904 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6905 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
6906 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6907 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6908 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6909 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6910 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6911 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6912 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6913 libmono-security2.0-cil libmono-sharpzip2.84-cil
6914 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
6915 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
6916 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
6917 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
6918 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
6919 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
6920 libxalan2-java libxerces2-java media-player-info mesa-utils
6921 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
6922 nautilus-sendto-empathy openoffice.org-writer2latex
6923 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
6924 python-aptdaemon python-aptdaemon-gtk python-axiom
6925 python-beautifulsoup python-bugbuddy python-clientform
6926 python-coherence python-configobj python-crypto python-cupshelpers
6927 python-cupsutils python-eggtrayicon python-elementtree
6928 python-epsilon python-evolution python-feedparser python-gdata
6929 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6930 python-gtksourceview2 python-httplib2 python-louie python-mako
6931 python-markupsafe python-mechanize python-nevow python-notify
6932 python-opengl python-openssl python-pam python-pkg-resources
6933 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6934 python-tagpy python-twisted-bin python-twisted-conch
6935 python-twisted-core python-twisted-web python-utidylib python-webkit
6936 python-xdg python-zope.interface remmina remmina-plugin-data
6937 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6938 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6939 software-center svgalibg1 system-config-printer-udev
6940 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
6941 totem totem-coherence totem-mozilla totem-plugins
6942 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6944 </p
></blockquote
>
6946 Installed using apt-get, removed with aptitude
6948 <blockquote
><p
>
6949 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6950 epiphany-extensions epiphany-gecko evolution-exchange
6951 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6952 gedit-common gnome-app-install gnome-games gnome-games-data
6953 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6954 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6955 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6956 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
6957 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
6958 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
6959 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
6960 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
6961 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
6962 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
6963 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
6964 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
6965 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6966 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6967 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6968 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6969 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
6970 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
6971 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
6972 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
6973 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
6974 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6975 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6976 sound-juicer swfdec-gnome system-config-printer totem-common
6977 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6978 </p
></blockquote
>
6980 <p
>Installed using aptitude, missing with apt-get
</p
>
6982 <blockquote
><p
>
6983 gstreamer0.10-gnomevfs
6984 </p
></blockquote
>
6986 <p
>Installed using aptitude, removed with apt-get
</p
>
6988 <blockquote
><p
>
6990 </p
></blockquote
>
6992 <p
>This is for KDE:
</p
>
6994 <p
>Installed using apt-get, missing with aptitude
</p
>
6996 <blockquote
><p
>
6997 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
6998 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6999 ghostscript-x git gnome-audio gnugo granatier gs-common
7000 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
7001 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
7002 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
7003 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7004 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
7005 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
7006 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7007 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
7008 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
7009 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
7010 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
7011 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
7012 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
7013 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
7014 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
7015 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
7016 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
7017 libkrossui4 libmailtools-perl libmime-tools-perl
7018 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
7019 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
7020 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
7021 lirc luatex marble networkstatus noatun-plugins
7022 openoffice.org-writer2latex palapeli palapeli-data parley
7023 parley-data poster psutils pulseaudio pulseaudio-esound-compat
7024 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
7025 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
7027 </p
></blockquote
>
7029 <p
>Installed using apt-get, removed with aptitude
</p
>
7031 <blockquote
><p
>
7032 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
7033 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
7034 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
7035 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
7036 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
7037 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
7038 kitchensync kiten kjumpingcube klatin klettres klickety klines
7039 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
7040 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
7041 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
7042 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
7043 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
7044 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
7045 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
7046 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
7047 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7048 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
7049 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
7050 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7051 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
7052 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
7053 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
7054 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
7055 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7056 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
7057 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
7058 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
7059 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
7060 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
7061 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
7062 mpeglib network-manager-kde noatun pmount tex-common texlive-base
7063 texlive-common texlive-doc-base texlive-fonts-recommended tidy
7064 ttf-dustin ttf-kochi-gothic ttf-sjfonts
7065 </p
></blockquote
>
7067 <p
>Installed using aptitude, missing with apt-get
</p
>
7069 <blockquote
><p
>
7070 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
7071 kdeartwork kdebase kdebase-apps kdebase-workspace
7072 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
7073 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
7074 netpbm plasma-widget-folderview plasma-widget-networkmanagement
7075 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
7076 xscreensaver-screensaver-bsod
7077 </p
></blockquote
>
7079 <p
>Installed using aptitude, removed with apt-get
</p
>
7081 <blockquote
><p
>
7082 kdebase-bin konq-plugins konqueror
7083 </p
></blockquote
>
7088 <title>Gnash buildbot slave and Debian kfreebsd
</title>
7089 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
7090 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
7091 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
7092 <description><p
>Answering
7093 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
7094 call from the Gnash project
</a
> for
7095 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
7096 current source, I have set up a virtual KVM machine on the Debian
7097 Edu/Skolelinux virtualization host to test the git source on
7098 Debian/Squeeze. I hope this can help the developers in getting new
7099 releases out more often.
</p
>
7101 <p
>As the developers want less main-stream build platforms tested to,
7102 I have considered setting up a
<a
7103 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
7104 machine as well. I have also considered using the kfreebsd
7105 architecture in Debian as a file server in NUUG to get access to the
5
7106 TB zfs volume we currently use to store DV video. Because of this, I
7107 finally got around to do a test installation of Debian/Squeeze with
7108 kfreebsd. Installation went fairly smooth, thought I noticed some
7109 visual glitches in the cdebconf dialogs (black cursor left on the
7110 screen at random locations). Have not gotten very far with the
7111 testing. Noticed cfdisk did not work, but fdisk did so it was not a
7112 fatal problem. Have to spend some more time on it to see if it is
7113 useful as a file server for NUUG. Will try to find time to set up a
7114 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
7119 <title>Debian in
3D
</title>
7120 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
7121 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
7122 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
7123 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
7125 <p
>3D printing is just great. I just came across this Debian logo in
7127 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
7128 thingiverse blog
</a
>.
</p
>
7133 <title>Software updates
2010-
10-
24</title>
7134 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
7135 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
7136 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
7137 <description><p
>Some updates.
</p
>
7139 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
7140 raise money for the project is going well. The lower limit of
10
7141 signers was reached in
24 hours, and so far
13 people have signed it.
7142 More signers and more funding is most welcome, and I am really curious
7143 how far we can get before the time limit of December
24 is reached.
7146 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
7147 about what appear to be a great code coverage tool capable of
7148 generating code coverage stats without any changes to the source code.
7150 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
7151 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
7152 It is missing in Debian, but the git source built just fine in Squeeze
7153 after I installed libelf-dev, libdwarf-dev, pkg-config and
7154 libglib2.0-dev. Failed to build in Lenny, but suspect that is
7155 solvable. I hope kcov make it into Debian soon.
</p
>
7157 <p
>Finally found time to wrap up the release notes for
<a
7158 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
7159 new alpha release of Debian Edu
</a
>, and just published the second
7160 alpha test release of the Squeeze based Debian Edu /
7161 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
7162 release. Give it a try if you need a complete linux solution for your
7163 school, including central infrastructure server, workstations, thin
7164 client servers and diskless workstations. A nice touch added
7165 yesterday is RDP support on the thin client servers, for windows
7166 clients to get a Linux desktop on request.
</p
>
7171 <title>Some notes on Flash in Debian and Debian Edu
</title>
7172 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
7173 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
7174 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
7175 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
7176 popularity-contest numbers
</a
>, the adobe-flashplugin package the
7177 second most popular used package that is missing in Debian. The sixth
7178 most popular is flashplayer-mozilla. This is a clear indication that
7179 working flash is important for Debian users. Around
10 percent of the
7180 users submitting data to popcon.debian.org have this package
7181 installed.
</p
>
7183 <p
>In the report written by Lars Risan in August
2008
7184 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
7185 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
7186 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
7187 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
7188 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
7189 web sites require Flash to work, and lacking working Flash support in
7190 the web browser and the problems with installing it was perceived as a
7191 good reason to stay with Windows.
</p
>
7193 <p
>I once saw a funny and sad comment in a web forum, where Linux was
7194 said to be the retarded cousin that did not really understand
7195 everything you told him but could work fairly well. This was a
7196 comment regarding the problems Linux have with proprietary formats and
7197 non-standard web pages, and is sad because it exposes a fairly common
7198 understanding of whose fault it is if web pages that only work in for
7199 example Internet Explorer
6 fail to work on Firefox, and funny because
7200 it explain very well how annoying it is for users when Linux
7201 distributions do not work with the documents they receive or the web
7202 pages they want to visit.
</p
>
7204 <p
>This is part of the reason why I believe it is important for Debian
7205 and Debian Edu to have a well working Flash implementation in the
7206 distribution, to get at least popular sites as Youtube and Google
7207 Video to working out of the box. For Squeeze, Debian have the chance
7208 to include the latest version of Gnash that will make this happen, as
7209 the new release
0.8.8 was published a few weeks ago and is resting in
7210 unstable. The new version work with more sites that version
0.8.7.
7211 The Gnash maintainers have asked for a freeze exception, but the
7212 release team have not had time to reply to it yet. I hope they agree
7213 with me that Flash is important for the Debian desktop users, and thus
7214 accept the new package into Squeeze.
</p
>
7219 <title>Circular package dependencies harms apt recovery
</title>
7220 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
7221 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
7222 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
7223 <description><p
>I discovered this while doing
7224 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
7225 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
7226 in Debian still got circular dependencies, and it is often claimed
7227 that apt and aptitude should be able to handle this just fine, but
7228 some times these dependency loops causes apt to fail.
</p
>
7230 <p
>An example is from todays
7231 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
7232 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
7233 causes perl-modules to fail to upgrade. The cause is simple. If a
7234 package fail to unpack, then only part of packages with the circular
7235 dependency might end up being unpacked when unpacking aborts, and the
7236 ones already unpacked will fail to configure in the recovery phase
7237 because its dependencies are unavailable.
</p
>
7239 <p
>In this log, the problem manifest itself with this error:
</p
>
7241 <blockquote
><pre
>
7242 dpkg: dependency problems prevent configuration of perl-modules:
7243 perl-modules depends on perl (
>=
5.10.1-
1); however:
7244 Version of perl on system is
5.10.0-
19lenny
2.
7245 dpkg: error processing perl-modules (--configure):
7246 dependency problems - leaving unconfigured
7247 </pre
></blockquote
>
7249 <p
>The perl/perl-modules circular dependency is already
7250 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
7251 hopefully be solved as soon as possible, but it is not the only one,
7252 and each one of these loops in the dependency tree can cause similar
7253 failures. Of course, they only occur when there are bugs in other
7254 packages causing the unpacking to fail, but it is rather nasty when
7255 the failure of one package causes the problem to become worse because
7256 of dependency loops.
</p
>
7259 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
7260 tireless effort by Bill Allombert
</a
>, the number of circular
7262 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
7263 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
7265 <p
>Todays testing also exposed a bug in
7266 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
7267 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
7268 apt-get and aptitude, the latter possibly caused by some circular
7269 dependency. Reported both to BTS to try to get someone to look at
7275 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
7276 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
7277 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
7278 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
7279 <description><p
>This is a
7280 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
7282 <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
7284 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
7285 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
7287 <p
>As a step to try to see if it possible to merge the DNS and DHCP
7288 LDAP objects, I have had a look at how the packages pdns-backend-ldap
7289 and dhcp3-server-ldap in Debian use the LDAP server. The two
7290 implementations are quite different in how they use LDAP.
</p
>
7292 To get this information, I started slapd with debugging enabled and
7293 dumped the debug output to a file to get the LDAP searches performed
7294 on a Debian Edu main-server. Here is a summary.
7296 <p
><strong
>powerdns
</strong
></p
>
7298 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
7299 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
7302 <p
>PowerDNS have two modes of operation using LDAP as its backend.
7303 One
"strict
" mode where the forward and reverse DNS lookups are done
7304 using the same LDAP objects, and a
"tree
" mode where the forward and
7305 reverse entries are in two different subtrees in LDAP with a structure
7306 based on the DNS names, as in tjener.intern and
7307 2.2.0.10.in-addr.arpa.
</p
>
7309 <p
>In tree mode, the server is set up to use a LDAP subtree as its
7310 base, and uses a
"base
" scoped search for the DNS name by adding
7311 "dc=tjener,dc=intern,
" to the base with a filter for
7312 "(associateddomain=tjener.intern)
" for the forward entry and
7313 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
7314 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
7315 forward entries, it is looking for attributes named dnsttl, arecord,
7316 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
7317 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
7318 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
7319 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
7320 spfrecord and modifytimestamp. For reverse entries it is looking for
7321 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
7322 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
7323 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
7324 ldapsearch commands could look like this:
</p
>
7326 <blockquote
><pre
>
7327 ldapsearch -h ldap \
7328 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7329 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7330 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7331 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7332 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7333 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7335 ldapsearch -h ldap \
7336 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7337 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
7338 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
7339 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
7340 srvrecord naptrrecord modifytimestamp
7341 </pre
></blockquote
>
7343 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
7344 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
7345 example LDAP objects used there. In addition to these objects, the
7346 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
7347 also exist.
</p
>
7349 <blockquote
><pre
>
7350 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
7352 objectclass: dnsdomain
7353 objectclass: domainrelatedobject
7356 associateddomain: tjener.intern
7358 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
7360 objectclass: dnsdomain2
7361 objectclass: domainrelatedobject
7363 ptrrecord: tjener.intern
7364 associateddomain:
2.2.0.10.in-addr.arpa
7365 </pre
></blockquote
>
7367 <p
>In strict mode, the server behaves differently. When looking for
7368 forward DNS entries, it is doing a
"subtree
" scoped search with the
7369 same base as in the tree mode for a object with filter
7370 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
7371 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
7372 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
7373 naptrrecord and modifytimestamp. For reverse entires it also do a
7374 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
7375 and the requested attributes are associateddomain, dnsttl and
7376 modifytimestamp. In short, in strict mode the objects with ptrrecord
7377 go away, and the arecord attribute in the forward object is used
7380 <p
>The forward and reverse searches can be simulated using ldapsearch
7381 like this:
</p
>
7383 <blockquote
><pre
>
7384 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7385 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7386 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7387 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7388 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7389 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7391 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7392 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
7393 </pre
></blockquote
>
7395 <p
>In addition to the forward and reverse searches , there is also a
7396 search for SOA records, which behave similar to the forward and
7397 reverse lookups.
</p
>
7399 <p
>A thing to note with the PowerDNS behaviour is that it do not
7400 specify any objectclass names, and instead look for the attributes it
7401 need to generate a DNS reply. This make it able to work with any
7402 objectclass that provide the needed attributes.
</p
>
7404 <p
>The attributes are normally provided in the cosine (RFC
1274) and
7405 dnsdomain2 schemas. The latter is used for reverse entries like
7406 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
7408 <p
>In Debian Edu, we have created DNS objects using the object classes
7409 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
7410 attributes) and domainrelatedobject (for associatedDomain). The use
7411 of structural object classes make it impossible to combine these
7412 classes with the object classes used by DHCP.
</p
>
7414 <p
>There are other schemas that could be used too, for example the
7415 dnszone structural object class used by Gosa and bind-sdb for the DNS
7416 attributes combined with the domainrelatedobject object class, but in
7417 this case some unused attributes would have to be included as well
7418 (zonename and relativedomainname).
</p
>
7420 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
7421 mode and not use any of the existing objectclasses (dnsdomain,
7422 dnsdomain2 and dnszone) when one want to combine the DNS information
7423 with DHCP information, and instead create a auxiliary object class
7424 defined something like this (using the attributes defined for
7425 dnsdomain and dnsdomain2 or dnszone):
</p
>
7427 <blockquote
><pre
>
7428 objectclass ( some-oid NAME
'dnsDomainAux
'
7431 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
7432 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
7433 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
7434 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
7435 A6Record $ DNAMERecord
7437 </pre
></blockquote
>
7439 <p
>This will allow any object to become a DNS entry when combined with
7440 the domainrelatedobject object class, and allow any entity to include
7441 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
7442 developers asking for their view on this schema and if they are
7443 interested in providing such schema with PowerDNS, and I hope my
7444 message will be accepted into their mailing list soon.
</p
>
7446 <p
><strong
>ISC dhcp
</strong
></p
>
7448 <p
>The DHCP server searches for specific objectclass and requests all
7449 the object attributes, and then uses the attributes it want. This
7450 make it harder to figure out exactly what attributes are used, but
7451 thanks to the working example in Debian Edu I can at least get an idea
7452 what is needed without having to read the source code.
</p
>
7454 <p
>In the DHCP server configuration, the LDAP base to use and the
7455 search filter to use to locate the correct dhcpServer entity is
7456 stored. These are the relevant entries from
7457 /etc/dhcp3/dhcpd.conf:
</p
>
7459 <blockquote
><pre
>
7460 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
7461 ldap-dhcp-server-cn
"dhcp
";
7462 </pre
></blockquote
>
7464 <p
>The DHCP server uses this information to nest all the DHCP
7465 configuration it need. The cn
"dhcp
" is located using the given LDAP
7466 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
7467 search result is this entry:
</p
>
7469 <blockquote
><pre
>
7470 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
7473 objectClass: dhcpServer
7474 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7475 </pre
></blockquote
>
7477 <p
>The content of the dhcpServiceDN attribute is next used to locate the
7478 subtree with DHCP configuration. The DHCP configuration subtree base
7479 is located using a base scope search with base
"cn=DHCP
7480 Config,dc=skole,dc=skolelinux,dc=no
" and filter
7481 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
7482 The search result is this entry:
</p
>
7484 <blockquote
><pre
>
7485 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7488 objectClass: dhcpService
7489 objectClass: dhcpOptions
7490 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
7491 dhcpStatements: ddns-update-style none
7492 dhcpStatements: authoritative
7493 dhcpOption: smtp-server code
69 = array of ip-address
7494 dhcpOption: www-server code
72 = array of ip-address
7495 dhcpOption: wpad-url code
252 = text
7496 </pre
></blockquote
>
7498 <p
>Next, the entire subtree is processed, one level at the time. When
7499 all the DHCP configuration is loaded, it is ready to receive requests.
7500 The subtree in Debian Edu contain objects with object classes
7501 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
7502 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
7503 and information about netmasks, dynamic range etc. Leaving out the
7504 details here because it is not relevant for the focus of my
7505 investigation, which is to see if it is possible to merge dns and dhcp
7506 related computer objects.
</p
>
7508 <p
>When a DHCP request come in, LDAP is searched for the MAC address
7509 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
7510 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
7511 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
7512 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
7515 <blockquote
><pre
>
7516 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7519 objectClass: dhcpHost
7520 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7521 dhcpStatements: fixed-address hostname
7522 </pre
></blockquote
>
7524 <p
>There is less flexiblity in the way LDAP searches are done here.
7525 The object classes need to have fixed names, and the configuration
7526 need to be stored in a fairly specific LDAP structure. On the
7527 positive side, the invidiual dhcpHost entires can be anywhere without
7528 the DN pointed to by the dhcpServer entries. The latter should make
7529 it possible to group all host entries in a subtree next to the
7530 configuration entries, and this subtree can also be shared with the
7531 DNS server if the schema proposed above is combined with the dhcpHost
7532 structural object class.
7534 <p
><strong
>Conclusion
</strong
></p
>
7536 <p
>The PowerDNS implementation seem to be very flexible when it come
7537 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
7538 come to the the LDAP structure, the
"strict
" mode is very flexible,
7539 allowing DNS objects to be stored anywhere under the base cn specified
7540 in the configuration.
</p
>
7542 <p
>The DHCP implementation on the other hand is very inflexible, both
7543 regarding which LDAP schemas to use and which LDAP structure to use.
7544 I guess one could implement ones own schema, as long as the
7545 objectclasses and attributes have the names used, but this do not
7546 really help when the DHCP subtree need to have a fairly fixed
7547 structure.
</p
>
7549 <p
>Based on the observed behaviour, I suspect a LDAP structure like
7550 this might work for Debian Edu:
</p
>
7552 <blockquote
><pre
>
7554 cn=machine-info (dhcpService) - dhcpServiceDN points here
7555 cn=dhcp (dhcpServer)
7556 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7557 cn=
10.0.2.0 (dhcpSubnet)
7558 cn=group1 (dhcpGroup/dhcpOptions)
7559 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7560 cn=
192.168.0.0 (dhcpSubnet)
7561 cn=group1 (dhcpGroup/dhcpOptions)
7562 ou=machines - PowerDNS base points here
7563 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7564 </pre
></blockquote
>
7566 <P
>This is not tested yet. If the DHCP server require the dhcpHost
7567 entries to be in the dhcpGroup subtrees, the entries can be stored
7568 there instead of a common machines subtree, and the PowerDNS base
7569 would have to be moved one level up to the machine-info subtree.
</p
>
7571 <p
>The combined object under the machines subtree would look something
7572 like this:
</p
>
7574 <blockquote
><pre
>
7575 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7578 objectClass: dhcpHost
7579 objectclass: domainrelatedobject
7580 objectclass: dnsDomainAux
7581 associateddomain: hostname.intern
7582 arecord:
10.11.12.13
7583 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7584 dhcpStatements: fixed-address hostname.intern
7585 </pre
></blockquote
>
7587 </p
>One could even add the LTSP configuration associated with a given
7588 machine, as long as the required attributes are available in a
7589 auxiliary object class.
</p
>
7594 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
7595 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
7596 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
7597 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
7598 <description><p
>For a while now, I have wanted to find a way to change the DNS and
7599 DHCP services in Debian Edu to use the same LDAP objects for a given
7600 computer, to avoid the possibility of having a inconsistent state for
7601 a computer in LDAP (as in DHCP but no DNS entry or the other way
7602 around) and make it easier to add computers to LDAP.
</p
>
7604 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
7605 information finally found a solution that seem to work.
</p
>
7607 <p
>The old setup required three LDAP objects for a given computer.
7608 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7609 we switch powerdns to use its strict LDAP method (ldap-method=strict
7610 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7611 merged into one while making it impossible to transfer the reverse map
7612 to a slave DNS server.
</p
>
7614 <p
>If we also replace the object class used to get the DNS related
7615 attributes to one allowing these attributes to be combined with the
7616 dhcphost object class, we can merge the DNS and DHCP entries into one.
7617 I
've written such object class in the dnsdomainaux.schema file (need
7618 proper OIDs, but that is a minor issue), and tested the setup. It
7619 seem to work.
</p
>
7621 <p
>With this test setup in place, we can get away with one LDAP object
7622 for both DNS and DHCP, and even the LTSP configuration I suggested in
7623 an earlier email. The combined LDAP object will look something like
7626 <blockquote
><pre
>
7627 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7629 objectClass: dhcphost
7630 objectclass: domainrelatedobject
7631 objectclass: dnsdomainaux
7632 associateddomain: hostname.intern
7633 arecord:
10.11.12.13
7634 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
7635 dhcpstatements: fixed-address hostname
7637 </pre
></blockquote
>
7639 <p
>The DNS server uses the associateddomain and arecord entries, while
7640 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7641 before asking DNS to resolve the fixed-adddress. LTSP will use
7642 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
7644 <p
>I am not yet sure if I can get the DHCP server to look for its
7645 dhcphost in a different location, to allow us to put the objects
7646 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
7647 that. If I can
't figure out a way to do that, we can still get rid of
7648 the hosts subtree and move all its content into the DHCP Config tree
7649 (which probably should be renamed to be more related to the new
7650 content. I suspect cn=dnsdhcp,ou=services or something like that
7651 might be a good place to put it.
</p
>
7653 <p
>If you want to help out with implementing this for Debian Edu,
7654 please contact us on debian-edu@lists.debian.org.
</p
>
7659 <title>Idea for storing LTSP configuration in LDAP
</title>
7660 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
7661 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
7662 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
7663 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
7664 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7665 clients, and that this can be used to fetch configuration from LDAP if
7666 Debian Edu choose to store configuration there.
</p
>
7668 <p
>Armed with this information, I got inspired and wrote a test module
7669 to get configuration from LDAP. The idea is to look up the MAC
7670 address of the client in LDAP, and look for attributes on the form
7671 ltspconfigsetting=value, and use this to export SETTING=value to the
7672 LTSP clients.
</p
>
7674 <p
>The goal is to be able to store the LTSP configuration attributes
7675 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
7676 allowing us to store all information about a computer in one place.
</p
>
7678 <p
>This is a untested draft implementation, and I welcome feedback on
7679 this approach. A real LDAP schema for the ltspClientAux objectclass
7680 need to be written. Comments, suggestions, etc?
</p
>
7682 <blockquote
><pre
>
7683 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7685 # Fetch LTSP client settings from LDAP based on MAC address
7687 # Uses ethernet address as stored in the dhcpHost objectclass using
7688 # the dhcpHWAddress attribute or ethernet address stored in the
7689 # ieee802Device objectclass with the macAddress attribute.
7691 # This module is written to be schema agnostic, and only depend on the
7692 # existence of attribute names.
7694 # The LTSP configuration variables are saved directly using a
7695 # ltspConfig prefix and uppercasing the rest of the attribute name.
7696 # To set the SERVER variable, set the ltspConfigServer attribute.
7698 # Some LDAP schema should be created with all the relevant
7699 # configuration settings. Something like this should work:
7701 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
7704 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7706 LDAPSERVER=$(debian-edu-ldapserver)
7707 if [
"$LDAPSERVER
" ] ; then
7708 LDAPBASE=$(debian-edu-ldapserver -b)
7709 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
7710 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
7711 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
7712 grep
'^ltspConfig
' | while read attr value ; do
7713 # Remove prefix and convert to upper case
7714 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
7715 # bass value on to clients
7716 eval
"$attr=$value; export $attr
"
7720 </pre
></blockquote
>
7722 <p
>I
'm not sure this shell construction will work, because I suspect
7723 the while block might end up in a subshell causing the variables set
7724 there to not show up in ltsp-config, but if that is the case I am sure
7725 the code can be restructured to make sure the variables are passed on.
7726 I expect that can be solved with some testing. :)
</p
>
7728 <p
>If you want to help out with implementing this for Debian Edu,
7729 please contact us on debian-edu@lists.debian.org.
</p
>
7731 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
7732 configuration in LDAP that was created around year
2000 by
7733 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
7734 Xperience, Inc.,
2000</a
>. I found its
7735 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
7736 personal home page over at redhat.com.
</p
>
7741 <title>jXplorer, a very nice LDAP GUI
</title>
7742 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
7743 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
7744 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
7745 <description><p
>Since
7746 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
7747 last post
</a
> about available LDAP tools in Debian, I was told about a
7748 LDAP GUI that is even better than luma. The java application
7749 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
7750 moving LDAP objects and subtrees using drag-and-drop, and can
7751 authenticate using Kerberos. I have only tested the Kerberos
7752 authentication, but do not have a LDAP setup allowing me to rewrite
7753 LDAP with my test user yet. It is
7754 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
7755 Debian
</a
> testing and unstable at the moment. The only problem I
7756 have with it is how it handle errors. If something go wrong, its
7757 non-intuitive behaviour require me to go through some query work list
7758 and remove the failing query. Nothing big, but very annoying.
</p
>
7763 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
7764 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
7765 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
7766 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
7767 <description><p
>Here is a short update on my
<a
7768 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
7769 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
7770 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
7771 not reporting the status for KDE, because the upgrade crashes when
7772 aptitude try because of missing conflicts
7773 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
7774 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
7776 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
7777 complete list of the installed packages. Based on this I see these
7778 differences when I did a test run today. As usual, I do not really
7779 know what the correct set of packages would be, but thought it best to
7780 publish the difference.
</p
>
7782 <p
>Installed using apt-get, missing with aptitude
</p
>
7784 <blockquote
><p
>
7785 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
7786 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
7787 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7788 libgtksourceview-common libpt-
1.10.10-plugins-alsa
7789 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7790 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7791 python-
4suite-xml python-eggtrayicon python-gtkhtml2
7792 python-gtkmozembed svgalibg1 xserver-xephyr zip
7793 </p
></blockquote
>
7795 <p
>Installed using apt-get, removed with aptitude
</p
>
7797 <blockquote
><p
>
7798 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7799 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7800 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
7801 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
7802 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
7803 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
7804 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7805 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7806 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7807 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
7808 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
7809 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
7810 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7811 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
7812 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7813 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
7814 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
7815 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7816 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7817 mysql-common swfdec-gnome totem-gstreamer wodim
7818 </p
></blockquote
>
7820 <p
>Installed using aptitude, missing with apt-get
</p
>
7822 <blockquote
><p
>
7823 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7824 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7825 xserver-xorg-input-all xserver-xorg-input-evdev
7826 xserver-xorg-input-kbd xserver-xorg-input-mouse
7827 xserver-xorg-input-synaptics xserver-xorg-video-all
7828 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7829 xserver-xorg-video-chips xserver-xorg-video-cirrus
7830 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7831 xserver-xorg-video-glint xserver-xorg-video-i128
7832 xserver-xorg-video-i740 xserver-xorg-video-mach64
7833 xserver-xorg-video-mga xserver-xorg-video-neomagic
7834 xserver-xorg-video-nouveau xserver-xorg-video-nv
7835 xserver-xorg-video-r128 xserver-xorg-video-radeon
7836 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7837 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7838 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7839 xserver-xorg-video-sis xserver-xorg-video-sisusb
7840 xserver-xorg-video-tdfx xserver-xorg-video-tga
7841 xserver-xorg-video-trident xserver-xorg-video-tseng
7842 xserver-xorg-video-vesa xserver-xorg-video-vmware
7843 xserver-xorg-video-voodoo
7844 </p
></blockquote
>
7846 <p
>Installed using aptitude, removed with apt-get
</p
>
7848 <blockquote
><p
>
7849 deskbar-applet xserver-xorg xserver-xorg-core
7850 xserver-xorg-input-wacom xserver-xorg-video-intel
7851 xserver-xorg-video-openchrome
7852 </p
></blockquote
>
7854 <p
>I was told on IRC that the xorg-xserver package was
7855 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
7856 in git
</a
> today to try to get apt-get to not remove xorg completely.
7857 No idea when it hits Squeeze, but when it does I hope it will reduce
7858 the difference somewhat.
7863 <title>LUMA, a very nice LDAP GUI
</title>
7864 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
7865 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
7866 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
7867 <description><p
>The last few days I have been looking into the status of the LDAP
7868 directory in Debian Edu, and in the process I started to miss a GUI
7869 tool to browse the LDAP tree. The only one I was able to find in
7870 Debian/Squeeze and Lenny is
7871 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
7872 be a great tool to get a overview of the current LDAP directory
7873 populated by default in Skolelinux. Thanks to it, I have been able to
7874 find empty and obsolete subtrees, misplaced objects and duplicate
7875 objects. It will be installed by default in Debian/Squeeze. If you
7876 are working with LDAP, give it a go. :)
</p
>
7878 <p
>I did notice one problem with it I have not had time to report to
7879 the BTS yet. There is no .desktop file in the package, so the tool do
7880 not show up in the Gnome and KDE menus, but only deep down in in the
7881 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7884 <p
>I have not yet been able to get it to modify the tree yet. I would
7885 like to move objects and remove subtrees directly in the GUI, but have
7886 not found a way to do that with LUMA yet. So in the mean time, I use
7887 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
7889 <p
>If you have tips on other GUI tools for LDAP that might be useful
7890 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
7892 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
7893 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
7894 useful GUI alternative. It seem like a good tool, but is unmaintained
7895 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7896 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
7901 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
7902 <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>
7903 <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>
7904 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
7905 <description><p
>A while back, I
7906 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
7907 about the fact
</a
> that it is not possible with the provided schemas
7908 for storing DNS and DHCP information in LDAP to combine the two sets
7909 of information into one LDAP object representing a computer.
</p
>
7911 <p
>In the mean time, I discovered that a simple fix would be to make
7912 the dhcpHost object class auxiliary, to allow it to be combined with
7913 the dNSDomain object class, and thus forming one object for one
7914 computer when storing both DHCP and DNS information in LDAP.
</p
>
7916 <p
>If I understand this correctly, it is not safe to do this change
7917 without also changing the assigned number for the object class, and I
7918 do not know enough about LDAP schema design to do that properly for
7919 Debian Edu.
</p
>
7921 <p
>Anyway, for future reference, this is how I believe we could change
7923 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
7924 schema
</a
> to solve at least part of the problem with the LDAP schemas
7925 available today from IETF.
</p
>
7928 --- dhcp.schema (revision
65192)
7929 +++ dhcp.schema (working copy)
7931 objectclass (
2.16.840.1.113719.1.203.6.6
7932 NAME
'dhcpHost
'
7933 DESC
'This represents information about a particular client
'
7937 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7938 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
7941 <p
>I very much welcome clues on how to do this properly for Debian
7942 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7943 package, and should thus be free to rewrite it as we see fit.
</p
>
7945 <p
>If you want to help out with implementing this for Debian Edu,
7946 please contact us on debian-edu@lists.debian.org.
</p
>
7951 <title>Calling tasksel like the installer, while still getting useful output
</title>
7952 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
7953 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
7954 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
7955 <description><p
>A few times I have had the need to simulate the way tasksel
7956 installs packages during the normal debian-installer run. Until now,
7957 I have ended up letting tasksel do the work, with the annoying problem
7958 of not getting any feedback at all when something fails (like a
7959 conffile question from dpkg or a download that fails), using code like
7962 <blockquote
><pre
>
7963 export DEBIAN_FRONTEND=noninteractive
7964 tasksel --new-install
7965 </pre
></blockquote
>
7967 This would invoke tasksel, let its automatic task selection pick the
7968 tasks to install, and continue to install the requested tasks without
7969 any output what so ever.
7971 Recently I revisited this problem while working on the automatic
7972 package upgrade testing, because tasksel would some times hang without
7973 any useful feedback, and I want to see what is going on when it
7974 happen. Then it occured to me, I can parse the output from tasksel
7975 when asked to run in test mode, and use that aptitude command line
7976 printed by tasksel then to simulate the tasksel run. I ended up using
7979 <blockquote
><pre
>
7980 export DEBIAN_FRONTEND=noninteractive
7981 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
7983 </pre
></blockquote
>
7985 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
7986 --without-recommends -o APT::Install-Recommends=no -y install
7987 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7988 ~pimportant
</tt
>", which will install the gnome desktop task, the
7989 laptop task and all packages with priority standard , required and
7990 important, just like tasksel would have done it during
7991 installation.
</p
>
7993 <p
>A better approach is probably to extend tasksel to be able to
7994 install packages without using debconf-apt-progress, for use cases
7995 like this.
</p
>
8000 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
8001 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
8002 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
8003 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
8004 <description><p
>My
8005 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
8006 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
8007 finally made the upgrade logs available from
8008 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
8009 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
8010 apt and aptitude, and found their differences interesting. This time
8011 I will only focus on their removal plans.
</p
>
8013 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
8014 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
8015 surprising part is that it want to remove xorg and all
8016 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
8017 sure why. When asking aptitude to do the same, it want to remove
129
8018 packages, but most of them are library packages I suspect are no
8019 longer needed. Both of them want to remove bluetooth packages, which
8020 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
8022 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
8023 which seem like a bad idea and xorg the same way as with Gnome. Asking
8024 aptitude for the same, it wants to remove
192 packages, none which are
8025 too surprising.
</p
>
8027 <p
>I guess the removal of xorg during upgrades should be investigated
8028 and avoided, and perhaps others as well. Here are the complete list
8029 of planned removals. The complete logs is available from the URL
8030 above. Note if you want to repeat these tests, that the upgrade test
8031 for kde+apt-get hung in the tasksel setup because of dpkg asking
8032 conffile questions. No idea why. I worked around it by using
8033 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
8036 <p
><b
>apt-get gnome
72</b
>
8037 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
8038 gnome-desktop-environment gnome-network-admin gtkhtml3.14
8039 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
8040 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
8041 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
8042 serpentine swfdec-mozilla update-manager xorg xserver-xorg
8043 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8044 xserver-xorg-input-kbd xserver-xorg-input-mouse
8045 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8046 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8047 xserver-xorg-video-ati xserver-xorg-video-chips
8048 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8049 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8050 xserver-xorg-video-glint xserver-xorg-video-i128
8051 xserver-xorg-video-i740 xserver-xorg-video-imstt
8052 xserver-xorg-video-intel xserver-xorg-video-mach64
8053 xserver-xorg-video-mga xserver-xorg-video-neomagic
8054 xserver-xorg-video-nsc xserver-xorg-video-nv
8055 xserver-xorg-video-openchrome xserver-xorg-video-r128
8056 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8057 xserver-xorg-video-rendition xserver-xorg-video-s3
8058 xserver-xorg-video-s3virge xserver-xorg-video-savage
8059 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8060 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8061 xserver-xorg-video-tga xserver-xorg-video-trident
8062 xserver-xorg-video-tseng xserver-xorg-video-v4l
8063 xserver-xorg-video-vesa xserver-xorg-video-vga
8064 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
8065 xulrunner-
1.9-gnome-support
</p
>
8067 <p
><b
>aptitude gnome
129</b
>
8069 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
8070 djvulibre-desktop finger gnome-app-install gnome-mount
8071 gnome-network-admin gnome-spell gnome-vfs-obexftp
8072 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
8073 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
8074 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
8075 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
8076 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
8077 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
8078 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
8079 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
8080 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
8081 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
8082 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
8083 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
8084 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
8085 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
8086 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
8087 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
8088 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
8089 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
8090 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
8091 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
8092 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
8093 openoffice.org-writer2latex openssl-blacklist p7zip
8094 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
8095 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
8096 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
8097 swfdec-mozilla totem-gstreamer update-manager wodim
8098 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8099 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8102 <p
><b
>apt-get kde
82</b
>
8104 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
8105 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
8106 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
8107 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
8108 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
8109 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
8110 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8111 xserver-xorg-input-kbd xserver-xorg-input-mouse
8112 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8113 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8114 xserver-xorg-video-ati xserver-xorg-video-chips
8115 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8116 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8117 xserver-xorg-video-glint xserver-xorg-video-i128
8118 xserver-xorg-video-i740 xserver-xorg-video-imstt
8119 xserver-xorg-video-intel xserver-xorg-video-mach64
8120 xserver-xorg-video-mga xserver-xorg-video-neomagic
8121 xserver-xorg-video-nsc xserver-xorg-video-nv
8122 xserver-xorg-video-openchrome xserver-xorg-video-r128
8123 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8124 xserver-xorg-video-rendition xserver-xorg-video-s3
8125 xserver-xorg-video-s3virge xserver-xorg-video-savage
8126 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8127 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8128 xserver-xorg-video-tga xserver-xorg-video-trident
8129 xserver-xorg-video-tseng xserver-xorg-video-v4l
8130 xserver-xorg-video-vesa xserver-xorg-video-vga
8131 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
8133 <p
><b
>aptitude kde
192</b
>
8134 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
8135 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
8136 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
8137 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
8138 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8139 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
8140 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
8141 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8142 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
8143 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
8144 kghostview khelpcenter khexedit kiconedit kitchensync klatin
8145 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
8146 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
8147 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
8148 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
8149 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
8150 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
8151 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8152 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
8153 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
8154 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8155 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
8156 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
8157 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
8158 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8159 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
8160 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
8161 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
8162 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
8163 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
8164 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
8165 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
8166 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
8167 texlive-common texlive-doc-base texlive-fonts-recommended
8168 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8169 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8170 xulrunner-
1.9</p
>
8176 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
8177 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
8178 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
8179 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
8180 <description><p
>The last few days I have done some upgrade testing in Debian, to
8181 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
8182 have been discovered and reported in the process
8183 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
8184 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
8185 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
8186 kdebase-workspace-data), and to get a more regular testing going on, I
8187 am working on a script to automate the test.
</p
>
8189 <p
>The idea is to create a Lenny chroot and use tasksel to install a
8190 Gnome or KDE desktop installation inside the chroot before upgrading
8191 it. To ensure no services are started in the chroot, a policy-rc.d
8192 script is inserted. To make sure tasksel believe it is to install a
8193 desktop on a laptop, the tasksel tests are replaced in the chroot
8194 (only acceptable because this is a throw-away chroot).
</p
>
8196 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
8197 currently always fail because udev refuses to upgrade with the kernel
8198 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
8199 is created. The bug report
8200 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
8201 this problem do not trigger in a chroot, but I touch the file anyway
8202 to make sure the upgrade go well. Testing on virtual and real
8203 hardware have failed me because of udev so far, and creating this file
8204 do the trick in such settings anyway. This is a
8205 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
8206 issue
</a
> and the current udev behaviour is intended by the udev
8207 maintainer because he lack the resources to rewrite udev to keep
8208 working with old kernels or something like that. I really wish the
8209 udev upstream would keep udev backwards compatible, to avoid such
8210 upgrade problem, but given that they fail to do so, I guess
8211 documenting the way out of this mess is the best option we got for
8212 Debian Squeeze.
</p
>
8214 <p
>Anyway, back to the task at hand, testing upgrades. This test
8215 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
8218 <blockquote
><pre
>
8222 if [
"$
1" ] ; then
8231 exec
&lt; /dev/null
8233 mirror=http://ftp.skolelinux.org/debian
8234 tmpdir=chroot-$from-upgrade-$to-$desktop
8236 debootstrap $from $tmpdir $mirror
8237 chroot $tmpdir aptitude update
8238 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
8242 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
8246 mount -t proc proc $tmpdir/proc
8247 # Make sure proc is unmounted also on failure
8248 trap exit_cleanup EXIT INT
8250 chroot $tmpdir aptitude -y install debconf-utils
8252 # Make sure tasksel autoselection trigger. It need the test scripts
8253 # to return the correct answers.
8254 echo tasksel tasksel/desktop multiselect $desktop | \
8255 chroot $tmpdir debconf-set-selections
8257 # Include the desktop and laptop task
8258 for test in desktop laptop ; do
8259 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
8263 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
8266 DEBIAN_FRONTEND=noninteractive
8267 DEBIAN_PRIORITY=critical
8268 export DEBIAN_FRONTEND DEBIAN_PRIORITY
8269 chroot $tmpdir tasksel --new-install
8271 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
8272 chroot $tmpdir aptitude update
8273 touch $tmpdir/etc/udev/kernel-upgrade
8274 chroot $tmpdir aptitude -y dist-upgrade
8276 </pre
></blockquote
>
8278 <p
>I suspect it would be useful to test upgrades with both apt-get and
8279 with aptitude, but I have not had time to look at how they behave
8280 differently so far. I hope to get a cron job running to do the test
8281 regularly and post the result on the web. The Gnome upgrade currently
8282 work, while the KDE upgrade fail because of the bug in
8283 kdebase-workspace-data
</p
>
8285 <p
>I am not quite sure what kind of extract from the huge upgrade logs
8286 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
8287 post, so I will refrain from trying. I can report that for Gnome,
8288 aptitude report
760 packages upgraded,
448 newly installed,
129 to
8289 remove and
1 not upgraded and
1024MB need to be downloaded while for
8290 KDE the same numbers are
702 packages upgraded,
507 newly installed,
8291 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
8293 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
8294 is able to migrate to dependency based boot sequencing and parallel
8295 booting without a hitch. Was unsure if there were still bugs with
8296 packages failing to clean up their obsolete init.d script during
8297 upgrades, and no such problem seem to affect the Gnome desktop+laptop
8303 <title>Upstart or sysvinit - as init.d scripts see it
</title>
8304 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
8305 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
8306 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
8307 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
8308 scripts to migrate (some of) their operations to upstart job while
8309 keeping the init.d for hurd and kfreebsd. The packages with such
8310 needs will need a way to get their init.d scripts to behave
8311 differently when used with sysvinit and with upstart. Because of
8312 this, I had a look at the environment variables set when a init.d
8313 script is running under upstart, and when it is not.
</p
>
8315 <p
>With upstart, I notice these environment variables are set when a
8316 script is started from rcS.d/ (ignoring some irrelevant ones like
8319 <blockquote
><pre
>
8325 UPSTART_EVENTS=startup
8327 UPSTART_JOB=rc-sysinit
8328 </pre
></blockquote
>
8330 <p
>With sysvinit, these environment variables are set for the same
8333 <blockquote
><pre
>
8334 INIT_VERSION=sysvinit-
2.88
8339 </pre
></blockquote
>
8341 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
8342 sysvinit are not set by upstart. Not sure if it is intentional or not
8343 to not be compatible with sysvinit in this regard.
</p
>
8345 <p
>For scripts needing to behave differently when upstart is used,
8346 looking for the UPSTART_JOB environment variable seem to be a good
8352 <title>A manual for standards wars...
</title>
8353 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
8354 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
8355 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
8356 <description><p
>Via the
8357 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
8358 of Rob Weir
</a
> I came across the very interesting essay named
8359 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
8360 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
8361 following the standards wars of today.
</p
>
8366 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
8367 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
8368 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
8369 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
8370 <description><p
>When using sitesummary at a site to track machines, it is possible
8371 to get a list of the machine types in use thanks to the DMI
8372 information extracted from each machine. The script to do so is
8373 included in the sitesummary package, and here is example output from
8374 the Skolelinux build servers:
</p
>
8376 <blockquote
><pre
>
8377 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
8379 Dell Computer Corporation
1
8382 eserver xSeries
345 -[
8670M1X]-
1
8386 </pre
></blockquote
>
8388 <p
>The quality of the report depend on the quality of the DMI tables
8389 provided in each machine. Here there are Intel machines without model
8390 information listed with Intel as vendor and no model, and virtual Xen
8391 machines listed as [no-dmi-info]. One can add -l as a command line
8392 option to list the individual machines.
</p
>
8394 <p
>A larger list is
8395 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
8396 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
8397 provide the basic sitesummary report publicly. In their report there
8398 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
8399 their machines, and as sitesummary is available in both distributions,
8400 it is trivial to get all of them to report to the same central
8401 collector.
</p
>
8406 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
8407 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
8408 <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>
8409 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
8410 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
8411 start at boot when an NVidia video card is used is handled. The
8412 problem seem to be that the nvidia X.org driver uses a long time to
8413 initialize, and this duration is longer than kdm is configured to
8416 <p
>I came across two bugs related to this issue,
8417 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
8418 against initscripts and passed on to nvidia-glx when it became obvious
8419 that the nvidia drivers were involved, and
8420 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
8421 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
8423 <p
>To me, it seem that no-one is interested in actually solving the
8424 problem nvidia video card owners experience and make sure the Debian
8425 distribution work out of the box for these users. The nvidia driver
8426 maintainers expect kdm to be set up to wait longer, while kdm expect
8427 the nvidia driver maintainers to fix the driver to start faster, and
8428 while they wait for each other I guess the users end up switching to a
8429 distribution that work for them. I have no idea what the solution is,
8430 but I am pretty sure that waiting for each other is not it.
</p
>
8432 <p
>I wonder why we end up handling bugs this way.
</p
>
8437 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
8438 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
8439 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
8440 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
8441 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
8442 The feature seem to hold up pretty well, but three fairly serious
8443 issues are known and should be solved:
8447 <li
>The wicd package seen to
8448 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
8449 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
8450 parallel booting is enabled. No idea why, but the wicd maintainer
8451 seem to be on the case.
</li
>
8453 <li
>The nvidia X driver seem to
8454 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
8455 triggered more easily when parallel booting is in effect. The
8456 maintainer is on the case.
</li
>
8458 <li
>The sysv-rc package fail to properly enable dependency based boot
8459 sequencing (the shutdown is broken) when old file-rc users
8460 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
8461 sysv-rc. One way to solve it would be for file-rc to create
8462 /etc/init.d/.legacy-bootordering, and another is to try to make
8463 sysv-rc more robust. Will investigate some more and probably upload a
8464 workaround in sysv-rc to help those trying to move from file-rc to
8465 sysv-rc get a working shutdown.
</li
>
8467 </ul
></p
>
8469 <p
>All in all not many surprising issues, and all of them seem
8470 solvable before Squeeze is released. In addition to these there are
8471 some packages with bugs in their dependencies and run level settings,
8472 which I expect will be fixed in a reasonable time span.
</p
>
8474 <p
>If you report any problems with dependencies in init.d scripts to
8475 the BTS, please usertag the report to get it to show up at
8476 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8477 list of usertagged bugs related to this
</a
>.
</p
>
8479 <p
>Update: Correct bug number to file-rc issue.
</p
>
8484 <title>More flexible firmware handling in debian-installer
</title>
8485 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
8486 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
8487 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
8488 <description><p
>After a long break from debian-installer development, I finally
8489 found time today to return to the project. Having to spend less time
8490 working dependency based boot in debian, as it is almost complete now,
8491 definitely helped freeing some time.
</p
>
8493 <p
>A while back, I ran into a problem while working on Debian Edu. We
8494 include some firmware packages on the Debian Edu CDs, those needed to
8495 get disk and network controllers working. Without having these
8496 firmware packages available during installation, it is impossible to
8497 install Debian Edu on the given machine, and because our target group
8498 are non-technical people, asking them to provide firmware packages on
8499 an external medium is a support pain. Initially, I expected it to be
8500 enough to include the firmware packages on the CD to get
8501 debian-installer to find and use them. This proved to be wrong.
8502 Next, I hoped it was enough to symlink the relevant firmware packages
8503 to some useful location on the CD (tried /cdrom/ and
8504 /cdrom/firmware/). This also proved to not work, and at this point I
8505 found time to look at the debian-installer code to figure out what was
8506 going to work.
</p
>
8508 <p
>The firmware loading code is in the hw-detect package, and a closer
8509 look revealed that it would only look for firmware packages outside
8510 the installation media, so the CD was never checked for firmware
8511 packages. It would only check USB sticks, floppies and other
8512 "external
" media devices. Today I changed it to also look in the
8513 /cdrom/firmware/ directory on the mounted CD or DVD, which should
8514 solve the problem I ran into with Debian edu. I also changed it to
8515 look in /firmware/, to make sure the installer also find firmware
8516 provided in the initrd when booting the installer via PXE, to allow us
8517 to provide the same feature in the PXE setup included in Debian
8520 <p
>To make sure firmware deb packages with a license questions are not
8521 activated without asking if the license is accepted, I extended
8522 hw-detect to look for preinst scripts in the firmware packages, and
8523 run these before activating the firmware during installation. The
8524 license question is asked using debconf in the preinst, so this should
8525 solve the issue for the firmware packages I have looked at so far.
</p
>
8527 <p
>If you want to discuss the details of these features, please
8528 contact us on debian-boot@lists.debian.org.
</p
>
8533 <title>Parallellized boot is now the default in Debian/unstable
</title>
8534 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
8535 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
8536 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
8537 <description><p
>Since this evening, parallel booting is the default in
8538 Debian/unstable for machines using dependency based boot sequencing.
8539 Apparently the testing of concurrent booting has been wider than
8540 expected, if I am to believe the
8541 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
8542 on debian-devel@
</a
>, and I concluded a few days ago to move forward
8543 with the feature this weekend, to give us some time to detect any
8544 remaining problems before Squeeze is frozen. If serious problems are
8545 detected, it is simple to change the default back to sequential boot.
8546 The upload of the new sysvinit package also activate a new upstream
8549 More information about
8550 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8551 based boot sequencing
</a
> is available from the Debian wiki. It is
8552 currently possible to disable parallel booting when one run into
8553 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
8555 <blockquote
><pre
>
8557 </pre
></blockquote
>
8559 <p
>If you report any problems with dependencies in init.d scripts to
8560 the BTS, please usertag the report to get it to show up at
8561 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8562 list of usertagged bugs related to this
</a
>.
</p
>
8567 <title>Sitesummary tip: Listing MAC address of all clients
</title>
8568 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
8569 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
8570 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
8571 <description><p
>In the recent Debian Edu versions, the
8572 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
8573 system
</a
> is used to keep track of the machines in the school
8574 network. Each machine will automatically report its status to the
8575 central server after boot and once per night. The network setup is
8576 also reported, and using this information it is possible to get the
8577 MAC address of all network interfaces in the machines. This is useful
8578 to update the DHCP configuration.
</p
>
8580 <p
>To give some idea how to use sitesummary, here is a one-liner to
8581 ist all MAC addresses of all machines reporting to sitesummary. Run
8582 this on the collector host:
</p
>
8584 <blockquote
><pre
>
8585 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
8586 </pre
></blockquote
>
8588 <p
>This will list all MAC addresses assosiated with all machine, one
8589 line per machine and with space between the MAC addresses.
</p
>
8591 <p
>To allow system administrators easier job at adding static DHCP
8592 addresses for hosts, it would be possible to extend this to fetch
8593 machine information from sitesummary and update the DHCP and DNS
8594 tables in LDAP using this information. Such tool is unfortunately not
8595 written yet.
</p
>
8600 <title>systemd, an interesting alternative to upstart
</title>
8601 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
8602 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
8603 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
8604 <description><p
>The last few days a new boot system called
8605 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
8607 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
8609 to the free software world. I have not yet had time to play around
8610 with it, but it seem to be a very interesting alternative to
8611 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
8612 a good alternative for Debian when we are able to switch to an event
8613 based boot system. Tollef is
8614 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
8615 systemd into Debian, and I look forward to seeing how well it work. I
8616 like the fact that systemd handles init.d scripts with dependency
8617 information natively, allowing them to run in parallel where upstart
8618 at the moment do not.
</p
>
8620 <p
>Unfortunately do systemd have the same problem as upstart regarding
8621 platform support. It only work on recent Linux kernels, and also need
8622 some new kernel features enabled to function properly. This means
8623 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8624 system. Not sure how that will be handled if systemd proves to be the
8625 way forward.
</p
>
8627 <p
>In the mean time, based on the
8628 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
8629 on debian-devel@
</a
> regarding parallel booting in Debian, I have
8630 decided to enable full parallel booting as the default in Debian as
8631 soon as possible (probably this weekend or early next week), to see if
8632 there are any remaining serious bugs in the init.d dependencies. A
8633 new version of the sysvinit package implementing this change is
8634 already in experimental. If all go well, Squeeze will be released
8635 with parallel booting enabled by default.
</p
>
8640 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
8641 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
8642 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
8643 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
8644 <description><p
>These days, the init.d script dependencies in Squeeze are quite
8645 complete, so complete that it is actually possible to run all the
8646 init.d scripts in parallell based on these dependencies. If you want
8647 to test your Squeeze system, make sure
8648 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8649 based boot sequencing
</a
> is enabled, and add this line to
8650 /etc/default/rcS:
</p
>
8652 <blockquote
><pre
>
8653 CONCURRENCY=makefile
8654 </pre
></blockquote
>
8656 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
8657 scripts in parallel using the dependency information stored in
8658 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8659 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8660 to try to start the kdm and gdm scripts as early as possible, and will
8661 start the facilities required by kdm or gdm as early as possible to
8662 make this happen.
</p
>
8664 <p
>Give it a try, and see if you like the result. If some services
8665 fail to start properly, it is most likely because they have incomplete
8666 init.d script dependencies in their startup script (or some of their
8667 dependent scripts have incomplete dependencies). Report bugs and get
8668 the package maintainers to fix it. :)
</p
>
8670 <p
>Running scripts in parallel could be the default in Debian when we
8671 manage to get the init.d script dependencies complete and correct. I
8672 expect we will get there in Squeeze+
1, if we get manage to test and
8673 fix the remaining issues.
</p
>
8675 <p
>If you report any problems with dependencies in init.d scripts to
8676 the BTS, please usertag the report to get it to show up at
8677 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8678 list of usertagged bugs related to this
</a
>.
</p
>
8683 <title>Debian has switched to dependency based boot sequencing
</title>
8684 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
8685 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
8686 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
8687 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
8688 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
8689 have been migrated to using dependency based boot sequencing. This
8690 conclude work me and others have been doing for the last three days.
8691 It feels great to see this finally part of the default Debian
8692 installation. Now we just need to weed out the last few problems that
8693 are bound to show up, to get everything ready for Squeeze.
</p
>
8695 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
8696 fixing the more fundamental problem of handing the event based
8697 non-predictable kernel in the early boot.
</p
>
8702 <title>Taking over sysvinit development
</title>
8703 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
8704 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
8705 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
8706 <description><p
>After several years of frustration with the lack of activity from
8707 the existing sysvinit upstream developer, I decided a few weeks ago to
8708 take over the package and become the new upstream. The number of
8709 patches to track for the Debian package was becoming a burden, and the
8710 lack of synchronization between the distribution made it hard to keep
8711 the package up to date.
</p
>
8713 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8714 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
8715 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
8716 and Fedora), based on the patches currently in use in these
8717 distributions. We Debian maintainers plan to move to this tarball as
8718 the new upstream as soon as we find time to do the merge. Since the
8719 new tarball was created, we agreed with Werner at SuSe to make a new
8720 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
8721 development there. The project is registered and currently waiting
8722 for approval by the Savannah administrators, and as soon as it is
8723 approved, we will import the old versions from svn and continue
8724 working on the future release.
</p
>
8726 <p
>It is a bit ironic that this is done now, when some of the involved
8727 distributions are moving to upstart as a syvinit replacement.
</p
>
8732 <title>Debian boots quicker and quicker
</title>
8733 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
8734 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
8735 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
8736 <description><p
>I spent Monday and tuesday this week in London with a lot of the
8737 people involved in the boot system on Debian and Ubuntu, to see if we
8738 could find more ways to speed up the boot system. This was an Ubuntu
8740 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
8741 gathering
</a
>. It was quite productive. We also discussed the future
8742 of boot systems, and ways to handle the increasing number of boot
8743 issues introduced by the Linux kernel becoming more and more
8744 asynchronous and event base. The Ubuntu approach using udev and
8745 upstart might be a good way forward. Time will show.
</p
>
8747 <p
>Anyway, there are a few ways at the moment to speed up the boot
8748 process in Debian. All of these should be applied to get a quick
8753 <li
>Use dash as /bin/sh.
</li
>
8755 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
8756 clock is in UTC.
</li
>
8758 <li
>Install and activate the insserv package to enable
8759 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8760 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
8764 These points are based on the Google summer of code work done by
8765 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
8768 <p
>Support for makefile-style concurrency during boot was uploaded to
8769 unstable yesterday. When we tested it, we were able to cut
6 seconds
8770 from the boot sequence. It depend on very correct dependency
8771 declaration in all init.d scripts, so I expect us to find edge cases
8772 where the dependences in some scripts are slightly wrong when we start
8773 using this.
</p
>
8775 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8776 introduced by Raphael Geissert today, one that could affect the
8777 startup speed as well. Instead of starting some scripts concurrently
8778 from rcS.d/ and another set of scripts from rc2.d/, it would be
8779 possible to run a of them in the same process. A quick way to test
8780 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
8781 insserv
'. Will need to test if that work. :)
</p
>
8786 <title>BSAs påstander om piratkopiering møter motstand
</title>
8787 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
8788 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
8789 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
8790 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
8791 programvareselskapene som Microsoft og Apple, publisert en rapport der
8792 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8793 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8795 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
8796 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
8797 dagene. Et spesielt interessant kommentar fra Sverige,
8798 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
8799 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
8802 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
8803 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8804 företag.
"Man bör nog kanske inte se de här siffrorna som helt
8805 exakta
", säger BSAs Sverigechef John Hugosson.
8808 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
8809 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
8810 piracy figures need a shot of reality
</a
> og
<a
8811 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
8812 Copyright Treaty Work?
</a
></p
>
8814 <p
>Fant lenkene via
<a
8815 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
8816 på Slashdot
</a
>.
</p
>
8821 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
8822 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
8823 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
8824 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
8825 <description><p
>Kom over
8826 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
8827 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8828 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8829 jobber til daglig. En rask opptelling forteller meg at vi har
490
8830 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
8831 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
8832 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
8837 <title>Kryptert harddisk - naturligvis
</title>
8838 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
8839 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
8840 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
8841 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
8842 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
8843 når en tar tap av arbeidstid, fortrolige dokumenter,
8844 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8845 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8846 til at jeg har kryptert harddisken på både kontormaskinen og min
8847 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8848 komme på avveie, den første informasjon relatert til jobben min ved
8849 Universitetet i Oslo, og den andre relatert til blant annet
8850 foreningsarbeide. Kryptering av diskene gjør at det er lite
8851 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8852 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8853 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8854 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8855 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8856 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8857 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8858 det er gjort slik jeg gjør det er minimale, og gevinstene er
8859 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8860 maskinen reinstalleres og alt er tapt.
</p
>
8862 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8863 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8864 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8865 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8866 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8867 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8868 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8869 betydelige.
</p
>
8874 <title>Two projects that have improved the quality of free software a lot
</title>
8875 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
8876 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
8877 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
8878 <description><p
>There are two software projects that have had huge influence on the
8879 quality of free software, and I wanted to mention both in case someone
8880 do not yet know them.
</p
>
8882 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
8883 tool to detect and expose errors in the memory handling of programs.
8884 It is easy to use, all one need to do is to run
'valgrind program
',
8885 and it will report any problems on stdout. It is even better if the
8886 program include debug information. With debug information, it is able
8887 to report the source file name and line number where the problem
8888 occurs. It can report things like
'reading past memory block in file
8889 X line N, the memory block was allocated in file Y, line M
', and
8890 'using uninitialised value in control logic
'. This tool has made it
8891 trivial to investigate reproducible crash bugs in programs, and have
8892 reduced the number of this kind of bugs in free software a lot.
8894 <p
>The second one is
8895 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
8896 a source code checker. It is able to process the source of a program
8897 and find problems in the logic without running the program. It
8898 started out as the Stanford Checker and became well known when it was
8899 used to find bugs in the Linux kernel. It is now a commercial tool
8900 and the company behind it is running
8901 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
8902 free software community, where a lot of free software projects get
8903 their source checked for free. Several thousand defects have been
8904 found and fixed so far. It can find errors like
'lock L taken in file
8905 X line N is never released if exiting in line M
', or
'the code in file
8906 Y lines O to P can never be executed
'. The projects included in the
8907 community service project have managed to get rid of a lot of
8908 reliability problems thanks to Coverity.
</p
>
8910 <p
>I believe tools like this, that are able to automatically find
8911 errors in the source, are vital to improve the quality of software and
8912 make sure we can get rid of the crashing and failing software we are
8913 surrounded by today.
</p
>
8918 <title>No patch is not better than a useless patch
</title>
8919 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
8920 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
8921 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
8922 <description><p
>Julien Blache
8923 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
8924 patch is better than a useless patch
</a
>. I completely disagree, as a
8925 patch allow one to discuss a concrete and proposed solution, and also
8926 prove that the issue at hand is important enough for someone to spent
8927 time on fixing it. No patch do not provide any of these positive
8928 properties.
</p
>
8933 <title>Standardize on protocols and formats, not vendors and applications
</title>
8934 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
8935 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
8936 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
8937 <description><p
>Where I work at the University of Oslo, one decision stand out as a
8938 very good one to form a long lived computer infrastructure. It is the
8939 simple one, lost by many in todays computer industry: Standardize on
8940 open network protocols and open exchange/storage formats, not applications.
8941 Applications come and go, while protocols and files tend to stay, and
8942 thus one want to make it easy to change application and vendor, while
8943 avoiding conversion costs and locking users to a specific platform or
8944 application.
</p
>
8946 <p
>This approach make it possible to replace the client applications
8947 independently of the server applications. One can even allow users to
8948 use several different applications as long as they handle the selected
8949 protocol and format. In the normal case, only one client application
8950 is recommended and users only get help if they choose to use this
8951 application, but those that want to deviate from the easy path are not
8952 blocked from doing so.
</p
>
8954 <p
>It also allow us to replace the server side without forcing the
8955 users to replace their applications, and thus allow us to select the
8956 best server implementation at any moment, when scale and resouce
8957 requirements change.
</p
>
8959 <p
>I strongly recommend standardizing - on open network protocols and
8960 open formats, but I would never recommend standardizing on a single
8961 application that do not use open network protocol or open formats.
</p
>
8966 <title>Returning from Skolelinux developer gathering
</title>
8967 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
8968 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
8969 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
8970 <description><p
>I
'm sitting on the train going home from this weekends Debian
8971 Edu/Skolelinux development gathering. I got a bit done tuning the
8972 desktop, and looked into the dynamic service location protocol
8973 implementation avahi. It look like it could be useful for us. Almost
8974 30 people participated, and I believe it was a great environment to
8975 get to know the Skolelinux system. Walter Bender, involved in the
8976 development of the Sugar educational platform, presented his stuff and
8977 also helped me improve my OLPC installation. He also showed me that
8978 his Turtle Art application can be used in standalone mode, and we
8979 agreed that I would help getting it packaged for Debian. As a
8980 standalone application it would be great for Debian Edu. We also
8981 tried to get the video conferencing working with two OLPCs, but that
8982 proved to be too hard for us. The application seem to need more work
8983 before it is ready for me. I look forward to getting home and relax
8989 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
8990 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
8991 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
8992 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
8993 <description><p
>The state of standardized LDAP schemas on Linux is far from
8994 optimal. There is RFC
2307 documenting one way to store NIS maps in
8995 LDAP, and a modified version of this normally called RFC
2307bis, with
8996 some modifications to be compatible with Active Directory. The RFC
8997 specification handle the content of a lot of system databases, but do
8998 not handle DNS zones and DHCP configuration.
</p
>
9000 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
9001 we would like to store information about users, SMB clients/hosts,
9002 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
9003 and LTSP configuration in LDAP. These objects have a lot in common,
9004 but with the current LDAP schemas it is not possible to have one
9005 object per entity. For example, one need to have at least three LDAP
9006 objects for a given computer, one with the SMB related stuff, one with
9007 DNS information and another with DHCP information. The schemas
9008 provided for DNS and DHCP are impossible to combine into one LDAP
9009 object. In addition, it is impossible to implement quick queries for
9010 netgroup membership, because of the way NIS triples are implemented.
9011 It just do not scale. I believe it is time for a few RFC
9012 specifications to cleam up this mess.
</p
>
9014 <p
>I would like to have one LDAP object representing each computer in
9015 the network, and this object can then keep the SMB (ie host key), DHCP
9016 (mac address/name) and DNS (name/IP address) settings in one place.
9017 It need to be efficently stored to make sure it scale well.
</p
>
9019 <p
>I would also like to have a quick way to map from a user or
9020 computer and to the net group this user or computer is a member.
</p
>
9022 <p
>Active Directory have done a better job than unix heads like myself
9023 in this regard, and the unix side need to catch up. Time to start a
9024 new IETF work group?
</p
>
9029 <title>Endelig er Debian Lenny gitt ut
</title>
9030 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
9031 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
9032 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
9033 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
9034 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
9035 Et langt steg videre for Debian-prosjektet, og en rekke nye
9036 programpakker blir nå tilgjengelig for de av oss som bruker den
9037 stabile utgaven av Debian. Neste steg er nå å få
9038 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
9039 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
9040 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
9041 slippes løs på skolene. Takk til alle debian-utviklerne som har
9042 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
9043 bootsekvens tilgjengelig i stabil utgave, vha pakken
9044 <tt
>insserv
</tt
>.
</p
>
9049 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
9050 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
9051 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
9052 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
9053 <description><p
>This weekend we had a small developer gathering for Debian Edu in
9054 Oslo. Most of Saturday was used for the general assemly for the
9055 member organization, but the rest of the weekend I used to tune the
9056 LTSP installation. LTSP now work out of the box on the
10-network.
9057 Acer Aspire One proved to be a very nice thin client, with both
9058 screen, mouse and keybard in a small box. Was working on getting the
9059 diskless workstation setup configured out of the box, but did not
9060 finish it before the weekend was up.
</p
>
9062 <p
>Did not find time to look at the
4 VGA cards in one box we got from
9063 the Brazilian group, so that will have to wait for the next
9064 development gathering. Would love to have the Debian Edu installer
9065 automatically detect and configure a multiseat setup when it find one
9066 of these cards.
</p
>
9071 <title>The sorry state of multimedia browser plugins in Debian
</title>
9072 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
9073 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
9074 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
9075 <description><p
>Recently I have spent some time evaluating the multimedia browser
9076 plugins available in Debian Lenny, to see which one we should use by
9077 default in Debian Edu. We need an embedded video playing plugin with
9078 control buttons to pause or stop the video, and capable of streaming
9079 all the multimedia content available on the web. The test results and
9080 notes are available on
9081 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
9082 Debian wiki
</a
>. I was surprised how few of the plugins are able to
9083 fill this need. My personal video player favorite, VLC, has a really
9084 bad plugin which fail on a lot of the test pages. A lot of the MIME
9085 types I would expect to work with any free software player (like
9086 video/ogg), just do not work. And simple formats like the
9087 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
9088 totem and vlc plugins. I hope the situation will improve soon. No
9089 wonder sites use the proprietary Adobe flash to play video.
</p
>
9091 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
9092 be the only one fitting our needs. :/
</p
>