1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries tagged debian
</title>
5 <description>Entries tagged debian
</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
11 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
13 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
14 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
15 system
</a
> is a user-focused solution in Debian for handling hardware
16 related packages. The idea is to have a database of mappings between
17 hardware and packages, and pop up a dialog suggesting for the user to
18 install the packages to use a given hardware dongle. Some use cases
19 are when you insert a Yubikey, it proposes to install the software
20 needed to control it; when you insert a braille reader list it
21 proposes to install the packages needed to send text to the reader;
22 and when you insert a ColorHug screen calibrator it suggests to
23 install the driver for it. The system work well, and even have a few
24 command line tools to install firmware packages and packages for the
25 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
27 <p
>The system was initially written using aptdaemon, because I found
28 good documentation and example code on how to use it. But aptdaemon
29 is going away and is generally being replaced by
30 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
31 so Isenkram needed a rewrite. And today, thanks to the great patch
32 from my college Sunil Mohan Adapa in the FreedomBox project, the
33 rewrite finally took place. I
've just uploaded a new version of
34 Isenkram into Debian Unstable with the patch included, and the default
35 for the background daemon is now to use PackageKit. To check it out,
36 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
37 and see if it is recognised.
</p
>
39 <p
>If you want to know what kind of packages isenkram would propose for
40 the machine it is running on, you can check out the isenkram-lookup
41 program. This is what it look like on a Thinkpad X230:
</p
>
43 <p
><blockquote
><pre
>
59 </pre
></blockquote
></p
>
61 <p
>The hardware mappings come from several places. The preferred way
62 is for packages to announce their hardware support using
63 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
64 cross distribution appstream system
</a
>.
66 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
67 blog posts about isenkram
</a
> to learn how to do that.
</p
>
72 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
73 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
74 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
75 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
76 <description><p
>Yesterday I updated the
77 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
78 package in Debian
</a
> with a few patches sent to me by skilled and
79 enterprising users. There were some nice user and visible changes.
80 First of all, both desktop menu entries now work. A design flaw in
81 one of the script made the history graph fail to show up (its PNG was
82 dumped in ~/.xsession-errors) if no controlling TTY was available.
83 The script worked when called from the command line, but not when
84 called from the desktop menu. I changed this to look for a DISPLAY
85 variable or a TTY before deciding where to draw the graph, and now the
86 graph window pop up as expected.
</p
>
88 <p
>The next new feature is a discharge rate estimator in one of the
89 graphs (the one showing the last few hours). New is also the user of
90 colours showing charging in blue and discharge in red. The percentages
91 of this graph is relative to last full charge, not battery design
94 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
96 <p
>The other graph show the entire history of the collected battery
97 statistics, comparing it to the design capacity of the battery to
98 visualise how the battery life time get shorter over time. The red
99 line in this graph is what the previous graph considers
100 percent:
101 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
103 <p
>In this graph you can see that I only charge the battery to
80
104 percent of last full capacity, and how the capacity of the battery is
105 shrinking. :(
</p
>
107 <p
>The last new feature is in the collector, which now will handle
108 more hardware models. On some hardware, Linux power supply
109 information is stored in /sys/class/power_supply/ACAD/, while the
110 collector previously only looked in /sys/class/power_supply/AC/. Now
111 both are checked to figure if there is power connected to the
114 <p
>If you are interested in how your laptop battery is doing, please
116 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
117 in Debian unstable, or rebuild it on Jessie to get it working on
118 Debian stable. :) The upstream source is available from
<a
119 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
120 Patches are very welcome.
</p
>
122 <p
>As usual, if you use Bitcoin and want to show your support of my
123 activities, please send Bitcoin donations to my address
124 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
129 <title>Debian now with ZFS on Linux included
</title>
130 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
131 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
132 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
133 <description><p
>Today, after many years of hard work from many people,
134 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
135 Debian. The package status can be seen on
136 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
137 for zfs-linux
</a
>. and
138 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
139 team status page
</a
>. If you want to help out, please join us.
140 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
141 source code
</a
> is available via git on Alioth. It would also be
142 great if you could help out with
143 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
144 it is an important piece of the puzzle to get ZFS working.
</p
>
149 <title>What is the best multimedia player in Debian?
</title>
150 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
151 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
152 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
153 <description><p
><strong
>Where I set out to figure out which multimedia player in
154 Debian claim support for most file formats.
</strong
></p
>
156 <p
>A few years ago, I had a look at the media support for Browser
157 plugins in Debian, to get an idea which plugins to include in Debian
158 Edu. I created a script to extract the set of supported MIME types
159 for each plugin, and used this to find out which multimedia browser
160 plugin supported most file formats / media types.
161 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
162 result
</a
> can still be seen on the Debian wiki, even though it have
163 not been updated for a while. But browser plugins are less relevant
164 these days, so I thought it was time to look at standalone
167 <p
>A few days ago I was tired of VLC not being listed as a viable
168 player when I wanted to play videos from the Norwegian National
169 Broadcasting Company, and decided to investigate why. The cause is a
170 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
171 desktop file
</a
>. In the process I wrote a script to compare the set
172 of MIME types announced in the desktop file and the browser plugin,
173 only to discover that there is quite a large difference between the
174 two for VLC. This discovery made me dig up the script I used to
175 compare browser plugins, and adjust it to compare desktop files
176 instead, to try to figure out which multimedia player in Debian
177 support most file formats.
</p
>
179 <p
>The result can be seen on the Debian Wiki, as
180 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
181 table listing all MIME types supported by one of the packages included
182 in the table
</a
>, with the package supporting most MIME types being
183 listed first in the table.
</p
>
185 </p
>The best multimedia player in Debian? It is totem, followed by
186 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
187 kmplayer. Time for the other players to update their announced MIME
193 <title>The Pyra - handheld computer with Debian preinstalled
</title>
194 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
195 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
196 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
197 <description>A friend of mine made me aware of
198 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
199 handheld computer which will be delivered with Debian preinstalled. I
200 would love to get one of those for my birthday. :)
</p
>
202 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
203 plugs and many others connectors, and include a full keyboard and a
5"
204 LCD touch screen. The
6000mAh battery is claimed to provide a whole
205 day of battery life time, but I have not seen any independent tests
206 confirming this. The vendor is still collecting preorders, and the
207 last I heard last night was that
22 more orders were needed before
208 production started.
</p
>
210 <p
>As far as I know, this is the first handheld preinstalled with
211 Debian. Please let me know if you know of any others. Is it the
212 first computer being sold with Debian preinstalled?
</p
>
217 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
218 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
219 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
220 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
221 <description><p
>During this weekends
222 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
223 squashing party and developer gathering
</a
>, we decided to do our part
224 to make sure there are good books about Debian available in Norwegian
225 Bokmål, and got in touch with the people behind the
226 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
227 project
</a
> to get started. If you want to help out, please start
229 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
230 hosted weblate project page
</a
>, and get in touch using
231 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
232 translators mailing list
</a
>. Please also check out
233 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
234 contributors
</a
>.
</p
>
236 <p
>The book is already available on paper in English, French and
237 Japanese, and our goal is to get it available on paper in Norwegian
238 Bokmål too. In addition to the paper edition, there are also EPUB and
239 Mobi versions available. And there are incomplete translations
240 available for many more languages.
</p
>
245 <title>One in two hundred Debian users using ZFS on Linux?
</title>
246 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
247 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
248 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
249 <description><p
>Just for fun I had a look at the popcon number of ZFS related
250 packages in Debian, and was quite surprised with what I found. I use
251 ZFS myself at home, but did not really expect many others to do so.
252 But I might be wrong.
</p
>
254 <p
>According to
255 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
256 results for spl-linux
</a
>, there are
1019 Debian installations, or
257 0.53% of the population, with the package installed. As far as I know
258 the only use of the spl-linux package is as a support library for ZFS
259 on Linux, so I use it here as proxy for measuring the number of ZFS
260 installation on Linux in Debian. In the kFreeBSD variant of Debian
261 the ZFS feature is already available, and there
262 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
263 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
264 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
266 <p
>But even though the Debian project leader Lucas Nussbaum
267 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
268 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
269 cleared, the package is still not in Debian. The package is again in
270 the NEW queue. Several uploads have been rejected so far because the
271 debian/copyright file was incomplete or wrong, but there is no reason
272 to give up. The current status can be seen on
273 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
274 team status page
</a
>, and
275 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
276 source code
</a
> is available on Alioth.
</p
>
278 <p
>As I want ZFS to be included in next version of Debian to make sure
279 my home server can function in the future using only official Debian
280 packages, and the current blocker is to get the debian/copyright file
281 accepted by the FTP masters in Debian, I decided a while back to try
282 to help out the team. This was the background for my blog post about
283 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
284 updating and checking debian/copyright semi-automatically
</a
>, and I
285 used the techniques I explored there to try to find any errors in the
286 copyright file. It is not very easy to check every one of the around
287 2000 files in the source package, but I hope we this time got it
288 right. If you want to help out, check out the git source and try to
289 find missing entries in the debian/copyright file.
</p
>
294 <title>Full battery stats collector is now available in Debian
</title>
295 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
296 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
297 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
298 <description><p
>Since this morning, the battery-stats package in Debian include an
299 extended collector that will collect the complete battery history for
300 later processing and graphing. The original collector store the
301 battery level as percentage of last full level, while the new
302 collector also record battery vendor, model, serial number, design
303 full level, last full level and current battery level. This make it
304 possible to predict the lifetime of the battery as well as visualise
305 the energy flow when the battery is charging or discharging.
</p
>
307 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
308 in the version
0.5.1 package in unstable. Get the new battery level graph
309 and lifetime prediction by running:
312 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
313 </pre
></p
>
315 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
317 <p
>The flow in/out of the battery can be seen by running (no menu
318 entry yet):
</p
>
321 /usr/share/battery-stats/battery-stats-graph-flow
322 </pre
></p
>
324 <p
>I
'm not quite happy with the way the data is visualised, at least
325 when there are few data points. The graphs look a bit better with a
326 few years of data.
</p
>
328 <p
>A while back one important feature I use in the battery stats
329 collector broke in Debian. The scripts in
330 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
331 suspect it happened when Jessie started using systemd, but I do not
332 know. The issue is reported as
333 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
334 pm-utils. I managed to work around it by adding an udev rule to call
335 the collector script every time the power connector is connected and
336 disconnected. With this fix in place it was finally time to make a
337 new release of the package, and get it into Debian.
</p
>
339 <p
>If you are interested in how your laptop battery is doing, please
341 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
342 in Debian unstable, or rebuild it on Jessie to get it working on
343 Debian stable. :) The upstream source is available from
344 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
345 As always, patches are very welcome.
</p
>
350 <title>Making battery measurements a little easier in Debian
</title>
351 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
352 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
353 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
354 <description><p
>Back in September, I blogged about
355 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
356 system I wrote to collect statistics about my laptop battery
</a
>, and
357 how it showed the decay and death of this battery (now replaced). I
358 created a simple deb package to handle the collection and graphing,
359 but did not want to upload it to Debian as there were already
360 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
361 package in Debian
</a
> that should do the same thing, and I did not see
362 a point of uploading a competing package when battery-stats could be
363 fixed instead. I reported a few bugs about its non-function, and
364 hoped someone would step in and fix it. But no-one did.
</p
>
366 <p
>I got tired of waiting a few days ago, and took matters in my own
367 hands. The end result is that I am now the new upstream developer of
368 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
369 battery-stats in Debian, and the package in Debian unstable is finally
370 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
371 information provided by the Linux kernel. If you install the
372 battery-stats package from unstable now, you will be able to get a
373 graph of the current battery fill level, to get some idea about the
374 status of the battery. The source package build and work just fine in
375 Debian testing and stable (and probably oldstable too, but I have not
376 tested). The default graph you get for that system look like this:
</p
>
378 <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
>
380 <p
>My plans for the future is to merge my old scripts into the
381 battery-stats package, as my old scripts collected a lot more details
382 about the battery. The scripts are merged into the upstream
383 battery-stats git repository already, but I am not convinced they work
384 yet, as I changed a lot of paths along the way. Will have to test a
385 bit more before I make a new release.
</p
>
387 <p
>I will also consider changing the file format slightly, as I
388 suspect the way I combine several values into one field might make it
389 impossible to know the type of the value when using it for processing
390 and graphing.
</p
>
392 <p
>If you would like I would like to keep an close eye on your laptop
393 battery, check out the battery-stats package in
394 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
396 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
397 I would love some help to improve the system further.
</p
>
402 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
403 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
404 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
405 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
406 <description><p
>Making packages for Debian requires quite a lot of attention to
407 details. And one of the details is the content of the
408 debian/copyright file, which should list all relevant licenses used by
409 the code in the package in question, preferably in
410 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
411 readable DEP5 format
</a
>.
</p
>
413 <p
>For large packages with lots of contributors it is hard to write
414 and update this file manually, and if you get some detail wrong, the
415 package is normally rejected by the ftpmasters. So getting it right
416 the first time around get the package into Debian faster, and save
417 both you and the ftpmasters some work.. Today, while trying to figure
418 out what was wrong with
419 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
420 zfsonlinux copyright file
</a
>, I decided to spend some time on
421 figuring out the options for doing this job automatically, or at least
422 semi-automatically.
</p
>
424 <p
>Lucikly, there are at least two tools available for generating the
425 file based on the code in the source package,
426 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
427 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
428 not sure which one of them came first, but both seem to be able to
429 create a sensible draft file. As far as I can tell, none of them can
430 be trusted to get the result just right, so the content need to be
431 polished a bit before the file is OK to upload. I found the debmake
433 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
434 blog posts from
2014</a
>.
436 <p
>To generate using debmake, use the -cc option:
439 debmake -cc
> debian/copyright
440 </pre
></p
>
442 <p
>Note there are some problems with python and non-ASCII names, so
443 this might not be the best option.
</p
>
445 <p
>The cme option is based on a config parsing library, and I found
447 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
448 blog post from
2015</a
>. To generate using cme, use the
'update
449 dpkg-copyright
' option:
452 cme update dpkg-copyright
453 </pre
></p
>
455 <p
>This will create or update debian/copyright. The cme tool seem to
456 handle UTF-
8 names better than debmake.
</p
>
458 <p
>When the copyright file is created, I would also like some help to
459 check if the file is correct. For this I found two good options,
460 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
461 to focus on license types and file matching, and is able to detect
462 ineffective blocks in the copyright file. The latter reports missing
463 copyright holders and years, but was confused by inconsistent license
464 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
465 fix all issues reported by them before uploading. But I do not know
466 if the tools and the ftpmasters agree on what is important to fix in a
467 copyright file, so the package might still be rejected.
</p
>
469 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
470 will read through the source and try to find all copyright statements.
471 It is not comparing the result to the content of debian/copyright, but
472 can be useful when verifying the content of the copyright file.
</p
>
474 <p
>Are you aware of better tools in Debian to create and update
475 debian/copyright file. Please let me know, or blog about it on
476 planet.debian.org.
</p
>
478 <p
>As usual, if you use Bitcoin and want to show your support of my
479 activities, please send Bitcoin donations to my address
480 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
482 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
483 on how to use licensecheck and cdbs to create a draft copyright file
486 licensecheck --copyright -r `find * -type f` | \
487 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
488 </pre
></p
>
490 <p
>He mentioned that he normally check the generated file into the
491 version control system to make it easier to discover license and
492 copyright changes in the upstream source. I will try to do the same
493 with my packages in the future.
</p
>
495 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
496 against using -quiet for new users, so I removed it from the proposed
497 command line.
</p
>
502 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
503 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
504 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
505 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
506 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
507 is taking shape in Debian, and one provided feature is a very
508 convenient way to tell you which package to install to make a given
509 firmware file available when the kernel is looking for it. This can
510 be done using apt-file too, but that is for someone else to blog
513 <p
>Here is a small recipe to find the package with a given firmware
514 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
515 picked from the set of firmware announced using appstream in Debian
516 unstable. In general you would be looking for the firmware requested
517 by the kernel during kernel module loading. To find the package
518 providing the example file, do like this:
</p
>
520 <blockquote
><pre
>
521 % apt install appstream
525 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
526 awk
'/Package:/ {print $
2}
'
529 </pre
></blockquote
>
531 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
532 appstream wiki
</a
> page to learn how to embed the package metadata in
533 a way appstream can use.
</p
>
535 <p
>This same approach can be used to find any package supporting a
536 given MIME type. This is very useful when you get a file you do not
537 know how to handle. First find the mime type using
<tt
>file
538 --mime-type
</tt
>, and next look up the package providing support for
539 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
540 and you can find all packages handling this type like this:
</p
>
542 <blockquote
><pre
>
543 % apt install appstream
547 % appstreamcli what-provides mimetype image/svg+xml | \
548 awk
'/Package:/ {print $
2}
'
570 </pre
></blockquote
>
572 <p
>I believe the MIME types are fetched from the desktop file for
573 packages providing appstream metadata.
</p
>
578 <title>Creepy, visualise geotagged social media information - nice free software
</title>
579 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
580 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
581 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
582 <description><p
>Most people seem not to realise that every time they walk around
583 with the computerised radio beacon known as a mobile phone their
584 position is tracked by the phone company and often stored for a long
585 time (like every time a SMS is received or sent). And if their
586 computerised radio beacon is capable of running programs (often called
587 mobile apps) downloaded from the Internet, these programs are often
588 also capable of tracking their location (if the app requested access
589 during installation). And when these programs send out information to
590 central collection points, the location is often included, unless
591 extra care is taken to not send the location. The provided
592 information is used by several entities, for good and bad (what is
593 good and bad, depend on your point of view). What is certain, is that
594 the private sphere and the right to free movement is challenged and
595 perhaps even eradicated for those announcing their location this way,
596 when they share their whereabouts with private and public
599 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
601 <p
>The phone company logs provide a register of locations to check out
602 when one want to figure out what the tracked person was doing. It is
603 unavailable for most of us, but provided to selected government
604 officials, company staff, those illegally buying information from
605 unfaithful servants and crackers stealing the information. But the
606 public information can be collected and analysed, and a free software
607 tool to do so is called
608 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
609 discovered it when I read
610 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
611 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
612 November
2014, and decided to check if it was available in Debian.
613 The python program was in Debian, but
614 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
615 Debian
</a
> was completely broken and practically unmaintained. I
616 uploaded a new version which did not work quite right, but did not
617 have time to fix it then. This Christmas I decided to finally try to
618 get Creepy operational in Debian. Now a fixed version is available in
619 Debian unstable and testing, and almost all Debian specific patches
621 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
623 <p
>The Creepy program visualises geolocation information fetched from
624 Twitter, Instagram, Flickr and Google+, and allow one to get a
625 complete picture of every social media message posted recently in a
626 given area, or track the movement of a given individual across all
627 these services. Earlier it was possible to use the search API of at
628 least some of these services without identifying oneself, but these
629 days it is impossible. This mean that to use Creepy, you need to
630 configure it to log in as yourself on these services, and provide
631 information to them about your search interests. This should be taken
632 into account when using Creepy, as it will also share information
633 about yourself with the services.
</p
>
635 <p
>The picture above show the twitter messages sent from (or at least
636 geotagged with a position from) the city centre of Oslo, the capital
637 of Norway. One useful way to use Creepy is to first look at
638 information tagged with an area of interest, and next look at all the
639 information provided by one or more individuals who was in the area.
640 I tested it by checking out which celebrity provide their location in
641 twitter messages by checkout out who sent twitter messages near a
642 Norwegian TV station, and next could track their position over time,
643 making it possible to locate their home and work place, among other
644 things. A similar technique have been
645 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
646 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
647 tool to discover lying governments, and a useful tool to help people
648 understand the value of the private information they provide to the
651 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
652 it depend on several python modules currently missing in Jessie (at
653 least python-instagram, python-flickrapi and
654 python-requests-toolbelt).
</p
>
656 <p
>(I have uploaded
657 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
658 screenshots.debian.net
</a
> and licensed it under the same terms as the
659 Creepy program in Debian.)
</p
>
664 <title>Always download Debian packages using Tor - the simple recipe
</title>
665 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
666 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
667 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
668 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
669 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
670 that those listening on the Internet lines would have good reason to
671 believe a computer have a given security hole
</a
> if it download a
672 security fix from a Debian mirror. This is a good reason to always
673 use encrypted connections to the Debian mirror, to make sure those
674 listening do not know which IP address to attack. In August, Richard
675 Hartmann observed that encryption was not enough, when it was possible
676 to interfere download size to security patches or the fact that
677 download took place shortly after a security fix was released, and
678 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
679 to always use Tor to download packages from the Debian mirror
</a
>. He
680 was not the first to propose this, as the
681 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
682 package by Tim Retout already existed to make it easy to convince apt
683 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
684 aware of that package when I read the blog post from Richard.
</p
>
686 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
687 sysadmins, and he set up a Tor hidden service on one of the central
688 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
689 it possible to download packages directly between two tor nodes,
690 making sure the network traffic always were encrypted.
</p
>
692 <p
>Here is a short recipe for enabling this on your machine, by
693 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
694 urls with tor+http and tor+https, and using the hidden service instead
695 of the official Debian mirror site. I recommend installing
696 <tt
>etckeeper
</tt
> before you start to have a history of the changes
697 done in /etc/.
</p
>
699 <blockquote
><pre
>
700 apt install apt-transport-tor
701 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
702 sed -i
's% http% tor+http%
' /etc/apt/sources.list
703 </pre
></blockquote
>
705 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
706 the sed commands for these too. The sed command is assuming your are
707 using the ftp.debian.org Debian mirror. Adjust the command (or just
708 edit the file manually) to match your mirror.
</p
>
710 <p
>This work in Debian Jessie and later. Note that tools like
711 <tt
>apt-file
</tt
> only recently started using the apt transport
712 system, and do not work with these tor+http URLs. For
713 <tt
>apt-file
</tt
> you need the version currently in experimental,
714 which need a recent apt version currently only in unstable. So if you
715 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
717 <p
>Another advantage from this change is that your machine will start
718 using Tor regularly and at fairly random intervals (every time you
719 update the package lists or upgrade or install a new package), thus
720 masking other Tor traffic done from the same machine. Using Tor will
721 become normal for the machine in question.
</p
>
723 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
724 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
725 enabled. It would be great if it was the default on any Debian
731 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
732 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
733 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
734 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
735 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
736 call the car license plate numbers in those days. I would write the
737 numbers down in my little book and compare notes with the other kids
738 to see how many region codes we had seen and if we had seen some
739 exotic or special region codes and numbers. It was a fun game to pass
740 time, as we kids have plenty of it.
</p
>
742 <p
>A few days I came across
743 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
744 project
</a
>, a free software project to automatically discover and
745 report license plates in images and video streams, and provide the
746 "car numbers
" in a machine readable format. I
've been looking for
747 such system for a while now, because I believe it is a bad idea that the
748 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
749 number plate recognition
</a
> tool only is available in the hands of
750 the powerful, and want it to be available also for the powerless to
751 even the score when it comes to surveillance and sousveillance. I
752 discovered the developer
753 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
754 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
755 help him get it into shape to get the package uploaded into the Debian
758 <p
>Today we finally managed to get the package into shape and uploaded
759 it into Debian, where it currently
760 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
761 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
763 <p
>I guess you are wondering why on earth such tool would be useful
764 for the common folks, ie those not running a large government
765 surveillance system? Well, I plan to put it in a computer on my bike
766 and in my car, tracking the cars nearby and allowing me to be notified
767 when number plates on my watch list are discovered. Another use case
768 was suggested by a friend of mine, who wanted to set it up at his home
769 to open the car port automatically when it discovered the plate on his
770 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
771 capable of placing his license plate number of a piece of cardboard to
772 open his car port, men replied that it was always unlocked anyway. I
773 guess for such use case it make sense. I am sure there are other use
774 cases too, for those with imagination and a vision.
</p
>
776 <p
>If you want to build your own version of the Debian package, check
777 out the upstream git source and symlink ./distros/debian to ./debian/
778 before running
"debuild
" to build the source. Or wait a bit until the
779 package show up in unstable.
</p
>
784 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
785 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
786 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
787 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
788 <description><p
>Around three years ago, I created
789 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
790 system
</a
> to get a more practical solution in Debian for handing
791 hardware related packages. A GUI system in the isenkram package will
792 present a pop-up dialog when some hardware dongle supported by
793 relevant packages in Debian is inserted into the machine. The same
794 lookup mechanism to detect packages is available as command line
795 tools in the isenkram-cli package. In addition to mapping hardware,
796 it will also map kernel firmware files to packages and make it easy to
797 install needed firmware packages automatically. The key for this
798 system to work is a good way to map hardware to packages, in other
799 words, allow packages to announce what hardware they will work
802 <p
>I started by providing data files in the isenkram source, and
803 adding code to download the latest version of these data files at run
804 time, to ensure every user had the most up to date mapping available.
805 I also added support for storing the mapping in the Packages file in
806 the apt repositories, but did not push this approach because while I
807 was trying to figure out how to best store hardware/package mappings,
808 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
809 appstream system
</a
> was announced. I got in touch and suggested to
810 add the hardware mapping into that data set to be able to use
811 appstream as a data source, and this was accepted at least for the
812 Debian version of appstream.
</p
>
814 <p
>A few days ago using appstream in Debian for this became possible,
815 and today I uploaded a new version
0.20 of isenkram adding support for
816 appstream as a data source for mapping hardware to packages. The only
817 package so far using appstream to announce its hardware support is my
818 pymissile package. I got help from Matthias Klumpp with figuring out
819 how do add the required
820 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
821 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
822 this content:
</p
>
824 <blockquote
><pre
>
825 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
826 &lt;component
&gt;
827 &lt;id
&gt;pymissile
&lt;/id
&gt;
828 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
829 &lt;name
&gt;pymissile
&lt;/name
&gt;
830 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
831 &lt;description
&gt;
833 Pymissile provides a curses interface to control an original
834 Marks and Spencer / Striker USB Missile Launcher, as well as a
835 motion control script to allow a webcamera to control the
838 &lt;/description
&gt;
839 &lt;provides
&gt;
840 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
841 &lt;/provides
&gt;
842 &lt;/component
&gt;
843 </pre
></blockquote
>
845 <p
>The key for isenkram is the component/provides/modalias value,
846 which is a glob style match rule for hardware specific strings
847 (modalias strings) provided by the Linux kernel. In this case, it
848 will map to all USB devices with vendor code
1130 and product code
851 <p
>Note, it is important that the license of all the metadata files
852 are compatible to have permissions to aggregate them into archive wide
853 appstream files. Matthias suggested to use MIT or BSD licenses for
854 these files. A challenge is figuring out a good id for the data, as
855 it is supposed to be globally unique and shared across distributions
856 (in other words, best to coordinate with upstream what to use). But
857 it can be changed later or, so we went with the package name as
858 upstream for this project is dormant.
</p
>
860 <p
>To get the metadata file installed in the correct location for the
861 mirror update scripts to pick it up and include its content the
862 appstream data source, the file must be installed in the binary
863 package under /usr/share/appdata/. I did this by adding the following
864 line to debian/pymissile.install:
</p
>
866 <blockquote
><pre
>
867 debian/pymissile.metainfo.xml usr/share/appdata
868 </pre
></blockquote
>
870 <p
>With that in place, the command line tool isenkram-lookup will list
871 all packages useful on the current computer automatically, and the GUI
872 pop-up handler will propose to install the package not already
873 installed if a hardware dongle is inserted into the machine in
876 <p
>Details of the modalias field in appstream is available from the
877 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
879 <p
>To locate the modalias values of all hardware present in a machine,
880 try running this command on the command line:
</p
>
882 <blockquote
><pre
>
883 cat $(find /sys/devices/|grep modalias)
884 </pre
></blockquote
>
886 <p
>To learn more about the isenkram system, please check out
887 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
888 blog posts tagged isenkram
</a
>.
</p
>
893 <title>The GNU General Public License is not magic pixie dust
</title>
894 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
895 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
896 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
897 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
898 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
899 GPL is not magic pixie dust
</a
>" explain the importance of making sure
900 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
901 I quote the blog post from Paul in full here with his permission:
<p
>
905 <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
>
908 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
910 The first step is to choose a
911 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
914 The next step is, when someone fails to follow that copyleft license,
915 <b
>it must be enforced
</b
><br/
>
917 and its a simple fact of our modern society that such type of
920 is incredibly expensive to do and incredibly difficult to do.
923 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
924 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
925 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
926 0x57</a
></small
></p
>
928 <p
>As the Debian Website
929 <a href=
"https://bugs.debian.org/
794116">used
</a
>
930 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
931 imply, public domain and permissively licensed software can lead to
932 the production of more proprietary software as people discover useful
933 software, extend it and or incorporate it into their hardware or
934 software products. Copyleft licenses such as the GNU GPL were created
935 to close off this avenue to the production of proprietary software but
936 such licenses are not enough. With the ongoing adoption of Free
937 Software by individuals and groups, inevitably the community
's
938 expectations of license compliance are violated, usually out of
939 ignorance of the way Free Software works, but not always. As Karen
940 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
941 Freedom
">FaiF
</a
>
942 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
943 copyleft is nothing if no-one is willing and able to stand up in court
944 to protect it. The reality of today
's world is that legal
945 representation is expensive, difficult and time consuming. With
946 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
947 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
948 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
949 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
950 of the Linux project, Debian and other groups against GPL violations.
951 In March the SFC supported a
952 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
953 by Christoph Hellwig
</a
> against VMware for refusing to
954 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
955 with the GPL
</a
> in relation to their use of parts of the Linux
956 kernel. Since then two of their sponsors pulled corporate funding and
958 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
959 or cancelled their talks
</a
>. As a result they have decided to rely
960 less on corporate funding and more on the broad community of
961 individuals who support Free Software and copyleft. So the SFC has
962 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
963 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
964 a community of folks who stand up for copyleft and the GPL by
965 supporting their work on promoting and supporting copyleft and Free
968 <p
>If you support Free Software,
969 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
970 what the SFC do, agree with their
971 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
972 principles
</a
>, are happy about their
973 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
974 work on a project that is an SFC
975 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
976 just want to stand up for copyleft, please join
977 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
978 Allan Webber
</a
>,
979 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
981 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
982 Bacon
</a
>, myself and
983 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
985 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
986 next week your donation will be
987 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
988 by an anonymous donor. Please also consider asking your employer to
989 match your donation or become a sponsor of SFC. Don
't forget to
990 spread the word about your support for SFC via email, your blog and or
991 social media accounts.
</p
>
995 <p
>I agree with Paul on this topic and just signed up as a Supporter
996 of Software Freedom Conservancy myself. Perhaps you should be a
997 supporter too?
</p
>
1002 <title>PGP key transition statement for key EE4E02F9
</title>
1003 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
1004 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
1005 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
1006 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
1007 set it up properly. I wanted to generate it offline and have it
1008 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
1009 smart card
</a
> for daily use, and learning how to do it and finding
1010 time to sit down with an offline machine almost took forever. But
1011 finally I
've been able to complete the process, and have now moved
1012 from my old GPG key to a new GPG key. See
1013 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
1014 full transition statement, signed with both my old and new key
</a
> for
1015 the details. This is my new key:
</p
>
1018 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
1019 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
1020 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
1021 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
1022 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
1023 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
1024 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
1027 <p
>The key can be downloaded from the OpenPGP key servers, signed by
1028 my old key.
</p
>
1030 <p
>If you signed my old key
1031 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
1032 I
'd very much appreciate a signature on my new key, details and
1033 instructions in the transition statement. I m happy to reciprocate if
1034 you have a similarly signed transition statement to present.
</p
>
1039 <title>The life and death of a laptop battery
</title>
1040 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
1041 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
1042 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
1043 <description><p
>When I get a new laptop, the battery life time at the start is OK.
1044 But this do not last. The last few laptops gave me a feeling that
1045 within a year, the life time is just a fraction of what it used to be,
1046 and it slowly become painful to use the laptop without power connected
1047 all the time. Because of this, when I got a new Thinkpad X230 laptop
1048 about two years ago, I decided to monitor its battery state to have
1049 more hard facts when the battery started to fail.
</p
>
1051 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
1053 <p
>First I tried to find a sensible Debian package to record the
1054 battery status, assuming that this must be a problem already handled
1055 by someone else. I found
1056 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
1057 which collects statistics from the battery, but it was completely
1058 broken. I sent a few suggestions to the maintainer, but decided to
1059 write my own collector as a shell script while I waited for feedback
1061 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
1062 blog post about the battery development on a MacBook Air
</a
> I also
1064 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
1065 available in Debian.
</p
>
1067 <p
>I started my collector
2013-
07-
15, and it has been collecting
1068 battery stats ever since. Now my
1069 /var/log/hjemmenett-battery-status.log file contain around
115,
000
1070 measurements, from the time the battery was working great until now,
1071 when it is unable to charge above
7% of original capacity. My
1072 collector shell script is quite simple and look like this:
</p
>
1077 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
1079 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
1080 logfile=/var/log/hjemmenett-battery-status.log
1082 files=
"manufacturer model_name technology serial_number \
1083 energy_full energy_full_design energy_now cycle_count status
"
1085 if [ ! -e
"$logfile
" ] ; then
1087 printf
"timestamp,
"
1089 printf
"%s,
" $f
1092 )
> "$logfile
"
1096 # Print complete message in one echo call, to avoid race condition
1097 # when several log processes run in parallel.
1098 msg=$(printf
"%s,
" $(date +%s); \
1099 for f in $files; do \
1100 printf
"%s,
" $(cat $f); \
1102 echo
"$msg
"
1105 cd /sys/class/power_supply
1108 (cd $bat
&& log_battery
>> "$logfile
")
1112 <p
>The script is called when the power management system detect a
1113 change in the power status (power plug in or out), and when going into
1114 and out of hibernation and suspend. In addition, it collect a value
1115 every
10 minutes. This make it possible for me know when the battery
1116 is discharging, charging and how the maximum charge change over time.
1117 The code for the Debian package
1118 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
1119 available on github
</a
>.
</p
>
1121 <p
>The collected log file look like this:
</p
>
1124 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
1125 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
1127 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1128 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
1131 <p
>I wrote a small script to create a graph of the charge development
1132 over time. This graph depicted above show the slow death of my laptop
1135 <p
>But why is this happening? Why are my laptop batteries always
1136 dying in a year or two, while the batteries of space probes and
1137 satellites keep working year after year. If we are to believe
1138 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
1139 University
</a
>, the cause is me charging the battery whenever I have a
1140 chance, and the fix is to not charge the Lithium-ion batteries to
100%
1141 all the time, but to stay below
90% of full charge most of the time.
1142 I
've been told that the Tesla electric cars
1143 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
1144 the charge of their batteries to
80%
</a
>, with the option to charge to
1145 100% when preparing for a longer trip (not that I would want a car
1146 like Tesla where rights to privacy is abandoned, but that is another
1147 story), which I guess is the option we should have for laptops on
1148 Linux too.
</p
>
1150 <p
>Is there a good and generic way with Linux to tell the battery to
1151 stop charging at
80%, unless requested to charge to
100% once in
1152 preparation for a longer trip? I found
1153 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
1154 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
1155 80%
</a
>, but could not get it to work (kernel module refused to
1158 <p
>I wonder why the battery capacity was reported to be more than
100%
1159 at the start. I also wonder why the
"full capacity
" increases some
1160 times, and if it is possible to repeat the process to get the battery
1161 back to design capacity. And I wonder if the discharge and charge
1162 speed change over time, or if this stay the same. I did not yet try
1163 to write a tool to calculate the derivative values of the battery
1164 level, but suspect some interesting insights might be learned from
1167 <p
>Update
2015-
09-
24: I got a tip to install the packages
1168 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
1169 packages instead of the tp-smapi-dkms package I had tried to use
1170 initially, and use
'tlp setcharge
40 80' to change when charging start
1171 and stop. I
've done so now, but expect my existing battery is toast
1172 and need to be replaced. The proposal is unfortunately Thinkpad
1178 <title>New laptop - some more clues and ideas based on feedback
</title>
1179 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
1180 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
1181 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
1182 <description><p
>Several people contacted me after my previous blog post about my
1183 need for a new laptop, and provided very useful feedback. I wish to
1184 thank every one of these. Several pointed me to the possibility of
1185 fixing my X230, and I am already in the process of getting Lenovo to
1186 do so thanks to the on site, next day support contract covering the
1187 machine. But the battery is almost useless (I expect to replace it
1188 with a non-official battery) and I do not expect the machine to live
1189 for many more years, so it is time to plan its replacement. If I did
1190 not have a support contract, it was suggested to find replacement parts
1191 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
1192 might present a language barrier as I do not understand French.
</p
>
1194 <p
>One tip I got was to use the
1195 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
1196 compare laptop models. It seem to have more models available than
1197 prisjakt.no. Another tip I got from someone I know have similar
1198 keyboard preferences was that the HP EliteBook
840 keyboard is not
1199 very good, and this matches my experience with earlier EliteBook
1200 keyboards I tested. Because of this, I will not consider it any further.
1202 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
1203 newest Thinkpad X model. The keyboard reintroduces mouse buttons
1204 (which is missing from the X240), and is working fairly well with
1205 Debian Sid/Unstable according to
1206 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
1207 got on the keyboard quality are not consistent. Some say the keyboard
1208 is good, others say it is ok, while others say it is not very good.
1209 Those with experience from X41 and and X60 agree that the X250
1210 keyboard is not as good as those trusty old laptops, and suggest I
1211 keep and fix my X230 instead of upgrading, or get a used X230 to
1212 replace it. I
'm also told that the X250 lack leds for caps lock, disk
1213 activity and battery status, which is very convenient on my X230. I
'm
1214 also told that the CPU fan is running very often, making it a bit
1215 noisy. In any case, the X250 do not work out of the box with Debian
1216 Stable/Jessie, one of my requirements.
</p
>
1218 <p
>I have also gotten a few vendor proposals, one was
1219 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
1220 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
1221 The latter look very attractive to me.
</p
>
1223 <p
>Again, thank you all for the very useful feedback. It help a lot
1224 as I keep looking for a replacement.
</p
>
1226 <p
>Update
2015-
07-
06: I was recommended to check out the
1227 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
1229 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
1230 thinkpad X models
</a
>, and provide one year warranty.
</p
>
1235 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
1236 <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>
1237 <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>
1238 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
1239 <description><p
>My primary work horse laptop is failing, and will need a
1240 replacement soon. The left
5 cm of the screen on my Thinkpad X230
1241 started flickering yesterday, and I suspect the cause is a broken
1242 cable, as changing the angle of the screen some times get rid of the
1243 flickering.
</p
>
1245 <p
>My requirements have not really changed since I bought it, and is
1247 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
1248 described them in
2013</a
>. The last time I bought a laptop, I had
1250 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
1251 where I could select at least a few of the requirements (mouse pin,
1252 wifi, weight) and go through the rest manually. Three button mouse
1253 and a good keyboard is not available as an option, and all the three
1254 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
1255 G2) lack three mouse buttons). It is also unclear to me how good the
1256 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
1257 the keyboard, even if the quality and robustness in the X series have
1258 deteriorated since X41.
</p
>
1260 <p
>I wonder how I can find a sensible laptop when none of the options
1261 seem sensible to me? Are there better services around to search the
1262 set of available laptops for features? Please send me an email if you
1263 have suggestions.
</p
>
1265 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
1266 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
1267 of endorsed hardware
</a
>, which is useful background information.
</p
>
1272 <title>How to stay with sysvinit in Debian Jessie
</title>
1273 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
1274 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
1275 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
1276 <description><p
>By now, it is well known that Debian Jessie will not be using
1277 sysvinit as its boot system by default. But how can one keep using
1278 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
1280 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
1281 Schubert
</a
> and
1282 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
1285 <p
>If you already are using Wheezy and want to upgrade to Jessie and
1286 keep sysvinit as your boot system, create a file
1287 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
1288 you upgrade:
</p
>
1290 <p
><blockquote
><pre
>
1291 Package: systemd-sysv
1292 Pin: release o=Debian
1294 </pre
></blockquote
><p
>
1296 <p
>This file content will tell apt and aptitude to not consider
1297 installing systemd-sysv as part of any installation and upgrade
1298 solution when resolving dependencies, and thus tell it to avoid
1299 systemd as a default boot system. The end result should be that the
1300 upgraded system keep using sysvinit.
</p
>
1302 <p
>If you are installing Jessie for the first time, there is no way to
1303 get sysvinit installed by default (debootstrap used by
1304 debian-installer have no option for this), but one can tell the
1305 installer to switch to sysvinit before the first boot. Either by
1306 using a kernel argument to the installer, or by adding a line to the
1307 preseed file used. First, the kernel command line argument:
1309 <p
><blockquote
><pre
>
1310 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
1311 </pre
></blockquote
><p
>
1313 <p
>Next, the line to use in a preseed file:
</p
>
1315 <p
><blockquote
><pre
>
1316 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
1317 </pre
></blockquote
><p
>
1319 <p
>One can of course also do this after the first boot by installing
1320 the sysvinit-core package.
</p
>
1322 <p
>I recommend only using sysvinit if you really need it, as the
1323 sysvinit boot sequence in Debian have several hardware specific bugs
1324 on Linux caused by the fact that it is unpredictable when hardware
1325 devices show up during boot. But on the other hand, the new default
1326 boot system still have a few rough edges I hope will be fixed before
1327 Jessie is released.
</p
>
1329 <p
>Update
2014-
11-
26: Inspired by
1330 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
1331 blog post by Torsten Glaser
</a
>, added --purge to the preseed
1337 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
1338 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
1339 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
1340 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
1341 <description><p
>The right to communicate with your friends and family in private,
1342 without anyone snooping, is a right every citicen have in a liberal
1343 democracy. But this right is under serious attack these days.
</p
>
1345 <p
>A while back it occurred to me that one way to make the dragnet
1346 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
1347 the whisleblower Snowden) more expensive for Internet email,
1348 is to deliver all email using SMTP via Tor. Such SMTP option would be
1349 a nice addition to the FreedomBox project if we could send email
1350 between FreedomBox machines without leaking metadata about the emails
1351 to the people peeking on the wire. I
1352 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
1353 this on the FreedomBox project mailing list in October
</a
> and got a
1354 lot of useful feedback and suggestions. It also became obvious to me
1355 that this was not a novel idea, as the same idea was tested and
1356 documented by Johannes Berg as early as
2006, and both
1357 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
1358 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
1359 propose a similar method / protocol to pass emails between users.
</p
>
1361 <p
>To implement such system one need to set up a Tor hidden service
1362 providing the SMTP protocol on port
25, and use email addresses
1363 looking like username@hidden-service-name.onion. With such addresses
1364 the connections to port
25 on hidden-service-name.onion using Tor will
1365 go to the correct SMTP server. To do this, one need to configure the
1366 Tor daemon to provide the hidden service and the mail server to accept
1367 emails for this .onion domain. To learn more about Exim configuration
1368 in Debian and test the design provided by Johannes Berg in his FAQ, I
1369 set out yesterday to create a Debian package for making it trivial to
1370 set up such SMTP over Tor service based on Debian. Getting it to work
1371 were fairly easy, and
1372 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
1373 source code for the Debian package
</a
> is available from github. I
1374 plan to move it into Debian if further testing prove this to be a
1375 useful approach.
</p
>
1377 <p
>If you want to test this, set up a blank Debian machine without any
1378 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
1379 get rid of exim4). Install tor, clone the git repository mentioned
1380 above, build the deb and install it on the machine. Next, run
1381 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
1382 the instructions to get the service up and running. Restart tor and
1383 exim when it is done, and test mail delivery using swaks like
1386 <p
><blockquote
><pre
>
1387 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
1388 --to fbx@dutlqrrmjhtfa3vp.onion
1389 </pre
></blockquote
></p
>
1391 <p
>This will test the SMTP delivery using tor. Replace the email
1392 address with your own address to test your server. :)
</p
>
1394 <p
>The setup procedure is still to complex, and I hope it can be made
1395 easier and more automatic. Especially the tor setup need more work.
1396 Also, the package include a tor-smtp tool written in C, but its task
1397 should probably be rewritten in some script language to make the deb
1398 architecture independent. It would probably also make the code easier
1399 to review. The tor-smtp tool currently need to listen on a socket for
1400 exim to talk to it and is started using xinetd. It would be better if
1401 no daemon and no socket is needed. I suspect it is possible to get
1402 exim to run a command line tool for delivery instead of talking to a
1403 socket, and hope to figure out how in a future version of this
1406 <p
>Until I wipe my test machine, I can be reached using the
1407 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
1408 SMTorP. :)
</p
>
1413 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
1414 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
1415 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
1416 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
1417 <description><p
>If you ever had to moderate a mailman list, like the ones on
1418 alioth.debian.org, you know the web interface is fairly slow to
1419 operate. First you visit one web page, enter the moderation password
1420 and get a new page shown with a list of all the messages to moderate
1421 and various options for each email address. This take a while for
1422 every list you moderate, and you need to do it regularly to do a good
1423 job as a list moderator. But there is a quick alternative,
1424 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
1425 listadmin program
</a
>. It allow you to check lists for new messages
1426 to moderate in a fraction of a second. Here is a test run on two
1427 lists I recently took over:
</p
>
1429 <p
><blockquote
><pre
>
1430 % time listadmin xiph
1431 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1432 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1438 </pre
></blockquote
></p
>
1440 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
1441 there are no message in the moderation queue. Every morning I
1442 currently moderate
68 mailman lists, and it normally take around two
1443 minutes. When I took over the two pkg-xiph lists above a few days
1444 ago, there were
400 emails waiting in the moderator queue. It took me
1445 less than
15 minutes to process them all using the listadmin
1448 <p
>If you install
1449 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
1450 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
1451 with content like this, the moderation task is a breeze:
</p
>
1453 <p
><blockquote
><pre
>
1454 username username@example.org
1457 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
1460 adminurl https://{domain}/mailman/admindb/{list}
1461 mailman-list@lists.example.com
1464 other-list@otherserver.example.org
1465 </pre
></blockquote
></p
>
1467 <p
>There are other options to set as well. Check the manual page to
1468 learn the details.
</p
>
1470 <p
>If you are forced to moderate lists on a mailman installation where
1471 the SSL certificate is self signed or not properly signed by a
1472 generally accepted signing authority, you can set a environment
1473 variable when calling listadmin to disable SSL verification:
</p
>
1475 <p
><blockquote
><pre
>
1476 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
1477 </pre
></blockquote
></p
>
1479 <p
>If you want to moderate a subset of the lists you take care of, you
1480 can provide an argument to the listadmin script like I do in the
1481 initial screen dump (the xiph argument). Using an argument, only
1482 lists matching the argument string will be processed. This make it
1483 quick to accept messages if you notice the moderation request in your
1486 <p
>Without the listadmin program, I would never be the moderator of
68
1487 mailing lists, as I simply do not have time to spend on that if the
1488 process was any slower. The listadmin program have saved me hours of
1489 time I could spend elsewhere over the years. It truly is nice free
1492 <p
>As usual, if you use Bitcoin and want to show your support of my
1493 activities, please send Bitcoin donations to my address
1494 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1496 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
1497 configuration example. Also, I
've been told that the
1498 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
1504 <title>Debian Jessie, PXE and automatic firmware installation
</title>
1505 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
1506 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
1507 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
1508 <description><p
>When PXE installing laptops with Debian, I often run into the
1509 problem that the WiFi card require some firmware to work properly.
1510 And it has been a pain to fix this using preseeding in Debian.
1511 Normally something more is needed. But thanks to
1512 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
1513 package
</a
> and its recent tasksel extension, it has now become easy
1514 to do this using simple preseeding.
</p
>
1516 <p
>The isenkram-cli package provide tasksel tasks which will install
1517 firmware for the hardware found in the machine (actually, requested by
1518 the kernel modules for the hardware). (It can also install user space
1519 programs supporting the hardware detected, but that is not the focus
1520 of this story.)
</p
>
1522 <p
>To get this working in the default installation, two preeseding
1523 values are needed. First, the isenkram-cli package must be installed
1524 into the target chroot (aka the hard drive) before tasksel is executed
1525 in the pkgsel step of the debian-installer system. This is done by
1526 preseeding the base-installer/includes debconf value to include the
1527 isenkram-cli package. The package name is next passed to debootstrap
1528 for installation. With the isenkram-cli package in place, tasksel
1529 will automatically use the isenkram tasks to detect hardware specific
1530 packages for the machine being installed and install them, because
1531 isenkram-cli contain tasksel tasks.
</p
>
1533 <p
>Second, one need to enable the non-free APT repository, because
1534 most firmware unfortunately is non-free. This is done by preseeding
1535 the apt-mirror-setup step. This is unfortunate, but for a lot of
1536 hardware it is the only option in Debian.
</p
>
1538 <p
>The end result is two lines needed in your preseeding file to get
1539 firmware installed automatically by the installer:
</p
>
1541 <p
><blockquote
><pre
>
1542 base-installer base-installer/includes string isenkram-cli
1543 apt-mirror-setup apt-setup/non-free boolean true
1544 </pre
></blockquote
></p
>
1546 <p
>The current version of isenkram-cli in testing/jessie will install
1547 both firmware and user space packages when using this method. It also
1548 do not work well, so use version
0.15 or later. Installing both
1549 firmware and user space packages might give you a bit more than you
1550 want, so I decided to split the tasksel task in two, one for firmware
1551 and one for user space programs. The firmware task is enabled by
1552 default, while the one for user space programs is not. This split is
1553 implemented in the package currently in unstable.
</p
>
1555 <p
>If you decide to give this a go, please let me know (via email) how
1556 this recipe work for you. :)
</p
>
1558 <p
>So, I bet you are wondering, how can this work. First and
1559 foremost, it work because tasksel is modular, and driven by whatever
1560 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1561 isenkram-cli package place two files for tasksel to find. First there
1562 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
1564 <p
><blockquote
><pre
>
1565 Task: isenkram-packages
1567 Description: Hardware specific packages (autodetected by isenkram)
1568 Based on the detected hardware various hardware specific packages are
1570 Test-new-install: show show
1572 Packages: for-current-hardware
1574 Task: isenkram-firmware
1576 Description: Hardware specific firmware packages (autodetected by isenkram)
1577 Based on the detected hardware various hardware specific firmware
1578 packages are proposed.
1579 Test-new-install: mark show
1581 Packages: for-current-hardware-firmware
1582 </pre
></blockquote
></p
>
1584 <p
>The key parts are Test-new-install which indicate how the task
1585 should be handled and the Packages line referencing to a script in
1586 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1587 list of packages to install. The for-current-hardware-firmware script
1588 look like this to list relevant firmware for the machine:
1590 <p
><blockquote
><pre
>
1593 PATH=/usr/sbin:$PATH
1595 isenkram-autoinstall-firmware -l
1596 </pre
></blockquote
></p
>
1598 <p
>With those two pieces in place, the firmware is installed by
1599 tasksel during the normal d-i run. :)
</p
>
1601 <p
>If you want to test what tasksel will install when isenkram-cli is
1602 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
1603 --new-install
</tt
> to get the list of packages that tasksel would
1606 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
1607 pilots in testing this feature, as isenkram is used there now to
1608 install firmware, replacing the earlier scripts.
</p
>
1613 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
1614 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
1615 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
1616 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
1617 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
1618 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1619 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
1620 on a screen normally showing the bread types and prizes:
</p
>
1622 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
1624 <p
>If it had booted as it was supposed to, I would never had known
1625 about this hidden Linux installation. It is interesting what
1626 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
1631 <title>New lsdvd release version
0.17 is ready
</title>
1632 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
1633 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
1634 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
1635 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
1636 got a new set of developers a few weeks ago, after the original
1637 developer decided to step down and pass the project to fresh blood.
1638 This project is now maintained by Petter Reinholdtsen and Steve
1641 <p
>I just wrapped up
1642 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
1643 new lsdvd release
</a
>, available in git or from
1644 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
1645 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
1650 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
1651 <li
>Check for garbage in the program chains, which indicate that a track is
1652 non-existant, to work around additional copy protection
</li
>
1653 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
1654 <li
>Fix pallete display of first entry
</li
>
1655 <li
>Fix include orders
</li
>
1656 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
1657 <li
>Fix the chapter count
</li
>
1658 <li
>Make sure the array size and the array limit used when initialising
1659 the palette size is the same.
</li
>
1660 <li
>Fix array printing.
</li
>
1661 <li
>Correct subsecond calculations.
</li
>
1662 <li
>Add sector information to the output format.
</li
>
1663 <li
>Clean up code to be closer to ANSI C and compile without warnings
1664 with more GCC compiler warnings.
</li
>
1668 <p
>This change bring together patches for lsdvd in use in various
1669 Linux and Unix distributions, as well as patches submitted to the
1670 project the last nine years. Please check it out. :)
</p
>
1675 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
1676 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
1677 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
1678 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
1679 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
1680 project
</a
> provide a Linux solution for schools, including a
1681 powerful desktop with education software, a central server providing
1682 web pages, user database, user home directories, central login and PXE
1683 boot of both clients without disk and the installation to install Debian
1684 Edu on machines with disk (and a few other services perhaps to small
1685 to mention here). We in the Debian Edu team are currently working on
1686 the Jessie based version, trying to get everything in shape before the
1687 freeze, to avoid having to maintain our own package repository in the
1689 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
1690 status
</a
> can be seen on the Debian wiki, and there is still heaps of
1691 work left. Some fatal problems block testing, breaking the installer,
1692 but it is possible to work around these to get anyway. Here is a
1693 recipe on how to get the installation limping along.
</p
>
1695 <p
>First, download the test ISO via
1696 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
1697 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
1699 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
1700 The ISO build was broken on Tuesday, so we do not get a new ISO every
1701 12 hours or so, but thankfully the ISO we already got we are able to
1702 install with some tweaking.
</p
>
1704 <p
>When you get to the Debian Edu profile question, go to tty2
1705 (use Alt-Ctrl-F2), run
</p
>
1707 <p
><blockquote
><pre
>
1708 nano /usr/bin/edu-eatmydata-install
1709 </pre
></blockquote
></p
>
1711 <p
>and add
'exit
0' as the second line, disabling the eatmydata
1712 optimization. Return to the installation, select the profile you want
1713 and continue. Without this change, exim4-config will fail to install
1714 due to a known bug in eatmydata.
</p
>
1716 <p
>When you get the grub question at the end, answer /dev/sda (or if
1717 this do not work, figure out what your correct value would be. All my
1718 test machines need /dev/sda, so I have no advice if it do not fit
1719 your need.
</p
>
1721 <p
>If you installed a profile including a graphical desktop, log in as
1722 root after the initial boot from hard drive, and install the
1723 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1724 or mate. If you want several desktop options, install more than one
1725 metapackage. Once this is done, reboot and you should have a working
1726 graphical login screen. This workaround should no longer be needed
1727 once the education-tasks package version
1.801 enter testing in two
1730 <p
>I believe the ISO build will start working on two days when the new
1731 tasksel package enter testing and Steve McIntyre get a chance to
1732 update the debian-cd git repository. The eatmydata, grub and desktop
1733 issues are already fixed in unstable and testing, and should show up
1734 on the ISO as soon as the ISO build start working again. Well the
1735 eatmydata optimization is really just disabled. The proper fix
1736 require an upload by the eatmydata maintainer applying the patch
1737 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
1738 The rest have proper fixes in unstable.
</p
>
1740 <p
>I hope this get you going with the installation testing, as we are
1741 quickly running out of time trying to get our Jessie based
1742 installation ready before the distribution freeze in a month.
</p
>
1747 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
1748 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
1749 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
1750 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
1751 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
1752 to handle my fairly large DVD collection. It is a nice command line
1753 tool to get details about a DVD, like title, tracks, track length,
1754 etc, in XML, Perl or human readable format. But lsdvd have not seen
1755 any new development since
2006 and had a few irritating bugs affecting
1756 its use with some DVDs. Upstream seemed to be dead, and in January I
1757 sent a small probe asking for a version control repository for the
1758 project, without any reply. But I use it regularly and would like to
1759 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
1760 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
1761 the project admin, and after getting a reply from him explaining that
1762 he was no longer interested in the project, I asked if I could take
1763 over. And yesterday, I became project admin.
</p
>
1765 <p
>I
've been in touch with a Gentoo developer and the Debian
1766 maintainer interested in joining forces to maintain the upstream
1767 project, and I hope we can get a new release out fairly quickly,
1768 collecting the patches spread around on the internet into on place.
1769 I
've added the relevant Debian patches to the freshly created git
1770 repository, and expect the Gentoo patches to make it too. If you got
1771 a DVD collection and care about command line tools, check out
1772 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
1773 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
1774 list
</a
>. :)
</p
>
1779 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
1780 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
1781 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
1782 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
1783 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
1784 a lot quicker. When we install more than
2000 packages in
1785 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
1786 tasksel in the installer, unpacking the binary packages take forever.
1787 A part of the slow I/O issue was discussed in
1788 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
1789 much file system sync-ing done by dpkg, which is the package
1790 responsible for unpacking the binary packages. Other parts (like code
1791 executed by postinst scripts) might also sync to disk during
1792 installation. All this sync-ing to disk do not really make sense to
1793 me. If the machine crash half-way through, I start over, I do not try
1794 to salvage the half installed system. So the failure sync-ing is
1795 supposed to protect against, hardware or system crash, is not really
1796 relevant while the installer is running.
</p
>
1798 <p
>A few days ago, I thought of a way to get rid of all the file
1799 system sync()-ing in a fairly non-intrusive way, without the need to
1800 change the code in several packages. The idea is not new, but I have
1801 not heard anyone propose the approach using dpkg-divert before. It
1802 depend on the small and clever package
1803 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
1804 uses LD_PRELOAD to replace the system functions for syncing data to
1805 disk with functions doing nothing, thus allowing programs to live
1806 dangerous while speeding up disk I/O significantly. Instead of
1807 modifying the implementation of dpkg, apt and tasksel (which are the
1808 packages responsible for selecting, fetching and installing packages),
1809 it occurred to me that we could just divert the programs away, replace
1810 them with a simple shell wrapper calling
1811 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
1812 Two days ago I decided to test the idea, and wrapped up a simple
1813 implementation for the Debian Edu udeb.
</p
>
1815 <p
>The effect was stunning. In my first test it reduced the running
1816 time of the pkgsel step (installing tasks) from
64 to less than
44
1817 minutes (
20 minutes shaved off the installation) on an old Dell
1818 Latitude D505 machine. I am not quite sure what the optimised time
1819 would have been, as I messed up the testing a bit, causing the debconf
1820 priority to get low enough for two questions to pop up during
1821 installation. As soon as I saw the questions I moved the installation
1822 along, but do not know how long the question were holding up the
1823 installation. I did some more measurements using Debian Edu Jessie,
1824 and got these results. The time measured is the time stamp in
1825 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
1826 "pkgsel: finishing up
" lines, if you want to do the same measurement
1827 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1828 timing thus do not depend on how quickly the user handle the tasksel
1831 <p
><table
>
1834 <th
>Machine/setup
</th
>
1835 <th
>Original tasksel
</th
>
1836 <th
>Optimised tasksel
</th
>
1837 <th
>Reduction
</th
>
1841 <td
>Latitude D505 Main+LTSP LXDE
</td
>
1842 <td
>64 min (
07:
46-
08:
50)
</td
>
1843 <td
><44 min (
11:
27-
12:
11)
</td
>
1844 <td
>>20 min
18%
</td
>
1848 <td
>Latitude D505 Roaming LXDE
</td
>
1849 <td
>57 min (
08:
48-
09:
45)
</td
>
1850 <td
>34 min (
07:
43-
08:
17)
</td
>
1851 <td
>23 min
40%
</td
>
1855 <td
>Latitude D505 Minimal
</td
>
1856 <td
>22 min (
10:
37-
10:
59)
</td
>
1857 <td
>11 min (
11:
16-
11:
27)
</td
>
1858 <td
>11 min
50%
</td
>
1862 <td
>Thinkpad X200 Minimal
</td
>
1863 <td
>6 min (
08:
19-
08:
25)
</td
>
1864 <td
>4 min (
08:
04-
08:
08)
</td
>
1865 <td
>2 min
33%
</td
>
1869 <td
>Thinkpad X200 Roaming KDE
</td
>
1870 <td
>19 min (
09:
21-
09:
40)
</td
>
1871 <td
>15 min (
10:
25-
10:
40)
</td
>
1872 <td
>4 min
21%
</td
>
1875 </table
></p
>
1877 <p
>The test is done using a netinst ISO on a USB stick, so some of the
1878 time is spent downloading packages. The connection to the Internet
1879 was
100Mbit/s during testing, so downloading should not be a
1880 significant factor in the measurement. Download typically took a few
1881 seconds to a few minutes, depending on the amount of packages being
1882 installed.
</p
>
1884 <p
>The speedup is implemented by using two hooks in
1885 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
1886 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
1887 finish-install.d hook to remove the divert at the end of the
1888 installation. I picked the pre-pkgsel.d hook instead of the
1889 post-base-installer.d hook because I test using an ISO without the
1890 eatmydata package included, and the post-base-installer.d hook in
1891 Debian Edu can only operate on packages included in the ISO. The
1892 negative effect of this is that I am unable to activate this
1893 optimization for the kernel installation step in d-i. If the code is
1894 moved to the post-base-installer.d hook, the speedup would be larger
1895 for the entire installation.
</p
>
1897 <p
>I
've implemented this in the
1898 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
1899 git repository, and plan to provide the optimization as part of the
1900 Debian Edu installation. If you want to test this yourself, you can
1901 create two files in the installer (or in an udeb). One shell script
1902 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
1904 <p
><blockquote
><pre
>
1907 . /usr/share/debconf/confmodule
1909 logger -t my-pkgsel
"info: $*
"
1912 logger -t my-pkgsel
"error: $*
"
1914 override_install() {
1915 apt-install eatmydata || true
1916 if [ -x /target/usr/bin/eatmydata ] ; then
1917 for bin in dpkg apt-get aptitude tasksel ; do
1919 # Test that the file exist and have not been diverted already.
1920 if [ -f /target$file ] ; then
1921 info
"diverting $file using eatmydata
"
1922 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
1923 > /target$file.edu
1924 chmod
755 /target$file.edu
1925 in-target dpkg-divert --package debian-edu-config \
1926 --rename --quiet --add $file
1927 ln -sf ./$bin.edu /target$file
1929 error
"unable to divert $file, as it is missing.
"
1933 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
1938 </pre
></blockquote
></p
>
1940 <p
>To clean up, another shell script should go into
1941 /usr/lib/finish-install.d/ with code like this:
1943 <p
><blockquote
><pre
>
1945 . /usr/share/debconf/confmodule
1947 logger -t my-finish-install
"error: $@
"
1949 remove_install_override() {
1950 for bin in dpkg apt-get aptitude tasksel ; do
1952 if [ -x /target$file.edu ] ; then
1954 in-target dpkg-divert --package debian-edu-config \
1955 --rename --quiet --remove $file
1958 error
"Missing divert for $file.
"
1961 sync # Flush file buffers before continuing
1964 remove_install_override
1965 </pre
></blockquote
></p
>
1967 <p
>In Debian Edu, I placed both code fragments in a separate script
1968 edu-eatmydata-install and call it from the pre-pkgsel.d and
1969 finish-install.d scripts.
</p
>
1971 <p
>By now you might ask if this change should get into the normal
1972 Debian installer too? I suspect it should, but am not sure the
1973 current debian-installer coordinators find it useful enough. It also
1974 depend on the side effects of the change. I
'm not aware of any, but I
1975 guess we will see if the change is safe after some more testing.
1976 Perhaps there is some package in Debian depending on sync() and
1977 fsync() having effect? Perhaps it should go into its own udeb, to
1978 allow those of us wanting to enable it to do so without affecting
1981 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
1982 will break installation of all programs using gnutls because of
1983 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
1984 eatmydata package in Debian will solve it.
</p
>
1986 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
1987 the optimization work again. And I have discovered that the
1988 dpkg-divert trick is not really needed and implemented a slightly
1989 simpler approach as part of the debian-edu-install package. See
1990 tools/edu-eatmydata-install in the source package.
</p
>
1992 <p
>Update
2014-
11-
11: Unfortunately, a new
1993 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
1994 triggering on i386 made it into testing, and broke this installation
1995 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
1996 request
768893</a
> is accepted, it should be working again.
</p
>
2001 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
2002 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
2003 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
2004 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
2005 <description><p
>Yesterday, I had the pleasure of attending a talk with the
2006 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
2007 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
2008 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
2009 learn that there is a large set of publicly available key servers to
2010 use when looking for peoples public key. So far I have used
2011 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
2012 were misbehaving, but those days are ended. The servers I have used
2013 up until yesterday have been slow and some times unavailable. I hope
2014 those problems are gone now.
</p
>
2016 <p
>Behind the round robin DNS entry of the
2017 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
2018 there is a pool of more than
100 keyservers which are checked every
2019 day to ensure they are well connected and up to date. It must be
2020 better than what I have used so far. :)
</p
>
2022 <p
>Yesterdays speaker told me that the service is the default
2023 keyserver provided by the default configuration in GnuPG, but this do
2024 not seem to be used in Debian. Perhaps it should?
</p
>
2026 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
2029 <p
><blockquote
><pre
>
2030 keyserver pool.sks-keyservers.net
2031 </pre
></blockquote
></p
>
2033 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
2034 entries in DNS. Just for fun, I did just that at work, so now every
2035 user of GnuPG at the University of Oslo should find a OpenGPG
2036 keyserver automatically should their need it:
</p
>
2038 <p
><blockquote
><pre
>
2039 % host -t srv _pgpkey-http._tcp.uio.no
2040 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
2042 </pre
></blockquote
></p
>
2044 <p
>Now if only
2045 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
2046 HKP lookup protocol
</a
> supported finding signature paths, I would be
2047 very happy. It can look up a given key or search for a user ID, but I
2048 normally do not want that, but to find a trust path from my key to
2049 another key. Given a user ID or key ID, I would like to find (and
2050 download) the keys representing a signature path from my key to the
2051 key in question, to be able to get a trust path between the two keys.
2052 This is as far as I can tell not possible today. Perhaps something
2053 for a future version of the protocol?
</p
>
2058 <title>From English wiki to translated PDF and epub via Docbook
</title>
2059 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
2060 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
2061 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
2062 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2063 project
</a
> provide an instruction manual for teachers, system
2064 administrators and other users that contain useful tips for setting up
2065 and maintaining a Debian Edu installation. This text is about how the
2066 text processing of this manual is handled in the project.
</p
>
2068 <p
>One goal of the project is to provide information in the native
2069 language of its users, and for this we need to handle translations.
2070 But we also want to make sure each language contain the same
2071 information, so for this we need a good way to keep the translations
2072 in sync. And we want it to be easy for our users to improve the
2073 documentation, avoiding the need to learn special formats or tools to
2074 contribute, and the obvious way to do this is to make it possible to
2075 edit the documentation using a web browser. We also want it to be
2076 easy for translators to keep the translation up to date, and give them
2077 help in figuring out what need to be translated. Here is the list of
2078 tools and the process we have found trying to reach all these
2081 <p
>We maintain the authoritative source of our manual in the
2082 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
2083 wiki
</a
>, as several wiki pages written in English. It consist of one
2084 front page with references to the different chapters, several pages
2085 for each chapter, and finally one
"collection page
" gluing all the
2086 chapters together into one large web page (aka
2087 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
2088 AllInOne page
</a
>). The AllInOne page is the one used for further
2089 processing and translations. Thanks to the fact that the
2090 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
2091 wiki.debian.org support exporting pages in
2092 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
2093 the list of pages to export using the raw version of the AllInOne
2094 page, loop over each of them to generate a Docbook XML version of the
2095 manual. This process also download images and transform image
2096 references to use the locally downloaded images. The generated
2097 Docbook XML files are slightly broken, so some post-processing is done
2098 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
2099 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
2100 a handfull of images. The XML file can now be used to generate PDF, HTML
2101 and epub versions of the English manual. This is the basic step of
2102 our process, making PDF (using dblatex), HTML (using xsltproc) and
2103 epub (using dbtoepub) version from Docbook XML, and the resulting files
2104 are placed in the debian-edu-doc-en binary package.
</p
>
2106 <p
>But English documentation is not enough for us. We want translated
2107 documentation too, and we want to make it easy for translators to
2108 track the English original. For this we use the
2109 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
2110 which allow us to transform the English Docbook XML file into a
2111 translation file (a .pot file), usable with the normal gettext based
2112 translation tools used by those translating free software. The pot
2113 file is used to create and maintain translation files (several .po
2114 files), which the translations update with the native language
2115 translations of all titles, paragraphs and blocks of text in the
2116 original. The next step is combining the original English Docbook XML
2117 and the translation file (say debian-edu-wheezy-manual.nb.po), to
2118 create a translated Docbook XML file (in this case
2119 debian-edu-wheezy-manual.nb.xml). This translated (or partly
2120 translated, if the translation is not complete) Docbook XML file can
2121 then be used like the original to create a PDF, HTML and epub version
2122 of the documentation.
</p
>
2124 <p
>The translators use different tools to edit the .po files. We
2126 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
2127 while some use emacs and vi, others can use web based editors like
2128 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
2129 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
2130 is where the .po file end up, in our git repository. Updated
2131 translations can either be committed directly to git, or submitted as
2132 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
2133 against the debian-edu-doc package
</a
>.
</p
>
2135 <p
>One challenge is images, which both might need to be translated (if
2136 they show translated user applications), and are needed in different
2137 formats when creating PDF and HTML versions (epub is a HTML version in
2138 this regard). For this we transform the original PNG images to the
2139 needed density and format during build, and have a way to provide
2140 translated images by storing translated versions in
2141 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
2142 package maintainers know more.
</p
>
2144 <p
>If you wonder what the result look like, we provide
2145 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
2146 of the documentation packages on the web
</a
>. See for example the
2147 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
2148 PDF version
</a
> or the
2149 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
2150 HTML version
</a
>. We do not yet build the epub version by default,
2151 but perhaps it will be done in the future.
</p
>
2153 <p
>To learn more, check out
2154 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
2155 debian-edu-doc package
</a
>,
2156 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
2157 manual on the wiki
</a
> and
2158 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
2159 translation instructions
</a
> in the manual.
</p
>
2164 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
2165 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
2166 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
2167 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
2168 <description><p
>It would be nice if it was easier in Debian to get all the hardware
2169 related packages relevant for the computer installed automatically.
2170 So I implemented one, using
2171 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
2172 package
</a
>. To use it, install the tasksel and isenkram packages and
2173 run tasksel as user root. You should be presented with a new option,
2174 "Hardware specific packages (autodetected by isenkram)
". When you
2175 select it, tasksel will install the packages isenkram claim is fit for
2176 the current hardware, hot pluggable or not.
<p
>
2178 <p
>The implementation is in two files, one is the tasksel menu entry
2179 description, and the other is the script used to extract the list of
2180 packages to install. The first part is in
2181 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
2184 <p
><blockquote
><pre
>
2187 Description: Hardware specific packages (autodetected by isenkram)
2188 Based on the detected hardware various hardware specific packages are
2190 Test-new-install: mark show
2192 Packages: for-current-hardware
2193 </pre
></blockquote
></p
>
2195 <p
>The second part is in
2196 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
2199 <p
><blockquote
><pre
>
2204 isenkram-autoinstall-firmware -l
2206 </pre
></blockquote
></p
>
2208 <p
>All in all, a very short and simple implementation making it
2209 trivial to install the hardware dependent package we all may want to
2210 have installed on our machines. I
've not been able to find a way to
2211 get tasksel to tell you exactly which packages it plan to install
2212 before doing the installation. So if you are curious or careful,
2213 check the output from the isenkram-* command line tools first.
</p
>
2215 <p
>The information about which packages are handling which hardware is
2216 fetched either from the isenkram package itself in
2217 /usr/share/isenkram/, from git.debian.org or from the APT package
2218 database (using the Modaliases header). The APT package database
2219 parsing have caused a nasty resource leak in the isenkram daemon (bugs
2220 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
2221 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
2222 the python-apt code (bug
2223 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
2224 workaround I was able to get rid of the file descriptor leak and
2225 reduce the memory leak from ~
30 MiB per hardware detection down to
2226 around
2 MiB per hardware detection. It should make the desktop
2227 daemon a lot more useful. The fix is in version
0.7 uploaded to
2228 unstable today.
</p
>
2230 <p
>I believe the current way of mapping hardware to packages in
2231 Isenkram is is a good draft, but in the future I expect isenkram to
2232 use the AppStream data source for this. A proposal for getting proper
2233 AppStream support into Debian is floating around as
2234 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
2235 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
2236 project
</a
> will take place this summer to improve the situation. I
2237 look forward to seeing the result, and welcome patches for isenkram to
2238 start using the information when it is ready.
</p
>
2240 <p
>If you want your package to map to some specific hardware, either
2241 add a
"Xb-Modaliases
" header to your control file like I did in
2242 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
2243 package
</a
> or submit a bug report with the details to the isenkram
2245 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
2246 blog posts tagged isenkram
</a
> for details on the notation. I expect
2247 the information will be migrated to AppStream eventually, but for the
2248 moment I got no better place to store it.
</p
>
2253 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
2254 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
2255 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
2256 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
2257 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
2258 project
</a
> is working on providing the software and hardware to make
2259 it easy for non-technical people to host their data and communication
2260 at home, and being able to communicate with their friends and family
2261 encrypted and away from prying eyes. It is still going strong, and
2262 today a major mile stone was reached.
</p
>
2264 <p
>Today, the last of the packages currently used by the project to
2265 created the system images were accepted into Debian Unstable. It was
2266 the freedombox-setup package, which is used to configure the images
2267 during build and on the first boot. Now all one need to get going is
2268 the build code from the freedom-maker git repository and packages from
2269 Debian. And once the freedombox-setup package enter testing, we can
2270 build everything directly from Debian. :)
</p
>
2272 <p
>Some key packages used by Freedombox are
2273 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
2274 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
2275 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
2276 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
2277 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
2278 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
2279 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
2280 are plans to integrate more packages into the setup. User
2281 documentation is maintained on the Debian wiki. Please
2282 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
2283 the manual
</a
> and help us improve it.
</p
>
2285 <p
>To test for yourself and create boot images with the FreedomBox
2286 setup, run this on a Debian machine using a user with sudo rights to
2287 become root:
</p
>
2289 <p
><pre
>
2290 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2291 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2293 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2295 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2296 </pre
></p
>
2298 <p
>Root access is needed to run debootstrap and mount loopback
2299 devices. See the README in the freedom-maker git repo for more
2300 details on the build. If you do not want all three images, trim the
2301 make line. Note that the virtualbox-image target is not really
2302 virtualbox specific. It create a x86 image usable in kvm, qemu,
2303 vmware and any other x86 virtual machine environment. You might need
2304 the version of vmdebootstrap in Jessie to get the build working, as it
2305 include fixes for a race condition with kpartx.
</p
>
2307 <p
>If you instead want to install using a Debian CD and the preseed
2308 method, boot a Debian Wheezy ISO and use this boot argument to load
2309 the preseed values:
</p
>
2311 <p
><pre
>
2312 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
2313 </pre
></p
>
2315 <p
>I have not tested it myself the last few weeks, so I do not know if
2316 it still work.
</p
>
2318 <p
>If you wonder how to help, one task you could look at is using
2319 systemd as the boot system. It will become the default for Linux in
2320 Jessie, so we need to make sure it is usable on the Freedombox. I did
2321 a simple test a few weeks ago, and noticed dnsmasq failed to start
2322 during boot when using systemd. I suspect there are other problems
2323 too. :) To detect problems, there is a test suite included, which can
2324 be run from the plinth web interface.
</p
>
2326 <p
>Give it a go and let us know how it goes on the mailing list, and help
2327 us get the new release published. :) Please join us on
2328 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
2329 irc.debian.org)
</a
> and
2330 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2331 mailing list
</a
> if you want to help make this vision come true.
</p
>
2336 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
2337 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
2338 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
2339 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
2340 <description><p
>For a while now, I have been looking for a sensible offsite backup
2341 solution for use at home. My requirements are simple, it must be
2342 cheap and locally encrypted (in other words, I keep the encryption
2343 keys, the storage provider do not have access to my private files).
2344 One idea me and my friends had many years ago, before the cloud
2345 storage providers showed up, was to use Google mail as storage,
2346 writing a Linux block device storing blocks as emails in the mail
2347 service provided by Google, and thus get heaps of free space. On top
2348 of this one can add encryption, RAID and volume management to have
2349 lots of (fairly slow, I admit that) cheap and encrypted storage. But
2350 I never found time to implement such system. But the last few weeks I
2351 have looked at a system called
2352 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
2353 mounted network backed file system with the features I need.
</p
>
2355 <p
>S3QL is a fuse file system with a local cache and cloud storage,
2356 handling several different storage providers, any with Amazon S3,
2357 Google Drive or OpenStack API. There are heaps of such storage
2358 providers. S3QL can also use a local directory as storage, which
2359 combined with sshfs allow for file storage on any ssh server. S3QL
2360 include support for encryption, compression, de-duplication, snapshots
2361 and immutable file systems, allowing me to mount the remote storage as
2362 a local mount point, look at and use the files as if they were local,
2363 while the content is stored in the cloud as well. This allow me to
2364 have a backup that should survive fire. The file system can not be
2365 shared between several machines at the same time, as only one can
2366 mount it at the time, but any machine with the encryption key and
2367 access to the storage service can mount it if it is unmounted.
</p
>
2369 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
2370 package is included already. So to get started, run
<tt
>apt-get
2371 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
2372 Greenqloud, after reading their nice recipe on
2373 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
2374 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
2375 in Iceland more than those in USA when it come to keeping my personal
2376 data safe and private, and thus would rather spend money on a company
2377 in Iceland. Another nice recipe is available from the article
2378 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
2379 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
2380 Admin magazine. When the provider is picked, figure out how to get
2381 the API key needed to connect to the storage API. With Greencloud,
2382 the key did not show up until I had added payment details to my
2385 <p
>Armed with the API access details, it is time to create the file
2386 system. First, create a new bucket in the cloud. This bucket is the
2387 file system storage area. I picked a bucket name reflecting the
2388 machine that was going to store data there, but any name will do.
2389 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
2390 the API login and password, and a locally created password. Store it
2391 all in ~root/.s3ql/authinfo2 like this:
2393 <p
><blockquote
><pre
>
2395 storage-url: s3c://s.greenqloud.com:
443/bucket-name
2396 backend-login: API-login
2397 backend-password: API-password
2398 fs-passphrase: local-password
2399 </pre
></blockquote
></p
>
2401 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
2402 but any sensible way to create a fairly random password should do it.
2403 Armed with these details, it is now time to run mkfs, entering the API
2404 details and password to create it:
</p
>
2406 <p
><blockquote
><pre
>
2407 # mkdir -m
700 /var/lib/s3ql-cache
2408 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2409 --ssl s3c://s.greenqloud.com:
443/bucket-name
2410 Enter backend login:
2411 Enter backend password:
2412 Before using S3QL, make sure to read the user
's guide, especially
2413 the
'Important Rules to Avoid Loosing Data
' section.
2414 Enter encryption password:
2415 Confirm encryption password:
2416 Generating random encryption key...
2417 Creating metadata tables...
2427 Compressing and uploading metadata...
2428 Wrote
0.00 MB of compressed metadata.
2429 #
</pre
></blockquote
></p
>
2431 <p
>The next step is mounting the file system to make the storage available.
2433 <p
><blockquote
><pre
>
2434 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2435 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2436 Using
4 upload threads.
2437 Downloading and decompressing metadata...
2447 Mounting filesystem...
2449 Filesystem Size Used Avail Use% Mounted on
2450 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
2452 </pre
></blockquote
></p
>
2454 <p
>The file system is now ready for use. I use rsync to store my
2455 backups in it, and as the metadata used by rsync is downloaded at
2456 mount time, no network traffic (and storage cost) is triggered by
2457 running rsync. To unmount, one should not use the normal umount
2458 command, as this will not flush the cache to the cloud storage, but
2459 instead running the umount.s3ql command like this:
2461 <p
><blockquote
><pre
>
2464 </pre
></blockquote
></p
>
2466 <p
>There is a fsck command available to check the file system and
2467 correct any problems detected. This can be used if the local server
2468 crashes while the file system is mounted, to reset the
"already
2469 mounted
" flag. This is what it look like when processing a working
2470 file system:
</p
>
2472 <p
><blockquote
><pre
>
2473 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
2474 Using cached metadata.
2475 File system seems clean, checking anyway.
2476 Checking DB integrity...
2477 Creating temporary extra indices...
2478 Checking lost+found...
2479 Checking cached objects...
2480 Checking names (refcounts)...
2481 Checking contents (names)...
2482 Checking contents (inodes)...
2483 Checking contents (parent inodes)...
2484 Checking objects (reference counts)...
2485 Checking objects (backend)...
2486 ..processed
5000 objects so far..
2487 ..processed
10000 objects so far..
2488 ..processed
15000 objects so far..
2489 Checking objects (sizes)...
2490 Checking blocks (referenced objects)...
2491 Checking blocks (refcounts)...
2492 Checking inode-block mapping (blocks)...
2493 Checking inode-block mapping (inodes)...
2494 Checking inodes (refcounts)...
2495 Checking inodes (sizes)...
2496 Checking extended attributes (names)...
2497 Checking extended attributes (inodes)...
2498 Checking symlinks (inodes)...
2499 Checking directory reachability...
2500 Checking unix conventions...
2501 Checking referential integrity...
2502 Dropping temporary indices...
2503 Backing up old metadata...
2513 Compressing and uploading metadata...
2514 Wrote
0.89 MB of compressed metadata.
2516 </pre
></blockquote
></p
>
2518 <p
>Thanks to the cache, working on files that fit in the cache is very
2519 quick, about the same speed as local file access. Uploading large
2520 amount of data is to me limited by the bandwidth out of and into my
2521 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
2522 which is very close to my upload speed, and downloading the same
2523 Debian installation ISO gave me
610 kiB/s, close to my download speed.
2524 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
2525 network, not the file system code. I do not know what a good cache
2526 size would be, but suspect that the cache should e larger than your
2527 working set.
</p
>
2529 <p
>I mentioned that only one machine can mount the file system at the
2530 time. If another machine try, it is told that the file system is
2533 <p
><blockquote
><pre
>
2534 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2535 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
2536 Using
8 upload threads.
2537 Backend reports that fs is still mounted elsewhere, aborting.
2539 </pre
></blockquote
></p
>
2541 <p
>The file content is uploaded when the cache is full, while the
2542 metadata is uploaded once every
24 hour by default. To ensure the
2543 file system content is flushed to the cloud, one can either umount the
2544 file system, or ask S3QL to flush the cache and metadata using
2547 <p
><blockquote
><pre
>
2548 # s3qlctrl upload-meta /s3ql
2549 # s3qlctrl flushcache /s3ql
2551 </pre
></blockquote
></p
>
2553 <p
>If you are curious about how much space your data uses in the
2554 cloud, and how much compression and deduplication cut down on the
2555 storage usage, you can use s3qlstat on the mounted file system to get
2558 <p
><blockquote
><pre
>
2560 Directory entries:
9141
2563 Total data size:
22049.38 MB
2564 After de-duplication:
21955.46 MB (
99.57% of total)
2565 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
2566 Database size:
2.39 MB (uncompressed)
2567 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2569 </pre
></blockquote
></p
>
2571 <p
>I mentioned earlier that there are several possible suppliers of
2572 storage. I did not try to locate them all, but am aware of at least
2573 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
2574 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
2575 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
2576 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
2577 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
2578 accept payment in Bitcoin. Pick one that suit your need. Some of
2579 them provide several GiB of free storage, but the prize models are
2580 quite different and you will have to figure out what suits you
2583 <p
>While researching this blog post, I had a look at research papers
2584 and posters discussing the S3QL file system. There are several, which
2585 told me that the file system is getting a critical check by the
2586 science community and increased my confidence in using it. One nice
2588 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
2589 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2590 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
2591 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2592 and Pamela Smith. Please have a look.
</p
>
2594 <p
>Given my problems with different file systems earlier, I decided to
2595 check out the mounted S3QL file system to see if it would be usable as
2596 a home directory (in other word, that it provided POSIX semantics when
2597 it come to locking and umask handling etc). Running
2598 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
2599 test code to check file system semantics
</a
>, I was happy to discover that
2600 no error was found. So the file system can be used for home
2601 directories, if one chooses to do so.
</p
>
2603 <p
>If you do not want a locally file system, and want something that
2604 work without the Linux fuse file system, I would like to mention the
2605 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
2606 provide locally encrypted backup using a command line client. It have
2607 a nicer access control system, where one can split out read and write
2608 access, allowing some systems to write to the backup and others to
2609 only read from it.
</p
>
2611 <p
>As usual, if you use Bitcoin and want to show your support of my
2612 activities, please send Bitcoin donations to my address
2613 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2618 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
2619 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
2620 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
2621 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
2622 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
2623 project
</a
> is working on providing the software and hardware for
2624 making it easy for non-technical people to host their data and
2625 communication at home, and being able to communicate with their
2626 friends and family encrypted and away from prying eyes. It has been
2627 going on for a while, and is slowly progressing towards a new test
2628 release (
0.2).
</p
>
2630 <p
>And what day could be better than the Pi day to announce that the
2631 new version will provide
"hard drive
" / SD card / USB stick images for
2632 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2633 system), and can also be installed using a Debian installer preseed
2634 file. The Debian based Freedombox is now based on Debian Jessie,
2635 where most of the needed packages used are already present. Only one,
2636 the freedombox-setup package, is missing. To try to build your own
2637 boot image to test the current status, fetch the freedom-maker scripts
2639 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
2640 with a user with sudo access to become root:
2643 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2645 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2646 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2648 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2651 <p
>Root access is needed to run debootstrap and mount loopback
2652 devices. See the README for more details on the build. If you do not
2653 want all three images, trim the make line. But note that thanks to
<a
2654 href=
"https://bugs.debian.org/
741407">a race condition in
2655 vmdebootstrap
</a
>, the build might fail without the patch to the
2656 kpartx call.
</p
>
2658 <p
>If you instead want to install using a Debian CD and the preseed
2659 method, boot a Debian Wheezy ISO and use this boot argument to load
2660 the preseed values:
</p
>
2663 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
2666 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
2667 recently introduced bug in apt in Jessie
</a
>, the installer will
2668 currently hang while setting up APT sources. Killing the
2669 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
2670 installation will get the installation going. This affect all
2671 installations in Jessie, and I expect it will be fixed soon.
</p
>
2673 <p
>Give it a go and let us know how it goes on the mailing list, and help
2674 us get the new release published. :) Please join us on
2675 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
2676 irc.debian.org)
</a
> and
2677 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
2678 mailing list
</a
> if you want to help make this vision come true.
</p
>
2683 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
2684 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
2685 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
2686 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
2687 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
2688 innetgr tools, because I needed them in
2689 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
2690 ng-utils, and it has served me well. I placed the project under the
2691 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
2692 repository. But many years ago, the CVS repository was dropped (lost,
2693 not migrated to new hardware, not sure), and the project have lacked a
2694 proper home since then.
</p
>
2696 <p
>Last summer, I had a look at the package and made a new release
2697 fixing a irritating crash bug, but was unable to store the changes in
2698 a proper source control system. I applied for a project on
2699 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
2700 to follow up on it. Until today. :)
</p
>
2702 <p
>After many hours of cleaning and migration, the ng-utils project
2703 now have a new home, and a git repository with the highlight of the
2704 history of the project. I published all release tarballs and imported
2705 them into the git repository. As the project is really stable and not
2706 expected to gain new features any time soon, I decided to make a new
2707 release and call it
1.0. Visit the new project home on
2708 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
2709 if you want to check it out. The new version is also uploaded into
2710 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
2715 <title>Testing sysvinit from experimental in Debian Hurd
</title>
2716 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
2717 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
2718 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
2719 <description><p
>A few days ago I decided to try to help the Hurd people to get
2720 their changes into sysvinit, to allow them to use the normal sysvinit
2721 boot system instead of their old one. This follow up on the
2722 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
2723 Google Summer of Code work
</a
> done last summer by Justus Winter to
2724 get Debian on Hurd working more like Debian on Linux. To get started,
2725 I downloaded a prebuilt hard disk image from
2726 <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
>,
2727 and started it using virt-manager.
</p
>
2729 <p
>The first think I had to do after logging in (root without any
2730 password) was to get the network operational. I followed
2731 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
2732 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
2733 commands as root to get the machine to accept a IP address from the
2734 kvm internal DHCP server:
</p
>
2736 <p
><blockquote
><pre
>
2737 settrans -fgap /dev/netdde /hurd/netdde
2738 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
2739 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
2741 </pre
></blockquote
></p
>
2743 <p
>After this, the machine had internet connectivity, and I could
2744 upgrade it and install the sysvinit packages from experimental and
2745 enable it as the default boot system in Hurd.
</p
>
2747 <p
>But before I did that, I set a password on the root user, as ssh is
2748 running on the machine it for ssh login to work a password need to be
2749 set. Also, note that a bug somewhere in openssh on Hurd block
2750 compression from working. Remember to turn that off on the client
2753 <p
>Run these commands as root to upgrade and test the new sysvinit
2756 <p
><blockquote
><pre
>
2757 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
2758 deb http://http.debian.net/debian/ experimental main
2761 apt-get dist-upgrade
2762 apt-get install -t experimental initscripts sysv-rc sysvinit \
2763 sysvinit-core sysvinit-utils
2764 update-alternatives --config runsystem
2765 </pre
></blockquote
></p
>
2767 <p
>To reboot after switching boot system, you have to use
2768 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
2769 yet a sysvinit process able to receive the signals from the normal
2770 'reboot
' command. After switching to sysvinit as the boot system,
2771 upgrading every package and rebooting, the network come up with DHCP
2772 after boot as it should, and the settrans/pkill hack mentioned at the
2773 start is no longer needed. But for some strange reason, there are no
2774 longer any login prompt in the virtual console, so I logged in using
2777 <p
>Note that there are some race conditions in Hurd making the boot
2778 fail some times. No idea what the cause is, but hope the Hurd porters
2779 figure it out. At least Justus said on IRC (#debian-hurd on
2780 irc.debian.org) that they are aware of the problem. A way to reduce
2781 the impact is to upgrade to the Hurd packages built by Justus by
2782 adding this repository to the machine:
</p
>
2784 <p
><blockquote
><pre
>
2785 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
2786 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2788 </pre
></blockquote
></p
>
2790 <p
>At the moment the prebuilt virtual machine get some packages from
2791 http://ftp.debian-ports.org/debian, because some of the packages in
2792 unstable do not yet include the required patches that are lingering in
2793 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
2795 <p
><blockquote
><pre
>
2796 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
2797 i emacs - GNU Emacs editor (metapackage)
2798 i gdb - GNU Debugger
2799 i hurd-recommended - Miscellaneous translators
2800 i isc-dhcp-client - ISC DHCP client
2801 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2802 i libc-bin - Embedded GNU C Library: Binaries
2803 i libc-dev-bin - Embedded GNU C Library: Development binaries
2804 i libc0.3 - Embedded GNU C Library: Shared libraries
2805 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2806 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2807 i multiarch-support - Transitional package to ensure multiarch compatibilit
2808 i A x11-common - X Window System (X.Org) infrastructure
2809 i xorg - X.Org X Window System
2810 i A xserver-xorg - X.Org X server
2811 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2813 </pre
></blockquote
></p
>
2815 <p
>All in all, testing hurd has been an interesting experience. :)
2816 X.org did not work out of the box and I never took the time to follow
2817 the porters instructions to fix it. This time I was interested in the
2818 command line stuff.
<p
>
2823 <title>New chrpath release
0.16</title>
2824 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
2825 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
2826 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
2827 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
2828 find problems in C, C++ and Java code using static source code
2829 analysis. It can detect a lot of different problems, and is very
2830 useful to find memory and locking bugs in the error handling part of
2831 the source. The company behind it provide
2832 <a href=
"https://scan.coverity.com/
">check of free software projects as
2833 a community service
</a
>, and many hundred free software projects are
2834 already checked. A few days ago I decided to have a closer look at
2835 the Coverity system, and discovered that the
2836 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
2837 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
2838 projects I am involved with was already registered. But these are
2839 fairly big, and I would also like to have a small and easy project to
2840 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
2841 checking of the chrpath project
</a
>. It was
2842 added to the checker and discovered seven potential defects. Six of
2843 these were real, mostly resource
"leak
" when the program detected an
2844 error. Nothing serious, as the resources would be released a fraction
2845 of a second later when the program exited because of the error, but it
2846 is nice to do it right in case the source of the program some time in
2847 the future end up in a library. Having fixed all defects and added
2848 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
2849 mailing list for the chrpath developers
</a
>, I decided it was time to
2850 publish a new release. These are the release notes:
</p
>
2852 <p
>New in
0.16 released
2014-
01-
14:
</p
>
2856 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
2857 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
2858 <li
>Mention new project mailing list in the documentation.
</li
>
2863 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
2864 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
2865 project if something is wrong with the new release. The test suite
2866 did not discover any old errors, so if you find a new one, please also
2867 include a test suite check.
</p
>
2872 <title>New chrpath release
0.15</title>
2873 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
2874 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
2875 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
2876 <description><p
>After many years break from the package and a vain hope that
2877 development would be continued by someone else, I finally pulled my
2878 acts together this morning and wrapped up a new release of chrpath,
2879 the command line tool to modify the rpath and runpath of already
2880 compiled ELF programs. The update was triggered by the persistence of
2881 Isha Vishnoi at IBM, which needed a new config.guess file to get
2882 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
2883 is working on. I checked the
2884 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
2885 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
2886 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
2887 packages for interesting patches (failed to find the source from
2888 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2889 These are the release notes:
</p
>
2891 <p
>New in
0.15 released
2013-
11-
24:
</p
>
2895 <li
>Updated config.sub and config.guess from the GNU project to work
2896 with newer architectures. Thanks to isha vishnoi for the heads
2899 <li
>Updated README with current URLs.
</li
>
2901 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2902 Matthias Klose.
</li
>
2904 <li
>Added missing help for -k|--keepgoing option, using patch by
2905 Petr Machata found in Fedora.
</li
>
2907 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
2908 .dynamic is a NULL terminated string. Based on patch found in
2909 Fedora credited Axel Thimm and Christian Krause.
</li
>
2914 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
2915 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
2916 project if something is wrong with the new release. The test suite
2917 did not discover any old errors, so if you find a new one, please also
2918 include a testsuite check.
</p
>
2923 <title>Debian init.d boot script example for rsyslog
</title>
2924 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
2925 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
2926 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
2927 <description><p
>If one of the points of switching to a new init system in Debian is
2928 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
2929 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
2930 init.d scripts at all. Here is an example init.d script, ie a rewrite
2931 of /etc/init.d/rsyslog:
</p
>
2933 <p
><pre
>
2934 #!/lib/init/init-d-script
2937 # Required-Start: $remote_fs $time
2938 # Required-Stop: umountnfs $time
2939 # X-Stop-After: sendsigs
2940 # Default-Start:
2 3 4 5
2941 # Default-Stop:
0 1 6
2942 # Short-Description: enhanced syslogd
2943 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2944 # It is quite compatible to stock sysklogd and can be
2945 # used as a drop-in replacement.
2947 DESC=
"enhanced syslogd
"
2948 DAEMON=/usr/sbin/rsyslogd
2949 </pre
></p
>
2951 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
2952 script was
137 lines, and the above is just
15 lines, most of it meta
2953 info/comments.
</p
>
2955 <p
>How to do this, you ask? Well, one create a new script
2956 /lib/init/init-d-script looking something like this:
2958 <p
><pre
>
2961 # Define LSB log_* functions.
2962 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
2963 # and status_of_proc is working.
2964 . /lib/lsb/init-functions
2967 # Function that starts the daemon/service
2973 #
0 if daemon has been started
2974 #
1 if daemon was already running
2975 #
2 if daemon could not be started
2976 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
2978 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2981 # Add code here, if necessary, that waits for the process to be ready
2982 # to handle requests from services started subsequently which depend
2983 # on this one. As a last resort, sleep for some time.
2987 # Function that stops the daemon/service
2992 #
0 if daemon has been stopped
2993 #
1 if daemon was already stopped
2994 #
2 if daemon could not be stopped
2995 # other if a failure occurred
2996 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
2997 RETVAL=
"$?
"
2998 [
"$RETVAL
" =
2 ]
&& return
2
2999 # Wait for children to finish too if this is a daemon that forks
3000 # and if the daemon is only ever run from this initscript.
3001 # If the above conditions are not satisfied then add some other code
3002 # that waits for the process to drop all resources that could be
3003 # needed by services started subsequently. A last resort is to
3004 # sleep for some time.
3005 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
3006 [
"$?
" =
2 ]
&& return
2
3007 # Many daemons don
't delete their pidfiles when they exit.
3009 return
"$RETVAL
"
3013 # Function that sends a SIGHUP to the daemon/service
3017 # If the daemon can reload its configuration without
3018 # restarting (for example, when it is sent a SIGHUP),
3019 # then implement that here.
3021 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
3026 scriptbasename=
"$(basename $
1)
"
3027 echo
"SN: $scriptbasename
"
3028 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
3029 script=
"$
1"
3036 NAME=$(basename $DAEMON)
3037 PIDFILE=/var/run/$NAME.pid
3039 # Exit if the package is not installed
3040 #[ -x
"$DAEMON
" ] || exit
0
3042 # Read configuration variable file if it is present
3043 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
3045 # Load the VERBOSE setting and other rcS variables
3048 case
"$
1" in
3050 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
3052 case
"$?
" in
3053 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3054 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3058 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
3060 case
"$?
" in
3061 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
3062 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
3066 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
3068 #reload|force-reload)
3070 # If do_reload() is not implemented then leave this commented out
3071 # and leave
'force-reload
' as an alias for
'restart
'.
3073 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
3077 restart|force-reload)
3079 # If the
"reload
" option is implemented then remove the
3080 #
'force-reload
' alias
3082 log_daemon_msg
"Restarting $DESC
" "$NAME
"
3084 case
"$?
" in
3087 case
"$?
" in
3089 1) log_end_msg
1 ;; # Old process is still running
3090 *) log_end_msg
1 ;; # Failed to start
3100 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
3106 </pre
></p
>
3108 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
3109 lot. I did not really polish the approach, so it might not always
3110 work out of the box, but you get the idea. I did not try very hard to
3111 optimize it nor make it more robust either.
</p
>
3113 <p
>A better argument for switching init system in Debian than reducing
3114 the size of init scripts (which is a good thing to do anyway), is to
3115 get boot system that is able to handle the kernel events sensibly and
3116 robustly, and do not depend on the boot to run sequentially. The boot
3117 and the kernel have not behaved sequentially in years.
</p
>
3122 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
3123 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
3124 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
3125 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
3126 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
3127 remote display access is the preferred solution with oVirt and RedHat
3128 Enterprise Virtualization, and I was sad to discover the other day
3129 that the browser plugin needed to use these systems seamlessly was
3130 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
3131 for a package
</a
> was from
2012-
04-
10 with no progress since
3132 2013-
04-
01, so I decided to wrap up a package based on the great work
3133 from Cajus Pollmeier and put it in a collab-maint maintained git
3134 repository to get a package I could use. I would very much like
3135 others to help me maintain the package (or just take over, I do not
3136 mind), but as no-one had volunteered so far, I just uploaded it to
3137 NEW. I hope it will be available in Debian in a few days.
</p
>
3139 <p
>The source is now available from
3140 <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
>
3145 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
3146 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
3147 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
3148 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
3149 <description><p
>The
3150 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
3151 program is a a very nice system to create virtual machine images. It
3152 create a image file, add a partition table, mount it and run
3153 debootstrap in the mounted directory to create a Debian system on a
3154 stick. Yesterday, I decided to try to teach it how to make images for
3155 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
3156 of a plan to simplify the build system for
3157 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
3158 project
</a
>. The FreedomBox project already uses vmdebootstrap for
3159 the virtualbox images, but its current build system made multistrap
3160 based system for Dreamplug images, and it is lacking support for
3161 Raspberry Pi.
</p
>
3163 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
3164 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
3165 code and adjusted it to be able to build armel images on my amd64
3166 Debian laptop. I ended up giving vmdebootstrap five new options,
3167 allowing me to replicate the image creation process I use to make
3168 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
3169 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
3170 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
3171 call debootstrap with --foreign and to copy the handler into the
3172 generated chroot before running the second stage. This allow
3173 vmdebootstrap to create armel images on an amd64 host. Next I added
3174 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
3175 fstype
</tt
> to teach it to create a separate /boot/ partition with the
3176 given file system type, allowing me to create an image with a vfat
3177 partition for the /boot/ stuff. I also added a
<tt
>--variant
3178 variant
</tt
> option to allow me to create smaller images without the
3179 Debian base system packages installed. Finally, I added an option
3180 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
3181 as a boot loader. It is not needed on the Raspberry Pi and probably
3182 most other non-x86 architectures. The changes were accepted by the
3183 upstream author of vmdebootstrap yesterday and today, and is now
3185 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
3186 upstream project page
</a
>.
</p
>
3188 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
3189 create a small script (the customize script) to add the non-free
3190 binary blob needed to boot the Raspberry Pi and the APT source
3193 <p
><pre
>
3195 set -e # Exit on first error
3196 rootdir=
"$
1"
3197 cd
"$rootdir
"
3198 cat
&lt;
&lt;EOF
> etc/apt/sources.list
3199 deb http://http.debian.net/debian/ jessie main contrib non-free
3201 # Install non-free binary blob needed to boot Raspberry Pi. This
3202 # install a kernel somewhere too.
3203 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
3204 -O $rootdir/usr/bin/rpi-update
3205 chmod a+x $rootdir/usr/bin/rpi-update
3206 mkdir -p $rootdir/lib/modules
3207 touch $rootdir/boot/start.elf
3208 chroot $rootdir rpi-update
3209 </pre
></p
>
3211 <p
>Next, fetch the latest vmdebootstrap script and call it like this
3212 to build the image:
</p
>
3215 sudo ./vmdebootstrap \
3218 --distribution jessie \
3219 --mirror http://http.debian.net/debian \
3228 --root-password raspberry \
3229 --hostname raspberrypi \
3230 --foreign /usr/bin/qemu-arm-static \
3231 --customize `pwd`/customize \
3233 --package git-core \
3234 --package binutils \
3235 --package ca-certificates \
3238 </pre
></p
>
3240 <p
>The list of packages being installed are the ones needed by
3241 rpi-update to make the image bootable on the Raspberry Pi, with the
3242 exception of netbase, which is needed by debootstrap to find
3243 /etc/hosts with the minbase variant. I really wish there was a way to
3244 set up an Raspberry Pi using only packages in the Debian archive, but
3245 that is not possible as far as I know, because it boots from the GPU
3246 using a non-free binary blob.
</p
>
3248 <p
>The build host need debootstrap, kpartx and qemu-user-static and
3249 probably a few others installed. I have not checked the complete
3250 build dependency list.
</p
>
3252 <p
>The resulting image will not use the hardware floating point unit
3253 on the Raspberry PI, because the armel architecture in Debian is not
3254 optimized for that use. So the images created will be a bit slower
3255 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
3260 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
3261 <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>
3262 <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>
3263 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
3264 <description><p
>The last few days I came across a few good causes that should get
3265 wider attention. I recommend signing and donating to each one of
3268 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
3269 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
3270 Women program which is a Google Summer of Code like initiative to get
3271 more women involved in free software. One debian sponsor has offered
3272 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
3273 earmarked
</a
> for this initiative. I donated a few minutes ago, and
3274 hope you will to. :)
</p
>
3276 <p
>And the Electronic Frontier Foundation just announced plans to
3277 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
3278 documentaries about the excessive spying
</a
> on every Internet user that
3279 take place these days, and their need to fund the work. I
've already
3280 donated. Are you next?
</p
>
3282 <p
>For my Norwegian audience, the organisation Studentenes og
3283 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
3284 statement under the heading
3285 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
3286 Access
</a
> for those of us asking for more focus on open access in the
3287 Norwegian government. So far
499 signatures. I hope you will sign it
3293 <title>Videos about the Freedombox project - for inspiration and learning
</title>
3294 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
3295 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
3296 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
3297 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
3298 project
</a
> have been going on for a while, and have presented the
3299 vision, ideas and solution several places. Here is a little
3300 collection of videos of talks and presentation of the project.
</p
>
3304 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
3305 2,
5 minute marketing film
</a
> (Youtube)
</li
>
3307 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
3308 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
3310 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
3311 Freedom in the Cloud - Software Freedom, Privacy and and Security for
3312 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
3313 (Youtube)
</li
>
3315 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
3316 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
3318 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
3319 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
3321 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
3322 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
3323 York City in
2012</a
> (Youtube)
</li
>
3325 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
3326 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
3327 (Youtube)
</li
>
3329 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
3330 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
3332 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
3333 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
3335 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
3336 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
3337 2013</a
> (Youtube)
</li
>
3341 <p
>A larger list is available from
3342 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
3343 Freedombox Wiki
</a
>.
</p
>
3345 <p
>On other news, I am happy to report that Freedombox based on Debian
3346 Jessie is coming along quite well, and soon both Owncloud and using
3347 Tor should be available for testers of the Freedombox solution. :) In
3348 a few weeks I hope everything needed to test it is included in Debian.
3349 The withsqlite package is already in Debian, and the plinth package is
3350 pending in NEW. The third and vital part of that puzzle is the
3351 metapackage/setup framework, which is still pending an upload. Join
3352 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
3353 (#freedombox on irc.debian.org)
</a
> and
3354 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3355 mailing list
</a
> if you want to help make this vision come true.
</p
>
3360 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
3361 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
3362 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
3363 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
3364 <description><p
>I was introduced to the
3365 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
3366 in
2010, when Eben Moglen presented his vision about serving the need
3367 of non-technical people to keep their personal information private and
3368 within the legal protection of their own homes. The idea is to give
3369 people back the power over their network and machines, and return
3370 Internet back to its intended peer-to-peer architecture. Instead of
3371 depending on a central service, the Freedombox will give everyone
3372 control over their own basic infrastructure.
</p
>
3374 <p
>I
've intended to join the effort since then, but other tasks have
3375 taken priority. But this summers nasty news about the misuse of trust
3376 and privilege exercised by the
"western
" intelligence gathering
3377 communities increased my eagerness to contribute to a point where I
3378 actually started working on the project a while back.
</p
>
3380 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
3381 Debian initiative
</a
> based on the vision from Eben Moglen, is to
3382 create a simple and cheap Debian based appliance that anyone can hook
3383 up in their home and get access to secure and private services and
3384 communication. The initial deployment platform have been the
3385 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
3386 which is a piece of hardware I do not own. So to be able to test what
3387 the current Freedombox setup look like, I had to come up with a way to install
3388 it on some hardware I do have access to. I have rewritten the
3389 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
3390 image build framework to use .deb packages instead of only copying
3391 setup into the boot images, and thanks to this rewrite I am able to
3392 set up any machine supported by Debian Wheezy as a Freedombox, using
3393 the previously mentioned deb (and a few support debs for packages
3394 missing in Debian).
</p
>
3396 <p
>The current Freedombox setup consist of a set of bootstrapping
3398 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
3399 and a administrative web interface
3400 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
3401 withsqlite), as well as a privacy enhancing proxy based on
3402 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
3403 (freedombox-privoxy). There is also a web/javascript based XMPP
3404 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
3405 trying (unsuccessfully so far) to talk to the XMPP server
3406 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
3407 web interface is pluggable, and the goal is to use it to enable OpenID
3408 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3409 this is really working yet, see
3410 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
3411 project TODO
</a
> for links to GIT repositories. Most of the code is
3412 on github at the moment. The HTTP proxy is operational out of the
3413 box, and the admin web interface can be used to add/remove plinth
3414 users. I
've not been able to do anything else with it so far, but
3415 know there are several branches spread around github and other places
3416 with lots of half baked features.
</p
>
3418 <p
>Anyway, if you want to have a look at the current state, the
3419 following recipes should work to give you a test machine to poke
3422 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
3426 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
3427 <li
>Boot from it, either as CD or USB stick.
</li
>
3428 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
3429 to the Debian installer:
<p
>
3430 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
3432 <li
>Answer the few language/region/password questions and pick disk to
3433 install on.
</li
>
3435 <li
>When the installation is finished and the machine have rebooted a
3436 few times, your Freedombox is ready for testing.
</li
>
3440 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
3444 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
3445 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
3446 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
3448 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
3449 </pre
></li
>
3450 <li
><p
>Run this as root:
</p
>
3452 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3455 apt-get install freedombox-setup
3456 /usr/lib/freedombox/setup
3457 </pre
></li
>
3458 <li
>Reboot into your freshly created Freedombox.
</li
>
3462 <p
>You can test it on other architectures too, but because the
3463 freedombox-privoxy package is binary, it will only work as intended on
3464 the architectures where I have had time to build the binary and put it
3465 in my APT repository. But do not let this stop you. It is only a
3466 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
3468 <p
>Note that by default Freedombox is a DHCP server on the
3469 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
3470 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
3471 disable
</tt
>" as root.
</p
>
3473 <p
>Please let me know if this works for you, or if you have any
3474 problems. We gather on the IRC channel
3475 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
3476 irc.debian.org and the
3477 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
3478 mailing list
</a
>.
</p
>
3480 <p
>Once you get your freedombox operational, you can visit
3481 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
3482 welcome screen (dead end - do not be surprised if you are unable to
3483 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
3484 to look at the rest of plinth. The default user is
'admin
' and the
3485 default password is
'secret
'.
</p
>
3490 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
3491 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
3492 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
3493 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
3494 <description><p
>Earlier, I reported about
3495 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
3496 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
3497 told by IBM that the original disk should be thrown away. And as
3498 there no longer was a problem if I bricked the firmware, I decided
3499 today to try to install Intel firmware to replace the Lenovo firmware
3500 currently on the disk.
</p
>
3502 <p
>I searched the Intel site for firmware, and found
3503 <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
>
3504 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3505 according to the site should contain the latest firmware for SSD
3506 disks. I inserted the broken disk in one of my spare laptops and
3507 booted the ISO from a USB stick. The disk was recognized, but the
3508 program claimed the newest firmware already were installed and refused
3509 to insert any Intel firmware. So no change, and the disk is still
3510 unable to handle write load. :( I guess the only way to get them
3511 working would be if Lenovo releases new firmware. No idea how likely
3512 that is. Anyway, just blogging about this test for completeness. I
3513 got a working Samsung disk, and see no point in spending more time on
3514 the broken disks.
</p
>
3519 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
3520 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
3521 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
3522 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
3523 <description><p
>Today I switched to
3524 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
3525 new laptop
</a
>. I
've previously written about the problems I had with
3526 my new Thinkpad X230, which was delivered with an
3527 <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
3528 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
3529 sustained writes. My hardware supplier have been very forthcoming in
3530 trying to find a solution, and after first trying with another
3531 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
3532 disk instead to fix it once and for all. The Samsung disk survived
3533 the installation of Debian with encrypted disks (filling the disk with
3534 random data during installation killed the first two), and I thus
3535 decided to trust it with my data. I have installed it as a Debian Edu
3536 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3537 server at home using Kerberos and LDAP, and will use it as my work
3538 station from now on.
</p
>
3540 <p
>As this is a solid state disk with no moving parts, I believe the
3541 Debian Wheezy default installation need to be tuned a bit to increase
3542 performance and increase life time of the disk. The Linux kernel and
3543 user space applications do not yet adjust automatically to such
3544 environment. To make it easier for my self, I created a draft Debian
3545 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
3546 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
3547 for the ssd-setup package
</a
> is available from collab-maint, and it
3548 is set up to adjust the setup of the machine by just installing the
3549 package. If there is any non-SSD disk in the machine, the package
3550 will refuse to install, as I did not try to write any logic to sort
3551 file systems in SSD and non-SSD file systems.
</p
>
3553 <p
>I consider the package a draft, as I am a bit unsure how to best
3554 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3555 where I set up the machine with one large encrypted partition (in
3556 addition to /boot), put LVM on top of this and set up partitions on
3557 top of this again. See the README file in the package source for the
3558 references I used to pick the settings. At the moment these
3559 parameters are tuned:
</p
>
3563 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
3564 (adding discard to /etc/crypttab)
</li
>
3566 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
3567 this case a cryptsetup partition) by changing issue_discards from
3568 0 to
1 in /etc/lvm/lvm.conf.
</li
>
3570 <li
>Set relatime as a file system option for ext3 and ext4 file
3573 <li
>Tell swap to use TRIM commands by adding
'discard
' to
3574 /etc/fstab.
</li
>
3576 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
3578 <li
>Run fstrim on every ext3 and ext4 file system every night (from
3579 cron.daily).
</li
>
3581 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
3582 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
3586 <p
>During installation, I cancelled the part where the installer fill
3587 the disk with random data, as this would kill the SSD performance for
3588 little gain. My goal with the encrypted file system is to ensure
3589 those stealing my laptop end up with a brick and not a working
3590 computer. I have no hope in keeping the really resourceful people
3591 from getting the data on the disk (see
3592 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
3593 Thus I concluded that adding the discard option to crypttab is the
3594 right thing to do.
</p
>
3596 <p
>I considered using the noop I/O scheduler, as several recommended
3597 it for SSD, but others recommended deadline and a benchmark I found
3598 indicated that deadline might be better for interactive use.
</p
>
3600 <p
>I also considered using the
'discard
' file system option for ext3
3601 and ext4, but read that it would give a performance hit ever time a
3602 file is removed, and thought it best to that that slowdown once a day
3603 instead of during my work.
</p
>
3605 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3606 this is already done by Debian Edu.
</p
>
3608 <p
>I have not yet started on the user space tuning. I expect
3609 iceweasel need some tuning, and perhaps other applications too, but
3610 have not yet had time to investigate those parts.
</p
>
3612 <p
>The package should work on Ubuntu too, but I have not yet tested it
3615 <p
>As for the answer to the question in the title of this blog post,
3616 as far as I know, the only solution I know about is to replace the
3617 disk. It might be possible to flash it with Intel firmware instead of
3618 the Lenovo firmware. But I have not tried and did not want to do so
3619 without approval from Lenovo as I wanted to keep the warranty on the
3620 disk until a solution was found and they wanted the broken disks
3626 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
3627 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
3628 <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>
3629 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
3630 <description><p
>A few days ago, I wrote about
3631 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
3632 problems I experienced with my new X230 and its SSD disk
</a
>, which
3633 was dying during installation because it is unable to cope with
3634 sustained write. My supplier is in contact with
3635 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
3636 replacement disk to try to fix the problem. They decided to send an
3637 identical model, so my hopes for a permanent fix was slim.
</p
>
3639 <p
>Anyway, today I got the replacement disk and tried to install
3640 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3641 same firmware version as the original. This time my hope raised
3642 slightly as the installation progressed, as the original disk used to
3643 die after
4-
7% of the disk was written to, while this time it kept
3644 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
3645 died again and I was back on square one. I still do not have a new
3646 laptop with a disk I can trust. I can not live with a disk that might
3647 lock up when I download a new
3648 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
3649 other large files. I look forward to hearing from my supplier with
3650 the next proposal from Lenovo.
</p
>
3652 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
3653 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3654 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
3655 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
3656 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
3657 P/N
45N8295, P0C38732.
</p
>
3659 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
3660 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
3661 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
3662 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
3663 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
3664 P/N
45N8295, P0C38732.
</p
>
3666 <p
>The only difference is in the first number (serial number?), ISN,
3667 SA, date and WNPP values. Mentioning all the details here in case
3668 someone is able to use the information to find a way to identify the
3669 failing disk among working ones (if any such working disk actually
3675 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
3676 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
3677 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
3678 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
3679 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
3680 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3681 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
3682 member assosiation NUUG
</a
> and
3683 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
3684 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
3685 Bitraf
</a
>.
</p
>
3687 <p
>It starts
10:
00 and continue until late evening. Everyone is
3688 welcome, and there is no fee to participate. There is on the other
3689 hand limited space, and only room for
30 people. Please put your name
3690 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
3691 wiki page
</a
> if you plan to join us.
</p
>
3696 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
3697 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
3698 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
3699 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
3700 <description><p
>Half a year ago, I reported that I had to find a
3701 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
3702 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
3703 time to spend on it, and it took a while to find a model I believe
3704 will do the job, but two days ago the replacement finally arrived. I
3706 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
3707 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3708 a roaming workstation, and it seemed to work flawlessly. But my
3709 second installation with encrypted disk was not as successful. More
3710 on that below.
</p
>
3712 <p
>I had a hard time trying to track down a good laptop, as my most
3713 important requirements (robust and with a good keyboard) are never
3714 listed in the feature list. But I did get good help from the search
3715 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
3716 allowed me to limit the list of interesting laptops based on my other
3717 requirements. A bit surprising that SSD disk are not disks according
3718 to that search interface, so I had to drop specifying the number of
3719 disks from my search parameters. I also asked around among friends to
3720 get their impression on keyboards and robustness.
</p
>
3722 <p
>So the new laptop arrived, and it is quite a lot wider than the
3723 X41. I am not quite convinced about the keyboard, as it is
3724 significantly wider than my old keyboard, and I have to stretch my
3725 hand a lot more to reach the edges. But the key response is fairly
3726 good and the individual key shape is fairly easy to handle, so I hope
3727 I will get used to it. My old X40 was starting to fail, and I really
3728 needed a new laptop now. :)
</p
>
3730 <p
>Turning off the touch pad was simple. All it took was a quick
3731 visit to the BIOS during boot it disable it.
</p
>
3733 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
3734 lock up during load. And this happen when installing Debian Wheezy
3735 with encrypted disk, while the disk is being filled with random data.
3736 I also tested to install Ubuntu Raring, and it happen there too if I
3737 reenable the code to fill the disk with random data (it is disabled by
3738 default in Ubuntu). And the bug with is already known. It was
3739 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
3740 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
3741 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3742 kernel developers as
3743 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
3744 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
3745 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3746 Lenovo forums, both for
3747 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
3748 2012-
11-
10</a
> and for
3749 <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
3750 03-
20-
2013</a
>. The problem do not only affect installation. The
3751 reports state that the disk lock up during use if many writes are done
3752 on the disk, so it is much no use to work around the installation
3753 problem and end up with a computer that can lock up at any moment.
3755 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
3756 available
</a
> that will lock up the hard drive after running a few
3757 minutes by writing to a file.
</p
>
3759 <p
>I
've contacted my supplier and asked how to handle this, and after
3760 contacting PCHELP Norway (request
01D1FDP) which handle support
3761 requests for Lenovo, his first suggestion was to upgrade the disk
3762 firmware. Unfortunately there is no newer firmware available from
3763 Lenovo, as my disk already have the most recent one (version LF1i). I
3764 hope to hear more from him today and hope the problem can be
3770 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
3771 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
3772 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
3773 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
3774 <description><p
>Half a year ago, I reported that I had to find a replacement for my
3775 trusty old Thinkpad X41. Unfortunately I did not have much time to
3776 spend on it, but today the replacement finally arrived. I ended up
3777 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
3778 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
3779 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3780 this, it is installing what I hope will be a more final installation,
3781 with a encrypted hard drive to ensure any dope head stealing it end up
3782 with an expencive door stop.
</p
>
3784 <p
>I had a hard time trying to track down a good laptop, as my most
3785 important requirements (robust and with a good keyboard) are never
3786 listed in the feature list. But I did get good help from the search
3787 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
3788 allowed me to limit the list of interesting laptops based on my other
3789 requirements. A bit surprising that SSD disk are not disks, so I had
3790 to drop number of disks from my search parameters.
</p
>
3792 <p
>I am not quite convinced about the keyboard, as it is significantly
3793 wider than my old keyboard, and I have to stretch my hand a lot more
3794 to reach the edges. But the key response is fairly good and the
3795 individual key shape is fairly easy to handle, so I hope I will get
3796 used to it. My old X40 was starting to fail, and I really needed a
3797 new laptop now. :)
</p
>
3799 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
3804 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
3805 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
3806 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
3807 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
3808 <description><p
>It annoys me when the computer fail to do automatically what it is
3809 perfectly capable of, and I have to do it manually to get things
3810 working. One such task is to find out what firmware packages are
3811 needed to get the hardware on my computer working. Most often this
3812 affect the wifi card, but some times it even affect the RAID
3813 controller or the ethernet card. Today I pushed version
0.4 of the
3814 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
3815 including a new script isenkram-autoinstall-firmware handling the
3816 process of asking all the loaded kernel modules what firmware files
3817 they want, find debian packages providing these files and install the
3818 debian packages. Here is a test run on my laptop:
</p
>
3820 <p
><pre
>
3821 # isenkram-autoinstall-firmware
3822 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3823 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3824 info: locating packages with the requested firmware files
3825 info: Updating APT sources after adding non-free APT source
3826 info: trying to install firmware-ipw2x00
3829 Preconfiguring packages ...
3830 Selecting previously deselected package firmware-ipw2x00.
3831 (Reading database ...
259727 files and directories currently installed.)
3832 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3833 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
3835 </pre
></p
>
3837 <p
>When all the requested firmware is present, a simple message is
3838 printed instead:
</p
>
3840 <p
><pre
>
3841 # isenkram-autoinstall-firmware
3842 info: did not find any firmware files requested by loaded kernel modules. exiting
3844 </pre
></p
>
3846 <p
>It could use some polish, but it is already working well and saving
3847 me some time when setting up new machines. :)
</p
>
3849 <p
>So, how does it work? It look at the set of currently loaded
3850 kernel modules, and look up each one of them using modinfo, to find
3851 the firmware files listed in the module meta-information. Next, it
3852 download the Contents file from a nearby APT mirror, and search for
3853 the firmware files in this file to locate the package with the
3854 requested firmware file. If the package is in the non-free section, a
3855 non-free APT source is added and the package is installed using
3856 <tt
>apt-get install
</tt
>. The end result is a slightly better working
3859 <p
>I hope someone find time to implement a more polished version of
3860 this script as part of the hw-detect debian-installer module, to
3861 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
3862 #
655507</a
>. There really is no need to insert USB sticks with
3863 firmware during a PXE install when the packages already are available
3864 from the nearby Debian mirror.
</p
>
3869 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
3870 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
3871 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
3872 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
3873 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3874 the screen just turn black when Linux boot, either during installation
3875 or on first boot from the hard disk. I
've seen it once in a while the
3876 last few years, but only recently understood the cause. I
've seen it
3877 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3878 The reason seem to be in the wiring of some laptops. The system to
3879 control the screen background light is inverted, so when Linux try to
3880 turn the brightness fully on, it end up turning it off instead. I do
3881 not know which Linux drivers are affected, but this post is about the
3882 i915 driver used by the
3883 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
3884 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
3886 <p
>The problem can be worked around two ways. Either by adding
3887 i915.invert_brightness=
1 as a kernel option, or by adding a file in
3888 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
3889 option when it load the i915 kernel module. On Debian and Ubuntu, it
3890 can be done by running these commands as root:
</p
>
3893 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
3894 update-initramfs -u -k all
3897 <p
>Since March
2012 there is
3898 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
3899 mechanism in the Linux kernel
</a
> to tell the i915 driver which
3900 hardware have this problem, and get the driver to invert the
3901 brightness setting automatically. To use it, one need to add a row in
3902 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
3903 intel_quirks array
</a
> in the driver source
3904 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
3905 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
3906 number (vendor number
8086 is assumed) and subdevice vendor and device
3909 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
3910 -vvnn
</tt
> for the video card in question:
</p
>
3912 <p
><pre
>
3913 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
3914 3rd Gen Core processor Graphics Controller [
8086:
0156] \
3915 (rev
09) (prog-if
00 [VGA controller])
3916 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
3917 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3918 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3919 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
3920 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
3922 Interrupt: pin A routed to IRQ
42
3923 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
3924 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
3925 Region
4: I/O ports at
4000 [size=
64]
3926 Expansion ROM at
<unassigned
> [disabled]
3927 Capabilities:
<access denied
>
3928 Kernel driver in use: i915
3929 </pre
></p
>
3931 <p
>The resulting intel_quirks entry would then look like this:
</p
>
3933 <p
><pre
>
3934 struct intel_quirk intel_quirks[] = {
3936 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3937 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
3940 </pre
></p
>
3942 <p
>According to the kernel module instructions (as seen using
3943 <tt
>modinfo i915
</tt
>), information about hardware needing the
3944 invert_brightness flag should be sent to the
3945 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
3946 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
3947 developers. But my email about the laptop sent
2013-
06-
03 have not
3949 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
3950 web archive for the mailing list
</a
>, so I suspect they do not accept
3951 emails from non-subscribers. Because of this, I sent my patch also to
3952 the Debian bug tracking system instead as
3953 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
3954 sure the patch is not lost.
</p
>
3956 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
3957 with this problem working properly with Linux. If you use Gnome, your
3958 worries should be over at this point. But if you use KDE, there is
3959 something in KDE ignoring the invert_brightness setting and turning on
3960 the screen during login. I
've reported it to Debian as
3961 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
3962 have no idea yet how to figure out exactly what subsystem is doing
3963 this. Perhaps you can help? Perhaps you know what the Gnome
3964 developers did to handle this, and this can give a clue to the KDE
3965 developers? Or you know where in KDE the screen brightness is changed
3966 during login? If so, please update the BTS report (or get in touch if
3967 you do not know how to update BTS).
</p
>
3969 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
3970 acpi_backlight=vendor, to disable ACPI backlight support completely,
3971 as the ACPI information on the machine is trash and it is better to
3972 leave it to the intel video driver to control the screen
3973 backlight.
</p
>
3978 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
3979 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
3980 <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>
3981 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
3982 <description><p
>Two days ago, I asked
3983 <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
3984 I could install Linux on a Packard Bell EasyNote LV computer
3985 preinstalled with Windows
8</a
>. I found a solution, but am horrified
3986 with the obstacles put in the way of Linux users on a laptop with UEFI
3987 and Windows
8.
</p
>
3989 <p
>I never found out if the cause of my problems were the use of UEFI
3990 secure booting or fast boot. I suspect fast boot was the problem,
3991 causing the firmware to boot directly from HD without considering any
3992 key presses and alternative devices, but do not know UEFI settings
3993 enough to tell.
</p
>
3995 <p
>There is no way to install Linux on the machine in question without
3996 opening the box and disconnecting the hard drive! This is as far as I
3997 can tell, the only way to get access to the firmware setup menu
3998 without accepting the Windows
8 license agreement. I am told (and
3999 found description on how to) that it is possible to configure the
4000 firmware setup once booted into Windows
8. But as I believe the terms
4001 of that agreement are completely unacceptable, accepting the license
4002 was never an alternative. I do not enter agreements I do not intend
4003 to follow.
</p
>
4005 <p
>I feared I had to return the laptops and ask for a refund, and
4006 waste many hours on this, but luckily there was a way to get it to
4007 work. But I would not recommend it to anyone planning to run Linux on
4008 it, and I have become sceptical to Windows
8 certified laptops. Is
4009 this the way Linux will be forced out of the market place, by making
4010 it close to impossible for
"normal
" users to install Linux without
4011 accepting the Microsoft Windows license terms? Or at least not
4012 without risking to loose the warranty?
</p
>
4014 <p
>I
've updated the
4015 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
4016 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
4017 do not have to struggle as much as I did to get Linux into the
4020 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
4021 Michael Tokarev and others for feedback and ideas.
</p
>
4026 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
4027 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
4028 <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>
4029 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
4030 <description><p
>I
've run into quite a problem the last few days. I bought three
4031 new laptops for my parents and a few others. I bought Packard Bell
4032 Easynote LV to run Kubuntu on and use as their home computer. But I
4033 am completely unable to figure out how to install Linux on it. The
4034 computer is preinstalled with Windows
8, and I suspect it uses UEFI
4035 instead of a BIOS to boot.
</p
>
4037 <p
>The problem is that I am unable to get it to PXE boot, and unable
4038 to get it to boot the Linux installer from my USB stick. I have yet
4039 to try the DVD install, and still hope it will work. when I turn on
4040 the computer, there is no information on what buttons to press to get
4041 the normal boot menu. I expect to get some boot menu to select PXE or
4042 USB stick booting. When booting, it first ask for the language to
4043 use, then for some regional settings, and finally if I will accept the
4044 Windows
8 terms of use. As these terms are completely unacceptable to
4045 me, I have no other choice but to turn off the computer and try again
4046 to get it to boot the Linux installer.
</p
>
4048 <p
>I have gathered my findings so far on a Linlap page about the
4049 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4050 EasyNote LV
</a
> model. If you have any idea how to get Linux
4051 installed on this machine, please get in touch or update that wiki
4052 page. If I can
't find a way to install Linux, I will have to return
4053 the laptop to the seller and find another machine for my parents.
</p
>
4055 <p
>I wonder, is this the way Linux will be forced out of the market
4056 using UEFI and
"secure boot
" by making it impossible to install Linux
4057 on new Laptops?
</p
>
4062 <title>How to transform a Debian based system to a Debian Edu installation
</title>
4063 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
4064 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
4065 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
4066 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
4067 an operating system based on Debian intended for use in schools. It
4068 contain a turn-key solution for the computer network provided to
4069 pupils in the primary schools. It provide both the central server,
4070 network boot servers and desktop environments with heaps of
4071 educational software. The project was founded almost
12 years ago,
4072 2001-
07-
02. If you want to support the project, which is in need for
4073 cash to fund developer gatherings and other project related activity,
4074 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
4075 donate some money
</a
>.
4077 <p
>A topic that come up again and again on the Debian Edu mailing
4078 lists and elsewhere, is the question on how to transform a Debian or
4079 Ubuntu installation into a Debian Edu installation. It isn
't very
4080 hard, and last week I wrote a script to replicate the steps done by
4081 the Debian Edu installer.
</p
>
4083 <p
>The script,
4084 <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/
>
4085 in the debian-edu-config package, will go through these six steps and
4086 transform an existing Debian Wheezy or Ubuntu (untested) installation
4087 into a Debian Edu Workstation:
</p
>
4091 <li
>Add skolelinux related APT sources.
</li
>
4092 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
4093 <li
>Install debian-edu-install to load preseeding values and pull in
4094 our configuration.
</li
>
4095 <li
>Preseed debconf database with profile setup in
4096 /etc/debian-edu/config, and run tasksel to install packages
4097 according to the profile specified in the config above,
4098 overriding some of the Debian automation machinery.
</li
>
4099 <li
>Run debian-edu-cfengine-D installation to configure everything
4100 that could not be done using preseeding.
</li
>
4101 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
4105 <p
>There are some steps in the Debian Edu installation that can not be
4106 replicated like this. Disk partitioning and LVM setup, for example.
4107 So this script just assume there is enough disk space to install all
4108 the needed packages.
</p
>
4110 <p
>The script was created to help a Debian Edu student working on
4111 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
4112 Debian Edu client, and using it he can take the existing
4113 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
4114 transform it into a fully functioning Debian Edu Workstation (or
4115 Roaming Workstation, or whatever :).
</p
>
4117 <p
>The default setting in the script is to create a KDE Workstation.
4118 If a LXDE based Roaming workstation is wanted instead, modify the
4119 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
4121 <p
><pre
>
4122 PROFILE=
"Roaming-Workstation
"
4123 DESKTOP=
"lxde
"
4124 </pre
></p
>
4126 <p
>The script could even become useful to set up Debian Edu servers in
4127 the cloud, by starting with a virtual Debian installation at some
4128 virtual hosting service and setting up all the services on first
4134 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
4135 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
4136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
4137 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
4138 <description><P
>In January,
4139 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
4140 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
4141 channel #debian-lego
</a
>, for those of us in the Debian and Linux
4142 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
4143 marvellous construction system from Denmark. We also created
4144 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
4145 a place to take notes and write down our plans and hopes. And several
4146 people showed up to help. I was very happy to see the effect of my
4147 call. Since the small start, we have a debtags tag
4148 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
4149 tag for LEGO related packages, and now count
10 packages related to
4150 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
4152 <p
><table
>
4153 <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
>
4154 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
4155 <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
>
4156 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
4157 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
4158 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
4159 <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
>
4160 <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
>
4161 <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
>
4162 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
4163 </table
></p
>
4165 <p
>Some of these are available in Wheezy, and all but one are
4166 currently available in Jessie/testing. leocad is so far only
4167 available in experimental.
</p
>
4169 <p
>If you care about LEGO in Debian, please join us on IRC and help
4170 adding the rest of the great free software tools available on Linux
4171 for LEGO designers.
</p
>
4176 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
4177 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
4178 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
4179 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
4180 <description><p
>When I woke up this morning, I was very happy to see that the
4181 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
4182 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
4183 Debian release, and I expect to move my machines at home over to it fairly
4186 <p
>The new debian release contain heaps of new stuff, and one program
4187 in particular make me very happy to see included. The
4188 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
4189 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
4190 included for the first time. Alongside similar programs like
4191 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
4192 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
4193 it allow for visual programming where syntax errors can not happen,
4194 and a friendly programming environment for learning to control the
4195 computer. Scratch will also be included in the next release of Debian
4198 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
4199 Edu/Skolelinux release too. The
4200 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
4201 alpha release
</a
> went out last week, and the next should soon
4207 <title>Isenkram
0.2 finally in the Debian archive
</title>
4208 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
4209 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
4210 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
4211 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
4212 package
</a
> finally made it into the archive, after lingering in NEW
4213 for many months. I uploaded it to the Debian experimental suite
4214 2013-
01-
27, and today it was accepted into the archive.
</p
>
4216 <p
>Isenkram is a system for suggesting to users what packages to
4217 install to work with a pluggable hardware device. The suggestion pop
4218 up when the device is plugged in. For example if a Lego Mindstorm NXT
4219 is inserted, it will suggest to install the program needed to program
4220 the NXT controller. Give it a go, and report bugs and suggestions to
4226 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
4227 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
4228 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
4229 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
4230 <description><p
>My
4231 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
4232 bitcoin related blog post
</a
> mentioned that the new
4233 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
4234 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
4235 2013-
01-
19, and have been available in unstable since then. It was
4236 automatically copied to Ubuntu, and is available in their Raring
4237 version too.
</p
>
4239 <p
>But there is a strange problem with the build that block this new
4240 version from being available on the i386 and kfreebsd-i386
4241 architectures. For some strange reason, the autobuilders in Debian
4242 for these architectures fail to run the test suite on these
4243 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
4244 We are so far unable to reproduce it when building it manually, and
4245 no-one have been able to propose a fix. If you got an idea what is
4246 failing, please let us know via the BTS.
</p
>
4248 <p
>One feature that is annoying me with of the bitcoin client, because
4249 I often run low on disk space, is the fact that the client will exit
4250 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
4251 #
696715</a
>). So make sure you have enough disk space when you run
4254 <p
>As usual, if you use bitcoin and want to show your support of my
4255 activities, please send Bitcoin donations to my address
4256 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4261 <title>Welcome to the world, Isenkram!
</title>
4262 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
4263 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
4264 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
4265 <description><p
>Yesterday, I
4266 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
4267 for testers
</a
> for my prototype for making Debian better at handling
4268 pluggable hardware devices, which I
4269 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
4270 out to create
</a
> earlier this month. Several valuable testers showed
4271 up, and caused me to really want to to open up the development to more
4272 people. But before I did this, I want to come up with a sensible name
4273 for this project. Today I finally decided on a new name, and I have
4274 renamed the project from hw-support-handler to this new name. In the
4275 process, I moved the source to git and made it available as a
4276 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
4277 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
4278 To fetch and build the latest version of the source, use
</p
>
4281 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
4282 cd isenkram
&& git-buildpackage -us -uc
4285 <p
>I have not yet adjusted all files to use the new name yet. If you
4286 want to hack on the source or improve the package, please go ahead.
4287 But please talk to me first on IRC or via email before you do major
4288 changes, to make sure we do not step on each others toes. :)
</p
>
4290 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
4291 stuff, typically meaning tools, nails, screws, etc. Typical hardware
4292 stuff, in other words. I
've been told it is the Norwegian variant of
4293 the German word eisenkram, for those that are familiar with that
4296 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
4297 instructions, to avoid confusing people with an error from the signing
4300 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
4301 clone argument to avoid the need for authentication.
</p
>
4306 <title>First prototype ready making hardware easier to use in Debian
</title>
4307 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
4308 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
4309 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
4310 <description><p
>Early this month I set out to try to
4311 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
4312 the Debian support for pluggable hardware devices
</a
>. Now my
4313 prototype is working, and it is ready for a larger audience. To test
4315 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
4316 from the Debian Edu subversion repository
</a
>, build and install the
4317 package. You might have to log out and in again activate the
4318 autostart script.
</p
>
4320 <p
>The design is simple:
</p
>
4324 <li
>Add desktop entry in /usr/share/autostart/ causing a program
4325 hw-support-handlerd to start when the user log in.
</li
>
4327 <li
>This program listen for kernel events about new hardware (directly
4328 from the kernel like udev does), not using HAL dbus events as I
4329 initially did.
</li
>
4331 <li
>When new hardware is inserted, look up the hardware modalias in
4332 the APT database, a database
4333 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
4334 via HTTP
</a
> and a database available as part of the package.
</li
>
4336 <li
>If a package is mapped to the hardware in question, the package
4337 isn
't installed yet and this is the first time the hardware was
4338 plugged in, show a desktop notification suggesting to install the
4339 package or packages.
</li
>
4341 <li
>If the user click on the
'install package now
' button, ask
4342 aptdaemon via the PackageKit API to install the requrired package.
</li
>
4344 <li
>aptdaemon ask for root password or sudo password, and install the
4345 package while showing progress information in a window.
</li
>
4349 <p
>I still need to come up with a better name for the system. Here
4350 are some screen shots showing the prototype in action. First the
4351 notification, then the password request, and finally the request to
4352 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
4354 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
4355 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
4356 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
4357 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
4358 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
4360 <p
>The prototype still need to be improved with longer timeouts, but
4361 is already useful. The database of hardware to package mappings also
4362 need more work. It is currently compatible with the Ubuntu way of
4363 storing such information in the package control file, but could be
4364 changed to use other formats instead or in addition to the current
4365 method. I
've dropped the use of discover for this mapping, as the
4366 modalias approach is more flexible and easier to use on Linux as long
4367 as the Linux kernel expose its modalias strings directly.
</p
>
4369 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
4370 here is the command required to check out and build the source: Use
4371 '<tt
>svn checkout
4372 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
4373 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
4374 devscripts package.
</p
>
4376 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
4377 renamed to Isenkram and the source moved from the Debian Edu
4378 subversion repository to a Debian collab-maint git repository. See
4379 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
4380 instructions
</a
> for details.
</p
>
4385 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
4386 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
4387 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
4388 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
4389 <description><p
>This Christmas my trusty old laptop died. It died quietly and
4390 suddenly in bed. With a quiet whimper, it went completely quiet and
4391 black. The power button was no longer able to turn it on. It was a
4392 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4393 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4394 Compaq I had before that. Now I need to find a replacement. To keep
4395 going during Christmas, I moved the one year old SSD disk to my old
4396 X40 where it fitted (only one I had left that could use it), but it is
4397 not a durable solution.
4399 <p
>My laptop needs are fairly modest. This is my wishlist from when I
4400 got a new one more than
10 years ago. It still holds true.:)
</p
>
4404 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
4405 than A4).
</li
>
4406 <li
>Robust, it will be in my backpack every day.
</li
>
4407 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
4408 <li
>Long battery life time. Preferable a week.
</li
>
4409 <li
>Internal WIFI network card.
</li
>
4410 <li
>Internal Twisted Pair network card.
</li
>
4411 <li
>Some USB slots (
2-
3 is plenty)
</li
>
4412 <li
>Good keyboard - similar to the Thinkpad.
</li
>
4413 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
4415 <li
>Hardware supported by Debian Stable, ie the default kernel and
4416 X.org packages.
</li
>
4417 <li
>Quiet, preferably fan free (or at least not using the fan most of
4422 <p
>You will notice that there are no RAM and CPU requirements in the
4423 list. The reason is simply that the specifications on laptops the
4424 last
10-
15 years have been sufficient for my needs, and I have to look
4425 at other features to choose my laptop. But are there still made as
4426 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4427 robust, and Thinkpads seem to be heading in the wrong direction since
4428 Lenovo took over. But I
've been told that X220 and X1 Carbon might
4429 still be useful.
</p
>
4431 <p
>Perhaps I should rethink my needs, and look for a pad with an
4432 external keyboard? I
'll have to check the
4433 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
4434 well-supported laptops, or perhaps just buy one preinstalled from one
4435 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
4436 Pre-loaded site
</a
>.
</p
>
4441 <title>How to find a browser plugin supporting a given MIME type
</title>
4442 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
4443 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
4444 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
4445 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
4446 install to get support for a given MIME type. Thanks to
4447 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
4448 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
4449 Unfortunately, not very many packages provide the needed meta
4450 information, Anyway, here is a small script to look up all browser
4451 plugin packages announcing ther MIME support using this specification:
</p
>
4457 def pkgs_handling_mimetype(mimetype):
4462 version = pkg.candidate
4464 version = pkg.installed
4467 record = version.record
4468 if not record.has_key(
'Npp-MimeType
'):
4470 mime_types = record[
'Npp-MimeType
'].split(
',
')
4471 for t in mime_types:
4472 t = t.rstrip().strip()
4474 thepkgs.append(pkg.name)
4476 mimetype =
"audio/ogg
"
4477 if
1 < len(sys.argv):
4478 mimetype = sys.argv[
1]
4479 print
"Browser plugin packages supporting %s:
" % mimetype
4480 for pkg in pkgs_handling_mimetype(mimetype):
4481 print
" %s
" %pkg
4484 <p
>It can be used like this to look up a given MIME type:
</p
>
4487 % ./apt-find-browserplug-for-mimetype
4488 Browser plugin packages supporting audio/ogg:
4490 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4491 Browser plugin packages supporting application/x-shockwave-flash:
4492 browser-plugin-gnash
4496 <p
>In Ubuntu this mechanism is combined with support in the browser
4497 itself to query for plugins and propose to install the needed
4498 packages. It would be great if Debian supported such feature too. Is
4499 anyone working on adding it?
</p
>
4501 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
4502 request for icweasel support for this feature is
4503 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
4504 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
4505 of manpower and wish for a different design is the reason thus feature
4506 is not yet in iceweasel from Debian.
</p
>
4511 <title>What is the most supported MIME type in Debian?
</title>
4512 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
4513 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
4514 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
4515 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
4516 proposal to add AppStream information to the Debian archive
</a
>, is a
4517 proposal to make it possible for a Desktop application to propose to
4518 the user some package to install to gain support for a given MIME
4519 type, font, library etc. that is currently missing. With such
4520 mechanism in place, it would be possible for the desktop to
4521 automatically propose and install leocad if some LDraw file is
4522 downloaded by the browser.
</p
>
4524 <p
>To get some idea about the current content of the archive, I decided
4525 to write a simple program to extract all .desktop files from the
4526 Debian archive and look up the claimed MIME support there. The result
4528 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
4529 site
</a
>. Using the collected information, it become possible to
4530 answer the question in the title. Here are the
20 most supported MIME
4531 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4532 The complete list is available from the link above.
</p
>
4534 <p
><strong
>Debian Stable:
</strong
></p
>
4538 ----- -----------------------
4554 18 application/x-ogg
4561 <p
><strong
>Debian Testing:
</strong
></p
>
4565 ----- -----------------------
4581 18 application/x-ogg
4588 <p
><strong
>Debian Unstable:
</strong
></p
>
4592 ----- -----------------------
4609 18 application/x-ogg
4615 <p
>I am told that PackageKit can provide an API to access the kind of
4616 information mentioned in DEP-
11. I have not yet had time to look at
4617 it, but hope the PackageKit people in Debian are on top of these
4620 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
4621 discovering a typo in my script.
</p
>
4626 <title>Using modalias info to find packages handling my hardware
</title>
4627 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
4628 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
4629 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
4630 <description><p
>Yesterday, I wrote about the
4631 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
4632 values provided by the Linux kernel
</a
> following my hope for
4633 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
4634 dongle support in Debian
</a
>. Using this knowledge, I have tested how
4635 modalias values attached to package names can be used to map packages
4636 to hardware. This allow the system to look up and suggest relevant
4637 packages when I plug in some new hardware into my machine, and replace
4638 discover and discover-data as the database used to map hardware to
4641 <p
>I create a modaliases file with entries like the following,
4642 containing package name, kernel module name (if relevant, otherwise
4643 the package name) and globs matching the relevant hardware
4646 <p
><blockquote
>
4647 Package: package-name
4648 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
4649 </blockquote
></p
>
4651 <p
>It is fairly trivial to write code to find the relevant packages
4652 for a given modalias value using this file.
</p
>
4654 <p
>An entry like this would suggest the video and picture application
4655 cheese for many USB web cameras (interface bus class
0E01):
</p
>
4657 <p
><blockquote
>
4659 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
4660 </blockquote
></p
>
4662 <p
>An entry like this would suggest the pcmciautils package when a
4663 CardBus bridge (bus class
0607) PCI device is present:
</p
>
4665 <p
><blockquote
>
4666 Package: pcmciautils
4667 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4668 </blockquote
></p
>
4670 <p
>An entry like this would suggest the package colorhug-client when
4671 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
4673 <p
><blockquote
>
4674 Package: colorhug-client
4675 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
4676 </blockquote
></p
>
4678 <p
>I believe the format is compatible with the format of the Packages
4679 file in the Debian archive. Ubuntu already uses their Packages file
4680 to store their mappings from packages to hardware.
</p
>
4682 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
4683 announce the hardware it support in a way my prototype understand.
4684 This allow those publishing packages in an APT source outside the
4685 Debian archive as well as those backporting packages to make sure the
4686 hardware mapping are included in the package meta information. I
've
4687 tested such header in the pymissile package, and its modalias mapping
4688 is working as it should with my prototype. It even made it to Ubuntu
4691 <p
>To test if it was possible to look up supported hardware using only
4692 the shell tools available in the Debian installer, I wrote a shell
4693 implementation of the lookup code. The idea is to create files for
4694 each modalias and let the shell do the matching. Please check out and
4696 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
4697 shell script. It run without any extra dependencies and fetch the
4698 hardware mappings from the Debian archive and the subversion
4699 repository where I currently work on my prototype.
</p
>
4701 <p
>When I use it on a machine with a yubikey inserted, it suggest to
4702 install yubikey-personalization:
</p
>
4704 <p
><blockquote
>
4705 % ./hw-support-lookup
4706 <br
>yubikey-personalization
4708 </blockquote
></p
>
4710 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4711 propose to install the pcmciautils package:
</p
>
4713 <p
><blockquote
>
4714 % ./hw-support-lookup
4715 <br
>pcmciautils
4717 </blockquote
></p
>
4719 <p
>If you know of any hardware-package mapping that should be added to
4720 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
4721 database
</a
>, please tell me about it.
</p
>
4723 <p
>It could be possible to generate several of the mappings between
4724 packages and hardware. One source would be to look at packages with
4725 kernel modules, ie packages with *.ko files in /lib/modules/, and
4726 extract their modalias information. Another would be to look at
4727 packages with udev rules, ie packages with files in
4728 /lib/udev/rules.d/, and extract their vendor/model information to
4729 generate a modalias matching rule. I have not tested any of these to
4730 see if it work.
</p
>
4732 <p
>If you want to help implementing a system to let us propose what
4733 packages to install when new hardware is plugged into a Debian
4734 machine, please send me an email or talk to me on
4735 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
4740 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
4741 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
4742 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
4743 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
4744 <description><p
>While looking into how to look up Debian packages based on hardware
4745 information, to find the packages that support a given piece of
4746 hardware, I refreshed my memory regarding modalias values, and decided
4747 to document the details. Here are my findings so far, also available
4749 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
4750 Debian Edu subversion repository
</a
>:
4752 <p
><strong
>Modalias decoded
</strong
></p
>
4754 <p
>This document try to explain what the different types of modalias
4755 values stands for. It is in part based on information from
4756 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
4757 &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;,
4758 &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
4759 &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;.
4761 <p
>The modalias entries for a given Linux machine can be found using
4762 this shell script:
</p
>
4765 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
4768 <p
>The supported modalias globs for a given kernel module can be found
4769 using modinfo:
</p
>
4772 % /sbin/modinfo psmouse | grep alias:
4773 alias: serio:ty05pr*id*ex*
4774 alias: serio:ty01pr*id*ex*
4778 <p
><strong
>PCI subtype
</strong
></p
>
4780 <p
>A typical PCI entry can look like this. This is an Intel Host
4781 Bridge memory controller:
</p
>
4783 <p
><blockquote
>
4784 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4785 </blockquote
></p
>
4787 <p
>This represent these values:
</p
>
4792 sv
00001028 (subvendor)
4793 sd
000001AD (subdevice)
4795 sc
00 (bus subclass)
4799 <p
>The vendor/device values are the same values outputted from
'lspci
4800 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
4801 0600. The
0600 class is a host bridge. Other useful bus values are
4802 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
4804 <p
>Not sure how to figure out the interface value, nor what it
4807 <p
><strong
>USB subtype
</strong
></p
>
4809 <p
>Some typical USB entries can look like this. This is an internal
4810 USB hub in a laptop:
</p
>
4812 <p
><blockquote
>
4813 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4814 </blockquote
></p
>
4816 <p
>Here is the values included in this alias:
</p
>
4819 v
1D6B (device vendor)
4820 p
0001 (device product)
4822 dc
09 (device class)
4823 dsc
00 (device subclass)
4824 dp
00 (device protocol)
4825 ic
09 (interface class)
4826 isc
00 (interface subclass)
4827 ip
00 (interface protocol)
4830 <p
>The
0900 device class/subclass means hub. Some times the relevant
4831 class is in the interface class section. For a simple USB web camera,
4832 these alias entries show up:
</p
>
4834 <p
><blockquote
>
4835 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4836 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4837 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4838 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4839 </blockquote
></p
>
4841 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
4842 camera),
0101 is audio control device and
0102 is audio streaming (aka
4843 microphone). Thus this is a camera with microphone included.
</p
>
4845 <p
><strong
>ACPI subtype
</strong
></p
>
4847 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
4848 receiver in a Thinkpad X40:
</p
>
4850 <p
><blockquote
>
4851 acpi:IBM0071:PNP0511:
4852 </blockquote
></p
>
4854 <p
>The values between the colons are IDs.
</p
>
4856 <p
><strong
>DMI subtype
</strong
></p
>
4858 <p
>The DMI table contain lots of information about the computer case
4859 and model. This is an entry for a IBM Thinkpad X40, fetched from
4860 /sys/devices/virtual/dmi/id/modalias:
</p
>
4862 <p
><blockquote
>
4863 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4864 </blockquote
></p
>
4866 <p
>The values present are
</p
>
4869 bvn IBM (BIOS vendor)
4870 bvr
1UETB
6WW(
1.66) (BIOS version)
4871 bd
06/
15/
2005 (BIOS date)
4872 svn IBM (system vendor)
4873 pn
2371H4G (product name)
4874 pvr ThinkPadX40 (product version)
4875 rvn IBM (board vendor)
4876 rn
2371H4G (board name)
4877 rvr NotAvailable (board version)
4878 cvn IBM (chassis vendor)
4879 ct
10 (chassis type)
4880 cvr NotAvailable (chassis version)
4883 <p
>The chassis type
10 is Notebook. Other interesting values can be
4884 found in the dmidecode source:
</p
>
4888 4 Low Profile Desktop
4901 17 Main Server Chassis
4902 18 Expansion Chassis
4904 20 Bus Expansion Chassis
4905 21 Peripheral Chassis
4907 23 Rack Mount Chassis
4916 <p
>The chassis type values are not always accurately set in the DMI
4917 table. For example my home server is a tower, but the DMI modalias
4918 claim it is a desktop.
</p
>
4920 <p
><strong
>SerIO subtype
</strong
></p
>
4922 <p
>This type is used for PS/
2 mouse plugs. One example is from my
4923 test machine:
</p
>
4925 <p
><blockquote
>
4926 serio:ty01pr00id00ex00
4927 </blockquote
></p
>
4929 <p
>The values present are
</p
>
4938 <p
>This type is supported by the psmouse driver. I am not sure what
4939 the valid values are.
</p
>
4941 <p
><strong
>Other subtypes
</strong
></p
>
4943 <p
>There are heaps of other modalias subtypes according to
4944 file2alias.c. There is the rest of the list from that source: amba,
4945 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4946 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4947 vmbus, x86cpu and zorro. I did not spend time documenting all of
4948 these, as they do not seem relevant for my intended use with mapping
4949 hardware to packages when new stuff is inserted during run time.
</p
>
4951 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
4953 <p
>To check which kernel modules provide support for a given modalias,
4954 one can use the following shell script:
</p
>
4957 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
4958 echo
"$id
" ; \
4959 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
4963 <p
>The output can look like this (only the first few entries as the
4964 list is very long on my test machine):
</p
>
4968 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
4970 FATAL: Module acpi:device: not found.
4972 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
4973 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
4974 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
4975 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4976 acpi:IBM0071:PNP0511:
4977 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
4978 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
4979 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
4983 <p
>If you want to help implementing a system to let us propose what
4984 packages to install when new hardware is plugged into a Debian
4985 machine, please send me an email or talk to me on
4986 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
4988 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
4989 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
4990 in /sys/ with space in them.
</p
>
4995 <title>Moved the pymissile Debian packaging to collab-maint
</title>
4996 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
4997 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
4998 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
4999 <description><p
>As part of my investigation on how to improve the support in Debian
5000 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
5001 Launcher and updated the Debian package
5002 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
5003 sure udev will fix the device permissions when it is plugged in. I
5004 also added a
"Modaliases
" header to test it in the Debian archive and
5005 hopefully make the package be proposed by jockey in Ubuntu when a user
5006 plug in his rocket launcher. In the process I moved the source to a
5007 git repository under collab-maint, to make it easier for any DD to
5008 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
5009 is not very active, but the software still work for me even after five
5010 years of relative silence. The new git repository is not listed in
5011 the uploaded package yet, because I want to test the other changes a
5012 bit more before I upload the new version. If you want to check out
5013 the new version with a .desktop file included, visit the
5014 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
5015 view
</a
> or use
"<tt
>git clone
5016 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
5021 <title>Lets make hardware dongles easier to use in Debian
</title>
5022 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
5023 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
5024 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
5025 <description><p
>One thing that annoys me with Debian and Linux distributions in
5026 general, is that there is a great package management system with the
5027 ability to automatically install software packages by downloading them
5028 from the distribution mirrors, but no way to get it to automatically
5029 install the packages I need to use the hardware I plug into my
5030 machine. Even if the package to use it is easily available from the
5031 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
5032 suggest to automatically install the python-nxt, nbc and t2n packages
5033 I need to talk to it. When I plug in a Yubikey, it could propose the
5034 yubikey-personalization package. The information required to do this
5035 is available, but no-one have pulled all the pieces together.
</p
>
5037 <p
>Some years ago, I proposed to
5038 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
5039 the discover subsystem to implement this
</a
>. The idea is fairly
5044 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
5045 starting when a user log in.
</li
>
5047 <li
>Set this program up to listen for kernel events emitted when new
5048 hardware is inserted into the computer.
</li
>
5050 <li
>When new hardware is inserted, look up the hardware ID in a
5051 database mapping to packages, and take note of any non-installed
5052 packages.
</li
>
5054 <li
>Show a message to the user proposing to install the discovered
5055 package, and make it easy to install it.
</li
>
5059 <p
>I am not sure what the best way to implement this is, but my
5060 initial idea was to use dbus events to discover new hardware, the
5061 discover database to find packages and
5062 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
5065 <p
>Yesterday, I found time to try to implement this idea, and the
5066 draft package is now checked into
5067 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5068 Debian Edu subversion repository
</a
>. In the process, I updated the
5069 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
5070 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
5071 the relevant packages in Debian, and uploaded a new version
5072 2.2013.01.09 to unstable. I also discovered that the current
5073 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
5074 package in Debian no longer discovered any USB devices, because
5075 /proc/bus/usb/devices is no longer present. I ported it to use
5076 libusb as a fall back option to get it working. The fixed package
5077 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
5078 because of the freeze).
</p
>
5080 <p
>With this prototype in place, I can insert my Yubikey, and get this
5081 desktop notification to show up (only once, the first time it is
5082 inserted):
</p
>
5084 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
5086 <p
>For this prototype to be really useful, some way to automatically
5087 install the proposed packages by pressing the
"Please install
5088 program(s)
" button should to be implemented.
</p
>
5090 <p
>If this idea seem useful to you, and you want to help make it
5091 happen, please help me update the discover-data database with mappings
5092 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
5093 list the package you would like to have installed when a given
5094 hardware device is inserted into your computer, and report bugs using
5095 reportbug if it isn
't. Or, if you know of a better way to provide
5096 such mapping, please let me know.
</p
>
5098 <p
>This prototype need more work, and there are several questions that
5099 should be considered before it is ready for production use. Is dbus
5100 the correct way to detect new hardware? At the moment I look for HAL
5101 dbus events on the system bus, because that is the events I could see
5102 on my Debian Squeeze KDE desktop. Are there better events to use?
5103 How should the user be notified? Is the desktop notification
5104 mechanism the best option, or should the background daemon raise a
5105 popup instead? How should packages be installed? When should they
5106 not be installed?
</p
>
5108 <p
>If you want to help getting such feature implemented in Debian,
5109 please send me an email. :)
</p
>
5114 <title>New IRC channel for LEGO designers using Debian
</title>
5115 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
5116 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
5117 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
5118 <description><p
>During Christmas, I have worked a bit on the Debian support for
5119 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
5120 NXT
</a
>. My son and I have played a bit with my NXT set, and I
5121 discovered I had to build all the tools myself because none were
5122 already in Debian Squeeze. If Debian support for LEGO is something
5123 you care about, please join me on the IRC channel
5124 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
5125 irc.debian.org). There is a lot that could be done to improve the
5126 Debian support for LEGO designers. For example both CAD software
5127 and Mindstorm compilers are missing. :)
</p
>
5129 <p
>Update
2012-
01-
03: A
5130 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
5131 including links to Lego related packages is now available.
</p
>
5136 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
5137 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
5138 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
5139 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
5140 <description><p
>Let me start by wishing you all marry Christmas and a happy new
5141 year! I hope next year will prove to be a good year.
</p
>
5143 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
5144 decentralised
"currency
" that allow people to transfer bitcoins
5145 between each other with minimal overhead, is a very interesting
5146 experiment. And as I wrote a few days ago, the bitcoin situation in
5147 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
5148 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
5149 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
5150 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
5151 for one of the ftpmasters to approve the new bitcoin-qt package
5154 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
5155 team in Debian, you can easily test the package in Debian Squeeze
5156 using the following steps to get a set of working packages:
</p
>
5158 <blockquote
><pre
>
5159 git clone git://git.debian.org/git/collab-maint/bitcoin
5161 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
5162 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
5163 </pre
></blockquote
>
5165 <p
>You might have to install some build dependencies as well. The
5166 list of commands should give you two packages, bitcoind and
5167 bitcoin-qt, ready for use in a Squeeze environment. Note that the
5168 client will download the complete set of bitcoin
"blocks
", which need
5169 around
5.6 GiB of data on my machine at the moment. Make sure your
5170 ~/.bitcoin/ directory have lots of spare room if you want to download
5171 all the blocks. The client will warn if the disk is getting full, so
5172 there is not really a problem if you got too little room, but you will
5173 not be able to get all the features out of the client.
</p
>
5175 <p
>As usual, if you use bitcoin and want to show your support of my
5176 activities, please send Bitcoin donations to my address
5177 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5182 <title>A word on bitcoin support in Debian
</title>
5183 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
5184 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
5185 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
5186 <description><p
>It has been a while since I wrote about
5187 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
5188 peer-to-peer based crypto-currency, and the reason is simply that I
5189 have been busy elsewhere. But two days ago, I started looking at the
5190 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
5191 Debian
</a
> again to try to recover my old bitcoin wallet. The package
5192 is now maintained by a
5193 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
5194 people
</a
>, and the grunt work had already been done by this team. We
5195 owe a huge thank you to all these team members. :)
5196 But I was sad to discover that the bitcoin client is missing in
5197 Wheezy. It is only available in Sid (and an outdated client from
5198 backports). The client had several RC bugs registered in BTS blocking
5199 it from entering testing. To try to help the team and improve the
5200 situation, I spent some time providing patches and triaging the bug
5201 reports. I also had a look at the bitcoin package available from Matt
5203 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
5204 Ubuntu
</a
>, and moved the useful pieces from that version into the
5205 Debian package.
</p
>
5207 <p
>After checking with the main package maintainer Jonas Smedegaard on
5208 IRC, I pushed several patches into the collab-maint git repository to
5209 improve the package. It now contains fixes for the RC issues (not from
5210 me, but fixed by Scott Howard), build rules for a Qt GUI client
5211 package, konqueror support for the bitcoin: URI and bash completion
5212 setup. As I work on Debian Squeeze, I also created
5213 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
5214 patch to backport
</a
> the latest version. Jonas is going to look at
5215 it and try to integrate it into the git repository before uploading a
5216 new version to unstable.
5218 <p
>I would very much like bitcoin to succeed, to get rid of the
5219 centralized control currently exercised in the monetary system. I
5220 find it completely unacceptable that the USA government is collecting
5221 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
5222 that the major credit card companies can block legal money
5223 transactions to Wikileaks. But for bitcoin to succeed, more people
5224 need to use bitcoins, and more people need to accept bitcoins when
5225 they sell products and services. Improving the bitcoin support in
5226 Debian is a small step in the right direction, but not enough.
5227 Unfortunately the user experience when browsing the web and wanting to
5228 pay with bitcoin is still not very good. The bitcoin: URI is a step
5229 in the right direction, but need to work in most or every browser in
5230 use. Also the bitcoin-qt client is too heavy to fire up to do a
5231 quick transaction. I believe there are other clients available, but
5232 have not tested them.
</p
>
5235 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
5236 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
5237 I received
20.15 BTC so far on the address I provided in my blog two
5238 years ago, as can be
5239 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
5240 on the blockexplorer service
</a
>. Thank you everyone for your
5241 donation. The blockexplorer service demonstrates quite well that
5242 bitcoin is not quite anonymous and untracked. :) I wonder if the
5243 number of users have gone up since then. If you use bitcoin and want
5244 to show your support of my activity, please send Bitcoin donations to
5245 the same address as last time,
5246 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5251 <title>Git repository for song book for Computer Scientists
</title>
5252 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
5253 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
5254 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
5255 <description><p
>As I
5256 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
5257 this summer
</a
>, I have created a Computer Science song book a few
5258 years ago, and today I finally found time to create a public
5259 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
5260 repository for the project
</a
>.
</p
>
5262 <p
>If you want to help out, please clone the source and submit patches
5263 to the HTML version. To generate the PDF and PostScript version,
5264 please use prince XML, or let me know about a useful free software
5265 processor capable of creating a good looking PDF from the HTML.
</p
>
5267 <p
>Want to sing? You can still find the song book in HTML, PDF and
5268 PostScript formats at
5269 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
5270 Science Songbook
</a
>.
</p
>
5275 <title>Gratulerer med
19-årsdagen, Debian!
</title>
5276 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
5277 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
5278 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
5279 <description><p
>I dag fyller
5280 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
5281 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
5282 si gratulerer med dagen, Debian!
</p
>
5287 <title>Song book for Computer Scientists
</title>
5288 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
5289 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
5290 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
5291 <description><p
>Many years ago, while studying Computer Science at the
5292 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
5293 collecting computer related songs for use at parties. The original
5294 version was written in LaTeX, but a few years ago I got help from
5295 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
5296 while keeping the ability to create a nice book in PDF format. I have
5297 not had time to maintain the book for a while now, and guess I should
5298 put it up on some public version control repository where others can
5299 help me extend and update the book. If anyone is volunteering to help
5300 me with this, send me an email. Also let me know if there are songs
5301 missing in my book.
</p
>
5303 <p
>I have not mentioned the book on my blog so far, and it occured to
5304 me today that I really should let all my readers share the joys of
5305 singing out load about programming, computers and computer networks.
5306 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
5307 12</a
> is about to start (and I am not going). Want to sing? Check
5308 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
5309 Computer Science Songbook
</a
>.
5314 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
5315 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
5316 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
5317 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
5318 <description><p
>At work we have heaps of servers. I believe the total count is
5319 around
1000 at the moment. To be able to get help from the vendors
5320 when something go wrong, we want to keep the firmware on the servers
5321 up to date. If the firmware isn
't the latest and greatest, the
5322 vendors typically refuse to start debugging any problems until the
5323 firmware is upgraded. So before every reboot, we want to upgrade the
5324 firmware, and we would really like everyone handling servers at the
5325 university to do this themselves when they plan to reboot a machine.
5326 For that to happen we at the unix server admin group need to provide
5327 the tools to do so.
</p
>
5329 <p
>To make firmware upgrading easier, I am working on a script to
5330 fetch and install the latest firmware for the servers we got. Most of
5331 our hardware are from Dell and HP, so I have focused on these servers
5332 so far. This blog post is about the Dell part.
</P
>
5334 <p
>On the Dell FTP site I was lucky enough to find
5335 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
5336 with firmware information for all
11th generation servers, listing
5337 which firmware should be used on a given model and where on the FTP
5338 site I can find it. Using a simple perl XML parser I can then
5339 download the shell scripts Dell provides to do firmware upgrades from
5340 within Linux and reboot when all the firmware is primed and ready to
5341 be activated on the first reboot.
</p
>
5343 <p
>This is the Dell related fragment of the perl code I am working on.
5344 Are there anyone working on similar tools for firmware upgrading all
5345 servers at a site? Please get in touch and lets share resources.
</p
>
5347 <p
><pre
>
5351 use File::Temp qw(tempdir);
5353 # Install needed RHEL packages if missing
5355 'XML::Simple
' =
> 'perl-XML-Simple
',
5357 for my $module (keys %rhelmodules) {
5358 eval
"use $module;
";
5360 my $pkg = $rhelmodules{$module};
5361 system(
"yum install -y $pkg
");
5362 eval
"use $module;
";
5366 my $errorsto =
'pere@hungry.com
';
5372 sub run_firmware_script {
5373 my ($opts, $script) = @_;
5375 print STDERR
"fail: missing script name\n
";
5378 print STDERR
"Running $script\n\n
";
5380 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
5381 print STDERR
"success: firmware script ran succcessfully\n
";
5383 print STDERR
"fail: firmware script returned error\n
";
5387 sub run_firmware_scripts {
5388 my ($opts, @dirs) = @_;
5389 # Run firmware packages
5390 for my $dir (@dirs) {
5391 print STDERR
"info: Running scripts in $dir\n
";
5392 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
5393 while (my $s = readdir $dh) {
5394 next if $s =~ m/^\.\.?/;
5395 run_firmware_script($opts,
"$dir/$s
");
5403 print STDERR
"info: Downloading $url\n
";
5404 system(
"wget --quiet \
"$url\
"");
5409 my $product = `dmidecode -s system-product-name`;
5412 if ($product =~ m/PowerEdge/) {
5414 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5415 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
5417 my $tmpdir = tempdir(
5421 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
5422 system(
'gunzip Catalog.xml.gz
');
5423 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
5424 # -q is quiet, disabling interactivity and reducing console output
5425 my $fwopts =
"-q
";
5427 for my $url (@paths) {
5428 fetch_dell_fw($url);
5430 run_firmware_scripts($fwopts, $tmpdir);
5432 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5433 print STDERR
"error: Please report to $errorsto.\n
";
5437 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
5438 print STDERR
"error: Please report to $errorsto.\n
";
5444 my $url =
"ftp://ftp.us.dell.com/$path
";
5448 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5449 # firmware packages to download from Dell. Only work for Linux
5450 # machines and
11th generation Dell servers.
5451 sub fetch_dell_fw_list {
5452 my $filename = shift;
5454 my $product = `dmidecode -s system-product-name`;
5456 my ($mybrand, $mymodel) = split(/\s+/, $product);
5458 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
5460 my $xml = XMLin($filename);
5462 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
5463 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
5464 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
5466 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
5467 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
5469 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
5471 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
5473 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
5476 for my $component (@{$xml-
>{SoftwareComponent}}) {
5477 my $componenttype = $component-
>{ComponentType}-
>{value};
5479 # Drop application packages, only firmware and BIOS
5480 next if
'APAC
' eq $componenttype;
5482 my $cpath = $component-
>{path};
5483 for my $path (@paths) {
5484 if ($cpath =~ m%/$path$%) {
5485 push(@paths, $cpath);
5493 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
5494 it could work on other platforms with some tweaking. Anyone know a
5495 index like Catalog.xml is available from HP for HP servers? At the
5496 moment I maintain a similar list manually and it is quickly getting
5502 <title>How is booting into runlevel
1 different from single user boots?
</title>
5503 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
5504 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
5505 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
5506 <description><p
>Wouter Verhelst have some
5507 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
5508 comments and opinions
</a
> on my blog post on
5509 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
5510 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
5511 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
5512 default KDE desktop in Debian
</a
>. I only have time to address one
5513 small piece of his comment now, and though it best to address the
5514 misunderstanding he bring forward:
</p
>
5516 <p
><blockquote
>
5517 Currently, a system admin has four options: [...] boot to a
5518 single-user system (by adding
'single
' to the kernel command line;
5519 this runs rcS and rc1 scripts)
5520 </blockquote
></p
>
5522 <p
>This make me believe Wouter believe booting into single user mode
5523 and booting into runlevel
1 is the same. I am not surprised he
5524 believe this, because it would make sense and is a quite sensible
5525 thing to believe. But because the boot in Debian is slightly broken,
5526 runlevel
1 do not work properly and it isn
't the same as single user
5527 mode. I
'll try to explain what is actually happing, but it is a bit
5528 hard to explain.
</p
>
5530 <p
>Single user mode is defined like this in /etc/inittab:
5531 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
5532 executed in single user mode is sulogin. Single user mode is a boot
5533 state
"between
" the runlevels, and when booting into single user mode,
5534 only the scripts in /etc/rcS.d/ are executed before the init process
5535 enters the single user state. When switching to runlevel
1, the state
5536 is in fact not ending in runlevel
1, but it passes through runlevel
1
5537 and end up in the single user mode (see /etc/rc1.d/S03single, which
5538 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
5539 1. It is confusing that the
'S
' (single user) init mode is not the
5540 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5543 <p
>This summary might make it clearer. When booting for the first
5544 time into single user mode, the following commands are executed:
5545 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
5546 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
5547 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
5548 trying to continue after visiting single user mode. Not all services
5549 are started again as they should, causing the machine to end up in an
5550 unpredicatble state. This is why Debian admins recommend rebooting
5551 after visiting single user mode.
</p
>
5553 <p
>A similar problem with runlevel
1 is caused by the amount of
5554 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
5555 to runlevel
1, the services started from /etc/rcS.d/ are not properly
5556 stopped when passing through the scripts in /etc/rc1.d/, and not
5557 started again when switching away from runlevel
1 to the runlevels
5558 2-
5. I believe the problem is best fixed by moving all the scripts
5559 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
5560 functioning single user mode during boot.
</p
>
5562 <p
>I have spent several years investigating the Debian boot system,
5563 and discovered this problem a few years ago. I suspect it originates
5564 from when sysvinit was introduced into Debian, a long time ago.
</p
>
5569 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
5570 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
5571 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
5572 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
5573 <description><p
>In the Debian boot system, several packages include scripts that
5574 are started from /etc/rcS.d/. In fact, there is a bite more of them
5575 than make sense, and this causes a few problems. What kind of
5576 problems, you might ask. There are at least two problems. The first
5577 is that it is not possible to recover a machine after switching to
5578 runlevel
1. One need to actually reboot to get the machine back to
5579 the expected state. The other is that single user boot will sometimes
5580 run into problems because some of the subsystems are activated before
5581 the root login is presented, causing problems when trying to recover a
5582 machine from a problem in that subsystem. A minor additional point is
5583 that moving more scripts out of rcS.d/ and into the other rc#.d/
5584 directories will increase the amount of scripts that can run in
5585 parallel during boot, and thus decrease the boot time.
</p
>
5587 <p
>So, which scripts should start from rcS.d/. In short, only the
5588 scripts that _have_ to execute before the root login prompt is
5589 presented during a single user boot should go there. Everything else
5590 should go into the numeric runlevels. This means things like
5591 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5592 the numeric runlevels. Today in Debian, there are around
115 init.d
5593 scripts that are started from rcS.d/, and most of them should be moved
5594 out. Do your package have one of them? Please help us make single
5595 user and runlevel
1 better by moving it.
</p
>
5597 <p
>Scripts setting up the screen, keyboard, system partitions
5598 etc. should still be started from rcS.d/, but there is for example no
5599 need to have the network enabled before the single user login prompt
5600 is presented.
</p
>
5602 <p
>As always, things are not so easy to fix as they sound. To keep
5603 Debian systems working while scripts migrate and during upgrades, the
5604 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5605 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5606 and the next ones can only be moved when their dependencies have been
5607 moved first. This migration must be done sequentially while we ensure
5608 that the package system upgrade packages in the right order to keep
5609 the system state correct. This will require some coordination when it
5610 comes to network related packages, but most of the packages with
5611 scripts that should migrate do not have anything in rcS.d/ depending
5612 on them. Some packages have already been updated, like the sudo
5613 package, while others are still left to do. I wish I had time to work
5614 on this myself, but real live constrains make it unlikely that I will
5615 find time to push this forward.
</p
>
5620 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
5621 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
5622 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
5623 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
5624 <description><p
>While at Debconf11, I have several times during discussions
5625 mentioned the issues I believe should be improved in Debian for its
5626 desktop to be useful for more people. The use case for this is my
5627 parents, which are currently running Kubuntu which solve the
5630 <p
>I suspect these four missing features are not very hard to
5631 implement. After all, they are present in Ubuntu, so if we wanted to
5632 do this in Debian we would have a source.
</p
>
5636 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
5637 are new packages available for upgrades, a icon in the KDE status bar
5638 indicate this, and clicking on it will activate the simple upgrade
5639 tool to handle it. I have no problem guiding both of my parents
5640 through the process over the phone. If a kernel reboot is required,
5641 this too is indicated by the status bars and the upgrade tool. Last
5642 time I checked, nothing with the same features was working in KDE in
5645 <li
><strong
>Simple handling of missing Firefox browser
5646 plugins.
</strong
> When the browser encounter a MIME type it do not
5647 currently have a handler for, it will ask the user if the system
5648 should search for a package that would add support for this MIME type,
5649 and if the user say yes, the APT sources will be searched for packages
5650 advertising the MIME type in their control file (visible in the
5651 Packages file in the APT archive). If one or more packages are found,
5652 it is a simple click of the mouse to add support for the missing mime
5653 type. If the package require the user to accept some non-free
5654 license, this is explained to the user. The entire process make it
5655 more clear to the user why something do not work in the browser, and
5656 make the chances higher for the user to blame the web page authors and
5657 not the browser for any missing features.
</li
>
5659 <li
><strong
>Simple handling of missing multimedia codec/format
5660 handlers.
</strong
> When the media players encounter a format or codec
5661 it is not supporting, a dialog pop up asking the user if the system
5662 should search for a package that would add support for it. This
5663 happen with things like MP3, Windows Media or H
.264. The selection
5664 and installation procedure is very similar to the Firefox browser
5665 plugin handling. This is as far as I know implemented using a
5666 gstreamer hook. The end result is that the user easily get access to
5667 the codecs that are present from the APT archives available, while
5668 explaining more on why a given format is unsupported by Ubuntu.
</li
>
5670 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
5671 displaying a text/plain file in my Debian browser, it will propose to
5672 start emacs to show it. If I remember correctly, when doing the same
5673 in Kunbutu it show the file as a text file in the browser. At least I
5674 know Opera will show text files within the browser. I much prefer the
5675 latter behaviour.
</li
>
5679 <p
>There are other nice features as well, like the simplified suite
5680 upgrader, but given that I am the one mostly doing the dist-upgrade,
5681 it do not matter much.
</p
>
5683 <p
>I really hope we could get these features in place for the next
5684 Debian release. It would require the coordinated effort of several
5685 maintainers, but would make the end user experience a lot better.
</p
>
5690 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
5691 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
5692 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
5693 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
5694 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
5695 site is build on Debian/Squeeze, and this platform was chosen because
5696 I am most familiar with Debian (being a Debian Developer for around
10
5697 years) because it is the latest stable Debian release which should get
5698 security support for a few years.
</p
>
5700 <p
>The web service is written in Perl, and depend on some perl modules
5701 that are missing in Debian at the moment. It would be great if these
5702 modules were added to the Debian archive, allowing anyone to set up
5703 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
5704 in their own country using only Debian packages. The list of modules
5705 missing in Debian/Squeeze isn
't very long, and I hope the perl group
5706 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
5707 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5708 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5709 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5710 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5711 easier in the future.
</p
>
5713 <p
>Thanks to the great tools in Debian, getting the missing modules
5714 installed on my server was a simple call to
'cpan2deb Module::Name
'
5715 and
'dpkg -i
' to install the resulting package. But this leave me
5716 with the responsibility of tracking security problems, which I really
5717 do not have time for.
</p
>
5722 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
5723 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
5724 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
5725 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
5726 <description><p
>Here is a small update for my English readers. Most of my blog
5727 posts have been in Norwegian the last few weeks, so here is a short
5728 update in English.
</p
>
5730 <p
>The kids still keep me too busy to get much free software work
5731 done, but I did manage to organise a project to get a Norwegian port
5732 of the British service
5733 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
5734 and it has been running for a month now. The entire project has been
5735 organised by me and two others. Around Christmas we gathered sponsors
5736 to fund the development work. In January I drafted a contract with
5737 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
5738 and in February the development took place. Most of it involved
5739 converting the source to use GPS coordinates instead of British
5740 easting/northing, and the resulting code should be a lot easier to get
5741 running in any country by now. The Norwegian
5742 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
5743 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
5744 source and the source for administrative borders in Norway, and
5745 support for this had to be added/fixed.
</p
>
5747 <p
>The Norwegian version went live March
3th, and we spent the weekend
5748 polishing the system before we announced it March
7th. The system is
5749 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
5750 problem reports in a few weeks. Soon we hope to announce the Android
5751 and iPhone versions making it even easier to report problems with the
5752 public infrastructure.
</p
>
5754 <p
>Perhaps something to consider for those of you in countries without
5755 such service?
</p
>
5760 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
5761 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
5762 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
5763 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
5764 <description><p
>The last few days I have looked at ways to track open security
5765 issues here at my work with the University of Oslo. My idea is that
5766 it should be possible to use the information about security issues
5767 available on the Internet, and check our locally
5768 maintained/distributed software against this information. It should
5769 allow us to verify that no known security issues are forgotten. The
5770 CVE database listing vulnerabilities seem like a great central point,
5771 and by using the package lists from Debian mapped to CVEs provided by
5772 the testing security team, I believed it should be possible to figure
5773 out which security holes were present in our free software
5774 collection.
</p
>
5776 <p
>After reading up on the topic, it became obvious that the first
5777 building block is to be able to name software packages in a unique and
5778 consistent way across data sources. I considered several ways to do
5779 this, for example coming up with my own naming scheme like using URLs
5780 to project home pages or URLs to the Freshmeat entries, or using some
5781 existing naming scheme. And it seem like I am not the first one to
5782 come across this problem, as MITRE already proposed and implemented a
5783 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
5784 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
5785 software, hardware and other platform components. The CPE ids are
5786 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
5787 Vulnerability Database
</a
>, allowing me to look up know security
5788 issues for any CPE name. With this in place, all I need to do is to
5789 locate the CPE id for the software packages we use at the university.
5790 This is fairly trivial (I google for
'cve cpe $package
' and check the
5791 NVD entry if a CVE for the package exist).
</p
>
5793 <p
>To give you an example. The GNU gzip source package have the CPE
5794 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
5795 check out, one could look up
5796 <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
5797 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
5798 The most recent one is
5799 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
5800 and at the bottom of the NVD page for this vulnerability the complete
5801 list of affected versions is provided.
</p
>
5803 <p
>The NVD database of CVEs is also available as a XML dump, allowing
5804 for offline processing of issues. Using this dump, I
've written a
5805 small script taking a list of CPEs as input and list all CVEs
5806 affecting the packages represented by these CPEs. One give it CPEs
5807 with version numbers as specified above and get a list of open
5808 security issues out.
</p
>
5810 <p
>Of course for this approach to be useful, the quality of the NVD
5811 information need to be high. For that to happen, I believe as many as
5812 possible need to use and contribute to the NVD database. I notice
5814 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
5815 map from CVE to CPE
</a
>, indicating that they are using the CPE
5816 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
5818 <p
>To get an idea about the quality for free software, I spent some
5819 time making it possible to compare the CVE database from Debian with
5820 the CVE database in NVD. The result look fairly good, but there are
5821 some inconsistencies in NVD (same software package having several
5822 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5823 Debian believe are affected by a CVE). Hope to find time to improve
5824 the quality of NVD, but that require being able to get in touch with
5825 someone maintaining it. So far my three emails with questions and
5826 corrections have not seen any reply, but I hope contact can be
5827 established soon.
</p
>
5829 <p
>An interesting application for CPEs is cross platform package
5830 mapping. It would be useful to know which packages in for example
5831 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5832 this would be trivial if all linux distributions provided CPE entries
5833 for their packages.
</p
>
5838 <title>Which module is loaded for a given PCI and USB device?
</title>
5839 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
5840 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
5841 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
5842 <description><p
>In the
5843 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
5844 package in Debian, there is a script to report useful information
5845 about the running hardware for use when people report missing
5846 information. One part of this script that I find very useful when
5847 debugging hardware problems, is the part mapping loaded kernel module
5848 to the PCI device it claims. It allow me to quickly see if the kernel
5849 module I expect is driving the hardware I am struggling with. To see
5850 the output, make sure discover-data is installed and run
5851 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
5852 one of my machines like this:
</p
>
5856 10de:
03eb i2c_nforce2
5859 10de:
03f0 snd_hda_intel
5868 <p
>The code in question look like this, slightly modified for
5869 readability and to drop the output to file descriptor
3:
</p
>
5872 if [ -d /sys/bus/pci/devices/ ] ; then
5873 echo loaded pci modules:
5875 cd /sys/bus/pci/devices/
5876 for address in * ; do
5877 if [ -d
"$address/driver/module
" ] ; then
5878 module=`cd $address/driver/module ; pwd -P | xargs basename`
5879 if grep -q
"^$module
" /proc/modules ; then
5880 address=$(echo $address |sed s/
0000://)
5881 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
5882 echo
"$id $module
"
5891 <p
>Similar code could be used to extract USB device module
5895 if [ -d /sys/bus/usb/devices/ ] ; then
5896 echo loaded usb modules:
5898 cd /sys/bus/usb/devices/
5899 for address in * ; do
5900 if [ -d
"$address/driver/module
" ] ; then
5901 module=`cd $address/driver/module ; pwd -P | xargs basename`
5902 if grep -q
"^$module
" /proc/modules ; then
5903 address=$(echo $address |sed s/
0000://)
5904 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
5905 if [
"$id
" ] ; then
5906 echo
"$id $module
"
5916 <p
>This might perhaps be something to include in other tools as
5922 <title>How to test if a laptop is working with Linux
</title>
5923 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
5924 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
5925 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
5926 <description><p
>The last few days I have spent at work here at the
<a
5927 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
5928 batch of computers will work with Linux. Every year for the last few
5929 years the university have organised shared bid of a few thousand
5930 computers, and this year HP won the bid. Two different desktops and
5931 five different laptops are on the list this year. We in the UNIX
5932 group want to know which one of these computers work well with RHEL
5933 and Ubuntu, the two Linux distributions we currently handle at the
5934 university.
</p
>
5936 <p
>My test method is simple, and I share it here to get feedback and
5937 perhaps inspire others to test hardware as well. To test, I PXE
5938 install the OS version of choice, and log in as my normal user and run
5939 a few applications and plug in selected pieces of hardware. When
5940 something fail, I make a note about this in the test matrix and move
5941 on. If I have some spare time I try to report the bug to the OS
5942 vendor, but as I only have the machines for a short time, I rarely
5943 have the time to do this for all the problems I find.
</p
>
5945 <p
>Anyway, to get to the point of this post. Here is the simple tests
5946 I perform on a new model.
</p
>
5950 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
5951 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5952 RHEL5 and Debian Edu/Squeeze.
</li
>
5954 <li
>Is X.org working? If the graphical login screen show up after
5955 installation, X.org is working.
</li
>
5957 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
5958 package mesa-utils on Ubuntu) and writing down the frames per second
5959 reported by the program.
</li
>
5961 <li
>Is sound working? With Gnome and KDE, a sound is played when
5962 logging in, and if I can hear this the test is successful. If there
5963 are several audio exits on the machine, I try them all and check if
5964 the Gnome/KDE audio mixer can control where to send the sound. I
5965 normally test this by playing
5966 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
5967 video
</a
> in Firefox/Iceweasel.
</li
>
5969 <li
>Is the USB subsystem working? I test this by plugging in a USB
5970 memory stick and see if Gnome/KDE notices this.
</li
>
5972 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
5973 I have lying around, and see if Gnome/KDE notices this.
</li
>
5975 <li
>Is any built in camera working? Test using cheese, and see if a
5976 picture from the v4l device show up.
</li
>
5978 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5979 any bluetooth devices are discovered. In my office, I normally see a
5982 <li
>For laptops, is the SD or Compaq Flash reader working. I have
5983 memory modules lying around, and stick them in and see if Gnome/KDE
5984 notice this.
</li
>
5986 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
5987 special button work, and if the laptop continue to work after
5990 <li
>For laptops, is the extra buttons working, like audio level,
5991 adjusting background light, switching on/off external video output,
5992 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5993 laptop to laptop, so I just write down which are working and which are
5996 <li
>Some laptops have smart card readers, finger print readers,
5997 acceleration sensors etc. I rarely test these, as I do not know how
5998 to quickly test if they are working or not, so I only document their
5999 existence.
</li
>
6003 <p
>By now I suspect you are really curious what the test results are
6004 for the HP machines I am testing. I
'm not done yet, so I will report
6005 the test results later. For now I can report that HP
8100 Elite work
6006 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
6007 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
6008 can see, I have most machines left to test. One interesting
6009 observation is that Ubuntu Lucid has almost twice the frame rate than
6010 RHEL6 with glxgears. No idea why.
</p
>
6015 <title>Some thoughts on BitCoins
</title>
6016 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
6017 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
6018 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
6019 <description><p
>As I continue to explore
6020 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
6021 what properties the system have, and how it will be affected by laws
6022 and regulations here in Norway. Here are some random notes.
</p
>
6024 <p
>One interesting thing to note is that since the transactions are
6025 verified using a peer to peer network, all details about a transaction
6026 is known to everyone. This means that if a BitCoin address has been
6027 published like I did with mine in my initial post about BitCoin, it is
6028 possible for everyone to see how many BitCoins have been transfered to
6029 that address. There is even a web service to look at the details for
6030 all transactions. There I can see that my address
6031 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
6032 have received
16.06 Bitcoin, the
6033 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
6034 address of Simon Phipps have received
181.97 BitCoin and the address
6035 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
6036 of EFF have received
2447.38 BitCoins so far. Thank you to each and
6037 every one of you that donated bitcoins to support my activity. The
6038 fact that anyone can see how much money was transfered to a given
6039 address make it more obvious why the BitCoin community recommend to
6040 generate and hand out a new address for each transaction. I
'm told
6041 there is no way to track which addresses belong to a given person or
6042 organisation without the person or organisation revealing it
6043 themselves, as Simon, EFF and I have done.
</p
>
6045 <p
>In Norway, and in most other countries, there are laws and
6046 regulations limiting how much money one can transfer across the border
6047 without declaring it. There are money laundering, tax and accounting
6048 laws and regulations I would expect to apply to the use of BitCoin.
6049 If the Skolelinux foundation
6050 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
6051 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
6052 normal bank transfers like EFF is doing, how should this be accounted?
6053 Given that it is impossible to know if money can cross the border or
6054 not, should everything or nothing be declared? What exchange rate
6055 should be used when calculating taxes? Would receivers have to pay
6056 income tax if the foundation were to pay Skolelinux contributors in
6057 BitCoin? I have no idea, but it would be interesting to know.
</p
>
6059 <p
>For a currency to be useful and successful, it must be trusted and
6060 accepted by a lot of users. It must be possible to get easy access to
6061 the currency (as a wage or using currency exchanges), and it must be
6062 easy to spend it. At the moment BitCoin seem fairly easy to get
6063 access to, but there are very few places to spend it. I am not really
6064 a regular user of any of the vendor types currently accepting BitCoin,
6065 so I wonder when my kind of shop would start accepting BitCoins. I
6066 would like to buy electronics, travels and subway tickets, not herbs
6067 and books. :) The currency is young, and this will improve over time
6068 if it become popular, but I suspect regular banks will start to lobby
6069 to get BitCoin declared illegal if it become popular. I
'm sure they
6070 will claim it is helping fund terrorism and money laundering (which
6071 probably would be true, as is any currency in existence), but I
6072 believe the problems should be solved elsewhere and not by blaming
6073 currencies.
</p
>
6075 <p
>The process of creating new BitCoins is called mining, and it is
6076 CPU intensive process that depend on a bit of luck as well (as one is
6077 competing against all the other miners currently spending CPU cycles
6078 to see which one get the next lump of cash). The
"winner
" get
50
6079 BitCoin when this happen. Yesterday I came across the obvious way to
6080 join forces to increase ones changes of getting at least some coins,
6081 by coordinating the work on mining BitCoins across several machines
6082 and people, and sharing the result if one is lucky and get the
50
6084 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
6085 if this sounds interesting. I have not had time to try to set up a
6086 machine to participate there yet, but have seen that running on ones
6087 own for a few days have not yield any BitCoins througth mining
6090 <p
>Update
2010-
12-
15: Found an
<a
6091 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
6092 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
6093 it was interesting to read. The arguments presented seem to be
6094 equally valid for gold, which was used as a currency for many years.
</p
>
6099 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
6100 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
6101 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
6102 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
6103 <description><p
>With this weeks lawless
6104 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
6105 attacks
</a
> on Wikileak and
6106 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
6107 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
6108 not be trusted to handle money transactions.
6110 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
6111 Phipps on bitcoin
</a
> reminded me about a project that a friend of
6112 mine mentioned earlier. I decided to follow Simon
's example, and get
6113 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
6114 some help from my friend to get it all running, and he even handed me
6115 some bitcoins to get started. I even donated a few bitcoins to Simon
6116 for helping me remember BitCoin.
</p
>
6118 <p
>So, what is bitcoins, you probably wonder? It is a digital
6119 crypto-currency, decentralised and handled using peer-to-peer
6120 networks. It allows anonymous transactions and prohibits central
6121 control over the transactions, making it impossible for governments
6122 and companies alike to block donations and other transactions. The
6123 source is free software, and while the key dependency wxWidgets
2.9
6124 for the graphical user interface is missing in Debian, the command
6125 line client builds just fine. Hopefully Jonas
6126 <a href=
"http://bugs.debian.org/
578157">will get the package into
6127 Debian
</a
> soon.
</p
>
6129 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
6130 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
6131 bitcoins
</a
> when selling services and goods, and there are even
6132 currency
"stock
" markets where the exchange rate is decided. There
6133 are not many users so far, but the concept seems promising. If you
6134 want to get started and lack a friend with any bitcoins to spare,
6136 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
6137 bitcoin at the time of writing). Use
6138 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
6139 on the current exchange rates.
</p
>
6141 <p
>As an experiment, I have decided to set up bitcoind on one of my
6142 machines. If you want to support my activity, please send Bitcoin
6143 donations to the address
6144 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
6149 <title>Why isn
't Debian Edu using VLC?
</title>
6150 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
6151 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
6152 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
6153 <description><p
>In the latest issue of Linux Journal, the readers choices were
6154 presented, and the winner among the multimedia player were VLC.
6155 Personally, I like VLC, and it is my player of choice when I first try
6156 to play a video file or stream. Only if VLC fail will I drag out
6157 gmplayer to see if it can do better. The reason is mostly the failure
6158 model and trust. When VLC fail, it normally pop up a error message
6159 reporting the problem. When mplayer fail, it normally segfault or
6160 just hangs. The latter failure mode drain my trust in the program.
<p
>
6162 <p
>But even if VLC is my player of choice, we have choosen to use
6163 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
6164 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
6165 plugin to play web videos seamlessly, and the VLC browser plugin is
6166 not very good. For example, it lack in-line control buttons, so there
6167 is no way for the user to pause the video. Also, when I
6168 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
6169 tested the browser plugins
</a
> available in Debian, the VLC plugin
6170 failed on several video pages where mplayer based plugins worked. If
6171 the browser plugin for VLC was as good as the gecko-mediaplayer
6172 package (which uses mplayer), we would switch.
</P
>
6174 <p
>While VLC is a good player, its user interface is slightly
6175 annoying. The most annoying feature is its inconsistent use of
6176 keyboard shortcuts. When the player is in full screen mode, its
6177 shortcuts are different from when it is playing the video in a window.
6178 For example, space only work as pause when in full screen mode. I
6179 wish it had consisten shortcuts and that space also would work when in
6180 window mode. Another nice shortcut in gmplayer is [enter] to restart
6181 the current video. It is very nice when playing short videos from the
6182 web and want to restart it when new people arrive to have a look at
6183 what is going on.
</p
>
6188 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
6189 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
6190 <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>
6191 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
6192 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
6193 upgrade testing of the
6194 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
6195 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
6196 This seem like a very good idea, so I adjusted by test scripts and
6197 can now present the updated result from today:
</p
>
6199 <p
>This is for Gnome:
</p
>
6201 <p
>Installed using apt-get, missing with aptitude
</p
>
6203 <blockquote
><p
>
6208 browser-plugin-gnash
6215 freedesktop-sound-theme
6217 gconf-defaults-service
6232 gnome-desktop-environment
6236 gnome-session-canberra
6241 gstreamer0.10-fluendo-mp3
6247 libapache2-mod-dnssd
6250 libaprutil1-dbd-sqlite3
6253 libboost-date-time1.42
.0
6254 libboost-python1.42
.0
6255 libboost-thread1.42
.0
6257 libchamplain-gtk-
0.4-
0
6259 libclutter-gtk-
0.10-
0
6266 libfreerdp-plugins-standard
6281 libgnomepanel2.24-cil
6286 libgtksourceview2.0-common
6287 libmono-addins-gui0.2-cil
6288 libmono-addins0.2-cil
6289 libmono-cairo2.0-cil
6290 libmono-corlib2.0-cil
6291 libmono-i18n-west2.0-cil
6292 libmono-posix2.0-cil
6293 libmono-security2.0-cil
6294 libmono-sharpzip2.84-cil
6295 libmono-system2.0-cil
6298 libndesk-dbus-glib1.0-cil
6299 libndesk-dbus1.0-cil
6309 libtelepathy-farsight0
6318 nautilus-sendto-empathy
6322 python-aptdaemon-gtk
6324 python-beautifulsoup
6339 python-gtksourceview2
6350 python-pkg-resources
6357 python-twisted-conch
6363 python-zope.interface
6368 rhythmbox-plugin-cdrecorder
6375 system-config-printer-udev
6377 telepathy-mission-control-
5
6388 </p
></blockquote
>
6390 <p
>Installed using apt-get, removed with aptitude
</p
>
6392 <blockquote
><p
>
6398 fast-user-switch-applet
6417 libgtksourceview2.0-
0
6419 libsdl1.2debian-alsa
6425 system-config-printer
6430 </p
></blockquote
>
6432 <p
>Installed using aptitude, missing with apt-get
</p
>
6434 <blockquote
><p
>
6435 gstreamer0.10-gnomevfs
6436 </p
></blockquote
>
6438 <p
>Installed using aptitude, removed with apt-get
</p
>
6440 <blockquote
><p
>
6442 </p
></blockquote
>
6444 <p
>This is for KDE:
</p
>
6446 <p
>Installed using apt-get, missing with aptitude
</p
>
6448 <blockquote
><p
>
6450 </p
></blockquote
>
6452 <p
>Installed using apt-get, removed with aptitude
</p
>
6454 <blockquote
><p
>
6457 </p
></blockquote
>
6459 <p
>Installed using aptitude, missing with apt-get
</p
>
6461 <blockquote
><p
>
6475 kdeartwork-emoticons
6477 kdeartwork-theme-icon
6481 kdebase-workspace-bin
6482 kdebase-workspace-data
6496 kscreensaver-xsavers
6511 plasma-dataengines-workspace
6513 plasma-desktopthemes-artwork
6514 plasma-runners-addons
6515 plasma-scriptengine-googlegadgets
6516 plasma-scriptengine-python
6517 plasma-scriptengine-qedje
6518 plasma-scriptengine-ruby
6519 plasma-scriptengine-webkit
6520 plasma-scriptengines
6521 plasma-wallpapers-addons
6522 plasma-widget-folderview
6523 plasma-widget-networkmanagement
6527 xscreensaver-data-extra
6529 xscreensaver-gl-extra
6530 xscreensaver-screensaver-bsod
6531 </p
></blockquote
>
6533 <p
>Installed using aptitude, removed with apt-get
</p
>
6535 <blockquote
><p
>
6537 google-gadgets-common
6555 libggadget-qt-
1.0-
0b
6560 libkonqsidebarplugin4a
6569 libplasma-geolocation-interface4
6571 libplasmagenericshell4
6585 libsmokeknewstuff2-
3
6586 libsmokeknewstuff3-
3
6588 libsmokektexteditor3
6596 libsmokeqtnetwork4-
3
6602 libsmokeqtuitools4-
3
6614 plasma-dataengines-addons
6615 plasma-scriptengine-superkaramba
6616 plasma-widget-lancelot
6617 plasma-widgets-addons
6618 plasma-widgets-workspace
6622 update-notifier-common
6623 </p
></blockquote
>
6625 <p
>Running apt-get autoremove made the results using apt-get and
6626 aptitude a bit more similar, but there are still quite a lott of
6627 differences. I have no idea what packages should be installed after
6628 the upgrade, but hope those that do can have a look.
</p
>
6633 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
6634 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
6635 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
6636 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
6637 <description><p
>Most of the computers in use by the
6638 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
6639 are virtual machines. And they have been Xen machines running on a
6640 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
6641 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
6642 bit harder that it could have been, because we set up the Xen virtual
6643 machines to get the virtual partitions from LVM, which as far as I
6644 know is not supported by KVM. So to migrate, we had to convert
6645 several LVM logical volumes to partitions on a virtual disk file.
</p
>
6648 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
6649 nice recipe
</a
> to do this, and wrote the following script to do the
6650 migration. It uses qemu-img from the qemu package to make the disk
6651 image, parted to partition it, losetup and kpartx to present the disk
6652 image partions as devices, and dd to copy the data. I NFS mounted the
6653 new servers storage area on the old server to do the migration.
</p
>
6659 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6664 if [ -z
"$
1" ] ; then
6665 echo
"Usage: $
0 &lt;hostname
&gt;
"
6671 if [ ! -e /dev/vg_data/$host-disk ] ; then
6672 echo
"error: unable to find LVM volume for $host
"
6676 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6677 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
6678 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
6679 totalsize=$(( ( $disksize + $swapsize ) ))
6682 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
6683 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6685 parted $img mklabel msdos
6686 parted $img mkpart primary linux-swap
0 $disksize
6687 parted $img mkpart primary ext2 $disksize $totalsize
6688 parted $img set
1 boot on
6691 losetup /dev/loop0 $img
6692 kpartx -a /dev/loop0
6694 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
6695 fsck.ext3 -f /dev/mapper/loop0p1 || true
6696 mkswap /dev/mapper/loop0p2
6698 kpartx -d /dev/loop0
6699 losetup -d /dev/loop0
6702 <p
>The script is perhaps so simple that it is not copyrightable, but
6703 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
6705 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
6706 the new disk image attached, installed grub-pc and linux-image-
686 and
6707 set up grub to boot from the disk image. After this, the KVM machines
6708 seem to work just fine.
</p
>
6713 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
6714 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
6715 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
6716 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
6717 <description><p
>I
'm still running upgrade testing of the
6718 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
6719 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
6720 status. Here is a short update based on a test I ran
20101118.
</p
>
6722 <p
>I still do not know what a correct migration should look like, so I
6723 report any differences between apt and aptitude and hope someone else
6724 can see if anything should be changed.
</p
>
6726 <p
>This is for Gnome:
</p
>
6728 <p
>Installed using apt-get, missing with aptitude
</p
>
6730 <blockquote
><p
>
6731 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6732 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
6733 dmz-cursor-theme empathy empathy-common finger
6734 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6735 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6736 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6737 gnome-cards-data gnome-codec-install gnome-core
6738 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6739 gnome-search-tool gnome-session-canberra gnome-spell
6740 gnome-system-log gnome-themes-extras gnome-themes-more
6741 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6742 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6743 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6744 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6745 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
6746 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
6747 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
6748 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
6749 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
6750 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6751 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
6752 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6753 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6754 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6755 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6756 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6757 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6758 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6759 libmono-security2.0-cil libmono-sharpzip2.84-cil
6760 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
6761 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
6762 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
6763 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
6764 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
6765 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
6766 libxalan2-java libxerces2-java media-player-info mesa-utils
6767 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
6768 nautilus-sendto-empathy openoffice.org-writer2latex
6769 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
6770 python-aptdaemon python-aptdaemon-gtk python-axiom
6771 python-beautifulsoup python-bugbuddy python-clientform
6772 python-coherence python-configobj python-crypto python-cupshelpers
6773 python-cupsutils python-eggtrayicon python-elementtree
6774 python-epsilon python-evolution python-feedparser python-gdata
6775 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6776 python-gtksourceview2 python-httplib2 python-louie python-mako
6777 python-markupsafe python-mechanize python-nevow python-notify
6778 python-opengl python-openssl python-pam python-pkg-resources
6779 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6780 python-tagpy python-twisted-bin python-twisted-conch
6781 python-twisted-core python-twisted-web python-utidylib python-webkit
6782 python-xdg python-zope.interface remmina remmina-plugin-data
6783 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6784 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6785 software-center svgalibg1 system-config-printer-udev
6786 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
6787 totem totem-coherence totem-mozilla totem-plugins
6788 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6790 </p
></blockquote
>
6792 Installed using apt-get, removed with aptitude
6794 <blockquote
><p
>
6795 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6796 epiphany-extensions epiphany-gecko evolution-exchange
6797 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6798 gedit-common gnome-app-install gnome-games gnome-games-data
6799 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6800 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6801 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6802 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
6803 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
6804 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
6805 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
6806 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
6807 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
6808 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
6809 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
6810 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
6811 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6812 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6813 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6814 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6815 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
6816 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
6817 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
6818 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
6819 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
6820 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6821 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6822 sound-juicer swfdec-gnome system-config-printer totem-common
6823 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6824 </p
></blockquote
>
6826 <p
>Installed using aptitude, missing with apt-get
</p
>
6828 <blockquote
><p
>
6829 gstreamer0.10-gnomevfs
6830 </p
></blockquote
>
6832 <p
>Installed using aptitude, removed with apt-get
</p
>
6834 <blockquote
><p
>
6836 </p
></blockquote
>
6838 <p
>This is for KDE:
</p
>
6840 <p
>Installed using apt-get, missing with aptitude
</p
>
6842 <blockquote
><p
>
6843 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
6844 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6845 ghostscript-x git gnome-audio gnugo granatier gs-common
6846 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6847 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6848 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6849 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6850 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6851 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6852 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6853 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6854 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6855 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6856 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6857 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
6858 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6859 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6860 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6861 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6862 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6863 libkrossui4 libmailtools-perl libmime-tools-perl
6864 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6865 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6866 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6867 lirc luatex marble networkstatus noatun-plugins
6868 openoffice.org-writer2latex palapeli palapeli-data parley
6869 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6870 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6871 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6873 </p
></blockquote
>
6875 <p
>Installed using apt-get, removed with aptitude
</p
>
6877 <blockquote
><p
>
6878 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6879 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6880 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6881 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6882 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6883 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6884 kitchensync kiten kjumpingcube klatin klettres klickety klines
6885 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6886 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6887 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6888 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6889 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6890 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6891 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6892 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6893 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6894 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
6895 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
6896 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6897 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
6898 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
6899 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6900 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6901 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6902 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6903 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6904 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6905 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
6906 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
6907 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6908 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6909 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6910 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6911 </p
></blockquote
>
6913 <p
>Installed using aptitude, missing with apt-get
</p
>
6915 <blockquote
><p
>
6916 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6917 kdeartwork kdebase kdebase-apps kdebase-workspace
6918 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6919 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6920 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6921 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6922 xscreensaver-screensaver-bsod
6923 </p
></blockquote
>
6925 <p
>Installed using aptitude, removed with apt-get
</p
>
6927 <blockquote
><p
>
6928 kdebase-bin konq-plugins konqueror
6929 </p
></blockquote
>
6934 <title>Gnash buildbot slave and Debian kfreebsd
</title>
6935 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
6936 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
6937 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
6938 <description><p
>Answering
6939 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
6940 call from the Gnash project
</a
> for
6941 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
6942 current source, I have set up a virtual KVM machine on the Debian
6943 Edu/Skolelinux virtualization host to test the git source on
6944 Debian/Squeeze. I hope this can help the developers in getting new
6945 releases out more often.
</p
>
6947 <p
>As the developers want less main-stream build platforms tested to,
6948 I have considered setting up a
<a
6949 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
6950 machine as well. I have also considered using the kfreebsd
6951 architecture in Debian as a file server in NUUG to get access to the
5
6952 TB zfs volume we currently use to store DV video. Because of this, I
6953 finally got around to do a test installation of Debian/Squeeze with
6954 kfreebsd. Installation went fairly smooth, thought I noticed some
6955 visual glitches in the cdebconf dialogs (black cursor left on the
6956 screen at random locations). Have not gotten very far with the
6957 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6958 fatal problem. Have to spend some more time on it to see if it is
6959 useful as a file server for NUUG. Will try to find time to set up a
6960 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
6965 <title>Debian in
3D
</title>
6966 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
6967 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
6968 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
6969 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
6971 <p
>3D printing is just great. I just came across this Debian logo in
6973 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
6974 thingiverse blog
</a
>.
</p
>
6979 <title>Software updates
2010-
10-
24</title>
6980 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
6981 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
6982 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
6983 <description><p
>Some updates.
</p
>
6985 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
6986 raise money for the project is going well. The lower limit of
10
6987 signers was reached in
24 hours, and so far
13 people have signed it.
6988 More signers and more funding is most welcome, and I am really curious
6989 how far we can get before the time limit of December
24 is reached.
6992 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
6993 about what appear to be a great code coverage tool capable of
6994 generating code coverage stats without any changes to the source code.
6996 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
6997 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
6998 It is missing in Debian, but the git source built just fine in Squeeze
6999 after I installed libelf-dev, libdwarf-dev, pkg-config and
7000 libglib2.0-dev. Failed to build in Lenny, but suspect that is
7001 solvable. I hope kcov make it into Debian soon.
</p
>
7003 <p
>Finally found time to wrap up the release notes for
<a
7004 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
7005 new alpha release of Debian Edu
</a
>, and just published the second
7006 alpha test release of the Squeeze based Debian Edu /
7007 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
7008 release. Give it a try if you need a complete linux solution for your
7009 school, including central infrastructure server, workstations, thin
7010 client servers and diskless workstations. A nice touch added
7011 yesterday is RDP support on the thin client servers, for windows
7012 clients to get a Linux desktop on request.
</p
>
7017 <title>Some notes on Flash in Debian and Debian Edu
</title>
7018 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
7019 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
7020 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
7021 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
7022 popularity-contest numbers
</a
>, the adobe-flashplugin package the
7023 second most popular used package that is missing in Debian. The sixth
7024 most popular is flashplayer-mozilla. This is a clear indication that
7025 working flash is important for Debian users. Around
10 percent of the
7026 users submitting data to popcon.debian.org have this package
7027 installed.
</p
>
7029 <p
>In the report written by Lars Risan in August
2008
7030 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
7031 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
7032 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
7033 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
7034 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
7035 web sites require Flash to work, and lacking working Flash support in
7036 the web browser and the problems with installing it was perceived as a
7037 good reason to stay with Windows.
</p
>
7039 <p
>I once saw a funny and sad comment in a web forum, where Linux was
7040 said to be the retarded cousin that did not really understand
7041 everything you told him but could work fairly well. This was a
7042 comment regarding the problems Linux have with proprietary formats and
7043 non-standard web pages, and is sad because it exposes a fairly common
7044 understanding of whose fault it is if web pages that only work in for
7045 example Internet Explorer
6 fail to work on Firefox, and funny because
7046 it explain very well how annoying it is for users when Linux
7047 distributions do not work with the documents they receive or the web
7048 pages they want to visit.
</p
>
7050 <p
>This is part of the reason why I believe it is important for Debian
7051 and Debian Edu to have a well working Flash implementation in the
7052 distribution, to get at least popular sites as Youtube and Google
7053 Video to working out of the box. For Squeeze, Debian have the chance
7054 to include the latest version of Gnash that will make this happen, as
7055 the new release
0.8.8 was published a few weeks ago and is resting in
7056 unstable. The new version work with more sites that version
0.8.7.
7057 The Gnash maintainers have asked for a freeze exception, but the
7058 release team have not had time to reply to it yet. I hope they agree
7059 with me that Flash is important for the Debian desktop users, and thus
7060 accept the new package into Squeeze.
</p
>
7065 <title>Circular package dependencies harms apt recovery
</title>
7066 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
7067 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
7068 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
7069 <description><p
>I discovered this while doing
7070 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
7071 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
7072 in Debian still got circular dependencies, and it is often claimed
7073 that apt and aptitude should be able to handle this just fine, but
7074 some times these dependency loops causes apt to fail.
</p
>
7076 <p
>An example is from todays
7077 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
7078 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
7079 causes perl-modules to fail to upgrade. The cause is simple. If a
7080 package fail to unpack, then only part of packages with the circular
7081 dependency might end up being unpacked when unpacking aborts, and the
7082 ones already unpacked will fail to configure in the recovery phase
7083 because its dependencies are unavailable.
</p
>
7085 <p
>In this log, the problem manifest itself with this error:
</p
>
7087 <blockquote
><pre
>
7088 dpkg: dependency problems prevent configuration of perl-modules:
7089 perl-modules depends on perl (
>=
5.10.1-
1); however:
7090 Version of perl on system is
5.10.0-
19lenny
2.
7091 dpkg: error processing perl-modules (--configure):
7092 dependency problems - leaving unconfigured
7093 </pre
></blockquote
>
7095 <p
>The perl/perl-modules circular dependency is already
7096 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
7097 hopefully be solved as soon as possible, but it is not the only one,
7098 and each one of these loops in the dependency tree can cause similar
7099 failures. Of course, they only occur when there are bugs in other
7100 packages causing the unpacking to fail, but it is rather nasty when
7101 the failure of one package causes the problem to become worse because
7102 of dependency loops.
</p
>
7105 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
7106 tireless effort by Bill Allombert
</a
>, the number of circular
7108 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
7109 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
7111 <p
>Todays testing also exposed a bug in
7112 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
7113 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
7114 apt-get and aptitude, the latter possibly caused by some circular
7115 dependency. Reported both to BTS to try to get someone to look at
7121 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
7122 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
7123 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
7124 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
7125 <description><p
>This is a
7126 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
7128 <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
7130 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
7131 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
7133 <p
>As a step to try to see if it possible to merge the DNS and DHCP
7134 LDAP objects, I have had a look at how the packages pdns-backend-ldap
7135 and dhcp3-server-ldap in Debian use the LDAP server. The two
7136 implementations are quite different in how they use LDAP.
</p
>
7138 To get this information, I started slapd with debugging enabled and
7139 dumped the debug output to a file to get the LDAP searches performed
7140 on a Debian Edu main-server. Here is a summary.
7142 <p
><strong
>powerdns
</strong
></p
>
7144 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
7145 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
7148 <p
>PowerDNS have two modes of operation using LDAP as its backend.
7149 One
"strict
" mode where the forward and reverse DNS lookups are done
7150 using the same LDAP objects, and a
"tree
" mode where the forward and
7151 reverse entries are in two different subtrees in LDAP with a structure
7152 based on the DNS names, as in tjener.intern and
7153 2.2.0.10.in-addr.arpa.
</p
>
7155 <p
>In tree mode, the server is set up to use a LDAP subtree as its
7156 base, and uses a
"base
" scoped search for the DNS name by adding
7157 "dc=tjener,dc=intern,
" to the base with a filter for
7158 "(associateddomain=tjener.intern)
" for the forward entry and
7159 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
7160 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
7161 forward entries, it is looking for attributes named dnsttl, arecord,
7162 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
7163 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
7164 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
7165 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
7166 spfrecord and modifytimestamp. For reverse entries it is looking for
7167 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
7168 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
7169 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
7170 ldapsearch commands could look like this:
</p
>
7172 <blockquote
><pre
>
7173 ldapsearch -h ldap \
7174 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7175 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7176 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7177 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7178 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7179 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7181 ldapsearch -h ldap \
7182 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7183 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
7184 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
7185 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
7186 srvrecord naptrrecord modifytimestamp
7187 </pre
></blockquote
>
7189 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
7190 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
7191 example LDAP objects used there. In addition to these objects, the
7192 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
7193 also exist.
</p
>
7195 <blockquote
><pre
>
7196 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
7198 objectclass: dnsdomain
7199 objectclass: domainrelatedobject
7202 associateddomain: tjener.intern
7204 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
7206 objectclass: dnsdomain2
7207 objectclass: domainrelatedobject
7209 ptrrecord: tjener.intern
7210 associateddomain:
2.2.0.10.in-addr.arpa
7211 </pre
></blockquote
>
7213 <p
>In strict mode, the server behaves differently. When looking for
7214 forward DNS entries, it is doing a
"subtree
" scoped search with the
7215 same base as in the tree mode for a object with filter
7216 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
7217 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
7218 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
7219 naptrrecord and modifytimestamp. For reverse entires it also do a
7220 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
7221 and the requested attributes are associateddomain, dnsttl and
7222 modifytimestamp. In short, in strict mode the objects with ptrrecord
7223 go away, and the arecord attribute in the forward object is used
7226 <p
>The forward and reverse searches can be simulated using ldapsearch
7227 like this:
</p
>
7229 <blockquote
><pre
>
7230 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7231 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
7232 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7233 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7234 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7235 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7237 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7238 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
7239 </pre
></blockquote
>
7241 <p
>In addition to the forward and reverse searches , there is also a
7242 search for SOA records, which behave similar to the forward and
7243 reverse lookups.
</p
>
7245 <p
>A thing to note with the PowerDNS behaviour is that it do not
7246 specify any objectclass names, and instead look for the attributes it
7247 need to generate a DNS reply. This make it able to work with any
7248 objectclass that provide the needed attributes.
</p
>
7250 <p
>The attributes are normally provided in the cosine (RFC
1274) and
7251 dnsdomain2 schemas. The latter is used for reverse entries like
7252 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
7254 <p
>In Debian Edu, we have created DNS objects using the object classes
7255 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
7256 attributes) and domainrelatedobject (for associatedDomain). The use
7257 of structural object classes make it impossible to combine these
7258 classes with the object classes used by DHCP.
</p
>
7260 <p
>There are other schemas that could be used too, for example the
7261 dnszone structural object class used by Gosa and bind-sdb for the DNS
7262 attributes combined with the domainrelatedobject object class, but in
7263 this case some unused attributes would have to be included as well
7264 (zonename and relativedomainname).
</p
>
7266 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
7267 mode and not use any of the existing objectclasses (dnsdomain,
7268 dnsdomain2 and dnszone) when one want to combine the DNS information
7269 with DHCP information, and instead create a auxiliary object class
7270 defined something like this (using the attributes defined for
7271 dnsdomain and dnsdomain2 or dnszone):
</p
>
7273 <blockquote
><pre
>
7274 objectclass ( some-oid NAME
'dnsDomainAux
'
7277 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
7278 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
7279 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
7280 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
7281 A6Record $ DNAMERecord
7283 </pre
></blockquote
>
7285 <p
>This will allow any object to become a DNS entry when combined with
7286 the domainrelatedobject object class, and allow any entity to include
7287 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
7288 developers asking for their view on this schema and if they are
7289 interested in providing such schema with PowerDNS, and I hope my
7290 message will be accepted into their mailing list soon.
</p
>
7292 <p
><strong
>ISC dhcp
</strong
></p
>
7294 <p
>The DHCP server searches for specific objectclass and requests all
7295 the object attributes, and then uses the attributes it want. This
7296 make it harder to figure out exactly what attributes are used, but
7297 thanks to the working example in Debian Edu I can at least get an idea
7298 what is needed without having to read the source code.
</p
>
7300 <p
>In the DHCP server configuration, the LDAP base to use and the
7301 search filter to use to locate the correct dhcpServer entity is
7302 stored. These are the relevant entries from
7303 /etc/dhcp3/dhcpd.conf:
</p
>
7305 <blockquote
><pre
>
7306 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
7307 ldap-dhcp-server-cn
"dhcp
";
7308 </pre
></blockquote
>
7310 <p
>The DHCP server uses this information to nest all the DHCP
7311 configuration it need. The cn
"dhcp
" is located using the given LDAP
7312 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
7313 search result is this entry:
</p
>
7315 <blockquote
><pre
>
7316 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
7319 objectClass: dhcpServer
7320 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7321 </pre
></blockquote
>
7323 <p
>The content of the dhcpServiceDN attribute is next used to locate the
7324 subtree with DHCP configuration. The DHCP configuration subtree base
7325 is located using a base scope search with base
"cn=DHCP
7326 Config,dc=skole,dc=skolelinux,dc=no
" and filter
7327 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
7328 The search result is this entry:
</p
>
7330 <blockquote
><pre
>
7331 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7334 objectClass: dhcpService
7335 objectClass: dhcpOptions
7336 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
7337 dhcpStatements: ddns-update-style none
7338 dhcpStatements: authoritative
7339 dhcpOption: smtp-server code
69 = array of ip-address
7340 dhcpOption: www-server code
72 = array of ip-address
7341 dhcpOption: wpad-url code
252 = text
7342 </pre
></blockquote
>
7344 <p
>Next, the entire subtree is processed, one level at the time. When
7345 all the DHCP configuration is loaded, it is ready to receive requests.
7346 The subtree in Debian Edu contain objects with object classes
7347 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
7348 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
7349 and information about netmasks, dynamic range etc. Leaving out the
7350 details here because it is not relevant for the focus of my
7351 investigation, which is to see if it is possible to merge dns and dhcp
7352 related computer objects.
</p
>
7354 <p
>When a DHCP request come in, LDAP is searched for the MAC address
7355 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
7356 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
7357 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
7358 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
7361 <blockquote
><pre
>
7362 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7365 objectClass: dhcpHost
7366 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7367 dhcpStatements: fixed-address hostname
7368 </pre
></blockquote
>
7370 <p
>There is less flexiblity in the way LDAP searches are done here.
7371 The object classes need to have fixed names, and the configuration
7372 need to be stored in a fairly specific LDAP structure. On the
7373 positive side, the invidiual dhcpHost entires can be anywhere without
7374 the DN pointed to by the dhcpServer entries. The latter should make
7375 it possible to group all host entries in a subtree next to the
7376 configuration entries, and this subtree can also be shared with the
7377 DNS server if the schema proposed above is combined with the dhcpHost
7378 structural object class.
7380 <p
><strong
>Conclusion
</strong
></p
>
7382 <p
>The PowerDNS implementation seem to be very flexible when it come
7383 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
7384 come to the the LDAP structure, the
"strict
" mode is very flexible,
7385 allowing DNS objects to be stored anywhere under the base cn specified
7386 in the configuration.
</p
>
7388 <p
>The DHCP implementation on the other hand is very inflexible, both
7389 regarding which LDAP schemas to use and which LDAP structure to use.
7390 I guess one could implement ones own schema, as long as the
7391 objectclasses and attributes have the names used, but this do not
7392 really help when the DHCP subtree need to have a fairly fixed
7393 structure.
</p
>
7395 <p
>Based on the observed behaviour, I suspect a LDAP structure like
7396 this might work for Debian Edu:
</p
>
7398 <blockquote
><pre
>
7400 cn=machine-info (dhcpService) - dhcpServiceDN points here
7401 cn=dhcp (dhcpServer)
7402 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7403 cn=
10.0.2.0 (dhcpSubnet)
7404 cn=group1 (dhcpGroup/dhcpOptions)
7405 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7406 cn=
192.168.0.0 (dhcpSubnet)
7407 cn=group1 (dhcpGroup/dhcpOptions)
7408 ou=machines - PowerDNS base points here
7409 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7410 </pre
></blockquote
>
7412 <P
>This is not tested yet. If the DHCP server require the dhcpHost
7413 entries to be in the dhcpGroup subtrees, the entries can be stored
7414 there instead of a common machines subtree, and the PowerDNS base
7415 would have to be moved one level up to the machine-info subtree.
</p
>
7417 <p
>The combined object under the machines subtree would look something
7418 like this:
</p
>
7420 <blockquote
><pre
>
7421 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7424 objectClass: dhcpHost
7425 objectclass: domainrelatedobject
7426 objectclass: dnsDomainAux
7427 associateddomain: hostname.intern
7428 arecord:
10.11.12.13
7429 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
7430 dhcpStatements: fixed-address hostname.intern
7431 </pre
></blockquote
>
7433 </p
>One could even add the LTSP configuration associated with a given
7434 machine, as long as the required attributes are available in a
7435 auxiliary object class.
</p
>
7440 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
7441 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
7442 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
7443 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
7444 <description><p
>For a while now, I have wanted to find a way to change the DNS and
7445 DHCP services in Debian Edu to use the same LDAP objects for a given
7446 computer, to avoid the possibility of having a inconsistent state for
7447 a computer in LDAP (as in DHCP but no DNS entry or the other way
7448 around) and make it easier to add computers to LDAP.
</p
>
7450 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
7451 information finally found a solution that seem to work.
</p
>
7453 <p
>The old setup required three LDAP objects for a given computer.
7454 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7455 we switch powerdns to use its strict LDAP method (ldap-method=strict
7456 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7457 merged into one while making it impossible to transfer the reverse map
7458 to a slave DNS server.
</p
>
7460 <p
>If we also replace the object class used to get the DNS related
7461 attributes to one allowing these attributes to be combined with the
7462 dhcphost object class, we can merge the DNS and DHCP entries into one.
7463 I
've written such object class in the dnsdomainaux.schema file (need
7464 proper OIDs, but that is a minor issue), and tested the setup. It
7465 seem to work.
</p
>
7467 <p
>With this test setup in place, we can get away with one LDAP object
7468 for both DNS and DHCP, and even the LTSP configuration I suggested in
7469 an earlier email. The combined LDAP object will look something like
7472 <blockquote
><pre
>
7473 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7475 objectClass: dhcphost
7476 objectclass: domainrelatedobject
7477 objectclass: dnsdomainaux
7478 associateddomain: hostname.intern
7479 arecord:
10.11.12.13
7480 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
7481 dhcpstatements: fixed-address hostname
7483 </pre
></blockquote
>
7485 <p
>The DNS server uses the associateddomain and arecord entries, while
7486 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7487 before asking DNS to resolve the fixed-adddress. LTSP will use
7488 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
7490 <p
>I am not yet sure if I can get the DHCP server to look for its
7491 dhcphost in a different location, to allow us to put the objects
7492 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
7493 that. If I can
't figure out a way to do that, we can still get rid of
7494 the hosts subtree and move all its content into the DHCP Config tree
7495 (which probably should be renamed to be more related to the new
7496 content. I suspect cn=dnsdhcp,ou=services or something like that
7497 might be a good place to put it.
</p
>
7499 <p
>If you want to help out with implementing this for Debian Edu,
7500 please contact us on debian-edu@lists.debian.org.
</p
>
7505 <title>Idea for storing LTSP configuration in LDAP
</title>
7506 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
7507 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
7508 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
7509 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
7510 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7511 clients, and that this can be used to fetch configuration from LDAP if
7512 Debian Edu choose to store configuration there.
</p
>
7514 <p
>Armed with this information, I got inspired and wrote a test module
7515 to get configuration from LDAP. The idea is to look up the MAC
7516 address of the client in LDAP, and look for attributes on the form
7517 ltspconfigsetting=value, and use this to export SETTING=value to the
7518 LTSP clients.
</p
>
7520 <p
>The goal is to be able to store the LTSP configuration attributes
7521 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
7522 allowing us to store all information about a computer in one place.
</p
>
7524 <p
>This is a untested draft implementation, and I welcome feedback on
7525 this approach. A real LDAP schema for the ltspClientAux objectclass
7526 need to be written. Comments, suggestions, etc?
</p
>
7528 <blockquote
><pre
>
7529 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7531 # Fetch LTSP client settings from LDAP based on MAC address
7533 # Uses ethernet address as stored in the dhcpHost objectclass using
7534 # the dhcpHWAddress attribute or ethernet address stored in the
7535 # ieee802Device objectclass with the macAddress attribute.
7537 # This module is written to be schema agnostic, and only depend on the
7538 # existence of attribute names.
7540 # The LTSP configuration variables are saved directly using a
7541 # ltspConfig prefix and uppercasing the rest of the attribute name.
7542 # To set the SERVER variable, set the ltspConfigServer attribute.
7544 # Some LDAP schema should be created with all the relevant
7545 # configuration settings. Something like this should work:
7547 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
7550 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7552 LDAPSERVER=$(debian-edu-ldapserver)
7553 if [
"$LDAPSERVER
" ] ; then
7554 LDAPBASE=$(debian-edu-ldapserver -b)
7555 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
7556 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
7557 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
7558 grep
'^ltspConfig
' | while read attr value ; do
7559 # Remove prefix and convert to upper case
7560 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
7561 # bass value on to clients
7562 eval
"$attr=$value; export $attr
"
7566 </pre
></blockquote
>
7568 <p
>I
'm not sure this shell construction will work, because I suspect
7569 the while block might end up in a subshell causing the variables set
7570 there to not show up in ltsp-config, but if that is the case I am sure
7571 the code can be restructured to make sure the variables are passed on.
7572 I expect that can be solved with some testing. :)
</p
>
7574 <p
>If you want to help out with implementing this for Debian Edu,
7575 please contact us on debian-edu@lists.debian.org.
</p
>
7577 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
7578 configuration in LDAP that was created around year
2000 by
7579 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
7580 Xperience, Inc.,
2000</a
>. I found its
7581 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
7582 personal home page over at redhat.com.
</p
>
7587 <title>jXplorer, a very nice LDAP GUI
</title>
7588 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
7589 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
7590 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
7591 <description><p
>Since
7592 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
7593 last post
</a
> about available LDAP tools in Debian, I was told about a
7594 LDAP GUI that is even better than luma. The java application
7595 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
7596 moving LDAP objects and subtrees using drag-and-drop, and can
7597 authenticate using Kerberos. I have only tested the Kerberos
7598 authentication, but do not have a LDAP setup allowing me to rewrite
7599 LDAP with my test user yet. It is
7600 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
7601 Debian
</a
> testing and unstable at the moment. The only problem I
7602 have with it is how it handle errors. If something go wrong, its
7603 non-intuitive behaviour require me to go through some query work list
7604 and remove the failing query. Nothing big, but very annoying.
</p
>
7609 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
7610 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
7611 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
7612 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
7613 <description><p
>Here is a short update on my
<a
7614 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
7615 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
7616 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
7617 not reporting the status for KDE, because the upgrade crashes when
7618 aptitude try because of missing conflicts
7619 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
7620 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
7622 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
7623 complete list of the installed packages. Based on this I see these
7624 differences when I did a test run today. As usual, I do not really
7625 know what the correct set of packages would be, but thought it best to
7626 publish the difference.
</p
>
7628 <p
>Installed using apt-get, missing with aptitude
</p
>
7630 <blockquote
><p
>
7631 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
7632 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
7633 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7634 libgtksourceview-common libpt-
1.10.10-plugins-alsa
7635 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7636 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7637 python-
4suite-xml python-eggtrayicon python-gtkhtml2
7638 python-gtkmozembed svgalibg1 xserver-xephyr zip
7639 </p
></blockquote
>
7641 <p
>Installed using apt-get, removed with aptitude
</p
>
7643 <blockquote
><p
>
7644 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7645 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7646 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
7647 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
7648 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
7649 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
7650 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7651 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7652 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7653 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
7654 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
7655 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
7656 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7657 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
7658 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7659 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
7660 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
7661 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7662 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7663 mysql-common swfdec-gnome totem-gstreamer wodim
7664 </p
></blockquote
>
7666 <p
>Installed using aptitude, missing with apt-get
</p
>
7668 <blockquote
><p
>
7669 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7670 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7671 xserver-xorg-input-all xserver-xorg-input-evdev
7672 xserver-xorg-input-kbd xserver-xorg-input-mouse
7673 xserver-xorg-input-synaptics xserver-xorg-video-all
7674 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7675 xserver-xorg-video-chips xserver-xorg-video-cirrus
7676 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7677 xserver-xorg-video-glint xserver-xorg-video-i128
7678 xserver-xorg-video-i740 xserver-xorg-video-mach64
7679 xserver-xorg-video-mga xserver-xorg-video-neomagic
7680 xserver-xorg-video-nouveau xserver-xorg-video-nv
7681 xserver-xorg-video-r128 xserver-xorg-video-radeon
7682 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7683 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7684 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7685 xserver-xorg-video-sis xserver-xorg-video-sisusb
7686 xserver-xorg-video-tdfx xserver-xorg-video-tga
7687 xserver-xorg-video-trident xserver-xorg-video-tseng
7688 xserver-xorg-video-vesa xserver-xorg-video-vmware
7689 xserver-xorg-video-voodoo
7690 </p
></blockquote
>
7692 <p
>Installed using aptitude, removed with apt-get
</p
>
7694 <blockquote
><p
>
7695 deskbar-applet xserver-xorg xserver-xorg-core
7696 xserver-xorg-input-wacom xserver-xorg-video-intel
7697 xserver-xorg-video-openchrome
7698 </p
></blockquote
>
7700 <p
>I was told on IRC that the xorg-xserver package was
7701 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
7702 in git
</a
> today to try to get apt-get to not remove xorg completely.
7703 No idea when it hits Squeeze, but when it does I hope it will reduce
7704 the difference somewhat.
7709 <title>LUMA, a very nice LDAP GUI
</title>
7710 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
7711 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
7712 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
7713 <description><p
>The last few days I have been looking into the status of the LDAP
7714 directory in Debian Edu, and in the process I started to miss a GUI
7715 tool to browse the LDAP tree. The only one I was able to find in
7716 Debian/Squeeze and Lenny is
7717 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
7718 be a great tool to get a overview of the current LDAP directory
7719 populated by default in Skolelinux. Thanks to it, I have been able to
7720 find empty and obsolete subtrees, misplaced objects and duplicate
7721 objects. It will be installed by default in Debian/Squeeze. If you
7722 are working with LDAP, give it a go. :)
</p
>
7724 <p
>I did notice one problem with it I have not had time to report to
7725 the BTS yet. There is no .desktop file in the package, so the tool do
7726 not show up in the Gnome and KDE menus, but only deep down in in the
7727 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7730 <p
>I have not yet been able to get it to modify the tree yet. I would
7731 like to move objects and remove subtrees directly in the GUI, but have
7732 not found a way to do that with LUMA yet. So in the mean time, I use
7733 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
7735 <p
>If you have tips on other GUI tools for LDAP that might be useful
7736 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
7738 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
7739 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
7740 useful GUI alternative. It seem like a good tool, but is unmaintained
7741 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7742 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
7747 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
7748 <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>
7749 <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>
7750 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
7751 <description><p
>A while back, I
7752 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
7753 about the fact
</a
> that it is not possible with the provided schemas
7754 for storing DNS and DHCP information in LDAP to combine the two sets
7755 of information into one LDAP object representing a computer.
</p
>
7757 <p
>In the mean time, I discovered that a simple fix would be to make
7758 the dhcpHost object class auxiliary, to allow it to be combined with
7759 the dNSDomain object class, and thus forming one object for one
7760 computer when storing both DHCP and DNS information in LDAP.
</p
>
7762 <p
>If I understand this correctly, it is not safe to do this change
7763 without also changing the assigned number for the object class, and I
7764 do not know enough about LDAP schema design to do that properly for
7765 Debian Edu.
</p
>
7767 <p
>Anyway, for future reference, this is how I believe we could change
7769 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
7770 schema
</a
> to solve at least part of the problem with the LDAP schemas
7771 available today from IETF.
</p
>
7774 --- dhcp.schema (revision
65192)
7775 +++ dhcp.schema (working copy)
7777 objectclass (
2.16.840.1.113719.1.203.6.6
7778 NAME
'dhcpHost
'
7779 DESC
'This represents information about a particular client
'
7783 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7784 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
7787 <p
>I very much welcome clues on how to do this properly for Debian
7788 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7789 package, and should thus be free to rewrite it as we see fit.
</p
>
7791 <p
>If you want to help out with implementing this for Debian Edu,
7792 please contact us on debian-edu@lists.debian.org.
</p
>
7797 <title>Calling tasksel like the installer, while still getting useful output
</title>
7798 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
7799 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
7800 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
7801 <description><p
>A few times I have had the need to simulate the way tasksel
7802 installs packages during the normal debian-installer run. Until now,
7803 I have ended up letting tasksel do the work, with the annoying problem
7804 of not getting any feedback at all when something fails (like a
7805 conffile question from dpkg or a download that fails), using code like
7808 <blockquote
><pre
>
7809 export DEBIAN_FRONTEND=noninteractive
7810 tasksel --new-install
7811 </pre
></blockquote
>
7813 This would invoke tasksel, let its automatic task selection pick the
7814 tasks to install, and continue to install the requested tasks without
7815 any output what so ever.
7817 Recently I revisited this problem while working on the automatic
7818 package upgrade testing, because tasksel would some times hang without
7819 any useful feedback, and I want to see what is going on when it
7820 happen. Then it occured to me, I can parse the output from tasksel
7821 when asked to run in test mode, and use that aptitude command line
7822 printed by tasksel then to simulate the tasksel run. I ended up using
7825 <blockquote
><pre
>
7826 export DEBIAN_FRONTEND=noninteractive
7827 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
7829 </pre
></blockquote
>
7831 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
7832 --without-recommends -o APT::Install-Recommends=no -y install
7833 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7834 ~pimportant
</tt
>", which will install the gnome desktop task, the
7835 laptop task and all packages with priority standard , required and
7836 important, just like tasksel would have done it during
7837 installation.
</p
>
7839 <p
>A better approach is probably to extend tasksel to be able to
7840 install packages without using debconf-apt-progress, for use cases
7841 like this.
</p
>
7846 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
7847 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
7848 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
7849 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
7850 <description><p
>My
7851 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
7852 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
7853 finally made the upgrade logs available from
7854 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
7855 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7856 apt and aptitude, and found their differences interesting. This time
7857 I will only focus on their removal plans.
</p
>
7859 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
7860 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
7861 surprising part is that it want to remove xorg and all
7862 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7863 sure why. When asking aptitude to do the same, it want to remove
129
7864 packages, but most of them are library packages I suspect are no
7865 longer needed. Both of them want to remove bluetooth packages, which
7866 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
7868 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
7869 which seem like a bad idea and xorg the same way as with Gnome. Asking
7870 aptitude for the same, it wants to remove
192 packages, none which are
7871 too surprising.
</p
>
7873 <p
>I guess the removal of xorg during upgrades should be investigated
7874 and avoided, and perhaps others as well. Here are the complete list
7875 of planned removals. The complete logs is available from the URL
7876 above. Note if you want to repeat these tests, that the upgrade test
7877 for kde+apt-get hung in the tasksel setup because of dpkg asking
7878 conffile questions. No idea why. I worked around it by using
7879 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
7882 <p
><b
>apt-get gnome
72</b
>
7883 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
7884 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7885 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
7886 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7887 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7888 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7889 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7890 xserver-xorg-input-kbd xserver-xorg-input-mouse
7891 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7892 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7893 xserver-xorg-video-ati xserver-xorg-video-chips
7894 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7895 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7896 xserver-xorg-video-glint xserver-xorg-video-i128
7897 xserver-xorg-video-i740 xserver-xorg-video-imstt
7898 xserver-xorg-video-intel xserver-xorg-video-mach64
7899 xserver-xorg-video-mga xserver-xorg-video-neomagic
7900 xserver-xorg-video-nsc xserver-xorg-video-nv
7901 xserver-xorg-video-openchrome xserver-xorg-video-r128
7902 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7903 xserver-xorg-video-rendition xserver-xorg-video-s3
7904 xserver-xorg-video-s3virge xserver-xorg-video-savage
7905 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7906 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7907 xserver-xorg-video-tga xserver-xorg-video-trident
7908 xserver-xorg-video-tseng xserver-xorg-video-v4l
7909 xserver-xorg-video-vesa xserver-xorg-video-vga
7910 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
7911 xulrunner-
1.9-gnome-support
</p
>
7913 <p
><b
>aptitude gnome
129</b
>
7915 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
7916 djvulibre-desktop finger gnome-app-install gnome-mount
7917 gnome-network-admin gnome-spell gnome-vfs-obexftp
7918 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7919 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7920 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7921 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
7922 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
7923 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
7924 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
7925 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
7926 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
7927 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
7928 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
7929 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
7930 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7931 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
7932 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
7933 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
7934 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
7935 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
7936 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7937 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7938 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7939 openoffice.org-writer2latex openssl-blacklist p7zip
7940 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
7941 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7942 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7943 swfdec-mozilla totem-gstreamer update-manager wodim
7944 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7945 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7948 <p
><b
>apt-get kde
82</b
>
7950 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7951 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7952 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7953 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7954 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7955 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7956 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7957 xserver-xorg-input-kbd xserver-xorg-input-mouse
7958 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7959 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7960 xserver-xorg-video-ati xserver-xorg-video-chips
7961 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7962 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7963 xserver-xorg-video-glint xserver-xorg-video-i128
7964 xserver-xorg-video-i740 xserver-xorg-video-imstt
7965 xserver-xorg-video-intel xserver-xorg-video-mach64
7966 xserver-xorg-video-mga xserver-xorg-video-neomagic
7967 xserver-xorg-video-nsc xserver-xorg-video-nv
7968 xserver-xorg-video-openchrome xserver-xorg-video-r128
7969 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7970 xserver-xorg-video-rendition xserver-xorg-video-s3
7971 xserver-xorg-video-s3virge xserver-xorg-video-savage
7972 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7973 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7974 xserver-xorg-video-tga xserver-xorg-video-trident
7975 xserver-xorg-video-tseng xserver-xorg-video-v4l
7976 xserver-xorg-video-vesa xserver-xorg-video-vga
7977 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
7979 <p
><b
>aptitude kde
192</b
>
7980 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
7981 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7982 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7983 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7984 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7985 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7986 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7987 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7988 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7989 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7990 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7991 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7992 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7993 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7994 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7995 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7996 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7997 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7998 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
7999 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
8000 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8001 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
8002 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
8003 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
8004 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8005 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
8006 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
8007 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
8008 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
8009 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
8010 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
8011 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
8012 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
8013 texlive-common texlive-doc-base texlive-fonts-recommended
8014 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8015 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8016 xulrunner-
1.9</p
>
8022 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
8023 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
8024 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
8025 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
8026 <description><p
>The last few days I have done some upgrade testing in Debian, to
8027 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
8028 have been discovered and reported in the process
8029 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
8030 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
8031 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
8032 kdebase-workspace-data), and to get a more regular testing going on, I
8033 am working on a script to automate the test.
</p
>
8035 <p
>The idea is to create a Lenny chroot and use tasksel to install a
8036 Gnome or KDE desktop installation inside the chroot before upgrading
8037 it. To ensure no services are started in the chroot, a policy-rc.d
8038 script is inserted. To make sure tasksel believe it is to install a
8039 desktop on a laptop, the tasksel tests are replaced in the chroot
8040 (only acceptable because this is a throw-away chroot).
</p
>
8042 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
8043 currently always fail because udev refuses to upgrade with the kernel
8044 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
8045 is created. The bug report
8046 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
8047 this problem do not trigger in a chroot, but I touch the file anyway
8048 to make sure the upgrade go well. Testing on virtual and real
8049 hardware have failed me because of udev so far, and creating this file
8050 do the trick in such settings anyway. This is a
8051 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
8052 issue
</a
> and the current udev behaviour is intended by the udev
8053 maintainer because he lack the resources to rewrite udev to keep
8054 working with old kernels or something like that. I really wish the
8055 udev upstream would keep udev backwards compatible, to avoid such
8056 upgrade problem, but given that they fail to do so, I guess
8057 documenting the way out of this mess is the best option we got for
8058 Debian Squeeze.
</p
>
8060 <p
>Anyway, back to the task at hand, testing upgrades. This test
8061 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
8064 <blockquote
><pre
>
8068 if [
"$
1" ] ; then
8077 exec
&lt; /dev/null
8079 mirror=http://ftp.skolelinux.org/debian
8080 tmpdir=chroot-$from-upgrade-$to-$desktop
8082 debootstrap $from $tmpdir $mirror
8083 chroot $tmpdir aptitude update
8084 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
8088 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
8092 mount -t proc proc $tmpdir/proc
8093 # Make sure proc is unmounted also on failure
8094 trap exit_cleanup EXIT INT
8096 chroot $tmpdir aptitude -y install debconf-utils
8098 # Make sure tasksel autoselection trigger. It need the test scripts
8099 # to return the correct answers.
8100 echo tasksel tasksel/desktop multiselect $desktop | \
8101 chroot $tmpdir debconf-set-selections
8103 # Include the desktop and laptop task
8104 for test in desktop laptop ; do
8105 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
8109 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
8112 DEBIAN_FRONTEND=noninteractive
8113 DEBIAN_PRIORITY=critical
8114 export DEBIAN_FRONTEND DEBIAN_PRIORITY
8115 chroot $tmpdir tasksel --new-install
8117 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
8118 chroot $tmpdir aptitude update
8119 touch $tmpdir/etc/udev/kernel-upgrade
8120 chroot $tmpdir aptitude -y dist-upgrade
8122 </pre
></blockquote
>
8124 <p
>I suspect it would be useful to test upgrades with both apt-get and
8125 with aptitude, but I have not had time to look at how they behave
8126 differently so far. I hope to get a cron job running to do the test
8127 regularly and post the result on the web. The Gnome upgrade currently
8128 work, while the KDE upgrade fail because of the bug in
8129 kdebase-workspace-data
</p
>
8131 <p
>I am not quite sure what kind of extract from the huge upgrade logs
8132 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
8133 post, so I will refrain from trying. I can report that for Gnome,
8134 aptitude report
760 packages upgraded,
448 newly installed,
129 to
8135 remove and
1 not upgraded and
1024MB need to be downloaded while for
8136 KDE the same numbers are
702 packages upgraded,
507 newly installed,
8137 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
8139 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
8140 is able to migrate to dependency based boot sequencing and parallel
8141 booting without a hitch. Was unsure if there were still bugs with
8142 packages failing to clean up their obsolete init.d script during
8143 upgrades, and no such problem seem to affect the Gnome desktop+laptop
8149 <title>Upstart or sysvinit - as init.d scripts see it
</title>
8150 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
8151 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
8152 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
8153 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
8154 scripts to migrate (some of) their operations to upstart job while
8155 keeping the init.d for hurd and kfreebsd. The packages with such
8156 needs will need a way to get their init.d scripts to behave
8157 differently when used with sysvinit and with upstart. Because of
8158 this, I had a look at the environment variables set when a init.d
8159 script is running under upstart, and when it is not.
</p
>
8161 <p
>With upstart, I notice these environment variables are set when a
8162 script is started from rcS.d/ (ignoring some irrelevant ones like
8165 <blockquote
><pre
>
8171 UPSTART_EVENTS=startup
8173 UPSTART_JOB=rc-sysinit
8174 </pre
></blockquote
>
8176 <p
>With sysvinit, these environment variables are set for the same
8179 <blockquote
><pre
>
8180 INIT_VERSION=sysvinit-
2.88
8185 </pre
></blockquote
>
8187 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
8188 sysvinit are not set by upstart. Not sure if it is intentional or not
8189 to not be compatible with sysvinit in this regard.
</p
>
8191 <p
>For scripts needing to behave differently when upstart is used,
8192 looking for the UPSTART_JOB environment variable seem to be a good
8198 <title>A manual for standards wars...
</title>
8199 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
8200 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
8201 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
8202 <description><p
>Via the
8203 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
8204 of Rob Weir
</a
> I came across the very interesting essay named
8205 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
8206 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
8207 following the standards wars of today.
</p
>
8212 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
8213 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
8214 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
8215 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
8216 <description><p
>When using sitesummary at a site to track machines, it is possible
8217 to get a list of the machine types in use thanks to the DMI
8218 information extracted from each machine. The script to do so is
8219 included in the sitesummary package, and here is example output from
8220 the Skolelinux build servers:
</p
>
8222 <blockquote
><pre
>
8223 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
8225 Dell Computer Corporation
1
8228 eserver xSeries
345 -[
8670M1X]-
1
8232 </pre
></blockquote
>
8234 <p
>The quality of the report depend on the quality of the DMI tables
8235 provided in each machine. Here there are Intel machines without model
8236 information listed with Intel as vendor and no model, and virtual Xen
8237 machines listed as [no-dmi-info]. One can add -l as a command line
8238 option to list the individual machines.
</p
>
8240 <p
>A larger list is
8241 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
8242 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
8243 provide the basic sitesummary report publicly. In their report there
8244 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
8245 their machines, and as sitesummary is available in both distributions,
8246 it is trivial to get all of them to report to the same central
8247 collector.
</p
>
8252 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
8253 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
8254 <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>
8255 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
8256 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
8257 start at boot when an NVidia video card is used is handled. The
8258 problem seem to be that the nvidia X.org driver uses a long time to
8259 initialize, and this duration is longer than kdm is configured to
8262 <p
>I came across two bugs related to this issue,
8263 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
8264 against initscripts and passed on to nvidia-glx when it became obvious
8265 that the nvidia drivers were involved, and
8266 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
8267 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
8269 <p
>To me, it seem that no-one is interested in actually solving the
8270 problem nvidia video card owners experience and make sure the Debian
8271 distribution work out of the box for these users. The nvidia driver
8272 maintainers expect kdm to be set up to wait longer, while kdm expect
8273 the nvidia driver maintainers to fix the driver to start faster, and
8274 while they wait for each other I guess the users end up switching to a
8275 distribution that work for them. I have no idea what the solution is,
8276 but I am pretty sure that waiting for each other is not it.
</p
>
8278 <p
>I wonder why we end up handling bugs this way.
</p
>
8283 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
8284 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
8285 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
8286 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
8287 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
8288 The feature seem to hold up pretty well, but three fairly serious
8289 issues are known and should be solved:
8293 <li
>The wicd package seen to
8294 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
8295 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
8296 parallel booting is enabled. No idea why, but the wicd maintainer
8297 seem to be on the case.
</li
>
8299 <li
>The nvidia X driver seem to
8300 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
8301 triggered more easily when parallel booting is in effect. The
8302 maintainer is on the case.
</li
>
8304 <li
>The sysv-rc package fail to properly enable dependency based boot
8305 sequencing (the shutdown is broken) when old file-rc users
8306 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
8307 sysv-rc. One way to solve it would be for file-rc to create
8308 /etc/init.d/.legacy-bootordering, and another is to try to make
8309 sysv-rc more robust. Will investigate some more and probably upload a
8310 workaround in sysv-rc to help those trying to move from file-rc to
8311 sysv-rc get a working shutdown.
</li
>
8313 </ul
></p
>
8315 <p
>All in all not many surprising issues, and all of them seem
8316 solvable before Squeeze is released. In addition to these there are
8317 some packages with bugs in their dependencies and run level settings,
8318 which I expect will be fixed in a reasonable time span.
</p
>
8320 <p
>If you report any problems with dependencies in init.d scripts to
8321 the BTS, please usertag the report to get it to show up at
8322 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8323 list of usertagged bugs related to this
</a
>.
</p
>
8325 <p
>Update: Correct bug number to file-rc issue.
</p
>
8330 <title>More flexible firmware handling in debian-installer
</title>
8331 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
8332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
8333 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
8334 <description><p
>After a long break from debian-installer development, I finally
8335 found time today to return to the project. Having to spend less time
8336 working dependency based boot in debian, as it is almost complete now,
8337 definitely helped freeing some time.
</p
>
8339 <p
>A while back, I ran into a problem while working on Debian Edu. We
8340 include some firmware packages on the Debian Edu CDs, those needed to
8341 get disk and network controllers working. Without having these
8342 firmware packages available during installation, it is impossible to
8343 install Debian Edu on the given machine, and because our target group
8344 are non-technical people, asking them to provide firmware packages on
8345 an external medium is a support pain. Initially, I expected it to be
8346 enough to include the firmware packages on the CD to get
8347 debian-installer to find and use them. This proved to be wrong.
8348 Next, I hoped it was enough to symlink the relevant firmware packages
8349 to some useful location on the CD (tried /cdrom/ and
8350 /cdrom/firmware/). This also proved to not work, and at this point I
8351 found time to look at the debian-installer code to figure out what was
8352 going to work.
</p
>
8354 <p
>The firmware loading code is in the hw-detect package, and a closer
8355 look revealed that it would only look for firmware packages outside
8356 the installation media, so the CD was never checked for firmware
8357 packages. It would only check USB sticks, floppies and other
8358 "external
" media devices. Today I changed it to also look in the
8359 /cdrom/firmware/ directory on the mounted CD or DVD, which should
8360 solve the problem I ran into with Debian edu. I also changed it to
8361 look in /firmware/, to make sure the installer also find firmware
8362 provided in the initrd when booting the installer via PXE, to allow us
8363 to provide the same feature in the PXE setup included in Debian
8366 <p
>To make sure firmware deb packages with a license questions are not
8367 activated without asking if the license is accepted, I extended
8368 hw-detect to look for preinst scripts in the firmware packages, and
8369 run these before activating the firmware during installation. The
8370 license question is asked using debconf in the preinst, so this should
8371 solve the issue for the firmware packages I have looked at so far.
</p
>
8373 <p
>If you want to discuss the details of these features, please
8374 contact us on debian-boot@lists.debian.org.
</p
>
8379 <title>Parallellized boot is now the default in Debian/unstable
</title>
8380 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
8381 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
8382 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
8383 <description><p
>Since this evening, parallel booting is the default in
8384 Debian/unstable for machines using dependency based boot sequencing.
8385 Apparently the testing of concurrent booting has been wider than
8386 expected, if I am to believe the
8387 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
8388 on debian-devel@
</a
>, and I concluded a few days ago to move forward
8389 with the feature this weekend, to give us some time to detect any
8390 remaining problems before Squeeze is frozen. If serious problems are
8391 detected, it is simple to change the default back to sequential boot.
8392 The upload of the new sysvinit package also activate a new upstream
8395 More information about
8396 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8397 based boot sequencing
</a
> is available from the Debian wiki. It is
8398 currently possible to disable parallel booting when one run into
8399 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
8401 <blockquote
><pre
>
8403 </pre
></blockquote
>
8405 <p
>If you report any problems with dependencies in init.d scripts to
8406 the BTS, please usertag the report to get it to show up at
8407 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8408 list of usertagged bugs related to this
</a
>.
</p
>
8413 <title>Sitesummary tip: Listing MAC address of all clients
</title>
8414 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
8415 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
8416 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
8417 <description><p
>In the recent Debian Edu versions, the
8418 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
8419 system
</a
> is used to keep track of the machines in the school
8420 network. Each machine will automatically report its status to the
8421 central server after boot and once per night. The network setup is
8422 also reported, and using this information it is possible to get the
8423 MAC address of all network interfaces in the machines. This is useful
8424 to update the DHCP configuration.
</p
>
8426 <p
>To give some idea how to use sitesummary, here is a one-liner to
8427 ist all MAC addresses of all machines reporting to sitesummary. Run
8428 this on the collector host:
</p
>
8430 <blockquote
><pre
>
8431 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
8432 </pre
></blockquote
>
8434 <p
>This will list all MAC addresses assosiated with all machine, one
8435 line per machine and with space between the MAC addresses.
</p
>
8437 <p
>To allow system administrators easier job at adding static DHCP
8438 addresses for hosts, it would be possible to extend this to fetch
8439 machine information from sitesummary and update the DHCP and DNS
8440 tables in LDAP using this information. Such tool is unfortunately not
8441 written yet.
</p
>
8446 <title>systemd, an interesting alternative to upstart
</title>
8447 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
8448 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
8449 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
8450 <description><p
>The last few days a new boot system called
8451 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
8453 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
8455 to the free software world. I have not yet had time to play around
8456 with it, but it seem to be a very interesting alternative to
8457 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
8458 a good alternative for Debian when we are able to switch to an event
8459 based boot system. Tollef is
8460 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
8461 systemd into Debian, and I look forward to seeing how well it work. I
8462 like the fact that systemd handles init.d scripts with dependency
8463 information natively, allowing them to run in parallel where upstart
8464 at the moment do not.
</p
>
8466 <p
>Unfortunately do systemd have the same problem as upstart regarding
8467 platform support. It only work on recent Linux kernels, and also need
8468 some new kernel features enabled to function properly. This means
8469 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8470 system. Not sure how that will be handled if systemd proves to be the
8471 way forward.
</p
>
8473 <p
>In the mean time, based on the
8474 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
8475 on debian-devel@
</a
> regarding parallel booting in Debian, I have
8476 decided to enable full parallel booting as the default in Debian as
8477 soon as possible (probably this weekend or early next week), to see if
8478 there are any remaining serious bugs in the init.d dependencies. A
8479 new version of the sysvinit package implementing this change is
8480 already in experimental. If all go well, Squeeze will be released
8481 with parallel booting enabled by default.
</p
>
8486 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
8487 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
8488 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
8489 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
8490 <description><p
>These days, the init.d script dependencies in Squeeze are quite
8491 complete, so complete that it is actually possible to run all the
8492 init.d scripts in parallell based on these dependencies. If you want
8493 to test your Squeeze system, make sure
8494 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8495 based boot sequencing
</a
> is enabled, and add this line to
8496 /etc/default/rcS:
</p
>
8498 <blockquote
><pre
>
8499 CONCURRENCY=makefile
8500 </pre
></blockquote
>
8502 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
8503 scripts in parallel using the dependency information stored in
8504 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8505 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8506 to try to start the kdm and gdm scripts as early as possible, and will
8507 start the facilities required by kdm or gdm as early as possible to
8508 make this happen.
</p
>
8510 <p
>Give it a try, and see if you like the result. If some services
8511 fail to start properly, it is most likely because they have incomplete
8512 init.d script dependencies in their startup script (or some of their
8513 dependent scripts have incomplete dependencies). Report bugs and get
8514 the package maintainers to fix it. :)
</p
>
8516 <p
>Running scripts in parallel could be the default in Debian when we
8517 manage to get the init.d script dependencies complete and correct. I
8518 expect we will get there in Squeeze+
1, if we get manage to test and
8519 fix the remaining issues.
</p
>
8521 <p
>If you report any problems with dependencies in init.d scripts to
8522 the BTS, please usertag the report to get it to show up at
8523 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
8524 list of usertagged bugs related to this
</a
>.
</p
>
8529 <title>Debian has switched to dependency based boot sequencing
</title>
8530 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
8531 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
8532 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
8533 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
8534 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
8535 have been migrated to using dependency based boot sequencing. This
8536 conclude work me and others have been doing for the last three days.
8537 It feels great to see this finally part of the default Debian
8538 installation. Now we just need to weed out the last few problems that
8539 are bound to show up, to get everything ready for Squeeze.
</p
>
8541 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
8542 fixing the more fundamental problem of handing the event based
8543 non-predictable kernel in the early boot.
</p
>
8548 <title>Taking over sysvinit development
</title>
8549 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
8550 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
8551 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
8552 <description><p
>After several years of frustration with the lack of activity from
8553 the existing sysvinit upstream developer, I decided a few weeks ago to
8554 take over the package and become the new upstream. The number of
8555 patches to track for the Debian package was becoming a burden, and the
8556 lack of synchronization between the distribution made it hard to keep
8557 the package up to date.
</p
>
8559 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8560 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
8561 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
8562 and Fedora), based on the patches currently in use in these
8563 distributions. We Debian maintainers plan to move to this tarball as
8564 the new upstream as soon as we find time to do the merge. Since the
8565 new tarball was created, we agreed with Werner at SuSe to make a new
8566 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
8567 development there. The project is registered and currently waiting
8568 for approval by the Savannah administrators, and as soon as it is
8569 approved, we will import the old versions from svn and continue
8570 working on the future release.
</p
>
8572 <p
>It is a bit ironic that this is done now, when some of the involved
8573 distributions are moving to upstart as a syvinit replacement.
</p
>
8578 <title>Debian boots quicker and quicker
</title>
8579 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
8580 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
8581 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
8582 <description><p
>I spent Monday and tuesday this week in London with a lot of the
8583 people involved in the boot system on Debian and Ubuntu, to see if we
8584 could find more ways to speed up the boot system. This was an Ubuntu
8586 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
8587 gathering
</a
>. It was quite productive. We also discussed the future
8588 of boot systems, and ways to handle the increasing number of boot
8589 issues introduced by the Linux kernel becoming more and more
8590 asynchronous and event base. The Ubuntu approach using udev and
8591 upstart might be a good way forward. Time will show.
</p
>
8593 <p
>Anyway, there are a few ways at the moment to speed up the boot
8594 process in Debian. All of these should be applied to get a quick
8599 <li
>Use dash as /bin/sh.
</li
>
8601 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
8602 clock is in UTC.
</li
>
8604 <li
>Install and activate the insserv package to enable
8605 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
8606 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
8610 These points are based on the Google summer of code work done by
8611 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
8614 <p
>Support for makefile-style concurrency during boot was uploaded to
8615 unstable yesterday. When we tested it, we were able to cut
6 seconds
8616 from the boot sequence. It depend on very correct dependency
8617 declaration in all init.d scripts, so I expect us to find edge cases
8618 where the dependences in some scripts are slightly wrong when we start
8619 using this.
</p
>
8621 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8622 introduced by Raphael Geissert today, one that could affect the
8623 startup speed as well. Instead of starting some scripts concurrently
8624 from rcS.d/ and another set of scripts from rc2.d/, it would be
8625 possible to run a of them in the same process. A quick way to test
8626 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
8627 insserv
'. Will need to test if that work. :)
</p
>
8632 <title>BSAs påstander om piratkopiering møter motstand
</title>
8633 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
8634 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
8635 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
8636 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
8637 programvareselskapene som Microsoft og Apple, publisert en rapport der
8638 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8639 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8641 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
8642 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
8643 dagene. Et spesielt interessant kommentar fra Sverige,
8644 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
8645 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
8648 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
8649 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8650 företag.
"Man bör nog kanske inte se de här siffrorna som helt
8651 exakta
", säger BSAs Sverigechef John Hugosson.
8654 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
8655 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
8656 piracy figures need a shot of reality
</a
> og
<a
8657 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
8658 Copyright Treaty Work?
</a
></p
>
8660 <p
>Fant lenkene via
<a
8661 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
8662 på Slashdot
</a
>.
</p
>
8667 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
8668 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
8669 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
8670 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
8671 <description><p
>Kom over
8672 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
8673 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8674 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8675 jobber til daglig. En rask opptelling forteller meg at vi har
490
8676 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
8677 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
8678 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
8683 <title>Kryptert harddisk - naturligvis
</title>
8684 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
8685 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
8686 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
8687 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
8688 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
8689 når en tar tap av arbeidstid, fortrolige dokumenter,
8690 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8691 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8692 til at jeg har kryptert harddisken på både kontormaskinen og min
8693 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8694 komme på avveie, den første informasjon relatert til jobben min ved
8695 Universitetet i Oslo, og den andre relatert til blant annet
8696 foreningsarbeide. Kryptering av diskene gjør at det er lite
8697 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8698 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8699 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8700 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8701 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8702 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8703 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8704 det er gjort slik jeg gjør det er minimale, og gevinstene er
8705 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8706 maskinen reinstalleres og alt er tapt.
</p
>
8708 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8709 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8710 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8711 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8712 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8713 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8714 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8715 betydelige.
</p
>
8720 <title>Two projects that have improved the quality of free software a lot
</title>
8721 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
8722 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
8723 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
8724 <description><p
>There are two software projects that have had huge influence on the
8725 quality of free software, and I wanted to mention both in case someone
8726 do not yet know them.
</p
>
8728 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
8729 tool to detect and expose errors in the memory handling of programs.
8730 It is easy to use, all one need to do is to run
'valgrind program
',
8731 and it will report any problems on stdout. It is even better if the
8732 program include debug information. With debug information, it is able
8733 to report the source file name and line number where the problem
8734 occurs. It can report things like
'reading past memory block in file
8735 X line N, the memory block was allocated in file Y, line M
', and
8736 'using uninitialised value in control logic
'. This tool has made it
8737 trivial to investigate reproducible crash bugs in programs, and have
8738 reduced the number of this kind of bugs in free software a lot.
8740 <p
>The second one is
8741 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
8742 a source code checker. It is able to process the source of a program
8743 and find problems in the logic without running the program. It
8744 started out as the Stanford Checker and became well known when it was
8745 used to find bugs in the Linux kernel. It is now a commercial tool
8746 and the company behind it is running
8747 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
8748 free software community, where a lot of free software projects get
8749 their source checked for free. Several thousand defects have been
8750 found and fixed so far. It can find errors like
'lock L taken in file
8751 X line N is never released if exiting in line M
', or
'the code in file
8752 Y lines O to P can never be executed
'. The projects included in the
8753 community service project have managed to get rid of a lot of
8754 reliability problems thanks to Coverity.
</p
>
8756 <p
>I believe tools like this, that are able to automatically find
8757 errors in the source, are vital to improve the quality of software and
8758 make sure we can get rid of the crashing and failing software we are
8759 surrounded by today.
</p
>
8764 <title>No patch is not better than a useless patch
</title>
8765 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
8766 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
8767 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
8768 <description><p
>Julien Blache
8769 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
8770 patch is better than a useless patch
</a
>. I completely disagree, as a
8771 patch allow one to discuss a concrete and proposed solution, and also
8772 prove that the issue at hand is important enough for someone to spent
8773 time on fixing it. No patch do not provide any of these positive
8774 properties.
</p
>
8779 <title>Standardize on protocols and formats, not vendors and applications
</title>
8780 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
8781 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
8782 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
8783 <description><p
>Where I work at the University of Oslo, one decision stand out as a
8784 very good one to form a long lived computer infrastructure. It is the
8785 simple one, lost by many in todays computer industry: Standardize on
8786 open network protocols and open exchange/storage formats, not applications.
8787 Applications come and go, while protocols and files tend to stay, and
8788 thus one want to make it easy to change application and vendor, while
8789 avoiding conversion costs and locking users to a specific platform or
8790 application.
</p
>
8792 <p
>This approach make it possible to replace the client applications
8793 independently of the server applications. One can even allow users to
8794 use several different applications as long as they handle the selected
8795 protocol and format. In the normal case, only one client application
8796 is recommended and users only get help if they choose to use this
8797 application, but those that want to deviate from the easy path are not
8798 blocked from doing so.
</p
>
8800 <p
>It also allow us to replace the server side without forcing the
8801 users to replace their applications, and thus allow us to select the
8802 best server implementation at any moment, when scale and resouce
8803 requirements change.
</p
>
8805 <p
>I strongly recommend standardizing - on open network protocols and
8806 open formats, but I would never recommend standardizing on a single
8807 application that do not use open network protocol or open formats.
</p
>
8812 <title>Returning from Skolelinux developer gathering
</title>
8813 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
8814 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
8815 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
8816 <description><p
>I
'm sitting on the train going home from this weekends Debian
8817 Edu/Skolelinux development gathering. I got a bit done tuning the
8818 desktop, and looked into the dynamic service location protocol
8819 implementation avahi. It look like it could be useful for us. Almost
8820 30 people participated, and I believe it was a great environment to
8821 get to know the Skolelinux system. Walter Bender, involved in the
8822 development of the Sugar educational platform, presented his stuff and
8823 also helped me improve my OLPC installation. He also showed me that
8824 his Turtle Art application can be used in standalone mode, and we
8825 agreed that I would help getting it packaged for Debian. As a
8826 standalone application it would be great for Debian Edu. We also
8827 tried to get the video conferencing working with two OLPCs, but that
8828 proved to be too hard for us. The application seem to need more work
8829 before it is ready for me. I look forward to getting home and relax
8835 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
8836 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
8837 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
8838 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
8839 <description><p
>The state of standardized LDAP schemas on Linux is far from
8840 optimal. There is RFC
2307 documenting one way to store NIS maps in
8841 LDAP, and a modified version of this normally called RFC
2307bis, with
8842 some modifications to be compatible with Active Directory. The RFC
8843 specification handle the content of a lot of system databases, but do
8844 not handle DNS zones and DHCP configuration.
</p
>
8846 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
8847 we would like to store information about users, SMB clients/hosts,
8848 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8849 and LTSP configuration in LDAP. These objects have a lot in common,
8850 but with the current LDAP schemas it is not possible to have one
8851 object per entity. For example, one need to have at least three LDAP
8852 objects for a given computer, one with the SMB related stuff, one with
8853 DNS information and another with DHCP information. The schemas
8854 provided for DNS and DHCP are impossible to combine into one LDAP
8855 object. In addition, it is impossible to implement quick queries for
8856 netgroup membership, because of the way NIS triples are implemented.
8857 It just do not scale. I believe it is time for a few RFC
8858 specifications to cleam up this mess.
</p
>
8860 <p
>I would like to have one LDAP object representing each computer in
8861 the network, and this object can then keep the SMB (ie host key), DHCP
8862 (mac address/name) and DNS (name/IP address) settings in one place.
8863 It need to be efficently stored to make sure it scale well.
</p
>
8865 <p
>I would also like to have a quick way to map from a user or
8866 computer and to the net group this user or computer is a member.
</p
>
8868 <p
>Active Directory have done a better job than unix heads like myself
8869 in this regard, and the unix side need to catch up. Time to start a
8870 new IETF work group?
</p
>
8875 <title>Endelig er Debian Lenny gitt ut
</title>
8876 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
8877 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
8878 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
8879 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
8880 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
8881 Et langt steg videre for Debian-prosjektet, og en rekke nye
8882 programpakker blir nå tilgjengelig for de av oss som bruker den
8883 stabile utgaven av Debian. Neste steg er nå å få
8884 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
8885 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
8886 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8887 slippes løs på skolene. Takk til alle debian-utviklerne som har
8888 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8889 bootsekvens tilgjengelig i stabil utgave, vha pakken
8890 <tt
>insserv
</tt
>.
</p
>
8895 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
8896 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
8897 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
8898 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
8899 <description><p
>This weekend we had a small developer gathering for Debian Edu in
8900 Oslo. Most of Saturday was used for the general assemly for the
8901 member organization, but the rest of the weekend I used to tune the
8902 LTSP installation. LTSP now work out of the box on the
10-network.
8903 Acer Aspire One proved to be a very nice thin client, with both
8904 screen, mouse and keybard in a small box. Was working on getting the
8905 diskless workstation setup configured out of the box, but did not
8906 finish it before the weekend was up.
</p
>
8908 <p
>Did not find time to look at the
4 VGA cards in one box we got from
8909 the Brazilian group, so that will have to wait for the next
8910 development gathering. Would love to have the Debian Edu installer
8911 automatically detect and configure a multiseat setup when it find one
8912 of these cards.
</p
>
8917 <title>The sorry state of multimedia browser plugins in Debian
</title>
8918 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
8919 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
8920 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
8921 <description><p
>Recently I have spent some time evaluating the multimedia browser
8922 plugins available in Debian Lenny, to see which one we should use by
8923 default in Debian Edu. We need an embedded video playing plugin with
8924 control buttons to pause or stop the video, and capable of streaming
8925 all the multimedia content available on the web. The test results and
8926 notes are available on
8927 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
8928 Debian wiki
</a
>. I was surprised how few of the plugins are able to
8929 fill this need. My personal video player favorite, VLC, has a really
8930 bad plugin which fail on a lot of the test pages. A lot of the MIME
8931 types I would expect to work with any free software player (like
8932 video/ogg), just do not work. And simple formats like the
8933 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
8934 totem and vlc plugins. I hope the situation will improve soon. No
8935 wonder sites use the proprietary Adobe flash to play video.
</p
>
8937 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
8938 be the only one fitting our needs. :/
</p
>