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>New lsdvd release version
0.17 is ready
</title>
11 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
13 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
14 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
15 got a new set of developers a few weeks ago, after the original
16 developer decided to step down and pass the project to fresh blod.
17 This project is now maintained by Petter Reinholdtsen and Steve
20 <p
>I just wrapped up
21 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
22 new lsdvd release
</a
>, available in git or from
23 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
24 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
29 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
30 <li
>Check for garbage in the program chains, which indicate that a track is
31 non-existant, to work around additional copy protection
</li
>
32 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
33 <li
>Fix pallete display of first entry
</li
>
34 <li
>Fix include orders
</li
>
35 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
36 <li
>Fix the chapter count
</li
>
37 <li
>Make sure the array size and the array limit used when initialising
38 the palette size is the same.
</li
>
39 <li
>Fix array printing.
</li
>
40 <li
>Correct subsecond calculations.
</li
>
41 <li
>Add sector information to the output format.
</li
>
42 <li
>Clean up code to be closer to ANSI C and compile without warnings
43 with more GCC compiler warnings.
</li
>
47 <p
>This change bring together patches for lsdvd in use in various
48 Linux and Unix distributions, as well as patches submitted to the
49 project the last nine years. Please check it out. :)
</p
>
54 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
55 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
56 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
57 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
58 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
59 project
</a
> provide a Linux solution for schools, including a
60 powerful desktop with education software, a central server providing
61 web pages, user database, user home directories, central login and PXE
62 boot of both clients without disk and the installation to install Debian
63 Edu on machines with disk (and a few other services perhaps to small
64 to mention here). We in the Debian Edu team are currently working on
65 the Jessie based version, trying to get everything in shape before the
66 freeze, to avoid having to maintain our own package repository in the
68 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
69 status
</a
> can be seen on the Debian wiki, and there is still heaps of
70 work left. Some fatal problems block testing, breaking the installer,
71 but it is possible to work around these to get anyway. Here is a
72 recipe on how to get the installation limping along.
</p
>
74 <p
>First, download the test ISO via
75 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
76 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
78 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
79 The ISO build was broken on Tuesday, so we do not get a new ISO every
80 12 hours or so, but thankfully the ISO we already got we are able to
81 install with some tweaking.
</p
>
83 <p
>When you get to the Debian Edu profile question, go to tty2
84 (use Alt-Ctrl-F2), run
</p
>
86 <p
><blockquote
><pre
>
87 nano /usr/bin/edu-eatmydata-install
88 </pre
></blockquote
></p
>
90 <p
>and add
'exit
0' as the second line, disabling the eatmydata
91 optimization. Return to the installation, select the profile you want
92 and continue. Without this change, exim4-config will fail to install
93 due to a known bug in eatmydata.
</p
>
95 <p
>When you get the grub question at the end, answer /dev/sda (or if
96 this do not work, figure out what your correct value would be. All my
97 test machines need /dev/sda, so I have no advice if it do not fit
100 <p
>If you installed a profile including a graphical desktop, log in as
101 root after the initial boot from hard drive, and install the
102 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
103 or mate. If you want several desktop options, install more than one
104 metapackage. Once this is done, reboot and you should have a working
105 graphical login screen. This workaround should no longer be needed
106 once the education-tasks package version
1.801 enter testing in two
109 <p
>I believe the ISO build will start working on two days when the new
110 tasksel package enter testing and Steve McIntyre get a chance to
111 update the debian-cd git repository. The eatmydata, grub and desktop
112 issues are already fixed in unstable and testing, and should show up
113 on the ISO as soon as the ISO build start working again. Well the
114 eatmydata optimization is really just disabled. The proper fix
115 require an upload by the eatmydata maintainer applying the patch
116 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
117 The rest have proper fixes in unstable.
</p
>
119 <p
>I hope this get you going with the installation testing, as we are
120 quickly running out of time trying to get our Jessie based
121 installation ready before the distribution freeze in a month.
</p
>
126 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
127 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
128 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
129 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
130 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
131 to handle my fairly large DVD collection. It is a nice command line
132 tool to get details about a DVD, like title, tracks, track length,
133 etc, in XML, Perl or human readable format. But lsdvd have not seen
134 any new development since
2006 and had a few irritating bugs affecting
135 its use with some DVDs. Upstream seemed to be dead, and in January I
136 sent a small probe asking for a version control repository for the
137 project, without any reply. But I use it regularly and would like to
138 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
139 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
140 the project admin, and after getting a reply from him explaining that
141 he was no longer interested in the project, I asked if I could take
142 over. And yesterday, I became project admin.
</p
>
144 <p
>I
've been in touch with a Gentoo developer and the Debian
145 maintainer interested in joining forces to maintain the upstream
146 project, and I hope we can get a new release out fairly quickly,
147 collecting the patches spread around on the internet into on place.
148 I
've added the relevant Debian patches to the freshly created git
149 repository, and expect the Gentoo patches to make it too. If you got
150 a DVD collection and care about command line tools, check out
151 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
152 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
153 list
</a
>. :)
</p
>
158 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
159 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
160 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
161 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
162 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
163 a lot quicker. When we install more than
2000 packages in
164 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
165 tasksel in the installer, unpacking the binary packages take forever.
166 A part of the slow I/O issue was discussed in
167 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
168 much file system sync-ing done by dpkg, which is the package
169 responsible for unpacking the binary packages. Other parts (like code
170 executed by postinst scripts) might also sync to disk during
171 installation. All this sync-ing to disk do not really make sense to
172 me. If the machine crash half-way through, I start over, I do not try
173 to salvage the half installed system. So the failure sync-ing is
174 supposed to protect against, hardware or system crash, is not really
175 relevant while the installer is running.
</p
>
177 <p
>A few days ago, I thought of a way to get rid of all the file
178 system sync()-ing in a fairly non-intrusive way, without the need to
179 change the code in several packages. The idea is not new, but I have
180 not heard anyone propose the approach using dpkg-divert before. It
181 depend on the small and clever package
182 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
183 uses LD_PRELOAD to replace the system functions for syncing data to
184 disk with functions doing nothing, thus allowing programs to live
185 dangerous while speeding up disk I/O significantly. Instead of
186 modifying the implementation of dpkg, apt and tasksel (which are the
187 packages responsible for selecting, fetching and installing packages),
188 it occurred to me that we could just divert the programs away, replace
189 them with a simple shell wrapper calling
190 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
191 Two days ago I decided to test the idea, and wrapped up a simple
192 implementation for the Debian Edu udeb.
</p
>
194 <p
>The effect was stunning. In my first test it reduced the running
195 time of the pkgsel step (installing tasks) from
64 to less than
44
196 minutes (
20 minutes shaved off the installation) on an old Dell
197 Latitude D505 machine. I am not quite sure what the optimised time
198 would have been, as I messed up the testing a bit, causing the debconf
199 priority to get low enough for two questions to pop up during
200 installation. As soon as I saw the questions I moved the installation
201 along, but do not know how long the question were holding up the
202 installation. I did some more measurements using Debian Edu Jessie,
203 and got these results. The time measured is the time stamp in
204 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
205 "pkgsel: finishing up
" lines, if you want to do the same measurement
206 yourself. In Debian Edu, the tasksel dialog do not show up, and the
207 timing thus do not depend on how quickly the user handle the tasksel
210 <p
><table
>
213 <th
>Machine/setup
</th
>
214 <th
>Original tasksel
</th
>
215 <th
>Optimised tasksel
</th
>
216 <th
>Reduction
</th
>
220 <td
>Latitude D505 Main+LTSP LXDE
</td
>
221 <td
>64 min (
07:
46-
08:
50)
</td
>
222 <td
><44 min (
11:
27-
12:
11)
</td
>
223 <td
>>20 min
18%
</td
>
227 <td
>Latitude D505 Roaming LXDE
</td
>
228 <td
>57 min (
08:
48-
09:
45)
</td
>
229 <td
>34 min (
07:
43-
08:
17)
</td
>
230 <td
>23 min
40%
</td
>
234 <td
>Latitude D505 Minimal
</td
>
235 <td
>22 min (
10:
37-
10:
59)
</td
>
236 <td
>11 min (
11:
16-
11:
27)
</td
>
237 <td
>11 min
50%
</td
>
241 <td
>Thinkpad X200 Minimal
</td
>
242 <td
>6 min (
08:
19-
08:
25)
</td
>
243 <td
>4 min (
08:
04-
08:
08)
</td
>
244 <td
>2 min
33%
</td
>
248 <td
>Thinkpad X200 Roaming KDE
</td
>
249 <td
>19 min (
09:
21-
09:
40)
</td
>
250 <td
>15 min (
10:
25-
10:
40)
</td
>
251 <td
>4 min
21%
</td
>
254 </table
></p
>
256 <p
>The test is done using a netinst ISO on a USB stick, so some of the
257 time is spent downloading packages. The connection to the Internet
258 was
100Mbit/s during testing, so downloading should not be a
259 significant factor in the measurement. Download typically took a few
260 seconds to a few minutes, depending on the amount of packages being
263 <p
>The speedup is implemented by using two hooks in
264 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
265 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
266 finish-install.d hook to remove the divert at the end of the
267 installation. I picked the pre-pkgsel.d hook instead of the
268 post-base-installer.d hook because I test using an ISO without the
269 eatmydata package included, and the post-base-installer.d hook in
270 Debian Edu can only operate on packages included in the ISO. The
271 negative effect of this is that I am unable to activate this
272 optimization for the kernel installation step in d-i. If the code is
273 moved to the post-base-installer.d hook, the speedup would be larger
274 for the entire installation.
</p
>
276 <p
>I
've implemented this in the
277 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
278 git repository, and plan to provide the optimization as part of the
279 Debian Edu installation. If you want to test this yourself, you can
280 create two files in the installer (or in an udeb). One shell script
281 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
283 <p
><blockquote
><pre
>
286 . /usr/share/debconf/confmodule
288 logger -t my-pkgsel
"info: $*
"
291 logger -t my-pkgsel
"error: $*
"
294 apt-install eatmydata || true
295 if [ -x /target/usr/bin/eatmydata ] ; then
296 for bin in dpkg apt-get aptitude tasksel ; do
298 # Test that the file exist and have not been diverted already.
299 if [ -f /target$file ] ; then
300 info
"diverting $file using eatmydata
"
301 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
302 > /target$file.edu
303 chmod
755 /target$file.edu
304 in-target dpkg-divert --package debian-edu-config \
305 --rename --quiet --add $file
306 ln -sf ./$bin.edu /target$file
308 error
"unable to divert $file, as it is missing.
"
312 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
317 </pre
></blockquote
></p
>
319 <p
>To clean up, another shell script should go into
320 /usr/lib/finish-install.d/ with code like this:
322 <p
><blockquote
><pre
>
324 . /usr/share/debconf/confmodule
326 logger -t my-finish-install
"error: $@
"
328 remove_install_override() {
329 for bin in dpkg apt-get aptitude tasksel ; do
331 if [ -x /target$file.edu ] ; then
333 in-target dpkg-divert --package debian-edu-config \
334 --rename --quiet --remove $file
337 error
"Missing divert for $file.
"
340 sync # Flush file buffers before continuing
343 remove_install_override
344 </pre
></blockquote
></p
>
346 <p
>In Debian Edu, I placed both code fragments in a separate script
347 edu-eatmydata-install and call it from the pre-pkgsel.d and
348 finish-install.d scripts.
</p
>
350 <p
>By now you might ask if this change should get into the normal
351 Debian installer too? I suspect it should, but am not sure the
352 current debian-installer coordinators find it useful enough. It also
353 depend on the side effects of the change. I
'm not aware of any, but I
354 guess we will see if the change is safe after some more testing.
355 Perhaps there is some package in Debian depending on sync() and
356 fsync() having effect? Perhaps it should go into its own udeb, to
357 allow those of us wanting to enable it to do so without affecting
360 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
361 will break installation of all programs using gnutls because of
362 <a href=
"https://bugs.debian.org/
702711">bug #
702711. An updated
363 eatmydata package in Debian will solve it.
</p
>
368 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
369 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
370 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
371 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
372 <description><p
>Yesterday, I had the pleasure of attending a talk with the
373 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
374 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
375 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
376 learn that there is a large set of publicly available key servers to
377 use when looking for peoples public key. So far I have used
378 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
379 were misbehaving, but those days are ended. The servers I have used
380 up until yesterday have been slow and some times unavailable. I hope
381 those problems are gone now.
</p
>
383 <p
>Behind the round robin DNS entry of the
384 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
385 there is a pool of more than
100 keyservers which are checked every
386 day to ensure they are well connected and up to date. It must be
387 better than what I have used so far. :)
</p
>
389 <p
>Yesterdays speaker told me that the service is the default
390 keyserver provided by the default configuration in GnuPG, but this do
391 not seem to be used in Debian. Perhaps it should?
</p
>
393 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
396 <p
><blockquote
><pre
>
397 keyserver pool.sks-keyservers.net
398 </pre
></blockquote
></p
>
400 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
401 entries in DNS. Just for fun, I did just that at work, so now every
402 user of GnuPG at the University of Oslo should find a OpenGPG
403 keyserver automatically should their need it:
</p
>
405 <p
><blockquote
><pre
>
406 % host -t srv _pgpkey-http._tcp.uio.no
407 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
409 </pre
></blockquote
></p
>
412 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
413 HKP lookup protocol
</a
> supported finding signature paths, I would be
414 very happy. It can look up a given key or search for a user ID, but I
415 normally do not want that, but to find a trust path from my key to
416 another key. Given a user ID or key ID, I would like to find (and
417 download) the keys representing a signature path from my key to the
418 key in question, to be able to get a trust path between the two keys.
419 This is as far as I can tell not possible today. Perhaps something
420 for a future version of the protocol?
</p
>
425 <title>From English wiki to translated PDF and epub via Docbook
</title>
426 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
427 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
428 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
429 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
430 project
</a
> provide an instruction manual for teachers, system
431 administrators and other users that contain useful tips for setting up
432 and maintaining a Debian Edu installation. This text is about how the
433 text processing of this manual is handled in the project.
</p
>
435 <p
>One goal of the project is to provide information in the native
436 language of its users, and for this we need to handle translations.
437 But we also want to make sure each language contain the same
438 information, so for this we need a good way to keep the translations
439 in sync. And we want it to be easy for our users to improve the
440 documentation, avoiding the need to learn special formats or tools to
441 contribute, and the obvious way to do this is to make it possible to
442 edit the documentation using a web browser. We also want it to be
443 easy for translators to keep the translation up to date, and give them
444 help in figuring out what need to be translated. Here is the list of
445 tools and the process we have found trying to reach all these
448 <p
>We maintain the authoritative source of our manual in the
449 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
450 wiki
</a
>, as several wiki pages written in English. It consist of one
451 front page with references to the different chapters, several pages
452 for each chapter, and finally one
"collection page
" gluing all the
453 chapters together into one large web page (aka
454 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
455 AllInOne page
</a
>). The AllInOne page is the one used for further
456 processing and translations. Thanks to the fact that the
457 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
458 wiki.debian.org support exporting pages in
459 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
460 the list of pages to export using the raw version of the AllInOne
461 page, loop over each of them to generate a Docbook XML version of the
462 manual. This process also download images and transform image
463 references to use the locally downloaded images. The generated
464 Docbook XML files are slightly broken, so some post-processing is done
465 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
466 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
467 a handfull of images. The XML file can now be used to generate PDF, HTML
468 and epub versions of the English manual. This is the basic step of
469 our process, making PDF (using dblatex), HTML (using xsltproc) and
470 epub (using dbtoepub) version from Docbook XML, and the resulting files
471 are placed in the debian-edu-doc-en binary package.
</p
>
473 <p
>But English documentation is not enough for us. We want translated
474 documentation too, and we want to make it easy for translators to
475 track the English original. For this we use the
476 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
477 which allow us to transform the English Docbook XML file into a
478 translation file (a .pot file), usable with the normal gettext based
479 translation tools used by those translating free software. The pot
480 file is used to create and maintain translation files (several .po
481 files), which the translations update with the native language
482 translations of all titles, paragraphs and blocks of text in the
483 original. The next step is combining the original English Docbook XML
484 and the translation file (say debian-edu-wheezy-manual.nb.po), to
485 create a translated Docbook XML file (in this case
486 debian-edu-wheezy-manual.nb.xml). This translated (or partly
487 translated, if the translation is not complete) Docbook XML file can
488 then be used like the original to create a PDF, HTML and epub version
489 of the documentation.
</p
>
491 <p
>The translators use different tools to edit the .po files. We
493 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
494 while some use emacs and vi, others can use web based editors like
495 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
496 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
497 is where the .po file end up, in our git repository. Updated
498 translations can either be committed directly to git, or submitted as
499 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
500 against the debian-edu-doc package
</a
>.
</p
>
502 <p
>One challenge is images, which both might need to be translated (if
503 they show translated user applications), and are needed in different
504 formats when creating PDF and HTML versions (epub is a HTML version in
505 this regard). For this we transform the original PNG images to the
506 needed density and format during build, and have a way to provide
507 translated images by storing translated versions in
508 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
509 package maintainers know more.
</p
>
511 <p
>If you wonder what the result look like, we provide
512 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
513 of the documentation packages on the web
</a
>. See for example the
514 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
515 PDF version
</a
> or the
516 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
517 HTML version
</a
>. We do not yet build the epub version by default,
518 but perhaps it will be done in the future.
</p
>
520 <p
>To learn more, check out
521 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
522 debian-edu-doc package
</a
>,
523 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
524 manual on the wiki
</a
> and
525 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
526 translation instructions
</a
> in the manual.
</p
>
531 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
532 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
533 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
534 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
535 <description><p
>It would be nice if it was easier in Debian to get all the hardware
536 related packages relevant for the computer installed automatically.
537 So I implemented one, using
538 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
539 package
</a
>. To use it, install the tasksel and isenkram packages and
540 run tasksel as user root. You should be presented with a new option,
541 "Hardware specific packages (autodetected by isenkram)
". When you
542 select it, tasksel will install the packages isenkram claim is fit for
543 the current hardware, hot pluggable or not.
<p
>
545 <p
>The implementation is in two files, one is the tasksel menu entry
546 description, and the other is the script used to extract the list of
547 packages to install. The first part is in
548 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
551 <p
><blockquote
><pre
>
554 Description: Hardware specific packages (autodetected by isenkram)
555 Based on the detected hardware various hardware specific packages are
557 Test-new-install: mark show
559 Packages: for-current-hardware
560 </pre
></blockquote
></p
>
562 <p
>The second part is in
563 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
566 <p
><blockquote
><pre
>
571 isenkram-autoinstall-firmware -l
573 </pre
></blockquote
></p
>
575 <p
>All in all, a very short and simple implementation making it
576 trivial to install the hardware dependent package we all may want to
577 have installed on our machines. I
've not been able to find a way to
578 get tasksel to tell you exactly which packages it plan to install
579 before doing the installation. So if you are curious or careful,
580 check the output from the isenkram-* command line tools first.
</p
>
582 <p
>The information about which packages are handling which hardware is
583 fetched either from the isenkram package itself in
584 /usr/share/isenkram/, from git.debian.org or from the APT package
585 database (using the Modaliases header). The APT package database
586 parsing have caused a nasty resource leak in the isenkram daemon (bugs
587 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
588 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
589 the python-apt code (bug
590 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
591 workaround I was able to get rid of the file descriptor leak and
592 reduce the memory leak from ~
30 MiB per hardware detection down to
593 around
2 MiB per hardware detection. It should make the desktop
594 daemon a lot more useful. The fix is in version
0.7 uploaded to
595 unstable today.
</p
>
597 <p
>I believe the current way of mapping hardware to packages in
598 Isenkram is is a good draft, but in the future I expect isenkram to
599 use the AppStream data source for this. A proposal for getting proper
600 AppStream support into Debian is floating around as
601 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
602 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
603 project
</a
> will take place this summer to improve the situation. I
604 look forward to seeing the result, and welcome patches for isenkram to
605 start using the information when it is ready.
</p
>
607 <p
>If you want your package to map to some specific hardware, either
608 add a
"Xb-Modaliases
" header to your control file like I did in
609 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
610 package
</a
> or submit a bug report with the details to the isenkram
612 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
613 blog posts tagged isenkram
</a
> for details on the notation. I expect
614 the information will be migrated to AppStream eventually, but for the
615 moment I got no better place to store it.
</p
>
620 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
621 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
622 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
623 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
624 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
625 project
</a
> is working on providing the software and hardware to make
626 it easy for non-technical people to host their data and communication
627 at home, and being able to communicate with their friends and family
628 encrypted and away from prying eyes. It is still going strong, and
629 today a major mile stone was reached.
</p
>
631 <p
>Today, the last of the packages currently used by the project to
632 created the system images were accepted into Debian Unstable. It was
633 the freedombox-setup package, which is used to configure the images
634 during build and on the first boot. Now all one need to get going is
635 the build code from the freedom-maker git repository and packages from
636 Debian. And once the freedombox-setup package enter testing, we can
637 build everything directly from Debian. :)
</p
>
639 <p
>Some key packages used by Freedombox are
640 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
641 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
642 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
643 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
644 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
645 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
646 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
647 are plans to integrate more packages into the setup. User
648 documentation is maintained on the Debian wiki. Please
649 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
650 the manual
</a
> and help us improve it.
</p
>
652 <p
>To test for yourself and create boot images with the FreedomBox
653 setup, run this on a Debian machine using a user with sudo rights to
654 become root:
</p
>
657 sudo apt-get install git vmdebootstrap mercurial python-docutils \
658 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
660 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
662 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
663 </pre
></p
>
665 <p
>Root access is needed to run debootstrap and mount loopback
666 devices. See the README in the freedom-maker git repo for more
667 details on the build. If you do not want all three images, trim the
668 make line. Note that the virtualbox-image target is not really
669 virtualbox specific. It create a x86 image usable in kvm, qemu,
670 vmware and any other x86 virtual machine environment. You might need
671 the version of vmdebootstrap in Jessie to get the build working, as it
672 include fixes for a race condition with kpartx.
</p
>
674 <p
>If you instead want to install using a Debian CD and the preseed
675 method, boot a Debian Wheezy ISO and use this boot argument to load
676 the preseed values:
</p
>
679 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
680 </pre
></p
>
682 <p
>I have not tested it myself the last few weeks, so I do not know if
683 it still work.
</p
>
685 <p
>If you wonder how to help, one task you could look at is using
686 systemd as the boot system. It will become the default for Linux in
687 Jessie, so we need to make sure it is usable on the Freedombox. I did
688 a simple test a few weeks ago, and noticed dnsmasq failed to start
689 during boot when using systemd. I suspect there are other problems
690 too. :) To detect problems, there is a test suite included, which can
691 be run from the plinth web interface.
</p
>
693 <p
>Give it a go and let us know how it goes on the mailing list, and help
694 us get the new release published. :) Please join us on
695 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
696 irc.debian.org)
</a
> and
697 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
698 mailing list
</a
> if you want to help make this vision come true.
</p
>
703 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
704 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
705 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
706 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
707 <description><p
>For a while now, I have been looking for a sensible offsite backup
708 solution for use at home. My requirements are simple, it must be
709 cheap and locally encrypted (in other words, I keep the encryption
710 keys, the storage provider do not have access to my private files).
711 One idea me and my friends had many years ago, before the cloud
712 storage providers showed up, was to use Google mail as storage,
713 writing a Linux block device storing blocks as emails in the mail
714 service provided by Google, and thus get heaps of free space. On top
715 of this one can add encryption, RAID and volume management to have
716 lots of (fairly slow, I admit that) cheap and encrypted storage. But
717 I never found time to implement such system. But the last few weeks I
718 have looked at a system called
719 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
720 mounted network backed file system with the features I need.
</p
>
722 <p
>S3QL is a fuse file system with a local cache and cloud storage,
723 handling several different storage providers, any with Amazon S3,
724 Google Drive or OpenStack API. There are heaps of such storage
725 providers. S3QL can also use a local directory as storage, which
726 combined with sshfs allow for file storage on any ssh server. S3QL
727 include support for encryption, compression, de-duplication, snapshots
728 and immutable file systems, allowing me to mount the remote storage as
729 a local mount point, look at and use the files as if they were local,
730 while the content is stored in the cloud as well. This allow me to
731 have a backup that should survive fire. The file system can not be
732 shared between several machines at the same time, as only one can
733 mount it at the time, but any machine with the encryption key and
734 access to the storage service can mount it if it is unmounted.
</p
>
736 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
737 package is included already. So to get started, run
<tt
>apt-get
738 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
739 Greenqloud, after reading their nice recipe on
740 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
741 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
742 in Iceland more than those in USA when it come to keeping my personal
743 data safe and private, and thus would rather spend money on a company
744 in Iceland. Another nice recipe is available from the article
745 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
746 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
747 Admin magazine. When the provider is picked, figure out how to get
748 the API key needed to connect to the storage API. With Greencloud,
749 the key did not show up until I had added payment details to my
752 <p
>Armed with the API access details, it is time to create the file
753 system. First, create a new bucket in the cloud. This bucket is the
754 file system storage area. I picked a bucket name reflecting the
755 machine that was going to store data there, but any name will do.
756 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
757 the API login and password, and a locally created password. Store it
758 all in ~root/.s3ql/authinfo2 like this:
760 <p
><blockquote
><pre
>
762 storage-url: s3c://s.greenqloud.com:
443/bucket-name
763 backend-login: API-login
764 backend-password: API-password
765 fs-passphrase: local-password
766 </pre
></blockquote
></p
>
768 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
769 but any sensible way to create a fairly random password should do it.
770 Armed with these details, it is now time to run mkfs, entering the API
771 details and password to create it:
</p
>
773 <p
><blockquote
><pre
>
774 # mkdir -m
700 /var/lib/s3ql-cache
775 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
776 --ssl s3c://s.greenqloud.com:
443/bucket-name
778 Enter backend password:
779 Before using S3QL, make sure to read the user
's guide, especially
780 the
'Important Rules to Avoid Loosing Data
' section.
781 Enter encryption password:
782 Confirm encryption password:
783 Generating random encryption key...
784 Creating metadata tables...
794 Compressing and uploading metadata...
795 Wrote
0.00 MB of compressed metadata.
796 #
</pre
></blockquote
></p
>
798 <p
>The next step is mounting the file system to make the storage available.
800 <p
><blockquote
><pre
>
801 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
802 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
803 Using
4 upload threads.
804 Downloading and decompressing metadata...
814 Mounting filesystem...
816 Filesystem Size Used Avail Use% Mounted on
817 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
819 </pre
></blockquote
></p
>
821 <p
>The file system is now ready for use. I use rsync to store my
822 backups in it, and as the metadata used by rsync is downloaded at
823 mount time, no network traffic (and storage cost) is triggered by
824 running rsync. To unmount, one should not use the normal umount
825 command, as this will not flush the cache to the cloud storage, but
826 instead running the umount.s3ql command like this:
828 <p
><blockquote
><pre
>
831 </pre
></blockquote
></p
>
833 <p
>There is a fsck command available to check the file system and
834 correct any problems detected. This can be used if the local server
835 crashes while the file system is mounted, to reset the
"already
836 mounted
" flag. This is what it look like when processing a working
837 file system:
</p
>
839 <p
><blockquote
><pre
>
840 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
841 Using cached metadata.
842 File system seems clean, checking anyway.
843 Checking DB integrity...
844 Creating temporary extra indices...
845 Checking lost+found...
846 Checking cached objects...
847 Checking names (refcounts)...
848 Checking contents (names)...
849 Checking contents (inodes)...
850 Checking contents (parent inodes)...
851 Checking objects (reference counts)...
852 Checking objects (backend)...
853 ..processed
5000 objects so far..
854 ..processed
10000 objects so far..
855 ..processed
15000 objects so far..
856 Checking objects (sizes)...
857 Checking blocks (referenced objects)...
858 Checking blocks (refcounts)...
859 Checking inode-block mapping (blocks)...
860 Checking inode-block mapping (inodes)...
861 Checking inodes (refcounts)...
862 Checking inodes (sizes)...
863 Checking extended attributes (names)...
864 Checking extended attributes (inodes)...
865 Checking symlinks (inodes)...
866 Checking directory reachability...
867 Checking unix conventions...
868 Checking referential integrity...
869 Dropping temporary indices...
870 Backing up old metadata...
880 Compressing and uploading metadata...
881 Wrote
0.89 MB of compressed metadata.
883 </pre
></blockquote
></p
>
885 <p
>Thanks to the cache, working on files that fit in the cache is very
886 quick, about the same speed as local file access. Uploading large
887 amount of data is to me limited by the bandwidth out of and into my
888 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
889 which is very close to my upload speed, and downloading the same
890 Debian installation ISO gave me
610 kiB/s, close to my download speed.
891 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
892 network, not the file system code. I do not know what a good cache
893 size would be, but suspect that the cache should e larger than your
894 working set.
</p
>
896 <p
>I mentioned that only one machine can mount the file system at the
897 time. If another machine try, it is told that the file system is
900 <p
><blockquote
><pre
>
901 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
902 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
903 Using
8 upload threads.
904 Backend reports that fs is still mounted elsewhere, aborting.
906 </pre
></blockquote
></p
>
908 <p
>The file content is uploaded when the cache is full, while the
909 metadata is uploaded once every
24 hour by default. To ensure the
910 file system content is flushed to the cloud, one can either umount the
911 file system, or ask S3QL to flush the cache and metadata using
914 <p
><blockquote
><pre
>
915 # s3qlctrl upload-meta /s3ql
916 # s3qlctrl flushcache /s3ql
918 </pre
></blockquote
></p
>
920 <p
>If you are curious about how much space your data uses in the
921 cloud, and how much compression and deduplication cut down on the
922 storage usage, you can use s3qlstat on the mounted file system to get
925 <p
><blockquote
><pre
>
927 Directory entries:
9141
930 Total data size:
22049.38 MB
931 After de-duplication:
21955.46 MB (
99.57% of total)
932 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
933 Database size:
2.39 MB (uncompressed)
934 (some values do not take into account not-yet-uploaded dirty blocks in cache)
936 </pre
></blockquote
></p
>
938 <p
>I mentioned earlier that there are several possible suppliers of
939 storage. I did not try to locate them all, but am aware of at least
940 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
941 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
942 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
943 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
944 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
945 accept payment in Bitcoin. Pick one that suit your need. Some of
946 them provide several GiB of free storage, but the prize models are
947 quite different and you will have to figure out what suits you
950 <p
>While researching this blog post, I had a look at research papers
951 and posters discussing the S3QL file system. There are several, which
952 told me that the file system is getting a critical check by the
953 science community and increased my confidence in using it. One nice
955 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
956 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
957 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
958 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
959 and Pamela Smith. Please have a look.
</p
>
961 <p
>Given my problems with different file systems earlier, I decided to
962 check out the mounted S3QL file system to see if it would be usable as
963 a home directory (in other word, that it provided POSIX semantics when
964 it come to locking and umask handling etc). Running
965 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
966 test code to check file system semantics
</a
>, I was happy to discover that
967 no error was found. So the file system can be used for home
968 directories, if one chooses to do so.
</p
>
970 <p
>If you do not want a locally file system, and want something that
971 work without the Linux fuse file system, I would like to mention the
972 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
973 provide locally encrypted backup using a command line client. It have
974 a nicer access control system, where one can split out read and write
975 access, allowing some systems to write to the backup and others to
976 only read from it.
</p
>
978 <p
>As usual, if you use Bitcoin and want to show your support of my
979 activities, please send Bitcoin donations to my address
980 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
985 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
986 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
987 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
988 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
989 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
990 project
</a
> is working on providing the software and hardware for
991 making it easy for non-technical people to host their data and
992 communication at home, and being able to communicate with their
993 friends and family encrypted and away from prying eyes. It has been
994 going on for a while, and is slowly progressing towards a new test
995 release (
0.2).
</p
>
997 <p
>And what day could be better than the Pi day to announce that the
998 new version will provide
"hard drive
" / SD card / USB stick images for
999 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1000 system), and can also be installed using a Debian installer preseed
1001 file. The Debian based Freedombox is now based on Debian Jessie,
1002 where most of the needed packages used are already present. Only one,
1003 the freedombox-setup package, is missing. To try to build your own
1004 boot image to test the current status, fetch the freedom-maker scripts
1006 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
1007 with a user with sudo access to become root:
1010 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1012 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1013 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1015 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1018 <p
>Root access is needed to run debootstrap and mount loopback
1019 devices. See the README for more details on the build. If you do not
1020 want all three images, trim the make line. But note that thanks to
<a
1021 href=
"https://bugs.debian.org/
741407">a race condition in
1022 vmdebootstrap
</a
>, the build might fail without the patch to the
1023 kpartx call.
</p
>
1025 <p
>If you instead want to install using a Debian CD and the preseed
1026 method, boot a Debian Wheezy ISO and use this boot argument to load
1027 the preseed values:
</p
>
1030 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
1033 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
1034 recently introduced bug in apt in Jessie
</a
>, the installer will
1035 currently hang while setting up APT sources. Killing the
1036 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
1037 installation will get the installation going. This affect all
1038 installations in Jessie, and I expect it will be fixed soon.
</p
>
1040 <p
>Give it a go and let us know how it goes on the mailing list, and help
1041 us get the new release published. :) Please join us on
1042 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
1043 irc.debian.org)
</a
> and
1044 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1045 mailing list
</a
> if you want to help make this vision come true.
</p
>
1050 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
1051 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
1052 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
1053 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
1054 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
1055 innetgr tools, because I needed them in
1056 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
1057 ng-utils, and it has served me well. I placed the project under the
1058 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
1059 repository. But many years ago, the CVS repository was dropped (lost,
1060 not migrated to new hardware, not sure), and the project have lacked a
1061 proper home since then.
</p
>
1063 <p
>Last summer, I had a look at the package and made a new release
1064 fixing a irritating crash bug, but was unable to store the changes in
1065 a proper source control system. I applied for a project on
1066 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
1067 to follow up on it. Until today. :)
</p
>
1069 <p
>After many hours of cleaning and migration, the ng-utils project
1070 now have a new home, and a git repository with the highlight of the
1071 history of the project. I published all release tarballs and imported
1072 them into the git repository. As the project is really stable and not
1073 expected to gain new features any time soon, I decided to make a new
1074 release and call it
1.0. Visit the new project home on
1075 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
1076 if you want to check it out. The new version is also uploaded into
1077 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
1082 <title>Testing sysvinit from experimental in Debian Hurd
</title>
1083 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
1084 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
1085 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
1086 <description><p
>A few days ago I decided to try to help the Hurd people to get
1087 their changes into sysvinit, to allow them to use the normal sysvinit
1088 boot system instead of their old one. This follow up on the
1089 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
1090 Google Summer of Code work
</a
> done last summer by Justus Winter to
1091 get Debian on Hurd working more like Debian on Linux. To get started,
1092 I downloaded a prebuilt hard disk image from
1093 <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
>,
1094 and started it using virt-manager.
</p
>
1096 <p
>The first think I had to do after logging in (root without any
1097 password) was to get the network operational. I followed
1098 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
1099 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
1100 commands as root to get the machine to accept a IP address from the
1101 kvm internal DHCP server:
</p
>
1103 <p
><blockquote
><pre
>
1104 settrans -fgap /dev/netdde /hurd/netdde
1105 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
1106 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
1108 </pre
></blockquote
></p
>
1110 <p
>After this, the machine had internet connectivity, and I could
1111 upgrade it and install the sysvinit packages from experimental and
1112 enable it as the default boot system in Hurd.
</p
>
1114 <p
>But before I did that, I set a password on the root user, as ssh is
1115 running on the machine it for ssh login to work a password need to be
1116 set. Also, note that a bug somewhere in openssh on Hurd block
1117 compression from working. Remember to turn that off on the client
1120 <p
>Run these commands as root to upgrade and test the new sysvinit
1123 <p
><blockquote
><pre
>
1124 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
1125 deb http://http.debian.net/debian/ experimental main
1128 apt-get dist-upgrade
1129 apt-get install -t experimental initscripts sysv-rc sysvinit \
1130 sysvinit-core sysvinit-utils
1131 update-alternatives --config runsystem
1132 </pre
></blockquote
></p
>
1134 <p
>To reboot after switching boot system, you have to use
1135 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
1136 yet a sysvinit process able to receive the signals from the normal
1137 'reboot
' command. After switching to sysvinit as the boot system,
1138 upgrading every package and rebooting, the network come up with DHCP
1139 after boot as it should, and the settrans/pkill hack mentioned at the
1140 start is no longer needed. But for some strange reason, there are no
1141 longer any login prompt in the virtual console, so I logged in using
1144 <p
>Note that there are some race conditions in Hurd making the boot
1145 fail some times. No idea what the cause is, but hope the Hurd porters
1146 figure it out. At least Justus said on IRC (#debian-hurd on
1147 irc.debian.org) that they are aware of the problem. A way to reduce
1148 the impact is to upgrade to the Hurd packages built by Justus by
1149 adding this repository to the machine:
</p
>
1151 <p
><blockquote
><pre
>
1152 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
1153 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1155 </pre
></blockquote
></p
>
1157 <p
>At the moment the prebuilt virtual machine get some packages from
1158 http://ftp.debian-ports.org/debian, because some of the packages in
1159 unstable do not yet include the required patches that are lingering in
1160 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
1162 <p
><blockquote
><pre
>
1163 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
1164 i emacs - GNU Emacs editor (metapackage)
1165 i gdb - GNU Debugger
1166 i hurd-recommended - Miscellaneous translators
1167 i isc-dhcp-client - ISC DHCP client
1168 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1169 i libc-bin - Embedded GNU C Library: Binaries
1170 i libc-dev-bin - Embedded GNU C Library: Development binaries
1171 i libc0.3 - Embedded GNU C Library: Shared libraries
1172 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1173 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1174 i multiarch-support - Transitional package to ensure multiarch compatibilit
1175 i A x11-common - X Window System (X.Org) infrastructure
1176 i xorg - X.Org X Window System
1177 i A xserver-xorg - X.Org X server
1178 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1180 </pre
></blockquote
></p
>
1182 <p
>All in all, testing hurd has been an interesting experience. :)
1183 X.org did not work out of the box and I never took the time to follow
1184 the porters instructions to fix it. This time I was interested in the
1185 command line stuff.
<p
>
1190 <title>New chrpath release
0.16</title>
1191 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
1192 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
1193 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
1194 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
1195 find problems in C, C++ and Java code using static source code
1196 analysis. It can detect a lot of different problems, and is very
1197 useful to find memory and locking bugs in the error handling part of
1198 the source. The company behind it provide
1199 <a href=
"https://scan.coverity.com/
">check of free software projects as
1200 a community service
</a
>, and many hundred free software projects are
1201 already checked. A few days ago I decided to have a closer look at
1202 the Coverity system, and discovered that the
1203 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
1204 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
1205 projects I am involved with was already registered. But these are
1206 fairly big, and I would also like to have a small and easy project to
1207 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
1208 checking of the chrpath project
</a
>. It was
1209 added to the checker and discovered seven potential defects. Six of
1210 these were real, mostly resource
"leak
" when the program detected an
1211 error. Nothing serious, as the resources would be released a fraction
1212 of a second later when the program exited because of the error, but it
1213 is nice to do it right in case the source of the program some time in
1214 the future end up in a library. Having fixed all defects and added
1215 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
1216 mailing list for the chrpath developers
</a
>, I decided it was time to
1217 publish a new release. These are the release notes:
</p
>
1219 <p
>New in
0.16 released
2014-
01-
14:
</p
>
1223 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
1224 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
1225 <li
>Mention new project mailing list in the documentation.
</li
>
1230 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
1231 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
1232 project if something is wrong with the new release. The test suite
1233 did not discover any old errors, so if you find a new one, please also
1234 include a test suite check.
</p
>
1239 <title>New chrpath release
0.15</title>
1240 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
1241 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
1242 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
1243 <description><p
>After many years break from the package and a vain hope that
1244 development would be continued by someone else, I finally pulled my
1245 acts together this morning and wrapped up a new release of chrpath,
1246 the command line tool to modify the rpath and runpath of already
1247 compiled ELF programs. The update was triggered by the persistence of
1248 Isha Vishnoi at IBM, which needed a new config.guess file to get
1249 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
1250 is working on. I checked the
1251 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
1252 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
1253 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
1254 packages for interesting patches (failed to find the source from
1255 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1256 These are the release notes:
</p
>
1258 <p
>New in
0.15 released
2013-
11-
24:
</p
>
1262 <li
>Updated config.sub and config.guess from the GNU project to work
1263 with newer architectures. Thanks to isha vishnoi for the heads
1266 <li
>Updated README with current URLs.
</li
>
1268 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1269 Matthias Klose.
</li
>
1271 <li
>Added missing help for -k|--keepgoing option, using patch by
1272 Petr Machata found in Fedora.
</li
>
1274 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
1275 .dynamic is a NULL terminated string. Based on patch found in
1276 Fedora credited Axel Thimm and Christian Krause.
</li
>
1281 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
1282 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
1283 project if something is wrong with the new release. The test suite
1284 did not discover any old errors, so if you find a new one, please also
1285 include a testsuite check.
</p
>
1290 <title>Debian init.d boot script example for rsyslog
</title>
1291 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
1292 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
1293 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
1294 <description><p
>If one of the points of switching to a new init system in Debian is
1295 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
1296 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
1297 init.d scripts at all. Here is an example init.d script, ie a rewrite
1298 of /etc/init.d/rsyslog:
</p
>
1300 <p
><pre
>
1301 #!/lib/init/init-d-script
1304 # Required-Start: $remote_fs $time
1305 # Required-Stop: umountnfs $time
1306 # X-Stop-After: sendsigs
1307 # Default-Start:
2 3 4 5
1308 # Default-Stop:
0 1 6
1309 # Short-Description: enhanced syslogd
1310 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1311 # It is quite compatible to stock sysklogd and can be
1312 # used as a drop-in replacement.
1314 DESC=
"enhanced syslogd
"
1315 DAEMON=/usr/sbin/rsyslogd
1316 </pre
></p
>
1318 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
1319 script was
137 lines, and the above is just
15 lines, most of it meta
1320 info/comments.
</p
>
1322 <p
>How to do this, you ask? Well, one create a new script
1323 /lib/init/init-d-script looking something like this:
1325 <p
><pre
>
1328 # Define LSB log_* functions.
1329 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
1330 # and status_of_proc is working.
1331 . /lib/lsb/init-functions
1334 # Function that starts the daemon/service
1340 #
0 if daemon has been started
1341 #
1 if daemon was already running
1342 #
2 if daemon could not be started
1343 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
1345 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1348 # Add code here, if necessary, that waits for the process to be ready
1349 # to handle requests from services started subsequently which depend
1350 # on this one. As a last resort, sleep for some time.
1354 # Function that stops the daemon/service
1359 #
0 if daemon has been stopped
1360 #
1 if daemon was already stopped
1361 #
2 if daemon could not be stopped
1362 # other if a failure occurred
1363 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
1364 RETVAL=
"$?
"
1365 [
"$RETVAL
" =
2 ]
&& return
2
1366 # Wait for children to finish too if this is a daemon that forks
1367 # and if the daemon is only ever run from this initscript.
1368 # If the above conditions are not satisfied then add some other code
1369 # that waits for the process to drop all resources that could be
1370 # needed by services started subsequently. A last resort is to
1371 # sleep for some time.
1372 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
1373 [
"$?
" =
2 ]
&& return
2
1374 # Many daemons don
't delete their pidfiles when they exit.
1376 return
"$RETVAL
"
1380 # Function that sends a SIGHUP to the daemon/service
1384 # If the daemon can reload its configuration without
1385 # restarting (for example, when it is sent a SIGHUP),
1386 # then implement that here.
1388 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
1393 scriptbasename=
"$(basename $
1)
"
1394 echo
"SN: $scriptbasename
"
1395 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
1396 script=
"$
1"
1403 NAME=$(basename $DAEMON)
1404 PIDFILE=/var/run/$NAME.pid
1406 # Exit if the package is not installed
1407 #[ -x
"$DAEMON
" ] || exit
0
1409 # Read configuration variable file if it is present
1410 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
1412 # Load the VERBOSE setting and other rcS variables
1415 case
"$
1" in
1417 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
1419 case
"$?
" in
1420 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
1421 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
1425 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
1427 case
"$?
" in
1428 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
1429 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
1433 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
1435 #reload|force-reload)
1437 # If do_reload() is not implemented then leave this commented out
1438 # and leave
'force-reload
' as an alias for
'restart
'.
1440 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
1444 restart|force-reload)
1446 # If the
"reload
" option is implemented then remove the
1447 #
'force-reload
' alias
1449 log_daemon_msg
"Restarting $DESC
" "$NAME
"
1451 case
"$?
" in
1454 case
"$?
" in
1456 1) log_end_msg
1 ;; # Old process is still running
1457 *) log_end_msg
1 ;; # Failed to start
1467 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
1473 </pre
></p
>
1475 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
1476 lot. I did not really polish the approach, so it might not always
1477 work out of the box, but you get the idea. I did not try very hard to
1478 optimize it nor make it more robust either.
</p
>
1480 <p
>A better argument for switching init system in Debian than reducing
1481 the size of init scripts (which is a good thing to do anyway), is to
1482 get boot system that is able to handle the kernel events sensibly and
1483 robustly, and do not depend on the boot to run sequentially. The boot
1484 and the kernel have not behaved sequentially in years.
</p
>
1489 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
1490 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
1491 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
1492 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
1493 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
1494 remote display access is the preferred solution with oVirt and RedHat
1495 Enterprise Virtualization, and I was sad to discover the other day
1496 that the browser plugin needed to use these systems seamlessly was
1497 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
1498 for a package
</a
> was from
2012-
04-
10 with no progress since
1499 2013-
04-
01, so I decided to wrap up a package based on the great work
1500 from Cajus Pollmeier and put it in a collab-maint maintained git
1501 repository to get a package I could use. I would very much like
1502 others to help me maintain the package (or just take over, I do not
1503 mind), but as no-one had volunteered so far, I just uploaded it to
1504 NEW. I hope it will be available in Debian in a few days.
</p
>
1506 <p
>The source is now available from
1507 <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
>
1512 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
1513 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
1514 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
1515 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
1516 <description><p
>The
1517 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
1518 program is a a very nice system to create virtual machine images. It
1519 create a image file, add a partition table, mount it and run
1520 debootstrap in the mounted directory to create a Debian system on a
1521 stick. Yesterday, I decided to try to teach it how to make images for
1522 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
1523 of a plan to simplify the build system for
1524 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
1525 project
</a
>. The FreedomBox project already uses vmdebootstrap for
1526 the virtualbox images, but its current build system made multistrap
1527 based system for Dreamplug images, and it is lacking support for
1528 Raspberry Pi.
</p
>
1530 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
1531 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1532 code and adjusted it to be able to build armel images on my amd64
1533 Debian laptop. I ended up giving vmdebootstrap five new options,
1534 allowing me to replicate the image creation process I use to make
1535 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
1536 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
1537 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
1538 call debootstrap with --foreign and to copy the handler into the
1539 generated chroot before running the second stage. This allow
1540 vmdebootstrap to create armel images on an amd64 host. Next I added
1541 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
1542 fstype
</tt
> to teach it to create a separate /boot/ partition with the
1543 given file system type, allowing me to create an image with a vfat
1544 partition for the /boot/ stuff. I also added a
<tt
>--variant
1545 variant
</tt
> option to allow me to create smaller images without the
1546 Debian base system packages installed. Finally, I added an option
1547 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
1548 as a boot loader. It is not needed on the Raspberry Pi and probably
1549 most other non-x86 architectures. The changes were accepted by the
1550 upstream author of vmdebootstrap yesterday and today, and is now
1552 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
1553 upstream project page
</a
>.
</p
>
1555 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
1556 create a small script (the customize script) to add the non-free
1557 binary blob needed to boot the Raspberry Pi and the APT source
1560 <p
><pre
>
1562 set -e # Exit on first error
1563 rootdir=
"$
1"
1564 cd
"$rootdir
"
1565 cat
&lt;
&lt;EOF
> etc/apt/sources.list
1566 deb http://http.debian.net/debian/ jessie main contrib non-free
1568 # Install non-free binary blob needed to boot Raspberry Pi. This
1569 # install a kernel somewhere too.
1570 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
1571 -O $rootdir/usr/bin/rpi-update
1572 chmod a+x $rootdir/usr/bin/rpi-update
1573 mkdir -p $rootdir/lib/modules
1574 touch $rootdir/boot/start.elf
1575 chroot $rootdir rpi-update
1576 </pre
></p
>
1578 <p
>Next, fetch the latest vmdebootstrap script and call it like this
1579 to build the image:
</p
>
1582 sudo ./vmdebootstrap \
1585 --distribution jessie \
1586 --mirror http://http.debian.net/debian \
1595 --root-password raspberry \
1596 --hostname raspberrypi \
1597 --foreign /usr/bin/qemu-arm-static \
1598 --customize `pwd`/customize \
1600 --package git-core \
1601 --package binutils \
1602 --package ca-certificates \
1605 </pre
></p
>
1607 <p
>The list of packages being installed are the ones needed by
1608 rpi-update to make the image bootable on the Raspberry Pi, with the
1609 exception of netbase, which is needed by debootstrap to find
1610 /etc/hosts with the minbase variant. I really wish there was a way to
1611 set up an Raspberry Pi using only packages in the Debian archive, but
1612 that is not possible as far as I know, because it boots from the GPU
1613 using a non-free binary blob.
</p
>
1615 <p
>The build host need debootstrap, kpartx and qemu-user-static and
1616 probably a few others installed. I have not checked the complete
1617 build dependency list.
</p
>
1619 <p
>The resulting image will not use the hardware floating point unit
1620 on the Raspberry PI, because the armel architecture in Debian is not
1621 optimized for that use. So the images created will be a bit slower
1622 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
1627 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
1628 <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>
1629 <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>
1630 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
1631 <description><p
>The last few days I came across a few good causes that should get
1632 wider attention. I recommend signing and donating to each one of
1635 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
1636 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
1637 Women program which is a Google Summer of Code like initiative to get
1638 more women involved in free software. One debian sponsor has offered
1639 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
1640 earmarked
</a
> for this initiative. I donated a few minutes ago, and
1641 hope you will to. :)
</p
>
1643 <p
>And the Electronic Frontier Foundation just announced plans to
1644 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
1645 documentaries about the excessive spying
</a
> on every Internet user that
1646 take place these days, and their need to fund the work. I
've already
1647 donated. Are you next?
</p
>
1649 <p
>For my Norwegian audience, the organisation Studentenes og
1650 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
1651 statement under the heading
1652 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
1653 Access
</a
> for those of us asking for more focus on open access in the
1654 Norwegian government. So far
499 signatures. I hope you will sign it
1660 <title>Videos about the Freedombox project - for inspiration and learning
</title>
1661 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
1662 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
1663 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
1664 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
1665 project
</a
> have been going on for a while, and have presented the
1666 vision, ideas and solution several places. Here is a little
1667 collection of videos of talks and presentation of the project.
</p
>
1671 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
1672 2,
5 minute marketing film
</a
> (Youtube)
</li
>
1674 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
1675 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
1677 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
1678 Freedom in the Cloud - Software Freedom, Privacy and and Security for
1679 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
1680 (Youtube)
</li
>
1682 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
1683 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
1685 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
1686 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
1688 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
1689 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
1690 York City in
2012</a
> (Youtube)
</li
>
1692 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
1693 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
1694 (Youtube)
</li
>
1696 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
1697 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
1699 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
1700 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
1702 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
1703 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
1704 2013</a
> (Youtube)
</li
>
1708 <p
>A larger list is available from
1709 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
1710 Freedombox Wiki
</a
>.
</p
>
1712 <p
>On other news, I am happy to report that Freedombox based on Debian
1713 Jessie is coming along quite well, and soon both Owncloud and using
1714 Tor should be available for testers of the Freedombox solution. :) In
1715 a few weeks I hope everything needed to test it is included in Debian.
1716 The withsqlite package is already in Debian, and the plinth package is
1717 pending in NEW. The third and vital part of that puzzle is the
1718 metapackage/setup framework, which is still pending an upload. Join
1719 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
1720 (#freedombox on irc.debian.org)
</a
> and
1721 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1722 mailing list
</a
> if you want to help make this vision come true.
</p
>
1727 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
1728 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
1729 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
1730 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
1731 <description><p
>I was introduced to the
1732 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
1733 in
2010, when Eben Moglen presented his vision about serving the need
1734 of non-technical people to keep their personal information private and
1735 within the legal protection of their own homes. The idea is to give
1736 people back the power over their network and machines, and return
1737 Internet back to its intended peer-to-peer architecture. Instead of
1738 depending on a central service, the Freedombox will give everyone
1739 control over their own basic infrastructure.
</p
>
1741 <p
>I
've intended to join the effort since then, but other tasks have
1742 taken priority. But this summers nasty news about the misuse of trust
1743 and privilege exercised by the
"western
" intelligence gathering
1744 communities increased my eagerness to contribute to a point where I
1745 actually started working on the project a while back.
</p
>
1747 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
1748 Debian initiative
</a
> based on the vision from Eben Moglen, is to
1749 create a simple and cheap Debian based appliance that anyone can hook
1750 up in their home and get access to secure and private services and
1751 communication. The initial deployment platform have been the
1752 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
1753 which is a piece of hardware I do not own. So to be able to test what
1754 the current Freedombox setup look like, I had to come up with a way to install
1755 it on some hardware I do have access to. I have rewritten the
1756 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
1757 image build framework to use .deb packages instead of only copying
1758 setup into the boot images, and thanks to this rewrite I am able to
1759 set up any machine supported by Debian Wheezy as a Freedombox, using
1760 the previously mentioned deb (and a few support debs for packages
1761 missing in Debian).
</p
>
1763 <p
>The current Freedombox setup consist of a set of bootstrapping
1765 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
1766 and a administrative web interface
1767 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
1768 withsqlite), as well as a privacy enhancing proxy based on
1769 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
1770 (freedombox-privoxy). There is also a web/javascript based XMPP
1771 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
1772 trying (unsuccessfully so far) to talk to the XMPP server
1773 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
1774 web interface is pluggable, and the goal is to use it to enable OpenID
1775 services, mesh network connectivity, use of TOR, etc, etc. Not much of
1776 this is really working yet, see
1777 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
1778 project TODO
</a
> for links to GIT repositories. Most of the code is
1779 on github at the moment. The HTTP proxy is operational out of the
1780 box, and the admin web interface can be used to add/remove plinth
1781 users. I
've not been able to do anything else with it so far, but
1782 know there are several branches spread around github and other places
1783 with lots of half baked features.
</p
>
1785 <p
>Anyway, if you want to have a look at the current state, the
1786 following recipes should work to give you a test machine to poke
1789 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
1793 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
1794 <li
>Boot from it, either as CD or USB stick.
</li
>
1795 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
1796 to the Debian installer:
<p
>
1797 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
1799 <li
>Answer the few language/region/password questions and pick disk to
1800 install on.
</li
>
1802 <li
>When the installation is finished and the machine have rebooted a
1803 few times, your Freedombox is ready for testing.
</li
>
1807 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
1811 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
1812 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
1813 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
1815 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
1816 </pre
></li
>
1817 <li
><p
>Run this as root:
</p
>
1819 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
1822 apt-get install freedombox-setup
1823 /usr/lib/freedombox/setup
1824 </pre
></li
>
1825 <li
>Reboot into your freshly created Freedombox.
</li
>
1829 <p
>You can test it on other architectures too, but because the
1830 freedombox-privoxy package is binary, it will only work as intended on
1831 the architectures where I have had time to build the binary and put it
1832 in my APT repository. But do not let this stop you. It is only a
1833 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
1835 <p
>Note that by default Freedombox is a DHCP server on the
1836 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
1837 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
1838 disable
</tt
>" as root.
</p
>
1840 <p
>Please let me know if this works for you, or if you have any
1841 problems. We gather on the IRC channel
1842 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
1843 irc.debian.org and the
1844 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
1845 mailing list
</a
>.
</p
>
1847 <p
>Once you get your freedombox operational, you can visit
1848 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
1849 welcome screen (dead end - do not be surprised if you are unable to
1850 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
1851 to look at the rest of plinth. The default user is
'admin
' and the
1852 default password is
'secret
'.
</p
>
1857 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
1858 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
1859 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
1860 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
1861 <description><p
>Earlier, I reported about
1862 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
1863 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
1864 told by IBM that the original disk should be thrown away. And as
1865 there no longer was a problem if I bricked the firmware, I decided
1866 today to try to install Intel firmware to replace the Lenovo firmware
1867 currently on the disk.
</p
>
1869 <p
>I searched the Intel site for firmware, and found
1870 <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
>
1871 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
1872 according to the site should contain the latest firmware for SSD
1873 disks. I inserted the broken disk in one of my spare laptops and
1874 booted the ISO from a USB stick. The disk was recognized, but the
1875 program claimed the newest firmware already were installed and refused
1876 to insert any Intel firmware. So no change, and the disk is still
1877 unable to handle write load. :( I guess the only way to get them
1878 working would be if Lenovo releases new firmware. No idea how likely
1879 that is. Anyway, just blogging about this test for completeness. I
1880 got a working Samsung disk, and see no point in spending more time on
1881 the broken disks.
</p
>
1886 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
1887 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
1888 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
1889 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
1890 <description><p
>Today I switched to
1891 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
1892 new laptop
</a
>. I
've previously written about the problems I had with
1893 my new Thinkpad X230, which was delivered with an
1894 <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
1895 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
1896 sustained writes. My hardware supplier have been very forthcoming in
1897 trying to find a solution, and after first trying with another
1898 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
1899 disk instead to fix it once and for all. The Samsung disk survived
1900 the installation of Debian with encrypted disks (filling the disk with
1901 random data during installation killed the first two), and I thus
1902 decided to trust it with my data. I have installed it as a Debian Edu
1903 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
1904 server at home using Kerberos and LDAP, and will use it as my work
1905 station from now on.
</p
>
1907 <p
>As this is a solid state disk with no moving parts, I believe the
1908 Debian Wheezy default installation need to be tuned a bit to increase
1909 performance and increase life time of the disk. The Linux kernel and
1910 user space applications do not yet adjust automatically to such
1911 environment. To make it easier for my self, I created a draft Debian
1912 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
1913 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
1914 for the ssd-setup package
</a
> is available from collab-maint, and it
1915 is set up to adjust the setup of the machine by just installing the
1916 package. If there is any non-SSD disk in the machine, the package
1917 will refuse to install, as I did not try to write any logic to sort
1918 file systems in SSD and non-SSD file systems.
</p
>
1920 <p
>I consider the package a draft, as I am a bit unsure how to best
1921 set up Debian Wheezy with an SSD. It is adjusted to my use case,
1922 where I set up the machine with one large encrypted partition (in
1923 addition to /boot), put LVM on top of this and set up partitions on
1924 top of this again. See the README file in the package source for the
1925 references I used to pick the settings. At the moment these
1926 parameters are tuned:
</p
>
1930 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
1931 (adding discard to /etc/crypttab)
</li
>
1933 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
1934 this case a cryptsetup partition) by changing issue_discards from
1935 0 to
1 in /etc/lvm/lvm.conf.
</li
>
1937 <li
>Set relatime as a file system option for ext3 and ext4 file
1940 <li
>Tell swap to use TRIM commands by adding
'discard
' to
1941 /etc/fstab.
</li
>
1943 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
1945 <li
>Run fstrim on every ext3 and ext4 file system every night (from
1946 cron.daily).
</li
>
1948 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
1949 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
1953 <p
>During installation, I cancelled the part where the installer fill
1954 the disk with random data, as this would kill the SSD performance for
1955 little gain. My goal with the encrypted file system is to ensure
1956 those stealing my laptop end up with a brick and not a working
1957 computer. I have no hope in keeping the really resourceful people
1958 from getting the data on the disk (see
1959 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
1960 Thus I concluded that adding the discard option to crypttab is the
1961 right thing to do.
</p
>
1963 <p
>I considered using the noop I/O scheduler, as several recommended
1964 it for SSD, but others recommended deadline and a benchmark I found
1965 indicated that deadline might be better for interactive use.
</p
>
1967 <p
>I also considered using the
'discard
' file system option for ext3
1968 and ext4, but read that it would give a performance hit ever time a
1969 file is removed, and thought it best to that that slowdown once a day
1970 instead of during my work.
</p
>
1972 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
1973 this is already done by Debian Edu.
</p
>
1975 <p
>I have not yet started on the user space tuning. I expect
1976 iceweasel need some tuning, and perhaps other applications too, but
1977 have not yet had time to investigate those parts.
</p
>
1979 <p
>The package should work on Ubuntu too, but I have not yet tested it
1982 <p
>As for the answer to the question in the title of this blog post,
1983 as far as I know, the only solution I know about is to replace the
1984 disk. It might be possible to flash it with Intel firmware instead of
1985 the Lenovo firmware. But I have not tried and did not want to do so
1986 without approval from Lenovo as I wanted to keep the warranty on the
1987 disk until a solution was found and they wanted the broken disks
1993 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
1994 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
1995 <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>
1996 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
1997 <description><p
>A few days ago, I wrote about
1998 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
1999 problems I experienced with my new X230 and its SSD disk
</a
>, which
2000 was dying during installation because it is unable to cope with
2001 sustained write. My supplier is in contact with
2002 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
2003 replacement disk to try to fix the problem. They decided to send an
2004 identical model, so my hopes for a permanent fix was slim.
</p
>
2006 <p
>Anyway, today I got the replacement disk and tried to install
2007 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2008 same firmware version as the original. This time my hope raised
2009 slightly as the installation progressed, as the original disk used to
2010 die after
4-
7% of the disk was written to, while this time it kept
2011 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
2012 died again and I was back on square one. I still do not have a new
2013 laptop with a disk I can trust. I can not live with a disk that might
2014 lock up when I download a new
2015 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
2016 other large files. I look forward to hearing from my supplier with
2017 the next proposal from Lenovo.
</p
>
2019 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
2020 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2021 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
2022 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
2023 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
2024 P/N
45N8295, P0C38732.
</p
>
2026 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
2027 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
2028 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
2029 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
2030 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
2031 P/N
45N8295, P0C38732.
</p
>
2033 <p
>The only difference is in the first number (serial number?), ISN,
2034 SA, date and WNPP values. Mentioning all the details here in case
2035 someone is able to use the information to find a way to identify the
2036 failing disk among working ones (if any such working disk actually
2042 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
2043 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
2044 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
2045 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
2046 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
2047 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2048 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
2049 member assosiation NUUG
</a
> and
2050 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
2051 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
2052 Bitraf
</a
>.
</p
>
2054 <p
>It starts
10:
00 and continue until late evening. Everyone is
2055 welcome, and there is no fee to participate. There is on the other
2056 hand limited space, and only room for
30 people. Please put your name
2057 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
2058 wiki page
</a
> if you plan to join us.
</p
>
2063 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
2064 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
2065 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
2066 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
2067 <description><p
>Half a year ago, I reported that I had to find a
2068 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
2069 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
2070 time to spend on it, and it took a while to find a model I believe
2071 will do the job, but two days ago the replacement finally arrived. I
2073 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
2074 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2075 a roaming workstation, and it seemed to work flawlessly. But my
2076 second installation with encrypted disk was not as successful. More
2077 on that below.
</p
>
2079 <p
>I had a hard time trying to track down a good laptop, as my most
2080 important requirements (robust and with a good keyboard) are never
2081 listed in the feature list. But I did get good help from the search
2082 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
2083 allowed me to limit the list of interesting laptops based on my other
2084 requirements. A bit surprising that SSD disk are not disks according
2085 to that search interface, so I had to drop specifying the number of
2086 disks from my search parameters. I also asked around among friends to
2087 get their impression on keyboards and robustness.
</p
>
2089 <p
>So the new laptop arrived, and it is quite a lot wider than the
2090 X41. I am not quite convinced about the keyboard, as it is
2091 significantly wider than my old keyboard, and I have to stretch my
2092 hand a lot more to reach the edges. But the key response is fairly
2093 good and the individual key shape is fairly easy to handle, so I hope
2094 I will get used to it. My old X40 was starting to fail, and I really
2095 needed a new laptop now. :)
</p
>
2097 <p
>Turning off the touch pad was simple. All it took was a quick
2098 visit to the BIOS during boot it disable it.
</p
>
2100 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
2101 lock up during load. And this happen when installing Debian Wheezy
2102 with encrypted disk, while the disk is being filled with random data.
2103 I also tested to install Ubuntu Raring, and it happen there too if I
2104 reenable the code to fill the disk with random data (it is disabled by
2105 default in Ubuntu). And the bug with is already known. It was
2106 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
2107 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
2108 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2109 kernel developers as
2110 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
2111 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
2112 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2113 Lenovo forums, both for
2114 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
2115 2012-
11-
10</a
> and for
2116 <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
2117 03-
20-
2013</a
>. The problem do not only affect installation. The
2118 reports state that the disk lock up during use if many writes are done
2119 on the disk, so it is much no use to work around the installation
2120 problem and end up with a computer that can lock up at any moment.
2122 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
2123 available
</a
> that will lock up the hard drive after running a few
2124 minutes by writing to a file.
</p
>
2126 <p
>I
've contacted my supplier and asked how to handle this, and after
2127 contacting PCHELP Norway (request
01D1FDP) which handle support
2128 requests for Lenovo, his first suggestion was to upgrade the disk
2129 firmware. Unfortunately there is no newer firmware available from
2130 Lenovo, as my disk already have the most recent one (version LF1i). I
2131 hope to hear more from him today and hope the problem can be
2137 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
2138 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
2139 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
2140 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
2141 <description><p
>Half a year ago, I reported that I had to find a replacement for my
2142 trusty old Thinkpad X41. Unfortunately I did not have much time to
2143 spend on it, but today the replacement finally arrived. I ended up
2144 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
2145 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
2146 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2147 this, it is installing what I hope will be a more final installation,
2148 with a encrypted hard drive to ensure any dope head stealing it end up
2149 with an expencive door stop.
</p
>
2151 <p
>I had a hard time trying to track down a good laptop, as my most
2152 important requirements (robust and with a good keyboard) are never
2153 listed in the feature list. But I did get good help from the search
2154 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
2155 allowed me to limit the list of interesting laptops based on my other
2156 requirements. A bit surprising that SSD disk are not disks, so I had
2157 to drop number of disks from my search parameters.
</p
>
2159 <p
>I am not quite convinced about the keyboard, as it is significantly
2160 wider than my old keyboard, and I have to stretch my hand a lot more
2161 to reach the edges. But the key response is fairly good and the
2162 individual key shape is fairly easy to handle, so I hope I will get
2163 used to it. My old X40 was starting to fail, and I really needed a
2164 new laptop now. :)
</p
>
2166 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
2171 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
2172 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
2173 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
2174 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
2175 <description><p
>It annoys me when the computer fail to do automatically what it is
2176 perfectly capable of, and I have to do it manually to get things
2177 working. One such task is to find out what firmware packages are
2178 needed to get the hardware on my computer working. Most often this
2179 affect the wifi card, but some times it even affect the RAID
2180 controller or the ethernet card. Today I pushed version
0.4 of the
2181 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
2182 including a new script isenkram-autoinstall-firmware handling the
2183 process of asking all the loaded kernel modules what firmware files
2184 they want, find debian packages providing these files and install the
2185 debian packages. Here is a test run on my laptop:
</p
>
2187 <p
><pre
>
2188 # isenkram-autoinstall-firmware
2189 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2190 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2191 info: locating packages with the requested firmware files
2192 info: Updating APT sources after adding non-free APT source
2193 info: trying to install firmware-ipw2x00
2196 Preconfiguring packages ...
2197 Selecting previously deselected package firmware-ipw2x00.
2198 (Reading database ...
259727 files and directories currently installed.)
2199 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2200 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
2202 </pre
></p
>
2204 <p
>When all the requested firmware is present, a simple message is
2205 printed instead:
</p
>
2207 <p
><pre
>
2208 # isenkram-autoinstall-firmware
2209 info: did not find any firmware files requested by loaded kernel modules. exiting
2211 </pre
></p
>
2213 <p
>It could use some polish, but it is already working well and saving
2214 me some time when setting up new machines. :)
</p
>
2216 <p
>So, how does it work? It look at the set of currently loaded
2217 kernel modules, and look up each one of them using modinfo, to find
2218 the firmware files listed in the module meta-information. Next, it
2219 download the Contents file from a nearby APT mirror, and search for
2220 the firmware files in this file to locate the package with the
2221 requested firmware file. If the package is in the non-free section, a
2222 non-free APT source is added and the package is installed using
2223 <tt
>apt-get install
</tt
>. The end result is a slightly better working
2226 <p
>I hope someone find time to implement a more polished version of
2227 this script as part of the hw-detect debian-installer module, to
2228 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
2229 #
655507</a
>. There really is no need to insert USB sticks with
2230 firmware during a PXE install when the packages already are available
2231 from the nearby Debian mirror.
</p
>
2236 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
2237 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
2238 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
2239 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
2240 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2241 the screen just turn black when Linux boot, either during installation
2242 or on first boot from the hard disk. I
've seen it once in a while the
2243 last few years, but only recently understood the cause. I
've seen it
2244 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2245 The reason seem to be in the wiring of some laptops. The system to
2246 control the screen background light is inverted, so when Linux try to
2247 turn the brightness fully on, it end up turning it off instead. I do
2248 not know which Linux drivers are affected, but this post is about the
2249 i915 driver used by the
2250 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
2251 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
2253 <p
>The problem can be worked around two ways. Either by adding
2254 i915.invert_brightness=
1 as a kernel option, or by adding a file in
2255 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
2256 option when it load the i915 kernel module. On Debian and Ubuntu, it
2257 can be done by running these commands as root:
</p
>
2260 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
2261 update-initramfs -u -k all
2264 <p
>Since March
2012 there is
2265 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
2266 mechanism in the Linux kernel
</a
> to tell the i915 driver which
2267 hardware have this problem, and get the driver to invert the
2268 brightness setting automatically. To use it, one need to add a row in
2269 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
2270 intel_quirks array
</a
> in the driver source
2271 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
2272 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
2273 number (vendor number
8086 is assumed) and subdevice vendor and device
2276 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
2277 -vvnn
</tt
> for the video card in question:
</p
>
2279 <p
><pre
>
2280 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
2281 3rd Gen Core processor Graphics Controller [
8086:
0156] \
2282 (rev
09) (prog-if
00 [VGA controller])
2283 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
2284 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2285 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2286 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
2287 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
2289 Interrupt: pin A routed to IRQ
42
2290 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
2291 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
2292 Region
4: I/O ports at
4000 [size=
64]
2293 Expansion ROM at
<unassigned
> [disabled]
2294 Capabilities:
<access denied
>
2295 Kernel driver in use: i915
2296 </pre
></p
>
2298 <p
>The resulting intel_quirks entry would then look like this:
</p
>
2300 <p
><pre
>
2301 struct intel_quirk intel_quirks[] = {
2303 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2304 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
2307 </pre
></p
>
2309 <p
>According to the kernel module instructions (as seen using
2310 <tt
>modinfo i915
</tt
>), information about hardware needing the
2311 invert_brightness flag should be sent to the
2312 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
2313 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
2314 developers. But my email about the laptop sent
2013-
06-
03 have not
2316 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
2317 web archive for the mailing list
</a
>, so I suspect they do not accept
2318 emails from non-subscribers. Because of this, I sent my patch also to
2319 the Debian bug tracking system instead as
2320 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
2321 sure the patch is not lost.
</p
>
2323 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
2324 with this problem working properly with Linux. If you use Gnome, your
2325 worries should be over at this point. But if you use KDE, there is
2326 something in KDE ignoring the invert_brightness setting and turning on
2327 the screen during login. I
've reported it to Debian as
2328 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
2329 have no idea yet how to figure out exactly what subsystem is doing
2330 this. Perhaps you can help? Perhaps you know what the Gnome
2331 developers did to handle this, and this can give a clue to the KDE
2332 developers? Or you know where in KDE the screen brightness is changed
2333 during login? If so, please update the BTS report (or get in touch if
2334 you do not know how to update BTS).
</p
>
2336 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
2337 acpi_backlight=vendor, to disable ACPI backlight support completely,
2338 as the ACPI information on the machine is trash and it is better to
2339 leave it to the intel video driver to control the screen
2340 backlight.
</p
>
2345 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
2346 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
2347 <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>
2348 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
2349 <description><p
>Two days ago, I asked
2350 <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
2351 I could install Linux on a Packard Bell EasyNote LV computer
2352 preinstalled with Windows
8</a
>. I found a solution, but am horrified
2353 with the obstacles put in the way of Linux users on a laptop with UEFI
2354 and Windows
8.
</p
>
2356 <p
>I never found out if the cause of my problems were the use of UEFI
2357 secure booting or fast boot. I suspect fast boot was the problem,
2358 causing the firmware to boot directly from HD without considering any
2359 key presses and alternative devices, but do not know UEFI settings
2360 enough to tell.
</p
>
2362 <p
>There is no way to install Linux on the machine in question without
2363 opening the box and disconnecting the hard drive! This is as far as I
2364 can tell, the only way to get access to the firmware setup menu
2365 without accepting the Windows
8 license agreement. I am told (and
2366 found description on how to) that it is possible to configure the
2367 firmware setup once booted into Windows
8. But as I believe the terms
2368 of that agreement are completely unacceptable, accepting the license
2369 was never an alternative. I do not enter agreements I do not intend
2370 to follow.
</p
>
2372 <p
>I feared I had to return the laptops and ask for a refund, and
2373 waste many hours on this, but luckily there was a way to get it to
2374 work. But I would not recommend it to anyone planning to run Linux on
2375 it, and I have become sceptical to Windows
8 certified laptops. Is
2376 this the way Linux will be forced out of the market place, by making
2377 it close to impossible for
"normal
" users to install Linux without
2378 accepting the Microsoft Windows license terms? Or at least not
2379 without risking to loose the warranty?
</p
>
2381 <p
>I
've updated the
2382 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
2383 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
2384 do not have to struggle as much as I did to get Linux into the
2387 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2388 Michael Tokarev and others for feedback and ideas.
</p
>
2393 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
2394 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
2395 <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>
2396 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
2397 <description><p
>I
've run into quite a problem the last few days. I bought three
2398 new laptops for my parents and a few others. I bought Packard Bell
2399 Easynote LV to run Kubuntu on and use as their home computer. But I
2400 am completely unable to figure out how to install Linux on it. The
2401 computer is preinstalled with Windows
8, and I suspect it uses UEFI
2402 instead of a BIOS to boot.
</p
>
2404 <p
>The problem is that I am unable to get it to PXE boot, and unable
2405 to get it to boot the Linux installer from my USB stick. I have yet
2406 to try the DVD install, and still hope it will work. when I turn on
2407 the computer, there is no information on what buttons to press to get
2408 the normal boot menu. I expect to get some boot menu to select PXE or
2409 USB stick booting. When booting, it first ask for the language to
2410 use, then for some regional settings, and finally if I will accept the
2411 Windows
8 terms of use. As these terms are completely unacceptable to
2412 me, I have no other choice but to turn off the computer and try again
2413 to get it to boot the Linux installer.
</p
>
2415 <p
>I have gathered my findings so far on a Linlap page about the
2416 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
2417 EasyNote LV
</a
> model. If you have any idea how to get Linux
2418 installed on this machine, please get in touch or update that wiki
2419 page. If I can
't find a way to install Linux, I will have to return
2420 the laptop to the seller and find another machine for my parents.
</p
>
2422 <p
>I wonder, is this the way Linux will be forced out of the market
2423 using UEFI and
"secure boot
" by making it impossible to install Linux
2424 on new Laptops?
</p
>
2429 <title>How to transform a Debian based system to a Debian Edu installation
</title>
2430 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
2431 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
2432 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
2433 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
2434 an operating system based on Debian intended for use in schools. It
2435 contain a turn-key solution for the computer network provided to
2436 pupils in the primary schools. It provide both the central server,
2437 network boot servers and desktop environments with heaps of
2438 educational software. The project was founded almost
12 years ago,
2439 2001-
07-
02. If you want to support the project, which is in need for
2440 cash to fund developer gatherings and other project related activity,
2441 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
2442 donate some money
</a
>.
2444 <p
>A topic that come up again and again on the Debian Edu mailing
2445 lists and elsewhere, is the question on how to transform a Debian or
2446 Ubuntu installation into a Debian Edu installation. It isn
't very
2447 hard, and last week I wrote a script to replicate the steps done by
2448 the Debian Edu installer.
</p
>
2450 <p
>The script,
2451 <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/
>
2452 in the debian-edu-config package, will go through these six steps and
2453 transform an existing Debian Wheezy or Ubuntu (untested) installation
2454 into a Debian Edu Workstation:
</p
>
2458 <li
>Add skolelinux related APT sources.
</li
>
2459 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
2460 <li
>Install debian-edu-install to load preseeding values and pull in
2461 our configuration.
</li
>
2462 <li
>Preseed debconf database with profile setup in
2463 /etc/debian-edu/config, and run tasksel to install packages
2464 according to the profile specified in the config above,
2465 overriding some of the Debian automation machinery.
</li
>
2466 <li
>Run debian-edu-cfengine-D installation to configure everything
2467 that could not be done using preseeding.
</li
>
2468 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
2472 <p
>There are some steps in the Debian Edu installation that can not be
2473 replicated like this. Disk partitioning and LVM setup, for example.
2474 So this script just assume there is enough disk space to install all
2475 the needed packages.
</p
>
2477 <p
>The script was created to help a Debian Edu student working on
2478 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
2479 Debian Edu client, and using it he can take the existing
2480 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
2481 transform it into a fully functioning Debian Edu Workstation (or
2482 Roaming Workstation, or whatever :).
</p
>
2484 <p
>The default setting in the script is to create a KDE Workstation.
2485 If a LXDE based Roaming workstation is wanted instead, modify the
2486 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
2488 <p
><pre
>
2489 PROFILE=
"Roaming-Workstation
"
2490 DESKTOP=
"lxde
"
2491 </pre
></p
>
2493 <p
>The script could even become useful to set up Debian Edu servers in
2494 the cloud, by starting with a virtual Debian installation at some
2495 virtual hosting service and setting up all the services on first
2501 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
2502 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
2503 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
2504 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
2505 <description><P
>In January,
2506 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
2507 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
2508 channel #debian-lego
</a
>, for those of us in the Debian and Linux
2509 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
2510 marvellous construction system from Denmark. We also created
2511 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
2512 a place to take notes and write down our plans and hopes. And several
2513 people showed up to help. I was very happy to see the effect of my
2514 call. Since the small start, we have a debtags tag
2515 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
2516 tag for LEGO related packages, and now count
10 packages related to
2517 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
2519 <p
><table
>
2520 <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
>
2521 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
2522 <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
>
2523 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
2524 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
2525 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
2526 <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
>
2527 <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
>
2528 <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
>
2529 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
2530 </table
></p
>
2532 <p
>Some of these are available in Wheezy, and all but one are
2533 currently available in Jessie/testing. leocad is so far only
2534 available in experimental.
</p
>
2536 <p
>If you care about LEGO in Debian, please join us on IRC and help
2537 adding the rest of the great free software tools available on Linux
2538 for LEGO designers.
</p
>
2543 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
2544 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
2545 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
2546 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
2547 <description><p
>When I woke up this morning, I was very happy to see that the
2548 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
2549 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
2550 Debian release, and I expect to move my machines at home over to it fairly
2553 <p
>The new debian release contain heaps of new stuff, and one program
2554 in particular make me very happy to see included. The
2555 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
2556 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
2557 included for the first time. Alongside similar programs like
2558 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
2559 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
2560 it allow for visual programming where syntax errors can not happen,
2561 and a friendly programming environment for learning to control the
2562 computer. Scratch will also be included in the next release of Debian
2565 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
2566 Edu/Skolelinux release too. The
2567 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
2568 alpha release
</a
> went out last week, and the next should soon
2574 <title>Isenkram
0.2 finally in the Debian archive
</title>
2575 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
2576 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
2577 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
2578 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
2579 package
</a
> finally made it into the archive, after lingering in NEW
2580 for many months. I uploaded it to the Debian experimental suite
2581 2013-
01-
27, and today it was accepted into the archive.
</p
>
2583 <p
>Isenkram is a system for suggesting to users what packages to
2584 install to work with a pluggable hardware device. The suggestion pop
2585 up when the device is plugged in. For example if a Lego Mindstorm NXT
2586 is inserted, it will suggest to install the program needed to program
2587 the NXT controller. Give it a go, and report bugs and suggestions to
2593 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
2594 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
2595 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
2596 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
2597 <description><p
>My
2598 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
2599 bitcoin related blog post
</a
> mentioned that the new
2600 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
2601 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
2602 2013-
01-
19, and have been available in unstable since then. It was
2603 automatically copied to Ubuntu, and is available in their Raring
2604 version too.
</p
>
2606 <p
>But there is a strange problem with the build that block this new
2607 version from being available on the i386 and kfreebsd-i386
2608 architectures. For some strange reason, the autobuilders in Debian
2609 for these architectures fail to run the test suite on these
2610 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
2611 We are so far unable to reproduce it when building it manually, and
2612 no-one have been able to propose a fix. If you got an idea what is
2613 failing, please let us know via the BTS.
</p
>
2615 <p
>One feature that is annoying me with of the bitcoin client, because
2616 I often run low on disk space, is the fact that the client will exit
2617 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
2618 #
696715</a
>). So make sure you have enough disk space when you run
2621 <p
>As usual, if you use bitcoin and want to show your support of my
2622 activities, please send Bitcoin donations to my address
2623 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2628 <title>Welcome to the world, Isenkram!
</title>
2629 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
2630 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
2631 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
2632 <description><p
>Yesterday, I
2633 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
2634 for testers
</a
> for my prototype for making Debian better at handling
2635 pluggable hardware devices, which I
2636 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
2637 out to create
</a
> earlier this month. Several valuable testers showed
2638 up, and caused me to really want to to open up the development to more
2639 people. But before I did this, I want to come up with a sensible name
2640 for this project. Today I finally decided on a new name, and I have
2641 renamed the project from hw-support-handler to this new name. In the
2642 process, I moved the source to git and made it available as a
2643 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
2644 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
2645 To fetch and build the latest version of the source, use
</p
>
2648 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
2649 cd isenkram
&& git-buildpackage -us -uc
2652 <p
>I have not yet adjusted all files to use the new name yet. If you
2653 want to hack on the source or improve the package, please go ahead.
2654 But please talk to me first on IRC or via email before you do major
2655 changes, to make sure we do not step on each others toes. :)
</p
>
2657 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
2658 stuff, typically meaning tools, nails, screws, etc. Typical hardware
2659 stuff, in other words. I
've been told it is the Norwegian variant of
2660 the German word eisenkram, for those that are familiar with that
2663 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
2664 instructions, to avoid confusing people with an error from the signing
2667 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
2668 clone argument to avoid the need for authentication.
</p
>
2673 <title>First prototype ready making hardware easier to use in Debian
</title>
2674 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
2675 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
2676 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
2677 <description><p
>Early this month I set out to try to
2678 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
2679 the Debian support for pluggable hardware devices
</a
>. Now my
2680 prototype is working, and it is ready for a larger audience. To test
2682 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
2683 from the Debian Edu subversion repository
</a
>, build and install the
2684 package. You might have to log out and in again activate the
2685 autostart script.
</p
>
2687 <p
>The design is simple:
</p
>
2691 <li
>Add desktop entry in /usr/share/autostart/ causing a program
2692 hw-support-handlerd to start when the user log in.
</li
>
2694 <li
>This program listen for kernel events about new hardware (directly
2695 from the kernel like udev does), not using HAL dbus events as I
2696 initially did.
</li
>
2698 <li
>When new hardware is inserted, look up the hardware modalias in
2699 the APT database, a database
2700 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
2701 via HTTP
</a
> and a database available as part of the package.
</li
>
2703 <li
>If a package is mapped to the hardware in question, the package
2704 isn
't installed yet and this is the first time the hardware was
2705 plugged in, show a desktop notification suggesting to install the
2706 package or packages.
</li
>
2708 <li
>If the user click on the
'install package now
' button, ask
2709 aptdaemon via the PackageKit API to install the requrired package.
</li
>
2711 <li
>aptdaemon ask for root password or sudo password, and install the
2712 package while showing progress information in a window.
</li
>
2716 <p
>I still need to come up with a better name for the system. Here
2717 are some screen shots showing the prototype in action. First the
2718 notification, then the password request, and finally the request to
2719 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
2721 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
2722 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
2723 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
2724 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
2725 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
2727 <p
>The prototype still need to be improved with longer timeouts, but
2728 is already useful. The database of hardware to package mappings also
2729 need more work. It is currently compatible with the Ubuntu way of
2730 storing such information in the package control file, but could be
2731 changed to use other formats instead or in addition to the current
2732 method. I
've dropped the use of discover for this mapping, as the
2733 modalias approach is more flexible and easier to use on Linux as long
2734 as the Linux kernel expose its modalias strings directly.
</p
>
2736 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
2737 here is the command required to check out and build the source: Use
2738 '<tt
>svn checkout
2739 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
2740 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
2741 devscripts package.
</p
>
2743 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
2744 renamed to Isenkram and the source moved from the Debian Edu
2745 subversion repository to a Debian collab-maint git repository. See
2746 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
2747 instructions
</a
> for details.
</p
>
2752 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
2753 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
2754 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
2755 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
2756 <description><p
>This Christmas my trusty old laptop died. It died quietly and
2757 suddenly in bed. With a quiet whimper, it went completely quiet and
2758 black. The power button was no longer able to turn it on. It was a
2759 IBM Thinkpad X41, and the best laptop I ever had. Better than both
2760 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
2761 Compaq I had before that. Now I need to find a replacement. To keep
2762 going during Christmas, I moved the one year old SSD disk to my old
2763 X40 where it fitted (only one I had left that could use it), but it is
2764 not a durable solution.
2766 <p
>My laptop needs are fairly modest. This is my wishlist from when I
2767 got a new one more than
10 years ago. It still holds true.:)
</p
>
2771 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
2772 than A4).
</li
>
2773 <li
>Robust, it will be in my backpack every day.
</li
>
2774 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
2775 <li
>Long battery life time. Preferable a week.
</li
>
2776 <li
>Internal WIFI network card.
</li
>
2777 <li
>Internal Twisted Pair network card.
</li
>
2778 <li
>Some USB slots (
2-
3 is plenty)
</li
>
2779 <li
>Good keyboard - similar to the Thinkpad.
</li
>
2780 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
2782 <li
>Hardware supported by Debian Stable, ie the default kernel and
2783 X.org packages.
</li
>
2784 <li
>Quiet, preferably fan free (or at least not using the fan most of
2789 <p
>You will notice that there are no RAM and CPU requirements in the
2790 list. The reason is simply that the specifications on laptops the
2791 last
10-
15 years have been sufficient for my needs, and I have to look
2792 at other features to choose my laptop. But are there still made as
2793 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
2794 robust, and Thinkpads seem to be heading in the wrong direction since
2795 Lenovo took over. But I
've been told that X220 and X1 Carbon might
2796 still be useful.
</p
>
2798 <p
>Perhaps I should rethink my needs, and look for a pad with an
2799 external keyboard? I
'll have to check the
2800 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
2801 well-supported laptops, or perhaps just buy one preinstalled from one
2802 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
2803 Pre-loaded site
</a
>.
</p
>
2808 <title>How to find a browser plugin supporting a given MIME type
</title>
2809 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
2810 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
2811 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
2812 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
2813 install to get support for a given MIME type. Thanks to
2814 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
2815 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
2816 Unfortunately, not very many packages provide the needed meta
2817 information, Anyway, here is a small script to look up all browser
2818 plugin packages announcing ther MIME support using this specification:
</p
>
2824 def pkgs_handling_mimetype(mimetype):
2829 version = pkg.candidate
2831 version = pkg.installed
2834 record = version.record
2835 if not record.has_key(
'Npp-MimeType
'):
2837 mime_types = record[
'Npp-MimeType
'].split(
',
')
2838 for t in mime_types:
2839 t = t.rstrip().strip()
2841 thepkgs.append(pkg.name)
2843 mimetype =
"audio/ogg
"
2844 if
1 < len(sys.argv):
2845 mimetype = sys.argv[
1]
2846 print
"Browser plugin packages supporting %s:
" % mimetype
2847 for pkg in pkgs_handling_mimetype(mimetype):
2848 print
" %s
" %pkg
2851 <p
>It can be used like this to look up a given MIME type:
</p
>
2854 % ./apt-find-browserplug-for-mimetype
2855 Browser plugin packages supporting audio/ogg:
2857 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
2858 Browser plugin packages supporting application/x-shockwave-flash:
2859 browser-plugin-gnash
2863 <p
>In Ubuntu this mechanism is combined with support in the browser
2864 itself to query for plugins and propose to install the needed
2865 packages. It would be great if Debian supported such feature too. Is
2866 anyone working on adding it?
</p
>
2868 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
2869 request for icweasel support for this feature is
2870 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
2871 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
2872 of manpower and wish for a different design is the reason thus feature
2873 is not yet in iceweasel from Debian.
</p
>
2878 <title>What is the most supported MIME type in Debian?
</title>
2879 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
2880 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
2881 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
2882 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
2883 proposal to add AppStream information to the Debian archive
</a
>, is a
2884 proposal to make it possible for a Desktop application to propose to
2885 the user some package to install to gain support for a given MIME
2886 type, font, library etc. that is currently missing. With such
2887 mechanism in place, it would be possible for the desktop to
2888 automatically propose and install leocad if some LDraw file is
2889 downloaded by the browser.
</p
>
2891 <p
>To get some idea about the current content of the archive, I decided
2892 to write a simple program to extract all .desktop files from the
2893 Debian archive and look up the claimed MIME support there. The result
2895 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
2896 site
</a
>. Using the collected information, it become possible to
2897 answer the question in the title. Here are the
20 most supported MIME
2898 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
2899 The complete list is available from the link above.
</p
>
2901 <p
><strong
>Debian Stable:
</strong
></p
>
2905 ----- -----------------------
2921 18 application/x-ogg
2928 <p
><strong
>Debian Testing:
</strong
></p
>
2932 ----- -----------------------
2948 18 application/x-ogg
2955 <p
><strong
>Debian Unstable:
</strong
></p
>
2959 ----- -----------------------
2976 18 application/x-ogg
2982 <p
>I am told that PackageKit can provide an API to access the kind of
2983 information mentioned in DEP-
11. I have not yet had time to look at
2984 it, but hope the PackageKit people in Debian are on top of these
2987 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
2988 discovering a typo in my script.
</p
>
2993 <title>Using modalias info to find packages handling my hardware
</title>
2994 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
2995 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
2996 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
2997 <description><p
>Yesterday, I wrote about the
2998 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
2999 values provided by the Linux kernel
</a
> following my hope for
3000 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
3001 dongle support in Debian
</a
>. Using this knowledge, I have tested how
3002 modalias values attached to package names can be used to map packages
3003 to hardware. This allow the system to look up and suggest relevant
3004 packages when I plug in some new hardware into my machine, and replace
3005 discover and discover-data as the database used to map hardware to
3008 <p
>I create a modaliases file with entries like the following,
3009 containing package name, kernel module name (if relevant, otherwise
3010 the package name) and globs matching the relevant hardware
3013 <p
><blockquote
>
3014 Package: package-name
3015 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
3016 </blockquote
></p
>
3018 <p
>It is fairly trivial to write code to find the relevant packages
3019 for a given modalias value using this file.
</p
>
3021 <p
>An entry like this would suggest the video and picture application
3022 cheese for many USB web cameras (interface bus class
0E01):
</p
>
3024 <p
><blockquote
>
3026 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
3027 </blockquote
></p
>
3029 <p
>An entry like this would suggest the pcmciautils package when a
3030 CardBus bridge (bus class
0607) PCI device is present:
</p
>
3032 <p
><blockquote
>
3033 Package: pcmciautils
3034 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3035 </blockquote
></p
>
3037 <p
>An entry like this would suggest the package colorhug-client when
3038 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
3040 <p
><blockquote
>
3041 Package: colorhug-client
3042 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
3043 </blockquote
></p
>
3045 <p
>I believe the format is compatible with the format of the Packages
3046 file in the Debian archive. Ubuntu already uses their Packages file
3047 to store their mappings from packages to hardware.
</p
>
3049 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
3050 announce the hardware it support in a way my prototype understand.
3051 This allow those publishing packages in an APT source outside the
3052 Debian archive as well as those backporting packages to make sure the
3053 hardware mapping are included in the package meta information. I
've
3054 tested such header in the pymissile package, and its modalias mapping
3055 is working as it should with my prototype. It even made it to Ubuntu
3058 <p
>To test if it was possible to look up supported hardware using only
3059 the shell tools available in the Debian installer, I wrote a shell
3060 implementation of the lookup code. The idea is to create files for
3061 each modalias and let the shell do the matching. Please check out and
3063 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
3064 shell script. It run without any extra dependencies and fetch the
3065 hardware mappings from the Debian archive and the subversion
3066 repository where I currently work on my prototype.
</p
>
3068 <p
>When I use it on a machine with a yubikey inserted, it suggest to
3069 install yubikey-personalization:
</p
>
3071 <p
><blockquote
>
3072 % ./hw-support-lookup
3073 <br
>yubikey-personalization
3075 </blockquote
></p
>
3077 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3078 propose to install the pcmciautils package:
</p
>
3080 <p
><blockquote
>
3081 % ./hw-support-lookup
3082 <br
>pcmciautils
3084 </blockquote
></p
>
3086 <p
>If you know of any hardware-package mapping that should be added to
3087 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
3088 database
</a
>, please tell me about it.
</p
>
3090 <p
>It could be possible to generate several of the mappings between
3091 packages and hardware. One source would be to look at packages with
3092 kernel modules, ie packages with *.ko files in /lib/modules/, and
3093 extract their modalias information. Another would be to look at
3094 packages with udev rules, ie packages with files in
3095 /lib/udev/rules.d/, and extract their vendor/model information to
3096 generate a modalias matching rule. I have not tested any of these to
3097 see if it work.
</p
>
3099 <p
>If you want to help implementing a system to let us propose what
3100 packages to install when new hardware is plugged into a Debian
3101 machine, please send me an email or talk to me on
3102 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
3107 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
3108 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
3109 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
3110 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
3111 <description><p
>While looking into how to look up Debian packages based on hardware
3112 information, to find the packages that support a given piece of
3113 hardware, I refreshed my memory regarding modalias values, and decided
3114 to document the details. Here are my findings so far, also available
3116 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
3117 Debian Edu subversion repository
</a
>:
3119 <p
><strong
>Modalias decoded
</strong
></p
>
3121 <p
>This document try to explain what the different types of modalias
3122 values stands for. It is in part based on information from
3123 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
3124 &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;,
3125 &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
3126 &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;.
3128 <p
>The modalias entries for a given Linux machine can be found using
3129 this shell script:
</p
>
3132 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
3135 <p
>The supported modalias globs for a given kernel module can be found
3136 using modinfo:
</p
>
3139 % /sbin/modinfo psmouse | grep alias:
3140 alias: serio:ty05pr*id*ex*
3141 alias: serio:ty01pr*id*ex*
3145 <p
><strong
>PCI subtype
</strong
></p
>
3147 <p
>A typical PCI entry can look like this. This is an Intel Host
3148 Bridge memory controller:
</p
>
3150 <p
><blockquote
>
3151 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3152 </blockquote
></p
>
3154 <p
>This represent these values:
</p
>
3159 sv
00001028 (subvendor)
3160 sd
000001AD (subdevice)
3162 sc
00 (bus subclass)
3166 <p
>The vendor/device values are the same values outputted from
'lspci
3167 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
3168 0600. The
0600 class is a host bridge. Other useful bus values are
3169 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
3171 <p
>Not sure how to figure out the interface value, nor what it
3174 <p
><strong
>USB subtype
</strong
></p
>
3176 <p
>Some typical USB entries can look like this. This is an internal
3177 USB hub in a laptop:
</p
>
3179 <p
><blockquote
>
3180 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3181 </blockquote
></p
>
3183 <p
>Here is the values included in this alias:
</p
>
3186 v
1D6B (device vendor)
3187 p
0001 (device product)
3189 dc
09 (device class)
3190 dsc
00 (device subclass)
3191 dp
00 (device protocol)
3192 ic
09 (interface class)
3193 isc
00 (interface subclass)
3194 ip
00 (interface protocol)
3197 <p
>The
0900 device class/subclass means hub. Some times the relevant
3198 class is in the interface class section. For a simple USB web camera,
3199 these alias entries show up:
</p
>
3201 <p
><blockquote
>
3202 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3203 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3204 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3205 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3206 </blockquote
></p
>
3208 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
3209 camera),
0101 is audio control device and
0102 is audio streaming (aka
3210 microphone). Thus this is a camera with microphone included.
</p
>
3212 <p
><strong
>ACPI subtype
</strong
></p
>
3214 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
3215 receiver in a Thinkpad X40:
</p
>
3217 <p
><blockquote
>
3218 acpi:IBM0071:PNP0511:
3219 </blockquote
></p
>
3221 <p
>The values between the colons are IDs.
</p
>
3223 <p
><strong
>DMI subtype
</strong
></p
>
3225 <p
>The DMI table contain lots of information about the computer case
3226 and model. This is an entry for a IBM Thinkpad X40, fetched from
3227 /sys/devices/virtual/dmi/id/modalias:
</p
>
3229 <p
><blockquote
>
3230 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3231 </blockquote
></p
>
3233 <p
>The values present are
</p
>
3236 bvn IBM (BIOS vendor)
3237 bvr
1UETB
6WW(
1.66) (BIOS version)
3238 bd
06/
15/
2005 (BIOS date)
3239 svn IBM (system vendor)
3240 pn
2371H4G (product name)
3241 pvr ThinkPadX40 (product version)
3242 rvn IBM (board vendor)
3243 rn
2371H4G (board name)
3244 rvr NotAvailable (board version)
3245 cvn IBM (chassis vendor)
3246 ct
10 (chassis type)
3247 cvr NotAvailable (chassis version)
3250 <p
>The chassis type
10 is Notebook. Other interesting values can be
3251 found in the dmidecode source:
</p
>
3255 4 Low Profile Desktop
3268 17 Main Server Chassis
3269 18 Expansion Chassis
3271 20 Bus Expansion Chassis
3272 21 Peripheral Chassis
3274 23 Rack Mount Chassis
3283 <p
>The chassis type values are not always accurately set in the DMI
3284 table. For example my home server is a tower, but the DMI modalias
3285 claim it is a desktop.
</p
>
3287 <p
><strong
>SerIO subtype
</strong
></p
>
3289 <p
>This type is used for PS/
2 mouse plugs. One example is from my
3290 test machine:
</p
>
3292 <p
><blockquote
>
3293 serio:ty01pr00id00ex00
3294 </blockquote
></p
>
3296 <p
>The values present are
</p
>
3305 <p
>This type is supported by the psmouse driver. I am not sure what
3306 the valid values are.
</p
>
3308 <p
><strong
>Other subtypes
</strong
></p
>
3310 <p
>There are heaps of other modalias subtypes according to
3311 file2alias.c. There is the rest of the list from that source: amba,
3312 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3313 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3314 vmbus, x86cpu and zorro. I did not spend time documenting all of
3315 these, as they do not seem relevant for my intended use with mapping
3316 hardware to packages when new stuff is inserted during run time.
</p
>
3318 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
3320 <p
>To check which kernel modules provide support for a given modalias,
3321 one can use the following shell script:
</p
>
3324 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
3325 echo
"$id
" ; \
3326 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
3330 <p
>The output can look like this (only the first few entries as the
3331 list is very long on my test machine):
</p
>
3335 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
3337 FATAL: Module acpi:device: not found.
3339 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
3340 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
3341 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
3342 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3343 acpi:IBM0071:PNP0511:
3344 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
3345 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
3346 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
3350 <p
>If you want to help implementing a system to let us propose what
3351 packages to install when new hardware is plugged into a Debian
3352 machine, please send me an email or talk to me on
3353 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
3355 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
3356 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
3357 in /sys/ with space in them.
</p
>
3362 <title>Moved the pymissile Debian packaging to collab-maint
</title>
3363 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
3364 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
3365 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
3366 <description><p
>As part of my investigation on how to improve the support in Debian
3367 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3368 Launcher and updated the Debian package
3369 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
3370 sure udev will fix the device permissions when it is plugged in. I
3371 also added a
"Modaliases
" header to test it in the Debian archive and
3372 hopefully make the package be proposed by jockey in Ubuntu when a user
3373 plug in his rocket launcher. In the process I moved the source to a
3374 git repository under collab-maint, to make it easier for any DD to
3375 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
3376 is not very active, but the software still work for me even after five
3377 years of relative silence. The new git repository is not listed in
3378 the uploaded package yet, because I want to test the other changes a
3379 bit more before I upload the new version. If you want to check out
3380 the new version with a .desktop file included, visit the
3381 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
3382 view
</a
> or use
"<tt
>git clone
3383 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
3388 <title>Lets make hardware dongles easier to use in Debian
</title>
3389 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
3390 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
3391 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
3392 <description><p
>One thing that annoys me with Debian and Linux distributions in
3393 general, is that there is a great package management system with the
3394 ability to automatically install software packages by downloading them
3395 from the distribution mirrors, but no way to get it to automatically
3396 install the packages I need to use the hardware I plug into my
3397 machine. Even if the package to use it is easily available from the
3398 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3399 suggest to automatically install the python-nxt, nbc and t2n packages
3400 I need to talk to it. When I plug in a Yubikey, it could propose the
3401 yubikey-personalization package. The information required to do this
3402 is available, but no-one have pulled all the pieces together.
</p
>
3404 <p
>Some years ago, I proposed to
3405 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
3406 the discover subsystem to implement this
</a
>. The idea is fairly
3411 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
3412 starting when a user log in.
</li
>
3414 <li
>Set this program up to listen for kernel events emitted when new
3415 hardware is inserted into the computer.
</li
>
3417 <li
>When new hardware is inserted, look up the hardware ID in a
3418 database mapping to packages, and take note of any non-installed
3419 packages.
</li
>
3421 <li
>Show a message to the user proposing to install the discovered
3422 package, and make it easy to install it.
</li
>
3426 <p
>I am not sure what the best way to implement this is, but my
3427 initial idea was to use dbus events to discover new hardware, the
3428 discover database to find packages and
3429 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
3432 <p
>Yesterday, I found time to try to implement this idea, and the
3433 draft package is now checked into
3434 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
3435 Debian Edu subversion repository
</a
>. In the process, I updated the
3436 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
3437 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3438 the relevant packages in Debian, and uploaded a new version
3439 2.2013.01.09 to unstable. I also discovered that the current
3440 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
3441 package in Debian no longer discovered any USB devices, because
3442 /proc/bus/usb/devices is no longer present. I ported it to use
3443 libusb as a fall back option to get it working. The fixed package
3444 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
3445 because of the freeze).
</p
>
3447 <p
>With this prototype in place, I can insert my Yubikey, and get this
3448 desktop notification to show up (only once, the first time it is
3449 inserted):
</p
>
3451 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
3453 <p
>For this prototype to be really useful, some way to automatically
3454 install the proposed packages by pressing the
"Please install
3455 program(s)
" button should to be implemented.
</p
>
3457 <p
>If this idea seem useful to you, and you want to help make it
3458 happen, please help me update the discover-data database with mappings
3459 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
3460 list the package you would like to have installed when a given
3461 hardware device is inserted into your computer, and report bugs using
3462 reportbug if it isn
't. Or, if you know of a better way to provide
3463 such mapping, please let me know.
</p
>
3465 <p
>This prototype need more work, and there are several questions that
3466 should be considered before it is ready for production use. Is dbus
3467 the correct way to detect new hardware? At the moment I look for HAL
3468 dbus events on the system bus, because that is the events I could see
3469 on my Debian Squeeze KDE desktop. Are there better events to use?
3470 How should the user be notified? Is the desktop notification
3471 mechanism the best option, or should the background daemon raise a
3472 popup instead? How should packages be installed? When should they
3473 not be installed?
</p
>
3475 <p
>If you want to help getting such feature implemented in Debian,
3476 please send me an email. :)
</p
>
3481 <title>New IRC channel for LEGO designers using Debian
</title>
3482 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
3483 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
3484 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
3485 <description><p
>During Christmas, I have worked a bit on the Debian support for
3486 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
3487 NXT
</a
>. My son and I have played a bit with my NXT set, and I
3488 discovered I had to build all the tools myself because none were
3489 already in Debian Squeeze. If Debian support for LEGO is something
3490 you care about, please join me on the IRC channel
3491 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
3492 irc.debian.org). There is a lot that could be done to improve the
3493 Debian support for LEGO designers. For example both CAD software
3494 and Mindstorm compilers are missing. :)
</p
>
3496 <p
>Update
2012-
01-
03: A
3497 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
3498 including links to Lego related packages is now available.
</p
>
3503 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
3504 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
3505 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
3506 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
3507 <description><p
>Let me start by wishing you all marry Christmas and a happy new
3508 year! I hope next year will prove to be a good year.
</p
>
3510 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
3511 decentralised
"currency
" that allow people to transfer bitcoins
3512 between each other with minimal overhead, is a very interesting
3513 experiment. And as I wrote a few days ago, the bitcoin situation in
3514 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
3515 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
3516 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
3517 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
3518 for one of the ftpmasters to approve the new bitcoin-qt package
3521 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
3522 team in Debian, you can easily test the package in Debian Squeeze
3523 using the following steps to get a set of working packages:
</p
>
3525 <blockquote
><pre
>
3526 git clone git://git.debian.org/git/collab-maint/bitcoin
3528 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3529 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3530 </pre
></blockquote
>
3532 <p
>You might have to install some build dependencies as well. The
3533 list of commands should give you two packages, bitcoind and
3534 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3535 client will download the complete set of bitcoin
"blocks
", which need
3536 around
5.6 GiB of data on my machine at the moment. Make sure your
3537 ~/.bitcoin/ directory have lots of spare room if you want to download
3538 all the blocks. The client will warn if the disk is getting full, so
3539 there is not really a problem if you got too little room, but you will
3540 not be able to get all the features out of the client.
</p
>
3542 <p
>As usual, if you use bitcoin and want to show your support of my
3543 activities, please send Bitcoin donations to my address
3544 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3549 <title>A word on bitcoin support in Debian
</title>
3550 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
3551 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
3552 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
3553 <description><p
>It has been a while since I wrote about
3554 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
3555 peer-to-peer based crypto-currency, and the reason is simply that I
3556 have been busy elsewhere. But two days ago, I started looking at the
3557 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
3558 Debian
</a
> again to try to recover my old bitcoin wallet. The package
3559 is now maintained by a
3560 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
3561 people
</a
>, and the grunt work had already been done by this team. We
3562 owe a huge thank you to all these team members. :)
3563 But I was sad to discover that the bitcoin client is missing in
3564 Wheezy. It is only available in Sid (and an outdated client from
3565 backports). The client had several RC bugs registered in BTS blocking
3566 it from entering testing. To try to help the team and improve the
3567 situation, I spent some time providing patches and triaging the bug
3568 reports. I also had a look at the bitcoin package available from Matt
3570 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
3571 Ubuntu
</a
>, and moved the useful pieces from that version into the
3572 Debian package.
</p
>
3574 <p
>After checking with the main package maintainer Jonas Smedegaard on
3575 IRC, I pushed several patches into the collab-maint git repository to
3576 improve the package. It now contains fixes for the RC issues (not from
3577 me, but fixed by Scott Howard), build rules for a Qt GUI client
3578 package, konqueror support for the bitcoin: URI and bash completion
3579 setup. As I work on Debian Squeeze, I also created
3580 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
3581 patch to backport
</a
> the latest version. Jonas is going to look at
3582 it and try to integrate it into the git repository before uploading a
3583 new version to unstable.
3585 <p
>I would very much like bitcoin to succeed, to get rid of the
3586 centralized control currently exercised in the monetary system. I
3587 find it completely unacceptable that the USA government is collecting
3588 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
3589 that the major credit card companies can block legal money
3590 transactions to Wikileaks. But for bitcoin to succeed, more people
3591 need to use bitcoins, and more people need to accept bitcoins when
3592 they sell products and services. Improving the bitcoin support in
3593 Debian is a small step in the right direction, but not enough.
3594 Unfortunately the user experience when browsing the web and wanting to
3595 pay with bitcoin is still not very good. The bitcoin: URI is a step
3596 in the right direction, but need to work in most or every browser in
3597 use. Also the bitcoin-qt client is too heavy to fire up to do a
3598 quick transaction. I believe there are other clients available, but
3599 have not tested them.
</p
>
3602 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
3603 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
3604 I received
20.15 BTC so far on the address I provided in my blog two
3605 years ago, as can be
3606 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
3607 on the blockexplorer service
</a
>. Thank you everyone for your
3608 donation. The blockexplorer service demonstrates quite well that
3609 bitcoin is not quite anonymous and untracked. :) I wonder if the
3610 number of users have gone up since then. If you use bitcoin and want
3611 to show your support of my activity, please send Bitcoin donations to
3612 the same address as last time,
3613 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3618 <title>Git repository for song book for Computer Scientists
</title>
3619 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
3620 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
3621 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
3622 <description><p
>As I
3623 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
3624 this summer
</a
>, I have created a Computer Science song book a few
3625 years ago, and today I finally found time to create a public
3626 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
3627 repository for the project
</a
>.
</p
>
3629 <p
>If you want to help out, please clone the source and submit patches
3630 to the HTML version. To generate the PDF and PostScript version,
3631 please use prince XML, or let me know about a useful free software
3632 processor capable of creating a good looking PDF from the HTML.
</p
>
3634 <p
>Want to sing? You can still find the song book in HTML, PDF and
3635 PostScript formats at
3636 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
3637 Science Songbook
</a
>.
</p
>
3642 <title>Gratulerer med
19-årsdagen, Debian!
</title>
3643 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
3644 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
3645 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
3646 <description><p
>I dag fyller
3647 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
3648 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
3649 si gratulerer med dagen, Debian!
</p
>
3654 <title>Song book for Computer Scientists
</title>
3655 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
3656 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
3657 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
3658 <description><p
>Many years ago, while studying Computer Science at the
3659 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
3660 collecting computer related songs for use at parties. The original
3661 version was written in LaTeX, but a few years ago I got help from
3662 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
3663 while keeping the ability to create a nice book in PDF format. I have
3664 not had time to maintain the book for a while now, and guess I should
3665 put it up on some public version control repository where others can
3666 help me extend and update the book. If anyone is volunteering to help
3667 me with this, send me an email. Also let me know if there are songs
3668 missing in my book.
</p
>
3670 <p
>I have not mentioned the book on my blog so far, and it occured to
3671 me today that I really should let all my readers share the joys of
3672 singing out load about programming, computers and computer networks.
3673 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
3674 12</a
> is about to start (and I am not going). Want to sing? Check
3675 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
3676 Computer Science Songbook
</a
>.
3681 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
3682 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
3683 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
3684 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
3685 <description><p
>At work we have heaps of servers. I believe the total count is
3686 around
1000 at the moment. To be able to get help from the vendors
3687 when something go wrong, we want to keep the firmware on the servers
3688 up to date. If the firmware isn
't the latest and greatest, the
3689 vendors typically refuse to start debugging any problems until the
3690 firmware is upgraded. So before every reboot, we want to upgrade the
3691 firmware, and we would really like everyone handling servers at the
3692 university to do this themselves when they plan to reboot a machine.
3693 For that to happen we at the unix server admin group need to provide
3694 the tools to do so.
</p
>
3696 <p
>To make firmware upgrading easier, I am working on a script to
3697 fetch and install the latest firmware for the servers we got. Most of
3698 our hardware are from Dell and HP, so I have focused on these servers
3699 so far. This blog post is about the Dell part.
</P
>
3701 <p
>On the Dell FTP site I was lucky enough to find
3702 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
3703 with firmware information for all
11th generation servers, listing
3704 which firmware should be used on a given model and where on the FTP
3705 site I can find it. Using a simple perl XML parser I can then
3706 download the shell scripts Dell provides to do firmware upgrades from
3707 within Linux and reboot when all the firmware is primed and ready to
3708 be activated on the first reboot.
</p
>
3710 <p
>This is the Dell related fragment of the perl code I am working on.
3711 Are there anyone working on similar tools for firmware upgrading all
3712 servers at a site? Please get in touch and lets share resources.
</p
>
3714 <p
><pre
>
3718 use File::Temp qw(tempdir);
3720 # Install needed RHEL packages if missing
3722 'XML::Simple
' =
> 'perl-XML-Simple
',
3724 for my $module (keys %rhelmodules) {
3725 eval
"use $module;
";
3727 my $pkg = $rhelmodules{$module};
3728 system(
"yum install -y $pkg
");
3729 eval
"use $module;
";
3733 my $errorsto =
'pere@hungry.com
';
3739 sub run_firmware_script {
3740 my ($opts, $script) = @_;
3742 print STDERR
"fail: missing script name\n
";
3745 print STDERR
"Running $script\n\n
";
3747 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
3748 print STDERR
"success: firmware script ran succcessfully\n
";
3750 print STDERR
"fail: firmware script returned error\n
";
3754 sub run_firmware_scripts {
3755 my ($opts, @dirs) = @_;
3756 # Run firmware packages
3757 for my $dir (@dirs) {
3758 print STDERR
"info: Running scripts in $dir\n
";
3759 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
3760 while (my $s = readdir $dh) {
3761 next if $s =~ m/^\.\.?/;
3762 run_firmware_script($opts,
"$dir/$s
");
3770 print STDERR
"info: Downloading $url\n
";
3771 system(
"wget --quiet \
"$url\
"");
3776 my $product = `dmidecode -s system-product-name`;
3779 if ($product =~ m/PowerEdge/) {
3781 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
3782 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
3784 my $tmpdir = tempdir(
3788 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
3789 system(
'gunzip Catalog.xml.gz
');
3790 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
3791 # -q is quiet, disabling interactivity and reducing console output
3792 my $fwopts =
"-q
";
3794 for my $url (@paths) {
3795 fetch_dell_fw($url);
3797 run_firmware_scripts($fwopts, $tmpdir);
3799 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
3800 print STDERR
"error: Please report to $errorsto.\n
";
3804 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
3805 print STDERR
"error: Please report to $errorsto.\n
";
3811 my $url =
"ftp://ftp.us.dell.com/$path
";
3815 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
3816 # firmware packages to download from Dell. Only work for Linux
3817 # machines and
11th generation Dell servers.
3818 sub fetch_dell_fw_list {
3819 my $filename = shift;
3821 my $product = `dmidecode -s system-product-name`;
3823 my ($mybrand, $mymodel) = split(/\s+/, $product);
3825 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
3827 my $xml = XMLin($filename);
3829 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
3830 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
3831 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
3833 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
3834 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
3836 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
3838 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
3840 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
3843 for my $component (@{$xml-
>{SoftwareComponent}}) {
3844 my $componenttype = $component-
>{ComponentType}-
>{value};
3846 # Drop application packages, only firmware and BIOS
3847 next if
'APAC
' eq $componenttype;
3849 my $cpath = $component-
>{path};
3850 for my $path (@paths) {
3851 if ($cpath =~ m%/$path$%) {
3852 push(@paths, $cpath);
3860 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
3861 it could work on other platforms with some tweaking. Anyone know a
3862 index like Catalog.xml is available from HP for HP servers? At the
3863 moment I maintain a similar list manually and it is quickly getting
3869 <title>How is booting into runlevel
1 different from single user boots?
</title>
3870 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
3871 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
3872 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
3873 <description><p
>Wouter Verhelst have some
3874 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
3875 comments and opinions
</a
> on my blog post on
3876 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
3877 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
3878 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
3879 default KDE desktop in Debian
</a
>. I only have time to address one
3880 small piece of his comment now, and though it best to address the
3881 misunderstanding he bring forward:
</p
>
3883 <p
><blockquote
>
3884 Currently, a system admin has four options: [...] boot to a
3885 single-user system (by adding
'single
' to the kernel command line;
3886 this runs rcS and rc1 scripts)
3887 </blockquote
></p
>
3889 <p
>This make me believe Wouter believe booting into single user mode
3890 and booting into runlevel
1 is the same. I am not surprised he
3891 believe this, because it would make sense and is a quite sensible
3892 thing to believe. But because the boot in Debian is slightly broken,
3893 runlevel
1 do not work properly and it isn
't the same as single user
3894 mode. I
'll try to explain what is actually happing, but it is a bit
3895 hard to explain.
</p
>
3897 <p
>Single user mode is defined like this in /etc/inittab:
3898 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
3899 executed in single user mode is sulogin. Single user mode is a boot
3900 state
"between
" the runlevels, and when booting into single user mode,
3901 only the scripts in /etc/rcS.d/ are executed before the init process
3902 enters the single user state. When switching to runlevel
1, the state
3903 is in fact not ending in runlevel
1, but it passes through runlevel
1
3904 and end up in the single user mode (see /etc/rc1.d/S03single, which
3905 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
3906 1. It is confusing that the
'S
' (single user) init mode is not the
3907 mode enabled by /etc/rcS.d/ (which is more like the initial boot
3910 <p
>This summary might make it clearer. When booting for the first
3911 time into single user mode, the following commands are executed:
3912 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
3913 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
3914 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
3915 trying to continue after visiting single user mode. Not all services
3916 are started again as they should, causing the machine to end up in an
3917 unpredicatble state. This is why Debian admins recommend rebooting
3918 after visiting single user mode.
</p
>
3920 <p
>A similar problem with runlevel
1 is caused by the amount of
3921 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
3922 to runlevel
1, the services started from /etc/rcS.d/ are not properly
3923 stopped when passing through the scripts in /etc/rc1.d/, and not
3924 started again when switching away from runlevel
1 to the runlevels
3925 2-
5. I believe the problem is best fixed by moving all the scripts
3926 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
3927 functioning single user mode during boot.
</p
>
3929 <p
>I have spent several years investigating the Debian boot system,
3930 and discovered this problem a few years ago. I suspect it originates
3931 from when sysvinit was introduced into Debian, a long time ago.
</p
>
3936 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
3937 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
3938 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
3939 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
3940 <description><p
>In the Debian boot system, several packages include scripts that
3941 are started from /etc/rcS.d/. In fact, there is a bite more of them
3942 than make sense, and this causes a few problems. What kind of
3943 problems, you might ask. There are at least two problems. The first
3944 is that it is not possible to recover a machine after switching to
3945 runlevel
1. One need to actually reboot to get the machine back to
3946 the expected state. The other is that single user boot will sometimes
3947 run into problems because some of the subsystems are activated before
3948 the root login is presented, causing problems when trying to recover a
3949 machine from a problem in that subsystem. A minor additional point is
3950 that moving more scripts out of rcS.d/ and into the other rc#.d/
3951 directories will increase the amount of scripts that can run in
3952 parallel during boot, and thus decrease the boot time.
</p
>
3954 <p
>So, which scripts should start from rcS.d/. In short, only the
3955 scripts that _have_ to execute before the root login prompt is
3956 presented during a single user boot should go there. Everything else
3957 should go into the numeric runlevels. This means things like
3958 lm-sensors, fuse and x11-common should not run from rcS.d, but from
3959 the numeric runlevels. Today in Debian, there are around
115 init.d
3960 scripts that are started from rcS.d/, and most of them should be moved
3961 out. Do your package have one of them? Please help us make single
3962 user and runlevel
1 better by moving it.
</p
>
3964 <p
>Scripts setting up the screen, keyboard, system partitions
3965 etc. should still be started from rcS.d/, but there is for example no
3966 need to have the network enabled before the single user login prompt
3967 is presented.
</p
>
3969 <p
>As always, things are not so easy to fix as they sound. To keep
3970 Debian systems working while scripts migrate and during upgrades, the
3971 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
3972 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
3973 and the next ones can only be moved when their dependencies have been
3974 moved first. This migration must be done sequentially while we ensure
3975 that the package system upgrade packages in the right order to keep
3976 the system state correct. This will require some coordination when it
3977 comes to network related packages, but most of the packages with
3978 scripts that should migrate do not have anything in rcS.d/ depending
3979 on them. Some packages have already been updated, like the sudo
3980 package, while others are still left to do. I wish I had time to work
3981 on this myself, but real live constrains make it unlikely that I will
3982 find time to push this forward.
</p
>
3987 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
3988 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
3989 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
3990 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
3991 <description><p
>While at Debconf11, I have several times during discussions
3992 mentioned the issues I believe should be improved in Debian for its
3993 desktop to be useful for more people. The use case for this is my
3994 parents, which are currently running Kubuntu which solve the
3997 <p
>I suspect these four missing features are not very hard to
3998 implement. After all, they are present in Ubuntu, so if we wanted to
3999 do this in Debian we would have a source.
</p
>
4003 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
4004 are new packages available for upgrades, a icon in the KDE status bar
4005 indicate this, and clicking on it will activate the simple upgrade
4006 tool to handle it. I have no problem guiding both of my parents
4007 through the process over the phone. If a kernel reboot is required,
4008 this too is indicated by the status bars and the upgrade tool. Last
4009 time I checked, nothing with the same features was working in KDE in
4012 <li
><strong
>Simple handling of missing Firefox browser
4013 plugins.
</strong
> When the browser encounter a MIME type it do not
4014 currently have a handler for, it will ask the user if the system
4015 should search for a package that would add support for this MIME type,
4016 and if the user say yes, the APT sources will be searched for packages
4017 advertising the MIME type in their control file (visible in the
4018 Packages file in the APT archive). If one or more packages are found,
4019 it is a simple click of the mouse to add support for the missing mime
4020 type. If the package require the user to accept some non-free
4021 license, this is explained to the user. The entire process make it
4022 more clear to the user why something do not work in the browser, and
4023 make the chances higher for the user to blame the web page authors and
4024 not the browser for any missing features.
</li
>
4026 <li
><strong
>Simple handling of missing multimedia codec/format
4027 handlers.
</strong
> When the media players encounter a format or codec
4028 it is not supporting, a dialog pop up asking the user if the system
4029 should search for a package that would add support for it. This
4030 happen with things like MP3, Windows Media or H
.264. The selection
4031 and installation procedure is very similar to the Firefox browser
4032 plugin handling. This is as far as I know implemented using a
4033 gstreamer hook. The end result is that the user easily get access to
4034 the codecs that are present from the APT archives available, while
4035 explaining more on why a given format is unsupported by Ubuntu.
</li
>
4037 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
4038 displaying a text/plain file in my Debian browser, it will propose to
4039 start emacs to show it. If I remember correctly, when doing the same
4040 in Kunbutu it show the file as a text file in the browser. At least I
4041 know Opera will show text files within the browser. I much prefer the
4042 latter behaviour.
</li
>
4046 <p
>There are other nice features as well, like the simplified suite
4047 upgrader, but given that I am the one mostly doing the dist-upgrade,
4048 it do not matter much.
</p
>
4050 <p
>I really hope we could get these features in place for the next
4051 Debian release. It would require the coordinated effort of several
4052 maintainers, but would make the end user experience a lot better.
</p
>
4057 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
4058 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
4059 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
4060 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
4061 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
4062 site is build on Debian/Squeeze, and this platform was chosen because
4063 I am most familiar with Debian (being a Debian Developer for around
10
4064 years) because it is the latest stable Debian release which should get
4065 security support for a few years.
</p
>
4067 <p
>The web service is written in Perl, and depend on some perl modules
4068 that are missing in Debian at the moment. It would be great if these
4069 modules were added to the Debian archive, allowing anyone to set up
4070 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
4071 in their own country using only Debian packages. The list of modules
4072 missing in Debian/Squeeze isn
't very long, and I hope the perl group
4073 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
4074 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4075 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4076 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4077 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4078 easier in the future.
</p
>
4080 <p
>Thanks to the great tools in Debian, getting the missing modules
4081 installed on my server was a simple call to
'cpan2deb Module::Name
'
4082 and
'dpkg -i
' to install the resulting package. But this leave me
4083 with the responsibility of tracking security problems, which I really
4084 do not have time for.
</p
>
4089 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
4090 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
4091 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
4092 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
4093 <description><p
>Here is a small update for my English readers. Most of my blog
4094 posts have been in Norwegian the last few weeks, so here is a short
4095 update in English.
</p
>
4097 <p
>The kids still keep me too busy to get much free software work
4098 done, but I did manage to organise a project to get a Norwegian port
4099 of the British service
4100 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
4101 and it has been running for a month now. The entire project has been
4102 organised by me and two others. Around Christmas we gathered sponsors
4103 to fund the development work. In January I drafted a contract with
4104 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
4105 and in February the development took place. Most of it involved
4106 converting the source to use GPS coordinates instead of British
4107 easting/northing, and the resulting code should be a lot easier to get
4108 running in any country by now. The Norwegian
4109 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
4110 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
4111 source and the source for administrative borders in Norway, and
4112 support for this had to be added/fixed.
</p
>
4114 <p
>The Norwegian version went live March
3th, and we spent the weekend
4115 polishing the system before we announced it March
7th. The system is
4116 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
4117 problem reports in a few weeks. Soon we hope to announce the Android
4118 and iPhone versions making it even easier to report problems with the
4119 public infrastructure.
</p
>
4121 <p
>Perhaps something to consider for those of you in countries without
4122 such service?
</p
>
4127 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
4128 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
4129 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
4130 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
4131 <description><p
>The last few days I have looked at ways to track open security
4132 issues here at my work with the University of Oslo. My idea is that
4133 it should be possible to use the information about security issues
4134 available on the Internet, and check our locally
4135 maintained/distributed software against this information. It should
4136 allow us to verify that no known security issues are forgotten. The
4137 CVE database listing vulnerabilities seem like a great central point,
4138 and by using the package lists from Debian mapped to CVEs provided by
4139 the testing security team, I believed it should be possible to figure
4140 out which security holes were present in our free software
4141 collection.
</p
>
4143 <p
>After reading up on the topic, it became obvious that the first
4144 building block is to be able to name software packages in a unique and
4145 consistent way across data sources. I considered several ways to do
4146 this, for example coming up with my own naming scheme like using URLs
4147 to project home pages or URLs to the Freshmeat entries, or using some
4148 existing naming scheme. And it seem like I am not the first one to
4149 come across this problem, as MITRE already proposed and implemented a
4150 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
4151 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
4152 software, hardware and other platform components. The CPE ids are
4153 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
4154 Vulnerability Database
</a
>, allowing me to look up know security
4155 issues for any CPE name. With this in place, all I need to do is to
4156 locate the CPE id for the software packages we use at the university.
4157 This is fairly trivial (I google for
'cve cpe $package
' and check the
4158 NVD entry if a CVE for the package exist).
</p
>
4160 <p
>To give you an example. The GNU gzip source package have the CPE
4161 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
4162 check out, one could look up
4163 <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
4164 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
4165 The most recent one is
4166 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
4167 and at the bottom of the NVD page for this vulnerability the complete
4168 list of affected versions is provided.
</p
>
4170 <p
>The NVD database of CVEs is also available as a XML dump, allowing
4171 for offline processing of issues. Using this dump, I
've written a
4172 small script taking a list of CPEs as input and list all CVEs
4173 affecting the packages represented by these CPEs. One give it CPEs
4174 with version numbers as specified above and get a list of open
4175 security issues out.
</p
>
4177 <p
>Of course for this approach to be useful, the quality of the NVD
4178 information need to be high. For that to happen, I believe as many as
4179 possible need to use and contribute to the NVD database. I notice
4181 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
4182 map from CVE to CPE
</a
>, indicating that they are using the CPE
4183 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
4185 <p
>To get an idea about the quality for free software, I spent some
4186 time making it possible to compare the CVE database from Debian with
4187 the CVE database in NVD. The result look fairly good, but there are
4188 some inconsistencies in NVD (same software package having several
4189 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4190 Debian believe are affected by a CVE). Hope to find time to improve
4191 the quality of NVD, but that require being able to get in touch with
4192 someone maintaining it. So far my three emails with questions and
4193 corrections have not seen any reply, but I hope contact can be
4194 established soon.
</p
>
4196 <p
>An interesting application for CPEs is cross platform package
4197 mapping. It would be useful to know which packages in for example
4198 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4199 this would be trivial if all linux distributions provided CPE entries
4200 for their packages.
</p
>
4205 <title>Which module is loaded for a given PCI and USB device?
</title>
4206 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
4207 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
4208 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
4209 <description><p
>In the
4210 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
4211 package in Debian, there is a script to report useful information
4212 about the running hardware for use when people report missing
4213 information. One part of this script that I find very useful when
4214 debugging hardware problems, is the part mapping loaded kernel module
4215 to the PCI device it claims. It allow me to quickly see if the kernel
4216 module I expect is driving the hardware I am struggling with. To see
4217 the output, make sure discover-data is installed and run
4218 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
4219 one of my machines like this:
</p
>
4223 10de:
03eb i2c_nforce2
4226 10de:
03f0 snd_hda_intel
4235 <p
>The code in question look like this, slightly modified for
4236 readability and to drop the output to file descriptor
3:
</p
>
4239 if [ -d /sys/bus/pci/devices/ ] ; then
4240 echo loaded pci modules:
4242 cd /sys/bus/pci/devices/
4243 for address in * ; do
4244 if [ -d
"$address/driver/module
" ] ; then
4245 module=`cd $address/driver/module ; pwd -P | xargs basename`
4246 if grep -q
"^$module
" /proc/modules ; then
4247 address=$(echo $address |sed s/
0000://)
4248 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
4249 echo
"$id $module
"
4258 <p
>Similar code could be used to extract USB device module
4262 if [ -d /sys/bus/usb/devices/ ] ; then
4263 echo loaded usb modules:
4265 cd /sys/bus/usb/devices/
4266 for address in * ; do
4267 if [ -d
"$address/driver/module
" ] ; then
4268 module=`cd $address/driver/module ; pwd -P | xargs basename`
4269 if grep -q
"^$module
" /proc/modules ; then
4270 address=$(echo $address |sed s/
0000://)
4271 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
4272 if [
"$id
" ] ; then
4273 echo
"$id $module
"
4283 <p
>This might perhaps be something to include in other tools as
4289 <title>How to test if a laptop is working with Linux
</title>
4290 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
4291 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
4292 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
4293 <description><p
>The last few days I have spent at work here at the
<a
4294 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
4295 batch of computers will work with Linux. Every year for the last few
4296 years the university have organised shared bid of a few thousand
4297 computers, and this year HP won the bid. Two different desktops and
4298 five different laptops are on the list this year. We in the UNIX
4299 group want to know which one of these computers work well with RHEL
4300 and Ubuntu, the two Linux distributions we currently handle at the
4301 university.
</p
>
4303 <p
>My test method is simple, and I share it here to get feedback and
4304 perhaps inspire others to test hardware as well. To test, I PXE
4305 install the OS version of choice, and log in as my normal user and run
4306 a few applications and plug in selected pieces of hardware. When
4307 something fail, I make a note about this in the test matrix and move
4308 on. If I have some spare time I try to report the bug to the OS
4309 vendor, but as I only have the machines for a short time, I rarely
4310 have the time to do this for all the problems I find.
</p
>
4312 <p
>Anyway, to get to the point of this post. Here is the simple tests
4313 I perform on a new model.
</p
>
4317 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
4318 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4319 RHEL5 and Debian Edu/Squeeze.
</li
>
4321 <li
>Is X.org working? If the graphical login screen show up after
4322 installation, X.org is working.
</li
>
4324 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
4325 package mesa-utils on Ubuntu) and writing down the frames per second
4326 reported by the program.
</li
>
4328 <li
>Is sound working? With Gnome and KDE, a sound is played when
4329 logging in, and if I can hear this the test is successful. If there
4330 are several audio exits on the machine, I try them all and check if
4331 the Gnome/KDE audio mixer can control where to send the sound. I
4332 normally test this by playing
4333 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
4334 video
</a
> in Firefox/Iceweasel.
</li
>
4336 <li
>Is the USB subsystem working? I test this by plugging in a USB
4337 memory stick and see if Gnome/KDE notices this.
</li
>
4339 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
4340 I have lying around, and see if Gnome/KDE notices this.
</li
>
4342 <li
>Is any built in camera working? Test using cheese, and see if a
4343 picture from the v4l device show up.
</li
>
4345 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4346 any bluetooth devices are discovered. In my office, I normally see a
4349 <li
>For laptops, is the SD or Compaq Flash reader working. I have
4350 memory modules lying around, and stick them in and see if Gnome/KDE
4351 notice this.
</li
>
4353 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
4354 special button work, and if the laptop continue to work after
4357 <li
>For laptops, is the extra buttons working, like audio level,
4358 adjusting background light, switching on/off external video output,
4359 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4360 laptop to laptop, so I just write down which are working and which are
4363 <li
>Some laptops have smart card readers, finger print readers,
4364 acceleration sensors etc. I rarely test these, as I do not know how
4365 to quickly test if they are working or not, so I only document their
4366 existence.
</li
>
4370 <p
>By now I suspect you are really curious what the test results are
4371 for the HP machines I am testing. I
'm not done yet, so I will report
4372 the test results later. For now I can report that HP
8100 Elite work
4373 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
4374 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
4375 can see, I have most machines left to test. One interesting
4376 observation is that Ubuntu Lucid has almost twice the frame rate than
4377 RHEL6 with glxgears. No idea why.
</p
>
4382 <title>Some thoughts on BitCoins
</title>
4383 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
4384 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
4385 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
4386 <description><p
>As I continue to explore
4387 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
4388 what properties the system have, and how it will be affected by laws
4389 and regulations here in Norway. Here are some random notes.
</p
>
4391 <p
>One interesting thing to note is that since the transactions are
4392 verified using a peer to peer network, all details about a transaction
4393 is known to everyone. This means that if a BitCoin address has been
4394 published like I did with mine in my initial post about BitCoin, it is
4395 possible for everyone to see how many BitCoins have been transfered to
4396 that address. There is even a web service to look at the details for
4397 all transactions. There I can see that my address
4398 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
4399 have received
16.06 Bitcoin, the
4400 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
4401 address of Simon Phipps have received
181.97 BitCoin and the address
4402 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
4403 of EFF have received
2447.38 BitCoins so far. Thank you to each and
4404 every one of you that donated bitcoins to support my activity. The
4405 fact that anyone can see how much money was transfered to a given
4406 address make it more obvious why the BitCoin community recommend to
4407 generate and hand out a new address for each transaction. I
'm told
4408 there is no way to track which addresses belong to a given person or
4409 organisation without the person or organisation revealing it
4410 themselves, as Simon, EFF and I have done.
</p
>
4412 <p
>In Norway, and in most other countries, there are laws and
4413 regulations limiting how much money one can transfer across the border
4414 without declaring it. There are money laundering, tax and accounting
4415 laws and regulations I would expect to apply to the use of BitCoin.
4416 If the Skolelinux foundation
4417 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
4418 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
4419 normal bank transfers like EFF is doing, how should this be accounted?
4420 Given that it is impossible to know if money can cross the border or
4421 not, should everything or nothing be declared? What exchange rate
4422 should be used when calculating taxes? Would receivers have to pay
4423 income tax if the foundation were to pay Skolelinux contributors in
4424 BitCoin? I have no idea, but it would be interesting to know.
</p
>
4426 <p
>For a currency to be useful and successful, it must be trusted and
4427 accepted by a lot of users. It must be possible to get easy access to
4428 the currency (as a wage or using currency exchanges), and it must be
4429 easy to spend it. At the moment BitCoin seem fairly easy to get
4430 access to, but there are very few places to spend it. I am not really
4431 a regular user of any of the vendor types currently accepting BitCoin,
4432 so I wonder when my kind of shop would start accepting BitCoins. I
4433 would like to buy electronics, travels and subway tickets, not herbs
4434 and books. :) The currency is young, and this will improve over time
4435 if it become popular, but I suspect regular banks will start to lobby
4436 to get BitCoin declared illegal if it become popular. I
'm sure they
4437 will claim it is helping fund terrorism and money laundering (which
4438 probably would be true, as is any currency in existence), but I
4439 believe the problems should be solved elsewhere and not by blaming
4440 currencies.
</p
>
4442 <p
>The process of creating new BitCoins is called mining, and it is
4443 CPU intensive process that depend on a bit of luck as well (as one is
4444 competing against all the other miners currently spending CPU cycles
4445 to see which one get the next lump of cash). The
"winner
" get
50
4446 BitCoin when this happen. Yesterday I came across the obvious way to
4447 join forces to increase ones changes of getting at least some coins,
4448 by coordinating the work on mining BitCoins across several machines
4449 and people, and sharing the result if one is lucky and get the
50
4451 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
4452 if this sounds interesting. I have not had time to try to set up a
4453 machine to participate there yet, but have seen that running on ones
4454 own for a few days have not yield any BitCoins througth mining
4457 <p
>Update
2010-
12-
15: Found an
<a
4458 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
4459 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
4460 it was interesting to read. The arguments presented seem to be
4461 equally valid for gold, which was used as a currency for many years.
</p
>
4466 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
4467 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
4468 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
4469 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
4470 <description><p
>With this weeks lawless
4471 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
4472 attacks
</a
> on Wikileak and
4473 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
4474 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
4475 not be trusted to handle money transactions.
4477 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
4478 Phipps on bitcoin
</a
> reminded me about a project that a friend of
4479 mine mentioned earlier. I decided to follow Simon
's example, and get
4480 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
4481 some help from my friend to get it all running, and he even handed me
4482 some bitcoins to get started. I even donated a few bitcoins to Simon
4483 for helping me remember BitCoin.
</p
>
4485 <p
>So, what is bitcoins, you probably wonder? It is a digital
4486 crypto-currency, decentralised and handled using peer-to-peer
4487 networks. It allows anonymous transactions and prohibits central
4488 control over the transactions, making it impossible for governments
4489 and companies alike to block donations and other transactions. The
4490 source is free software, and while the key dependency wxWidgets
2.9
4491 for the graphical user interface is missing in Debian, the command
4492 line client builds just fine. Hopefully Jonas
4493 <a href=
"http://bugs.debian.org/
578157">will get the package into
4494 Debian
</a
> soon.
</p
>
4496 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
4497 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
4498 bitcoins
</a
> when selling services and goods, and there are even
4499 currency
"stock
" markets where the exchange rate is decided. There
4500 are not many users so far, but the concept seems promising. If you
4501 want to get started and lack a friend with any bitcoins to spare,
4503 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
4504 bitcoin at the time of writing). Use
4505 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
4506 on the current exchange rates.
</p
>
4508 <p
>As an experiment, I have decided to set up bitcoind on one of my
4509 machines. If you want to support my activity, please send Bitcoin
4510 donations to the address
4511 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
4516 <title>Why isn
't Debian Edu using VLC?
</title>
4517 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
4518 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
4519 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
4520 <description><p
>In the latest issue of Linux Journal, the readers choices were
4521 presented, and the winner among the multimedia player were VLC.
4522 Personally, I like VLC, and it is my player of choice when I first try
4523 to play a video file or stream. Only if VLC fail will I drag out
4524 gmplayer to see if it can do better. The reason is mostly the failure
4525 model and trust. When VLC fail, it normally pop up a error message
4526 reporting the problem. When mplayer fail, it normally segfault or
4527 just hangs. The latter failure mode drain my trust in the program.
<p
>
4529 <p
>But even if VLC is my player of choice, we have choosen to use
4530 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
4531 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
4532 plugin to play web videos seamlessly, and the VLC browser plugin is
4533 not very good. For example, it lack in-line control buttons, so there
4534 is no way for the user to pause the video. Also, when I
4535 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
4536 tested the browser plugins
</a
> available in Debian, the VLC plugin
4537 failed on several video pages where mplayer based plugins worked. If
4538 the browser plugin for VLC was as good as the gecko-mediaplayer
4539 package (which uses mplayer), we would switch.
</P
>
4541 <p
>While VLC is a good player, its user interface is slightly
4542 annoying. The most annoying feature is its inconsistent use of
4543 keyboard shortcuts. When the player is in full screen mode, its
4544 shortcuts are different from when it is playing the video in a window.
4545 For example, space only work as pause when in full screen mode. I
4546 wish it had consisten shortcuts and that space also would work when in
4547 window mode. Another nice shortcut in gmplayer is [enter] to restart
4548 the current video. It is very nice when playing short videos from the
4549 web and want to restart it when new people arrive to have a look at
4550 what is going on.
</p
>
4555 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
4556 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
4557 <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>
4558 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
4559 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
4560 upgrade testing of the
4561 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
4562 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
4563 This seem like a very good idea, so I adjusted by test scripts and
4564 can now present the updated result from today:
</p
>
4566 <p
>This is for Gnome:
</p
>
4568 <p
>Installed using apt-get, missing with aptitude
</p
>
4570 <blockquote
><p
>
4575 browser-plugin-gnash
4582 freedesktop-sound-theme
4584 gconf-defaults-service
4599 gnome-desktop-environment
4603 gnome-session-canberra
4608 gstreamer0.10-fluendo-mp3
4614 libapache2-mod-dnssd
4617 libaprutil1-dbd-sqlite3
4620 libboost-date-time1.42
.0
4621 libboost-python1.42
.0
4622 libboost-thread1.42
.0
4624 libchamplain-gtk-
0.4-
0
4626 libclutter-gtk-
0.10-
0
4633 libfreerdp-plugins-standard
4648 libgnomepanel2.24-cil
4653 libgtksourceview2.0-common
4654 libmono-addins-gui0.2-cil
4655 libmono-addins0.2-cil
4656 libmono-cairo2.0-cil
4657 libmono-corlib2.0-cil
4658 libmono-i18n-west2.0-cil
4659 libmono-posix2.0-cil
4660 libmono-security2.0-cil
4661 libmono-sharpzip2.84-cil
4662 libmono-system2.0-cil
4665 libndesk-dbus-glib1.0-cil
4666 libndesk-dbus1.0-cil
4676 libtelepathy-farsight0
4685 nautilus-sendto-empathy
4689 python-aptdaemon-gtk
4691 python-beautifulsoup
4706 python-gtksourceview2
4717 python-pkg-resources
4724 python-twisted-conch
4730 python-zope.interface
4735 rhythmbox-plugin-cdrecorder
4742 system-config-printer-udev
4744 telepathy-mission-control-
5
4755 </p
></blockquote
>
4757 <p
>Installed using apt-get, removed with aptitude
</p
>
4759 <blockquote
><p
>
4765 fast-user-switch-applet
4784 libgtksourceview2.0-
0
4786 libsdl1.2debian-alsa
4792 system-config-printer
4797 </p
></blockquote
>
4799 <p
>Installed using aptitude, missing with apt-get
</p
>
4801 <blockquote
><p
>
4802 gstreamer0.10-gnomevfs
4803 </p
></blockquote
>
4805 <p
>Installed using aptitude, removed with apt-get
</p
>
4807 <blockquote
><p
>
4809 </p
></blockquote
>
4811 <p
>This is for KDE:
</p
>
4813 <p
>Installed using apt-get, missing with aptitude
</p
>
4815 <blockquote
><p
>
4817 </p
></blockquote
>
4819 <p
>Installed using apt-get, removed with aptitude
</p
>
4821 <blockquote
><p
>
4824 </p
></blockquote
>
4826 <p
>Installed using aptitude, missing with apt-get
</p
>
4828 <blockquote
><p
>
4842 kdeartwork-emoticons
4844 kdeartwork-theme-icon
4848 kdebase-workspace-bin
4849 kdebase-workspace-data
4863 kscreensaver-xsavers
4878 plasma-dataengines-workspace
4880 plasma-desktopthemes-artwork
4881 plasma-runners-addons
4882 plasma-scriptengine-googlegadgets
4883 plasma-scriptengine-python
4884 plasma-scriptengine-qedje
4885 plasma-scriptengine-ruby
4886 plasma-scriptengine-webkit
4887 plasma-scriptengines
4888 plasma-wallpapers-addons
4889 plasma-widget-folderview
4890 plasma-widget-networkmanagement
4894 xscreensaver-data-extra
4896 xscreensaver-gl-extra
4897 xscreensaver-screensaver-bsod
4898 </p
></blockquote
>
4900 <p
>Installed using aptitude, removed with apt-get
</p
>
4902 <blockquote
><p
>
4904 google-gadgets-common
4922 libggadget-qt-
1.0-
0b
4927 libkonqsidebarplugin4a
4936 libplasma-geolocation-interface4
4938 libplasmagenericshell4
4952 libsmokeknewstuff2-
3
4953 libsmokeknewstuff3-
3
4955 libsmokektexteditor3
4963 libsmokeqtnetwork4-
3
4969 libsmokeqtuitools4-
3
4981 plasma-dataengines-addons
4982 plasma-scriptengine-superkaramba
4983 plasma-widget-lancelot
4984 plasma-widgets-addons
4985 plasma-widgets-workspace
4989 update-notifier-common
4990 </p
></blockquote
>
4992 <p
>Running apt-get autoremove made the results using apt-get and
4993 aptitude a bit more similar, but there are still quite a lott of
4994 differences. I have no idea what packages should be installed after
4995 the upgrade, but hope those that do can have a look.
</p
>
5000 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
5001 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
5002 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
5003 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
5004 <description><p
>Most of the computers in use by the
5005 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
5006 are virtual machines. And they have been Xen machines running on a
5007 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
5008 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
5009 bit harder that it could have been, because we set up the Xen virtual
5010 machines to get the virtual partitions from LVM, which as far as I
5011 know is not supported by KVM. So to migrate, we had to convert
5012 several LVM logical volumes to partitions on a virtual disk file.
</p
>
5015 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
5016 nice recipe
</a
> to do this, and wrote the following script to do the
5017 migration. It uses qemu-img from the qemu package to make the disk
5018 image, parted to partition it, losetup and kpartx to present the disk
5019 image partions as devices, and dd to copy the data. I NFS mounted the
5020 new servers storage area on the old server to do the migration.
</p
>
5026 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5031 if [ -z
"$
1" ] ; then
5032 echo
"Usage: $
0 &lt;hostname
&gt;
"
5038 if [ ! -e /dev/vg_data/$host-disk ] ; then
5039 echo
"error: unable to find LVM volume for $host
"
5043 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5044 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
5045 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
5046 totalsize=$(( ( $disksize + $swapsize ) ))
5049 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
5050 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5052 parted $img mklabel msdos
5053 parted $img mkpart primary linux-swap
0 $disksize
5054 parted $img mkpart primary ext2 $disksize $totalsize
5055 parted $img set
1 boot on
5058 losetup /dev/loop0 $img
5059 kpartx -a /dev/loop0
5061 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
5062 fsck.ext3 -f /dev/mapper/loop0p1 || true
5063 mkswap /dev/mapper/loop0p2
5065 kpartx -d /dev/loop0
5066 losetup -d /dev/loop0
5069 <p
>The script is perhaps so simple that it is not copyrightable, but
5070 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
5072 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
5073 the new disk image attached, installed grub-pc and linux-image-
686 and
5074 set up grub to boot from the disk image. After this, the KVM machines
5075 seem to work just fine.
</p
>
5080 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
5081 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
5082 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
5083 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
5084 <description><p
>I
'm still running upgrade testing of the
5085 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
5086 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
5087 status. Here is a short update based on a test I ran
20101118.
</p
>
5089 <p
>I still do not know what a correct migration should look like, so I
5090 report any differences between apt and aptitude and hope someone else
5091 can see if anything should be changed.
</p
>
5093 <p
>This is for Gnome:
</p
>
5095 <p
>Installed using apt-get, missing with aptitude
</p
>
5097 <blockquote
><p
>
5098 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5099 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
5100 dmz-cursor-theme empathy empathy-common finger
5101 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5102 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5103 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5104 gnome-cards-data gnome-codec-install gnome-core
5105 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5106 gnome-search-tool gnome-session-canberra gnome-spell
5107 gnome-system-log gnome-themes-extras gnome-themes-more
5108 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5109 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5110 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5111 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5112 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
5113 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
5114 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
5115 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
5116 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
5117 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5118 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
5119 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5120 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5121 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5122 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5123 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5124 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5125 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5126 libmono-security2.0-cil libmono-sharpzip2.84-cil
5127 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
5128 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
5129 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
5130 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
5131 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
5132 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
5133 libxalan2-java libxerces2-java media-player-info mesa-utils
5134 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
5135 nautilus-sendto-empathy openoffice.org-writer2latex
5136 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
5137 python-aptdaemon python-aptdaemon-gtk python-axiom
5138 python-beautifulsoup python-bugbuddy python-clientform
5139 python-coherence python-configobj python-crypto python-cupshelpers
5140 python-cupsutils python-eggtrayicon python-elementtree
5141 python-epsilon python-evolution python-feedparser python-gdata
5142 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5143 python-gtksourceview2 python-httplib2 python-louie python-mako
5144 python-markupsafe python-mechanize python-nevow python-notify
5145 python-opengl python-openssl python-pam python-pkg-resources
5146 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5147 python-tagpy python-twisted-bin python-twisted-conch
5148 python-twisted-core python-twisted-web python-utidylib python-webkit
5149 python-xdg python-zope.interface remmina remmina-plugin-data
5150 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5151 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5152 software-center svgalibg1 system-config-printer-udev
5153 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
5154 totem totem-coherence totem-mozilla totem-plugins
5155 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5157 </p
></blockquote
>
5159 Installed using apt-get, removed with aptitude
5161 <blockquote
><p
>
5162 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5163 epiphany-extensions epiphany-gecko evolution-exchange
5164 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5165 gedit-common gnome-app-install gnome-games gnome-games-data
5166 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5167 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5168 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5169 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
5170 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
5171 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
5172 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
5173 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
5174 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
5175 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
5176 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
5177 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
5178 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5179 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5180 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5181 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5182 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
5183 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
5184 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
5185 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
5186 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
5187 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5188 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5189 sound-juicer swfdec-gnome system-config-printer totem-common
5190 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5191 </p
></blockquote
>
5193 <p
>Installed using aptitude, missing with apt-get
</p
>
5195 <blockquote
><p
>
5196 gstreamer0.10-gnomevfs
5197 </p
></blockquote
>
5199 <p
>Installed using aptitude, removed with apt-get
</p
>
5201 <blockquote
><p
>
5203 </p
></blockquote
>
5205 <p
>This is for KDE:
</p
>
5207 <p
>Installed using apt-get, missing with aptitude
</p
>
5209 <blockquote
><p
>
5210 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
5211 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5212 ghostscript-x git gnome-audio gnugo granatier gs-common
5213 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5214 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5215 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5216 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5217 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5218 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5219 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5220 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5221 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5222 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5223 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5224 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
5225 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5226 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5227 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5228 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5229 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5230 libkrossui4 libmailtools-perl libmime-tools-perl
5231 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5232 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5233 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5234 lirc luatex marble networkstatus noatun-plugins
5235 openoffice.org-writer2latex palapeli palapeli-data parley
5236 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5237 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5238 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5240 </p
></blockquote
>
5242 <p
>Installed using apt-get, removed with aptitude
</p
>
5244 <blockquote
><p
>
5245 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5246 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5247 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5248 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5249 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5250 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5251 kitchensync kiten kjumpingcube klatin klettres klickety klines
5252 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5253 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5254 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5255 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5256 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5257 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5258 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5259 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5260 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5261 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
5262 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
5263 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5264 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
5265 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
5266 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5267 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5268 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5269 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5270 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5271 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5272 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
5273 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
5274 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5275 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5276 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5277 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5278 </p
></blockquote
>
5280 <p
>Installed using aptitude, missing with apt-get
</p
>
5282 <blockquote
><p
>
5283 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5284 kdeartwork kdebase kdebase-apps kdebase-workspace
5285 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5286 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5287 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5288 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5289 xscreensaver-screensaver-bsod
5290 </p
></blockquote
>
5292 <p
>Installed using aptitude, removed with apt-get
</p
>
5294 <blockquote
><p
>
5295 kdebase-bin konq-plugins konqueror
5296 </p
></blockquote
>
5301 <title>Gnash buildbot slave and Debian kfreebsd
</title>
5302 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
5303 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
5304 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
5305 <description><p
>Answering
5306 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
5307 call from the Gnash project
</a
> for
5308 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
5309 current source, I have set up a virtual KVM machine on the Debian
5310 Edu/Skolelinux virtualization host to test the git source on
5311 Debian/Squeeze. I hope this can help the developers in getting new
5312 releases out more often.
</p
>
5314 <p
>As the developers want less main-stream build platforms tested to,
5315 I have considered setting up a
<a
5316 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
5317 machine as well. I have also considered using the kfreebsd
5318 architecture in Debian as a file server in NUUG to get access to the
5
5319 TB zfs volume we currently use to store DV video. Because of this, I
5320 finally got around to do a test installation of Debian/Squeeze with
5321 kfreebsd. Installation went fairly smooth, thought I noticed some
5322 visual glitches in the cdebconf dialogs (black cursor left on the
5323 screen at random locations). Have not gotten very far with the
5324 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5325 fatal problem. Have to spend some more time on it to see if it is
5326 useful as a file server for NUUG. Will try to find time to set up a
5327 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
5332 <title>Debian in
3D
</title>
5333 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
5334 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
5335 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
5336 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
5338 <p
>3D printing is just great. I just came across this Debian logo in
5340 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
5341 thingiverse blog
</a
>.
</p
>
5346 <title>Software updates
2010-
10-
24</title>
5347 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
5348 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
5349 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
5350 <description><p
>Some updates.
</p
>
5352 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
5353 raise money for the project is going well. The lower limit of
10
5354 signers was reached in
24 hours, and so far
13 people have signed it.
5355 More signers and more funding is most welcome, and I am really curious
5356 how far we can get before the time limit of December
24 is reached.
5359 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
5360 about what appear to be a great code coverage tool capable of
5361 generating code coverage stats without any changes to the source code.
5363 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
5364 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
5365 It is missing in Debian, but the git source built just fine in Squeeze
5366 after I installed libelf-dev, libdwarf-dev, pkg-config and
5367 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5368 solvable. I hope kcov make it into Debian soon.
</p
>
5370 <p
>Finally found time to wrap up the release notes for
<a
5371 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
5372 new alpha release of Debian Edu
</a
>, and just published the second
5373 alpha test release of the Squeeze based Debian Edu /
5374 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
5375 release. Give it a try if you need a complete linux solution for your
5376 school, including central infrastructure server, workstations, thin
5377 client servers and diskless workstations. A nice touch added
5378 yesterday is RDP support on the thin client servers, for windows
5379 clients to get a Linux desktop on request.
</p
>
5384 <title>Some notes on Flash in Debian and Debian Edu
</title>
5385 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
5386 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
5387 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
5388 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
5389 popularity-contest numbers
</a
>, the adobe-flashplugin package the
5390 second most popular used package that is missing in Debian. The sixth
5391 most popular is flashplayer-mozilla. This is a clear indication that
5392 working flash is important for Debian users. Around
10 percent of the
5393 users submitting data to popcon.debian.org have this package
5394 installed.
</p
>
5396 <p
>In the report written by Lars Risan in August
2008
5397 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
5398 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5399 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
5400 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
5401 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
5402 web sites require Flash to work, and lacking working Flash support in
5403 the web browser and the problems with installing it was perceived as a
5404 good reason to stay with Windows.
</p
>
5406 <p
>I once saw a funny and sad comment in a web forum, where Linux was
5407 said to be the retarded cousin that did not really understand
5408 everything you told him but could work fairly well. This was a
5409 comment regarding the problems Linux have with proprietary formats and
5410 non-standard web pages, and is sad because it exposes a fairly common
5411 understanding of whose fault it is if web pages that only work in for
5412 example Internet Explorer
6 fail to work on Firefox, and funny because
5413 it explain very well how annoying it is for users when Linux
5414 distributions do not work with the documents they receive or the web
5415 pages they want to visit.
</p
>
5417 <p
>This is part of the reason why I believe it is important for Debian
5418 and Debian Edu to have a well working Flash implementation in the
5419 distribution, to get at least popular sites as Youtube and Google
5420 Video to working out of the box. For Squeeze, Debian have the chance
5421 to include the latest version of Gnash that will make this happen, as
5422 the new release
0.8.8 was published a few weeks ago and is resting in
5423 unstable. The new version work with more sites that version
0.8.7.
5424 The Gnash maintainers have asked for a freeze exception, but the
5425 release team have not had time to reply to it yet. I hope they agree
5426 with me that Flash is important for the Debian desktop users, and thus
5427 accept the new package into Squeeze.
</p
>
5432 <title>Circular package dependencies harms apt recovery
</title>
5433 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
5434 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
5435 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
5436 <description><p
>I discovered this while doing
5437 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
5438 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
5439 in Debian still got circular dependencies, and it is often claimed
5440 that apt and aptitude should be able to handle this just fine, but
5441 some times these dependency loops causes apt to fail.
</p
>
5443 <p
>An example is from todays
5444 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
5445 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
5446 causes perl-modules to fail to upgrade. The cause is simple. If a
5447 package fail to unpack, then only part of packages with the circular
5448 dependency might end up being unpacked when unpacking aborts, and the
5449 ones already unpacked will fail to configure in the recovery phase
5450 because its dependencies are unavailable.
</p
>
5452 <p
>In this log, the problem manifest itself with this error:
</p
>
5454 <blockquote
><pre
>
5455 dpkg: dependency problems prevent configuration of perl-modules:
5456 perl-modules depends on perl (
>=
5.10.1-
1); however:
5457 Version of perl on system is
5.10.0-
19lenny
2.
5458 dpkg: error processing perl-modules (--configure):
5459 dependency problems - leaving unconfigured
5460 </pre
></blockquote
>
5462 <p
>The perl/perl-modules circular dependency is already
5463 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
5464 hopefully be solved as soon as possible, but it is not the only one,
5465 and each one of these loops in the dependency tree can cause similar
5466 failures. Of course, they only occur when there are bugs in other
5467 packages causing the unpacking to fail, but it is rather nasty when
5468 the failure of one package causes the problem to become worse because
5469 of dependency loops.
</p
>
5472 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
5473 tireless effort by Bill Allombert
</a
>, the number of circular
5475 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
5476 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
5478 <p
>Todays testing also exposed a bug in
5479 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
5480 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
5481 apt-get and aptitude, the latter possibly caused by some circular
5482 dependency. Reported both to BTS to try to get someone to look at
5488 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
5489 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
5490 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
5491 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
5492 <description><p
>This is a
5493 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
5495 <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
5497 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
5498 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
5500 <p
>As a step to try to see if it possible to merge the DNS and DHCP
5501 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5502 and dhcp3-server-ldap in Debian use the LDAP server. The two
5503 implementations are quite different in how they use LDAP.
</p
>
5505 To get this information, I started slapd with debugging enabled and
5506 dumped the debug output to a file to get the LDAP searches performed
5507 on a Debian Edu main-server. Here is a summary.
5509 <p
><strong
>powerdns
</strong
></p
>
5511 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
5512 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
5515 <p
>PowerDNS have two modes of operation using LDAP as its backend.
5516 One
"strict
" mode where the forward and reverse DNS lookups are done
5517 using the same LDAP objects, and a
"tree
" mode where the forward and
5518 reverse entries are in two different subtrees in LDAP with a structure
5519 based on the DNS names, as in tjener.intern and
5520 2.2.0.10.in-addr.arpa.
</p
>
5522 <p
>In tree mode, the server is set up to use a LDAP subtree as its
5523 base, and uses a
"base
" scoped search for the DNS name by adding
5524 "dc=tjener,dc=intern,
" to the base with a filter for
5525 "(associateddomain=tjener.intern)
" for the forward entry and
5526 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
5527 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
5528 forward entries, it is looking for attributes named dnsttl, arecord,
5529 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5530 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5531 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5532 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5533 spfrecord and modifytimestamp. For reverse entries it is looking for
5534 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5535 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5536 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5537 ldapsearch commands could look like this:
</p
>
5539 <blockquote
><pre
>
5540 ldapsearch -h ldap \
5541 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5542 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
5543 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5544 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5545 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5546 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5548 ldapsearch -h ldap \
5549 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5550 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
5551 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
5552 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
5553 srvrecord naptrrecord modifytimestamp
5554 </pre
></blockquote
>
5556 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
5557 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
5558 example LDAP objects used there. In addition to these objects, the
5559 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
5560 also exist.
</p
>
5562 <blockquote
><pre
>
5563 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
5565 objectclass: dnsdomain
5566 objectclass: domainrelatedobject
5569 associateddomain: tjener.intern
5571 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
5573 objectclass: dnsdomain2
5574 objectclass: domainrelatedobject
5576 ptrrecord: tjener.intern
5577 associateddomain:
2.2.0.10.in-addr.arpa
5578 </pre
></blockquote
>
5580 <p
>In strict mode, the server behaves differently. When looking for
5581 forward DNS entries, it is doing a
"subtree
" scoped search with the
5582 same base as in the tree mode for a object with filter
5583 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
5584 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
5585 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
5586 naptrrecord and modifytimestamp. For reverse entires it also do a
5587 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
5588 and the requested attributes are associateddomain, dnsttl and
5589 modifytimestamp. In short, in strict mode the objects with ptrrecord
5590 go away, and the arecord attribute in the forward object is used
5593 <p
>The forward and reverse searches can be simulated using ldapsearch
5594 like this:
</p
>
5596 <blockquote
><pre
>
5597 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5598 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
5599 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5600 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5601 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5602 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5604 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5605 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
5606 </pre
></blockquote
>
5608 <p
>In addition to the forward and reverse searches , there is also a
5609 search for SOA records, which behave similar to the forward and
5610 reverse lookups.
</p
>
5612 <p
>A thing to note with the PowerDNS behaviour is that it do not
5613 specify any objectclass names, and instead look for the attributes it
5614 need to generate a DNS reply. This make it able to work with any
5615 objectclass that provide the needed attributes.
</p
>
5617 <p
>The attributes are normally provided in the cosine (RFC
1274) and
5618 dnsdomain2 schemas. The latter is used for reverse entries like
5619 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
5621 <p
>In Debian Edu, we have created DNS objects using the object classes
5622 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
5623 attributes) and domainrelatedobject (for associatedDomain). The use
5624 of structural object classes make it impossible to combine these
5625 classes with the object classes used by DHCP.
</p
>
5627 <p
>There are other schemas that could be used too, for example the
5628 dnszone structural object class used by Gosa and bind-sdb for the DNS
5629 attributes combined with the domainrelatedobject object class, but in
5630 this case some unused attributes would have to be included as well
5631 (zonename and relativedomainname).
</p
>
5633 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
5634 mode and not use any of the existing objectclasses (dnsdomain,
5635 dnsdomain2 and dnszone) when one want to combine the DNS information
5636 with DHCP information, and instead create a auxiliary object class
5637 defined something like this (using the attributes defined for
5638 dnsdomain and dnsdomain2 or dnszone):
</p
>
5640 <blockquote
><pre
>
5641 objectclass ( some-oid NAME
'dnsDomainAux
'
5644 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
5645 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
5646 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
5647 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
5648 A6Record $ DNAMERecord
5650 </pre
></blockquote
>
5652 <p
>This will allow any object to become a DNS entry when combined with
5653 the domainrelatedobject object class, and allow any entity to include
5654 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
5655 developers asking for their view on this schema and if they are
5656 interested in providing such schema with PowerDNS, and I hope my
5657 message will be accepted into their mailing list soon.
</p
>
5659 <p
><strong
>ISC dhcp
</strong
></p
>
5661 <p
>The DHCP server searches for specific objectclass and requests all
5662 the object attributes, and then uses the attributes it want. This
5663 make it harder to figure out exactly what attributes are used, but
5664 thanks to the working example in Debian Edu I can at least get an idea
5665 what is needed without having to read the source code.
</p
>
5667 <p
>In the DHCP server configuration, the LDAP base to use and the
5668 search filter to use to locate the correct dhcpServer entity is
5669 stored. These are the relevant entries from
5670 /etc/dhcp3/dhcpd.conf:
</p
>
5672 <blockquote
><pre
>
5673 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
5674 ldap-dhcp-server-cn
"dhcp
";
5675 </pre
></blockquote
>
5677 <p
>The DHCP server uses this information to nest all the DHCP
5678 configuration it need. The cn
"dhcp
" is located using the given LDAP
5679 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
5680 search result is this entry:
</p
>
5682 <blockquote
><pre
>
5683 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
5686 objectClass: dhcpServer
5687 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5688 </pre
></blockquote
>
5690 <p
>The content of the dhcpServiceDN attribute is next used to locate the
5691 subtree with DHCP configuration. The DHCP configuration subtree base
5692 is located using a base scope search with base
"cn=DHCP
5693 Config,dc=skole,dc=skolelinux,dc=no
" and filter
5694 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
5695 The search result is this entry:
</p
>
5697 <blockquote
><pre
>
5698 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5701 objectClass: dhcpService
5702 objectClass: dhcpOptions
5703 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
5704 dhcpStatements: ddns-update-style none
5705 dhcpStatements: authoritative
5706 dhcpOption: smtp-server code
69 = array of ip-address
5707 dhcpOption: www-server code
72 = array of ip-address
5708 dhcpOption: wpad-url code
252 = text
5709 </pre
></blockquote
>
5711 <p
>Next, the entire subtree is processed, one level at the time. When
5712 all the DHCP configuration is loaded, it is ready to receive requests.
5713 The subtree in Debian Edu contain objects with object classes
5714 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
5715 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
5716 and information about netmasks, dynamic range etc. Leaving out the
5717 details here because it is not relevant for the focus of my
5718 investigation, which is to see if it is possible to merge dns and dhcp
5719 related computer objects.
</p
>
5721 <p
>When a DHCP request come in, LDAP is searched for the MAC address
5722 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
5723 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
5724 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
5725 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
5728 <blockquote
><pre
>
5729 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5732 objectClass: dhcpHost
5733 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
5734 dhcpStatements: fixed-address hostname
5735 </pre
></blockquote
>
5737 <p
>There is less flexiblity in the way LDAP searches are done here.
5738 The object classes need to have fixed names, and the configuration
5739 need to be stored in a fairly specific LDAP structure. On the
5740 positive side, the invidiual dhcpHost entires can be anywhere without
5741 the DN pointed to by the dhcpServer entries. The latter should make
5742 it possible to group all host entries in a subtree next to the
5743 configuration entries, and this subtree can also be shared with the
5744 DNS server if the schema proposed above is combined with the dhcpHost
5745 structural object class.
5747 <p
><strong
>Conclusion
</strong
></p
>
5749 <p
>The PowerDNS implementation seem to be very flexible when it come
5750 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
5751 come to the the LDAP structure, the
"strict
" mode is very flexible,
5752 allowing DNS objects to be stored anywhere under the base cn specified
5753 in the configuration.
</p
>
5755 <p
>The DHCP implementation on the other hand is very inflexible, both
5756 regarding which LDAP schemas to use and which LDAP structure to use.
5757 I guess one could implement ones own schema, as long as the
5758 objectclasses and attributes have the names used, but this do not
5759 really help when the DHCP subtree need to have a fairly fixed
5760 structure.
</p
>
5762 <p
>Based on the observed behaviour, I suspect a LDAP structure like
5763 this might work for Debian Edu:
</p
>
5765 <blockquote
><pre
>
5767 cn=machine-info (dhcpService) - dhcpServiceDN points here
5768 cn=dhcp (dhcpServer)
5769 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
5770 cn=
10.0.2.0 (dhcpSubnet)
5771 cn=group1 (dhcpGroup/dhcpOptions)
5772 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
5773 cn=
192.168.0.0 (dhcpSubnet)
5774 cn=group1 (dhcpGroup/dhcpOptions)
5775 ou=machines - PowerDNS base points here
5776 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
5777 </pre
></blockquote
>
5779 <P
>This is not tested yet. If the DHCP server require the dhcpHost
5780 entries to be in the dhcpGroup subtrees, the entries can be stored
5781 there instead of a common machines subtree, and the PowerDNS base
5782 would have to be moved one level up to the machine-info subtree.
</p
>
5784 <p
>The combined object under the machines subtree would look something
5785 like this:
</p
>
5787 <blockquote
><pre
>
5788 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
5791 objectClass: dhcpHost
5792 objectclass: domainrelatedobject
5793 objectclass: dnsDomainAux
5794 associateddomain: hostname.intern
5795 arecord:
10.11.12.13
5796 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
5797 dhcpStatements: fixed-address hostname.intern
5798 </pre
></blockquote
>
5800 </p
>One could even add the LTSP configuration associated with a given
5801 machine, as long as the required attributes are available in a
5802 auxiliary object class.
</p
>
5807 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
5808 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
5809 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
5810 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
5811 <description><p
>For a while now, I have wanted to find a way to change the DNS and
5812 DHCP services in Debian Edu to use the same LDAP objects for a given
5813 computer, to avoid the possibility of having a inconsistent state for
5814 a computer in LDAP (as in DHCP but no DNS entry or the other way
5815 around) and make it easier to add computers to LDAP.
</p
>
5817 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
5818 information finally found a solution that seem to work.
</p
>
5820 <p
>The old setup required three LDAP objects for a given computer.
5821 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
5822 we switch powerdns to use its strict LDAP method (ldap-method=strict
5823 in pdns-debian-edu.conf), the forward and reverse DNS entries are
5824 merged into one while making it impossible to transfer the reverse map
5825 to a slave DNS server.
</p
>
5827 <p
>If we also replace the object class used to get the DNS related
5828 attributes to one allowing these attributes to be combined with the
5829 dhcphost object class, we can merge the DNS and DHCP entries into one.
5830 I
've written such object class in the dnsdomainaux.schema file (need
5831 proper OIDs, but that is a minor issue), and tested the setup. It
5832 seem to work.
</p
>
5834 <p
>With this test setup in place, we can get away with one LDAP object
5835 for both DNS and DHCP, and even the LTSP configuration I suggested in
5836 an earlier email. The combined LDAP object will look something like
5839 <blockquote
><pre
>
5840 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5842 objectClass: dhcphost
5843 objectclass: domainrelatedobject
5844 objectclass: dnsdomainaux
5845 associateddomain: hostname.intern
5846 arecord:
10.11.12.13
5847 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
5848 dhcpstatements: fixed-address hostname
5850 </pre
></blockquote
>
5852 <p
>The DNS server uses the associateddomain and arecord entries, while
5853 the DHCP server uses the dhcphwaddress and dhcpstatements entries
5854 before asking DNS to resolve the fixed-adddress. LTSP will use
5855 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
5857 <p
>I am not yet sure if I can get the DHCP server to look for its
5858 dhcphost in a different location, to allow us to put the objects
5859 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
5860 that. If I can
't figure out a way to do that, we can still get rid of
5861 the hosts subtree and move all its content into the DHCP Config tree
5862 (which probably should be renamed to be more related to the new
5863 content. I suspect cn=dnsdhcp,ou=services or something like that
5864 might be a good place to put it.
</p
>
5866 <p
>If you want to help out with implementing this for Debian Edu,
5867 please contact us on debian-edu@lists.debian.org.
</p
>
5872 <title>Idea for storing LTSP configuration in LDAP
</title>
5873 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
5874 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
5875 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
5876 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
5877 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
5878 clients, and that this can be used to fetch configuration from LDAP if
5879 Debian Edu choose to store configuration there.
</p
>
5881 <p
>Armed with this information, I got inspired and wrote a test module
5882 to get configuration from LDAP. The idea is to look up the MAC
5883 address of the client in LDAP, and look for attributes on the form
5884 ltspconfigsetting=value, and use this to export SETTING=value to the
5885 LTSP clients.
</p
>
5887 <p
>The goal is to be able to store the LTSP configuration attributes
5888 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
5889 allowing us to store all information about a computer in one place.
</p
>
5891 <p
>This is a untested draft implementation, and I welcome feedback on
5892 this approach. A real LDAP schema for the ltspClientAux objectclass
5893 need to be written. Comments, suggestions, etc?
</p
>
5895 <blockquote
><pre
>
5896 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
5898 # Fetch LTSP client settings from LDAP based on MAC address
5900 # Uses ethernet address as stored in the dhcpHost objectclass using
5901 # the dhcpHWAddress attribute or ethernet address stored in the
5902 # ieee802Device objectclass with the macAddress attribute.
5904 # This module is written to be schema agnostic, and only depend on the
5905 # existence of attribute names.
5907 # The LTSP configuration variables are saved directly using a
5908 # ltspConfig prefix and uppercasing the rest of the attribute name.
5909 # To set the SERVER variable, set the ltspConfigServer attribute.
5911 # Some LDAP schema should be created with all the relevant
5912 # configuration settings. Something like this should work:
5914 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
5917 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
5919 LDAPSERVER=$(debian-edu-ldapserver)
5920 if [
"$LDAPSERVER
" ] ; then
5921 LDAPBASE=$(debian-edu-ldapserver -b)
5922 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
5923 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
5924 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
5925 grep
'^ltspConfig
' | while read attr value ; do
5926 # Remove prefix and convert to upper case
5927 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
5928 # bass value on to clients
5929 eval
"$attr=$value; export $attr
"
5933 </pre
></blockquote
>
5935 <p
>I
'm not sure this shell construction will work, because I suspect
5936 the while block might end up in a subshell causing the variables set
5937 there to not show up in ltsp-config, but if that is the case I am sure
5938 the code can be restructured to make sure the variables are passed on.
5939 I expect that can be solved with some testing. :)
</p
>
5941 <p
>If you want to help out with implementing this for Debian Edu,
5942 please contact us on debian-edu@lists.debian.org.
</p
>
5944 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
5945 configuration in LDAP that was created around year
2000 by
5946 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
5947 Xperience, Inc.,
2000</a
>. I found its
5948 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
5949 personal home page over at redhat.com.
</p
>
5954 <title>jXplorer, a very nice LDAP GUI
</title>
5955 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
5956 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
5957 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
5958 <description><p
>Since
5959 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
5960 last post
</a
> about available LDAP tools in Debian, I was told about a
5961 LDAP GUI that is even better than luma. The java application
5962 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
5963 moving LDAP objects and subtrees using drag-and-drop, and can
5964 authenticate using Kerberos. I have only tested the Kerberos
5965 authentication, but do not have a LDAP setup allowing me to rewrite
5966 LDAP with my test user yet. It is
5967 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
5968 Debian
</a
> testing and unstable at the moment. The only problem I
5969 have with it is how it handle errors. If something go wrong, its
5970 non-intuitive behaviour require me to go through some query work list
5971 and remove the failing query. Nothing big, but very annoying.
</p
>
5976 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
5977 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
5978 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
5979 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
5980 <description><p
>Here is a short update on my
<a
5981 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
5982 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
5983 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
5984 not reporting the status for KDE, because the upgrade crashes when
5985 aptitude try because of missing conflicts
5986 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
5987 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
5989 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
5990 complete list of the installed packages. Based on this I see these
5991 differences when I did a test run today. As usual, I do not really
5992 know what the correct set of packages would be, but thought it best to
5993 publish the difference.
</p
>
5995 <p
>Installed using apt-get, missing with aptitude
</p
>
5997 <blockquote
><p
>
5998 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
5999 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
6000 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6001 libgtksourceview-common libpt-
1.10.10-plugins-alsa
6002 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6003 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6004 python-
4suite-xml python-eggtrayicon python-gtkhtml2
6005 python-gtkmozembed svgalibg1 xserver-xephyr zip
6006 </p
></blockquote
>
6008 <p
>Installed using apt-get, removed with aptitude
</p
>
6010 <blockquote
><p
>
6011 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6012 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6013 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
6014 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
6015 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
6016 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
6017 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
6018 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
6019 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
6020 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
6021 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
6022 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
6023 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6024 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
6025 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6026 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
6027 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
6028 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6029 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6030 mysql-common swfdec-gnome totem-gstreamer wodim
6031 </p
></blockquote
>
6033 <p
>Installed using aptitude, missing with apt-get
</p
>
6035 <blockquote
><p
>
6036 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6037 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6038 xserver-xorg-input-all xserver-xorg-input-evdev
6039 xserver-xorg-input-kbd xserver-xorg-input-mouse
6040 xserver-xorg-input-synaptics xserver-xorg-video-all
6041 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6042 xserver-xorg-video-chips xserver-xorg-video-cirrus
6043 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6044 xserver-xorg-video-glint xserver-xorg-video-i128
6045 xserver-xorg-video-i740 xserver-xorg-video-mach64
6046 xserver-xorg-video-mga xserver-xorg-video-neomagic
6047 xserver-xorg-video-nouveau xserver-xorg-video-nv
6048 xserver-xorg-video-r128 xserver-xorg-video-radeon
6049 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6050 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6051 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6052 xserver-xorg-video-sis xserver-xorg-video-sisusb
6053 xserver-xorg-video-tdfx xserver-xorg-video-tga
6054 xserver-xorg-video-trident xserver-xorg-video-tseng
6055 xserver-xorg-video-vesa xserver-xorg-video-vmware
6056 xserver-xorg-video-voodoo
6057 </p
></blockquote
>
6059 <p
>Installed using aptitude, removed with apt-get
</p
>
6061 <blockquote
><p
>
6062 deskbar-applet xserver-xorg xserver-xorg-core
6063 xserver-xorg-input-wacom xserver-xorg-video-intel
6064 xserver-xorg-video-openchrome
6065 </p
></blockquote
>
6067 <p
>I was told on IRC that the xorg-xserver package was
6068 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
6069 in git
</a
> today to try to get apt-get to not remove xorg completely.
6070 No idea when it hits Squeeze, but when it does I hope it will reduce
6071 the difference somewhat.
6076 <title>LUMA, a very nice LDAP GUI
</title>
6077 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
6078 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
6079 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
6080 <description><p
>The last few days I have been looking into the status of the LDAP
6081 directory in Debian Edu, and in the process I started to miss a GUI
6082 tool to browse the LDAP tree. The only one I was able to find in
6083 Debian/Squeeze and Lenny is
6084 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
6085 be a great tool to get a overview of the current LDAP directory
6086 populated by default in Skolelinux. Thanks to it, I have been able to
6087 find empty and obsolete subtrees, misplaced objects and duplicate
6088 objects. It will be installed by default in Debian/Squeeze. If you
6089 are working with LDAP, give it a go. :)
</p
>
6091 <p
>I did notice one problem with it I have not had time to report to
6092 the BTS yet. There is no .desktop file in the package, so the tool do
6093 not show up in the Gnome and KDE menus, but only deep down in in the
6094 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6097 <p
>I have not yet been able to get it to modify the tree yet. I would
6098 like to move objects and remove subtrees directly in the GUI, but have
6099 not found a way to do that with LUMA yet. So in the mean time, I use
6100 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
6102 <p
>If you have tips on other GUI tools for LDAP that might be useful
6103 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
6105 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
6106 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
6107 useful GUI alternative. It seem like a good tool, but is unmaintained
6108 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6109 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
6114 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
6115 <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>
6116 <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>
6117 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
6118 <description><p
>A while back, I
6119 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
6120 about the fact
</a
> that it is not possible with the provided schemas
6121 for storing DNS and DHCP information in LDAP to combine the two sets
6122 of information into one LDAP object representing a computer.
</p
>
6124 <p
>In the mean time, I discovered that a simple fix would be to make
6125 the dhcpHost object class auxiliary, to allow it to be combined with
6126 the dNSDomain object class, and thus forming one object for one
6127 computer when storing both DHCP and DNS information in LDAP.
</p
>
6129 <p
>If I understand this correctly, it is not safe to do this change
6130 without also changing the assigned number for the object class, and I
6131 do not know enough about LDAP schema design to do that properly for
6132 Debian Edu.
</p
>
6134 <p
>Anyway, for future reference, this is how I believe we could change
6136 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
6137 schema
</a
> to solve at least part of the problem with the LDAP schemas
6138 available today from IETF.
</p
>
6141 --- dhcp.schema (revision
65192)
6142 +++ dhcp.schema (working copy)
6144 objectclass (
2.16.840.1.113719.1.203.6.6
6145 NAME
'dhcpHost
'
6146 DESC
'This represents information about a particular client
'
6150 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6151 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
6154 <p
>I very much welcome clues on how to do this properly for Debian
6155 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6156 package, and should thus be free to rewrite it as we see fit.
</p
>
6158 <p
>If you want to help out with implementing this for Debian Edu,
6159 please contact us on debian-edu@lists.debian.org.
</p
>
6164 <title>Calling tasksel like the installer, while still getting useful output
</title>
6165 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
6166 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
6167 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
6168 <description><p
>A few times I have had the need to simulate the way tasksel
6169 installs packages during the normal debian-installer run. Until now,
6170 I have ended up letting tasksel do the work, with the annoying problem
6171 of not getting any feedback at all when something fails (like a
6172 conffile question from dpkg or a download that fails), using code like
6175 <blockquote
><pre
>
6176 export DEBIAN_FRONTEND=noninteractive
6177 tasksel --new-install
6178 </pre
></blockquote
>
6180 This would invoke tasksel, let its automatic task selection pick the
6181 tasks to install, and continue to install the requested tasks without
6182 any output what so ever.
6184 Recently I revisited this problem while working on the automatic
6185 package upgrade testing, because tasksel would some times hang without
6186 any useful feedback, and I want to see what is going on when it
6187 happen. Then it occured to me, I can parse the output from tasksel
6188 when asked to run in test mode, and use that aptitude command line
6189 printed by tasksel then to simulate the tasksel run. I ended up using
6192 <blockquote
><pre
>
6193 export DEBIAN_FRONTEND=noninteractive
6194 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
6196 </pre
></blockquote
>
6198 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
6199 --without-recommends -o APT::Install-Recommends=no -y install
6200 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6201 ~pimportant
</tt
>", which will install the gnome desktop task, the
6202 laptop task and all packages with priority standard , required and
6203 important, just like tasksel would have done it during
6204 installation.
</p
>
6206 <p
>A better approach is probably to extend tasksel to be able to
6207 install packages without using debconf-apt-progress, for use cases
6208 like this.
</p
>
6213 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
6214 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
6215 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
6216 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
6217 <description><p
>My
6218 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
6219 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
6220 finally made the upgrade logs available from
6221 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
6222 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6223 apt and aptitude, and found their differences interesting. This time
6224 I will only focus on their removal plans.
</p
>
6226 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
6227 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
6228 surprising part is that it want to remove xorg and all
6229 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6230 sure why. When asking aptitude to do the same, it want to remove
129
6231 packages, but most of them are library packages I suspect are no
6232 longer needed. Both of them want to remove bluetooth packages, which
6233 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
6235 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
6236 which seem like a bad idea and xorg the same way as with Gnome. Asking
6237 aptitude for the same, it wants to remove
192 packages, none which are
6238 too surprising.
</p
>
6240 <p
>I guess the removal of xorg during upgrades should be investigated
6241 and avoided, and perhaps others as well. Here are the complete list
6242 of planned removals. The complete logs is available from the URL
6243 above. Note if you want to repeat these tests, that the upgrade test
6244 for kde+apt-get hung in the tasksel setup because of dpkg asking
6245 conffile questions. No idea why. I worked around it by using
6246 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
6249 <p
><b
>apt-get gnome
72</b
>
6250 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
6251 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6252 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
6253 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6254 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6255 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6256 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6257 xserver-xorg-input-kbd xserver-xorg-input-mouse
6258 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6259 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6260 xserver-xorg-video-ati xserver-xorg-video-chips
6261 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6262 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6263 xserver-xorg-video-glint xserver-xorg-video-i128
6264 xserver-xorg-video-i740 xserver-xorg-video-imstt
6265 xserver-xorg-video-intel xserver-xorg-video-mach64
6266 xserver-xorg-video-mga xserver-xorg-video-neomagic
6267 xserver-xorg-video-nsc xserver-xorg-video-nv
6268 xserver-xorg-video-openchrome xserver-xorg-video-r128
6269 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6270 xserver-xorg-video-rendition xserver-xorg-video-s3
6271 xserver-xorg-video-s3virge xserver-xorg-video-savage
6272 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6273 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6274 xserver-xorg-video-tga xserver-xorg-video-trident
6275 xserver-xorg-video-tseng xserver-xorg-video-v4l
6276 xserver-xorg-video-vesa xserver-xorg-video-vga
6277 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
6278 xulrunner-
1.9-gnome-support
</p
>
6280 <p
><b
>aptitude gnome
129</b
>
6282 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
6283 djvulibre-desktop finger gnome-app-install gnome-mount
6284 gnome-network-admin gnome-spell gnome-vfs-obexftp
6285 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6286 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6287 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6288 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
6289 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
6290 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
6291 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
6292 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
6293 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
6294 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
6295 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
6296 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
6297 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6298 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
6299 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
6300 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
6301 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
6302 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
6303 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6304 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6305 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6306 openoffice.org-writer2latex openssl-blacklist p7zip
6307 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
6308 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6309 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6310 swfdec-mozilla totem-gstreamer update-manager wodim
6311 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6312 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6315 <p
><b
>apt-get kde
82</b
>
6317 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6318 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6319 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6320 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6321 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6322 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6323 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6324 xserver-xorg-input-kbd xserver-xorg-input-mouse
6325 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6326 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6327 xserver-xorg-video-ati xserver-xorg-video-chips
6328 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6329 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6330 xserver-xorg-video-glint xserver-xorg-video-i128
6331 xserver-xorg-video-i740 xserver-xorg-video-imstt
6332 xserver-xorg-video-intel xserver-xorg-video-mach64
6333 xserver-xorg-video-mga xserver-xorg-video-neomagic
6334 xserver-xorg-video-nsc xserver-xorg-video-nv
6335 xserver-xorg-video-openchrome xserver-xorg-video-r128
6336 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6337 xserver-xorg-video-rendition xserver-xorg-video-s3
6338 xserver-xorg-video-s3virge xserver-xorg-video-savage
6339 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6340 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6341 xserver-xorg-video-tga xserver-xorg-video-trident
6342 xserver-xorg-video-tseng xserver-xorg-video-v4l
6343 xserver-xorg-video-vesa xserver-xorg-video-vga
6344 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
6346 <p
><b
>aptitude kde
192</b
>
6347 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
6348 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6349 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6350 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6351 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6352 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6353 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6354 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6355 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6356 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6357 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6358 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6359 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6360 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6361 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6362 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6363 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6364 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6365 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
6366 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6367 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6368 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
6369 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6370 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6371 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6372 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6373 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6374 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
6375 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
6376 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6377 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6378 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6379 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6380 texlive-common texlive-doc-base texlive-fonts-recommended
6381 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6382 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6383 xulrunner-
1.9</p
>
6389 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
6390 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
6391 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
6392 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
6393 <description><p
>The last few days I have done some upgrade testing in Debian, to
6394 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6395 have been discovered and reported in the process
6396 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
6397 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
6398 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
6399 kdebase-workspace-data), and to get a more regular testing going on, I
6400 am working on a script to automate the test.
</p
>
6402 <p
>The idea is to create a Lenny chroot and use tasksel to install a
6403 Gnome or KDE desktop installation inside the chroot before upgrading
6404 it. To ensure no services are started in the chroot, a policy-rc.d
6405 script is inserted. To make sure tasksel believe it is to install a
6406 desktop on a laptop, the tasksel tests are replaced in the chroot
6407 (only acceptable because this is a throw-away chroot).
</p
>
6409 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6410 currently always fail because udev refuses to upgrade with the kernel
6411 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6412 is created. The bug report
6413 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
6414 this problem do not trigger in a chroot, but I touch the file anyway
6415 to make sure the upgrade go well. Testing on virtual and real
6416 hardware have failed me because of udev so far, and creating this file
6417 do the trick in such settings anyway. This is a
6418 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
6419 issue
</a
> and the current udev behaviour is intended by the udev
6420 maintainer because he lack the resources to rewrite udev to keep
6421 working with old kernels or something like that. I really wish the
6422 udev upstream would keep udev backwards compatible, to avoid such
6423 upgrade problem, but given that they fail to do so, I guess
6424 documenting the way out of this mess is the best option we got for
6425 Debian Squeeze.
</p
>
6427 <p
>Anyway, back to the task at hand, testing upgrades. This test
6428 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
6431 <blockquote
><pre
>
6435 if [
"$
1" ] ; then
6444 exec
&lt; /dev/null
6446 mirror=http://ftp.skolelinux.org/debian
6447 tmpdir=chroot-$from-upgrade-$to-$desktop
6449 debootstrap $from $tmpdir $mirror
6450 chroot $tmpdir aptitude update
6451 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
6455 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6459 mount -t proc proc $tmpdir/proc
6460 # Make sure proc is unmounted also on failure
6461 trap exit_cleanup EXIT INT
6463 chroot $tmpdir aptitude -y install debconf-utils
6465 # Make sure tasksel autoselection trigger. It need the test scripts
6466 # to return the correct answers.
6467 echo tasksel tasksel/desktop multiselect $desktop | \
6468 chroot $tmpdir debconf-set-selections
6470 # Include the desktop and laptop task
6471 for test in desktop laptop ; do
6472 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
6476 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6479 DEBIAN_FRONTEND=noninteractive
6480 DEBIAN_PRIORITY=critical
6481 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6482 chroot $tmpdir tasksel --new-install
6484 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
6485 chroot $tmpdir aptitude update
6486 touch $tmpdir/etc/udev/kernel-upgrade
6487 chroot $tmpdir aptitude -y dist-upgrade
6489 </pre
></blockquote
>
6491 <p
>I suspect it would be useful to test upgrades with both apt-get and
6492 with aptitude, but I have not had time to look at how they behave
6493 differently so far. I hope to get a cron job running to do the test
6494 regularly and post the result on the web. The Gnome upgrade currently
6495 work, while the KDE upgrade fail because of the bug in
6496 kdebase-workspace-data
</p
>
6498 <p
>I am not quite sure what kind of extract from the huge upgrade logs
6499 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
6500 post, so I will refrain from trying. I can report that for Gnome,
6501 aptitude report
760 packages upgraded,
448 newly installed,
129 to
6502 remove and
1 not upgraded and
1024MB need to be downloaded while for
6503 KDE the same numbers are
702 packages upgraded,
507 newly installed,
6504 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
6506 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
6507 is able to migrate to dependency based boot sequencing and parallel
6508 booting without a hitch. Was unsure if there were still bugs with
6509 packages failing to clean up their obsolete init.d script during
6510 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6516 <title>Upstart or sysvinit - as init.d scripts see it
</title>
6517 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
6518 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
6519 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
6520 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
6521 scripts to migrate (some of) their operations to upstart job while
6522 keeping the init.d for hurd and kfreebsd. The packages with such
6523 needs will need a way to get their init.d scripts to behave
6524 differently when used with sysvinit and with upstart. Because of
6525 this, I had a look at the environment variables set when a init.d
6526 script is running under upstart, and when it is not.
</p
>
6528 <p
>With upstart, I notice these environment variables are set when a
6529 script is started from rcS.d/ (ignoring some irrelevant ones like
6532 <blockquote
><pre
>
6538 UPSTART_EVENTS=startup
6540 UPSTART_JOB=rc-sysinit
6541 </pre
></blockquote
>
6543 <p
>With sysvinit, these environment variables are set for the same
6546 <blockquote
><pre
>
6547 INIT_VERSION=sysvinit-
2.88
6552 </pre
></blockquote
>
6554 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
6555 sysvinit are not set by upstart. Not sure if it is intentional or not
6556 to not be compatible with sysvinit in this regard.
</p
>
6558 <p
>For scripts needing to behave differently when upstart is used,
6559 looking for the UPSTART_JOB environment variable seem to be a good
6565 <title>A manual for standards wars...
</title>
6566 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
6567 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
6568 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
6569 <description><p
>Via the
6570 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
6571 of Rob Weir
</a
> I came across the very interesting essay named
6572 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
6573 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
6574 following the standards wars of today.
</p
>
6579 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
6580 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
6581 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
6582 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
6583 <description><p
>When using sitesummary at a site to track machines, it is possible
6584 to get a list of the machine types in use thanks to the DMI
6585 information extracted from each machine. The script to do so is
6586 included in the sitesummary package, and here is example output from
6587 the Skolelinux build servers:
</p
>
6589 <blockquote
><pre
>
6590 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
6592 Dell Computer Corporation
1
6595 eserver xSeries
345 -[
8670M1X]-
1
6599 </pre
></blockquote
>
6601 <p
>The quality of the report depend on the quality of the DMI tables
6602 provided in each machine. Here there are Intel machines without model
6603 information listed with Intel as vendor and no model, and virtual Xen
6604 machines listed as [no-dmi-info]. One can add -l as a command line
6605 option to list the individual machines.
</p
>
6607 <p
>A larger list is
6608 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
6609 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
6610 provide the basic sitesummary report publicly. In their report there
6611 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
6612 their machines, and as sitesummary is available in both distributions,
6613 it is trivial to get all of them to report to the same central
6614 collector.
</p
>
6619 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
6620 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
6621 <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>
6622 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
6623 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
6624 start at boot when an NVidia video card is used is handled. The
6625 problem seem to be that the nvidia X.org driver uses a long time to
6626 initialize, and this duration is longer than kdm is configured to
6629 <p
>I came across two bugs related to this issue,
6630 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
6631 against initscripts and passed on to nvidia-glx when it became obvious
6632 that the nvidia drivers were involved, and
6633 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
6634 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
6636 <p
>To me, it seem that no-one is interested in actually solving the
6637 problem nvidia video card owners experience and make sure the Debian
6638 distribution work out of the box for these users. The nvidia driver
6639 maintainers expect kdm to be set up to wait longer, while kdm expect
6640 the nvidia driver maintainers to fix the driver to start faster, and
6641 while they wait for each other I guess the users end up switching to a
6642 distribution that work for them. I have no idea what the solution is,
6643 but I am pretty sure that waiting for each other is not it.
</p
>
6645 <p
>I wonder why we end up handling bugs this way.
</p
>
6650 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
6651 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
6652 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
6653 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
6654 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
6655 The feature seem to hold up pretty well, but three fairly serious
6656 issues are known and should be solved:
6660 <li
>The wicd package seen to
6661 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
6662 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
6663 parallel booting is enabled. No idea why, but the wicd maintainer
6664 seem to be on the case.
</li
>
6666 <li
>The nvidia X driver seem to
6667 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
6668 triggered more easily when parallel booting is in effect. The
6669 maintainer is on the case.
</li
>
6671 <li
>The sysv-rc package fail to properly enable dependency based boot
6672 sequencing (the shutdown is broken) when old file-rc users
6673 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
6674 sysv-rc. One way to solve it would be for file-rc to create
6675 /etc/init.d/.legacy-bootordering, and another is to try to make
6676 sysv-rc more robust. Will investigate some more and probably upload a
6677 workaround in sysv-rc to help those trying to move from file-rc to
6678 sysv-rc get a working shutdown.
</li
>
6680 </ul
></p
>
6682 <p
>All in all not many surprising issues, and all of them seem
6683 solvable before Squeeze is released. In addition to these there are
6684 some packages with bugs in their dependencies and run level settings,
6685 which I expect will be fixed in a reasonable time span.
</p
>
6687 <p
>If you report any problems with dependencies in init.d scripts to
6688 the BTS, please usertag the report to get it to show up at
6689 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
6690 list of usertagged bugs related to this
</a
>.
</p
>
6692 <p
>Update: Correct bug number to file-rc issue.
</p
>
6697 <title>More flexible firmware handling in debian-installer
</title>
6698 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
6699 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
6700 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
6701 <description><p
>After a long break from debian-installer development, I finally
6702 found time today to return to the project. Having to spend less time
6703 working dependency based boot in debian, as it is almost complete now,
6704 definitely helped freeing some time.
</p
>
6706 <p
>A while back, I ran into a problem while working on Debian Edu. We
6707 include some firmware packages on the Debian Edu CDs, those needed to
6708 get disk and network controllers working. Without having these
6709 firmware packages available during installation, it is impossible to
6710 install Debian Edu on the given machine, and because our target group
6711 are non-technical people, asking them to provide firmware packages on
6712 an external medium is a support pain. Initially, I expected it to be
6713 enough to include the firmware packages on the CD to get
6714 debian-installer to find and use them. This proved to be wrong.
6715 Next, I hoped it was enough to symlink the relevant firmware packages
6716 to some useful location on the CD (tried /cdrom/ and
6717 /cdrom/firmware/). This also proved to not work, and at this point I
6718 found time to look at the debian-installer code to figure out what was
6719 going to work.
</p
>
6721 <p
>The firmware loading code is in the hw-detect package, and a closer
6722 look revealed that it would only look for firmware packages outside
6723 the installation media, so the CD was never checked for firmware
6724 packages. It would only check USB sticks, floppies and other
6725 "external
" media devices. Today I changed it to also look in the
6726 /cdrom/firmware/ directory on the mounted CD or DVD, which should
6727 solve the problem I ran into with Debian edu. I also changed it to
6728 look in /firmware/, to make sure the installer also find firmware
6729 provided in the initrd when booting the installer via PXE, to allow us
6730 to provide the same feature in the PXE setup included in Debian
6733 <p
>To make sure firmware deb packages with a license questions are not
6734 activated without asking if the license is accepted, I extended
6735 hw-detect to look for preinst scripts in the firmware packages, and
6736 run these before activating the firmware during installation. The
6737 license question is asked using debconf in the preinst, so this should
6738 solve the issue for the firmware packages I have looked at so far.
</p
>
6740 <p
>If you want to discuss the details of these features, please
6741 contact us on debian-boot@lists.debian.org.
</p
>
6746 <title>Parallellized boot is now the default in Debian/unstable
</title>
6747 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
6748 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
6749 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
6750 <description><p
>Since this evening, parallel booting is the default in
6751 Debian/unstable for machines using dependency based boot sequencing.
6752 Apparently the testing of concurrent booting has been wider than
6753 expected, if I am to believe the
6754 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
6755 on debian-devel@
</a
>, and I concluded a few days ago to move forward
6756 with the feature this weekend, to give us some time to detect any
6757 remaining problems before Squeeze is frozen. If serious problems are
6758 detected, it is simple to change the default back to sequential boot.
6759 The upload of the new sysvinit package also activate a new upstream
6762 More information about
6763 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
6764 based boot sequencing
</a
> is available from the Debian wiki. It is
6765 currently possible to disable parallel booting when one run into
6766 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
6768 <blockquote
><pre
>
6770 </pre
></blockquote
>
6772 <p
>If you report any problems with dependencies in init.d scripts to
6773 the BTS, please usertag the report to get it to show up at
6774 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
6775 list of usertagged bugs related to this
</a
>.
</p
>
6780 <title>Sitesummary tip: Listing MAC address of all clients
</title>
6781 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
6782 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
6783 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
6784 <description><p
>In the recent Debian Edu versions, the
6785 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
6786 system
</a
> is used to keep track of the machines in the school
6787 network. Each machine will automatically report its status to the
6788 central server after boot and once per night. The network setup is
6789 also reported, and using this information it is possible to get the
6790 MAC address of all network interfaces in the machines. This is useful
6791 to update the DHCP configuration.
</p
>
6793 <p
>To give some idea how to use sitesummary, here is a one-liner to
6794 ist all MAC addresses of all machines reporting to sitesummary. Run
6795 this on the collector host:
</p
>
6797 <blockquote
><pre
>
6798 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
6799 </pre
></blockquote
>
6801 <p
>This will list all MAC addresses assosiated with all machine, one
6802 line per machine and with space between the MAC addresses.
</p
>
6804 <p
>To allow system administrators easier job at adding static DHCP
6805 addresses for hosts, it would be possible to extend this to fetch
6806 machine information from sitesummary and update the DHCP and DNS
6807 tables in LDAP using this information. Such tool is unfortunately not
6808 written yet.
</p
>
6813 <title>systemd, an interesting alternative to upstart
</title>
6814 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
6815 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
6816 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
6817 <description><p
>The last few days a new boot system called
6818 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
6820 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
6822 to the free software world. I have not yet had time to play around
6823 with it, but it seem to be a very interesting alternative to
6824 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
6825 a good alternative for Debian when we are able to switch to an event
6826 based boot system. Tollef is
6827 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
6828 systemd into Debian, and I look forward to seeing how well it work. I
6829 like the fact that systemd handles init.d scripts with dependency
6830 information natively, allowing them to run in parallel where upstart
6831 at the moment do not.
</p
>
6833 <p
>Unfortunately do systemd have the same problem as upstart regarding
6834 platform support. It only work on recent Linux kernels, and also need
6835 some new kernel features enabled to function properly. This means
6836 kFreeBSD and Hurd ports of Debian will need a port or a different boot
6837 system. Not sure how that will be handled if systemd proves to be the
6838 way forward.
</p
>
6840 <p
>In the mean time, based on the
6841 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
6842 on debian-devel@
</a
> regarding parallel booting in Debian, I have
6843 decided to enable full parallel booting as the default in Debian as
6844 soon as possible (probably this weekend or early next week), to see if
6845 there are any remaining serious bugs in the init.d dependencies. A
6846 new version of the sysvinit package implementing this change is
6847 already in experimental. If all go well, Squeeze will be released
6848 with parallel booting enabled by default.
</p
>
6853 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
6854 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
6855 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
6856 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
6857 <description><p
>These days, the init.d script dependencies in Squeeze are quite
6858 complete, so complete that it is actually possible to run all the
6859 init.d scripts in parallell based on these dependencies. If you want
6860 to test your Squeeze system, make sure
6861 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
6862 based boot sequencing
</a
> is enabled, and add this line to
6863 /etc/default/rcS:
</p
>
6865 <blockquote
><pre
>
6866 CONCURRENCY=makefile
6867 </pre
></blockquote
>
6869 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
6870 scripts in parallel using the dependency information stored in
6871 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
6872 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
6873 to try to start the kdm and gdm scripts as early as possible, and will
6874 start the facilities required by kdm or gdm as early as possible to
6875 make this happen.
</p
>
6877 <p
>Give it a try, and see if you like the result. If some services
6878 fail to start properly, it is most likely because they have incomplete
6879 init.d script dependencies in their startup script (or some of their
6880 dependent scripts have incomplete dependencies). Report bugs and get
6881 the package maintainers to fix it. :)
</p
>
6883 <p
>Running scripts in parallel could be the default in Debian when we
6884 manage to get the init.d script dependencies complete and correct. I
6885 expect we will get there in Squeeze+
1, if we get manage to test and
6886 fix the remaining issues.
</p
>
6888 <p
>If you report any problems with dependencies in init.d scripts to
6889 the BTS, please usertag the report to get it to show up at
6890 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
6891 list of usertagged bugs related to this
</a
>.
</p
>
6896 <title>Debian has switched to dependency based boot sequencing
</title>
6897 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
6898 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
6899 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
6900 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
6901 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
6902 have been migrated to using dependency based boot sequencing. This
6903 conclude work me and others have been doing for the last three days.
6904 It feels great to see this finally part of the default Debian
6905 installation. Now we just need to weed out the last few problems that
6906 are bound to show up, to get everything ready for Squeeze.
</p
>
6908 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
6909 fixing the more fundamental problem of handing the event based
6910 non-predictable kernel in the early boot.
</p
>
6915 <title>Taking over sysvinit development
</title>
6916 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
6917 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
6918 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
6919 <description><p
>After several years of frustration with the lack of activity from
6920 the existing sysvinit upstream developer, I decided a few weeks ago to
6921 take over the package and become the new upstream. The number of
6922 patches to track for the Debian package was becoming a burden, and the
6923 lack of synchronization between the distribution made it hard to keep
6924 the package up to date.
</p
>
6926 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
6927 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
6928 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
6929 and Fedora), based on the patches currently in use in these
6930 distributions. We Debian maintainers plan to move to this tarball as
6931 the new upstream as soon as we find time to do the merge. Since the
6932 new tarball was created, we agreed with Werner at SuSe to make a new
6933 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
6934 development there. The project is registered and currently waiting
6935 for approval by the Savannah administrators, and as soon as it is
6936 approved, we will import the old versions from svn and continue
6937 working on the future release.
</p
>
6939 <p
>It is a bit ironic that this is done now, when some of the involved
6940 distributions are moving to upstart as a syvinit replacement.
</p
>
6945 <title>Debian boots quicker and quicker
</title>
6946 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
6947 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
6948 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
6949 <description><p
>I spent Monday and tuesday this week in London with a lot of the
6950 people involved in the boot system on Debian and Ubuntu, to see if we
6951 could find more ways to speed up the boot system. This was an Ubuntu
6953 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
6954 gathering
</a
>. It was quite productive. We also discussed the future
6955 of boot systems, and ways to handle the increasing number of boot
6956 issues introduced by the Linux kernel becoming more and more
6957 asynchronous and event base. The Ubuntu approach using udev and
6958 upstart might be a good way forward. Time will show.
</p
>
6960 <p
>Anyway, there are a few ways at the moment to speed up the boot
6961 process in Debian. All of these should be applied to get a quick
6966 <li
>Use dash as /bin/sh.
</li
>
6968 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
6969 clock is in UTC.
</li
>
6971 <li
>Install and activate the insserv package to enable
6972 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
6973 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
6977 These points are based on the Google summer of code work done by
6978 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
6981 <p
>Support for makefile-style concurrency during boot was uploaded to
6982 unstable yesterday. When we tested it, we were able to cut
6 seconds
6983 from the boot sequence. It depend on very correct dependency
6984 declaration in all init.d scripts, so I expect us to find edge cases
6985 where the dependences in some scripts are slightly wrong when we start
6986 using this.
</p
>
6988 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
6989 introduced by Raphael Geissert today, one that could affect the
6990 startup speed as well. Instead of starting some scripts concurrently
6991 from rcS.d/ and another set of scripts from rc2.d/, it would be
6992 possible to run a of them in the same process. A quick way to test
6993 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
6994 insserv
'. Will need to test if that work. :)
</p
>
6999 <title>BSAs påstander om piratkopiering møter motstand
</title>
7000 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
7001 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
7002 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
7003 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
7004 programvareselskapene som Microsoft og Apple, publisert en rapport der
7005 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7006 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7008 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
7009 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
7010 dagene. Et spesielt interessant kommentar fra Sverige,
7011 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
7012 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
7015 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
7016 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7017 företag.
"Man bör nog kanske inte se de här siffrorna som helt
7018 exakta
", säger BSAs Sverigechef John Hugosson.
7021 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
7022 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
7023 piracy figures need a shot of reality
</a
> og
<a
7024 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
7025 Copyright Treaty Work?
</a
></p
>
7027 <p
>Fant lenkene via
<a
7028 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
7029 på Slashdot
</a
>.
</p
>
7034 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
7035 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
7036 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
7037 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
7038 <description><p
>Kom over
7039 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
7040 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7041 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7042 jobber til daglig. En rask opptelling forteller meg at vi har
490
7043 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
7044 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
7045 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
7050 <title>Kryptert harddisk - naturligvis
</title>
7051 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
7052 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
7053 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
7054 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
7055 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
7056 når en tar tap av arbeidstid, fortrolige dokumenter,
7057 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7058 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7059 til at jeg har kryptert harddisken på både kontormaskinen og min
7060 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7061 komme på avveie, den første informasjon relatert til jobben min ved
7062 Universitetet i Oslo, og den andre relatert til blant annet
7063 foreningsarbeide. Kryptering av diskene gjør at det er lite
7064 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7065 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7066 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7067 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7068 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7069 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7070 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7071 det er gjort slik jeg gjør det er minimale, og gevinstene er
7072 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7073 maskinen reinstalleres og alt er tapt.
</p
>
7075 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7076 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7077 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7078 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7079 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7080 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7081 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7082 betydelige.
</p
>
7087 <title>Two projects that have improved the quality of free software a lot
</title>
7088 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
7089 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
7090 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
7091 <description><p
>There are two software projects that have had huge influence on the
7092 quality of free software, and I wanted to mention both in case someone
7093 do not yet know them.
</p
>
7095 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
7096 tool to detect and expose errors in the memory handling of programs.
7097 It is easy to use, all one need to do is to run
'valgrind program
',
7098 and it will report any problems on stdout. It is even better if the
7099 program include debug information. With debug information, it is able
7100 to report the source file name and line number where the problem
7101 occurs. It can report things like
'reading past memory block in file
7102 X line N, the memory block was allocated in file Y, line M
', and
7103 'using uninitialised value in control logic
'. This tool has made it
7104 trivial to investigate reproducible crash bugs in programs, and have
7105 reduced the number of this kind of bugs in free software a lot.
7107 <p
>The second one is
7108 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
7109 a source code checker. It is able to process the source of a program
7110 and find problems in the logic without running the program. It
7111 started out as the Stanford Checker and became well known when it was
7112 used to find bugs in the Linux kernel. It is now a commercial tool
7113 and the company behind it is running
7114 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
7115 free software community, where a lot of free software projects get
7116 their source checked for free. Several thousand defects have been
7117 found and fixed so far. It can find errors like
'lock L taken in file
7118 X line N is never released if exiting in line M
', or
'the code in file
7119 Y lines O to P can never be executed
'. The projects included in the
7120 community service project have managed to get rid of a lot of
7121 reliability problems thanks to Coverity.
</p
>
7123 <p
>I believe tools like this, that are able to automatically find
7124 errors in the source, are vital to improve the quality of software and
7125 make sure we can get rid of the crashing and failing software we are
7126 surrounded by today.
</p
>
7131 <title>No patch is not better than a useless patch
</title>
7132 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
7133 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
7134 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
7135 <description><p
>Julien Blache
7136 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
7137 patch is better than a useless patch
</a
>. I completely disagree, as a
7138 patch allow one to discuss a concrete and proposed solution, and also
7139 prove that the issue at hand is important enough for someone to spent
7140 time on fixing it. No patch do not provide any of these positive
7141 properties.
</p
>
7146 <title>Standardize on protocols and formats, not vendors and applications
</title>
7147 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
7148 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
7149 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
7150 <description><p
>Where I work at the University of Oslo, one decision stand out as a
7151 very good one to form a long lived computer infrastructure. It is the
7152 simple one, lost by many in todays computer industry: Standardize on
7153 open network protocols and open exchange/storage formats, not applications.
7154 Applications come and go, while protocols and files tend to stay, and
7155 thus one want to make it easy to change application and vendor, while
7156 avoiding conversion costs and locking users to a specific platform or
7157 application.
</p
>
7159 <p
>This approach make it possible to replace the client applications
7160 independently of the server applications. One can even allow users to
7161 use several different applications as long as they handle the selected
7162 protocol and format. In the normal case, only one client application
7163 is recommended and users only get help if they choose to use this
7164 application, but those that want to deviate from the easy path are not
7165 blocked from doing so.
</p
>
7167 <p
>It also allow us to replace the server side without forcing the
7168 users to replace their applications, and thus allow us to select the
7169 best server implementation at any moment, when scale and resouce
7170 requirements change.
</p
>
7172 <p
>I strongly recommend standardizing - on open network protocols and
7173 open formats, but I would never recommend standardizing on a single
7174 application that do not use open network protocol or open formats.
</p
>
7179 <title>Returning from Skolelinux developer gathering
</title>
7180 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
7181 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
7182 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
7183 <description><p
>I
'm sitting on the train going home from this weekends Debian
7184 Edu/Skolelinux development gathering. I got a bit done tuning the
7185 desktop, and looked into the dynamic service location protocol
7186 implementation avahi. It look like it could be useful for us. Almost
7187 30 people participated, and I believe it was a great environment to
7188 get to know the Skolelinux system. Walter Bender, involved in the
7189 development of the Sugar educational platform, presented his stuff and
7190 also helped me improve my OLPC installation. He also showed me that
7191 his Turtle Art application can be used in standalone mode, and we
7192 agreed that I would help getting it packaged for Debian. As a
7193 standalone application it would be great for Debian Edu. We also
7194 tried to get the video conferencing working with two OLPCs, but that
7195 proved to be too hard for us. The application seem to need more work
7196 before it is ready for me. I look forward to getting home and relax
7202 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
7203 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
7204 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
7205 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
7206 <description><p
>The state of standardized LDAP schemas on Linux is far from
7207 optimal. There is RFC
2307 documenting one way to store NIS maps in
7208 LDAP, and a modified version of this normally called RFC
2307bis, with
7209 some modifications to be compatible with Active Directory. The RFC
7210 specification handle the content of a lot of system databases, but do
7211 not handle DNS zones and DHCP configuration.
</p
>
7213 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
7214 we would like to store information about users, SMB clients/hosts,
7215 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7216 and LTSP configuration in LDAP. These objects have a lot in common,
7217 but with the current LDAP schemas it is not possible to have one
7218 object per entity. For example, one need to have at least three LDAP
7219 objects for a given computer, one with the SMB related stuff, one with
7220 DNS information and another with DHCP information. The schemas
7221 provided for DNS and DHCP are impossible to combine into one LDAP
7222 object. In addition, it is impossible to implement quick queries for
7223 netgroup membership, because of the way NIS triples are implemented.
7224 It just do not scale. I believe it is time for a few RFC
7225 specifications to cleam up this mess.
</p
>
7227 <p
>I would like to have one LDAP object representing each computer in
7228 the network, and this object can then keep the SMB (ie host key), DHCP
7229 (mac address/name) and DNS (name/IP address) settings in one place.
7230 It need to be efficently stored to make sure it scale well.
</p
>
7232 <p
>I would also like to have a quick way to map from a user or
7233 computer and to the net group this user or computer is a member.
</p
>
7235 <p
>Active Directory have done a better job than unix heads like myself
7236 in this regard, and the unix side need to catch up. Time to start a
7237 new IETF work group?
</p
>
7242 <title>Endelig er Debian Lenny gitt ut
</title>
7243 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
7244 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
7245 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
7246 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
7247 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
7248 Et langt steg videre for Debian-prosjektet, og en rekke nye
7249 programpakker blir nå tilgjengelig for de av oss som bruker den
7250 stabile utgaven av Debian. Neste steg er nå å få
7251 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
7252 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
7253 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7254 slippes løs på skolene. Takk til alle debian-utviklerne som har
7255 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7256 bootsekvens tilgjengelig i stabil utgave, vha pakken
7257 <tt
>insserv
</tt
>.
</p
>
7262 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
7263 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
7264 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
7265 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
7266 <description><p
>This weekend we had a small developer gathering for Debian Edu in
7267 Oslo. Most of Saturday was used for the general assemly for the
7268 member organization, but the rest of the weekend I used to tune the
7269 LTSP installation. LTSP now work out of the box on the
10-network.
7270 Acer Aspire One proved to be a very nice thin client, with both
7271 screen, mouse and keybard in a small box. Was working on getting the
7272 diskless workstation setup configured out of the box, but did not
7273 finish it before the weekend was up.
</p
>
7275 <p
>Did not find time to look at the
4 VGA cards in one box we got from
7276 the Brazilian group, so that will have to wait for the next
7277 development gathering. Would love to have the Debian Edu installer
7278 automatically detect and configure a multiseat setup when it find one
7279 of these cards.
</p
>
7284 <title>The sorry state of multimedia browser plugins in Debian
</title>
7285 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
7286 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
7287 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
7288 <description><p
>Recently I have spent some time evaluating the multimedia browser
7289 plugins available in Debian Lenny, to see which one we should use by
7290 default in Debian Edu. We need an embedded video playing plugin with
7291 control buttons to pause or stop the video, and capable of streaming
7292 all the multimedia content available on the web. The test results and
7293 notes are available on
7294 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
7295 Debian wiki
</a
>. I was surprised how few of the plugins are able to
7296 fill this need. My personal video player favorite, VLC, has a really
7297 bad plugin which fail on a lot of the test pages. A lot of the MIME
7298 types I would expect to work with any free software player (like
7299 video/ogg), just do not work. And simple formats like the
7300 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
7301 totem and vlc plugins. I hope the situation will improve soon. No
7302 wonder sites use the proprietary Adobe flash to play video.
</p
>
7304 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
7305 be the only one fitting our needs. :/
</p
>