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>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
11 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
13 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
14 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
15 project
</a
> provide a Linux solution for schools, including a
16 powerful desktop with education software, a central server providing
17 web pages, user database, user home directories, central login and PXE
18 boot of both clients without disk and the installation to install Debian
19 Edu on machines with disk (and a few other services perhaps to small
20 to mention here). We in the Debian Edu team are currently working on
21 the Jessie based version, trying to get everything in shape before the
22 freeze, to avoid having to maintain our own package repository in the
24 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
25 status
</a
> can be seen on the Debian wiki, and there is still heaps of
26 work left. Some fatal problems block testing, breaking the installer,
27 but it is possible to work around these to get anyway. Here is a
28 recipe on how to get the installation limping along.
</p
>
30 <p
>First, download the test ISO via
31 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
32 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
34 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
35 The ISO build was broken on Tuesday, so we do not get a new ISO every
36 12 hours or so, but thankfully the ISO we got is able to install with
37 some tweaking.
</p
>
39 <p
>When you get to the Debian Edu profile question, go to tty2
40 (use Alt-Ctrl-F2), run
</p
>
42 <p
><blockquote
><pre
>
43 nano /usr/bin/edu-eatmydata-install
44 </pre
></blockquote
></p
>
46 <p
>and add
'exit
0' as the second line, disabling the eatmydata
47 optimization. Return to the installation, select the profile you want
48 and continue. Without this change, exim4-config will fail to install
49 due to a known bug in eatmydata.
</p
>
51 <p
>When you get the grub question at the end, answer /dev/sda (or if
52 this do not work, figure out what your correct value would be. All my
53 test machines need /dev/sda, so I have no advice if it do not fit
56 <p
>If you installed a profile including a graphical desktop, log in as
57 root after the initial boot from hard drive, and install the
58 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
59 or mate. If you want several desktop options, install more than one
60 metapackage. Once this is done, reboot and you should have a working
61 graphical login screen. This should no longer be needed once the
62 education-tasks package version
1.801 enter testing in two days.
</p
>
64 <p
>I believe the ISO build will start working on two days when the new
65 tasksel package enter testing and Steve McIntyre get a chance to
66 update the debian-cd git repository. The eatmydata, grub and desktop
67 issues are already fixed in unstable and testing, and should show up
68 on the ISO as soon as the ISO build start working again. Well the
69 eatmydata optimization is really just disabled. The proper fix
70 require an upload by the eatmydata maintainer applying the patch
71 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
72 The rest have proper fixes in unstable.
</p
>
74 <p
>I hope this get you going with the installation testing, as we are
75 quickly running out of time trying to get our Jessie based
76 installation ready before the distribution freeze in a month.
</p
>
81 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
82 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
83 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
84 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
85 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
86 to handle my fairly large DVD collection. It is a nice command line
87 tool to get details about a DVD, like title, tracks, track length,
88 etc, in XML, Perl or human readable format. But lsdvd have not seen
89 any new development since
2006 and had a few irritating bugs affecting
90 its use with some DVDs. Upstream seemed to be dead, and in January I
91 sent a small probe asking for a version control repository for the
92 project, without any reply. But I use it regularly and would like to
93 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
94 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
95 the project admin, and after getting a reply from him explaining that
96 he was no longer interested in the project, I asked if I could take
97 over. And yesterday, I became project admin.
</p
>
99 <p
>I
've been in touch with a Gentoo developer and the Debian
100 maintainer interested in joining forces to maintain the upstream
101 project, and I hope we can get a new release out fairly quickly,
102 collecting the patches spread around on the internet into on place.
103 I
've added the relevant Debian patches to the freshly created git
104 repository, and expect the Gentoo patches to make it too. If you got
105 a DVD collection and care about command line tools, check out
106 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
107 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
108 list
</a
>. :)
</p
>
113 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
114 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
115 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
116 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
117 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
118 a lot quicker. When we install more than
2000 packages in
119 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
120 tasksel in the installer, unpacking the binary packages take forever.
121 A part of the slow I/O issue was discussed in
122 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
123 much file system sync-ing done by dpkg, which is the package
124 responsible for unpacking the binary packages. Other parts (like code
125 executed by postinst scripts) might also sync to disk during
126 installation. All this sync-ing to disk do not really make sense to
127 me. If the machine crash half-way through, I start over, I do not try
128 to salvage the half installed system. So the failure sync-ing is
129 supposed to protect against, hardware or system crash, is not really
130 relevant while the installer is running.
</p
>
132 <p
>A few days ago, I thought of a way to get rid of all the file
133 system sync()-ing in a fairly non-intrusive way, without the need to
134 change the code in several packages. The idea is not new, but I have
135 not heard anyone propose the approach using dpkg-divert before. It
136 depend on the small and clever package
137 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
138 uses LD_PRELOAD to replace the system functions for syncing data to
139 disk with functions doing nothing, thus allowing programs to live
140 dangerous while speeding up disk I/O significantly. Instead of
141 modifying the implementation of dpkg, apt and tasksel (which are the
142 packages responsible for selecting, fetching and installing packages),
143 it occurred to me that we could just divert the programs away, replace
144 them with a simple shell wrapper calling
145 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
146 Two days ago I decided to test the idea, and wrapped up a simple
147 implementation for the Debian Edu udeb.
</p
>
149 <p
>The effect was stunning. In my first test it reduced the running
150 time of the pkgsel step (installing tasks) from
64 to less than
44
151 minutes (
20 minutes shaved off the installation) on an old Dell
152 Latitude D505 machine. I am not quite sure what the optimised time
153 would have been, as I messed up the testing a bit, causing the debconf
154 priority to get low enough for two questions to pop up during
155 installation. As soon as I saw the questions I moved the installation
156 along, but do not know how long the question were holding up the
157 installation. I did some more measurements using Debian Edu Jessie,
158 and got these results. The time measured is the time stamp in
159 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
160 "pkgsel: finishing up
" lines, if you want to do the same measurement
161 yourself. In Debian Edu, the tasksel dialog do not show up, and the
162 timing thus do not depend on how quickly the user handle the tasksel
165 <p
><table
>
168 <th
>Machine/setup
</th
>
169 <th
>Original tasksel
</th
>
170 <th
>Optimised tasksel
</th
>
171 <th
>Reduction
</th
>
175 <td
>Latitude D505 Main+LTSP LXDE
</td
>
176 <td
>64 min (
07:
46-
08:
50)
</td
>
177 <td
><44 min (
11:
27-
12:
11)
</td
>
178 <td
>>20 min
18%
</td
>
182 <td
>Latitude D505 Roaming LXDE
</td
>
183 <td
>57 min (
08:
48-
09:
45)
</td
>
184 <td
>34 min (
07:
43-
08:
17)
</td
>
185 <td
>23 min
40%
</td
>
189 <td
>Latitude D505 Minimal
</td
>
190 <td
>22 min (
10:
37-
10:
59)
</td
>
191 <td
>11 min (
11:
16-
11:
27)
</td
>
192 <td
>11 min
50%
</td
>
196 <td
>Thinkpad X200 Minimal
</td
>
197 <td
>6 min (
08:
19-
08:
25)
</td
>
198 <td
>4 min (
08:
04-
08:
08)
</td
>
199 <td
>2 min
33%
</td
>
203 <td
>Thinkpad X200 Roaming KDE
</td
>
204 <td
>19 min (
09:
21-
09:
40)
</td
>
205 <td
>15 min (
10:
25-
10:
40)
</td
>
206 <td
>4 min
21%
</td
>
209 </table
></p
>
211 <p
>The test is done using a netinst ISO on a USB stick, so some of the
212 time is spent downloading packages. The connection to the Internet
213 was
100Mbit/s during testing, so downloading should not be a
214 significant factor in the measurement. Download typically took a few
215 seconds to a few minutes, depending on the amount of packages being
218 <p
>The speedup is implemented by using two hooks in
219 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
220 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
221 finish-install.d hook to remove the divert at the end of the
222 installation. I picked the pre-pkgsel.d hook instead of the
223 post-base-installer.d hook because I test using an ISO without the
224 eatmydata package included, and the post-base-installer.d hook in
225 Debian Edu can only operate on packages included in the ISO. The
226 negative effect of this is that I am unable to activate this
227 optimization for the kernel installation step in d-i. If the code is
228 moved to the post-base-installer.d hook, the speedup would be larger
229 for the entire installation.
</p
>
231 <p
>I
've implemented this in the
232 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
233 git repository, and plan to provide the optimization as part of the
234 Debian Edu installation. If you want to test this yourself, you can
235 create two files in the installer (or in an udeb). One shell script
236 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
238 <p
><blockquote
><pre
>
241 . /usr/share/debconf/confmodule
243 logger -t my-pkgsel
"info: $*
"
246 logger -t my-pkgsel
"error: $*
"
249 apt-install eatmydata || true
250 if [ -x /target/usr/bin/eatmydata ] ; then
251 for bin in dpkg apt-get aptitude tasksel ; do
253 # Test that the file exist and have not been diverted already.
254 if [ -f /target$file ] ; then
255 info
"diverting $file using eatmydata
"
256 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
257 > /target$file.edu
258 chmod
755 /target$file.edu
259 in-target dpkg-divert --package debian-edu-config \
260 --rename --quiet --add $file
261 ln -sf ./$bin.edu /target$file
263 error
"unable to divert $file, as it is missing.
"
267 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
272 </pre
></blockquote
></p
>
274 <p
>To clean up, another shell script should go into
275 /usr/lib/finish-install.d/ with code like this:
277 <p
><blockquote
><pre
>
279 . /usr/share/debconf/confmodule
281 logger -t my-finish-install
"error: $@
"
283 remove_install_override() {
284 for bin in dpkg apt-get aptitude tasksel ; do
286 if [ -x /target$file.edu ] ; then
288 in-target dpkg-divert --package debian-edu-config \
289 --rename --quiet --remove $file
292 error
"Missing divert for $file.
"
295 sync # Flush file buffers before continuing
298 remove_install_override
299 </pre
></blockquote
></p
>
301 <p
>In Debian Edu, I placed both code fragments in a separate script
302 edu-eatmydata-install and call it from the pre-pkgsel.d and
303 finish-install.d scripts.
</p
>
305 <p
>By now you might ask if this change should get into the normal
306 Debian installer too? I suspect it should, but am not sure the
307 current debian-installer coordinators find it useful enough. It also
308 depend on the side effects of the change. I
'm not aware of any, but I
309 guess we will see if the change is safe after some more testing.
310 Perhaps there is some package in Debian depending on sync() and
311 fsync() having effect? Perhaps it should go into its own udeb, to
312 allow those of us wanting to enable it to do so without affecting
315 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
316 will break installation of all programs using gnutls because of
317 <a href=
"https://bugs.debian.org/
702711">bug #
702711. An updated
318 eatmydata package in Debian will solve it.
</p
>
323 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
324 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
325 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
326 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
327 <description><p
>Yesterday, I had the pleasure of attending a talk with the
328 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
329 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
330 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
331 learn that there is a large set of publicly available key servers to
332 use when looking for peoples public key. So far I have used
333 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
334 were misbehaving, but those days are ended. The servers I have used
335 up until yesterday have been slow and some times unavailable. I hope
336 those problems are gone now.
</p
>
338 <p
>Behind the round robin DNS entry of the
339 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
340 there is a pool of more than
100 keyservers which are checked every
341 day to ensure they are well connected and up to date. It must be
342 better than what I have used so far. :)
</p
>
344 <p
>Yesterdays speaker told me that the service is the default
345 keyserver provided by the default configuration in GnuPG, but this do
346 not seem to be used in Debian. Perhaps it should?
</p
>
348 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
351 <p
><blockquote
><pre
>
352 keyserver pool.sks-keyservers.net
353 </pre
></blockquote
></p
>
355 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
356 entries in DNS. Just for fun, I did just that at work, so now every
357 user of GnuPG at the University of Oslo should find a OpenGPG
358 keyserver automatically should their need it:
</p
>
360 <p
><blockquote
><pre
>
361 % host -t srv _pgpkey-http._tcp.uio.no
362 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
364 </pre
></blockquote
></p
>
367 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
368 HKP lookup protocol
</a
> supported finding signature paths, I would be
369 very happy. It can look up a given key or search for a user ID, but I
370 normally do not want that, but to find a trust path from my key to
371 another key. Given a user ID or key ID, I would like to find (and
372 download) the keys representing a signature path from my key to the
373 key in question, to be able to get a trust path between the two keys.
374 This is as far as I can tell not possible today. Perhaps something
375 for a future version of the protocol?
</p
>
380 <title>From English wiki to translated PDF and epub via Docbook
</title>
381 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
382 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
383 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
384 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
385 project
</a
> provide an instruction manual for teachers, system
386 administrators and other users that contain useful tips for setting up
387 and maintaining a Debian Edu installation. This text is about how the
388 text processing of this manual is handled in the project.
</p
>
390 <p
>One goal of the project is to provide information in the native
391 language of its users, and for this we need to handle translations.
392 But we also want to make sure each language contain the same
393 information, so for this we need a good way to keep the translations
394 in sync. And we want it to be easy for our users to improve the
395 documentation, avoiding the need to learn special formats or tools to
396 contribute, and the obvious way to do this is to make it possible to
397 edit the documentation using a web browser. We also want it to be
398 easy for translators to keep the translation up to date, and give them
399 help in figuring out what need to be translated. Here is the list of
400 tools and the process we have found trying to reach all these
403 <p
>We maintain the authoritative source of our manual in the
404 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
405 wiki
</a
>, as several wiki pages written in English. It consist of one
406 front page with references to the different chapters, several pages
407 for each chapter, and finally one
"collection page
" gluing all the
408 chapters together into one large web page (aka
409 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
410 AllInOne page
</a
>). The AllInOne page is the one used for further
411 processing and translations. Thanks to the fact that the
412 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
413 wiki.debian.org support exporting pages in
414 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
415 the list of pages to export using the raw version of the AllInOne
416 page, loop over each of them to generate a Docbook XML version of the
417 manual. This process also download images and transform image
418 references to use the locally downloaded images. The generated
419 Docbook XML files are slightly broken, so some post-processing is done
420 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
421 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
422 a handfull of images. The XML file can now be used to generate PDF, HTML
423 and epub versions of the English manual. This is the basic step of
424 our process, making PDF (using dblatex), HTML (using xsltproc) and
425 epub (using dbtoepub) version from Docbook XML, and the resulting files
426 are placed in the debian-edu-doc-en binary package.
</p
>
428 <p
>But English documentation is not enough for us. We want translated
429 documentation too, and we want to make it easy for translators to
430 track the English original. For this we use the
431 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
432 which allow us to transform the English Docbook XML file into a
433 translation file (a .pot file), usable with the normal gettext based
434 translation tools used by those translating free software. The pot
435 file is used to create and maintain translation files (several .po
436 files), which the translations update with the native language
437 translations of all titles, paragraphs and blocks of text in the
438 original. The next step is combining the original English Docbook XML
439 and the translation file (say debian-edu-wheezy-manual.nb.po), to
440 create a translated Docbook XML file (in this case
441 debian-edu-wheezy-manual.nb.xml). This translated (or partly
442 translated, if the translation is not complete) Docbook XML file can
443 then be used like the original to create a PDF, HTML and epub version
444 of the documentation.
</p
>
446 <p
>The translators use different tools to edit the .po files. We
448 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
449 while some use emacs and vi, others can use web based editors like
450 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
451 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
452 is where the .po file end up, in our git repository. Updated
453 translations can either be committed directly to git, or submitted as
454 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
455 against the debian-edu-doc package
</a
>.
</p
>
457 <p
>One challenge is images, which both might need to be translated (if
458 they show translated user applications), and are needed in different
459 formats when creating PDF and HTML versions (epub is a HTML version in
460 this regard). For this we transform the original PNG images to the
461 needed density and format during build, and have a way to provide
462 translated images by storing translated versions in
463 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
464 package maintainers know more.
</p
>
466 <p
>If you wonder what the result look like, we provide
467 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
468 of the documentation packages on the web
</a
>. See for example the
469 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
470 PDF version
</a
> or the
471 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
472 HTML version
</a
>. We do not yet build the epub version by default,
473 but perhaps it will be done in the future.
</p
>
475 <p
>To learn more, check out
476 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
477 debian-edu-doc package
</a
>,
478 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
479 manual on the wiki
</a
> and
480 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
481 translation instructions
</a
> in the manual.
</p
>
486 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
487 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
488 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
489 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
490 <description><p
>It would be nice if it was easier in Debian to get all the hardware
491 related packages relevant for the computer installed automatically.
492 So I implemented one, using
493 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
494 package
</a
>. To use it, install the tasksel and isenkram packages and
495 run tasksel as user root. You should be presented with a new option,
496 "Hardware specific packages (autodetected by isenkram)
". When you
497 select it, tasksel will install the packages isenkram claim is fit for
498 the current hardware, hot pluggable or not.
<p
>
500 <p
>The implementation is in two files, one is the tasksel menu entry
501 description, and the other is the script used to extract the list of
502 packages to install. The first part is in
503 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
506 <p
><blockquote
><pre
>
509 Description: Hardware specific packages (autodetected by isenkram)
510 Based on the detected hardware various hardware specific packages are
512 Test-new-install: mark show
514 Packages: for-current-hardware
515 </pre
></blockquote
></p
>
517 <p
>The second part is in
518 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
521 <p
><blockquote
><pre
>
526 isenkram-autoinstall-firmware -l
528 </pre
></blockquote
></p
>
530 <p
>All in all, a very short and simple implementation making it
531 trivial to install the hardware dependent package we all may want to
532 have installed on our machines. I
've not been able to find a way to
533 get tasksel to tell you exactly which packages it plan to install
534 before doing the installation. So if you are curious or careful,
535 check the output from the isenkram-* command line tools first.
</p
>
537 <p
>The information about which packages are handling which hardware is
538 fetched either from the isenkram package itself in
539 /usr/share/isenkram/, from git.debian.org or from the APT package
540 database (using the Modaliases header). The APT package database
541 parsing have caused a nasty resource leak in the isenkram daemon (bugs
542 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
543 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
544 the python-apt code (bug
545 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
546 workaround I was able to get rid of the file descriptor leak and
547 reduce the memory leak from ~
30 MiB per hardware detection down to
548 around
2 MiB per hardware detection. It should make the desktop
549 daemon a lot more useful. The fix is in version
0.7 uploaded to
550 unstable today.
</p
>
552 <p
>I believe the current way of mapping hardware to packages in
553 Isenkram is is a good draft, but in the future I expect isenkram to
554 use the AppStream data source for this. A proposal for getting proper
555 AppStream support into Debian is floating around as
556 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
557 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
558 project
</a
> will take place this summer to improve the situation. I
559 look forward to seeing the result, and welcome patches for isenkram to
560 start using the information when it is ready.
</p
>
562 <p
>If you want your package to map to some specific hardware, either
563 add a
"Xb-Modaliases
" header to your control file like I did in
564 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
565 package
</a
> or submit a bug report with the details to the isenkram
567 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
568 blog posts tagged isenkram
</a
> for details on the notation. I expect
569 the information will be migrated to AppStream eventually, but for the
570 moment I got no better place to store it.
</p
>
575 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
576 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
577 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
578 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
579 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
580 project
</a
> is working on providing the software and hardware to make
581 it easy for non-technical people to host their data and communication
582 at home, and being able to communicate with their friends and family
583 encrypted and away from prying eyes. It is still going strong, and
584 today a major mile stone was reached.
</p
>
586 <p
>Today, the last of the packages currently used by the project to
587 created the system images were accepted into Debian Unstable. It was
588 the freedombox-setup package, which is used to configure the images
589 during build and on the first boot. Now all one need to get going is
590 the build code from the freedom-maker git repository and packages from
591 Debian. And once the freedombox-setup package enter testing, we can
592 build everything directly from Debian. :)
</p
>
594 <p
>Some key packages used by Freedombox are
595 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
596 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
597 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
598 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
599 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
600 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
601 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
602 are plans to integrate more packages into the setup. User
603 documentation is maintained on the Debian wiki. Please
604 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
605 the manual
</a
> and help us improve it.
</p
>
607 <p
>To test for yourself and create boot images with the FreedomBox
608 setup, run this on a Debian machine using a user with sudo rights to
609 become root:
</p
>
612 sudo apt-get install git vmdebootstrap mercurial python-docutils \
613 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
615 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
617 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
618 </pre
></p
>
620 <p
>Root access is needed to run debootstrap and mount loopback
621 devices. See the README in the freedom-maker git repo for more
622 details on the build. If you do not want all three images, trim the
623 make line. Note that the virtualbox-image target is not really
624 virtualbox specific. It create a x86 image usable in kvm, qemu,
625 vmware and any other x86 virtual machine environment. You might need
626 the version of vmdebootstrap in Jessie to get the build working, as it
627 include fixes for a race condition with kpartx.
</p
>
629 <p
>If you instead want to install using a Debian CD and the preseed
630 method, boot a Debian Wheezy ISO and use this boot argument to load
631 the preseed values:
</p
>
634 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
635 </pre
></p
>
637 <p
>I have not tested it myself the last few weeks, so I do not know if
638 it still work.
</p
>
640 <p
>If you wonder how to help, one task you could look at is using
641 systemd as the boot system. It will become the default for Linux in
642 Jessie, so we need to make sure it is usable on the Freedombox. I did
643 a simple test a few weeks ago, and noticed dnsmasq failed to start
644 during boot when using systemd. I suspect there are other problems
645 too. :) To detect problems, there is a test suite included, which can
646 be run from the plinth web interface.
</p
>
648 <p
>Give it a go and let us know how it goes on the mailing list, and help
649 us get the new release published. :) Please join us on
650 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
651 irc.debian.org)
</a
> and
652 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
653 mailing list
</a
> if you want to help make this vision come true.
</p
>
658 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
659 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
660 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
661 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
662 <description><p
>For a while now, I have been looking for a sensible offsite backup
663 solution for use at home. My requirements are simple, it must be
664 cheap and locally encrypted (in other words, I keep the encryption
665 keys, the storage provider do not have access to my private files).
666 One idea me and my friends had many years ago, before the cloud
667 storage providers showed up, was to use Google mail as storage,
668 writing a Linux block device storing blocks as emails in the mail
669 service provided by Google, and thus get heaps of free space. On top
670 of this one can add encryption, RAID and volume management to have
671 lots of (fairly slow, I admit that) cheap and encrypted storage. But
672 I never found time to implement such system. But the last few weeks I
673 have looked at a system called
674 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
675 mounted network backed file system with the features I need.
</p
>
677 <p
>S3QL is a fuse file system with a local cache and cloud storage,
678 handling several different storage providers, any with Amazon S3,
679 Google Drive or OpenStack API. There are heaps of such storage
680 providers. S3QL can also use a local directory as storage, which
681 combined with sshfs allow for file storage on any ssh server. S3QL
682 include support for encryption, compression, de-duplication, snapshots
683 and immutable file systems, allowing me to mount the remote storage as
684 a local mount point, look at and use the files as if they were local,
685 while the content is stored in the cloud as well. This allow me to
686 have a backup that should survive fire. The file system can not be
687 shared between several machines at the same time, as only one can
688 mount it at the time, but any machine with the encryption key and
689 access to the storage service can mount it if it is unmounted.
</p
>
691 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
692 package is included already. So to get started, run
<tt
>apt-get
693 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
694 Greenqloud, after reading their nice recipe on
695 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
696 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
697 in Iceland more than those in USA when it come to keeping my personal
698 data safe and private, and thus would rather spend money on a company
699 in Iceland. Another nice recipe is available from the article
700 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
701 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
702 Admin magazine. When the provider is picked, figure out how to get
703 the API key needed to connect to the storage API. With Greencloud,
704 the key did not show up until I had added payment details to my
707 <p
>Armed with the API access details, it is time to create the file
708 system. First, create a new bucket in the cloud. This bucket is the
709 file system storage area. I picked a bucket name reflecting the
710 machine that was going to store data there, but any name will do.
711 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
712 the API login and password, and a locally created password. Store it
713 all in ~root/.s3ql/authinfo2 like this:
715 <p
><blockquote
><pre
>
717 storage-url: s3c://s.greenqloud.com:
443/bucket-name
718 backend-login: API-login
719 backend-password: API-password
720 fs-passphrase: local-password
721 </pre
></blockquote
></p
>
723 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
724 but any sensible way to create a fairly random password should do it.
725 Armed with these details, it is now time to run mkfs, entering the API
726 details and password to create it:
</p
>
728 <p
><blockquote
><pre
>
729 # mkdir -m
700 /var/lib/s3ql-cache
730 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
731 --ssl s3c://s.greenqloud.com:
443/bucket-name
733 Enter backend password:
734 Before using S3QL, make sure to read the user
's guide, especially
735 the
'Important Rules to Avoid Loosing Data
' section.
736 Enter encryption password:
737 Confirm encryption password:
738 Generating random encryption key...
739 Creating metadata tables...
749 Compressing and uploading metadata...
750 Wrote
0.00 MB of compressed metadata.
751 #
</pre
></blockquote
></p
>
753 <p
>The next step is mounting the file system to make the storage available.
755 <p
><blockquote
><pre
>
756 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
757 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
758 Using
4 upload threads.
759 Downloading and decompressing metadata...
769 Mounting filesystem...
771 Filesystem Size Used Avail Use% Mounted on
772 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
774 </pre
></blockquote
></p
>
776 <p
>The file system is now ready for use. I use rsync to store my
777 backups in it, and as the metadata used by rsync is downloaded at
778 mount time, no network traffic (and storage cost) is triggered by
779 running rsync. To unmount, one should not use the normal umount
780 command, as this will not flush the cache to the cloud storage, but
781 instead running the umount.s3ql command like this:
783 <p
><blockquote
><pre
>
786 </pre
></blockquote
></p
>
788 <p
>There is a fsck command available to check the file system and
789 correct any problems detected. This can be used if the local server
790 crashes while the file system is mounted, to reset the
"already
791 mounted
" flag. This is what it look like when processing a working
792 file system:
</p
>
794 <p
><blockquote
><pre
>
795 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
796 Using cached metadata.
797 File system seems clean, checking anyway.
798 Checking DB integrity...
799 Creating temporary extra indices...
800 Checking lost+found...
801 Checking cached objects...
802 Checking names (refcounts)...
803 Checking contents (names)...
804 Checking contents (inodes)...
805 Checking contents (parent inodes)...
806 Checking objects (reference counts)...
807 Checking objects (backend)...
808 ..processed
5000 objects so far..
809 ..processed
10000 objects so far..
810 ..processed
15000 objects so far..
811 Checking objects (sizes)...
812 Checking blocks (referenced objects)...
813 Checking blocks (refcounts)...
814 Checking inode-block mapping (blocks)...
815 Checking inode-block mapping (inodes)...
816 Checking inodes (refcounts)...
817 Checking inodes (sizes)...
818 Checking extended attributes (names)...
819 Checking extended attributes (inodes)...
820 Checking symlinks (inodes)...
821 Checking directory reachability...
822 Checking unix conventions...
823 Checking referential integrity...
824 Dropping temporary indices...
825 Backing up old metadata...
835 Compressing and uploading metadata...
836 Wrote
0.89 MB of compressed metadata.
838 </pre
></blockquote
></p
>
840 <p
>Thanks to the cache, working on files that fit in the cache is very
841 quick, about the same speed as local file access. Uploading large
842 amount of data is to me limited by the bandwidth out of and into my
843 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
844 which is very close to my upload speed, and downloading the same
845 Debian installation ISO gave me
610 kiB/s, close to my download speed.
846 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
847 network, not the file system code. I do not know what a good cache
848 size would be, but suspect that the cache should e larger than your
849 working set.
</p
>
851 <p
>I mentioned that only one machine can mount the file system at the
852 time. If another machine try, it is told that the file system is
855 <p
><blockquote
><pre
>
856 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
857 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
858 Using
8 upload threads.
859 Backend reports that fs is still mounted elsewhere, aborting.
861 </pre
></blockquote
></p
>
863 <p
>The file content is uploaded when the cache is full, while the
864 metadata is uploaded once every
24 hour by default. To ensure the
865 file system content is flushed to the cloud, one can either umount the
866 file system, or ask S3QL to flush the cache and metadata using
869 <p
><blockquote
><pre
>
870 # s3qlctrl upload-meta /s3ql
871 # s3qlctrl flushcache /s3ql
873 </pre
></blockquote
></p
>
875 <p
>If you are curious about how much space your data uses in the
876 cloud, and how much compression and deduplication cut down on the
877 storage usage, you can use s3qlstat on the mounted file system to get
880 <p
><blockquote
><pre
>
882 Directory entries:
9141
885 Total data size:
22049.38 MB
886 After de-duplication:
21955.46 MB (
99.57% of total)
887 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
888 Database size:
2.39 MB (uncompressed)
889 (some values do not take into account not-yet-uploaded dirty blocks in cache)
891 </pre
></blockquote
></p
>
893 <p
>I mentioned earlier that there are several possible suppliers of
894 storage. I did not try to locate them all, but am aware of at least
895 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
896 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
897 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
898 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
899 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
900 accept payment in Bitcoin. Pick one that suit your need. Some of
901 them provide several GiB of free storage, but the prize models are
902 quite different and you will have to figure out what suits you
905 <p
>While researching this blog post, I had a look at research papers
906 and posters discussing the S3QL file system. There are several, which
907 told me that the file system is getting a critical check by the
908 science community and increased my confidence in using it. One nice
910 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
911 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
912 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
913 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
914 and Pamela Smith. Please have a look.
</p
>
916 <p
>Given my problems with different file systems earlier, I decided to
917 check out the mounted S3QL file system to see if it would be usable as
918 a home directory (in other word, that it provided POSIX semantics when
919 it come to locking and umask handling etc). Running
920 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
921 test code to check file system semantics
</a
>, I was happy to discover that
922 no error was found. So the file system can be used for home
923 directories, if one chooses to do so.
</p
>
925 <p
>If you do not want a locally file system, and want something that
926 work without the Linux fuse file system, I would like to mention the
927 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
928 provide locally encrypted backup using a command line client. It have
929 a nicer access control system, where one can split out read and write
930 access, allowing some systems to write to the backup and others to
931 only read from it.
</p
>
933 <p
>As usual, if you use Bitcoin and want to show your support of my
934 activities, please send Bitcoin donations to my address
935 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
940 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
941 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
942 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
943 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
944 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
945 project
</a
> is working on providing the software and hardware for
946 making it easy for non-technical people to host their data and
947 communication at home, and being able to communicate with their
948 friends and family encrypted and away from prying eyes. It has been
949 going on for a while, and is slowly progressing towards a new test
950 release (
0.2).
</p
>
952 <p
>And what day could be better than the Pi day to announce that the
953 new version will provide
"hard drive
" / SD card / USB stick images for
954 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
955 system), and can also be installed using a Debian installer preseed
956 file. The Debian based Freedombox is now based on Debian Jessie,
957 where most of the needed packages used are already present. Only one,
958 the freedombox-setup package, is missing. To try to build your own
959 boot image to test the current status, fetch the freedom-maker scripts
961 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
962 with a user with sudo access to become root:
965 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
967 sudo apt-get install git vmdebootstrap mercurial python-docutils \
968 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
970 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
973 <p
>Root access is needed to run debootstrap and mount loopback
974 devices. See the README for more details on the build. If you do not
975 want all three images, trim the make line. But note that thanks to
<a
976 href=
"https://bugs.debian.org/
741407">a race condition in
977 vmdebootstrap
</a
>, the build might fail without the patch to the
978 kpartx call.
</p
>
980 <p
>If you instead want to install using a Debian CD and the preseed
981 method, boot a Debian Wheezy ISO and use this boot argument to load
982 the preseed values:
</p
>
985 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
988 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
989 recently introduced bug in apt in Jessie
</a
>, the installer will
990 currently hang while setting up APT sources. Killing the
991 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
992 installation will get the installation going. This affect all
993 installations in Jessie, and I expect it will be fixed soon.
</p
>
995 <p
>Give it a go and let us know how it goes on the mailing list, and help
996 us get the new release published. :) Please join us on
997 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
998 irc.debian.org)
</a
> and
999 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1000 mailing list
</a
> if you want to help make this vision come true.
</p
>
1005 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
1006 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
1007 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
1008 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
1009 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
1010 innetgr tools, because I needed them in
1011 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
1012 ng-utils, and it has served me well. I placed the project under the
1013 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
1014 repository. But many years ago, the CVS repository was dropped (lost,
1015 not migrated to new hardware, not sure), and the project have lacked a
1016 proper home since then.
</p
>
1018 <p
>Last summer, I had a look at the package and made a new release
1019 fixing a irritating crash bug, but was unable to store the changes in
1020 a proper source control system. I applied for a project on
1021 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
1022 to follow up on it. Until today. :)
</p
>
1024 <p
>After many hours of cleaning and migration, the ng-utils project
1025 now have a new home, and a git repository with the highlight of the
1026 history of the project. I published all release tarballs and imported
1027 them into the git repository. As the project is really stable and not
1028 expected to gain new features any time soon, I decided to make a new
1029 release and call it
1.0. Visit the new project home on
1030 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
1031 if you want to check it out. The new version is also uploaded into
1032 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
1037 <title>Testing sysvinit from experimental in Debian Hurd
</title>
1038 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
1039 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
1040 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
1041 <description><p
>A few days ago I decided to try to help the Hurd people to get
1042 their changes into sysvinit, to allow them to use the normal sysvinit
1043 boot system instead of their old one. This follow up on the
1044 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
1045 Google Summer of Code work
</a
> done last summer by Justus Winter to
1046 get Debian on Hurd working more like Debian on Linux. To get started,
1047 I downloaded a prebuilt hard disk image from
1048 <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
>,
1049 and started it using virt-manager.
</p
>
1051 <p
>The first think I had to do after logging in (root without any
1052 password) was to get the network operational. I followed
1053 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
1054 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
1055 commands as root to get the machine to accept a IP address from the
1056 kvm internal DHCP server:
</p
>
1058 <p
><blockquote
><pre
>
1059 settrans -fgap /dev/netdde /hurd/netdde
1060 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
1061 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
1063 </pre
></blockquote
></p
>
1065 <p
>After this, the machine had internet connectivity, and I could
1066 upgrade it and install the sysvinit packages from experimental and
1067 enable it as the default boot system in Hurd.
</p
>
1069 <p
>But before I did that, I set a password on the root user, as ssh is
1070 running on the machine it for ssh login to work a password need to be
1071 set. Also, note that a bug somewhere in openssh on Hurd block
1072 compression from working. Remember to turn that off on the client
1075 <p
>Run these commands as root to upgrade and test the new sysvinit
1078 <p
><blockquote
><pre
>
1079 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
1080 deb http://http.debian.net/debian/ experimental main
1083 apt-get dist-upgrade
1084 apt-get install -t experimental initscripts sysv-rc sysvinit \
1085 sysvinit-core sysvinit-utils
1086 update-alternatives --config runsystem
1087 </pre
></blockquote
></p
>
1089 <p
>To reboot after switching boot system, you have to use
1090 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
1091 yet a sysvinit process able to receive the signals from the normal
1092 'reboot
' command. After switching to sysvinit as the boot system,
1093 upgrading every package and rebooting, the network come up with DHCP
1094 after boot as it should, and the settrans/pkill hack mentioned at the
1095 start is no longer needed. But for some strange reason, there are no
1096 longer any login prompt in the virtual console, so I logged in using
1099 <p
>Note that there are some race conditions in Hurd making the boot
1100 fail some times. No idea what the cause is, but hope the Hurd porters
1101 figure it out. At least Justus said on IRC (#debian-hurd on
1102 irc.debian.org) that they are aware of the problem. A way to reduce
1103 the impact is to upgrade to the Hurd packages built by Justus by
1104 adding this repository to the machine:
</p
>
1106 <p
><blockquote
><pre
>
1107 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
1108 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1110 </pre
></blockquote
></p
>
1112 <p
>At the moment the prebuilt virtual machine get some packages from
1113 http://ftp.debian-ports.org/debian, because some of the packages in
1114 unstable do not yet include the required patches that are lingering in
1115 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
1117 <p
><blockquote
><pre
>
1118 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
1119 i emacs - GNU Emacs editor (metapackage)
1120 i gdb - GNU Debugger
1121 i hurd-recommended - Miscellaneous translators
1122 i isc-dhcp-client - ISC DHCP client
1123 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1124 i libc-bin - Embedded GNU C Library: Binaries
1125 i libc-dev-bin - Embedded GNU C Library: Development binaries
1126 i libc0.3 - Embedded GNU C Library: Shared libraries
1127 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1128 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1129 i multiarch-support - Transitional package to ensure multiarch compatibilit
1130 i A x11-common - X Window System (X.Org) infrastructure
1131 i xorg - X.Org X Window System
1132 i A xserver-xorg - X.Org X server
1133 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1135 </pre
></blockquote
></p
>
1137 <p
>All in all, testing hurd has been an interesting experience. :)
1138 X.org did not work out of the box and I never took the time to follow
1139 the porters instructions to fix it. This time I was interested in the
1140 command line stuff.
<p
>
1145 <title>New chrpath release
0.16</title>
1146 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
1147 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
1148 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
1149 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
1150 find problems in C, C++ and Java code using static source code
1151 analysis. It can detect a lot of different problems, and is very
1152 useful to find memory and locking bugs in the error handling part of
1153 the source. The company behind it provide
1154 <a href=
"https://scan.coverity.com/
">check of free software projects as
1155 a community service
</a
>, and many hundred free software projects are
1156 already checked. A few days ago I decided to have a closer look at
1157 the Coverity system, and discovered that the
1158 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
1159 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
1160 projects I am involved with was already registered. But these are
1161 fairly big, and I would also like to have a small and easy project to
1162 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
1163 checking of the chrpath project
</a
>. It was
1164 added to the checker and discovered seven potential defects. Six of
1165 these were real, mostly resource
"leak
" when the program detected an
1166 error. Nothing serious, as the resources would be released a fraction
1167 of a second later when the program exited because of the error, but it
1168 is nice to do it right in case the source of the program some time in
1169 the future end up in a library. Having fixed all defects and added
1170 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
1171 mailing list for the chrpath developers
</a
>, I decided it was time to
1172 publish a new release. These are the release notes:
</p
>
1174 <p
>New in
0.16 released
2014-
01-
14:
</p
>
1178 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
1179 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
1180 <li
>Mention new project mailing list in the documentation.
</li
>
1185 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
1186 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
1187 project if something is wrong with the new release. The test suite
1188 did not discover any old errors, so if you find a new one, please also
1189 include a test suite check.
</p
>
1194 <title>New chrpath release
0.15</title>
1195 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
1196 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
1197 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
1198 <description><p
>After many years break from the package and a vain hope that
1199 development would be continued by someone else, I finally pulled my
1200 acts together this morning and wrapped up a new release of chrpath,
1201 the command line tool to modify the rpath and runpath of already
1202 compiled ELF programs. The update was triggered by the persistence of
1203 Isha Vishnoi at IBM, which needed a new config.guess file to get
1204 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
1205 is working on. I checked the
1206 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
1207 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
1208 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
1209 packages for interesting patches (failed to find the source from
1210 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1211 These are the release notes:
</p
>
1213 <p
>New in
0.15 released
2013-
11-
24:
</p
>
1217 <li
>Updated config.sub and config.guess from the GNU project to work
1218 with newer architectures. Thanks to isha vishnoi for the heads
1221 <li
>Updated README with current URLs.
</li
>
1223 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1224 Matthias Klose.
</li
>
1226 <li
>Added missing help for -k|--keepgoing option, using patch by
1227 Petr Machata found in Fedora.
</li
>
1229 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
1230 .dynamic is a NULL terminated string. Based on patch found in
1231 Fedora credited Axel Thimm and Christian Krause.
</li
>
1236 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
1237 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
1238 project if something is wrong with the new release. The test suite
1239 did not discover any old errors, so if you find a new one, please also
1240 include a testsuite check.
</p
>
1245 <title>Debian init.d boot script example for rsyslog
</title>
1246 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
1247 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
1248 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
1249 <description><p
>If one of the points of switching to a new init system in Debian is
1250 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
1251 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
1252 init.d scripts at all. Here is an example init.d script, ie a rewrite
1253 of /etc/init.d/rsyslog:
</p
>
1255 <p
><pre
>
1256 #!/lib/init/init-d-script
1259 # Required-Start: $remote_fs $time
1260 # Required-Stop: umountnfs $time
1261 # X-Stop-After: sendsigs
1262 # Default-Start:
2 3 4 5
1263 # Default-Stop:
0 1 6
1264 # Short-Description: enhanced syslogd
1265 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1266 # It is quite compatible to stock sysklogd and can be
1267 # used as a drop-in replacement.
1269 DESC=
"enhanced syslogd
"
1270 DAEMON=/usr/sbin/rsyslogd
1271 </pre
></p
>
1273 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
1274 script was
137 lines, and the above is just
15 lines, most of it meta
1275 info/comments.
</p
>
1277 <p
>How to do this, you ask? Well, one create a new script
1278 /lib/init/init-d-script looking something like this:
1280 <p
><pre
>
1283 # Define LSB log_* functions.
1284 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
1285 # and status_of_proc is working.
1286 . /lib/lsb/init-functions
1289 # Function that starts the daemon/service
1295 #
0 if daemon has been started
1296 #
1 if daemon was already running
1297 #
2 if daemon could not be started
1298 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
1300 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1303 # Add code here, if necessary, that waits for the process to be ready
1304 # to handle requests from services started subsequently which depend
1305 # on this one. As a last resort, sleep for some time.
1309 # Function that stops the daemon/service
1314 #
0 if daemon has been stopped
1315 #
1 if daemon was already stopped
1316 #
2 if daemon could not be stopped
1317 # other if a failure occurred
1318 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
1319 RETVAL=
"$?
"
1320 [
"$RETVAL
" =
2 ]
&& return
2
1321 # Wait for children to finish too if this is a daemon that forks
1322 # and if the daemon is only ever run from this initscript.
1323 # If the above conditions are not satisfied then add some other code
1324 # that waits for the process to drop all resources that could be
1325 # needed by services started subsequently. A last resort is to
1326 # sleep for some time.
1327 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
1328 [
"$?
" =
2 ]
&& return
2
1329 # Many daemons don
't delete their pidfiles when they exit.
1331 return
"$RETVAL
"
1335 # Function that sends a SIGHUP to the daemon/service
1339 # If the daemon can reload its configuration without
1340 # restarting (for example, when it is sent a SIGHUP),
1341 # then implement that here.
1343 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
1348 scriptbasename=
"$(basename $
1)
"
1349 echo
"SN: $scriptbasename
"
1350 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
1351 script=
"$
1"
1358 NAME=$(basename $DAEMON)
1359 PIDFILE=/var/run/$NAME.pid
1361 # Exit if the package is not installed
1362 #[ -x
"$DAEMON
" ] || exit
0
1364 # Read configuration variable file if it is present
1365 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
1367 # Load the VERBOSE setting and other rcS variables
1370 case
"$
1" in
1372 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
1374 case
"$?
" in
1375 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
1376 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
1380 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
1382 case
"$?
" in
1383 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
1384 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
1388 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
1390 #reload|force-reload)
1392 # If do_reload() is not implemented then leave this commented out
1393 # and leave
'force-reload
' as an alias for
'restart
'.
1395 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
1399 restart|force-reload)
1401 # If the
"reload
" option is implemented then remove the
1402 #
'force-reload
' alias
1404 log_daemon_msg
"Restarting $DESC
" "$NAME
"
1406 case
"$?
" in
1409 case
"$?
" in
1411 1) log_end_msg
1 ;; # Old process is still running
1412 *) log_end_msg
1 ;; # Failed to start
1422 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
1428 </pre
></p
>
1430 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
1431 lot. I did not really polish the approach, so it might not always
1432 work out of the box, but you get the idea. I did not try very hard to
1433 optimize it nor make it more robust either.
</p
>
1435 <p
>A better argument for switching init system in Debian than reducing
1436 the size of init scripts (which is a good thing to do anyway), is to
1437 get boot system that is able to handle the kernel events sensibly and
1438 robustly, and do not depend on the boot to run sequentially. The boot
1439 and the kernel have not behaved sequentially in years.
</p
>
1444 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
1445 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
1446 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
1447 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
1448 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
1449 remote display access is the preferred solution with oVirt and RedHat
1450 Enterprise Virtualization, and I was sad to discover the other day
1451 that the browser plugin needed to use these systems seamlessly was
1452 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
1453 for a package
</a
> was from
2012-
04-
10 with no progress since
1454 2013-
04-
01, so I decided to wrap up a package based on the great work
1455 from Cajus Pollmeier and put it in a collab-maint maintained git
1456 repository to get a package I could use. I would very much like
1457 others to help me maintain the package (or just take over, I do not
1458 mind), but as no-one had volunteered so far, I just uploaded it to
1459 NEW. I hope it will be available in Debian in a few days.
</p
>
1461 <p
>The source is now available from
1462 <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
>
1467 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
1468 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
1469 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
1470 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
1471 <description><p
>The
1472 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
1473 program is a a very nice system to create virtual machine images. It
1474 create a image file, add a partition table, mount it and run
1475 debootstrap in the mounted directory to create a Debian system on a
1476 stick. Yesterday, I decided to try to teach it how to make images for
1477 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
1478 of a plan to simplify the build system for
1479 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
1480 project
</a
>. The FreedomBox project already uses vmdebootstrap for
1481 the virtualbox images, but its current build system made multistrap
1482 based system for Dreamplug images, and it is lacking support for
1483 Raspberry Pi.
</p
>
1485 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
1486 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1487 code and adjusted it to be able to build armel images on my amd64
1488 Debian laptop. I ended up giving vmdebootstrap five new options,
1489 allowing me to replicate the image creation process I use to make
1490 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
1491 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
1492 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
1493 call debootstrap with --foreign and to copy the handler into the
1494 generated chroot before running the second stage. This allow
1495 vmdebootstrap to create armel images on an amd64 host. Next I added
1496 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
1497 fstype
</tt
> to teach it to create a separate /boot/ partition with the
1498 given file system type, allowing me to create an image with a vfat
1499 partition for the /boot/ stuff. I also added a
<tt
>--variant
1500 variant
</tt
> option to allow me to create smaller images without the
1501 Debian base system packages installed. Finally, I added an option
1502 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
1503 as a boot loader. It is not needed on the Raspberry Pi and probably
1504 most other non-x86 architectures. The changes were accepted by the
1505 upstream author of vmdebootstrap yesterday and today, and is now
1507 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
1508 upstream project page
</a
>.
</p
>
1510 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
1511 create a small script (the customize script) to add the non-free
1512 binary blob needed to boot the Raspberry Pi and the APT source
1515 <p
><pre
>
1517 set -e # Exit on first error
1518 rootdir=
"$
1"
1519 cd
"$rootdir
"
1520 cat
&lt;
&lt;EOF
> etc/apt/sources.list
1521 deb http://http.debian.net/debian/ jessie main contrib non-free
1523 # Install non-free binary blob needed to boot Raspberry Pi. This
1524 # install a kernel somewhere too.
1525 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
1526 -O $rootdir/usr/bin/rpi-update
1527 chmod a+x $rootdir/usr/bin/rpi-update
1528 mkdir -p $rootdir/lib/modules
1529 touch $rootdir/boot/start.elf
1530 chroot $rootdir rpi-update
1531 </pre
></p
>
1533 <p
>Next, fetch the latest vmdebootstrap script and call it like this
1534 to build the image:
</p
>
1537 sudo ./vmdebootstrap \
1540 --distribution jessie \
1541 --mirror http://http.debian.net/debian \
1550 --root-password raspberry \
1551 --hostname raspberrypi \
1552 --foreign /usr/bin/qemu-arm-static \
1553 --customize `pwd`/customize \
1555 --package git-core \
1556 --package binutils \
1557 --package ca-certificates \
1560 </pre
></p
>
1562 <p
>The list of packages being installed are the ones needed by
1563 rpi-update to make the image bootable on the Raspberry Pi, with the
1564 exception of netbase, which is needed by debootstrap to find
1565 /etc/hosts with the minbase variant. I really wish there was a way to
1566 set up an Raspberry Pi using only packages in the Debian archive, but
1567 that is not possible as far as I know, because it boots from the GPU
1568 using a non-free binary blob.
</p
>
1570 <p
>The build host need debootstrap, kpartx and qemu-user-static and
1571 probably a few others installed. I have not checked the complete
1572 build dependency list.
</p
>
1574 <p
>The resulting image will not use the hardware floating point unit
1575 on the Raspberry PI, because the armel architecture in Debian is not
1576 optimized for that use. So the images created will be a bit slower
1577 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
1582 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
1583 <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>
1584 <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>
1585 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
1586 <description><p
>The last few days I came across a few good causes that should get
1587 wider attention. I recommend signing and donating to each one of
1590 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
1591 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
1592 Women program which is a Google Summer of Code like initiative to get
1593 more women involved in free software. One debian sponsor has offered
1594 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
1595 earmarked
</a
> for this initiative. I donated a few minutes ago, and
1596 hope you will to. :)
</p
>
1598 <p
>And the Electronic Frontier Foundation just announced plans to
1599 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
1600 documentaries about the excessive spying
</a
> on every Internet user that
1601 take place these days, and their need to fund the work. I
've already
1602 donated. Are you next?
</p
>
1604 <p
>For my Norwegian audience, the organisation Studentenes og
1605 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
1606 statement under the heading
1607 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
1608 Access
</a
> for those of us asking for more focus on open access in the
1609 Norwegian government. So far
499 signatures. I hope you will sign it
1615 <title>Videos about the Freedombox project - for inspiration and learning
</title>
1616 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
1617 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
1618 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
1619 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
1620 project
</a
> have been going on for a while, and have presented the
1621 vision, ideas and solution several places. Here is a little
1622 collection of videos of talks and presentation of the project.
</p
>
1626 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
1627 2,
5 minute marketing film
</a
> (Youtube)
</li
>
1629 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
1630 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
1632 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
1633 Freedom in the Cloud - Software Freedom, Privacy and and Security for
1634 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
1635 (Youtube)
</li
>
1637 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
1638 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
1640 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
1641 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
1643 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
1644 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
1645 York City in
2012</a
> (Youtube)
</li
>
1647 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
1648 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
1649 (Youtube)
</li
>
1651 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
1652 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
1654 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
1655 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
1657 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
1658 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
1659 2013</a
> (Youtube)
</li
>
1663 <p
>A larger list is available from
1664 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
1665 Freedombox Wiki
</a
>.
</p
>
1667 <p
>On other news, I am happy to report that Freedombox based on Debian
1668 Jessie is coming along quite well, and soon both Owncloud and using
1669 Tor should be available for testers of the Freedombox solution. :) In
1670 a few weeks I hope everything needed to test it is included in Debian.
1671 The withsqlite package is already in Debian, and the plinth package is
1672 pending in NEW. The third and vital part of that puzzle is the
1673 metapackage/setup framework, which is still pending an upload. Join
1674 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
1675 (#freedombox on irc.debian.org)
</a
> and
1676 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1677 mailing list
</a
> if you want to help make this vision come true.
</p
>
1682 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
1683 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
1684 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
1685 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
1686 <description><p
>I was introduced to the
1687 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
1688 in
2010, when Eben Moglen presented his vision about serving the need
1689 of non-technical people to keep their personal information private and
1690 within the legal protection of their own homes. The idea is to give
1691 people back the power over their network and machines, and return
1692 Internet back to its intended peer-to-peer architecture. Instead of
1693 depending on a central service, the Freedombox will give everyone
1694 control over their own basic infrastructure.
</p
>
1696 <p
>I
've intended to join the effort since then, but other tasks have
1697 taken priority. But this summers nasty news about the misuse of trust
1698 and privilege exercised by the
"western
" intelligence gathering
1699 communities increased my eagerness to contribute to a point where I
1700 actually started working on the project a while back.
</p
>
1702 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
1703 Debian initiative
</a
> based on the vision from Eben Moglen, is to
1704 create a simple and cheap Debian based appliance that anyone can hook
1705 up in their home and get access to secure and private services and
1706 communication. The initial deployment platform have been the
1707 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
1708 which is a piece of hardware I do not own. So to be able to test what
1709 the current Freedombox setup look like, I had to come up with a way to install
1710 it on some hardware I do have access to. I have rewritten the
1711 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
1712 image build framework to use .deb packages instead of only copying
1713 setup into the boot images, and thanks to this rewrite I am able to
1714 set up any machine supported by Debian Wheezy as a Freedombox, using
1715 the previously mentioned deb (and a few support debs for packages
1716 missing in Debian).
</p
>
1718 <p
>The current Freedombox setup consist of a set of bootstrapping
1720 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
1721 and a administrative web interface
1722 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
1723 withsqlite), as well as a privacy enhancing proxy based on
1724 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
1725 (freedombox-privoxy). There is also a web/javascript based XMPP
1726 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
1727 trying (unsuccessfully so far) to talk to the XMPP server
1728 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
1729 web interface is pluggable, and the goal is to use it to enable OpenID
1730 services, mesh network connectivity, use of TOR, etc, etc. Not much of
1731 this is really working yet, see
1732 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
1733 project TODO
</a
> for links to GIT repositories. Most of the code is
1734 on github at the moment. The HTTP proxy is operational out of the
1735 box, and the admin web interface can be used to add/remove plinth
1736 users. I
've not been able to do anything else with it so far, but
1737 know there are several branches spread around github and other places
1738 with lots of half baked features.
</p
>
1740 <p
>Anyway, if you want to have a look at the current state, the
1741 following recipes should work to give you a test machine to poke
1744 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
1748 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
1749 <li
>Boot from it, either as CD or USB stick.
</li
>
1750 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
1751 to the Debian installer:
<p
>
1752 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
1754 <li
>Answer the few language/region/password questions and pick disk to
1755 install on.
</li
>
1757 <li
>When the installation is finished and the machine have rebooted a
1758 few times, your Freedombox is ready for testing.
</li
>
1762 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
1766 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
1767 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
1768 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
1770 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
1771 </pre
></li
>
1772 <li
><p
>Run this as root:
</p
>
1774 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
1777 apt-get install freedombox-setup
1778 /usr/lib/freedombox/setup
1779 </pre
></li
>
1780 <li
>Reboot into your freshly created Freedombox.
</li
>
1784 <p
>You can test it on other architectures too, but because the
1785 freedombox-privoxy package is binary, it will only work as intended on
1786 the architectures where I have had time to build the binary and put it
1787 in my APT repository. But do not let this stop you. It is only a
1788 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
1790 <p
>Note that by default Freedombox is a DHCP server on the
1791 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
1792 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
1793 disable
</tt
>" as root.
</p
>
1795 <p
>Please let me know if this works for you, or if you have any
1796 problems. We gather on the IRC channel
1797 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
1798 irc.debian.org and the
1799 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
1800 mailing list
</a
>.
</p
>
1802 <p
>Once you get your freedombox operational, you can visit
1803 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
1804 welcome screen (dead end - do not be surprised if you are unable to
1805 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
1806 to look at the rest of plinth. The default user is
'admin
' and the
1807 default password is
'secret
'.
</p
>
1812 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
1813 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
1814 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
1815 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
1816 <description><p
>Earlier, I reported about
1817 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
1818 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
1819 told by IBM that the original disk should be thrown away. And as
1820 there no longer was a problem if I bricked the firmware, I decided
1821 today to try to install Intel firmware to replace the Lenovo firmware
1822 currently on the disk.
</p
>
1824 <p
>I searched the Intel site for firmware, and found
1825 <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
>
1826 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
1827 according to the site should contain the latest firmware for SSD
1828 disks. I inserted the broken disk in one of my spare laptops and
1829 booted the ISO from a USB stick. The disk was recognized, but the
1830 program claimed the newest firmware already were installed and refused
1831 to insert any Intel firmware. So no change, and the disk is still
1832 unable to handle write load. :( I guess the only way to get them
1833 working would be if Lenovo releases new firmware. No idea how likely
1834 that is. Anyway, just blogging about this test for completeness. I
1835 got a working Samsung disk, and see no point in spending more time on
1836 the broken disks.
</p
>
1841 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
1842 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
1843 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
1844 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
1845 <description><p
>Today I switched to
1846 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
1847 new laptop
</a
>. I
've previously written about the problems I had with
1848 my new Thinkpad X230, which was delivered with an
1849 <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
1850 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
1851 sustained writes. My hardware supplier have been very forthcoming in
1852 trying to find a solution, and after first trying with another
1853 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
1854 disk instead to fix it once and for all. The Samsung disk survived
1855 the installation of Debian with encrypted disks (filling the disk with
1856 random data during installation killed the first two), and I thus
1857 decided to trust it with my data. I have installed it as a Debian Edu
1858 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
1859 server at home using Kerberos and LDAP, and will use it as my work
1860 station from now on.
</p
>
1862 <p
>As this is a solid state disk with no moving parts, I believe the
1863 Debian Wheezy default installation need to be tuned a bit to increase
1864 performance and increase life time of the disk. The Linux kernel and
1865 user space applications do not yet adjust automatically to such
1866 environment. To make it easier for my self, I created a draft Debian
1867 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
1868 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
1869 for the ssd-setup package
</a
> is available from collab-maint, and it
1870 is set up to adjust the setup of the machine by just installing the
1871 package. If there is any non-SSD disk in the machine, the package
1872 will refuse to install, as I did not try to write any logic to sort
1873 file systems in SSD and non-SSD file systems.
</p
>
1875 <p
>I consider the package a draft, as I am a bit unsure how to best
1876 set up Debian Wheezy with an SSD. It is adjusted to my use case,
1877 where I set up the machine with one large encrypted partition (in
1878 addition to /boot), put LVM on top of this and set up partitions on
1879 top of this again. See the README file in the package source for the
1880 references I used to pick the settings. At the moment these
1881 parameters are tuned:
</p
>
1885 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
1886 (adding discard to /etc/crypttab)
</li
>
1888 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
1889 this case a cryptsetup partition) by changing issue_discards from
1890 0 to
1 in /etc/lvm/lvm.conf.
</li
>
1892 <li
>Set relatime as a file system option for ext3 and ext4 file
1895 <li
>Tell swap to use TRIM commands by adding
'discard
' to
1896 /etc/fstab.
</li
>
1898 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
1900 <li
>Run fstrim on every ext3 and ext4 file system every night (from
1901 cron.daily).
</li
>
1903 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
1904 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
1908 <p
>During installation, I cancelled the part where the installer fill
1909 the disk with random data, as this would kill the SSD performance for
1910 little gain. My goal with the encrypted file system is to ensure
1911 those stealing my laptop end up with a brick and not a working
1912 computer. I have no hope in keeping the really resourceful people
1913 from getting the data on the disk (see
1914 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
1915 Thus I concluded that adding the discard option to crypttab is the
1916 right thing to do.
</p
>
1918 <p
>I considered using the noop I/O scheduler, as several recommended
1919 it for SSD, but others recommended deadline and a benchmark I found
1920 indicated that deadline might be better for interactive use.
</p
>
1922 <p
>I also considered using the
'discard
' file system option for ext3
1923 and ext4, but read that it would give a performance hit ever time a
1924 file is removed, and thought it best to that that slowdown once a day
1925 instead of during my work.
</p
>
1927 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
1928 this is already done by Debian Edu.
</p
>
1930 <p
>I have not yet started on the user space tuning. I expect
1931 iceweasel need some tuning, and perhaps other applications too, but
1932 have not yet had time to investigate those parts.
</p
>
1934 <p
>The package should work on Ubuntu too, but I have not yet tested it
1937 <p
>As for the answer to the question in the title of this blog post,
1938 as far as I know, the only solution I know about is to replace the
1939 disk. It might be possible to flash it with Intel firmware instead of
1940 the Lenovo firmware. But I have not tried and did not want to do so
1941 without approval from Lenovo as I wanted to keep the warranty on the
1942 disk until a solution was found and they wanted the broken disks
1948 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
1949 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
1950 <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>
1951 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
1952 <description><p
>A few days ago, I wrote about
1953 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
1954 problems I experienced with my new X230 and its SSD disk
</a
>, which
1955 was dying during installation because it is unable to cope with
1956 sustained write. My supplier is in contact with
1957 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
1958 replacement disk to try to fix the problem. They decided to send an
1959 identical model, so my hopes for a permanent fix was slim.
</p
>
1961 <p
>Anyway, today I got the replacement disk and tried to install
1962 Debian Edu Wheezy with encrypted disk on it. The new disk have the
1963 same firmware version as the original. This time my hope raised
1964 slightly as the installation progressed, as the original disk used to
1965 die after
4-
7% of the disk was written to, while this time it kept
1966 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
1967 died again and I was back on square one. I still do not have a new
1968 laptop with a disk I can trust. I can not live with a disk that might
1969 lock up when I download a new
1970 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
1971 other large files. I look forward to hearing from my supplier with
1972 the next proposal from Lenovo.
</p
>
1974 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
1975 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
1976 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
1977 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
1978 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
1979 P/N
45N8295, P0C38732.
</p
>
1981 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
1982 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
1983 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
1984 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
1985 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
1986 P/N
45N8295, P0C38732.
</p
>
1988 <p
>The only difference is in the first number (serial number?), ISN,
1989 SA, date and WNPP values. Mentioning all the details here in case
1990 someone is able to use the information to find a way to identify the
1991 failing disk among working ones (if any such working disk actually
1997 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
1998 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
1999 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
2000 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
2001 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
2002 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2003 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
2004 member assosiation NUUG
</a
> and
2005 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
2006 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
2007 Bitraf
</a
>.
</p
>
2009 <p
>It starts
10:
00 and continue until late evening. Everyone is
2010 welcome, and there is no fee to participate. There is on the other
2011 hand limited space, and only room for
30 people. Please put your name
2012 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
2013 wiki page
</a
> if you plan to join us.
</p
>
2018 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
2019 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
2020 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
2021 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
2022 <description><p
>Half a year ago, I reported that I had to find a
2023 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
2024 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
2025 time to spend on it, and it took a while to find a model I believe
2026 will do the job, but two days ago the replacement finally arrived. I
2028 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
2029 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2030 a roaming workstation, and it seemed to work flawlessly. But my
2031 second installation with encrypted disk was not as successful. More
2032 on that below.
</p
>
2034 <p
>I had a hard time trying to track down a good laptop, as my most
2035 important requirements (robust and with a good keyboard) are never
2036 listed in the feature list. But I did get good help from the search
2037 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
2038 allowed me to limit the list of interesting laptops based on my other
2039 requirements. A bit surprising that SSD disk are not disks according
2040 to that search interface, so I had to drop specifying the number of
2041 disks from my search parameters. I also asked around among friends to
2042 get their impression on keyboards and robustness.
</p
>
2044 <p
>So the new laptop arrived, and it is quite a lot wider than the
2045 X41. I am not quite convinced about the keyboard, as it is
2046 significantly wider than my old keyboard, and I have to stretch my
2047 hand a lot more to reach the edges. But the key response is fairly
2048 good and the individual key shape is fairly easy to handle, so I hope
2049 I will get used to it. My old X40 was starting to fail, and I really
2050 needed a new laptop now. :)
</p
>
2052 <p
>Turning off the touch pad was simple. All it took was a quick
2053 visit to the BIOS during boot it disable it.
</p
>
2055 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
2056 lock up during load. And this happen when installing Debian Wheezy
2057 with encrypted disk, while the disk is being filled with random data.
2058 I also tested to install Ubuntu Raring, and it happen there too if I
2059 reenable the code to fill the disk with random data (it is disabled by
2060 default in Ubuntu). And the bug with is already known. It was
2061 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
2062 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
2063 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2064 kernel developers as
2065 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
2066 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
2067 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2068 Lenovo forums, both for
2069 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
2070 2012-
11-
10</a
> and for
2071 <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
2072 03-
20-
2013</a
>. The problem do not only affect installation. The
2073 reports state that the disk lock up during use if many writes are done
2074 on the disk, so it is much no use to work around the installation
2075 problem and end up with a computer that can lock up at any moment.
2077 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
2078 available
</a
> that will lock up the hard drive after running a few
2079 minutes by writing to a file.
</p
>
2081 <p
>I
've contacted my supplier and asked how to handle this, and after
2082 contacting PCHELP Norway (request
01D1FDP) which handle support
2083 requests for Lenovo, his first suggestion was to upgrade the disk
2084 firmware. Unfortunately there is no newer firmware available from
2085 Lenovo, as my disk already have the most recent one (version LF1i). I
2086 hope to hear more from him today and hope the problem can be
2092 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
2093 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
2094 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
2095 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
2096 <description><p
>Half a year ago, I reported that I had to find a replacement for my
2097 trusty old Thinkpad X41. Unfortunately I did not have much time to
2098 spend on it, but today the replacement finally arrived. I ended up
2099 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
2100 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
2101 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2102 this, it is installing what I hope will be a more final installation,
2103 with a encrypted hard drive to ensure any dope head stealing it end up
2104 with an expencive door stop.
</p
>
2106 <p
>I had a hard time trying to track down a good laptop, as my most
2107 important requirements (robust and with a good keyboard) are never
2108 listed in the feature list. But I did get good help from the search
2109 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
2110 allowed me to limit the list of interesting laptops based on my other
2111 requirements. A bit surprising that SSD disk are not disks, so I had
2112 to drop number of disks from my search parameters.
</p
>
2114 <p
>I am not quite convinced about the keyboard, as it is significantly
2115 wider than my old keyboard, and I have to stretch my hand a lot more
2116 to reach the edges. But the key response is fairly good and the
2117 individual key shape is fairly easy to handle, so I hope I will get
2118 used to it. My old X40 was starting to fail, and I really needed a
2119 new laptop now. :)
</p
>
2121 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
2126 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
2127 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
2128 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
2129 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
2130 <description><p
>It annoys me when the computer fail to do automatically what it is
2131 perfectly capable of, and I have to do it manually to get things
2132 working. One such task is to find out what firmware packages are
2133 needed to get the hardware on my computer working. Most often this
2134 affect the wifi card, but some times it even affect the RAID
2135 controller or the ethernet card. Today I pushed version
0.4 of the
2136 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
2137 including a new script isenkram-autoinstall-firmware handling the
2138 process of asking all the loaded kernel modules what firmware files
2139 they want, find debian packages providing these files and install the
2140 debian packages. Here is a test run on my laptop:
</p
>
2142 <p
><pre
>
2143 # isenkram-autoinstall-firmware
2144 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2145 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2146 info: locating packages with the requested firmware files
2147 info: Updating APT sources after adding non-free APT source
2148 info: trying to install firmware-ipw2x00
2151 Preconfiguring packages ...
2152 Selecting previously deselected package firmware-ipw2x00.
2153 (Reading database ...
259727 files and directories currently installed.)
2154 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2155 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
2157 </pre
></p
>
2159 <p
>When all the requested firmware is present, a simple message is
2160 printed instead:
</p
>
2162 <p
><pre
>
2163 # isenkram-autoinstall-firmware
2164 info: did not find any firmware files requested by loaded kernel modules. exiting
2166 </pre
></p
>
2168 <p
>It could use some polish, but it is already working well and saving
2169 me some time when setting up new machines. :)
</p
>
2171 <p
>So, how does it work? It look at the set of currently loaded
2172 kernel modules, and look up each one of them using modinfo, to find
2173 the firmware files listed in the module meta-information. Next, it
2174 download the Contents file from a nearby APT mirror, and search for
2175 the firmware files in this file to locate the package with the
2176 requested firmware file. If the package is in the non-free section, a
2177 non-free APT source is added and the package is installed using
2178 <tt
>apt-get install
</tt
>. The end result is a slightly better working
2181 <p
>I hope someone find time to implement a more polished version of
2182 this script as part of the hw-detect debian-installer module, to
2183 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
2184 #
655507</a
>. There really is no need to insert USB sticks with
2185 firmware during a PXE install when the packages already are available
2186 from the nearby Debian mirror.
</p
>
2191 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
2192 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
2193 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
2194 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
2195 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2196 the screen just turn black when Linux boot, either during installation
2197 or on first boot from the hard disk. I
've seen it once in a while the
2198 last few years, but only recently understood the cause. I
've seen it
2199 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2200 The reason seem to be in the wiring of some laptops. The system to
2201 control the screen background light is inverted, so when Linux try to
2202 turn the brightness fully on, it end up turning it off instead. I do
2203 not know which Linux drivers are affected, but this post is about the
2204 i915 driver used by the
2205 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
2206 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
2208 <p
>The problem can be worked around two ways. Either by adding
2209 i915.invert_brightness=
1 as a kernel option, or by adding a file in
2210 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
2211 option when it load the i915 kernel module. On Debian and Ubuntu, it
2212 can be done by running these commands as root:
</p
>
2215 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
2216 update-initramfs -u -k all
2219 <p
>Since March
2012 there is
2220 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
2221 mechanism in the Linux kernel
</a
> to tell the i915 driver which
2222 hardware have this problem, and get the driver to invert the
2223 brightness setting automatically. To use it, one need to add a row in
2224 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
2225 intel_quirks array
</a
> in the driver source
2226 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
2227 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
2228 number (vendor number
8086 is assumed) and subdevice vendor and device
2231 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
2232 -vvnn
</tt
> for the video card in question:
</p
>
2234 <p
><pre
>
2235 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
2236 3rd Gen Core processor Graphics Controller [
8086:
0156] \
2237 (rev
09) (prog-if
00 [VGA controller])
2238 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
2239 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2240 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2241 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
2242 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
2244 Interrupt: pin A routed to IRQ
42
2245 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
2246 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
2247 Region
4: I/O ports at
4000 [size=
64]
2248 Expansion ROM at
<unassigned
> [disabled]
2249 Capabilities:
<access denied
>
2250 Kernel driver in use: i915
2251 </pre
></p
>
2253 <p
>The resulting intel_quirks entry would then look like this:
</p
>
2255 <p
><pre
>
2256 struct intel_quirk intel_quirks[] = {
2258 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2259 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
2262 </pre
></p
>
2264 <p
>According to the kernel module instructions (as seen using
2265 <tt
>modinfo i915
</tt
>), information about hardware needing the
2266 invert_brightness flag should be sent to the
2267 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
2268 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
2269 developers. But my email about the laptop sent
2013-
06-
03 have not
2271 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
2272 web archive for the mailing list
</a
>, so I suspect they do not accept
2273 emails from non-subscribers. Because of this, I sent my patch also to
2274 the Debian bug tracking system instead as
2275 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
2276 sure the patch is not lost.
</p
>
2278 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
2279 with this problem working properly with Linux. If you use Gnome, your
2280 worries should be over at this point. But if you use KDE, there is
2281 something in KDE ignoring the invert_brightness setting and turning on
2282 the screen during login. I
've reported it to Debian as
2283 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
2284 have no idea yet how to figure out exactly what subsystem is doing
2285 this. Perhaps you can help? Perhaps you know what the Gnome
2286 developers did to handle this, and this can give a clue to the KDE
2287 developers? Or you know where in KDE the screen brightness is changed
2288 during login? If so, please update the BTS report (or get in touch if
2289 you do not know how to update BTS).
</p
>
2291 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
2292 acpi_backlight=vendor, to disable ACPI backlight support completely,
2293 as the ACPI information on the machine is trash and it is better to
2294 leave it to the intel video driver to control the screen
2295 backlight.
</p
>
2300 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
2301 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
2302 <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>
2303 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
2304 <description><p
>Two days ago, I asked
2305 <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
2306 I could install Linux on a Packard Bell EasyNote LV computer
2307 preinstalled with Windows
8</a
>. I found a solution, but am horrified
2308 with the obstacles put in the way of Linux users on a laptop with UEFI
2309 and Windows
8.
</p
>
2311 <p
>I never found out if the cause of my problems were the use of UEFI
2312 secure booting or fast boot. I suspect fast boot was the problem,
2313 causing the firmware to boot directly from HD without considering any
2314 key presses and alternative devices, but do not know UEFI settings
2315 enough to tell.
</p
>
2317 <p
>There is no way to install Linux on the machine in question without
2318 opening the box and disconnecting the hard drive! This is as far as I
2319 can tell, the only way to get access to the firmware setup menu
2320 without accepting the Windows
8 license agreement. I am told (and
2321 found description on how to) that it is possible to configure the
2322 firmware setup once booted into Windows
8. But as I believe the terms
2323 of that agreement are completely unacceptable, accepting the license
2324 was never an alternative. I do not enter agreements I do not intend
2325 to follow.
</p
>
2327 <p
>I feared I had to return the laptops and ask for a refund, and
2328 waste many hours on this, but luckily there was a way to get it to
2329 work. But I would not recommend it to anyone planning to run Linux on
2330 it, and I have become sceptical to Windows
8 certified laptops. Is
2331 this the way Linux will be forced out of the market place, by making
2332 it close to impossible for
"normal
" users to install Linux without
2333 accepting the Microsoft Windows license terms? Or at least not
2334 without risking to loose the warranty?
</p
>
2336 <p
>I
've updated the
2337 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
2338 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
2339 do not have to struggle as much as I did to get Linux into the
2342 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2343 Michael Tokarev and others for feedback and ideas.
</p
>
2348 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
2349 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
2350 <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>
2351 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
2352 <description><p
>I
've run into quite a problem the last few days. I bought three
2353 new laptops for my parents and a few others. I bought Packard Bell
2354 Easynote LV to run Kubuntu on and use as their home computer. But I
2355 am completely unable to figure out how to install Linux on it. The
2356 computer is preinstalled with Windows
8, and I suspect it uses UEFI
2357 instead of a BIOS to boot.
</p
>
2359 <p
>The problem is that I am unable to get it to PXE boot, and unable
2360 to get it to boot the Linux installer from my USB stick. I have yet
2361 to try the DVD install, and still hope it will work. when I turn on
2362 the computer, there is no information on what buttons to press to get
2363 the normal boot menu. I expect to get some boot menu to select PXE or
2364 USB stick booting. When booting, it first ask for the language to
2365 use, then for some regional settings, and finally if I will accept the
2366 Windows
8 terms of use. As these terms are completely unacceptable to
2367 me, I have no other choice but to turn off the computer and try again
2368 to get it to boot the Linux installer.
</p
>
2370 <p
>I have gathered my findings so far on a Linlap page about the
2371 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
2372 EasyNote LV
</a
> model. If you have any idea how to get Linux
2373 installed on this machine, please get in touch or update that wiki
2374 page. If I can
't find a way to install Linux, I will have to return
2375 the laptop to the seller and find another machine for my parents.
</p
>
2377 <p
>I wonder, is this the way Linux will be forced out of the market
2378 using UEFI and
"secure boot
" by making it impossible to install Linux
2379 on new Laptops?
</p
>
2384 <title>How to transform a Debian based system to a Debian Edu installation
</title>
2385 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
2386 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
2387 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
2388 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
2389 an operating system based on Debian intended for use in schools. It
2390 contain a turn-key solution for the computer network provided to
2391 pupils in the primary schools. It provide both the central server,
2392 network boot servers and desktop environments with heaps of
2393 educational software. The project was founded almost
12 years ago,
2394 2001-
07-
02. If you want to support the project, which is in need for
2395 cash to fund developer gatherings and other project related activity,
2396 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
2397 donate some money
</a
>.
2399 <p
>A topic that come up again and again on the Debian Edu mailing
2400 lists and elsewhere, is the question on how to transform a Debian or
2401 Ubuntu installation into a Debian Edu installation. It isn
't very
2402 hard, and last week I wrote a script to replicate the steps done by
2403 the Debian Edu installer.
</p
>
2405 <p
>The script,
2406 <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/
>
2407 in the debian-edu-config package, will go through these six steps and
2408 transform an existing Debian Wheezy or Ubuntu (untested) installation
2409 into a Debian Edu Workstation:
</p
>
2413 <li
>Add skolelinux related APT sources.
</li
>
2414 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
2415 <li
>Install debian-edu-install to load preseeding values and pull in
2416 our configuration.
</li
>
2417 <li
>Preseed debconf database with profile setup in
2418 /etc/debian-edu/config, and run tasksel to install packages
2419 according to the profile specified in the config above,
2420 overriding some of the Debian automation machinery.
</li
>
2421 <li
>Run debian-edu-cfengine-D installation to configure everything
2422 that could not be done using preseeding.
</li
>
2423 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
2427 <p
>There are some steps in the Debian Edu installation that can not be
2428 replicated like this. Disk partitioning and LVM setup, for example.
2429 So this script just assume there is enough disk space to install all
2430 the needed packages.
</p
>
2432 <p
>The script was created to help a Debian Edu student working on
2433 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
2434 Debian Edu client, and using it he can take the existing
2435 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
2436 transform it into a fully functioning Debian Edu Workstation (or
2437 Roaming Workstation, or whatever :).
</p
>
2439 <p
>The default setting in the script is to create a KDE Workstation.
2440 If a LXDE based Roaming workstation is wanted instead, modify the
2441 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
2443 <p
><pre
>
2444 PROFILE=
"Roaming-Workstation
"
2445 DESKTOP=
"lxde
"
2446 </pre
></p
>
2448 <p
>The script could even become useful to set up Debian Edu servers in
2449 the cloud, by starting with a virtual Debian installation at some
2450 virtual hosting service and setting up all the services on first
2456 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
2457 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
2458 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
2459 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
2460 <description><P
>In January,
2461 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
2462 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
2463 channel #debian-lego
</a
>, for those of us in the Debian and Linux
2464 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
2465 marvellous construction system from Denmark. We also created
2466 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
2467 a place to take notes and write down our plans and hopes. And several
2468 people showed up to help. I was very happy to see the effect of my
2469 call. Since the small start, we have a debtags tag
2470 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
2471 tag for LEGO related packages, and now count
10 packages related to
2472 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
2474 <p
><table
>
2475 <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
>
2476 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
2477 <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
>
2478 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
2479 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
2480 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
2481 <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
>
2482 <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
>
2483 <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
>
2484 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
2485 </table
></p
>
2487 <p
>Some of these are available in Wheezy, and all but one are
2488 currently available in Jessie/testing. leocad is so far only
2489 available in experimental.
</p
>
2491 <p
>If you care about LEGO in Debian, please join us on IRC and help
2492 adding the rest of the great free software tools available on Linux
2493 for LEGO designers.
</p
>
2498 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
2499 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
2500 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
2501 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
2502 <description><p
>When I woke up this morning, I was very happy to see that the
2503 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
2504 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
2505 Debian release, and I expect to move my machines at home over to it fairly
2508 <p
>The new debian release contain heaps of new stuff, and one program
2509 in particular make me very happy to see included. The
2510 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
2511 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
2512 included for the first time. Alongside similar programs like
2513 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
2514 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
2515 it allow for visual programming where syntax errors can not happen,
2516 and a friendly programming environment for learning to control the
2517 computer. Scratch will also be included in the next release of Debian
2520 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
2521 Edu/Skolelinux release too. The
2522 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
2523 alpha release
</a
> went out last week, and the next should soon
2529 <title>Isenkram
0.2 finally in the Debian archive
</title>
2530 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
2531 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
2532 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
2533 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
2534 package
</a
> finally made it into the archive, after lingering in NEW
2535 for many months. I uploaded it to the Debian experimental suite
2536 2013-
01-
27, and today it was accepted into the archive.
</p
>
2538 <p
>Isenkram is a system for suggesting to users what packages to
2539 install to work with a pluggable hardware device. The suggestion pop
2540 up when the device is plugged in. For example if a Lego Mindstorm NXT
2541 is inserted, it will suggest to install the program needed to program
2542 the NXT controller. Give it a go, and report bugs and suggestions to
2548 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
2549 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
2550 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
2551 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
2552 <description><p
>My
2553 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
2554 bitcoin related blog post
</a
> mentioned that the new
2555 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
2556 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
2557 2013-
01-
19, and have been available in unstable since then. It was
2558 automatically copied to Ubuntu, and is available in their Raring
2559 version too.
</p
>
2561 <p
>But there is a strange problem with the build that block this new
2562 version from being available on the i386 and kfreebsd-i386
2563 architectures. For some strange reason, the autobuilders in Debian
2564 for these architectures fail to run the test suite on these
2565 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
2566 We are so far unable to reproduce it when building it manually, and
2567 no-one have been able to propose a fix. If you got an idea what is
2568 failing, please let us know via the BTS.
</p
>
2570 <p
>One feature that is annoying me with of the bitcoin client, because
2571 I often run low on disk space, is the fact that the client will exit
2572 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
2573 #
696715</a
>). So make sure you have enough disk space when you run
2576 <p
>As usual, if you use bitcoin and want to show your support of my
2577 activities, please send Bitcoin donations to my address
2578 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2583 <title>Welcome to the world, Isenkram!
</title>
2584 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
2585 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
2586 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
2587 <description><p
>Yesterday, I
2588 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
2589 for testers
</a
> for my prototype for making Debian better at handling
2590 pluggable hardware devices, which I
2591 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
2592 out to create
</a
> earlier this month. Several valuable testers showed
2593 up, and caused me to really want to to open up the development to more
2594 people. But before I did this, I want to come up with a sensible name
2595 for this project. Today I finally decided on a new name, and I have
2596 renamed the project from hw-support-handler to this new name. In the
2597 process, I moved the source to git and made it available as a
2598 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
2599 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
2600 To fetch and build the latest version of the source, use
</p
>
2603 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
2604 cd isenkram
&& git-buildpackage -us -uc
2607 <p
>I have not yet adjusted all files to use the new name yet. If you
2608 want to hack on the source or improve the package, please go ahead.
2609 But please talk to me first on IRC or via email before you do major
2610 changes, to make sure we do not step on each others toes. :)
</p
>
2612 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
2613 stuff, typically meaning tools, nails, screws, etc. Typical hardware
2614 stuff, in other words. I
've been told it is the Norwegian variant of
2615 the German word eisenkram, for those that are familiar with that
2618 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
2619 instructions, to avoid confusing people with an error from the signing
2622 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
2623 clone argument to avoid the need for authentication.
</p
>
2628 <title>First prototype ready making hardware easier to use in Debian
</title>
2629 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
2630 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
2631 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
2632 <description><p
>Early this month I set out to try to
2633 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
2634 the Debian support for pluggable hardware devices
</a
>. Now my
2635 prototype is working, and it is ready for a larger audience. To test
2637 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
2638 from the Debian Edu subversion repository
</a
>, build and install the
2639 package. You might have to log out and in again activate the
2640 autostart script.
</p
>
2642 <p
>The design is simple:
</p
>
2646 <li
>Add desktop entry in /usr/share/autostart/ causing a program
2647 hw-support-handlerd to start when the user log in.
</li
>
2649 <li
>This program listen for kernel events about new hardware (directly
2650 from the kernel like udev does), not using HAL dbus events as I
2651 initially did.
</li
>
2653 <li
>When new hardware is inserted, look up the hardware modalias in
2654 the APT database, a database
2655 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
2656 via HTTP
</a
> and a database available as part of the package.
</li
>
2658 <li
>If a package is mapped to the hardware in question, the package
2659 isn
't installed yet and this is the first time the hardware was
2660 plugged in, show a desktop notification suggesting to install the
2661 package or packages.
</li
>
2663 <li
>If the user click on the
'install package now
' button, ask
2664 aptdaemon via the PackageKit API to install the requrired package.
</li
>
2666 <li
>aptdaemon ask for root password or sudo password, and install the
2667 package while showing progress information in a window.
</li
>
2671 <p
>I still need to come up with a better name for the system. Here
2672 are some screen shots showing the prototype in action. First the
2673 notification, then the password request, and finally the request to
2674 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
2676 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
2677 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
2678 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
2679 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
2680 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
2682 <p
>The prototype still need to be improved with longer timeouts, but
2683 is already useful. The database of hardware to package mappings also
2684 need more work. It is currently compatible with the Ubuntu way of
2685 storing such information in the package control file, but could be
2686 changed to use other formats instead or in addition to the current
2687 method. I
've dropped the use of discover for this mapping, as the
2688 modalias approach is more flexible and easier to use on Linux as long
2689 as the Linux kernel expose its modalias strings directly.
</p
>
2691 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
2692 here is the command required to check out and build the source: Use
2693 '<tt
>svn checkout
2694 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
2695 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
2696 devscripts package.
</p
>
2698 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
2699 renamed to Isenkram and the source moved from the Debian Edu
2700 subversion repository to a Debian collab-maint git repository. See
2701 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
2702 instructions
</a
> for details.
</p
>
2707 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
2708 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
2709 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
2710 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
2711 <description><p
>This Christmas my trusty old laptop died. It died quietly and
2712 suddenly in bed. With a quiet whimper, it went completely quiet and
2713 black. The power button was no longer able to turn it on. It was a
2714 IBM Thinkpad X41, and the best laptop I ever had. Better than both
2715 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
2716 Compaq I had before that. Now I need to find a replacement. To keep
2717 going during Christmas, I moved the one year old SSD disk to my old
2718 X40 where it fitted (only one I had left that could use it), but it is
2719 not a durable solution.
2721 <p
>My laptop needs are fairly modest. This is my wishlist from when I
2722 got a new one more than
10 years ago. It still holds true.:)
</p
>
2726 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
2727 than A4).
</li
>
2728 <li
>Robust, it will be in my backpack every day.
</li
>
2729 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
2730 <li
>Long battery life time. Preferable a week.
</li
>
2731 <li
>Internal WIFI network card.
</li
>
2732 <li
>Internal Twisted Pair network card.
</li
>
2733 <li
>Some USB slots (
2-
3 is plenty)
</li
>
2734 <li
>Good keyboard - similar to the Thinkpad.
</li
>
2735 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
2737 <li
>Hardware supported by Debian Stable, ie the default kernel and
2738 X.org packages.
</li
>
2739 <li
>Quiet, preferably fan free (or at least not using the fan most of
2744 <p
>You will notice that there are no RAM and CPU requirements in the
2745 list. The reason is simply that the specifications on laptops the
2746 last
10-
15 years have been sufficient for my needs, and I have to look
2747 at other features to choose my laptop. But are there still made as
2748 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
2749 robust, and Thinkpads seem to be heading in the wrong direction since
2750 Lenovo took over. But I
've been told that X220 and X1 Carbon might
2751 still be useful.
</p
>
2753 <p
>Perhaps I should rethink my needs, and look for a pad with an
2754 external keyboard? I
'll have to check the
2755 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
2756 well-supported laptops, or perhaps just buy one preinstalled from one
2757 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
2758 Pre-loaded site
</a
>.
</p
>
2763 <title>How to find a browser plugin supporting a given MIME type
</title>
2764 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
2765 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
2766 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
2767 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
2768 install to get support for a given MIME type. Thanks to
2769 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
2770 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
2771 Unfortunately, not very many packages provide the needed meta
2772 information, Anyway, here is a small script to look up all browser
2773 plugin packages announcing ther MIME support using this specification:
</p
>
2779 def pkgs_handling_mimetype(mimetype):
2784 version = pkg.candidate
2786 version = pkg.installed
2789 record = version.record
2790 if not record.has_key(
'Npp-MimeType
'):
2792 mime_types = record[
'Npp-MimeType
'].split(
',
')
2793 for t in mime_types:
2794 t = t.rstrip().strip()
2796 thepkgs.append(pkg.name)
2798 mimetype =
"audio/ogg
"
2799 if
1 < len(sys.argv):
2800 mimetype = sys.argv[
1]
2801 print
"Browser plugin packages supporting %s:
" % mimetype
2802 for pkg in pkgs_handling_mimetype(mimetype):
2803 print
" %s
" %pkg
2806 <p
>It can be used like this to look up a given MIME type:
</p
>
2809 % ./apt-find-browserplug-for-mimetype
2810 Browser plugin packages supporting audio/ogg:
2812 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
2813 Browser plugin packages supporting application/x-shockwave-flash:
2814 browser-plugin-gnash
2818 <p
>In Ubuntu this mechanism is combined with support in the browser
2819 itself to query for plugins and propose to install the needed
2820 packages. It would be great if Debian supported such feature too. Is
2821 anyone working on adding it?
</p
>
2823 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
2824 request for icweasel support for this feature is
2825 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
2826 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
2827 of manpower and wish for a different design is the reason thus feature
2828 is not yet in iceweasel from Debian.
</p
>
2833 <title>What is the most supported MIME type in Debian?
</title>
2834 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
2835 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
2836 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
2837 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
2838 proposal to add AppStream information to the Debian archive
</a
>, is a
2839 proposal to make it possible for a Desktop application to propose to
2840 the user some package to install to gain support for a given MIME
2841 type, font, library etc. that is currently missing. With such
2842 mechanism in place, it would be possible for the desktop to
2843 automatically propose and install leocad if some LDraw file is
2844 downloaded by the browser.
</p
>
2846 <p
>To get some idea about the current content of the archive, I decided
2847 to write a simple program to extract all .desktop files from the
2848 Debian archive and look up the claimed MIME support there. The result
2850 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
2851 site
</a
>. Using the collected information, it become possible to
2852 answer the question in the title. Here are the
20 most supported MIME
2853 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
2854 The complete list is available from the link above.
</p
>
2856 <p
><strong
>Debian Stable:
</strong
></p
>
2860 ----- -----------------------
2876 18 application/x-ogg
2883 <p
><strong
>Debian Testing:
</strong
></p
>
2887 ----- -----------------------
2903 18 application/x-ogg
2910 <p
><strong
>Debian Unstable:
</strong
></p
>
2914 ----- -----------------------
2931 18 application/x-ogg
2937 <p
>I am told that PackageKit can provide an API to access the kind of
2938 information mentioned in DEP-
11. I have not yet had time to look at
2939 it, but hope the PackageKit people in Debian are on top of these
2942 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
2943 discovering a typo in my script.
</p
>
2948 <title>Using modalias info to find packages handling my hardware
</title>
2949 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
2950 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
2951 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
2952 <description><p
>Yesterday, I wrote about the
2953 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
2954 values provided by the Linux kernel
</a
> following my hope for
2955 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
2956 dongle support in Debian
</a
>. Using this knowledge, I have tested how
2957 modalias values attached to package names can be used to map packages
2958 to hardware. This allow the system to look up and suggest relevant
2959 packages when I plug in some new hardware into my machine, and replace
2960 discover and discover-data as the database used to map hardware to
2963 <p
>I create a modaliases file with entries like the following,
2964 containing package name, kernel module name (if relevant, otherwise
2965 the package name) and globs matching the relevant hardware
2968 <p
><blockquote
>
2969 Package: package-name
2970 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
2971 </blockquote
></p
>
2973 <p
>It is fairly trivial to write code to find the relevant packages
2974 for a given modalias value using this file.
</p
>
2976 <p
>An entry like this would suggest the video and picture application
2977 cheese for many USB web cameras (interface bus class
0E01):
</p
>
2979 <p
><blockquote
>
2981 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
2982 </blockquote
></p
>
2984 <p
>An entry like this would suggest the pcmciautils package when a
2985 CardBus bridge (bus class
0607) PCI device is present:
</p
>
2987 <p
><blockquote
>
2988 Package: pcmciautils
2989 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
2990 </blockquote
></p
>
2992 <p
>An entry like this would suggest the package colorhug-client when
2993 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
2995 <p
><blockquote
>
2996 Package: colorhug-client
2997 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
2998 </blockquote
></p
>
3000 <p
>I believe the format is compatible with the format of the Packages
3001 file in the Debian archive. Ubuntu already uses their Packages file
3002 to store their mappings from packages to hardware.
</p
>
3004 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
3005 announce the hardware it support in a way my prototype understand.
3006 This allow those publishing packages in an APT source outside the
3007 Debian archive as well as those backporting packages to make sure the
3008 hardware mapping are included in the package meta information. I
've
3009 tested such header in the pymissile package, and its modalias mapping
3010 is working as it should with my prototype. It even made it to Ubuntu
3013 <p
>To test if it was possible to look up supported hardware using only
3014 the shell tools available in the Debian installer, I wrote a shell
3015 implementation of the lookup code. The idea is to create files for
3016 each modalias and let the shell do the matching. Please check out and
3018 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
3019 shell script. It run without any extra dependencies and fetch the
3020 hardware mappings from the Debian archive and the subversion
3021 repository where I currently work on my prototype.
</p
>
3023 <p
>When I use it on a machine with a yubikey inserted, it suggest to
3024 install yubikey-personalization:
</p
>
3026 <p
><blockquote
>
3027 % ./hw-support-lookup
3028 <br
>yubikey-personalization
3030 </blockquote
></p
>
3032 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3033 propose to install the pcmciautils package:
</p
>
3035 <p
><blockquote
>
3036 % ./hw-support-lookup
3037 <br
>pcmciautils
3039 </blockquote
></p
>
3041 <p
>If you know of any hardware-package mapping that should be added to
3042 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
3043 database
</a
>, please tell me about it.
</p
>
3045 <p
>It could be possible to generate several of the mappings between
3046 packages and hardware. One source would be to look at packages with
3047 kernel modules, ie packages with *.ko files in /lib/modules/, and
3048 extract their modalias information. Another would be to look at
3049 packages with udev rules, ie packages with files in
3050 /lib/udev/rules.d/, and extract their vendor/model information to
3051 generate a modalias matching rule. I have not tested any of these to
3052 see if it work.
</p
>
3054 <p
>If you want to help implementing a system to let us propose what
3055 packages to install when new hardware is plugged into a Debian
3056 machine, please send me an email or talk to me on
3057 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
3062 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
3063 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
3064 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
3065 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
3066 <description><p
>While looking into how to look up Debian packages based on hardware
3067 information, to find the packages that support a given piece of
3068 hardware, I refreshed my memory regarding modalias values, and decided
3069 to document the details. Here are my findings so far, also available
3071 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
3072 Debian Edu subversion repository
</a
>:
3074 <p
><strong
>Modalias decoded
</strong
></p
>
3076 <p
>This document try to explain what the different types of modalias
3077 values stands for. It is in part based on information from
3078 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
3079 &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;,
3080 &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
3081 &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;.
3083 <p
>The modalias entries for a given Linux machine can be found using
3084 this shell script:
</p
>
3087 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
3090 <p
>The supported modalias globs for a given kernel module can be found
3091 using modinfo:
</p
>
3094 % /sbin/modinfo psmouse | grep alias:
3095 alias: serio:ty05pr*id*ex*
3096 alias: serio:ty01pr*id*ex*
3100 <p
><strong
>PCI subtype
</strong
></p
>
3102 <p
>A typical PCI entry can look like this. This is an Intel Host
3103 Bridge memory controller:
</p
>
3105 <p
><blockquote
>
3106 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3107 </blockquote
></p
>
3109 <p
>This represent these values:
</p
>
3114 sv
00001028 (subvendor)
3115 sd
000001AD (subdevice)
3117 sc
00 (bus subclass)
3121 <p
>The vendor/device values are the same values outputted from
'lspci
3122 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
3123 0600. The
0600 class is a host bridge. Other useful bus values are
3124 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
3126 <p
>Not sure how to figure out the interface value, nor what it
3129 <p
><strong
>USB subtype
</strong
></p
>
3131 <p
>Some typical USB entries can look like this. This is an internal
3132 USB hub in a laptop:
</p
>
3134 <p
><blockquote
>
3135 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3136 </blockquote
></p
>
3138 <p
>Here is the values included in this alias:
</p
>
3141 v
1D6B (device vendor)
3142 p
0001 (device product)
3144 dc
09 (device class)
3145 dsc
00 (device subclass)
3146 dp
00 (device protocol)
3147 ic
09 (interface class)
3148 isc
00 (interface subclass)
3149 ip
00 (interface protocol)
3152 <p
>The
0900 device class/subclass means hub. Some times the relevant
3153 class is in the interface class section. For a simple USB web camera,
3154 these alias entries show up:
</p
>
3156 <p
><blockquote
>
3157 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3158 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3159 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3160 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3161 </blockquote
></p
>
3163 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
3164 camera),
0101 is audio control device and
0102 is audio streaming (aka
3165 microphone). Thus this is a camera with microphone included.
</p
>
3167 <p
><strong
>ACPI subtype
</strong
></p
>
3169 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
3170 receiver in a Thinkpad X40:
</p
>
3172 <p
><blockquote
>
3173 acpi:IBM0071:PNP0511:
3174 </blockquote
></p
>
3176 <p
>The values between the colons are IDs.
</p
>
3178 <p
><strong
>DMI subtype
</strong
></p
>
3180 <p
>The DMI table contain lots of information about the computer case
3181 and model. This is an entry for a IBM Thinkpad X40, fetched from
3182 /sys/devices/virtual/dmi/id/modalias:
</p
>
3184 <p
><blockquote
>
3185 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3186 </blockquote
></p
>
3188 <p
>The values present are
</p
>
3191 bvn IBM (BIOS vendor)
3192 bvr
1UETB
6WW(
1.66) (BIOS version)
3193 bd
06/
15/
2005 (BIOS date)
3194 svn IBM (system vendor)
3195 pn
2371H4G (product name)
3196 pvr ThinkPadX40 (product version)
3197 rvn IBM (board vendor)
3198 rn
2371H4G (board name)
3199 rvr NotAvailable (board version)
3200 cvn IBM (chassis vendor)
3201 ct
10 (chassis type)
3202 cvr NotAvailable (chassis version)
3205 <p
>The chassis type
10 is Notebook. Other interesting values can be
3206 found in the dmidecode source:
</p
>
3210 4 Low Profile Desktop
3223 17 Main Server Chassis
3224 18 Expansion Chassis
3226 20 Bus Expansion Chassis
3227 21 Peripheral Chassis
3229 23 Rack Mount Chassis
3238 <p
>The chassis type values are not always accurately set in the DMI
3239 table. For example my home server is a tower, but the DMI modalias
3240 claim it is a desktop.
</p
>
3242 <p
><strong
>SerIO subtype
</strong
></p
>
3244 <p
>This type is used for PS/
2 mouse plugs. One example is from my
3245 test machine:
</p
>
3247 <p
><blockquote
>
3248 serio:ty01pr00id00ex00
3249 </blockquote
></p
>
3251 <p
>The values present are
</p
>
3260 <p
>This type is supported by the psmouse driver. I am not sure what
3261 the valid values are.
</p
>
3263 <p
><strong
>Other subtypes
</strong
></p
>
3265 <p
>There are heaps of other modalias subtypes according to
3266 file2alias.c. There is the rest of the list from that source: amba,
3267 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3268 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3269 vmbus, x86cpu and zorro. I did not spend time documenting all of
3270 these, as they do not seem relevant for my intended use with mapping
3271 hardware to packages when new stuff is inserted during run time.
</p
>
3273 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
3275 <p
>To check which kernel modules provide support for a given modalias,
3276 one can use the following shell script:
</p
>
3279 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
3280 echo
"$id
" ; \
3281 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
3285 <p
>The output can look like this (only the first few entries as the
3286 list is very long on my test machine):
</p
>
3290 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
3292 FATAL: Module acpi:device: not found.
3294 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
3295 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
3296 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
3297 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3298 acpi:IBM0071:PNP0511:
3299 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
3300 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
3301 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
3305 <p
>If you want to help implementing a system to let us propose what
3306 packages to install when new hardware is plugged into a Debian
3307 machine, please send me an email or talk to me on
3308 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
3310 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
3311 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
3312 in /sys/ with space in them.
</p
>
3317 <title>Moved the pymissile Debian packaging to collab-maint
</title>
3318 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
3319 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
3320 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
3321 <description><p
>As part of my investigation on how to improve the support in Debian
3322 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3323 Launcher and updated the Debian package
3324 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
3325 sure udev will fix the device permissions when it is plugged in. I
3326 also added a
"Modaliases
" header to test it in the Debian archive and
3327 hopefully make the package be proposed by jockey in Ubuntu when a user
3328 plug in his rocket launcher. In the process I moved the source to a
3329 git repository under collab-maint, to make it easier for any DD to
3330 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
3331 is not very active, but the software still work for me even after five
3332 years of relative silence. The new git repository is not listed in
3333 the uploaded package yet, because I want to test the other changes a
3334 bit more before I upload the new version. If you want to check out
3335 the new version with a .desktop file included, visit the
3336 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
3337 view
</a
> or use
"<tt
>git clone
3338 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
3343 <title>Lets make hardware dongles easier to use in Debian
</title>
3344 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
3345 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
3346 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
3347 <description><p
>One thing that annoys me with Debian and Linux distributions in
3348 general, is that there is a great package management system with the
3349 ability to automatically install software packages by downloading them
3350 from the distribution mirrors, but no way to get it to automatically
3351 install the packages I need to use the hardware I plug into my
3352 machine. Even if the package to use it is easily available from the
3353 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3354 suggest to automatically install the python-nxt, nbc and t2n packages
3355 I need to talk to it. When I plug in a Yubikey, it could propose the
3356 yubikey-personalization package. The information required to do this
3357 is available, but no-one have pulled all the pieces together.
</p
>
3359 <p
>Some years ago, I proposed to
3360 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
3361 the discover subsystem to implement this
</a
>. The idea is fairly
3366 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
3367 starting when a user log in.
</li
>
3369 <li
>Set this program up to listen for kernel events emitted when new
3370 hardware is inserted into the computer.
</li
>
3372 <li
>When new hardware is inserted, look up the hardware ID in a
3373 database mapping to packages, and take note of any non-installed
3374 packages.
</li
>
3376 <li
>Show a message to the user proposing to install the discovered
3377 package, and make it easy to install it.
</li
>
3381 <p
>I am not sure what the best way to implement this is, but my
3382 initial idea was to use dbus events to discover new hardware, the
3383 discover database to find packages and
3384 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
3387 <p
>Yesterday, I found time to try to implement this idea, and the
3388 draft package is now checked into
3389 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
3390 Debian Edu subversion repository
</a
>. In the process, I updated the
3391 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
3392 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3393 the relevant packages in Debian, and uploaded a new version
3394 2.2013.01.09 to unstable. I also discovered that the current
3395 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
3396 package in Debian no longer discovered any USB devices, because
3397 /proc/bus/usb/devices is no longer present. I ported it to use
3398 libusb as a fall back option to get it working. The fixed package
3399 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
3400 because of the freeze).
</p
>
3402 <p
>With this prototype in place, I can insert my Yubikey, and get this
3403 desktop notification to show up (only once, the first time it is
3404 inserted):
</p
>
3406 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
3408 <p
>For this prototype to be really useful, some way to automatically
3409 install the proposed packages by pressing the
"Please install
3410 program(s)
" button should to be implemented.
</p
>
3412 <p
>If this idea seem useful to you, and you want to help make it
3413 happen, please help me update the discover-data database with mappings
3414 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
3415 list the package you would like to have installed when a given
3416 hardware device is inserted into your computer, and report bugs using
3417 reportbug if it isn
't. Or, if you know of a better way to provide
3418 such mapping, please let me know.
</p
>
3420 <p
>This prototype need more work, and there are several questions that
3421 should be considered before it is ready for production use. Is dbus
3422 the correct way to detect new hardware? At the moment I look for HAL
3423 dbus events on the system bus, because that is the events I could see
3424 on my Debian Squeeze KDE desktop. Are there better events to use?
3425 How should the user be notified? Is the desktop notification
3426 mechanism the best option, or should the background daemon raise a
3427 popup instead? How should packages be installed? When should they
3428 not be installed?
</p
>
3430 <p
>If you want to help getting such feature implemented in Debian,
3431 please send me an email. :)
</p
>
3436 <title>New IRC channel for LEGO designers using Debian
</title>
3437 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
3438 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
3439 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
3440 <description><p
>During Christmas, I have worked a bit on the Debian support for
3441 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
3442 NXT
</a
>. My son and I have played a bit with my NXT set, and I
3443 discovered I had to build all the tools myself because none were
3444 already in Debian Squeeze. If Debian support for LEGO is something
3445 you care about, please join me on the IRC channel
3446 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
3447 irc.debian.org). There is a lot that could be done to improve the
3448 Debian support for LEGO designers. For example both CAD software
3449 and Mindstorm compilers are missing. :)
</p
>
3451 <p
>Update
2012-
01-
03: A
3452 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
3453 including links to Lego related packages is now available.
</p
>
3458 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
3459 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
3460 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
3461 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
3462 <description><p
>Let me start by wishing you all marry Christmas and a happy new
3463 year! I hope next year will prove to be a good year.
</p
>
3465 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
3466 decentralised
"currency
" that allow people to transfer bitcoins
3467 between each other with minimal overhead, is a very interesting
3468 experiment. And as I wrote a few days ago, the bitcoin situation in
3469 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
3470 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
3471 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
3472 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
3473 for one of the ftpmasters to approve the new bitcoin-qt package
3476 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
3477 team in Debian, you can easily test the package in Debian Squeeze
3478 using the following steps to get a set of working packages:
</p
>
3480 <blockquote
><pre
>
3481 git clone git://git.debian.org/git/collab-maint/bitcoin
3483 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3484 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3485 </pre
></blockquote
>
3487 <p
>You might have to install some build dependencies as well. The
3488 list of commands should give you two packages, bitcoind and
3489 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3490 client will download the complete set of bitcoin
"blocks
", which need
3491 around
5.6 GiB of data on my machine at the moment. Make sure your
3492 ~/.bitcoin/ directory have lots of spare room if you want to download
3493 all the blocks. The client will warn if the disk is getting full, so
3494 there is not really a problem if you got too little room, but you will
3495 not be able to get all the features out of the client.
</p
>
3497 <p
>As usual, if you use bitcoin and want to show your support of my
3498 activities, please send Bitcoin donations to my address
3499 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3504 <title>A word on bitcoin support in Debian
</title>
3505 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
3506 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
3507 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
3508 <description><p
>It has been a while since I wrote about
3509 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
3510 peer-to-peer based crypto-currency, and the reason is simply that I
3511 have been busy elsewhere. But two days ago, I started looking at the
3512 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
3513 Debian
</a
> again to try to recover my old bitcoin wallet. The package
3514 is now maintained by a
3515 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
3516 people
</a
>, and the grunt work had already been done by this team. We
3517 owe a huge thank you to all these team members. :)
3518 But I was sad to discover that the bitcoin client is missing in
3519 Wheezy. It is only available in Sid (and an outdated client from
3520 backports). The client had several RC bugs registered in BTS blocking
3521 it from entering testing. To try to help the team and improve the
3522 situation, I spent some time providing patches and triaging the bug
3523 reports. I also had a look at the bitcoin package available from Matt
3525 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
3526 Ubuntu
</a
>, and moved the useful pieces from that version into the
3527 Debian package.
</p
>
3529 <p
>After checking with the main package maintainer Jonas Smedegaard on
3530 IRC, I pushed several patches into the collab-maint git repository to
3531 improve the package. It now contains fixes for the RC issues (not from
3532 me, but fixed by Scott Howard), build rules for a Qt GUI client
3533 package, konqueror support for the bitcoin: URI and bash completion
3534 setup. As I work on Debian Squeeze, I also created
3535 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
3536 patch to backport
</a
> the latest version. Jonas is going to look at
3537 it and try to integrate it into the git repository before uploading a
3538 new version to unstable.
3540 <p
>I would very much like bitcoin to succeed, to get rid of the
3541 centralized control currently exercised in the monetary system. I
3542 find it completely unacceptable that the USA government is collecting
3543 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
3544 that the major credit card companies can block legal money
3545 transactions to Wikileaks. But for bitcoin to succeed, more people
3546 need to use bitcoins, and more people need to accept bitcoins when
3547 they sell products and services. Improving the bitcoin support in
3548 Debian is a small step in the right direction, but not enough.
3549 Unfortunately the user experience when browsing the web and wanting to
3550 pay with bitcoin is still not very good. The bitcoin: URI is a step
3551 in the right direction, but need to work in most or every browser in
3552 use. Also the bitcoin-qt client is too heavy to fire up to do a
3553 quick transaction. I believe there are other clients available, but
3554 have not tested them.
</p
>
3557 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
3558 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
3559 I received
20.15 BTC so far on the address I provided in my blog two
3560 years ago, as can be
3561 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
3562 on the blockexplorer service
</a
>. Thank you everyone for your
3563 donation. The blockexplorer service demonstrates quite well that
3564 bitcoin is not quite anonymous and untracked. :) I wonder if the
3565 number of users have gone up since then. If you use bitcoin and want
3566 to show your support of my activity, please send Bitcoin donations to
3567 the same address as last time,
3568 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3573 <title>Git repository for song book for Computer Scientists
</title>
3574 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
3575 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
3576 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
3577 <description><p
>As I
3578 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
3579 this summer
</a
>, I have created a Computer Science song book a few
3580 years ago, and today I finally found time to create a public
3581 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
3582 repository for the project
</a
>.
</p
>
3584 <p
>If you want to help out, please clone the source and submit patches
3585 to the HTML version. To generate the PDF and PostScript version,
3586 please use prince XML, or let me know about a useful free software
3587 processor capable of creating a good looking PDF from the HTML.
</p
>
3589 <p
>Want to sing? You can still find the song book in HTML, PDF and
3590 PostScript formats at
3591 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
3592 Science Songbook
</a
>.
</p
>
3597 <title>Gratulerer med
19-årsdagen, Debian!
</title>
3598 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
3599 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
3600 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
3601 <description><p
>I dag fyller
3602 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
3603 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
3604 si gratulerer med dagen, Debian!
</p
>
3609 <title>Song book for Computer Scientists
</title>
3610 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
3611 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
3612 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
3613 <description><p
>Many years ago, while studying Computer Science at the
3614 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
3615 collecting computer related songs for use at parties. The original
3616 version was written in LaTeX, but a few years ago I got help from
3617 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
3618 while keeping the ability to create a nice book in PDF format. I have
3619 not had time to maintain the book for a while now, and guess I should
3620 put it up on some public version control repository where others can
3621 help me extend and update the book. If anyone is volunteering to help
3622 me with this, send me an email. Also let me know if there are songs
3623 missing in my book.
</p
>
3625 <p
>I have not mentioned the book on my blog so far, and it occured to
3626 me today that I really should let all my readers share the joys of
3627 singing out load about programming, computers and computer networks.
3628 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
3629 12</a
> is about to start (and I am not going). Want to sing? Check
3630 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
3631 Computer Science Songbook
</a
>.
3636 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
3637 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
3638 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
3639 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
3640 <description><p
>At work we have heaps of servers. I believe the total count is
3641 around
1000 at the moment. To be able to get help from the vendors
3642 when something go wrong, we want to keep the firmware on the servers
3643 up to date. If the firmware isn
't the latest and greatest, the
3644 vendors typically refuse to start debugging any problems until the
3645 firmware is upgraded. So before every reboot, we want to upgrade the
3646 firmware, and we would really like everyone handling servers at the
3647 university to do this themselves when they plan to reboot a machine.
3648 For that to happen we at the unix server admin group need to provide
3649 the tools to do so.
</p
>
3651 <p
>To make firmware upgrading easier, I am working on a script to
3652 fetch and install the latest firmware for the servers we got. Most of
3653 our hardware are from Dell and HP, so I have focused on these servers
3654 so far. This blog post is about the Dell part.
</P
>
3656 <p
>On the Dell FTP site I was lucky enough to find
3657 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
3658 with firmware information for all
11th generation servers, listing
3659 which firmware should be used on a given model and where on the FTP
3660 site I can find it. Using a simple perl XML parser I can then
3661 download the shell scripts Dell provides to do firmware upgrades from
3662 within Linux and reboot when all the firmware is primed and ready to
3663 be activated on the first reboot.
</p
>
3665 <p
>This is the Dell related fragment of the perl code I am working on.
3666 Are there anyone working on similar tools for firmware upgrading all
3667 servers at a site? Please get in touch and lets share resources.
</p
>
3669 <p
><pre
>
3673 use File::Temp qw(tempdir);
3675 # Install needed RHEL packages if missing
3677 'XML::Simple
' =
> 'perl-XML-Simple
',
3679 for my $module (keys %rhelmodules) {
3680 eval
"use $module;
";
3682 my $pkg = $rhelmodules{$module};
3683 system(
"yum install -y $pkg
");
3684 eval
"use $module;
";
3688 my $errorsto =
'pere@hungry.com
';
3694 sub run_firmware_script {
3695 my ($opts, $script) = @_;
3697 print STDERR
"fail: missing script name\n
";
3700 print STDERR
"Running $script\n\n
";
3702 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
3703 print STDERR
"success: firmware script ran succcessfully\n
";
3705 print STDERR
"fail: firmware script returned error\n
";
3709 sub run_firmware_scripts {
3710 my ($opts, @dirs) = @_;
3711 # Run firmware packages
3712 for my $dir (@dirs) {
3713 print STDERR
"info: Running scripts in $dir\n
";
3714 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
3715 while (my $s = readdir $dh) {
3716 next if $s =~ m/^\.\.?/;
3717 run_firmware_script($opts,
"$dir/$s
");
3725 print STDERR
"info: Downloading $url\n
";
3726 system(
"wget --quiet \
"$url\
"");
3731 my $product = `dmidecode -s system-product-name`;
3734 if ($product =~ m/PowerEdge/) {
3736 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
3737 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
3739 my $tmpdir = tempdir(
3743 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
3744 system(
'gunzip Catalog.xml.gz
');
3745 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
3746 # -q is quiet, disabling interactivity and reducing console output
3747 my $fwopts =
"-q
";
3749 for my $url (@paths) {
3750 fetch_dell_fw($url);
3752 run_firmware_scripts($fwopts, $tmpdir);
3754 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
3755 print STDERR
"error: Please report to $errorsto.\n
";
3759 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
3760 print STDERR
"error: Please report to $errorsto.\n
";
3766 my $url =
"ftp://ftp.us.dell.com/$path
";
3770 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
3771 # firmware packages to download from Dell. Only work for Linux
3772 # machines and
11th generation Dell servers.
3773 sub fetch_dell_fw_list {
3774 my $filename = shift;
3776 my $product = `dmidecode -s system-product-name`;
3778 my ($mybrand, $mymodel) = split(/\s+/, $product);
3780 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
3782 my $xml = XMLin($filename);
3784 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
3785 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
3786 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
3788 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
3789 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
3791 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
3793 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
3795 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
3798 for my $component (@{$xml-
>{SoftwareComponent}}) {
3799 my $componenttype = $component-
>{ComponentType}-
>{value};
3801 # Drop application packages, only firmware and BIOS
3802 next if
'APAC
' eq $componenttype;
3804 my $cpath = $component-
>{path};
3805 for my $path (@paths) {
3806 if ($cpath =~ m%/$path$%) {
3807 push(@paths, $cpath);
3815 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
3816 it could work on other platforms with some tweaking. Anyone know a
3817 index like Catalog.xml is available from HP for HP servers? At the
3818 moment I maintain a similar list manually and it is quickly getting
3824 <title>How is booting into runlevel
1 different from single user boots?
</title>
3825 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
3826 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
3827 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
3828 <description><p
>Wouter Verhelst have some
3829 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
3830 comments and opinions
</a
> on my blog post on
3831 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
3832 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
3833 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
3834 default KDE desktop in Debian
</a
>. I only have time to address one
3835 small piece of his comment now, and though it best to address the
3836 misunderstanding he bring forward:
</p
>
3838 <p
><blockquote
>
3839 Currently, a system admin has four options: [...] boot to a
3840 single-user system (by adding
'single
' to the kernel command line;
3841 this runs rcS and rc1 scripts)
3842 </blockquote
></p
>
3844 <p
>This make me believe Wouter believe booting into single user mode
3845 and booting into runlevel
1 is the same. I am not surprised he
3846 believe this, because it would make sense and is a quite sensible
3847 thing to believe. But because the boot in Debian is slightly broken,
3848 runlevel
1 do not work properly and it isn
't the same as single user
3849 mode. I
'll try to explain what is actually happing, but it is a bit
3850 hard to explain.
</p
>
3852 <p
>Single user mode is defined like this in /etc/inittab:
3853 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
3854 executed in single user mode is sulogin. Single user mode is a boot
3855 state
"between
" the runlevels, and when booting into single user mode,
3856 only the scripts in /etc/rcS.d/ are executed before the init process
3857 enters the single user state. When switching to runlevel
1, the state
3858 is in fact not ending in runlevel
1, but it passes through runlevel
1
3859 and end up in the single user mode (see /etc/rc1.d/S03single, which
3860 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
3861 1. It is confusing that the
'S
' (single user) init mode is not the
3862 mode enabled by /etc/rcS.d/ (which is more like the initial boot
3865 <p
>This summary might make it clearer. When booting for the first
3866 time into single user mode, the following commands are executed:
3867 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
3868 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
3869 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
3870 trying to continue after visiting single user mode. Not all services
3871 are started again as they should, causing the machine to end up in an
3872 unpredicatble state. This is why Debian admins recommend rebooting
3873 after visiting single user mode.
</p
>
3875 <p
>A similar problem with runlevel
1 is caused by the amount of
3876 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
3877 to runlevel
1, the services started from /etc/rcS.d/ are not properly
3878 stopped when passing through the scripts in /etc/rc1.d/, and not
3879 started again when switching away from runlevel
1 to the runlevels
3880 2-
5. I believe the problem is best fixed by moving all the scripts
3881 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
3882 functioning single user mode during boot.
</p
>
3884 <p
>I have spent several years investigating the Debian boot system,
3885 and discovered this problem a few years ago. I suspect it originates
3886 from when sysvinit was introduced into Debian, a long time ago.
</p
>
3891 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
3892 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
3893 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
3894 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
3895 <description><p
>In the Debian boot system, several packages include scripts that
3896 are started from /etc/rcS.d/. In fact, there is a bite more of them
3897 than make sense, and this causes a few problems. What kind of
3898 problems, you might ask. There are at least two problems. The first
3899 is that it is not possible to recover a machine after switching to
3900 runlevel
1. One need to actually reboot to get the machine back to
3901 the expected state. The other is that single user boot will sometimes
3902 run into problems because some of the subsystems are activated before
3903 the root login is presented, causing problems when trying to recover a
3904 machine from a problem in that subsystem. A minor additional point is
3905 that moving more scripts out of rcS.d/ and into the other rc#.d/
3906 directories will increase the amount of scripts that can run in
3907 parallel during boot, and thus decrease the boot time.
</p
>
3909 <p
>So, which scripts should start from rcS.d/. In short, only the
3910 scripts that _have_ to execute before the root login prompt is
3911 presented during a single user boot should go there. Everything else
3912 should go into the numeric runlevels. This means things like
3913 lm-sensors, fuse and x11-common should not run from rcS.d, but from
3914 the numeric runlevels. Today in Debian, there are around
115 init.d
3915 scripts that are started from rcS.d/, and most of them should be moved
3916 out. Do your package have one of them? Please help us make single
3917 user and runlevel
1 better by moving it.
</p
>
3919 <p
>Scripts setting up the screen, keyboard, system partitions
3920 etc. should still be started from rcS.d/, but there is for example no
3921 need to have the network enabled before the single user login prompt
3922 is presented.
</p
>
3924 <p
>As always, things are not so easy to fix as they sound. To keep
3925 Debian systems working while scripts migrate and during upgrades, the
3926 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
3927 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
3928 and the next ones can only be moved when their dependencies have been
3929 moved first. This migration must be done sequentially while we ensure
3930 that the package system upgrade packages in the right order to keep
3931 the system state correct. This will require some coordination when it
3932 comes to network related packages, but most of the packages with
3933 scripts that should migrate do not have anything in rcS.d/ depending
3934 on them. Some packages have already been updated, like the sudo
3935 package, while others are still left to do. I wish I had time to work
3936 on this myself, but real live constrains make it unlikely that I will
3937 find time to push this forward.
</p
>
3942 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
3943 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
3944 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
3945 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
3946 <description><p
>While at Debconf11, I have several times during discussions
3947 mentioned the issues I believe should be improved in Debian for its
3948 desktop to be useful for more people. The use case for this is my
3949 parents, which are currently running Kubuntu which solve the
3952 <p
>I suspect these four missing features are not very hard to
3953 implement. After all, they are present in Ubuntu, so if we wanted to
3954 do this in Debian we would have a source.
</p
>
3958 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
3959 are new packages available for upgrades, a icon in the KDE status bar
3960 indicate this, and clicking on it will activate the simple upgrade
3961 tool to handle it. I have no problem guiding both of my parents
3962 through the process over the phone. If a kernel reboot is required,
3963 this too is indicated by the status bars and the upgrade tool. Last
3964 time I checked, nothing with the same features was working in KDE in
3967 <li
><strong
>Simple handling of missing Firefox browser
3968 plugins.
</strong
> When the browser encounter a MIME type it do not
3969 currently have a handler for, it will ask the user if the system
3970 should search for a package that would add support for this MIME type,
3971 and if the user say yes, the APT sources will be searched for packages
3972 advertising the MIME type in their control file (visible in the
3973 Packages file in the APT archive). If one or more packages are found,
3974 it is a simple click of the mouse to add support for the missing mime
3975 type. If the package require the user to accept some non-free
3976 license, this is explained to the user. The entire process make it
3977 more clear to the user why something do not work in the browser, and
3978 make the chances higher for the user to blame the web page authors and
3979 not the browser for any missing features.
</li
>
3981 <li
><strong
>Simple handling of missing multimedia codec/format
3982 handlers.
</strong
> When the media players encounter a format or codec
3983 it is not supporting, a dialog pop up asking the user if the system
3984 should search for a package that would add support for it. This
3985 happen with things like MP3, Windows Media or H
.264. The selection
3986 and installation procedure is very similar to the Firefox browser
3987 plugin handling. This is as far as I know implemented using a
3988 gstreamer hook. The end result is that the user easily get access to
3989 the codecs that are present from the APT archives available, while
3990 explaining more on why a given format is unsupported by Ubuntu.
</li
>
3992 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
3993 displaying a text/plain file in my Debian browser, it will propose to
3994 start emacs to show it. If I remember correctly, when doing the same
3995 in Kunbutu it show the file as a text file in the browser. At least I
3996 know Opera will show text files within the browser. I much prefer the
3997 latter behaviour.
</li
>
4001 <p
>There are other nice features as well, like the simplified suite
4002 upgrader, but given that I am the one mostly doing the dist-upgrade,
4003 it do not matter much.
</p
>
4005 <p
>I really hope we could get these features in place for the next
4006 Debian release. It would require the coordinated effort of several
4007 maintainers, but would make the end user experience a lot better.
</p
>
4012 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
4013 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
4014 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
4015 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
4016 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
4017 site is build on Debian/Squeeze, and this platform was chosen because
4018 I am most familiar with Debian (being a Debian Developer for around
10
4019 years) because it is the latest stable Debian release which should get
4020 security support for a few years.
</p
>
4022 <p
>The web service is written in Perl, and depend on some perl modules
4023 that are missing in Debian at the moment. It would be great if these
4024 modules were added to the Debian archive, allowing anyone to set up
4025 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
4026 in their own country using only Debian packages. The list of modules
4027 missing in Debian/Squeeze isn
't very long, and I hope the perl group
4028 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
4029 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4030 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4031 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4032 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4033 easier in the future.
</p
>
4035 <p
>Thanks to the great tools in Debian, getting the missing modules
4036 installed on my server was a simple call to
'cpan2deb Module::Name
'
4037 and
'dpkg -i
' to install the resulting package. But this leave me
4038 with the responsibility of tracking security problems, which I really
4039 do not have time for.
</p
>
4044 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
4045 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
4046 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
4047 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
4048 <description><p
>Here is a small update for my English readers. Most of my blog
4049 posts have been in Norwegian the last few weeks, so here is a short
4050 update in English.
</p
>
4052 <p
>The kids still keep me too busy to get much free software work
4053 done, but I did manage to organise a project to get a Norwegian port
4054 of the British service
4055 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
4056 and it has been running for a month now. The entire project has been
4057 organised by me and two others. Around Christmas we gathered sponsors
4058 to fund the development work. In January I drafted a contract with
4059 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
4060 and in February the development took place. Most of it involved
4061 converting the source to use GPS coordinates instead of British
4062 easting/northing, and the resulting code should be a lot easier to get
4063 running in any country by now. The Norwegian
4064 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
4065 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
4066 source and the source for administrative borders in Norway, and
4067 support for this had to be added/fixed.
</p
>
4069 <p
>The Norwegian version went live March
3th, and we spent the weekend
4070 polishing the system before we announced it March
7th. The system is
4071 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
4072 problem reports in a few weeks. Soon we hope to announce the Android
4073 and iPhone versions making it even easier to report problems with the
4074 public infrastructure.
</p
>
4076 <p
>Perhaps something to consider for those of you in countries without
4077 such service?
</p
>
4082 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
4083 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
4084 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
4085 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
4086 <description><p
>The last few days I have looked at ways to track open security
4087 issues here at my work with the University of Oslo. My idea is that
4088 it should be possible to use the information about security issues
4089 available on the Internet, and check our locally
4090 maintained/distributed software against this information. It should
4091 allow us to verify that no known security issues are forgotten. The
4092 CVE database listing vulnerabilities seem like a great central point,
4093 and by using the package lists from Debian mapped to CVEs provided by
4094 the testing security team, I believed it should be possible to figure
4095 out which security holes were present in our free software
4096 collection.
</p
>
4098 <p
>After reading up on the topic, it became obvious that the first
4099 building block is to be able to name software packages in a unique and
4100 consistent way across data sources. I considered several ways to do
4101 this, for example coming up with my own naming scheme like using URLs
4102 to project home pages or URLs to the Freshmeat entries, or using some
4103 existing naming scheme. And it seem like I am not the first one to
4104 come across this problem, as MITRE already proposed and implemented a
4105 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
4106 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
4107 software, hardware and other platform components. The CPE ids are
4108 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
4109 Vulnerability Database
</a
>, allowing me to look up know security
4110 issues for any CPE name. With this in place, all I need to do is to
4111 locate the CPE id for the software packages we use at the university.
4112 This is fairly trivial (I google for
'cve cpe $package
' and check the
4113 NVD entry if a CVE for the package exist).
</p
>
4115 <p
>To give you an example. The GNU gzip source package have the CPE
4116 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
4117 check out, one could look up
4118 <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
4119 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
4120 The most recent one is
4121 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
4122 and at the bottom of the NVD page for this vulnerability the complete
4123 list of affected versions is provided.
</p
>
4125 <p
>The NVD database of CVEs is also available as a XML dump, allowing
4126 for offline processing of issues. Using this dump, I
've written a
4127 small script taking a list of CPEs as input and list all CVEs
4128 affecting the packages represented by these CPEs. One give it CPEs
4129 with version numbers as specified above and get a list of open
4130 security issues out.
</p
>
4132 <p
>Of course for this approach to be useful, the quality of the NVD
4133 information need to be high. For that to happen, I believe as many as
4134 possible need to use and contribute to the NVD database. I notice
4136 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
4137 map from CVE to CPE
</a
>, indicating that they are using the CPE
4138 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
4140 <p
>To get an idea about the quality for free software, I spent some
4141 time making it possible to compare the CVE database from Debian with
4142 the CVE database in NVD. The result look fairly good, but there are
4143 some inconsistencies in NVD (same software package having several
4144 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4145 Debian believe are affected by a CVE). Hope to find time to improve
4146 the quality of NVD, but that require being able to get in touch with
4147 someone maintaining it. So far my three emails with questions and
4148 corrections have not seen any reply, but I hope contact can be
4149 established soon.
</p
>
4151 <p
>An interesting application for CPEs is cross platform package
4152 mapping. It would be useful to know which packages in for example
4153 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4154 this would be trivial if all linux distributions provided CPE entries
4155 for their packages.
</p
>
4160 <title>Which module is loaded for a given PCI and USB device?
</title>
4161 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
4162 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
4163 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
4164 <description><p
>In the
4165 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
4166 package in Debian, there is a script to report useful information
4167 about the running hardware for use when people report missing
4168 information. One part of this script that I find very useful when
4169 debugging hardware problems, is the part mapping loaded kernel module
4170 to the PCI device it claims. It allow me to quickly see if the kernel
4171 module I expect is driving the hardware I am struggling with. To see
4172 the output, make sure discover-data is installed and run
4173 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
4174 one of my machines like this:
</p
>
4178 10de:
03eb i2c_nforce2
4181 10de:
03f0 snd_hda_intel
4190 <p
>The code in question look like this, slightly modified for
4191 readability and to drop the output to file descriptor
3:
</p
>
4194 if [ -d /sys/bus/pci/devices/ ] ; then
4195 echo loaded pci modules:
4197 cd /sys/bus/pci/devices/
4198 for address in * ; do
4199 if [ -d
"$address/driver/module
" ] ; then
4200 module=`cd $address/driver/module ; pwd -P | xargs basename`
4201 if grep -q
"^$module
" /proc/modules ; then
4202 address=$(echo $address |sed s/
0000://)
4203 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
4204 echo
"$id $module
"
4213 <p
>Similar code could be used to extract USB device module
4217 if [ -d /sys/bus/usb/devices/ ] ; then
4218 echo loaded usb modules:
4220 cd /sys/bus/usb/devices/
4221 for address in * ; do
4222 if [ -d
"$address/driver/module
" ] ; then
4223 module=`cd $address/driver/module ; pwd -P | xargs basename`
4224 if grep -q
"^$module
" /proc/modules ; then
4225 address=$(echo $address |sed s/
0000://)
4226 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
4227 if [
"$id
" ] ; then
4228 echo
"$id $module
"
4238 <p
>This might perhaps be something to include in other tools as
4244 <title>How to test if a laptop is working with Linux
</title>
4245 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
4246 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
4247 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
4248 <description><p
>The last few days I have spent at work here at the
<a
4249 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
4250 batch of computers will work with Linux. Every year for the last few
4251 years the university have organised shared bid of a few thousand
4252 computers, and this year HP won the bid. Two different desktops and
4253 five different laptops are on the list this year. We in the UNIX
4254 group want to know which one of these computers work well with RHEL
4255 and Ubuntu, the two Linux distributions we currently handle at the
4256 university.
</p
>
4258 <p
>My test method is simple, and I share it here to get feedback and
4259 perhaps inspire others to test hardware as well. To test, I PXE
4260 install the OS version of choice, and log in as my normal user and run
4261 a few applications and plug in selected pieces of hardware. When
4262 something fail, I make a note about this in the test matrix and move
4263 on. If I have some spare time I try to report the bug to the OS
4264 vendor, but as I only have the machines for a short time, I rarely
4265 have the time to do this for all the problems I find.
</p
>
4267 <p
>Anyway, to get to the point of this post. Here is the simple tests
4268 I perform on a new model.
</p
>
4272 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
4273 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4274 RHEL5 and Debian Edu/Squeeze.
</li
>
4276 <li
>Is X.org working? If the graphical login screen show up after
4277 installation, X.org is working.
</li
>
4279 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
4280 package mesa-utils on Ubuntu) and writing down the frames per second
4281 reported by the program.
</li
>
4283 <li
>Is sound working? With Gnome and KDE, a sound is played when
4284 logging in, and if I can hear this the test is successful. If there
4285 are several audio exits on the machine, I try them all and check if
4286 the Gnome/KDE audio mixer can control where to send the sound. I
4287 normally test this by playing
4288 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
4289 video
</a
> in Firefox/Iceweasel.
</li
>
4291 <li
>Is the USB subsystem working? I test this by plugging in a USB
4292 memory stick and see if Gnome/KDE notices this.
</li
>
4294 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
4295 I have lying around, and see if Gnome/KDE notices this.
</li
>
4297 <li
>Is any built in camera working? Test using cheese, and see if a
4298 picture from the v4l device show up.
</li
>
4300 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4301 any bluetooth devices are discovered. In my office, I normally see a
4304 <li
>For laptops, is the SD or Compaq Flash reader working. I have
4305 memory modules lying around, and stick them in and see if Gnome/KDE
4306 notice this.
</li
>
4308 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
4309 special button work, and if the laptop continue to work after
4312 <li
>For laptops, is the extra buttons working, like audio level,
4313 adjusting background light, switching on/off external video output,
4314 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4315 laptop to laptop, so I just write down which are working and which are
4318 <li
>Some laptops have smart card readers, finger print readers,
4319 acceleration sensors etc. I rarely test these, as I do not know how
4320 to quickly test if they are working or not, so I only document their
4321 existence.
</li
>
4325 <p
>By now I suspect you are really curious what the test results are
4326 for the HP machines I am testing. I
'm not done yet, so I will report
4327 the test results later. For now I can report that HP
8100 Elite work
4328 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
4329 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
4330 can see, I have most machines left to test. One interesting
4331 observation is that Ubuntu Lucid has almost twice the frame rate than
4332 RHEL6 with glxgears. No idea why.
</p
>
4337 <title>Some thoughts on BitCoins
</title>
4338 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
4339 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
4340 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
4341 <description><p
>As I continue to explore
4342 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
4343 what properties the system have, and how it will be affected by laws
4344 and regulations here in Norway. Here are some random notes.
</p
>
4346 <p
>One interesting thing to note is that since the transactions are
4347 verified using a peer to peer network, all details about a transaction
4348 is known to everyone. This means that if a BitCoin address has been
4349 published like I did with mine in my initial post about BitCoin, it is
4350 possible for everyone to see how many BitCoins have been transfered to
4351 that address. There is even a web service to look at the details for
4352 all transactions. There I can see that my address
4353 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
4354 have received
16.06 Bitcoin, the
4355 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
4356 address of Simon Phipps have received
181.97 BitCoin and the address
4357 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
4358 of EFF have received
2447.38 BitCoins so far. Thank you to each and
4359 every one of you that donated bitcoins to support my activity. The
4360 fact that anyone can see how much money was transfered to a given
4361 address make it more obvious why the BitCoin community recommend to
4362 generate and hand out a new address for each transaction. I
'm told
4363 there is no way to track which addresses belong to a given person or
4364 organisation without the person or organisation revealing it
4365 themselves, as Simon, EFF and I have done.
</p
>
4367 <p
>In Norway, and in most other countries, there are laws and
4368 regulations limiting how much money one can transfer across the border
4369 without declaring it. There are money laundering, tax and accounting
4370 laws and regulations I would expect to apply to the use of BitCoin.
4371 If the Skolelinux foundation
4372 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
4373 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
4374 normal bank transfers like EFF is doing, how should this be accounted?
4375 Given that it is impossible to know if money can cross the border or
4376 not, should everything or nothing be declared? What exchange rate
4377 should be used when calculating taxes? Would receivers have to pay
4378 income tax if the foundation were to pay Skolelinux contributors in
4379 BitCoin? I have no idea, but it would be interesting to know.
</p
>
4381 <p
>For a currency to be useful and successful, it must be trusted and
4382 accepted by a lot of users. It must be possible to get easy access to
4383 the currency (as a wage or using currency exchanges), and it must be
4384 easy to spend it. At the moment BitCoin seem fairly easy to get
4385 access to, but there are very few places to spend it. I am not really
4386 a regular user of any of the vendor types currently accepting BitCoin,
4387 so I wonder when my kind of shop would start accepting BitCoins. I
4388 would like to buy electronics, travels and subway tickets, not herbs
4389 and books. :) The currency is young, and this will improve over time
4390 if it become popular, but I suspect regular banks will start to lobby
4391 to get BitCoin declared illegal if it become popular. I
'm sure they
4392 will claim it is helping fund terrorism and money laundering (which
4393 probably would be true, as is any currency in existence), but I
4394 believe the problems should be solved elsewhere and not by blaming
4395 currencies.
</p
>
4397 <p
>The process of creating new BitCoins is called mining, and it is
4398 CPU intensive process that depend on a bit of luck as well (as one is
4399 competing against all the other miners currently spending CPU cycles
4400 to see which one get the next lump of cash). The
"winner
" get
50
4401 BitCoin when this happen. Yesterday I came across the obvious way to
4402 join forces to increase ones changes of getting at least some coins,
4403 by coordinating the work on mining BitCoins across several machines
4404 and people, and sharing the result if one is lucky and get the
50
4406 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
4407 if this sounds interesting. I have not had time to try to set up a
4408 machine to participate there yet, but have seen that running on ones
4409 own for a few days have not yield any BitCoins througth mining
4412 <p
>Update
2010-
12-
15: Found an
<a
4413 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
4414 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
4415 it was interesting to read. The arguments presented seem to be
4416 equally valid for gold, which was used as a currency for many years.
</p
>
4421 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
4422 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
4423 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
4424 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
4425 <description><p
>With this weeks lawless
4426 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
4427 attacks
</a
> on Wikileak and
4428 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
4429 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
4430 not be trusted to handle money transactions.
4432 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
4433 Phipps on bitcoin
</a
> reminded me about a project that a friend of
4434 mine mentioned earlier. I decided to follow Simon
's example, and get
4435 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
4436 some help from my friend to get it all running, and he even handed me
4437 some bitcoins to get started. I even donated a few bitcoins to Simon
4438 for helping me remember BitCoin.
</p
>
4440 <p
>So, what is bitcoins, you probably wonder? It is a digital
4441 crypto-currency, decentralised and handled using peer-to-peer
4442 networks. It allows anonymous transactions and prohibits central
4443 control over the transactions, making it impossible for governments
4444 and companies alike to block donations and other transactions. The
4445 source is free software, and while the key dependency wxWidgets
2.9
4446 for the graphical user interface is missing in Debian, the command
4447 line client builds just fine. Hopefully Jonas
4448 <a href=
"http://bugs.debian.org/
578157">will get the package into
4449 Debian
</a
> soon.
</p
>
4451 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
4452 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
4453 bitcoins
</a
> when selling services and goods, and there are even
4454 currency
"stock
" markets where the exchange rate is decided. There
4455 are not many users so far, but the concept seems promising. If you
4456 want to get started and lack a friend with any bitcoins to spare,
4458 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
4459 bitcoin at the time of writing). Use
4460 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
4461 on the current exchange rates.
</p
>
4463 <p
>As an experiment, I have decided to set up bitcoind on one of my
4464 machines. If you want to support my activity, please send Bitcoin
4465 donations to the address
4466 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
4471 <title>Why isn
't Debian Edu using VLC?
</title>
4472 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
4473 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
4474 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
4475 <description><p
>In the latest issue of Linux Journal, the readers choices were
4476 presented, and the winner among the multimedia player were VLC.
4477 Personally, I like VLC, and it is my player of choice when I first try
4478 to play a video file or stream. Only if VLC fail will I drag out
4479 gmplayer to see if it can do better. The reason is mostly the failure
4480 model and trust. When VLC fail, it normally pop up a error message
4481 reporting the problem. When mplayer fail, it normally segfault or
4482 just hangs. The latter failure mode drain my trust in the program.
<p
>
4484 <p
>But even if VLC is my player of choice, we have choosen to use
4485 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
4486 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
4487 plugin to play web videos seamlessly, and the VLC browser plugin is
4488 not very good. For example, it lack in-line control buttons, so there
4489 is no way for the user to pause the video. Also, when I
4490 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
4491 tested the browser plugins
</a
> available in Debian, the VLC plugin
4492 failed on several video pages where mplayer based plugins worked. If
4493 the browser plugin for VLC was as good as the gecko-mediaplayer
4494 package (which uses mplayer), we would switch.
</P
>
4496 <p
>While VLC is a good player, its user interface is slightly
4497 annoying. The most annoying feature is its inconsistent use of
4498 keyboard shortcuts. When the player is in full screen mode, its
4499 shortcuts are different from when it is playing the video in a window.
4500 For example, space only work as pause when in full screen mode. I
4501 wish it had consisten shortcuts and that space also would work when in
4502 window mode. Another nice shortcut in gmplayer is [enter] to restart
4503 the current video. It is very nice when playing short videos from the
4504 web and want to restart it when new people arrive to have a look at
4505 what is going on.
</p
>
4510 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
4511 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
4512 <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>
4513 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
4514 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
4515 upgrade testing of the
4516 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
4517 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
4518 This seem like a very good idea, so I adjusted by test scripts and
4519 can now present the updated result from today:
</p
>
4521 <p
>This is for Gnome:
</p
>
4523 <p
>Installed using apt-get, missing with aptitude
</p
>
4525 <blockquote
><p
>
4530 browser-plugin-gnash
4537 freedesktop-sound-theme
4539 gconf-defaults-service
4554 gnome-desktop-environment
4558 gnome-session-canberra
4563 gstreamer0.10-fluendo-mp3
4569 libapache2-mod-dnssd
4572 libaprutil1-dbd-sqlite3
4575 libboost-date-time1.42
.0
4576 libboost-python1.42
.0
4577 libboost-thread1.42
.0
4579 libchamplain-gtk-
0.4-
0
4581 libclutter-gtk-
0.10-
0
4588 libfreerdp-plugins-standard
4603 libgnomepanel2.24-cil
4608 libgtksourceview2.0-common
4609 libmono-addins-gui0.2-cil
4610 libmono-addins0.2-cil
4611 libmono-cairo2.0-cil
4612 libmono-corlib2.0-cil
4613 libmono-i18n-west2.0-cil
4614 libmono-posix2.0-cil
4615 libmono-security2.0-cil
4616 libmono-sharpzip2.84-cil
4617 libmono-system2.0-cil
4620 libndesk-dbus-glib1.0-cil
4621 libndesk-dbus1.0-cil
4631 libtelepathy-farsight0
4640 nautilus-sendto-empathy
4644 python-aptdaemon-gtk
4646 python-beautifulsoup
4661 python-gtksourceview2
4672 python-pkg-resources
4679 python-twisted-conch
4685 python-zope.interface
4690 rhythmbox-plugin-cdrecorder
4697 system-config-printer-udev
4699 telepathy-mission-control-
5
4710 </p
></blockquote
>
4712 <p
>Installed using apt-get, removed with aptitude
</p
>
4714 <blockquote
><p
>
4720 fast-user-switch-applet
4739 libgtksourceview2.0-
0
4741 libsdl1.2debian-alsa
4747 system-config-printer
4752 </p
></blockquote
>
4754 <p
>Installed using aptitude, missing with apt-get
</p
>
4756 <blockquote
><p
>
4757 gstreamer0.10-gnomevfs
4758 </p
></blockquote
>
4760 <p
>Installed using aptitude, removed with apt-get
</p
>
4762 <blockquote
><p
>
4764 </p
></blockquote
>
4766 <p
>This is for KDE:
</p
>
4768 <p
>Installed using apt-get, missing with aptitude
</p
>
4770 <blockquote
><p
>
4772 </p
></blockquote
>
4774 <p
>Installed using apt-get, removed with aptitude
</p
>
4776 <blockquote
><p
>
4779 </p
></blockquote
>
4781 <p
>Installed using aptitude, missing with apt-get
</p
>
4783 <blockquote
><p
>
4797 kdeartwork-emoticons
4799 kdeartwork-theme-icon
4803 kdebase-workspace-bin
4804 kdebase-workspace-data
4818 kscreensaver-xsavers
4833 plasma-dataengines-workspace
4835 plasma-desktopthemes-artwork
4836 plasma-runners-addons
4837 plasma-scriptengine-googlegadgets
4838 plasma-scriptengine-python
4839 plasma-scriptengine-qedje
4840 plasma-scriptengine-ruby
4841 plasma-scriptengine-webkit
4842 plasma-scriptengines
4843 plasma-wallpapers-addons
4844 plasma-widget-folderview
4845 plasma-widget-networkmanagement
4849 xscreensaver-data-extra
4851 xscreensaver-gl-extra
4852 xscreensaver-screensaver-bsod
4853 </p
></blockquote
>
4855 <p
>Installed using aptitude, removed with apt-get
</p
>
4857 <blockquote
><p
>
4859 google-gadgets-common
4877 libggadget-qt-
1.0-
0b
4882 libkonqsidebarplugin4a
4891 libplasma-geolocation-interface4
4893 libplasmagenericshell4
4907 libsmokeknewstuff2-
3
4908 libsmokeknewstuff3-
3
4910 libsmokektexteditor3
4918 libsmokeqtnetwork4-
3
4924 libsmokeqtuitools4-
3
4936 plasma-dataengines-addons
4937 plasma-scriptengine-superkaramba
4938 plasma-widget-lancelot
4939 plasma-widgets-addons
4940 plasma-widgets-workspace
4944 update-notifier-common
4945 </p
></blockquote
>
4947 <p
>Running apt-get autoremove made the results using apt-get and
4948 aptitude a bit more similar, but there are still quite a lott of
4949 differences. I have no idea what packages should be installed after
4950 the upgrade, but hope those that do can have a look.
</p
>
4955 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
4956 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
4957 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
4958 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
4959 <description><p
>Most of the computers in use by the
4960 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
4961 are virtual machines. And they have been Xen machines running on a
4962 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
4963 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
4964 bit harder that it could have been, because we set up the Xen virtual
4965 machines to get the virtual partitions from LVM, which as far as I
4966 know is not supported by KVM. So to migrate, we had to convert
4967 several LVM logical volumes to partitions on a virtual disk file.
</p
>
4970 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
4971 nice recipe
</a
> to do this, and wrote the following script to do the
4972 migration. It uses qemu-img from the qemu package to make the disk
4973 image, parted to partition it, losetup and kpartx to present the disk
4974 image partions as devices, and dd to copy the data. I NFS mounted the
4975 new servers storage area on the old server to do the migration.
</p
>
4981 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
4986 if [ -z
"$
1" ] ; then
4987 echo
"Usage: $
0 &lt;hostname
&gt;
"
4993 if [ ! -e /dev/vg_data/$host-disk ] ; then
4994 echo
"error: unable to find LVM volume for $host
"
4998 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
4999 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
5000 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
5001 totalsize=$(( ( $disksize + $swapsize ) ))
5004 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
5005 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5007 parted $img mklabel msdos
5008 parted $img mkpart primary linux-swap
0 $disksize
5009 parted $img mkpart primary ext2 $disksize $totalsize
5010 parted $img set
1 boot on
5013 losetup /dev/loop0 $img
5014 kpartx -a /dev/loop0
5016 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
5017 fsck.ext3 -f /dev/mapper/loop0p1 || true
5018 mkswap /dev/mapper/loop0p2
5020 kpartx -d /dev/loop0
5021 losetup -d /dev/loop0
5024 <p
>The script is perhaps so simple that it is not copyrightable, but
5025 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
5027 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
5028 the new disk image attached, installed grub-pc and linux-image-
686 and
5029 set up grub to boot from the disk image. After this, the KVM machines
5030 seem to work just fine.
</p
>
5035 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
5036 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
5037 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
5038 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
5039 <description><p
>I
'm still running upgrade testing of the
5040 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
5041 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
5042 status. Here is a short update based on a test I ran
20101118.
</p
>
5044 <p
>I still do not know what a correct migration should look like, so I
5045 report any differences between apt and aptitude and hope someone else
5046 can see if anything should be changed.
</p
>
5048 <p
>This is for Gnome:
</p
>
5050 <p
>Installed using apt-get, missing with aptitude
</p
>
5052 <blockquote
><p
>
5053 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5054 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
5055 dmz-cursor-theme empathy empathy-common finger
5056 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5057 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5058 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5059 gnome-cards-data gnome-codec-install gnome-core
5060 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5061 gnome-search-tool gnome-session-canberra gnome-spell
5062 gnome-system-log gnome-themes-extras gnome-themes-more
5063 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5064 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5065 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5066 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5067 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
5068 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
5069 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
5070 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
5071 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
5072 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5073 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
5074 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5075 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5076 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5077 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5078 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5079 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5080 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5081 libmono-security2.0-cil libmono-sharpzip2.84-cil
5082 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
5083 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
5084 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
5085 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
5086 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
5087 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
5088 libxalan2-java libxerces2-java media-player-info mesa-utils
5089 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
5090 nautilus-sendto-empathy openoffice.org-writer2latex
5091 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
5092 python-aptdaemon python-aptdaemon-gtk python-axiom
5093 python-beautifulsoup python-bugbuddy python-clientform
5094 python-coherence python-configobj python-crypto python-cupshelpers
5095 python-cupsutils python-eggtrayicon python-elementtree
5096 python-epsilon python-evolution python-feedparser python-gdata
5097 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5098 python-gtksourceview2 python-httplib2 python-louie python-mako
5099 python-markupsafe python-mechanize python-nevow python-notify
5100 python-opengl python-openssl python-pam python-pkg-resources
5101 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5102 python-tagpy python-twisted-bin python-twisted-conch
5103 python-twisted-core python-twisted-web python-utidylib python-webkit
5104 python-xdg python-zope.interface remmina remmina-plugin-data
5105 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5106 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5107 software-center svgalibg1 system-config-printer-udev
5108 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
5109 totem totem-coherence totem-mozilla totem-plugins
5110 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5112 </p
></blockquote
>
5114 Installed using apt-get, removed with aptitude
5116 <blockquote
><p
>
5117 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5118 epiphany-extensions epiphany-gecko evolution-exchange
5119 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5120 gedit-common gnome-app-install gnome-games gnome-games-data
5121 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5122 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5123 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5124 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
5125 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
5126 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
5127 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
5128 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
5129 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
5130 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
5131 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
5132 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
5133 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5134 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5135 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5136 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5137 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
5138 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
5139 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
5140 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
5141 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
5142 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5143 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5144 sound-juicer swfdec-gnome system-config-printer totem-common
5145 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5146 </p
></blockquote
>
5148 <p
>Installed using aptitude, missing with apt-get
</p
>
5150 <blockquote
><p
>
5151 gstreamer0.10-gnomevfs
5152 </p
></blockquote
>
5154 <p
>Installed using aptitude, removed with apt-get
</p
>
5156 <blockquote
><p
>
5158 </p
></blockquote
>
5160 <p
>This is for KDE:
</p
>
5162 <p
>Installed using apt-get, missing with aptitude
</p
>
5164 <blockquote
><p
>
5165 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
5166 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5167 ghostscript-x git gnome-audio gnugo granatier gs-common
5168 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5169 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5170 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5171 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5172 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5173 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5174 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5175 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5176 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5177 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5178 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5179 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
5180 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5181 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5182 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5183 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5184 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5185 libkrossui4 libmailtools-perl libmime-tools-perl
5186 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5187 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5188 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5189 lirc luatex marble networkstatus noatun-plugins
5190 openoffice.org-writer2latex palapeli palapeli-data parley
5191 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5192 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5193 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5195 </p
></blockquote
>
5197 <p
>Installed using apt-get, removed with aptitude
</p
>
5199 <blockquote
><p
>
5200 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5201 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5202 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5203 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5204 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5205 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5206 kitchensync kiten kjumpingcube klatin klettres klickety klines
5207 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5208 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5209 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5210 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5211 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5212 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5213 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5214 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5215 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5216 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
5217 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
5218 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5219 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
5220 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
5221 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5222 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5223 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5224 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5225 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5226 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5227 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
5228 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
5229 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5230 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5231 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5232 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5233 </p
></blockquote
>
5235 <p
>Installed using aptitude, missing with apt-get
</p
>
5237 <blockquote
><p
>
5238 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5239 kdeartwork kdebase kdebase-apps kdebase-workspace
5240 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5241 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5242 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5243 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5244 xscreensaver-screensaver-bsod
5245 </p
></blockquote
>
5247 <p
>Installed using aptitude, removed with apt-get
</p
>
5249 <blockquote
><p
>
5250 kdebase-bin konq-plugins konqueror
5251 </p
></blockquote
>
5256 <title>Gnash buildbot slave and Debian kfreebsd
</title>
5257 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
5258 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
5259 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
5260 <description><p
>Answering
5261 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
5262 call from the Gnash project
</a
> for
5263 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
5264 current source, I have set up a virtual KVM machine on the Debian
5265 Edu/Skolelinux virtualization host to test the git source on
5266 Debian/Squeeze. I hope this can help the developers in getting new
5267 releases out more often.
</p
>
5269 <p
>As the developers want less main-stream build platforms tested to,
5270 I have considered setting up a
<a
5271 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
5272 machine as well. I have also considered using the kfreebsd
5273 architecture in Debian as a file server in NUUG to get access to the
5
5274 TB zfs volume we currently use to store DV video. Because of this, I
5275 finally got around to do a test installation of Debian/Squeeze with
5276 kfreebsd. Installation went fairly smooth, thought I noticed some
5277 visual glitches in the cdebconf dialogs (black cursor left on the
5278 screen at random locations). Have not gotten very far with the
5279 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5280 fatal problem. Have to spend some more time on it to see if it is
5281 useful as a file server for NUUG. Will try to find time to set up a
5282 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
5287 <title>Debian in
3D
</title>
5288 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
5289 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
5290 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
5291 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
5293 <p
>3D printing is just great. I just came across this Debian logo in
5295 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
5296 thingiverse blog
</a
>.
</p
>
5301 <title>Software updates
2010-
10-
24</title>
5302 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
5303 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
5304 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
5305 <description><p
>Some updates.
</p
>
5307 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
5308 raise money for the project is going well. The lower limit of
10
5309 signers was reached in
24 hours, and so far
13 people have signed it.
5310 More signers and more funding is most welcome, and I am really curious
5311 how far we can get before the time limit of December
24 is reached.
5314 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
5315 about what appear to be a great code coverage tool capable of
5316 generating code coverage stats without any changes to the source code.
5318 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
5319 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
5320 It is missing in Debian, but the git source built just fine in Squeeze
5321 after I installed libelf-dev, libdwarf-dev, pkg-config and
5322 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5323 solvable. I hope kcov make it into Debian soon.
</p
>
5325 <p
>Finally found time to wrap up the release notes for
<a
5326 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
5327 new alpha release of Debian Edu
</a
>, and just published the second
5328 alpha test release of the Squeeze based Debian Edu /
5329 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
5330 release. Give it a try if you need a complete linux solution for your
5331 school, including central infrastructure server, workstations, thin
5332 client servers and diskless workstations. A nice touch added
5333 yesterday is RDP support on the thin client servers, for windows
5334 clients to get a Linux desktop on request.
</p
>
5339 <title>Some notes on Flash in Debian and Debian Edu
</title>
5340 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
5341 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
5342 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
5343 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
5344 popularity-contest numbers
</a
>, the adobe-flashplugin package the
5345 second most popular used package that is missing in Debian. The sixth
5346 most popular is flashplayer-mozilla. This is a clear indication that
5347 working flash is important for Debian users. Around
10 percent of the
5348 users submitting data to popcon.debian.org have this package
5349 installed.
</p
>
5351 <p
>In the report written by Lars Risan in August
2008
5352 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
5353 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5354 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
5355 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
5356 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
5357 web sites require Flash to work, and lacking working Flash support in
5358 the web browser and the problems with installing it was perceived as a
5359 good reason to stay with Windows.
</p
>
5361 <p
>I once saw a funny and sad comment in a web forum, where Linux was
5362 said to be the retarded cousin that did not really understand
5363 everything you told him but could work fairly well. This was a
5364 comment regarding the problems Linux have with proprietary formats and
5365 non-standard web pages, and is sad because it exposes a fairly common
5366 understanding of whose fault it is if web pages that only work in for
5367 example Internet Explorer
6 fail to work on Firefox, and funny because
5368 it explain very well how annoying it is for users when Linux
5369 distributions do not work with the documents they receive or the web
5370 pages they want to visit.
</p
>
5372 <p
>This is part of the reason why I believe it is important for Debian
5373 and Debian Edu to have a well working Flash implementation in the
5374 distribution, to get at least popular sites as Youtube and Google
5375 Video to working out of the box. For Squeeze, Debian have the chance
5376 to include the latest version of Gnash that will make this happen, as
5377 the new release
0.8.8 was published a few weeks ago and is resting in
5378 unstable. The new version work with more sites that version
0.8.7.
5379 The Gnash maintainers have asked for a freeze exception, but the
5380 release team have not had time to reply to it yet. I hope they agree
5381 with me that Flash is important for the Debian desktop users, and thus
5382 accept the new package into Squeeze.
</p
>
5387 <title>Circular package dependencies harms apt recovery
</title>
5388 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
5389 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
5390 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
5391 <description><p
>I discovered this while doing
5392 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
5393 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
5394 in Debian still got circular dependencies, and it is often claimed
5395 that apt and aptitude should be able to handle this just fine, but
5396 some times these dependency loops causes apt to fail.
</p
>
5398 <p
>An example is from todays
5399 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
5400 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
5401 causes perl-modules to fail to upgrade. The cause is simple. If a
5402 package fail to unpack, then only part of packages with the circular
5403 dependency might end up being unpacked when unpacking aborts, and the
5404 ones already unpacked will fail to configure in the recovery phase
5405 because its dependencies are unavailable.
</p
>
5407 <p
>In this log, the problem manifest itself with this error:
</p
>
5409 <blockquote
><pre
>
5410 dpkg: dependency problems prevent configuration of perl-modules:
5411 perl-modules depends on perl (
>=
5.10.1-
1); however:
5412 Version of perl on system is
5.10.0-
19lenny
2.
5413 dpkg: error processing perl-modules (--configure):
5414 dependency problems - leaving unconfigured
5415 </pre
></blockquote
>
5417 <p
>The perl/perl-modules circular dependency is already
5418 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
5419 hopefully be solved as soon as possible, but it is not the only one,
5420 and each one of these loops in the dependency tree can cause similar
5421 failures. Of course, they only occur when there are bugs in other
5422 packages causing the unpacking to fail, but it is rather nasty when
5423 the failure of one package causes the problem to become worse because
5424 of dependency loops.
</p
>
5427 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
5428 tireless effort by Bill Allombert
</a
>, the number of circular
5430 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
5431 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
5433 <p
>Todays testing also exposed a bug in
5434 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
5435 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
5436 apt-get and aptitude, the latter possibly caused by some circular
5437 dependency. Reported both to BTS to try to get someone to look at
5443 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
5444 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
5445 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
5446 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
5447 <description><p
>This is a
5448 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
5450 <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
5452 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
5453 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
5455 <p
>As a step to try to see if it possible to merge the DNS and DHCP
5456 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5457 and dhcp3-server-ldap in Debian use the LDAP server. The two
5458 implementations are quite different in how they use LDAP.
</p
>
5460 To get this information, I started slapd with debugging enabled and
5461 dumped the debug output to a file to get the LDAP searches performed
5462 on a Debian Edu main-server. Here is a summary.
5464 <p
><strong
>powerdns
</strong
></p
>
5466 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
5467 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
5470 <p
>PowerDNS have two modes of operation using LDAP as its backend.
5471 One
"strict
" mode where the forward and reverse DNS lookups are done
5472 using the same LDAP objects, and a
"tree
" mode where the forward and
5473 reverse entries are in two different subtrees in LDAP with a structure
5474 based on the DNS names, as in tjener.intern and
5475 2.2.0.10.in-addr.arpa.
</p
>
5477 <p
>In tree mode, the server is set up to use a LDAP subtree as its
5478 base, and uses a
"base
" scoped search for the DNS name by adding
5479 "dc=tjener,dc=intern,
" to the base with a filter for
5480 "(associateddomain=tjener.intern)
" for the forward entry and
5481 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
5482 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
5483 forward entries, it is looking for attributes named dnsttl, arecord,
5484 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5485 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5486 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5487 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5488 spfrecord and modifytimestamp. For reverse entries it is looking for
5489 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5490 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5491 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5492 ldapsearch commands could look like this:
</p
>
5494 <blockquote
><pre
>
5495 ldapsearch -h ldap \
5496 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5497 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
5498 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5499 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5500 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5501 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5503 ldapsearch -h ldap \
5504 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5505 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
5506 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
5507 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
5508 srvrecord naptrrecord modifytimestamp
5509 </pre
></blockquote
>
5511 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
5512 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
5513 example LDAP objects used there. In addition to these objects, the
5514 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
5515 also exist.
</p
>
5517 <blockquote
><pre
>
5518 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
5520 objectclass: dnsdomain
5521 objectclass: domainrelatedobject
5524 associateddomain: tjener.intern
5526 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
5528 objectclass: dnsdomain2
5529 objectclass: domainrelatedobject
5531 ptrrecord: tjener.intern
5532 associateddomain:
2.2.0.10.in-addr.arpa
5533 </pre
></blockquote
>
5535 <p
>In strict mode, the server behaves differently. When looking for
5536 forward DNS entries, it is doing a
"subtree
" scoped search with the
5537 same base as in the tree mode for a object with filter
5538 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
5539 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
5540 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
5541 naptrrecord and modifytimestamp. For reverse entires it also do a
5542 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
5543 and the requested attributes are associateddomain, dnsttl and
5544 modifytimestamp. In short, in strict mode the objects with ptrrecord
5545 go away, and the arecord attribute in the forward object is used
5548 <p
>The forward and reverse searches can be simulated using ldapsearch
5549 like this:
</p
>
5551 <blockquote
><pre
>
5552 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5553 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
5554 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5555 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5556 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5557 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5559 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5560 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
5561 </pre
></blockquote
>
5563 <p
>In addition to the forward and reverse searches , there is also a
5564 search for SOA records, which behave similar to the forward and
5565 reverse lookups.
</p
>
5567 <p
>A thing to note with the PowerDNS behaviour is that it do not
5568 specify any objectclass names, and instead look for the attributes it
5569 need to generate a DNS reply. This make it able to work with any
5570 objectclass that provide the needed attributes.
</p
>
5572 <p
>The attributes are normally provided in the cosine (RFC
1274) and
5573 dnsdomain2 schemas. The latter is used for reverse entries like
5574 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
5576 <p
>In Debian Edu, we have created DNS objects using the object classes
5577 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
5578 attributes) and domainrelatedobject (for associatedDomain). The use
5579 of structural object classes make it impossible to combine these
5580 classes with the object classes used by DHCP.
</p
>
5582 <p
>There are other schemas that could be used too, for example the
5583 dnszone structural object class used by Gosa and bind-sdb for the DNS
5584 attributes combined with the domainrelatedobject object class, but in
5585 this case some unused attributes would have to be included as well
5586 (zonename and relativedomainname).
</p
>
5588 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
5589 mode and not use any of the existing objectclasses (dnsdomain,
5590 dnsdomain2 and dnszone) when one want to combine the DNS information
5591 with DHCP information, and instead create a auxiliary object class
5592 defined something like this (using the attributes defined for
5593 dnsdomain and dnsdomain2 or dnszone):
</p
>
5595 <blockquote
><pre
>
5596 objectclass ( some-oid NAME
'dnsDomainAux
'
5599 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
5600 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
5601 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
5602 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
5603 A6Record $ DNAMERecord
5605 </pre
></blockquote
>
5607 <p
>This will allow any object to become a DNS entry when combined with
5608 the domainrelatedobject object class, and allow any entity to include
5609 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
5610 developers asking for their view on this schema and if they are
5611 interested in providing such schema with PowerDNS, and I hope my
5612 message will be accepted into their mailing list soon.
</p
>
5614 <p
><strong
>ISC dhcp
</strong
></p
>
5616 <p
>The DHCP server searches for specific objectclass and requests all
5617 the object attributes, and then uses the attributes it want. This
5618 make it harder to figure out exactly what attributes are used, but
5619 thanks to the working example in Debian Edu I can at least get an idea
5620 what is needed without having to read the source code.
</p
>
5622 <p
>In the DHCP server configuration, the LDAP base to use and the
5623 search filter to use to locate the correct dhcpServer entity is
5624 stored. These are the relevant entries from
5625 /etc/dhcp3/dhcpd.conf:
</p
>
5627 <blockquote
><pre
>
5628 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
5629 ldap-dhcp-server-cn
"dhcp
";
5630 </pre
></blockquote
>
5632 <p
>The DHCP server uses this information to nest all the DHCP
5633 configuration it need. The cn
"dhcp
" is located using the given LDAP
5634 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
5635 search result is this entry:
</p
>
5637 <blockquote
><pre
>
5638 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
5641 objectClass: dhcpServer
5642 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5643 </pre
></blockquote
>
5645 <p
>The content of the dhcpServiceDN attribute is next used to locate the
5646 subtree with DHCP configuration. The DHCP configuration subtree base
5647 is located using a base scope search with base
"cn=DHCP
5648 Config,dc=skole,dc=skolelinux,dc=no
" and filter
5649 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
5650 The search result is this entry:
</p
>
5652 <blockquote
><pre
>
5653 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5656 objectClass: dhcpService
5657 objectClass: dhcpOptions
5658 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
5659 dhcpStatements: ddns-update-style none
5660 dhcpStatements: authoritative
5661 dhcpOption: smtp-server code
69 = array of ip-address
5662 dhcpOption: www-server code
72 = array of ip-address
5663 dhcpOption: wpad-url code
252 = text
5664 </pre
></blockquote
>
5666 <p
>Next, the entire subtree is processed, one level at the time. When
5667 all the DHCP configuration is loaded, it is ready to receive requests.
5668 The subtree in Debian Edu contain objects with object classes
5669 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
5670 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
5671 and information about netmasks, dynamic range etc. Leaving out the
5672 details here because it is not relevant for the focus of my
5673 investigation, which is to see if it is possible to merge dns and dhcp
5674 related computer objects.
</p
>
5676 <p
>When a DHCP request come in, LDAP is searched for the MAC address
5677 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
5678 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
5679 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
5680 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
5683 <blockquote
><pre
>
5684 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5687 objectClass: dhcpHost
5688 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
5689 dhcpStatements: fixed-address hostname
5690 </pre
></blockquote
>
5692 <p
>There is less flexiblity in the way LDAP searches are done here.
5693 The object classes need to have fixed names, and the configuration
5694 need to be stored in a fairly specific LDAP structure. On the
5695 positive side, the invidiual dhcpHost entires can be anywhere without
5696 the DN pointed to by the dhcpServer entries. The latter should make
5697 it possible to group all host entries in a subtree next to the
5698 configuration entries, and this subtree can also be shared with the
5699 DNS server if the schema proposed above is combined with the dhcpHost
5700 structural object class.
5702 <p
><strong
>Conclusion
</strong
></p
>
5704 <p
>The PowerDNS implementation seem to be very flexible when it come
5705 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
5706 come to the the LDAP structure, the
"strict
" mode is very flexible,
5707 allowing DNS objects to be stored anywhere under the base cn specified
5708 in the configuration.
</p
>
5710 <p
>The DHCP implementation on the other hand is very inflexible, both
5711 regarding which LDAP schemas to use and which LDAP structure to use.
5712 I guess one could implement ones own schema, as long as the
5713 objectclasses and attributes have the names used, but this do not
5714 really help when the DHCP subtree need to have a fairly fixed
5715 structure.
</p
>
5717 <p
>Based on the observed behaviour, I suspect a LDAP structure like
5718 this might work for Debian Edu:
</p
>
5720 <blockquote
><pre
>
5722 cn=machine-info (dhcpService) - dhcpServiceDN points here
5723 cn=dhcp (dhcpServer)
5724 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
5725 cn=
10.0.2.0 (dhcpSubnet)
5726 cn=group1 (dhcpGroup/dhcpOptions)
5727 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
5728 cn=
192.168.0.0 (dhcpSubnet)
5729 cn=group1 (dhcpGroup/dhcpOptions)
5730 ou=machines - PowerDNS base points here
5731 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
5732 </pre
></blockquote
>
5734 <P
>This is not tested yet. If the DHCP server require the dhcpHost
5735 entries to be in the dhcpGroup subtrees, the entries can be stored
5736 there instead of a common machines subtree, and the PowerDNS base
5737 would have to be moved one level up to the machine-info subtree.
</p
>
5739 <p
>The combined object under the machines subtree would look something
5740 like this:
</p
>
5742 <blockquote
><pre
>
5743 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
5746 objectClass: dhcpHost
5747 objectclass: domainrelatedobject
5748 objectclass: dnsDomainAux
5749 associateddomain: hostname.intern
5750 arecord:
10.11.12.13
5751 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
5752 dhcpStatements: fixed-address hostname.intern
5753 </pre
></blockquote
>
5755 </p
>One could even add the LTSP configuration associated with a given
5756 machine, as long as the required attributes are available in a
5757 auxiliary object class.
</p
>
5762 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
5763 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
5764 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
5765 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
5766 <description><p
>For a while now, I have wanted to find a way to change the DNS and
5767 DHCP services in Debian Edu to use the same LDAP objects for a given
5768 computer, to avoid the possibility of having a inconsistent state for
5769 a computer in LDAP (as in DHCP but no DNS entry or the other way
5770 around) and make it easier to add computers to LDAP.
</p
>
5772 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
5773 information finally found a solution that seem to work.
</p
>
5775 <p
>The old setup required three LDAP objects for a given computer.
5776 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
5777 we switch powerdns to use its strict LDAP method (ldap-method=strict
5778 in pdns-debian-edu.conf), the forward and reverse DNS entries are
5779 merged into one while making it impossible to transfer the reverse map
5780 to a slave DNS server.
</p
>
5782 <p
>If we also replace the object class used to get the DNS related
5783 attributes to one allowing these attributes to be combined with the
5784 dhcphost object class, we can merge the DNS and DHCP entries into one.
5785 I
've written such object class in the dnsdomainaux.schema file (need
5786 proper OIDs, but that is a minor issue), and tested the setup. It
5787 seem to work.
</p
>
5789 <p
>With this test setup in place, we can get away with one LDAP object
5790 for both DNS and DHCP, and even the LTSP configuration I suggested in
5791 an earlier email. The combined LDAP object will look something like
5794 <blockquote
><pre
>
5795 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5797 objectClass: dhcphost
5798 objectclass: domainrelatedobject
5799 objectclass: dnsdomainaux
5800 associateddomain: hostname.intern
5801 arecord:
10.11.12.13
5802 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
5803 dhcpstatements: fixed-address hostname
5805 </pre
></blockquote
>
5807 <p
>The DNS server uses the associateddomain and arecord entries, while
5808 the DHCP server uses the dhcphwaddress and dhcpstatements entries
5809 before asking DNS to resolve the fixed-adddress. LTSP will use
5810 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
5812 <p
>I am not yet sure if I can get the DHCP server to look for its
5813 dhcphost in a different location, to allow us to put the objects
5814 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
5815 that. If I can
't figure out a way to do that, we can still get rid of
5816 the hosts subtree and move all its content into the DHCP Config tree
5817 (which probably should be renamed to be more related to the new
5818 content. I suspect cn=dnsdhcp,ou=services or something like that
5819 might be a good place to put it.
</p
>
5821 <p
>If you want to help out with implementing this for Debian Edu,
5822 please contact us on debian-edu@lists.debian.org.
</p
>
5827 <title>Idea for storing LTSP configuration in LDAP
</title>
5828 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
5829 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
5830 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
5831 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
5832 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
5833 clients, and that this can be used to fetch configuration from LDAP if
5834 Debian Edu choose to store configuration there.
</p
>
5836 <p
>Armed with this information, I got inspired and wrote a test module
5837 to get configuration from LDAP. The idea is to look up the MAC
5838 address of the client in LDAP, and look for attributes on the form
5839 ltspconfigsetting=value, and use this to export SETTING=value to the
5840 LTSP clients.
</p
>
5842 <p
>The goal is to be able to store the LTSP configuration attributes
5843 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
5844 allowing us to store all information about a computer in one place.
</p
>
5846 <p
>This is a untested draft implementation, and I welcome feedback on
5847 this approach. A real LDAP schema for the ltspClientAux objectclass
5848 need to be written. Comments, suggestions, etc?
</p
>
5850 <blockquote
><pre
>
5851 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
5853 # Fetch LTSP client settings from LDAP based on MAC address
5855 # Uses ethernet address as stored in the dhcpHost objectclass using
5856 # the dhcpHWAddress attribute or ethernet address stored in the
5857 # ieee802Device objectclass with the macAddress attribute.
5859 # This module is written to be schema agnostic, and only depend on the
5860 # existence of attribute names.
5862 # The LTSP configuration variables are saved directly using a
5863 # ltspConfig prefix and uppercasing the rest of the attribute name.
5864 # To set the SERVER variable, set the ltspConfigServer attribute.
5866 # Some LDAP schema should be created with all the relevant
5867 # configuration settings. Something like this should work:
5869 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
5872 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
5874 LDAPSERVER=$(debian-edu-ldapserver)
5875 if [
"$LDAPSERVER
" ] ; then
5876 LDAPBASE=$(debian-edu-ldapserver -b)
5877 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
5878 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
5879 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
5880 grep
'^ltspConfig
' | while read attr value ; do
5881 # Remove prefix and convert to upper case
5882 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
5883 # bass value on to clients
5884 eval
"$attr=$value; export $attr
"
5888 </pre
></blockquote
>
5890 <p
>I
'm not sure this shell construction will work, because I suspect
5891 the while block might end up in a subshell causing the variables set
5892 there to not show up in ltsp-config, but if that is the case I am sure
5893 the code can be restructured to make sure the variables are passed on.
5894 I expect that can be solved with some testing. :)
</p
>
5896 <p
>If you want to help out with implementing this for Debian Edu,
5897 please contact us on debian-edu@lists.debian.org.
</p
>
5899 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
5900 configuration in LDAP that was created around year
2000 by
5901 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
5902 Xperience, Inc.,
2000</a
>. I found its
5903 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
5904 personal home page over at redhat.com.
</p
>
5909 <title>jXplorer, a very nice LDAP GUI
</title>
5910 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
5911 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
5912 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
5913 <description><p
>Since
5914 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
5915 last post
</a
> about available LDAP tools in Debian, I was told about a
5916 LDAP GUI that is even better than luma. The java application
5917 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
5918 moving LDAP objects and subtrees using drag-and-drop, and can
5919 authenticate using Kerberos. I have only tested the Kerberos
5920 authentication, but do not have a LDAP setup allowing me to rewrite
5921 LDAP with my test user yet. It is
5922 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
5923 Debian
</a
> testing and unstable at the moment. The only problem I
5924 have with it is how it handle errors. If something go wrong, its
5925 non-intuitive behaviour require me to go through some query work list
5926 and remove the failing query. Nothing big, but very annoying.
</p
>
5931 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
5932 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
5933 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
5934 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
5935 <description><p
>Here is a short update on my
<a
5936 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
5937 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
5938 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
5939 not reporting the status for KDE, because the upgrade crashes when
5940 aptitude try because of missing conflicts
5941 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
5942 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
5944 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
5945 complete list of the installed packages. Based on this I see these
5946 differences when I did a test run today. As usual, I do not really
5947 know what the correct set of packages would be, but thought it best to
5948 publish the difference.
</p
>
5950 <p
>Installed using apt-get, missing with aptitude
</p
>
5952 <blockquote
><p
>
5953 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
5954 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
5955 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
5956 libgtksourceview-common libpt-
1.10.10-plugins-alsa
5957 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
5958 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
5959 python-
4suite-xml python-eggtrayicon python-gtkhtml2
5960 python-gtkmozembed svgalibg1 xserver-xephyr zip
5961 </p
></blockquote
>
5963 <p
>Installed using apt-get, removed with aptitude
</p
>
5965 <blockquote
><p
>
5966 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
5967 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
5968 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
5969 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
5970 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
5971 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
5972 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
5973 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
5974 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
5975 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
5976 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
5977 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
5978 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
5979 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
5980 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
5981 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
5982 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
5983 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
5984 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
5985 mysql-common swfdec-gnome totem-gstreamer wodim
5986 </p
></blockquote
>
5988 <p
>Installed using aptitude, missing with apt-get
</p
>
5990 <blockquote
><p
>
5991 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
5992 python-gnomekeyring python-wnck rhythmbox-plugins xorg
5993 xserver-xorg-input-all xserver-xorg-input-evdev
5994 xserver-xorg-input-kbd xserver-xorg-input-mouse
5995 xserver-xorg-input-synaptics xserver-xorg-video-all
5996 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
5997 xserver-xorg-video-chips xserver-xorg-video-cirrus
5998 xserver-xorg-video-dummy xserver-xorg-video-fbdev
5999 xserver-xorg-video-glint xserver-xorg-video-i128
6000 xserver-xorg-video-i740 xserver-xorg-video-mach64
6001 xserver-xorg-video-mga xserver-xorg-video-neomagic
6002 xserver-xorg-video-nouveau xserver-xorg-video-nv
6003 xserver-xorg-video-r128 xserver-xorg-video-radeon
6004 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6005 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6006 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6007 xserver-xorg-video-sis xserver-xorg-video-sisusb
6008 xserver-xorg-video-tdfx xserver-xorg-video-tga
6009 xserver-xorg-video-trident xserver-xorg-video-tseng
6010 xserver-xorg-video-vesa xserver-xorg-video-vmware
6011 xserver-xorg-video-voodoo
6012 </p
></blockquote
>
6014 <p
>Installed using aptitude, removed with apt-get
</p
>
6016 <blockquote
><p
>
6017 deskbar-applet xserver-xorg xserver-xorg-core
6018 xserver-xorg-input-wacom xserver-xorg-video-intel
6019 xserver-xorg-video-openchrome
6020 </p
></blockquote
>
6022 <p
>I was told on IRC that the xorg-xserver package was
6023 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
6024 in git
</a
> today to try to get apt-get to not remove xorg completely.
6025 No idea when it hits Squeeze, but when it does I hope it will reduce
6026 the difference somewhat.
6031 <title>LUMA, a very nice LDAP GUI
</title>
6032 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
6033 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
6034 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
6035 <description><p
>The last few days I have been looking into the status of the LDAP
6036 directory in Debian Edu, and in the process I started to miss a GUI
6037 tool to browse the LDAP tree. The only one I was able to find in
6038 Debian/Squeeze and Lenny is
6039 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
6040 be a great tool to get a overview of the current LDAP directory
6041 populated by default in Skolelinux. Thanks to it, I have been able to
6042 find empty and obsolete subtrees, misplaced objects and duplicate
6043 objects. It will be installed by default in Debian/Squeeze. If you
6044 are working with LDAP, give it a go. :)
</p
>
6046 <p
>I did notice one problem with it I have not had time to report to
6047 the BTS yet. There is no .desktop file in the package, so the tool do
6048 not show up in the Gnome and KDE menus, but only deep down in in the
6049 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6052 <p
>I have not yet been able to get it to modify the tree yet. I would
6053 like to move objects and remove subtrees directly in the GUI, but have
6054 not found a way to do that with LUMA yet. So in the mean time, I use
6055 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
6057 <p
>If you have tips on other GUI tools for LDAP that might be useful
6058 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
6060 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
6061 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
6062 useful GUI alternative. It seem like a good tool, but is unmaintained
6063 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6064 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
6069 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
6070 <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>
6071 <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>
6072 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
6073 <description><p
>A while back, I
6074 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
6075 about the fact
</a
> that it is not possible with the provided schemas
6076 for storing DNS and DHCP information in LDAP to combine the two sets
6077 of information into one LDAP object representing a computer.
</p
>
6079 <p
>In the mean time, I discovered that a simple fix would be to make
6080 the dhcpHost object class auxiliary, to allow it to be combined with
6081 the dNSDomain object class, and thus forming one object for one
6082 computer when storing both DHCP and DNS information in LDAP.
</p
>
6084 <p
>If I understand this correctly, it is not safe to do this change
6085 without also changing the assigned number for the object class, and I
6086 do not know enough about LDAP schema design to do that properly for
6087 Debian Edu.
</p
>
6089 <p
>Anyway, for future reference, this is how I believe we could change
6091 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
6092 schema
</a
> to solve at least part of the problem with the LDAP schemas
6093 available today from IETF.
</p
>
6096 --- dhcp.schema (revision
65192)
6097 +++ dhcp.schema (working copy)
6099 objectclass (
2.16.840.1.113719.1.203.6.6
6100 NAME
'dhcpHost
'
6101 DESC
'This represents information about a particular client
'
6105 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6106 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
6109 <p
>I very much welcome clues on how to do this properly for Debian
6110 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6111 package, and should thus be free to rewrite it as we see fit.
</p
>
6113 <p
>If you want to help out with implementing this for Debian Edu,
6114 please contact us on debian-edu@lists.debian.org.
</p
>
6119 <title>Calling tasksel like the installer, while still getting useful output
</title>
6120 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
6121 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
6122 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
6123 <description><p
>A few times I have had the need to simulate the way tasksel
6124 installs packages during the normal debian-installer run. Until now,
6125 I have ended up letting tasksel do the work, with the annoying problem
6126 of not getting any feedback at all when something fails (like a
6127 conffile question from dpkg or a download that fails), using code like
6130 <blockquote
><pre
>
6131 export DEBIAN_FRONTEND=noninteractive
6132 tasksel --new-install
6133 </pre
></blockquote
>
6135 This would invoke tasksel, let its automatic task selection pick the
6136 tasks to install, and continue to install the requested tasks without
6137 any output what so ever.
6139 Recently I revisited this problem while working on the automatic
6140 package upgrade testing, because tasksel would some times hang without
6141 any useful feedback, and I want to see what is going on when it
6142 happen. Then it occured to me, I can parse the output from tasksel
6143 when asked to run in test mode, and use that aptitude command line
6144 printed by tasksel then to simulate the tasksel run. I ended up using
6147 <blockquote
><pre
>
6148 export DEBIAN_FRONTEND=noninteractive
6149 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
6151 </pre
></blockquote
>
6153 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
6154 --without-recommends -o APT::Install-Recommends=no -y install
6155 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6156 ~pimportant
</tt
>", which will install the gnome desktop task, the
6157 laptop task and all packages with priority standard , required and
6158 important, just like tasksel would have done it during
6159 installation.
</p
>
6161 <p
>A better approach is probably to extend tasksel to be able to
6162 install packages without using debconf-apt-progress, for use cases
6163 like this.
</p
>
6168 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
6169 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
6170 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
6171 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
6172 <description><p
>My
6173 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
6174 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
6175 finally made the upgrade logs available from
6176 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
6177 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6178 apt and aptitude, and found their differences interesting. This time
6179 I will only focus on their removal plans.
</p
>
6181 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
6182 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
6183 surprising part is that it want to remove xorg and all
6184 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6185 sure why. When asking aptitude to do the same, it want to remove
129
6186 packages, but most of them are library packages I suspect are no
6187 longer needed. Both of them want to remove bluetooth packages, which
6188 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
6190 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
6191 which seem like a bad idea and xorg the same way as with Gnome. Asking
6192 aptitude for the same, it wants to remove
192 packages, none which are
6193 too surprising.
</p
>
6195 <p
>I guess the removal of xorg during upgrades should be investigated
6196 and avoided, and perhaps others as well. Here are the complete list
6197 of planned removals. The complete logs is available from the URL
6198 above. Note if you want to repeat these tests, that the upgrade test
6199 for kde+apt-get hung in the tasksel setup because of dpkg asking
6200 conffile questions. No idea why. I worked around it by using
6201 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
6204 <p
><b
>apt-get gnome
72</b
>
6205 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
6206 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6207 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
6208 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6209 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6210 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6211 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6212 xserver-xorg-input-kbd xserver-xorg-input-mouse
6213 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6214 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6215 xserver-xorg-video-ati xserver-xorg-video-chips
6216 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6217 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6218 xserver-xorg-video-glint xserver-xorg-video-i128
6219 xserver-xorg-video-i740 xserver-xorg-video-imstt
6220 xserver-xorg-video-intel xserver-xorg-video-mach64
6221 xserver-xorg-video-mga xserver-xorg-video-neomagic
6222 xserver-xorg-video-nsc xserver-xorg-video-nv
6223 xserver-xorg-video-openchrome xserver-xorg-video-r128
6224 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6225 xserver-xorg-video-rendition xserver-xorg-video-s3
6226 xserver-xorg-video-s3virge xserver-xorg-video-savage
6227 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6228 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6229 xserver-xorg-video-tga xserver-xorg-video-trident
6230 xserver-xorg-video-tseng xserver-xorg-video-v4l
6231 xserver-xorg-video-vesa xserver-xorg-video-vga
6232 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
6233 xulrunner-
1.9-gnome-support
</p
>
6235 <p
><b
>aptitude gnome
129</b
>
6237 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
6238 djvulibre-desktop finger gnome-app-install gnome-mount
6239 gnome-network-admin gnome-spell gnome-vfs-obexftp
6240 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6241 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6242 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6243 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
6244 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
6245 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
6246 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
6247 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
6248 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
6249 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
6250 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
6251 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
6252 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6253 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
6254 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
6255 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
6256 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
6257 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
6258 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6259 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6260 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6261 openoffice.org-writer2latex openssl-blacklist p7zip
6262 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
6263 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6264 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6265 swfdec-mozilla totem-gstreamer update-manager wodim
6266 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6267 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6270 <p
><b
>apt-get kde
82</b
>
6272 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6273 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6274 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6275 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6276 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6277 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6278 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6279 xserver-xorg-input-kbd xserver-xorg-input-mouse
6280 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6281 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6282 xserver-xorg-video-ati xserver-xorg-video-chips
6283 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6284 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6285 xserver-xorg-video-glint xserver-xorg-video-i128
6286 xserver-xorg-video-i740 xserver-xorg-video-imstt
6287 xserver-xorg-video-intel xserver-xorg-video-mach64
6288 xserver-xorg-video-mga xserver-xorg-video-neomagic
6289 xserver-xorg-video-nsc xserver-xorg-video-nv
6290 xserver-xorg-video-openchrome xserver-xorg-video-r128
6291 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6292 xserver-xorg-video-rendition xserver-xorg-video-s3
6293 xserver-xorg-video-s3virge xserver-xorg-video-savage
6294 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6295 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6296 xserver-xorg-video-tga xserver-xorg-video-trident
6297 xserver-xorg-video-tseng xserver-xorg-video-v4l
6298 xserver-xorg-video-vesa xserver-xorg-video-vga
6299 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
6301 <p
><b
>aptitude kde
192</b
>
6302 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
6303 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6304 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6305 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6306 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6307 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6308 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6309 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6310 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6311 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6312 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6313 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6314 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6315 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6316 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6317 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6318 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6319 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6320 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
6321 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6322 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6323 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
6324 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6325 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6326 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6327 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6328 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6329 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
6330 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
6331 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6332 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6333 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6334 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6335 texlive-common texlive-doc-base texlive-fonts-recommended
6336 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6337 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6338 xulrunner-
1.9</p
>
6344 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
6345 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
6346 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
6347 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
6348 <description><p
>The last few days I have done some upgrade testing in Debian, to
6349 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6350 have been discovered and reported in the process
6351 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
6352 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
6353 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
6354 kdebase-workspace-data), and to get a more regular testing going on, I
6355 am working on a script to automate the test.
</p
>
6357 <p
>The idea is to create a Lenny chroot and use tasksel to install a
6358 Gnome or KDE desktop installation inside the chroot before upgrading
6359 it. To ensure no services are started in the chroot, a policy-rc.d
6360 script is inserted. To make sure tasksel believe it is to install a
6361 desktop on a laptop, the tasksel tests are replaced in the chroot
6362 (only acceptable because this is a throw-away chroot).
</p
>
6364 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6365 currently always fail because udev refuses to upgrade with the kernel
6366 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6367 is created. The bug report
6368 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
6369 this problem do not trigger in a chroot, but I touch the file anyway
6370 to make sure the upgrade go well. Testing on virtual and real
6371 hardware have failed me because of udev so far, and creating this file
6372 do the trick in such settings anyway. This is a
6373 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
6374 issue
</a
> and the current udev behaviour is intended by the udev
6375 maintainer because he lack the resources to rewrite udev to keep
6376 working with old kernels or something like that. I really wish the
6377 udev upstream would keep udev backwards compatible, to avoid such
6378 upgrade problem, but given that they fail to do so, I guess
6379 documenting the way out of this mess is the best option we got for
6380 Debian Squeeze.
</p
>
6382 <p
>Anyway, back to the task at hand, testing upgrades. This test
6383 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
6386 <blockquote
><pre
>
6390 if [
"$
1" ] ; then
6399 exec
&lt; /dev/null
6401 mirror=http://ftp.skolelinux.org/debian
6402 tmpdir=chroot-$from-upgrade-$to-$desktop
6404 debootstrap $from $tmpdir $mirror
6405 chroot $tmpdir aptitude update
6406 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
6410 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6414 mount -t proc proc $tmpdir/proc
6415 # Make sure proc is unmounted also on failure
6416 trap exit_cleanup EXIT INT
6418 chroot $tmpdir aptitude -y install debconf-utils
6420 # Make sure tasksel autoselection trigger. It need the test scripts
6421 # to return the correct answers.
6422 echo tasksel tasksel/desktop multiselect $desktop | \
6423 chroot $tmpdir debconf-set-selections
6425 # Include the desktop and laptop task
6426 for test in desktop laptop ; do
6427 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
6431 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6434 DEBIAN_FRONTEND=noninteractive
6435 DEBIAN_PRIORITY=critical
6436 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6437 chroot $tmpdir tasksel --new-install
6439 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
6440 chroot $tmpdir aptitude update
6441 touch $tmpdir/etc/udev/kernel-upgrade
6442 chroot $tmpdir aptitude -y dist-upgrade
6444 </pre
></blockquote
>
6446 <p
>I suspect it would be useful to test upgrades with both apt-get and
6447 with aptitude, but I have not had time to look at how they behave
6448 differently so far. I hope to get a cron job running to do the test
6449 regularly and post the result on the web. The Gnome upgrade currently
6450 work, while the KDE upgrade fail because of the bug in
6451 kdebase-workspace-data
</p
>
6453 <p
>I am not quite sure what kind of extract from the huge upgrade logs
6454 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
6455 post, so I will refrain from trying. I can report that for Gnome,
6456 aptitude report
760 packages upgraded,
448 newly installed,
129 to
6457 remove and
1 not upgraded and
1024MB need to be downloaded while for
6458 KDE the same numbers are
702 packages upgraded,
507 newly installed,
6459 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
6461 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
6462 is able to migrate to dependency based boot sequencing and parallel
6463 booting without a hitch. Was unsure if there were still bugs with
6464 packages failing to clean up their obsolete init.d script during
6465 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6471 <title>Upstart or sysvinit - as init.d scripts see it
</title>
6472 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
6473 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
6474 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
6475 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
6476 scripts to migrate (some of) their operations to upstart job while
6477 keeping the init.d for hurd and kfreebsd. The packages with such
6478 needs will need a way to get their init.d scripts to behave
6479 differently when used with sysvinit and with upstart. Because of
6480 this, I had a look at the environment variables set when a init.d
6481 script is running under upstart, and when it is not.
</p
>
6483 <p
>With upstart, I notice these environment variables are set when a
6484 script is started from rcS.d/ (ignoring some irrelevant ones like
6487 <blockquote
><pre
>
6493 UPSTART_EVENTS=startup
6495 UPSTART_JOB=rc-sysinit
6496 </pre
></blockquote
>
6498 <p
>With sysvinit, these environment variables are set for the same
6501 <blockquote
><pre
>
6502 INIT_VERSION=sysvinit-
2.88
6507 </pre
></blockquote
>
6509 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
6510 sysvinit are not set by upstart. Not sure if it is intentional or not
6511 to not be compatible with sysvinit in this regard.
</p
>
6513 <p
>For scripts needing to behave differently when upstart is used,
6514 looking for the UPSTART_JOB environment variable seem to be a good
6520 <title>A manual for standards wars...
</title>
6521 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
6522 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
6523 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
6524 <description><p
>Via the
6525 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
6526 of Rob Weir
</a
> I came across the very interesting essay named
6527 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
6528 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
6529 following the standards wars of today.
</p
>
6534 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
6535 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
6536 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
6537 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
6538 <description><p
>When using sitesummary at a site to track machines, it is possible
6539 to get a list of the machine types in use thanks to the DMI
6540 information extracted from each machine. The script to do so is
6541 included in the sitesummary package, and here is example output from
6542 the Skolelinux build servers:
</p
>
6544 <blockquote
><pre
>
6545 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
6547 Dell Computer Corporation
1
6550 eserver xSeries
345 -[
8670M1X]-
1
6554 </pre
></blockquote
>
6556 <p
>The quality of the report depend on the quality of the DMI tables
6557 provided in each machine. Here there are Intel machines without model
6558 information listed with Intel as vendor and no model, and virtual Xen
6559 machines listed as [no-dmi-info]. One can add -l as a command line
6560 option to list the individual machines.
</p
>
6562 <p
>A larger list is
6563 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
6564 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
6565 provide the basic sitesummary report publicly. In their report there
6566 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
6567 their machines, and as sitesummary is available in both distributions,
6568 it is trivial to get all of them to report to the same central
6569 collector.
</p
>
6574 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
6575 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
6576 <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>
6577 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
6578 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
6579 start at boot when an NVidia video card is used is handled. The
6580 problem seem to be that the nvidia X.org driver uses a long time to
6581 initialize, and this duration is longer than kdm is configured to
6584 <p
>I came across two bugs related to this issue,
6585 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
6586 against initscripts and passed on to nvidia-glx when it became obvious
6587 that the nvidia drivers were involved, and
6588 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
6589 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
6591 <p
>To me, it seem that no-one is interested in actually solving the
6592 problem nvidia video card owners experience and make sure the Debian
6593 distribution work out of the box for these users. The nvidia driver
6594 maintainers expect kdm to be set up to wait longer, while kdm expect
6595 the nvidia driver maintainers to fix the driver to start faster, and
6596 while they wait for each other I guess the users end up switching to a
6597 distribution that work for them. I have no idea what the solution is,
6598 but I am pretty sure that waiting for each other is not it.
</p
>
6600 <p
>I wonder why we end up handling bugs this way.
</p
>
6605 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
6606 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
6607 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
6608 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
6609 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
6610 The feature seem to hold up pretty well, but three fairly serious
6611 issues are known and should be solved:
6615 <li
>The wicd package seen to
6616 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
6617 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
6618 parallel booting is enabled. No idea why, but the wicd maintainer
6619 seem to be on the case.
</li
>
6621 <li
>The nvidia X driver seem to
6622 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
6623 triggered more easily when parallel booting is in effect. The
6624 maintainer is on the case.
</li
>
6626 <li
>The sysv-rc package fail to properly enable dependency based boot
6627 sequencing (the shutdown is broken) when old file-rc users
6628 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
6629 sysv-rc. One way to solve it would be for file-rc to create
6630 /etc/init.d/.legacy-bootordering, and another is to try to make
6631 sysv-rc more robust. Will investigate some more and probably upload a
6632 workaround in sysv-rc to help those trying to move from file-rc to
6633 sysv-rc get a working shutdown.
</li
>
6635 </ul
></p
>
6637 <p
>All in all not many surprising issues, and all of them seem
6638 solvable before Squeeze is released. In addition to these there are
6639 some packages with bugs in their dependencies and run level settings,
6640 which I expect will be fixed in a reasonable time span.
</p
>
6642 <p
>If you report any problems with dependencies in init.d scripts to
6643 the BTS, please usertag the report to get it to show up at
6644 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
6645 list of usertagged bugs related to this
</a
>.
</p
>
6647 <p
>Update: Correct bug number to file-rc issue.
</p
>
6652 <title>More flexible firmware handling in debian-installer
</title>
6653 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
6654 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
6655 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
6656 <description><p
>After a long break from debian-installer development, I finally
6657 found time today to return to the project. Having to spend less time
6658 working dependency based boot in debian, as it is almost complete now,
6659 definitely helped freeing some time.
</p
>
6661 <p
>A while back, I ran into a problem while working on Debian Edu. We
6662 include some firmware packages on the Debian Edu CDs, those needed to
6663 get disk and network controllers working. Without having these
6664 firmware packages available during installation, it is impossible to
6665 install Debian Edu on the given machine, and because our target group
6666 are non-technical people, asking them to provide firmware packages on
6667 an external medium is a support pain. Initially, I expected it to be
6668 enough to include the firmware packages on the CD to get
6669 debian-installer to find and use them. This proved to be wrong.
6670 Next, I hoped it was enough to symlink the relevant firmware packages
6671 to some useful location on the CD (tried /cdrom/ and
6672 /cdrom/firmware/). This also proved to not work, and at this point I
6673 found time to look at the debian-installer code to figure out what was
6674 going to work.
</p
>
6676 <p
>The firmware loading code is in the hw-detect package, and a closer
6677 look revealed that it would only look for firmware packages outside
6678 the installation media, so the CD was never checked for firmware
6679 packages. It would only check USB sticks, floppies and other
6680 "external
" media devices. Today I changed it to also look in the
6681 /cdrom/firmware/ directory on the mounted CD or DVD, which should
6682 solve the problem I ran into with Debian edu. I also changed it to
6683 look in /firmware/, to make sure the installer also find firmware
6684 provided in the initrd when booting the installer via PXE, to allow us
6685 to provide the same feature in the PXE setup included in Debian
6688 <p
>To make sure firmware deb packages with a license questions are not
6689 activated without asking if the license is accepted, I extended
6690 hw-detect to look for preinst scripts in the firmware packages, and
6691 run these before activating the firmware during installation. The
6692 license question is asked using debconf in the preinst, so this should
6693 solve the issue for the firmware packages I have looked at so far.
</p
>
6695 <p
>If you want to discuss the details of these features, please
6696 contact us on debian-boot@lists.debian.org.
</p
>
6701 <title>Parallellized boot is now the default in Debian/unstable
</title>
6702 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
6703 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
6704 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
6705 <description><p
>Since this evening, parallel booting is the default in
6706 Debian/unstable for machines using dependency based boot sequencing.
6707 Apparently the testing of concurrent booting has been wider than
6708 expected, if I am to believe the
6709 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
6710 on debian-devel@
</a
>, and I concluded a few days ago to move forward
6711 with the feature this weekend, to give us some time to detect any
6712 remaining problems before Squeeze is frozen. If serious problems are
6713 detected, it is simple to change the default back to sequential boot.
6714 The upload of the new sysvinit package also activate a new upstream
6717 More information about
6718 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
6719 based boot sequencing
</a
> is available from the Debian wiki. It is
6720 currently possible to disable parallel booting when one run into
6721 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
6723 <blockquote
><pre
>
6725 </pre
></blockquote
>
6727 <p
>If you report any problems with dependencies in init.d scripts to
6728 the BTS, please usertag the report to get it to show up at
6729 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
6730 list of usertagged bugs related to this
</a
>.
</p
>
6735 <title>Sitesummary tip: Listing MAC address of all clients
</title>
6736 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
6737 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
6738 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
6739 <description><p
>In the recent Debian Edu versions, the
6740 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
6741 system
</a
> is used to keep track of the machines in the school
6742 network. Each machine will automatically report its status to the
6743 central server after boot and once per night. The network setup is
6744 also reported, and using this information it is possible to get the
6745 MAC address of all network interfaces in the machines. This is useful
6746 to update the DHCP configuration.
</p
>
6748 <p
>To give some idea how to use sitesummary, here is a one-liner to
6749 ist all MAC addresses of all machines reporting to sitesummary. Run
6750 this on the collector host:
</p
>
6752 <blockquote
><pre
>
6753 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
6754 </pre
></blockquote
>
6756 <p
>This will list all MAC addresses assosiated with all machine, one
6757 line per machine and with space between the MAC addresses.
</p
>
6759 <p
>To allow system administrators easier job at adding static DHCP
6760 addresses for hosts, it would be possible to extend this to fetch
6761 machine information from sitesummary and update the DHCP and DNS
6762 tables in LDAP using this information. Such tool is unfortunately not
6763 written yet.
</p
>
6768 <title>systemd, an interesting alternative to upstart
</title>
6769 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
6770 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
6771 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
6772 <description><p
>The last few days a new boot system called
6773 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
6775 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
6777 to the free software world. I have not yet had time to play around
6778 with it, but it seem to be a very interesting alternative to
6779 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
6780 a good alternative for Debian when we are able to switch to an event
6781 based boot system. Tollef is
6782 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
6783 systemd into Debian, and I look forward to seeing how well it work. I
6784 like the fact that systemd handles init.d scripts with dependency
6785 information natively, allowing them to run in parallel where upstart
6786 at the moment do not.
</p
>
6788 <p
>Unfortunately do systemd have the same problem as upstart regarding
6789 platform support. It only work on recent Linux kernels, and also need
6790 some new kernel features enabled to function properly. This means
6791 kFreeBSD and Hurd ports of Debian will need a port or a different boot
6792 system. Not sure how that will be handled if systemd proves to be the
6793 way forward.
</p
>
6795 <p
>In the mean time, based on the
6796 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
6797 on debian-devel@
</a
> regarding parallel booting in Debian, I have
6798 decided to enable full parallel booting as the default in Debian as
6799 soon as possible (probably this weekend or early next week), to see if
6800 there are any remaining serious bugs in the init.d dependencies. A
6801 new version of the sysvinit package implementing this change is
6802 already in experimental. If all go well, Squeeze will be released
6803 with parallel booting enabled by default.
</p
>
6808 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
6809 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
6810 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
6811 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
6812 <description><p
>These days, the init.d script dependencies in Squeeze are quite
6813 complete, so complete that it is actually possible to run all the
6814 init.d scripts in parallell based on these dependencies. If you want
6815 to test your Squeeze system, make sure
6816 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
6817 based boot sequencing
</a
> is enabled, and add this line to
6818 /etc/default/rcS:
</p
>
6820 <blockquote
><pre
>
6821 CONCURRENCY=makefile
6822 </pre
></blockquote
>
6824 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
6825 scripts in parallel using the dependency information stored in
6826 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
6827 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
6828 to try to start the kdm and gdm scripts as early as possible, and will
6829 start the facilities required by kdm or gdm as early as possible to
6830 make this happen.
</p
>
6832 <p
>Give it a try, and see if you like the result. If some services
6833 fail to start properly, it is most likely because they have incomplete
6834 init.d script dependencies in their startup script (or some of their
6835 dependent scripts have incomplete dependencies). Report bugs and get
6836 the package maintainers to fix it. :)
</p
>
6838 <p
>Running scripts in parallel could be the default in Debian when we
6839 manage to get the init.d script dependencies complete and correct. I
6840 expect we will get there in Squeeze+
1, if we get manage to test and
6841 fix the remaining issues.
</p
>
6843 <p
>If you report any problems with dependencies in init.d scripts to
6844 the BTS, please usertag the report to get it to show up at
6845 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
6846 list of usertagged bugs related to this
</a
>.
</p
>
6851 <title>Debian has switched to dependency based boot sequencing
</title>
6852 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
6853 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
6854 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
6855 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
6856 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
6857 have been migrated to using dependency based boot sequencing. This
6858 conclude work me and others have been doing for the last three days.
6859 It feels great to see this finally part of the default Debian
6860 installation. Now we just need to weed out the last few problems that
6861 are bound to show up, to get everything ready for Squeeze.
</p
>
6863 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
6864 fixing the more fundamental problem of handing the event based
6865 non-predictable kernel in the early boot.
</p
>
6870 <title>Taking over sysvinit development
</title>
6871 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
6872 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
6873 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
6874 <description><p
>After several years of frustration with the lack of activity from
6875 the existing sysvinit upstream developer, I decided a few weeks ago to
6876 take over the package and become the new upstream. The number of
6877 patches to track for the Debian package was becoming a burden, and the
6878 lack of synchronization between the distribution made it hard to keep
6879 the package up to date.
</p
>
6881 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
6882 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
6883 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
6884 and Fedora), based on the patches currently in use in these
6885 distributions. We Debian maintainers plan to move to this tarball as
6886 the new upstream as soon as we find time to do the merge. Since the
6887 new tarball was created, we agreed with Werner at SuSe to make a new
6888 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
6889 development there. The project is registered and currently waiting
6890 for approval by the Savannah administrators, and as soon as it is
6891 approved, we will import the old versions from svn and continue
6892 working on the future release.
</p
>
6894 <p
>It is a bit ironic that this is done now, when some of the involved
6895 distributions are moving to upstart as a syvinit replacement.
</p
>
6900 <title>Debian boots quicker and quicker
</title>
6901 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
6902 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
6903 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
6904 <description><p
>I spent Monday and tuesday this week in London with a lot of the
6905 people involved in the boot system on Debian and Ubuntu, to see if we
6906 could find more ways to speed up the boot system. This was an Ubuntu
6908 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
6909 gathering
</a
>. It was quite productive. We also discussed the future
6910 of boot systems, and ways to handle the increasing number of boot
6911 issues introduced by the Linux kernel becoming more and more
6912 asynchronous and event base. The Ubuntu approach using udev and
6913 upstart might be a good way forward. Time will show.
</p
>
6915 <p
>Anyway, there are a few ways at the moment to speed up the boot
6916 process in Debian. All of these should be applied to get a quick
6921 <li
>Use dash as /bin/sh.
</li
>
6923 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
6924 clock is in UTC.
</li
>
6926 <li
>Install and activate the insserv package to enable
6927 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
6928 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
6932 These points are based on the Google summer of code work done by
6933 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
6936 <p
>Support for makefile-style concurrency during boot was uploaded to
6937 unstable yesterday. When we tested it, we were able to cut
6 seconds
6938 from the boot sequence. It depend on very correct dependency
6939 declaration in all init.d scripts, so I expect us to find edge cases
6940 where the dependences in some scripts are slightly wrong when we start
6941 using this.
</p
>
6943 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
6944 introduced by Raphael Geissert today, one that could affect the
6945 startup speed as well. Instead of starting some scripts concurrently
6946 from rcS.d/ and another set of scripts from rc2.d/, it would be
6947 possible to run a of them in the same process. A quick way to test
6948 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
6949 insserv
'. Will need to test if that work. :)
</p
>
6954 <title>BSAs påstander om piratkopiering møter motstand
</title>
6955 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
6956 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
6957 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
6958 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
6959 programvareselskapene som Microsoft og Apple, publisert en rapport der
6960 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
6961 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
6963 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
6964 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
6965 dagene. Et spesielt interessant kommentar fra Sverige,
6966 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
6967 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
6970 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
6971 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
6972 företag.
"Man bör nog kanske inte se de här siffrorna som helt
6973 exakta
", säger BSAs Sverigechef John Hugosson.
6976 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
6977 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
6978 piracy figures need a shot of reality
</a
> og
<a
6979 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
6980 Copyright Treaty Work?
</a
></p
>
6982 <p
>Fant lenkene via
<a
6983 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
6984 på Slashdot
</a
>.
</p
>
6989 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
6990 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
6991 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
6992 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
6993 <description><p
>Kom over
6994 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
6995 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
6996 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
6997 jobber til daglig. En rask opptelling forteller meg at vi har
490
6998 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
6999 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
7000 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
7005 <title>Kryptert harddisk - naturligvis
</title>
7006 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
7007 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
7008 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
7009 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
7010 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
7011 når en tar tap av arbeidstid, fortrolige dokumenter,
7012 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7013 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7014 til at jeg har kryptert harddisken på både kontormaskinen og min
7015 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7016 komme på avveie, den første informasjon relatert til jobben min ved
7017 Universitetet i Oslo, og den andre relatert til blant annet
7018 foreningsarbeide. Kryptering av diskene gjør at det er lite
7019 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7020 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7021 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7022 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7023 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7024 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7025 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7026 det er gjort slik jeg gjør det er minimale, og gevinstene er
7027 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7028 maskinen reinstalleres og alt er tapt.
</p
>
7030 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7031 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7032 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7033 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7034 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7035 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7036 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7037 betydelige.
</p
>
7042 <title>Two projects that have improved the quality of free software a lot
</title>
7043 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
7044 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
7045 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
7046 <description><p
>There are two software projects that have had huge influence on the
7047 quality of free software, and I wanted to mention both in case someone
7048 do not yet know them.
</p
>
7050 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
7051 tool to detect and expose errors in the memory handling of programs.
7052 It is easy to use, all one need to do is to run
'valgrind program
',
7053 and it will report any problems on stdout. It is even better if the
7054 program include debug information. With debug information, it is able
7055 to report the source file name and line number where the problem
7056 occurs. It can report things like
'reading past memory block in file
7057 X line N, the memory block was allocated in file Y, line M
', and
7058 'using uninitialised value in control logic
'. This tool has made it
7059 trivial to investigate reproducible crash bugs in programs, and have
7060 reduced the number of this kind of bugs in free software a lot.
7062 <p
>The second one is
7063 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
7064 a source code checker. It is able to process the source of a program
7065 and find problems in the logic without running the program. It
7066 started out as the Stanford Checker and became well known when it was
7067 used to find bugs in the Linux kernel. It is now a commercial tool
7068 and the company behind it is running
7069 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
7070 free software community, where a lot of free software projects get
7071 their source checked for free. Several thousand defects have been
7072 found and fixed so far. It can find errors like
'lock L taken in file
7073 X line N is never released if exiting in line M
', or
'the code in file
7074 Y lines O to P can never be executed
'. The projects included in the
7075 community service project have managed to get rid of a lot of
7076 reliability problems thanks to Coverity.
</p
>
7078 <p
>I believe tools like this, that are able to automatically find
7079 errors in the source, are vital to improve the quality of software and
7080 make sure we can get rid of the crashing and failing software we are
7081 surrounded by today.
</p
>
7086 <title>No patch is not better than a useless patch
</title>
7087 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
7088 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
7089 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
7090 <description><p
>Julien Blache
7091 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
7092 patch is better than a useless patch
</a
>. I completely disagree, as a
7093 patch allow one to discuss a concrete and proposed solution, and also
7094 prove that the issue at hand is important enough for someone to spent
7095 time on fixing it. No patch do not provide any of these positive
7096 properties.
</p
>
7101 <title>Standardize on protocols and formats, not vendors and applications
</title>
7102 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
7103 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
7104 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
7105 <description><p
>Where I work at the University of Oslo, one decision stand out as a
7106 very good one to form a long lived computer infrastructure. It is the
7107 simple one, lost by many in todays computer industry: Standardize on
7108 open network protocols and open exchange/storage formats, not applications.
7109 Applications come and go, while protocols and files tend to stay, and
7110 thus one want to make it easy to change application and vendor, while
7111 avoiding conversion costs and locking users to a specific platform or
7112 application.
</p
>
7114 <p
>This approach make it possible to replace the client applications
7115 independently of the server applications. One can even allow users to
7116 use several different applications as long as they handle the selected
7117 protocol and format. In the normal case, only one client application
7118 is recommended and users only get help if they choose to use this
7119 application, but those that want to deviate from the easy path are not
7120 blocked from doing so.
</p
>
7122 <p
>It also allow us to replace the server side without forcing the
7123 users to replace their applications, and thus allow us to select the
7124 best server implementation at any moment, when scale and resouce
7125 requirements change.
</p
>
7127 <p
>I strongly recommend standardizing - on open network protocols and
7128 open formats, but I would never recommend standardizing on a single
7129 application that do not use open network protocol or open formats.
</p
>
7134 <title>Returning from Skolelinux developer gathering
</title>
7135 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
7136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
7137 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
7138 <description><p
>I
'm sitting on the train going home from this weekends Debian
7139 Edu/Skolelinux development gathering. I got a bit done tuning the
7140 desktop, and looked into the dynamic service location protocol
7141 implementation avahi. It look like it could be useful for us. Almost
7142 30 people participated, and I believe it was a great environment to
7143 get to know the Skolelinux system. Walter Bender, involved in the
7144 development of the Sugar educational platform, presented his stuff and
7145 also helped me improve my OLPC installation. He also showed me that
7146 his Turtle Art application can be used in standalone mode, and we
7147 agreed that I would help getting it packaged for Debian. As a
7148 standalone application it would be great for Debian Edu. We also
7149 tried to get the video conferencing working with two OLPCs, but that
7150 proved to be too hard for us. The application seem to need more work
7151 before it is ready for me. I look forward to getting home and relax
7157 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
7158 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
7159 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
7160 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
7161 <description><p
>The state of standardized LDAP schemas on Linux is far from
7162 optimal. There is RFC
2307 documenting one way to store NIS maps in
7163 LDAP, and a modified version of this normally called RFC
2307bis, with
7164 some modifications to be compatible with Active Directory. The RFC
7165 specification handle the content of a lot of system databases, but do
7166 not handle DNS zones and DHCP configuration.
</p
>
7168 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
7169 we would like to store information about users, SMB clients/hosts,
7170 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7171 and LTSP configuration in LDAP. These objects have a lot in common,
7172 but with the current LDAP schemas it is not possible to have one
7173 object per entity. For example, one need to have at least three LDAP
7174 objects for a given computer, one with the SMB related stuff, one with
7175 DNS information and another with DHCP information. The schemas
7176 provided for DNS and DHCP are impossible to combine into one LDAP
7177 object. In addition, it is impossible to implement quick queries for
7178 netgroup membership, because of the way NIS triples are implemented.
7179 It just do not scale. I believe it is time for a few RFC
7180 specifications to cleam up this mess.
</p
>
7182 <p
>I would like to have one LDAP object representing each computer in
7183 the network, and this object can then keep the SMB (ie host key), DHCP
7184 (mac address/name) and DNS (name/IP address) settings in one place.
7185 It need to be efficently stored to make sure it scale well.
</p
>
7187 <p
>I would also like to have a quick way to map from a user or
7188 computer and to the net group this user or computer is a member.
</p
>
7190 <p
>Active Directory have done a better job than unix heads like myself
7191 in this regard, and the unix side need to catch up. Time to start a
7192 new IETF work group?
</p
>
7197 <title>Endelig er Debian Lenny gitt ut
</title>
7198 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
7199 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
7200 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
7201 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
7202 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
7203 Et langt steg videre for Debian-prosjektet, og en rekke nye
7204 programpakker blir nå tilgjengelig for de av oss som bruker den
7205 stabile utgaven av Debian. Neste steg er nå å få
7206 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
7207 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
7208 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7209 slippes løs på skolene. Takk til alle debian-utviklerne som har
7210 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7211 bootsekvens tilgjengelig i stabil utgave, vha pakken
7212 <tt
>insserv
</tt
>.
</p
>
7217 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
7218 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
7219 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
7220 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
7221 <description><p
>This weekend we had a small developer gathering for Debian Edu in
7222 Oslo. Most of Saturday was used for the general assemly for the
7223 member organization, but the rest of the weekend I used to tune the
7224 LTSP installation. LTSP now work out of the box on the
10-network.
7225 Acer Aspire One proved to be a very nice thin client, with both
7226 screen, mouse and keybard in a small box. Was working on getting the
7227 diskless workstation setup configured out of the box, but did not
7228 finish it before the weekend was up.
</p
>
7230 <p
>Did not find time to look at the
4 VGA cards in one box we got from
7231 the Brazilian group, so that will have to wait for the next
7232 development gathering. Would love to have the Debian Edu installer
7233 automatically detect and configure a multiseat setup when it find one
7234 of these cards.
</p
>
7239 <title>The sorry state of multimedia browser plugins in Debian
</title>
7240 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
7241 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
7242 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
7243 <description><p
>Recently I have spent some time evaluating the multimedia browser
7244 plugins available in Debian Lenny, to see which one we should use by
7245 default in Debian Edu. We need an embedded video playing plugin with
7246 control buttons to pause or stop the video, and capable of streaming
7247 all the multimedia content available on the web. The test results and
7248 notes are available on
7249 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
7250 Debian wiki
</a
>. I was surprised how few of the plugins are able to
7251 fill this need. My personal video player favorite, VLC, has a really
7252 bad plugin which fail on a lot of the test pages. A lot of the MIME
7253 types I would expect to work with any free software player (like
7254 video/ogg), just do not work. And simple formats like the
7255 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
7256 totem and vlc plugins. I hope the situation will improve soon. No
7257 wonder sites use the proprietary Adobe flash to play video.
</p
>
7259 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
7260 be the only one fitting our needs. :/
</p
>