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>listadmin, the quick way to moderate mailman lists - nice free software
</title>
11 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
13 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
14 <description><p
>If you ever had to moderate a mailman list, like the ones on
15 alioth.debian.org, you know the web interface is fairly slow to
16 operate. First you visit one web page, enter the moderation password
17 and get a new page shown with a list of all the messages to moderate
18 and various options for each email address. This take a while for
19 every list you moderate, and you need to do it regularly to do a good
20 job as a list moderator. But there is a quick alternative,
21 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
22 listadmin program
</a
>. It allow you to check lists for new messages
23 to moderate in a fraction of a second. Here is a test run on two
24 lists I recently took over:
</p
>
26 <p
><blockquote
><pre
>
28 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
29 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
35 </pre
></blockquote
></p
>
37 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
38 there are no message in the moderation queue. Every morning I
39 currently moderate
68 mailman lists, and it normally take around two
40 minutes. When I took over the two pkg-xiph lists above a few days
41 ago, there were
400 emails waiting in the moderator queue. It took me
42 less than
15 minutes to process them all using the listadmin
45 <p
>If you install
46 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
47 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
48 with content like this, the moderation task is a breeze:
</p
>
50 <p
><blockquote
><pre
>
51 username username@example.org
54 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
57 adminurl https://{domain}/mailman/admindb/{list}
58 mailman-list@lists.example.com
61 other-list@otherserver.example.org
62 </pre
></blockquote
></p
>
64 <p
>There are other options to set as well. Check the manual page to
65 learn the details.
</p
>
67 <p
>If you are forced to moderate lists on a mailman installation where
68 the SSL certificate is self signed or not properly signed by a
69 generally accepted signing authority, you can set a environment
70 variable when calling listadmin to disable SSL verification:
</p
>
72 <p
><blockquote
><pre
>
73 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
74 </pre
></blockquote
></p
>
76 <p
>If you want to moderate a subset of the lists you take care of, you
77 can provide an argument to the listadmin script like I do in the
78 initial screen dump (the xiph argument). Using an argument, only
79 lists matching the argument string will be processed. This make it
80 quick to accept messages if you notice the moderation request in your
83 <p
>Without the listadmin program, I would never be the moderator of
68
84 mailing lists, as I simply do not have time to spend on that if the
85 process was any slower. The listadmin program have saved me hours of
86 time I could spend elsewhere over the years. It truly is nice free
89 <p
>As usual, if you use Bitcoin and want to show your support of my
90 activities, please send Bitcoin donations to my address
91 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
93 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
94 configuration example. Also, I
've been told that the
95 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
101 <title>Debian Jessie, PXE and automatic firmware installation
</title>
102 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
103 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
104 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
105 <description><p
>When PXE installing laptops with Debian, I often run into the
106 problem that the WiFi card require some firmware to work properly.
107 And it has been a pain to fix this using preseeding in Debian.
108 Normally something more is needed. But thanks to
109 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
110 package
</a
> and its recent tasksel extension, it has now become easy
111 to do this using simple preseeding.
</p
>
113 <p
>The isenkram-cli package provide tasksel tasks which will install
114 firmware for the hardware found in the machine (actually, requested by
115 the kernel modules for the hardware). (It can also install user space
116 programs supporting the hardware detected, but that is not the focus
117 of this story.)
</p
>
119 <p
>To get this working in the default installation, two preeseding
120 values are needed. First, the isenkram-cli package must be installed
121 into the target chroot (aka the hard drive) before tasksel is executed
122 in the pkgsel step of the debian-installer system. This is done by
123 preseeding the base-installer/includes debconf value to include the
124 isenkram-cli package. The package name is next passed to debootstrap
125 for installation. With the isenkram-cli package in place, tasksel
126 will automatically use the isenkram tasks to detect hardware specific
127 packages for the machine being installed and install them, because
128 isenkram-cli contain tasksel tasks.
</p
>
130 <p
>Second, one need to enable the non-free APT repository, because
131 most firmware unfortunately is non-free. This is done by preseeding
132 the apt-mirror-setup step. This is unfortunate, but for a lot of
133 hardware it is the only option in Debian.
</p
>
135 <p
>The end result is two lines needed in your preseeding file to get
136 firmware installed automatically by the installer:
</p
>
138 <p
><blockquote
><pre
>
139 base-installer base-installer/includes string isenkram-cli
140 apt-mirror-setup apt-setup/non-free boolean true
141 </pre
></blockquote
></p
>
143 <p
>The current version of isenkram-cli in testing/jessie will install
144 both firmware and user space packages when using this method. It also
145 do not work well, so use version
0.15 or later. Installing both
146 firmware and user space packages might give you a bit more than you
147 want, so I decided to split the tasksel task in two, one for firmware
148 and one for user space programs. The firmware task is enabled by
149 default, while the one for user space programs is not. This split is
150 implemented in the package currently in unstable.
</p
>
152 <p
>If you decide to give this a go, please let me know (via email) how
153 this recipe work for you. :)
</p
>
155 <p
>So, I bet you are wondering, how can this work. First and
156 foremost, it work because tasksel is modular, and driven by whatever
157 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
158 isenkram-cli package place two files for tasksel to find. First there
159 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
161 <p
><blockquote
><pre
>
162 Task: isenkram-packages
164 Description: Hardware specific packages (autodetected by isenkram)
165 Based on the detected hardware various hardware specific packages are
167 Test-new-install: show show
169 Packages: for-current-hardware
171 Task: isenkram-firmware
173 Description: Hardware specific firmware packages (autodetected by isenkram)
174 Based on the detected hardware various hardware specific firmware
175 packages are proposed.
176 Test-new-install: mark show
178 Packages: for-current-hardware-firmware
179 </pre
></blockquote
></p
>
181 <p
>The key parts are Test-new-install which indicate how the task
182 should be handled and the Packages line referencing to a script in
183 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
184 list of packages to install. The for-current-hardware-firmware script
185 look like this to list relevant firmware for the machine:
187 <p
><blockquote
><pre
>
192 isenkram-autoinstall-firmware -l
193 </pre
></blockquote
></p
>
195 <p
>With those two pieces in place, the firmware is installed by
196 tasksel during the normal d-i run. :)
</p
>
198 <p
>If you want to test what tasksel will install when isenkram-cli is
199 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
200 --new-install
</tt
> to get the list of packages that tasksel would
203 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
204 pilots in testing this feature, as isenkram is used there now to
205 install firmware, replacing the earlier scripts.
</p
>
210 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
211 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
212 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
213 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
214 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
215 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
216 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
217 on a screen normally showing the bread types and prizes:
</p
>
219 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
221 <p
>If it had booted as it was supposed to, I would never had known
222 about this hidden Linux installation. It is interesting what
223 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
228 <title>New lsdvd release version
0.17 is ready
</title>
229 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
230 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
231 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
232 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
233 got a new set of developers a few weeks ago, after the original
234 developer decided to step down and pass the project to fresh blood.
235 This project is now maintained by Petter Reinholdtsen and Steve
238 <p
>I just wrapped up
239 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
240 new lsdvd release
</a
>, available in git or from
241 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
242 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
247 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
248 <li
>Check for garbage in the program chains, which indicate that a track is
249 non-existant, to work around additional copy protection
</li
>
250 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
251 <li
>Fix pallete display of first entry
</li
>
252 <li
>Fix include orders
</li
>
253 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
254 <li
>Fix the chapter count
</li
>
255 <li
>Make sure the array size and the array limit used when initialising
256 the palette size is the same.
</li
>
257 <li
>Fix array printing.
</li
>
258 <li
>Correct subsecond calculations.
</li
>
259 <li
>Add sector information to the output format.
</li
>
260 <li
>Clean up code to be closer to ANSI C and compile without warnings
261 with more GCC compiler warnings.
</li
>
265 <p
>This change bring together patches for lsdvd in use in various
266 Linux and Unix distributions, as well as patches submitted to the
267 project the last nine years. Please check it out. :)
</p
>
272 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
273 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
274 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
275 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
276 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
277 project
</a
> provide a Linux solution for schools, including a
278 powerful desktop with education software, a central server providing
279 web pages, user database, user home directories, central login and PXE
280 boot of both clients without disk and the installation to install Debian
281 Edu on machines with disk (and a few other services perhaps to small
282 to mention here). We in the Debian Edu team are currently working on
283 the Jessie based version, trying to get everything in shape before the
284 freeze, to avoid having to maintain our own package repository in the
286 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
287 status
</a
> can be seen on the Debian wiki, and there is still heaps of
288 work left. Some fatal problems block testing, breaking the installer,
289 but it is possible to work around these to get anyway. Here is a
290 recipe on how to get the installation limping along.
</p
>
292 <p
>First, download the test ISO via
293 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
294 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
296 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
297 The ISO build was broken on Tuesday, so we do not get a new ISO every
298 12 hours or so, but thankfully the ISO we already got we are able to
299 install with some tweaking.
</p
>
301 <p
>When you get to the Debian Edu profile question, go to tty2
302 (use Alt-Ctrl-F2), run
</p
>
304 <p
><blockquote
><pre
>
305 nano /usr/bin/edu-eatmydata-install
306 </pre
></blockquote
></p
>
308 <p
>and add
'exit
0' as the second line, disabling the eatmydata
309 optimization. Return to the installation, select the profile you want
310 and continue. Without this change, exim4-config will fail to install
311 due to a known bug in eatmydata.
</p
>
313 <p
>When you get the grub question at the end, answer /dev/sda (or if
314 this do not work, figure out what your correct value would be. All my
315 test machines need /dev/sda, so I have no advice if it do not fit
318 <p
>If you installed a profile including a graphical desktop, log in as
319 root after the initial boot from hard drive, and install the
320 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
321 or mate. If you want several desktop options, install more than one
322 metapackage. Once this is done, reboot and you should have a working
323 graphical login screen. This workaround should no longer be needed
324 once the education-tasks package version
1.801 enter testing in two
327 <p
>I believe the ISO build will start working on two days when the new
328 tasksel package enter testing and Steve McIntyre get a chance to
329 update the debian-cd git repository. The eatmydata, grub and desktop
330 issues are already fixed in unstable and testing, and should show up
331 on the ISO as soon as the ISO build start working again. Well the
332 eatmydata optimization is really just disabled. The proper fix
333 require an upload by the eatmydata maintainer applying the patch
334 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
335 The rest have proper fixes in unstable.
</p
>
337 <p
>I hope this get you going with the installation testing, as we are
338 quickly running out of time trying to get our Jessie based
339 installation ready before the distribution freeze in a month.
</p
>
344 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
345 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
346 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
347 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
348 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
349 to handle my fairly large DVD collection. It is a nice command line
350 tool to get details about a DVD, like title, tracks, track length,
351 etc, in XML, Perl or human readable format. But lsdvd have not seen
352 any new development since
2006 and had a few irritating bugs affecting
353 its use with some DVDs. Upstream seemed to be dead, and in January I
354 sent a small probe asking for a version control repository for the
355 project, without any reply. But I use it regularly and would like to
356 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
357 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
358 the project admin, and after getting a reply from him explaining that
359 he was no longer interested in the project, I asked if I could take
360 over. And yesterday, I became project admin.
</p
>
362 <p
>I
've been in touch with a Gentoo developer and the Debian
363 maintainer interested in joining forces to maintain the upstream
364 project, and I hope we can get a new release out fairly quickly,
365 collecting the patches spread around on the internet into on place.
366 I
've added the relevant Debian patches to the freshly created git
367 repository, and expect the Gentoo patches to make it too. If you got
368 a DVD collection and care about command line tools, check out
369 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
370 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
371 list
</a
>. :)
</p
>
376 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
377 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
378 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
379 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
380 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
381 a lot quicker. When we install more than
2000 packages in
382 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
383 tasksel in the installer, unpacking the binary packages take forever.
384 A part of the slow I/O issue was discussed in
385 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
386 much file system sync-ing done by dpkg, which is the package
387 responsible for unpacking the binary packages. Other parts (like code
388 executed by postinst scripts) might also sync to disk during
389 installation. All this sync-ing to disk do not really make sense to
390 me. If the machine crash half-way through, I start over, I do not try
391 to salvage the half installed system. So the failure sync-ing is
392 supposed to protect against, hardware or system crash, is not really
393 relevant while the installer is running.
</p
>
395 <p
>A few days ago, I thought of a way to get rid of all the file
396 system sync()-ing in a fairly non-intrusive way, without the need to
397 change the code in several packages. The idea is not new, but I have
398 not heard anyone propose the approach using dpkg-divert before. It
399 depend on the small and clever package
400 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
401 uses LD_PRELOAD to replace the system functions for syncing data to
402 disk with functions doing nothing, thus allowing programs to live
403 dangerous while speeding up disk I/O significantly. Instead of
404 modifying the implementation of dpkg, apt and tasksel (which are the
405 packages responsible for selecting, fetching and installing packages),
406 it occurred to me that we could just divert the programs away, replace
407 them with a simple shell wrapper calling
408 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
409 Two days ago I decided to test the idea, and wrapped up a simple
410 implementation for the Debian Edu udeb.
</p
>
412 <p
>The effect was stunning. In my first test it reduced the running
413 time of the pkgsel step (installing tasks) from
64 to less than
44
414 minutes (
20 minutes shaved off the installation) on an old Dell
415 Latitude D505 machine. I am not quite sure what the optimised time
416 would have been, as I messed up the testing a bit, causing the debconf
417 priority to get low enough for two questions to pop up during
418 installation. As soon as I saw the questions I moved the installation
419 along, but do not know how long the question were holding up the
420 installation. I did some more measurements using Debian Edu Jessie,
421 and got these results. The time measured is the time stamp in
422 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
423 "pkgsel: finishing up
" lines, if you want to do the same measurement
424 yourself. In Debian Edu, the tasksel dialog do not show up, and the
425 timing thus do not depend on how quickly the user handle the tasksel
428 <p
><table
>
431 <th
>Machine/setup
</th
>
432 <th
>Original tasksel
</th
>
433 <th
>Optimised tasksel
</th
>
434 <th
>Reduction
</th
>
438 <td
>Latitude D505 Main+LTSP LXDE
</td
>
439 <td
>64 min (
07:
46-
08:
50)
</td
>
440 <td
><44 min (
11:
27-
12:
11)
</td
>
441 <td
>>20 min
18%
</td
>
445 <td
>Latitude D505 Roaming LXDE
</td
>
446 <td
>57 min (
08:
48-
09:
45)
</td
>
447 <td
>34 min (
07:
43-
08:
17)
</td
>
448 <td
>23 min
40%
</td
>
452 <td
>Latitude D505 Minimal
</td
>
453 <td
>22 min (
10:
37-
10:
59)
</td
>
454 <td
>11 min (
11:
16-
11:
27)
</td
>
455 <td
>11 min
50%
</td
>
459 <td
>Thinkpad X200 Minimal
</td
>
460 <td
>6 min (
08:
19-
08:
25)
</td
>
461 <td
>4 min (
08:
04-
08:
08)
</td
>
462 <td
>2 min
33%
</td
>
466 <td
>Thinkpad X200 Roaming KDE
</td
>
467 <td
>19 min (
09:
21-
09:
40)
</td
>
468 <td
>15 min (
10:
25-
10:
40)
</td
>
469 <td
>4 min
21%
</td
>
472 </table
></p
>
474 <p
>The test is done using a netinst ISO on a USB stick, so some of the
475 time is spent downloading packages. The connection to the Internet
476 was
100Mbit/s during testing, so downloading should not be a
477 significant factor in the measurement. Download typically took a few
478 seconds to a few minutes, depending on the amount of packages being
481 <p
>The speedup is implemented by using two hooks in
482 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
483 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
484 finish-install.d hook to remove the divert at the end of the
485 installation. I picked the pre-pkgsel.d hook instead of the
486 post-base-installer.d hook because I test using an ISO without the
487 eatmydata package included, and the post-base-installer.d hook in
488 Debian Edu can only operate on packages included in the ISO. The
489 negative effect of this is that I am unable to activate this
490 optimization for the kernel installation step in d-i. If the code is
491 moved to the post-base-installer.d hook, the speedup would be larger
492 for the entire installation.
</p
>
494 <p
>I
've implemented this in the
495 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
496 git repository, and plan to provide the optimization as part of the
497 Debian Edu installation. If you want to test this yourself, you can
498 create two files in the installer (or in an udeb). One shell script
499 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
501 <p
><blockquote
><pre
>
504 . /usr/share/debconf/confmodule
506 logger -t my-pkgsel
"info: $*
"
509 logger -t my-pkgsel
"error: $*
"
512 apt-install eatmydata || true
513 if [ -x /target/usr/bin/eatmydata ] ; then
514 for bin in dpkg apt-get aptitude tasksel ; do
516 # Test that the file exist and have not been diverted already.
517 if [ -f /target$file ] ; then
518 info
"diverting $file using eatmydata
"
519 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
520 > /target$file.edu
521 chmod
755 /target$file.edu
522 in-target dpkg-divert --package debian-edu-config \
523 --rename --quiet --add $file
524 ln -sf ./$bin.edu /target$file
526 error
"unable to divert $file, as it is missing.
"
530 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
535 </pre
></blockquote
></p
>
537 <p
>To clean up, another shell script should go into
538 /usr/lib/finish-install.d/ with code like this:
540 <p
><blockquote
><pre
>
542 . /usr/share/debconf/confmodule
544 logger -t my-finish-install
"error: $@
"
546 remove_install_override() {
547 for bin in dpkg apt-get aptitude tasksel ; do
549 if [ -x /target$file.edu ] ; then
551 in-target dpkg-divert --package debian-edu-config \
552 --rename --quiet --remove $file
555 error
"Missing divert for $file.
"
558 sync # Flush file buffers before continuing
561 remove_install_override
562 </pre
></blockquote
></p
>
564 <p
>In Debian Edu, I placed both code fragments in a separate script
565 edu-eatmydata-install and call it from the pre-pkgsel.d and
566 finish-install.d scripts.
</p
>
568 <p
>By now you might ask if this change should get into the normal
569 Debian installer too? I suspect it should, but am not sure the
570 current debian-installer coordinators find it useful enough. It also
571 depend on the side effects of the change. I
'm not aware of any, but I
572 guess we will see if the change is safe after some more testing.
573 Perhaps there is some package in Debian depending on sync() and
574 fsync() having effect? Perhaps it should go into its own udeb, to
575 allow those of us wanting to enable it to do so without affecting
578 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
579 will break installation of all programs using gnutls because of
580 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
581 eatmydata package in Debian will solve it.
</p
>
583 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
584 the optimization work again. And I have discovered that the
585 dpkg-divert trick is not really needed and implemented a slightly
586 simpler approach as part of the debian-edu-install package. See
587 tools/edu-eatmydata-install in the source package.
</p
>
592 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
593 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
594 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
595 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
596 <description><p
>Yesterday, I had the pleasure of attending a talk with the
597 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
598 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
599 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
600 learn that there is a large set of publicly available key servers to
601 use when looking for peoples public key. So far I have used
602 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
603 were misbehaving, but those days are ended. The servers I have used
604 up until yesterday have been slow and some times unavailable. I hope
605 those problems are gone now.
</p
>
607 <p
>Behind the round robin DNS entry of the
608 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
609 there is a pool of more than
100 keyservers which are checked every
610 day to ensure they are well connected and up to date. It must be
611 better than what I have used so far. :)
</p
>
613 <p
>Yesterdays speaker told me that the service is the default
614 keyserver provided by the default configuration in GnuPG, but this do
615 not seem to be used in Debian. Perhaps it should?
</p
>
617 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
620 <p
><blockquote
><pre
>
621 keyserver pool.sks-keyservers.net
622 </pre
></blockquote
></p
>
624 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
625 entries in DNS. Just for fun, I did just that at work, so now every
626 user of GnuPG at the University of Oslo should find a OpenGPG
627 keyserver automatically should their need it:
</p
>
629 <p
><blockquote
><pre
>
630 % host -t srv _pgpkey-http._tcp.uio.no
631 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
633 </pre
></blockquote
></p
>
636 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
637 HKP lookup protocol
</a
> supported finding signature paths, I would be
638 very happy. It can look up a given key or search for a user ID, but I
639 normally do not want that, but to find a trust path from my key to
640 another key. Given a user ID or key ID, I would like to find (and
641 download) the keys representing a signature path from my key to the
642 key in question, to be able to get a trust path between the two keys.
643 This is as far as I can tell not possible today. Perhaps something
644 for a future version of the protocol?
</p
>
649 <title>From English wiki to translated PDF and epub via Docbook
</title>
650 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
651 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
652 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
653 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
654 project
</a
> provide an instruction manual for teachers, system
655 administrators and other users that contain useful tips for setting up
656 and maintaining a Debian Edu installation. This text is about how the
657 text processing of this manual is handled in the project.
</p
>
659 <p
>One goal of the project is to provide information in the native
660 language of its users, and for this we need to handle translations.
661 But we also want to make sure each language contain the same
662 information, so for this we need a good way to keep the translations
663 in sync. And we want it to be easy for our users to improve the
664 documentation, avoiding the need to learn special formats or tools to
665 contribute, and the obvious way to do this is to make it possible to
666 edit the documentation using a web browser. We also want it to be
667 easy for translators to keep the translation up to date, and give them
668 help in figuring out what need to be translated. Here is the list of
669 tools and the process we have found trying to reach all these
672 <p
>We maintain the authoritative source of our manual in the
673 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
674 wiki
</a
>, as several wiki pages written in English. It consist of one
675 front page with references to the different chapters, several pages
676 for each chapter, and finally one
"collection page
" gluing all the
677 chapters together into one large web page (aka
678 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
679 AllInOne page
</a
>). The AllInOne page is the one used for further
680 processing and translations. Thanks to the fact that the
681 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
682 wiki.debian.org support exporting pages in
683 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
684 the list of pages to export using the raw version of the AllInOne
685 page, loop over each of them to generate a Docbook XML version of the
686 manual. This process also download images and transform image
687 references to use the locally downloaded images. The generated
688 Docbook XML files are slightly broken, so some post-processing is done
689 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
690 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
691 a handfull of images. The XML file can now be used to generate PDF, HTML
692 and epub versions of the English manual. This is the basic step of
693 our process, making PDF (using dblatex), HTML (using xsltproc) and
694 epub (using dbtoepub) version from Docbook XML, and the resulting files
695 are placed in the debian-edu-doc-en binary package.
</p
>
697 <p
>But English documentation is not enough for us. We want translated
698 documentation too, and we want to make it easy for translators to
699 track the English original. For this we use the
700 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
701 which allow us to transform the English Docbook XML file into a
702 translation file (a .pot file), usable with the normal gettext based
703 translation tools used by those translating free software. The pot
704 file is used to create and maintain translation files (several .po
705 files), which the translations update with the native language
706 translations of all titles, paragraphs and blocks of text in the
707 original. The next step is combining the original English Docbook XML
708 and the translation file (say debian-edu-wheezy-manual.nb.po), to
709 create a translated Docbook XML file (in this case
710 debian-edu-wheezy-manual.nb.xml). This translated (or partly
711 translated, if the translation is not complete) Docbook XML file can
712 then be used like the original to create a PDF, HTML and epub version
713 of the documentation.
</p
>
715 <p
>The translators use different tools to edit the .po files. We
717 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
718 while some use emacs and vi, others can use web based editors like
719 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
720 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
721 is where the .po file end up, in our git repository. Updated
722 translations can either be committed directly to git, or submitted as
723 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
724 against the debian-edu-doc package
</a
>.
</p
>
726 <p
>One challenge is images, which both might need to be translated (if
727 they show translated user applications), and are needed in different
728 formats when creating PDF and HTML versions (epub is a HTML version in
729 this regard). For this we transform the original PNG images to the
730 needed density and format during build, and have a way to provide
731 translated images by storing translated versions in
732 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
733 package maintainers know more.
</p
>
735 <p
>If you wonder what the result look like, we provide
736 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
737 of the documentation packages on the web
</a
>. See for example the
738 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
739 PDF version
</a
> or the
740 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
741 HTML version
</a
>. We do not yet build the epub version by default,
742 but perhaps it will be done in the future.
</p
>
744 <p
>To learn more, check out
745 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
746 debian-edu-doc package
</a
>,
747 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
748 manual on the wiki
</a
> and
749 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
750 translation instructions
</a
> in the manual.
</p
>
755 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
756 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
757 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
758 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
759 <description><p
>It would be nice if it was easier in Debian to get all the hardware
760 related packages relevant for the computer installed automatically.
761 So I implemented one, using
762 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
763 package
</a
>. To use it, install the tasksel and isenkram packages and
764 run tasksel as user root. You should be presented with a new option,
765 "Hardware specific packages (autodetected by isenkram)
". When you
766 select it, tasksel will install the packages isenkram claim is fit for
767 the current hardware, hot pluggable or not.
<p
>
769 <p
>The implementation is in two files, one is the tasksel menu entry
770 description, and the other is the script used to extract the list of
771 packages to install. The first part is in
772 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
775 <p
><blockquote
><pre
>
778 Description: Hardware specific packages (autodetected by isenkram)
779 Based on the detected hardware various hardware specific packages are
781 Test-new-install: mark show
783 Packages: for-current-hardware
784 </pre
></blockquote
></p
>
786 <p
>The second part is in
787 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
790 <p
><blockquote
><pre
>
795 isenkram-autoinstall-firmware -l
797 </pre
></blockquote
></p
>
799 <p
>All in all, a very short and simple implementation making it
800 trivial to install the hardware dependent package we all may want to
801 have installed on our machines. I
've not been able to find a way to
802 get tasksel to tell you exactly which packages it plan to install
803 before doing the installation. So if you are curious or careful,
804 check the output from the isenkram-* command line tools first.
</p
>
806 <p
>The information about which packages are handling which hardware is
807 fetched either from the isenkram package itself in
808 /usr/share/isenkram/, from git.debian.org or from the APT package
809 database (using the Modaliases header). The APT package database
810 parsing have caused a nasty resource leak in the isenkram daemon (bugs
811 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
812 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
813 the python-apt code (bug
814 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
815 workaround I was able to get rid of the file descriptor leak and
816 reduce the memory leak from ~
30 MiB per hardware detection down to
817 around
2 MiB per hardware detection. It should make the desktop
818 daemon a lot more useful. The fix is in version
0.7 uploaded to
819 unstable today.
</p
>
821 <p
>I believe the current way of mapping hardware to packages in
822 Isenkram is is a good draft, but in the future I expect isenkram to
823 use the AppStream data source for this. A proposal for getting proper
824 AppStream support into Debian is floating around as
825 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
826 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
827 project
</a
> will take place this summer to improve the situation. I
828 look forward to seeing the result, and welcome patches for isenkram to
829 start using the information when it is ready.
</p
>
831 <p
>If you want your package to map to some specific hardware, either
832 add a
"Xb-Modaliases
" header to your control file like I did in
833 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
834 package
</a
> or submit a bug report with the details to the isenkram
836 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
837 blog posts tagged isenkram
</a
> for details on the notation. I expect
838 the information will be migrated to AppStream eventually, but for the
839 moment I got no better place to store it.
</p
>
844 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
845 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
846 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
847 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
848 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
849 project
</a
> is working on providing the software and hardware to make
850 it easy for non-technical people to host their data and communication
851 at home, and being able to communicate with their friends and family
852 encrypted and away from prying eyes. It is still going strong, and
853 today a major mile stone was reached.
</p
>
855 <p
>Today, the last of the packages currently used by the project to
856 created the system images were accepted into Debian Unstable. It was
857 the freedombox-setup package, which is used to configure the images
858 during build and on the first boot. Now all one need to get going is
859 the build code from the freedom-maker git repository and packages from
860 Debian. And once the freedombox-setup package enter testing, we can
861 build everything directly from Debian. :)
</p
>
863 <p
>Some key packages used by Freedombox are
864 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
865 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
866 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
867 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
868 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
869 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
870 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
871 are plans to integrate more packages into the setup. User
872 documentation is maintained on the Debian wiki. Please
873 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
874 the manual
</a
> and help us improve it.
</p
>
876 <p
>To test for yourself and create boot images with the FreedomBox
877 setup, run this on a Debian machine using a user with sudo rights to
878 become root:
</p
>
881 sudo apt-get install git vmdebootstrap mercurial python-docutils \
882 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
884 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
886 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
887 </pre
></p
>
889 <p
>Root access is needed to run debootstrap and mount loopback
890 devices. See the README in the freedom-maker git repo for more
891 details on the build. If you do not want all three images, trim the
892 make line. Note that the virtualbox-image target is not really
893 virtualbox specific. It create a x86 image usable in kvm, qemu,
894 vmware and any other x86 virtual machine environment. You might need
895 the version of vmdebootstrap in Jessie to get the build working, as it
896 include fixes for a race condition with kpartx.
</p
>
898 <p
>If you instead want to install using a Debian CD and the preseed
899 method, boot a Debian Wheezy ISO and use this boot argument to load
900 the preseed values:
</p
>
903 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
904 </pre
></p
>
906 <p
>I have not tested it myself the last few weeks, so I do not know if
907 it still work.
</p
>
909 <p
>If you wonder how to help, one task you could look at is using
910 systemd as the boot system. It will become the default for Linux in
911 Jessie, so we need to make sure it is usable on the Freedombox. I did
912 a simple test a few weeks ago, and noticed dnsmasq failed to start
913 during boot when using systemd. I suspect there are other problems
914 too. :) To detect problems, there is a test suite included, which can
915 be run from the plinth web interface.
</p
>
917 <p
>Give it a go and let us know how it goes on the mailing list, and help
918 us get the new release published. :) Please join us on
919 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
920 irc.debian.org)
</a
> and
921 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
922 mailing list
</a
> if you want to help make this vision come true.
</p
>
927 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
928 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
929 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
930 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
931 <description><p
>For a while now, I have been looking for a sensible offsite backup
932 solution for use at home. My requirements are simple, it must be
933 cheap and locally encrypted (in other words, I keep the encryption
934 keys, the storage provider do not have access to my private files).
935 One idea me and my friends had many years ago, before the cloud
936 storage providers showed up, was to use Google mail as storage,
937 writing a Linux block device storing blocks as emails in the mail
938 service provided by Google, and thus get heaps of free space. On top
939 of this one can add encryption, RAID and volume management to have
940 lots of (fairly slow, I admit that) cheap and encrypted storage. But
941 I never found time to implement such system. But the last few weeks I
942 have looked at a system called
943 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
944 mounted network backed file system with the features I need.
</p
>
946 <p
>S3QL is a fuse file system with a local cache and cloud storage,
947 handling several different storage providers, any with Amazon S3,
948 Google Drive or OpenStack API. There are heaps of such storage
949 providers. S3QL can also use a local directory as storage, which
950 combined with sshfs allow for file storage on any ssh server. S3QL
951 include support for encryption, compression, de-duplication, snapshots
952 and immutable file systems, allowing me to mount the remote storage as
953 a local mount point, look at and use the files as if they were local,
954 while the content is stored in the cloud as well. This allow me to
955 have a backup that should survive fire. The file system can not be
956 shared between several machines at the same time, as only one can
957 mount it at the time, but any machine with the encryption key and
958 access to the storage service can mount it if it is unmounted.
</p
>
960 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
961 package is included already. So to get started, run
<tt
>apt-get
962 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
963 Greenqloud, after reading their nice recipe on
964 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
965 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
966 in Iceland more than those in USA when it come to keeping my personal
967 data safe and private, and thus would rather spend money on a company
968 in Iceland. Another nice recipe is available from the article
969 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
970 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
971 Admin magazine. When the provider is picked, figure out how to get
972 the API key needed to connect to the storage API. With Greencloud,
973 the key did not show up until I had added payment details to my
976 <p
>Armed with the API access details, it is time to create the file
977 system. First, create a new bucket in the cloud. This bucket is the
978 file system storage area. I picked a bucket name reflecting the
979 machine that was going to store data there, but any name will do.
980 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
981 the API login and password, and a locally created password. Store it
982 all in ~root/.s3ql/authinfo2 like this:
984 <p
><blockquote
><pre
>
986 storage-url: s3c://s.greenqloud.com:
443/bucket-name
987 backend-login: API-login
988 backend-password: API-password
989 fs-passphrase: local-password
990 </pre
></blockquote
></p
>
992 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
993 but any sensible way to create a fairly random password should do it.
994 Armed with these details, it is now time to run mkfs, entering the API
995 details and password to create it:
</p
>
997 <p
><blockquote
><pre
>
998 # mkdir -m
700 /var/lib/s3ql-cache
999 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1000 --ssl s3c://s.greenqloud.com:
443/bucket-name
1001 Enter backend login:
1002 Enter backend password:
1003 Before using S3QL, make sure to read the user
's guide, especially
1004 the
'Important Rules to Avoid Loosing Data
' section.
1005 Enter encryption password:
1006 Confirm encryption password:
1007 Generating random encryption key...
1008 Creating metadata tables...
1018 Compressing and uploading metadata...
1019 Wrote
0.00 MB of compressed metadata.
1020 #
</pre
></blockquote
></p
>
1022 <p
>The next step is mounting the file system to make the storage available.
1024 <p
><blockquote
><pre
>
1025 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1026 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
1027 Using
4 upload threads.
1028 Downloading and decompressing metadata...
1038 Mounting filesystem...
1040 Filesystem Size Used Avail Use% Mounted on
1041 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
1043 </pre
></blockquote
></p
>
1045 <p
>The file system is now ready for use. I use rsync to store my
1046 backups in it, and as the metadata used by rsync is downloaded at
1047 mount time, no network traffic (and storage cost) is triggered by
1048 running rsync. To unmount, one should not use the normal umount
1049 command, as this will not flush the cache to the cloud storage, but
1050 instead running the umount.s3ql command like this:
1052 <p
><blockquote
><pre
>
1055 </pre
></blockquote
></p
>
1057 <p
>There is a fsck command available to check the file system and
1058 correct any problems detected. This can be used if the local server
1059 crashes while the file system is mounted, to reset the
"already
1060 mounted
" flag. This is what it look like when processing a working
1061 file system:
</p
>
1063 <p
><blockquote
><pre
>
1064 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
1065 Using cached metadata.
1066 File system seems clean, checking anyway.
1067 Checking DB integrity...
1068 Creating temporary extra indices...
1069 Checking lost+found...
1070 Checking cached objects...
1071 Checking names (refcounts)...
1072 Checking contents (names)...
1073 Checking contents (inodes)...
1074 Checking contents (parent inodes)...
1075 Checking objects (reference counts)...
1076 Checking objects (backend)...
1077 ..processed
5000 objects so far..
1078 ..processed
10000 objects so far..
1079 ..processed
15000 objects so far..
1080 Checking objects (sizes)...
1081 Checking blocks (referenced objects)...
1082 Checking blocks (refcounts)...
1083 Checking inode-block mapping (blocks)...
1084 Checking inode-block mapping (inodes)...
1085 Checking inodes (refcounts)...
1086 Checking inodes (sizes)...
1087 Checking extended attributes (names)...
1088 Checking extended attributes (inodes)...
1089 Checking symlinks (inodes)...
1090 Checking directory reachability...
1091 Checking unix conventions...
1092 Checking referential integrity...
1093 Dropping temporary indices...
1094 Backing up old metadata...
1104 Compressing and uploading metadata...
1105 Wrote
0.89 MB of compressed metadata.
1107 </pre
></blockquote
></p
>
1109 <p
>Thanks to the cache, working on files that fit in the cache is very
1110 quick, about the same speed as local file access. Uploading large
1111 amount of data is to me limited by the bandwidth out of and into my
1112 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
1113 which is very close to my upload speed, and downloading the same
1114 Debian installation ISO gave me
610 kiB/s, close to my download speed.
1115 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
1116 network, not the file system code. I do not know what a good cache
1117 size would be, but suspect that the cache should e larger than your
1118 working set.
</p
>
1120 <p
>I mentioned that only one machine can mount the file system at the
1121 time. If another machine try, it is told that the file system is
1124 <p
><blockquote
><pre
>
1125 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1126 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
1127 Using
8 upload threads.
1128 Backend reports that fs is still mounted elsewhere, aborting.
1130 </pre
></blockquote
></p
>
1132 <p
>The file content is uploaded when the cache is full, while the
1133 metadata is uploaded once every
24 hour by default. To ensure the
1134 file system content is flushed to the cloud, one can either umount the
1135 file system, or ask S3QL to flush the cache and metadata using
1138 <p
><blockquote
><pre
>
1139 # s3qlctrl upload-meta /s3ql
1140 # s3qlctrl flushcache /s3ql
1142 </pre
></blockquote
></p
>
1144 <p
>If you are curious about how much space your data uses in the
1145 cloud, and how much compression and deduplication cut down on the
1146 storage usage, you can use s3qlstat on the mounted file system to get
1149 <p
><blockquote
><pre
>
1151 Directory entries:
9141
1154 Total data size:
22049.38 MB
1155 After de-duplication:
21955.46 MB (
99.57% of total)
1156 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
1157 Database size:
2.39 MB (uncompressed)
1158 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1160 </pre
></blockquote
></p
>
1162 <p
>I mentioned earlier that there are several possible suppliers of
1163 storage. I did not try to locate them all, but am aware of at least
1164 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
1165 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
1166 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
1167 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
1168 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
1169 accept payment in Bitcoin. Pick one that suit your need. Some of
1170 them provide several GiB of free storage, but the prize models are
1171 quite different and you will have to figure out what suits you
1174 <p
>While researching this blog post, I had a look at research papers
1175 and posters discussing the S3QL file system. There are several, which
1176 told me that the file system is getting a critical check by the
1177 science community and increased my confidence in using it. One nice
1179 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
1180 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1181 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
1182 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1183 and Pamela Smith. Please have a look.
</p
>
1185 <p
>Given my problems with different file systems earlier, I decided to
1186 check out the mounted S3QL file system to see if it would be usable as
1187 a home directory (in other word, that it provided POSIX semantics when
1188 it come to locking and umask handling etc). Running
1189 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
1190 test code to check file system semantics
</a
>, I was happy to discover that
1191 no error was found. So the file system can be used for home
1192 directories, if one chooses to do so.
</p
>
1194 <p
>If you do not want a locally file system, and want something that
1195 work without the Linux fuse file system, I would like to mention the
1196 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
1197 provide locally encrypted backup using a command line client. It have
1198 a nicer access control system, where one can split out read and write
1199 access, allowing some systems to write to the backup and others to
1200 only read from it.
</p
>
1202 <p
>As usual, if you use Bitcoin and want to show your support of my
1203 activities, please send Bitcoin donations to my address
1204 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1209 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
1210 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
1211 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
1212 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
1213 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
1214 project
</a
> is working on providing the software and hardware for
1215 making it easy for non-technical people to host their data and
1216 communication at home, and being able to communicate with their
1217 friends and family encrypted and away from prying eyes. It has been
1218 going on for a while, and is slowly progressing towards a new test
1219 release (
0.2).
</p
>
1221 <p
>And what day could be better than the Pi day to announce that the
1222 new version will provide
"hard drive
" / SD card / USB stick images for
1223 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1224 system), and can also be installed using a Debian installer preseed
1225 file. The Debian based Freedombox is now based on Debian Jessie,
1226 where most of the needed packages used are already present. Only one,
1227 the freedombox-setup package, is missing. To try to build your own
1228 boot image to test the current status, fetch the freedom-maker scripts
1230 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
1231 with a user with sudo access to become root:
1234 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1236 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1237 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1239 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1242 <p
>Root access is needed to run debootstrap and mount loopback
1243 devices. See the README for more details on the build. If you do not
1244 want all three images, trim the make line. But note that thanks to
<a
1245 href=
"https://bugs.debian.org/
741407">a race condition in
1246 vmdebootstrap
</a
>, the build might fail without the patch to the
1247 kpartx call.
</p
>
1249 <p
>If you instead want to install using a Debian CD and the preseed
1250 method, boot a Debian Wheezy ISO and use this boot argument to load
1251 the preseed values:
</p
>
1254 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
1257 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
1258 recently introduced bug in apt in Jessie
</a
>, the installer will
1259 currently hang while setting up APT sources. Killing the
1260 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
1261 installation will get the installation going. This affect all
1262 installations in Jessie, and I expect it will be fixed soon.
</p
>
1264 <p
>Give it a go and let us know how it goes on the mailing list, and help
1265 us get the new release published. :) Please join us on
1266 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
1267 irc.debian.org)
</a
> and
1268 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1269 mailing list
</a
> if you want to help make this vision come true.
</p
>
1274 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
1275 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
1276 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
1277 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
1278 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
1279 innetgr tools, because I needed them in
1280 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
1281 ng-utils, and it has served me well. I placed the project under the
1282 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
1283 repository. But many years ago, the CVS repository was dropped (lost,
1284 not migrated to new hardware, not sure), and the project have lacked a
1285 proper home since then.
</p
>
1287 <p
>Last summer, I had a look at the package and made a new release
1288 fixing a irritating crash bug, but was unable to store the changes in
1289 a proper source control system. I applied for a project on
1290 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
1291 to follow up on it. Until today. :)
</p
>
1293 <p
>After many hours of cleaning and migration, the ng-utils project
1294 now have a new home, and a git repository with the highlight of the
1295 history of the project. I published all release tarballs and imported
1296 them into the git repository. As the project is really stable and not
1297 expected to gain new features any time soon, I decided to make a new
1298 release and call it
1.0. Visit the new project home on
1299 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
1300 if you want to check it out. The new version is also uploaded into
1301 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
1306 <title>Testing sysvinit from experimental in Debian Hurd
</title>
1307 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
1308 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
1309 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
1310 <description><p
>A few days ago I decided to try to help the Hurd people to get
1311 their changes into sysvinit, to allow them to use the normal sysvinit
1312 boot system instead of their old one. This follow up on the
1313 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
1314 Google Summer of Code work
</a
> done last summer by Justus Winter to
1315 get Debian on Hurd working more like Debian on Linux. To get started,
1316 I downloaded a prebuilt hard disk image from
1317 <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
>,
1318 and started it using virt-manager.
</p
>
1320 <p
>The first think I had to do after logging in (root without any
1321 password) was to get the network operational. I followed
1322 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
1323 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
1324 commands as root to get the machine to accept a IP address from the
1325 kvm internal DHCP server:
</p
>
1327 <p
><blockquote
><pre
>
1328 settrans -fgap /dev/netdde /hurd/netdde
1329 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
1330 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
1332 </pre
></blockquote
></p
>
1334 <p
>After this, the machine had internet connectivity, and I could
1335 upgrade it and install the sysvinit packages from experimental and
1336 enable it as the default boot system in Hurd.
</p
>
1338 <p
>But before I did that, I set a password on the root user, as ssh is
1339 running on the machine it for ssh login to work a password need to be
1340 set. Also, note that a bug somewhere in openssh on Hurd block
1341 compression from working. Remember to turn that off on the client
1344 <p
>Run these commands as root to upgrade and test the new sysvinit
1347 <p
><blockquote
><pre
>
1348 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
1349 deb http://http.debian.net/debian/ experimental main
1352 apt-get dist-upgrade
1353 apt-get install -t experimental initscripts sysv-rc sysvinit \
1354 sysvinit-core sysvinit-utils
1355 update-alternatives --config runsystem
1356 </pre
></blockquote
></p
>
1358 <p
>To reboot after switching boot system, you have to use
1359 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
1360 yet a sysvinit process able to receive the signals from the normal
1361 'reboot
' command. After switching to sysvinit as the boot system,
1362 upgrading every package and rebooting, the network come up with DHCP
1363 after boot as it should, and the settrans/pkill hack mentioned at the
1364 start is no longer needed. But for some strange reason, there are no
1365 longer any login prompt in the virtual console, so I logged in using
1368 <p
>Note that there are some race conditions in Hurd making the boot
1369 fail some times. No idea what the cause is, but hope the Hurd porters
1370 figure it out. At least Justus said on IRC (#debian-hurd on
1371 irc.debian.org) that they are aware of the problem. A way to reduce
1372 the impact is to upgrade to the Hurd packages built by Justus by
1373 adding this repository to the machine:
</p
>
1375 <p
><blockquote
><pre
>
1376 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
1377 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1379 </pre
></blockquote
></p
>
1381 <p
>At the moment the prebuilt virtual machine get some packages from
1382 http://ftp.debian-ports.org/debian, because some of the packages in
1383 unstable do not yet include the required patches that are lingering in
1384 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
1386 <p
><blockquote
><pre
>
1387 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
1388 i emacs - GNU Emacs editor (metapackage)
1389 i gdb - GNU Debugger
1390 i hurd-recommended - Miscellaneous translators
1391 i isc-dhcp-client - ISC DHCP client
1392 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1393 i libc-bin - Embedded GNU C Library: Binaries
1394 i libc-dev-bin - Embedded GNU C Library: Development binaries
1395 i libc0.3 - Embedded GNU C Library: Shared libraries
1396 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1397 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1398 i multiarch-support - Transitional package to ensure multiarch compatibilit
1399 i A x11-common - X Window System (X.Org) infrastructure
1400 i xorg - X.Org X Window System
1401 i A xserver-xorg - X.Org X server
1402 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1404 </pre
></blockquote
></p
>
1406 <p
>All in all, testing hurd has been an interesting experience. :)
1407 X.org did not work out of the box and I never took the time to follow
1408 the porters instructions to fix it. This time I was interested in the
1409 command line stuff.
<p
>
1414 <title>New chrpath release
0.16</title>
1415 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
1416 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
1417 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
1418 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
1419 find problems in C, C++ and Java code using static source code
1420 analysis. It can detect a lot of different problems, and is very
1421 useful to find memory and locking bugs in the error handling part of
1422 the source. The company behind it provide
1423 <a href=
"https://scan.coverity.com/
">check of free software projects as
1424 a community service
</a
>, and many hundred free software projects are
1425 already checked. A few days ago I decided to have a closer look at
1426 the Coverity system, and discovered that the
1427 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
1428 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
1429 projects I am involved with was already registered. But these are
1430 fairly big, and I would also like to have a small and easy project to
1431 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
1432 checking of the chrpath project
</a
>. It was
1433 added to the checker and discovered seven potential defects. Six of
1434 these were real, mostly resource
"leak
" when the program detected an
1435 error. Nothing serious, as the resources would be released a fraction
1436 of a second later when the program exited because of the error, but it
1437 is nice to do it right in case the source of the program some time in
1438 the future end up in a library. Having fixed all defects and added
1439 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
1440 mailing list for the chrpath developers
</a
>, I decided it was time to
1441 publish a new release. These are the release notes:
</p
>
1443 <p
>New in
0.16 released
2014-
01-
14:
</p
>
1447 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
1448 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
1449 <li
>Mention new project mailing list in the documentation.
</li
>
1454 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
1455 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
1456 project if something is wrong with the new release. The test suite
1457 did not discover any old errors, so if you find a new one, please also
1458 include a test suite check.
</p
>
1463 <title>New chrpath release
0.15</title>
1464 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
1465 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
1466 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
1467 <description><p
>After many years break from the package and a vain hope that
1468 development would be continued by someone else, I finally pulled my
1469 acts together this morning and wrapped up a new release of chrpath,
1470 the command line tool to modify the rpath and runpath of already
1471 compiled ELF programs. The update was triggered by the persistence of
1472 Isha Vishnoi at IBM, which needed a new config.guess file to get
1473 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
1474 is working on. I checked the
1475 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
1476 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
1477 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
1478 packages for interesting patches (failed to find the source from
1479 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1480 These are the release notes:
</p
>
1482 <p
>New in
0.15 released
2013-
11-
24:
</p
>
1486 <li
>Updated config.sub and config.guess from the GNU project to work
1487 with newer architectures. Thanks to isha vishnoi for the heads
1490 <li
>Updated README with current URLs.
</li
>
1492 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1493 Matthias Klose.
</li
>
1495 <li
>Added missing help for -k|--keepgoing option, using patch by
1496 Petr Machata found in Fedora.
</li
>
1498 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
1499 .dynamic is a NULL terminated string. Based on patch found in
1500 Fedora credited Axel Thimm and Christian Krause.
</li
>
1505 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
1506 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
1507 project if something is wrong with the new release. The test suite
1508 did not discover any old errors, so if you find a new one, please also
1509 include a testsuite check.
</p
>
1514 <title>Debian init.d boot script example for rsyslog
</title>
1515 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
1516 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
1517 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
1518 <description><p
>If one of the points of switching to a new init system in Debian is
1519 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
1520 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
1521 init.d scripts at all. Here is an example init.d script, ie a rewrite
1522 of /etc/init.d/rsyslog:
</p
>
1524 <p
><pre
>
1525 #!/lib/init/init-d-script
1528 # Required-Start: $remote_fs $time
1529 # Required-Stop: umountnfs $time
1530 # X-Stop-After: sendsigs
1531 # Default-Start:
2 3 4 5
1532 # Default-Stop:
0 1 6
1533 # Short-Description: enhanced syslogd
1534 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1535 # It is quite compatible to stock sysklogd and can be
1536 # used as a drop-in replacement.
1538 DESC=
"enhanced syslogd
"
1539 DAEMON=/usr/sbin/rsyslogd
1540 </pre
></p
>
1542 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
1543 script was
137 lines, and the above is just
15 lines, most of it meta
1544 info/comments.
</p
>
1546 <p
>How to do this, you ask? Well, one create a new script
1547 /lib/init/init-d-script looking something like this:
1549 <p
><pre
>
1552 # Define LSB log_* functions.
1553 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
1554 # and status_of_proc is working.
1555 . /lib/lsb/init-functions
1558 # Function that starts the daemon/service
1564 #
0 if daemon has been started
1565 #
1 if daemon was already running
1566 #
2 if daemon could not be started
1567 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
1569 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1572 # Add code here, if necessary, that waits for the process to be ready
1573 # to handle requests from services started subsequently which depend
1574 # on this one. As a last resort, sleep for some time.
1578 # Function that stops the daemon/service
1583 #
0 if daemon has been stopped
1584 #
1 if daemon was already stopped
1585 #
2 if daemon could not be stopped
1586 # other if a failure occurred
1587 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
1588 RETVAL=
"$?
"
1589 [
"$RETVAL
" =
2 ]
&& return
2
1590 # Wait for children to finish too if this is a daemon that forks
1591 # and if the daemon is only ever run from this initscript.
1592 # If the above conditions are not satisfied then add some other code
1593 # that waits for the process to drop all resources that could be
1594 # needed by services started subsequently. A last resort is to
1595 # sleep for some time.
1596 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
1597 [
"$?
" =
2 ]
&& return
2
1598 # Many daemons don
't delete their pidfiles when they exit.
1600 return
"$RETVAL
"
1604 # Function that sends a SIGHUP to the daemon/service
1608 # If the daemon can reload its configuration without
1609 # restarting (for example, when it is sent a SIGHUP),
1610 # then implement that here.
1612 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
1617 scriptbasename=
"$(basename $
1)
"
1618 echo
"SN: $scriptbasename
"
1619 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
1620 script=
"$
1"
1627 NAME=$(basename $DAEMON)
1628 PIDFILE=/var/run/$NAME.pid
1630 # Exit if the package is not installed
1631 #[ -x
"$DAEMON
" ] || exit
0
1633 # Read configuration variable file if it is present
1634 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
1636 # Load the VERBOSE setting and other rcS variables
1639 case
"$
1" in
1641 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
1643 case
"$?
" in
1644 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
1645 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
1649 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
1651 case
"$?
" in
1652 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
1653 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
1657 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
1659 #reload|force-reload)
1661 # If do_reload() is not implemented then leave this commented out
1662 # and leave
'force-reload
' as an alias for
'restart
'.
1664 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
1668 restart|force-reload)
1670 # If the
"reload
" option is implemented then remove the
1671 #
'force-reload
' alias
1673 log_daemon_msg
"Restarting $DESC
" "$NAME
"
1675 case
"$?
" in
1678 case
"$?
" in
1680 1) log_end_msg
1 ;; # Old process is still running
1681 *) log_end_msg
1 ;; # Failed to start
1691 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
1697 </pre
></p
>
1699 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
1700 lot. I did not really polish the approach, so it might not always
1701 work out of the box, but you get the idea. I did not try very hard to
1702 optimize it nor make it more robust either.
</p
>
1704 <p
>A better argument for switching init system in Debian than reducing
1705 the size of init scripts (which is a good thing to do anyway), is to
1706 get boot system that is able to handle the kernel events sensibly and
1707 robustly, and do not depend on the boot to run sequentially. The boot
1708 and the kernel have not behaved sequentially in years.
</p
>
1713 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
1714 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
1715 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
1716 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
1717 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
1718 remote display access is the preferred solution with oVirt and RedHat
1719 Enterprise Virtualization, and I was sad to discover the other day
1720 that the browser plugin needed to use these systems seamlessly was
1721 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
1722 for a package
</a
> was from
2012-
04-
10 with no progress since
1723 2013-
04-
01, so I decided to wrap up a package based on the great work
1724 from Cajus Pollmeier and put it in a collab-maint maintained git
1725 repository to get a package I could use. I would very much like
1726 others to help me maintain the package (or just take over, I do not
1727 mind), but as no-one had volunteered so far, I just uploaded it to
1728 NEW. I hope it will be available in Debian in a few days.
</p
>
1730 <p
>The source is now available from
1731 <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
>
1736 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
1737 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
1738 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
1739 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
1740 <description><p
>The
1741 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
1742 program is a a very nice system to create virtual machine images. It
1743 create a image file, add a partition table, mount it and run
1744 debootstrap in the mounted directory to create a Debian system on a
1745 stick. Yesterday, I decided to try to teach it how to make images for
1746 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
1747 of a plan to simplify the build system for
1748 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
1749 project
</a
>. The FreedomBox project already uses vmdebootstrap for
1750 the virtualbox images, but its current build system made multistrap
1751 based system for Dreamplug images, and it is lacking support for
1752 Raspberry Pi.
</p
>
1754 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
1755 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1756 code and adjusted it to be able to build armel images on my amd64
1757 Debian laptop. I ended up giving vmdebootstrap five new options,
1758 allowing me to replicate the image creation process I use to make
1759 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
1760 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
1761 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
1762 call debootstrap with --foreign and to copy the handler into the
1763 generated chroot before running the second stage. This allow
1764 vmdebootstrap to create armel images on an amd64 host. Next I added
1765 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
1766 fstype
</tt
> to teach it to create a separate /boot/ partition with the
1767 given file system type, allowing me to create an image with a vfat
1768 partition for the /boot/ stuff. I also added a
<tt
>--variant
1769 variant
</tt
> option to allow me to create smaller images without the
1770 Debian base system packages installed. Finally, I added an option
1771 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
1772 as a boot loader. It is not needed on the Raspberry Pi and probably
1773 most other non-x86 architectures. The changes were accepted by the
1774 upstream author of vmdebootstrap yesterday and today, and is now
1776 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
1777 upstream project page
</a
>.
</p
>
1779 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
1780 create a small script (the customize script) to add the non-free
1781 binary blob needed to boot the Raspberry Pi and the APT source
1784 <p
><pre
>
1786 set -e # Exit on first error
1787 rootdir=
"$
1"
1788 cd
"$rootdir
"
1789 cat
&lt;
&lt;EOF
> etc/apt/sources.list
1790 deb http://http.debian.net/debian/ jessie main contrib non-free
1792 # Install non-free binary blob needed to boot Raspberry Pi. This
1793 # install a kernel somewhere too.
1794 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
1795 -O $rootdir/usr/bin/rpi-update
1796 chmod a+x $rootdir/usr/bin/rpi-update
1797 mkdir -p $rootdir/lib/modules
1798 touch $rootdir/boot/start.elf
1799 chroot $rootdir rpi-update
1800 </pre
></p
>
1802 <p
>Next, fetch the latest vmdebootstrap script and call it like this
1803 to build the image:
</p
>
1806 sudo ./vmdebootstrap \
1809 --distribution jessie \
1810 --mirror http://http.debian.net/debian \
1819 --root-password raspberry \
1820 --hostname raspberrypi \
1821 --foreign /usr/bin/qemu-arm-static \
1822 --customize `pwd`/customize \
1824 --package git-core \
1825 --package binutils \
1826 --package ca-certificates \
1829 </pre
></p
>
1831 <p
>The list of packages being installed are the ones needed by
1832 rpi-update to make the image bootable on the Raspberry Pi, with the
1833 exception of netbase, which is needed by debootstrap to find
1834 /etc/hosts with the minbase variant. I really wish there was a way to
1835 set up an Raspberry Pi using only packages in the Debian archive, but
1836 that is not possible as far as I know, because it boots from the GPU
1837 using a non-free binary blob.
</p
>
1839 <p
>The build host need debootstrap, kpartx and qemu-user-static and
1840 probably a few others installed. I have not checked the complete
1841 build dependency list.
</p
>
1843 <p
>The resulting image will not use the hardware floating point unit
1844 on the Raspberry PI, because the armel architecture in Debian is not
1845 optimized for that use. So the images created will be a bit slower
1846 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
1851 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
1852 <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>
1853 <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>
1854 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
1855 <description><p
>The last few days I came across a few good causes that should get
1856 wider attention. I recommend signing and donating to each one of
1859 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
1860 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
1861 Women program which is a Google Summer of Code like initiative to get
1862 more women involved in free software. One debian sponsor has offered
1863 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
1864 earmarked
</a
> for this initiative. I donated a few minutes ago, and
1865 hope you will to. :)
</p
>
1867 <p
>And the Electronic Frontier Foundation just announced plans to
1868 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
1869 documentaries about the excessive spying
</a
> on every Internet user that
1870 take place these days, and their need to fund the work. I
've already
1871 donated. Are you next?
</p
>
1873 <p
>For my Norwegian audience, the organisation Studentenes og
1874 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
1875 statement under the heading
1876 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
1877 Access
</a
> for those of us asking for more focus on open access in the
1878 Norwegian government. So far
499 signatures. I hope you will sign it
1884 <title>Videos about the Freedombox project - for inspiration and learning
</title>
1885 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
1886 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
1887 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
1888 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
1889 project
</a
> have been going on for a while, and have presented the
1890 vision, ideas and solution several places. Here is a little
1891 collection of videos of talks and presentation of the project.
</p
>
1895 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
1896 2,
5 minute marketing film
</a
> (Youtube)
</li
>
1898 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
1899 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
1901 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
1902 Freedom in the Cloud - Software Freedom, Privacy and and Security for
1903 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
1904 (Youtube)
</li
>
1906 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
1907 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
1909 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
1910 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
1912 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
1913 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
1914 York City in
2012</a
> (Youtube)
</li
>
1916 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
1917 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
1918 (Youtube)
</li
>
1920 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
1921 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
1923 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
1924 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
1926 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
1927 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
1928 2013</a
> (Youtube)
</li
>
1932 <p
>A larger list is available from
1933 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
1934 Freedombox Wiki
</a
>.
</p
>
1936 <p
>On other news, I am happy to report that Freedombox based on Debian
1937 Jessie is coming along quite well, and soon both Owncloud and using
1938 Tor should be available for testers of the Freedombox solution. :) In
1939 a few weeks I hope everything needed to test it is included in Debian.
1940 The withsqlite package is already in Debian, and the plinth package is
1941 pending in NEW. The third and vital part of that puzzle is the
1942 metapackage/setup framework, which is still pending an upload. Join
1943 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
1944 (#freedombox on irc.debian.org)
</a
> and
1945 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1946 mailing list
</a
> if you want to help make this vision come true.
</p
>
1951 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
1952 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
1953 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
1954 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
1955 <description><p
>I was introduced to the
1956 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
1957 in
2010, when Eben Moglen presented his vision about serving the need
1958 of non-technical people to keep their personal information private and
1959 within the legal protection of their own homes. The idea is to give
1960 people back the power over their network and machines, and return
1961 Internet back to its intended peer-to-peer architecture. Instead of
1962 depending on a central service, the Freedombox will give everyone
1963 control over their own basic infrastructure.
</p
>
1965 <p
>I
've intended to join the effort since then, but other tasks have
1966 taken priority. But this summers nasty news about the misuse of trust
1967 and privilege exercised by the
"western
" intelligence gathering
1968 communities increased my eagerness to contribute to a point where I
1969 actually started working on the project a while back.
</p
>
1971 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
1972 Debian initiative
</a
> based on the vision from Eben Moglen, is to
1973 create a simple and cheap Debian based appliance that anyone can hook
1974 up in their home and get access to secure and private services and
1975 communication. The initial deployment platform have been the
1976 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
1977 which is a piece of hardware I do not own. So to be able to test what
1978 the current Freedombox setup look like, I had to come up with a way to install
1979 it on some hardware I do have access to. I have rewritten the
1980 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
1981 image build framework to use .deb packages instead of only copying
1982 setup into the boot images, and thanks to this rewrite I am able to
1983 set up any machine supported by Debian Wheezy as a Freedombox, using
1984 the previously mentioned deb (and a few support debs for packages
1985 missing in Debian).
</p
>
1987 <p
>The current Freedombox setup consist of a set of bootstrapping
1989 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
1990 and a administrative web interface
1991 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
1992 withsqlite), as well as a privacy enhancing proxy based on
1993 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
1994 (freedombox-privoxy). There is also a web/javascript based XMPP
1995 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
1996 trying (unsuccessfully so far) to talk to the XMPP server
1997 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
1998 web interface is pluggable, and the goal is to use it to enable OpenID
1999 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2000 this is really working yet, see
2001 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
2002 project TODO
</a
> for links to GIT repositories. Most of the code is
2003 on github at the moment. The HTTP proxy is operational out of the
2004 box, and the admin web interface can be used to add/remove plinth
2005 users. I
've not been able to do anything else with it so far, but
2006 know there are several branches spread around github and other places
2007 with lots of half baked features.
</p
>
2009 <p
>Anyway, if you want to have a look at the current state, the
2010 following recipes should work to give you a test machine to poke
2013 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
2017 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
2018 <li
>Boot from it, either as CD or USB stick.
</li
>
2019 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
2020 to the Debian installer:
<p
>
2021 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
2023 <li
>Answer the few language/region/password questions and pick disk to
2024 install on.
</li
>
2026 <li
>When the installation is finished and the machine have rebooted a
2027 few times, your Freedombox is ready for testing.
</li
>
2031 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
2035 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
2036 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
2037 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
2039 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
2040 </pre
></li
>
2041 <li
><p
>Run this as root:
</p
>
2043 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2046 apt-get install freedombox-setup
2047 /usr/lib/freedombox/setup
2048 </pre
></li
>
2049 <li
>Reboot into your freshly created Freedombox.
</li
>
2053 <p
>You can test it on other architectures too, but because the
2054 freedombox-privoxy package is binary, it will only work as intended on
2055 the architectures where I have had time to build the binary and put it
2056 in my APT repository. But do not let this stop you. It is only a
2057 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
2059 <p
>Note that by default Freedombox is a DHCP server on the
2060 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
2061 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
2062 disable
</tt
>" as root.
</p
>
2064 <p
>Please let me know if this works for you, or if you have any
2065 problems. We gather on the IRC channel
2066 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
2067 irc.debian.org and the
2068 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
2069 mailing list
</a
>.
</p
>
2071 <p
>Once you get your freedombox operational, you can visit
2072 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
2073 welcome screen (dead end - do not be surprised if you are unable to
2074 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
2075 to look at the rest of plinth. The default user is
'admin
' and the
2076 default password is
'secret
'.
</p
>
2081 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
2082 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
2083 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
2084 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
2085 <description><p
>Earlier, I reported about
2086 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
2087 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
2088 told by IBM that the original disk should be thrown away. And as
2089 there no longer was a problem if I bricked the firmware, I decided
2090 today to try to install Intel firmware to replace the Lenovo firmware
2091 currently on the disk.
</p
>
2093 <p
>I searched the Intel site for firmware, and found
2094 <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
>
2095 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2096 according to the site should contain the latest firmware for SSD
2097 disks. I inserted the broken disk in one of my spare laptops and
2098 booted the ISO from a USB stick. The disk was recognized, but the
2099 program claimed the newest firmware already were installed and refused
2100 to insert any Intel firmware. So no change, and the disk is still
2101 unable to handle write load. :( I guess the only way to get them
2102 working would be if Lenovo releases new firmware. No idea how likely
2103 that is. Anyway, just blogging about this test for completeness. I
2104 got a working Samsung disk, and see no point in spending more time on
2105 the broken disks.
</p
>
2110 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
2111 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
2112 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
2113 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
2114 <description><p
>Today I switched to
2115 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
2116 new laptop
</a
>. I
've previously written about the problems I had with
2117 my new Thinkpad X230, which was delivered with an
2118 <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
2119 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
2120 sustained writes. My hardware supplier have been very forthcoming in
2121 trying to find a solution, and after first trying with another
2122 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
2123 disk instead to fix it once and for all. The Samsung disk survived
2124 the installation of Debian with encrypted disks (filling the disk with
2125 random data during installation killed the first two), and I thus
2126 decided to trust it with my data. I have installed it as a Debian Edu
2127 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2128 server at home using Kerberos and LDAP, and will use it as my work
2129 station from now on.
</p
>
2131 <p
>As this is a solid state disk with no moving parts, I believe the
2132 Debian Wheezy default installation need to be tuned a bit to increase
2133 performance and increase life time of the disk. The Linux kernel and
2134 user space applications do not yet adjust automatically to such
2135 environment. To make it easier for my self, I created a draft Debian
2136 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
2137 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
2138 for the ssd-setup package
</a
> is available from collab-maint, and it
2139 is set up to adjust the setup of the machine by just installing the
2140 package. If there is any non-SSD disk in the machine, the package
2141 will refuse to install, as I did not try to write any logic to sort
2142 file systems in SSD and non-SSD file systems.
</p
>
2144 <p
>I consider the package a draft, as I am a bit unsure how to best
2145 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2146 where I set up the machine with one large encrypted partition (in
2147 addition to /boot), put LVM on top of this and set up partitions on
2148 top of this again. See the README file in the package source for the
2149 references I used to pick the settings. At the moment these
2150 parameters are tuned:
</p
>
2154 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
2155 (adding discard to /etc/crypttab)
</li
>
2157 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
2158 this case a cryptsetup partition) by changing issue_discards from
2159 0 to
1 in /etc/lvm/lvm.conf.
</li
>
2161 <li
>Set relatime as a file system option for ext3 and ext4 file
2164 <li
>Tell swap to use TRIM commands by adding
'discard
' to
2165 /etc/fstab.
</li
>
2167 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
2169 <li
>Run fstrim on every ext3 and ext4 file system every night (from
2170 cron.daily).
</li
>
2172 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
2173 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
2177 <p
>During installation, I cancelled the part where the installer fill
2178 the disk with random data, as this would kill the SSD performance for
2179 little gain. My goal with the encrypted file system is to ensure
2180 those stealing my laptop end up with a brick and not a working
2181 computer. I have no hope in keeping the really resourceful people
2182 from getting the data on the disk (see
2183 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
2184 Thus I concluded that adding the discard option to crypttab is the
2185 right thing to do.
</p
>
2187 <p
>I considered using the noop I/O scheduler, as several recommended
2188 it for SSD, but others recommended deadline and a benchmark I found
2189 indicated that deadline might be better for interactive use.
</p
>
2191 <p
>I also considered using the
'discard
' file system option for ext3
2192 and ext4, but read that it would give a performance hit ever time a
2193 file is removed, and thought it best to that that slowdown once a day
2194 instead of during my work.
</p
>
2196 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2197 this is already done by Debian Edu.
</p
>
2199 <p
>I have not yet started on the user space tuning. I expect
2200 iceweasel need some tuning, and perhaps other applications too, but
2201 have not yet had time to investigate those parts.
</p
>
2203 <p
>The package should work on Ubuntu too, but I have not yet tested it
2206 <p
>As for the answer to the question in the title of this blog post,
2207 as far as I know, the only solution I know about is to replace the
2208 disk. It might be possible to flash it with Intel firmware instead of
2209 the Lenovo firmware. But I have not tried and did not want to do so
2210 without approval from Lenovo as I wanted to keep the warranty on the
2211 disk until a solution was found and they wanted the broken disks
2217 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
2218 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
2219 <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>
2220 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
2221 <description><p
>A few days ago, I wrote about
2222 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
2223 problems I experienced with my new X230 and its SSD disk
</a
>, which
2224 was dying during installation because it is unable to cope with
2225 sustained write. My supplier is in contact with
2226 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
2227 replacement disk to try to fix the problem. They decided to send an
2228 identical model, so my hopes for a permanent fix was slim.
</p
>
2230 <p
>Anyway, today I got the replacement disk and tried to install
2231 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2232 same firmware version as the original. This time my hope raised
2233 slightly as the installation progressed, as the original disk used to
2234 die after
4-
7% of the disk was written to, while this time it kept
2235 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
2236 died again and I was back on square one. I still do not have a new
2237 laptop with a disk I can trust. I can not live with a disk that might
2238 lock up when I download a new
2239 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
2240 other large files. I look forward to hearing from my supplier with
2241 the next proposal from Lenovo.
</p
>
2243 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
2244 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2245 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
2246 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
2247 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
2248 P/N
45N8295, P0C38732.
</p
>
2250 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
2251 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
2252 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
2253 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
2254 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
2255 P/N
45N8295, P0C38732.
</p
>
2257 <p
>The only difference is in the first number (serial number?), ISN,
2258 SA, date and WNPP values. Mentioning all the details here in case
2259 someone is able to use the information to find a way to identify the
2260 failing disk among working ones (if any such working disk actually
2266 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
2267 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
2268 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
2269 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
2270 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
2271 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2272 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
2273 member assosiation NUUG
</a
> and
2274 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
2275 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
2276 Bitraf
</a
>.
</p
>
2278 <p
>It starts
10:
00 and continue until late evening. Everyone is
2279 welcome, and there is no fee to participate. There is on the other
2280 hand limited space, and only room for
30 people. Please put your name
2281 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
2282 wiki page
</a
> if you plan to join us.
</p
>
2287 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
2288 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
2289 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
2290 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
2291 <description><p
>Half a year ago, I reported that I had to find a
2292 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
2293 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
2294 time to spend on it, and it took a while to find a model I believe
2295 will do the job, but two days ago the replacement finally arrived. I
2297 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
2298 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2299 a roaming workstation, and it seemed to work flawlessly. But my
2300 second installation with encrypted disk was not as successful. More
2301 on that below.
</p
>
2303 <p
>I had a hard time trying to track down a good laptop, as my most
2304 important requirements (robust and with a good keyboard) are never
2305 listed in the feature list. But I did get good help from the search
2306 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
2307 allowed me to limit the list of interesting laptops based on my other
2308 requirements. A bit surprising that SSD disk are not disks according
2309 to that search interface, so I had to drop specifying the number of
2310 disks from my search parameters. I also asked around among friends to
2311 get their impression on keyboards and robustness.
</p
>
2313 <p
>So the new laptop arrived, and it is quite a lot wider than the
2314 X41. I am not quite convinced about the keyboard, as it is
2315 significantly wider than my old keyboard, and I have to stretch my
2316 hand a lot more to reach the edges. But the key response is fairly
2317 good and the individual key shape is fairly easy to handle, so I hope
2318 I will get used to it. My old X40 was starting to fail, and I really
2319 needed a new laptop now. :)
</p
>
2321 <p
>Turning off the touch pad was simple. All it took was a quick
2322 visit to the BIOS during boot it disable it.
</p
>
2324 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
2325 lock up during load. And this happen when installing Debian Wheezy
2326 with encrypted disk, while the disk is being filled with random data.
2327 I also tested to install Ubuntu Raring, and it happen there too if I
2328 reenable the code to fill the disk with random data (it is disabled by
2329 default in Ubuntu). And the bug with is already known. It was
2330 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
2331 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
2332 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2333 kernel developers as
2334 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
2335 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
2336 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2337 Lenovo forums, both for
2338 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
2339 2012-
11-
10</a
> and for
2340 <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
2341 03-
20-
2013</a
>. The problem do not only affect installation. The
2342 reports state that the disk lock up during use if many writes are done
2343 on the disk, so it is much no use to work around the installation
2344 problem and end up with a computer that can lock up at any moment.
2346 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
2347 available
</a
> that will lock up the hard drive after running a few
2348 minutes by writing to a file.
</p
>
2350 <p
>I
've contacted my supplier and asked how to handle this, and after
2351 contacting PCHELP Norway (request
01D1FDP) which handle support
2352 requests for Lenovo, his first suggestion was to upgrade the disk
2353 firmware. Unfortunately there is no newer firmware available from
2354 Lenovo, as my disk already have the most recent one (version LF1i). I
2355 hope to hear more from him today and hope the problem can be
2361 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
2362 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
2363 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
2364 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
2365 <description><p
>Half a year ago, I reported that I had to find a replacement for my
2366 trusty old Thinkpad X41. Unfortunately I did not have much time to
2367 spend on it, but today the replacement finally arrived. I ended up
2368 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
2369 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
2370 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2371 this, it is installing what I hope will be a more final installation,
2372 with a encrypted hard drive to ensure any dope head stealing it end up
2373 with an expencive door stop.
</p
>
2375 <p
>I had a hard time trying to track down a good laptop, as my most
2376 important requirements (robust and with a good keyboard) are never
2377 listed in the feature list. But I did get good help from the search
2378 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
2379 allowed me to limit the list of interesting laptops based on my other
2380 requirements. A bit surprising that SSD disk are not disks, so I had
2381 to drop number of disks from my search parameters.
</p
>
2383 <p
>I am not quite convinced about the keyboard, as it is significantly
2384 wider than my old keyboard, and I have to stretch my hand a lot more
2385 to reach the edges. But the key response is fairly good and the
2386 individual key shape is fairly easy to handle, so I hope I will get
2387 used to it. My old X40 was starting to fail, and I really needed a
2388 new laptop now. :)
</p
>
2390 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
2395 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
2396 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
2397 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
2398 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
2399 <description><p
>It annoys me when the computer fail to do automatically what it is
2400 perfectly capable of, and I have to do it manually to get things
2401 working. One such task is to find out what firmware packages are
2402 needed to get the hardware on my computer working. Most often this
2403 affect the wifi card, but some times it even affect the RAID
2404 controller or the ethernet card. Today I pushed version
0.4 of the
2405 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
2406 including a new script isenkram-autoinstall-firmware handling the
2407 process of asking all the loaded kernel modules what firmware files
2408 they want, find debian packages providing these files and install the
2409 debian packages. Here is a test run on my laptop:
</p
>
2411 <p
><pre
>
2412 # isenkram-autoinstall-firmware
2413 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2414 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2415 info: locating packages with the requested firmware files
2416 info: Updating APT sources after adding non-free APT source
2417 info: trying to install firmware-ipw2x00
2420 Preconfiguring packages ...
2421 Selecting previously deselected package firmware-ipw2x00.
2422 (Reading database ...
259727 files and directories currently installed.)
2423 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2424 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
2426 </pre
></p
>
2428 <p
>When all the requested firmware is present, a simple message is
2429 printed instead:
</p
>
2431 <p
><pre
>
2432 # isenkram-autoinstall-firmware
2433 info: did not find any firmware files requested by loaded kernel modules. exiting
2435 </pre
></p
>
2437 <p
>It could use some polish, but it is already working well and saving
2438 me some time when setting up new machines. :)
</p
>
2440 <p
>So, how does it work? It look at the set of currently loaded
2441 kernel modules, and look up each one of them using modinfo, to find
2442 the firmware files listed in the module meta-information. Next, it
2443 download the Contents file from a nearby APT mirror, and search for
2444 the firmware files in this file to locate the package with the
2445 requested firmware file. If the package is in the non-free section, a
2446 non-free APT source is added and the package is installed using
2447 <tt
>apt-get install
</tt
>. The end result is a slightly better working
2450 <p
>I hope someone find time to implement a more polished version of
2451 this script as part of the hw-detect debian-installer module, to
2452 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
2453 #
655507</a
>. There really is no need to insert USB sticks with
2454 firmware during a PXE install when the packages already are available
2455 from the nearby Debian mirror.
</p
>
2460 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
2461 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
2462 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
2463 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
2464 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2465 the screen just turn black when Linux boot, either during installation
2466 or on first boot from the hard disk. I
've seen it once in a while the
2467 last few years, but only recently understood the cause. I
've seen it
2468 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2469 The reason seem to be in the wiring of some laptops. The system to
2470 control the screen background light is inverted, so when Linux try to
2471 turn the brightness fully on, it end up turning it off instead. I do
2472 not know which Linux drivers are affected, but this post is about the
2473 i915 driver used by the
2474 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
2475 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
2477 <p
>The problem can be worked around two ways. Either by adding
2478 i915.invert_brightness=
1 as a kernel option, or by adding a file in
2479 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
2480 option when it load the i915 kernel module. On Debian and Ubuntu, it
2481 can be done by running these commands as root:
</p
>
2484 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
2485 update-initramfs -u -k all
2488 <p
>Since March
2012 there is
2489 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
2490 mechanism in the Linux kernel
</a
> to tell the i915 driver which
2491 hardware have this problem, and get the driver to invert the
2492 brightness setting automatically. To use it, one need to add a row in
2493 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
2494 intel_quirks array
</a
> in the driver source
2495 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
2496 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
2497 number (vendor number
8086 is assumed) and subdevice vendor and device
2500 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
2501 -vvnn
</tt
> for the video card in question:
</p
>
2503 <p
><pre
>
2504 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
2505 3rd Gen Core processor Graphics Controller [
8086:
0156] \
2506 (rev
09) (prog-if
00 [VGA controller])
2507 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
2508 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2509 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2510 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
2511 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
2513 Interrupt: pin A routed to IRQ
42
2514 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
2515 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
2516 Region
4: I/O ports at
4000 [size=
64]
2517 Expansion ROM at
<unassigned
> [disabled]
2518 Capabilities:
<access denied
>
2519 Kernel driver in use: i915
2520 </pre
></p
>
2522 <p
>The resulting intel_quirks entry would then look like this:
</p
>
2524 <p
><pre
>
2525 struct intel_quirk intel_quirks[] = {
2527 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2528 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
2531 </pre
></p
>
2533 <p
>According to the kernel module instructions (as seen using
2534 <tt
>modinfo i915
</tt
>), information about hardware needing the
2535 invert_brightness flag should be sent to the
2536 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
2537 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
2538 developers. But my email about the laptop sent
2013-
06-
03 have not
2540 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
2541 web archive for the mailing list
</a
>, so I suspect they do not accept
2542 emails from non-subscribers. Because of this, I sent my patch also to
2543 the Debian bug tracking system instead as
2544 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
2545 sure the patch is not lost.
</p
>
2547 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
2548 with this problem working properly with Linux. If you use Gnome, your
2549 worries should be over at this point. But if you use KDE, there is
2550 something in KDE ignoring the invert_brightness setting and turning on
2551 the screen during login. I
've reported it to Debian as
2552 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
2553 have no idea yet how to figure out exactly what subsystem is doing
2554 this. Perhaps you can help? Perhaps you know what the Gnome
2555 developers did to handle this, and this can give a clue to the KDE
2556 developers? Or you know where in KDE the screen brightness is changed
2557 during login? If so, please update the BTS report (or get in touch if
2558 you do not know how to update BTS).
</p
>
2560 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
2561 acpi_backlight=vendor, to disable ACPI backlight support completely,
2562 as the ACPI information on the machine is trash and it is better to
2563 leave it to the intel video driver to control the screen
2564 backlight.
</p
>
2569 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
2570 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
2571 <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>
2572 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
2573 <description><p
>Two days ago, I asked
2574 <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
2575 I could install Linux on a Packard Bell EasyNote LV computer
2576 preinstalled with Windows
8</a
>. I found a solution, but am horrified
2577 with the obstacles put in the way of Linux users on a laptop with UEFI
2578 and Windows
8.
</p
>
2580 <p
>I never found out if the cause of my problems were the use of UEFI
2581 secure booting or fast boot. I suspect fast boot was the problem,
2582 causing the firmware to boot directly from HD without considering any
2583 key presses and alternative devices, but do not know UEFI settings
2584 enough to tell.
</p
>
2586 <p
>There is no way to install Linux on the machine in question without
2587 opening the box and disconnecting the hard drive! This is as far as I
2588 can tell, the only way to get access to the firmware setup menu
2589 without accepting the Windows
8 license agreement. I am told (and
2590 found description on how to) that it is possible to configure the
2591 firmware setup once booted into Windows
8. But as I believe the terms
2592 of that agreement are completely unacceptable, accepting the license
2593 was never an alternative. I do not enter agreements I do not intend
2594 to follow.
</p
>
2596 <p
>I feared I had to return the laptops and ask for a refund, and
2597 waste many hours on this, but luckily there was a way to get it to
2598 work. But I would not recommend it to anyone planning to run Linux on
2599 it, and I have become sceptical to Windows
8 certified laptops. Is
2600 this the way Linux will be forced out of the market place, by making
2601 it close to impossible for
"normal
" users to install Linux without
2602 accepting the Microsoft Windows license terms? Or at least not
2603 without risking to loose the warranty?
</p
>
2605 <p
>I
've updated the
2606 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
2607 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
2608 do not have to struggle as much as I did to get Linux into the
2611 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2612 Michael Tokarev and others for feedback and ideas.
</p
>
2617 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
2618 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
2619 <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>
2620 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
2621 <description><p
>I
've run into quite a problem the last few days. I bought three
2622 new laptops for my parents and a few others. I bought Packard Bell
2623 Easynote LV to run Kubuntu on and use as their home computer. But I
2624 am completely unable to figure out how to install Linux on it. The
2625 computer is preinstalled with Windows
8, and I suspect it uses UEFI
2626 instead of a BIOS to boot.
</p
>
2628 <p
>The problem is that I am unable to get it to PXE boot, and unable
2629 to get it to boot the Linux installer from my USB stick. I have yet
2630 to try the DVD install, and still hope it will work. when I turn on
2631 the computer, there is no information on what buttons to press to get
2632 the normal boot menu. I expect to get some boot menu to select PXE or
2633 USB stick booting. When booting, it first ask for the language to
2634 use, then for some regional settings, and finally if I will accept the
2635 Windows
8 terms of use. As these terms are completely unacceptable to
2636 me, I have no other choice but to turn off the computer and try again
2637 to get it to boot the Linux installer.
</p
>
2639 <p
>I have gathered my findings so far on a Linlap page about the
2640 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
2641 EasyNote LV
</a
> model. If you have any idea how to get Linux
2642 installed on this machine, please get in touch or update that wiki
2643 page. If I can
't find a way to install Linux, I will have to return
2644 the laptop to the seller and find another machine for my parents.
</p
>
2646 <p
>I wonder, is this the way Linux will be forced out of the market
2647 using UEFI and
"secure boot
" by making it impossible to install Linux
2648 on new Laptops?
</p
>
2653 <title>How to transform a Debian based system to a Debian Edu installation
</title>
2654 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
2655 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
2656 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
2657 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
2658 an operating system based on Debian intended for use in schools. It
2659 contain a turn-key solution for the computer network provided to
2660 pupils in the primary schools. It provide both the central server,
2661 network boot servers and desktop environments with heaps of
2662 educational software. The project was founded almost
12 years ago,
2663 2001-
07-
02. If you want to support the project, which is in need for
2664 cash to fund developer gatherings and other project related activity,
2665 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
2666 donate some money
</a
>.
2668 <p
>A topic that come up again and again on the Debian Edu mailing
2669 lists and elsewhere, is the question on how to transform a Debian or
2670 Ubuntu installation into a Debian Edu installation. It isn
't very
2671 hard, and last week I wrote a script to replicate the steps done by
2672 the Debian Edu installer.
</p
>
2674 <p
>The script,
2675 <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/
>
2676 in the debian-edu-config package, will go through these six steps and
2677 transform an existing Debian Wheezy or Ubuntu (untested) installation
2678 into a Debian Edu Workstation:
</p
>
2682 <li
>Add skolelinux related APT sources.
</li
>
2683 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
2684 <li
>Install debian-edu-install to load preseeding values and pull in
2685 our configuration.
</li
>
2686 <li
>Preseed debconf database with profile setup in
2687 /etc/debian-edu/config, and run tasksel to install packages
2688 according to the profile specified in the config above,
2689 overriding some of the Debian automation machinery.
</li
>
2690 <li
>Run debian-edu-cfengine-D installation to configure everything
2691 that could not be done using preseeding.
</li
>
2692 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
2696 <p
>There are some steps in the Debian Edu installation that can not be
2697 replicated like this. Disk partitioning and LVM setup, for example.
2698 So this script just assume there is enough disk space to install all
2699 the needed packages.
</p
>
2701 <p
>The script was created to help a Debian Edu student working on
2702 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
2703 Debian Edu client, and using it he can take the existing
2704 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
2705 transform it into a fully functioning Debian Edu Workstation (or
2706 Roaming Workstation, or whatever :).
</p
>
2708 <p
>The default setting in the script is to create a KDE Workstation.
2709 If a LXDE based Roaming workstation is wanted instead, modify the
2710 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
2712 <p
><pre
>
2713 PROFILE=
"Roaming-Workstation
"
2714 DESKTOP=
"lxde
"
2715 </pre
></p
>
2717 <p
>The script could even become useful to set up Debian Edu servers in
2718 the cloud, by starting with a virtual Debian installation at some
2719 virtual hosting service and setting up all the services on first
2725 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
2726 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
2727 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
2728 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
2729 <description><P
>In January,
2730 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
2731 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
2732 channel #debian-lego
</a
>, for those of us in the Debian and Linux
2733 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
2734 marvellous construction system from Denmark. We also created
2735 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
2736 a place to take notes and write down our plans and hopes. And several
2737 people showed up to help. I was very happy to see the effect of my
2738 call. Since the small start, we have a debtags tag
2739 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
2740 tag for LEGO related packages, and now count
10 packages related to
2741 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
2743 <p
><table
>
2744 <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
>
2745 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
2746 <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
>
2747 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
2748 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
2749 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
2750 <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
>
2751 <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
>
2752 <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
>
2753 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
2754 </table
></p
>
2756 <p
>Some of these are available in Wheezy, and all but one are
2757 currently available in Jessie/testing. leocad is so far only
2758 available in experimental.
</p
>
2760 <p
>If you care about LEGO in Debian, please join us on IRC and help
2761 adding the rest of the great free software tools available on Linux
2762 for LEGO designers.
</p
>
2767 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
2768 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
2769 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
2770 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
2771 <description><p
>When I woke up this morning, I was very happy to see that the
2772 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
2773 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
2774 Debian release, and I expect to move my machines at home over to it fairly
2777 <p
>The new debian release contain heaps of new stuff, and one program
2778 in particular make me very happy to see included. The
2779 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
2780 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
2781 included for the first time. Alongside similar programs like
2782 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
2783 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
2784 it allow for visual programming where syntax errors can not happen,
2785 and a friendly programming environment for learning to control the
2786 computer. Scratch will also be included in the next release of Debian
2789 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
2790 Edu/Skolelinux release too. The
2791 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
2792 alpha release
</a
> went out last week, and the next should soon
2798 <title>Isenkram
0.2 finally in the Debian archive
</title>
2799 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
2800 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
2801 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
2802 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
2803 package
</a
> finally made it into the archive, after lingering in NEW
2804 for many months. I uploaded it to the Debian experimental suite
2805 2013-
01-
27, and today it was accepted into the archive.
</p
>
2807 <p
>Isenkram is a system for suggesting to users what packages to
2808 install to work with a pluggable hardware device. The suggestion pop
2809 up when the device is plugged in. For example if a Lego Mindstorm NXT
2810 is inserted, it will suggest to install the program needed to program
2811 the NXT controller. Give it a go, and report bugs and suggestions to
2817 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
2818 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
2819 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
2820 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
2821 <description><p
>My
2822 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
2823 bitcoin related blog post
</a
> mentioned that the new
2824 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
2825 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
2826 2013-
01-
19, and have been available in unstable since then. It was
2827 automatically copied to Ubuntu, and is available in their Raring
2828 version too.
</p
>
2830 <p
>But there is a strange problem with the build that block this new
2831 version from being available on the i386 and kfreebsd-i386
2832 architectures. For some strange reason, the autobuilders in Debian
2833 for these architectures fail to run the test suite on these
2834 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
2835 We are so far unable to reproduce it when building it manually, and
2836 no-one have been able to propose a fix. If you got an idea what is
2837 failing, please let us know via the BTS.
</p
>
2839 <p
>One feature that is annoying me with of the bitcoin client, because
2840 I often run low on disk space, is the fact that the client will exit
2841 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
2842 #
696715</a
>). So make sure you have enough disk space when you run
2845 <p
>As usual, if you use bitcoin and want to show your support of my
2846 activities, please send Bitcoin donations to my address
2847 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2852 <title>Welcome to the world, Isenkram!
</title>
2853 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
2854 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
2855 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
2856 <description><p
>Yesterday, I
2857 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
2858 for testers
</a
> for my prototype for making Debian better at handling
2859 pluggable hardware devices, which I
2860 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
2861 out to create
</a
> earlier this month. Several valuable testers showed
2862 up, and caused me to really want to to open up the development to more
2863 people. But before I did this, I want to come up with a sensible name
2864 for this project. Today I finally decided on a new name, and I have
2865 renamed the project from hw-support-handler to this new name. In the
2866 process, I moved the source to git and made it available as a
2867 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
2868 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
2869 To fetch and build the latest version of the source, use
</p
>
2872 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
2873 cd isenkram
&& git-buildpackage -us -uc
2876 <p
>I have not yet adjusted all files to use the new name yet. If you
2877 want to hack on the source or improve the package, please go ahead.
2878 But please talk to me first on IRC or via email before you do major
2879 changes, to make sure we do not step on each others toes. :)
</p
>
2881 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
2882 stuff, typically meaning tools, nails, screws, etc. Typical hardware
2883 stuff, in other words. I
've been told it is the Norwegian variant of
2884 the German word eisenkram, for those that are familiar with that
2887 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
2888 instructions, to avoid confusing people with an error from the signing
2891 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
2892 clone argument to avoid the need for authentication.
</p
>
2897 <title>First prototype ready making hardware easier to use in Debian
</title>
2898 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
2899 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
2900 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
2901 <description><p
>Early this month I set out to try to
2902 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
2903 the Debian support for pluggable hardware devices
</a
>. Now my
2904 prototype is working, and it is ready for a larger audience. To test
2906 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
2907 from the Debian Edu subversion repository
</a
>, build and install the
2908 package. You might have to log out and in again activate the
2909 autostart script.
</p
>
2911 <p
>The design is simple:
</p
>
2915 <li
>Add desktop entry in /usr/share/autostart/ causing a program
2916 hw-support-handlerd to start when the user log in.
</li
>
2918 <li
>This program listen for kernel events about new hardware (directly
2919 from the kernel like udev does), not using HAL dbus events as I
2920 initially did.
</li
>
2922 <li
>When new hardware is inserted, look up the hardware modalias in
2923 the APT database, a database
2924 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
2925 via HTTP
</a
> and a database available as part of the package.
</li
>
2927 <li
>If a package is mapped to the hardware in question, the package
2928 isn
't installed yet and this is the first time the hardware was
2929 plugged in, show a desktop notification suggesting to install the
2930 package or packages.
</li
>
2932 <li
>If the user click on the
'install package now
' button, ask
2933 aptdaemon via the PackageKit API to install the requrired package.
</li
>
2935 <li
>aptdaemon ask for root password or sudo password, and install the
2936 package while showing progress information in a window.
</li
>
2940 <p
>I still need to come up with a better name for the system. Here
2941 are some screen shots showing the prototype in action. First the
2942 notification, then the password request, and finally the request to
2943 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
2945 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
2946 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
2947 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
2948 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
2949 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
2951 <p
>The prototype still need to be improved with longer timeouts, but
2952 is already useful. The database of hardware to package mappings also
2953 need more work. It is currently compatible with the Ubuntu way of
2954 storing such information in the package control file, but could be
2955 changed to use other formats instead or in addition to the current
2956 method. I
've dropped the use of discover for this mapping, as the
2957 modalias approach is more flexible and easier to use on Linux as long
2958 as the Linux kernel expose its modalias strings directly.
</p
>
2960 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
2961 here is the command required to check out and build the source: Use
2962 '<tt
>svn checkout
2963 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
2964 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
2965 devscripts package.
</p
>
2967 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
2968 renamed to Isenkram and the source moved from the Debian Edu
2969 subversion repository to a Debian collab-maint git repository. See
2970 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
2971 instructions
</a
> for details.
</p
>
2976 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
2977 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
2978 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
2979 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
2980 <description><p
>This Christmas my trusty old laptop died. It died quietly and
2981 suddenly in bed. With a quiet whimper, it went completely quiet and
2982 black. The power button was no longer able to turn it on. It was a
2983 IBM Thinkpad X41, and the best laptop I ever had. Better than both
2984 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
2985 Compaq I had before that. Now I need to find a replacement. To keep
2986 going during Christmas, I moved the one year old SSD disk to my old
2987 X40 where it fitted (only one I had left that could use it), but it is
2988 not a durable solution.
2990 <p
>My laptop needs are fairly modest. This is my wishlist from when I
2991 got a new one more than
10 years ago. It still holds true.:)
</p
>
2995 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
2996 than A4).
</li
>
2997 <li
>Robust, it will be in my backpack every day.
</li
>
2998 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
2999 <li
>Long battery life time. Preferable a week.
</li
>
3000 <li
>Internal WIFI network card.
</li
>
3001 <li
>Internal Twisted Pair network card.
</li
>
3002 <li
>Some USB slots (
2-
3 is plenty)
</li
>
3003 <li
>Good keyboard - similar to the Thinkpad.
</li
>
3004 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
3006 <li
>Hardware supported by Debian Stable, ie the default kernel and
3007 X.org packages.
</li
>
3008 <li
>Quiet, preferably fan free (or at least not using the fan most of
3013 <p
>You will notice that there are no RAM and CPU requirements in the
3014 list. The reason is simply that the specifications on laptops the
3015 last
10-
15 years have been sufficient for my needs, and I have to look
3016 at other features to choose my laptop. But are there still made as
3017 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3018 robust, and Thinkpads seem to be heading in the wrong direction since
3019 Lenovo took over. But I
've been told that X220 and X1 Carbon might
3020 still be useful.
</p
>
3022 <p
>Perhaps I should rethink my needs, and look for a pad with an
3023 external keyboard? I
'll have to check the
3024 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
3025 well-supported laptops, or perhaps just buy one preinstalled from one
3026 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
3027 Pre-loaded site
</a
>.
</p
>
3032 <title>How to find a browser plugin supporting a given MIME type
</title>
3033 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
3034 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
3035 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
3036 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
3037 install to get support for a given MIME type. Thanks to
3038 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
3039 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
3040 Unfortunately, not very many packages provide the needed meta
3041 information, Anyway, here is a small script to look up all browser
3042 plugin packages announcing ther MIME support using this specification:
</p
>
3048 def pkgs_handling_mimetype(mimetype):
3053 version = pkg.candidate
3055 version = pkg.installed
3058 record = version.record
3059 if not record.has_key(
'Npp-MimeType
'):
3061 mime_types = record[
'Npp-MimeType
'].split(
',
')
3062 for t in mime_types:
3063 t = t.rstrip().strip()
3065 thepkgs.append(pkg.name)
3067 mimetype =
"audio/ogg
"
3068 if
1 < len(sys.argv):
3069 mimetype = sys.argv[
1]
3070 print
"Browser plugin packages supporting %s:
" % mimetype
3071 for pkg in pkgs_handling_mimetype(mimetype):
3072 print
" %s
" %pkg
3075 <p
>It can be used like this to look up a given MIME type:
</p
>
3078 % ./apt-find-browserplug-for-mimetype
3079 Browser plugin packages supporting audio/ogg:
3081 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3082 Browser plugin packages supporting application/x-shockwave-flash:
3083 browser-plugin-gnash
3087 <p
>In Ubuntu this mechanism is combined with support in the browser
3088 itself to query for plugins and propose to install the needed
3089 packages. It would be great if Debian supported such feature too. Is
3090 anyone working on adding it?
</p
>
3092 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
3093 request for icweasel support for this feature is
3094 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
3095 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
3096 of manpower and wish for a different design is the reason thus feature
3097 is not yet in iceweasel from Debian.
</p
>
3102 <title>What is the most supported MIME type in Debian?
</title>
3103 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
3104 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
3105 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
3106 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
3107 proposal to add AppStream information to the Debian archive
</a
>, is a
3108 proposal to make it possible for a Desktop application to propose to
3109 the user some package to install to gain support for a given MIME
3110 type, font, library etc. that is currently missing. With such
3111 mechanism in place, it would be possible for the desktop to
3112 automatically propose and install leocad if some LDraw file is
3113 downloaded by the browser.
</p
>
3115 <p
>To get some idea about the current content of the archive, I decided
3116 to write a simple program to extract all .desktop files from the
3117 Debian archive and look up the claimed MIME support there. The result
3119 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
3120 site
</a
>. Using the collected information, it become possible to
3121 answer the question in the title. Here are the
20 most supported MIME
3122 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3123 The complete list is available from the link above.
</p
>
3125 <p
><strong
>Debian Stable:
</strong
></p
>
3129 ----- -----------------------
3145 18 application/x-ogg
3152 <p
><strong
>Debian Testing:
</strong
></p
>
3156 ----- -----------------------
3172 18 application/x-ogg
3179 <p
><strong
>Debian Unstable:
</strong
></p
>
3183 ----- -----------------------
3200 18 application/x-ogg
3206 <p
>I am told that PackageKit can provide an API to access the kind of
3207 information mentioned in DEP-
11. I have not yet had time to look at
3208 it, but hope the PackageKit people in Debian are on top of these
3211 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
3212 discovering a typo in my script.
</p
>
3217 <title>Using modalias info to find packages handling my hardware
</title>
3218 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
3219 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
3220 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
3221 <description><p
>Yesterday, I wrote about the
3222 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
3223 values provided by the Linux kernel
</a
> following my hope for
3224 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
3225 dongle support in Debian
</a
>. Using this knowledge, I have tested how
3226 modalias values attached to package names can be used to map packages
3227 to hardware. This allow the system to look up and suggest relevant
3228 packages when I plug in some new hardware into my machine, and replace
3229 discover and discover-data as the database used to map hardware to
3232 <p
>I create a modaliases file with entries like the following,
3233 containing package name, kernel module name (if relevant, otherwise
3234 the package name) and globs matching the relevant hardware
3237 <p
><blockquote
>
3238 Package: package-name
3239 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
3240 </blockquote
></p
>
3242 <p
>It is fairly trivial to write code to find the relevant packages
3243 for a given modalias value using this file.
</p
>
3245 <p
>An entry like this would suggest the video and picture application
3246 cheese for many USB web cameras (interface bus class
0E01):
</p
>
3248 <p
><blockquote
>
3250 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
3251 </blockquote
></p
>
3253 <p
>An entry like this would suggest the pcmciautils package when a
3254 CardBus bridge (bus class
0607) PCI device is present:
</p
>
3256 <p
><blockquote
>
3257 Package: pcmciautils
3258 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3259 </blockquote
></p
>
3261 <p
>An entry like this would suggest the package colorhug-client when
3262 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
3264 <p
><blockquote
>
3265 Package: colorhug-client
3266 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
3267 </blockquote
></p
>
3269 <p
>I believe the format is compatible with the format of the Packages
3270 file in the Debian archive. Ubuntu already uses their Packages file
3271 to store their mappings from packages to hardware.
</p
>
3273 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
3274 announce the hardware it support in a way my prototype understand.
3275 This allow those publishing packages in an APT source outside the
3276 Debian archive as well as those backporting packages to make sure the
3277 hardware mapping are included in the package meta information. I
've
3278 tested such header in the pymissile package, and its modalias mapping
3279 is working as it should with my prototype. It even made it to Ubuntu
3282 <p
>To test if it was possible to look up supported hardware using only
3283 the shell tools available in the Debian installer, I wrote a shell
3284 implementation of the lookup code. The idea is to create files for
3285 each modalias and let the shell do the matching. Please check out and
3287 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
3288 shell script. It run without any extra dependencies and fetch the
3289 hardware mappings from the Debian archive and the subversion
3290 repository where I currently work on my prototype.
</p
>
3292 <p
>When I use it on a machine with a yubikey inserted, it suggest to
3293 install yubikey-personalization:
</p
>
3295 <p
><blockquote
>
3296 % ./hw-support-lookup
3297 <br
>yubikey-personalization
3299 </blockquote
></p
>
3301 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3302 propose to install the pcmciautils package:
</p
>
3304 <p
><blockquote
>
3305 % ./hw-support-lookup
3306 <br
>pcmciautils
3308 </blockquote
></p
>
3310 <p
>If you know of any hardware-package mapping that should be added to
3311 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
3312 database
</a
>, please tell me about it.
</p
>
3314 <p
>It could be possible to generate several of the mappings between
3315 packages and hardware. One source would be to look at packages with
3316 kernel modules, ie packages with *.ko files in /lib/modules/, and
3317 extract their modalias information. Another would be to look at
3318 packages with udev rules, ie packages with files in
3319 /lib/udev/rules.d/, and extract their vendor/model information to
3320 generate a modalias matching rule. I have not tested any of these to
3321 see if it work.
</p
>
3323 <p
>If you want to help implementing a system to let us propose what
3324 packages to install when new hardware is plugged into a Debian
3325 machine, please send me an email or talk to me on
3326 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
3331 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
3332 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
3333 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
3334 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
3335 <description><p
>While looking into how to look up Debian packages based on hardware
3336 information, to find the packages that support a given piece of
3337 hardware, I refreshed my memory regarding modalias values, and decided
3338 to document the details. Here are my findings so far, also available
3340 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
3341 Debian Edu subversion repository
</a
>:
3343 <p
><strong
>Modalias decoded
</strong
></p
>
3345 <p
>This document try to explain what the different types of modalias
3346 values stands for. It is in part based on information from
3347 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
3348 &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;,
3349 &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
3350 &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;.
3352 <p
>The modalias entries for a given Linux machine can be found using
3353 this shell script:
</p
>
3356 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
3359 <p
>The supported modalias globs for a given kernel module can be found
3360 using modinfo:
</p
>
3363 % /sbin/modinfo psmouse | grep alias:
3364 alias: serio:ty05pr*id*ex*
3365 alias: serio:ty01pr*id*ex*
3369 <p
><strong
>PCI subtype
</strong
></p
>
3371 <p
>A typical PCI entry can look like this. This is an Intel Host
3372 Bridge memory controller:
</p
>
3374 <p
><blockquote
>
3375 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3376 </blockquote
></p
>
3378 <p
>This represent these values:
</p
>
3383 sv
00001028 (subvendor)
3384 sd
000001AD (subdevice)
3386 sc
00 (bus subclass)
3390 <p
>The vendor/device values are the same values outputted from
'lspci
3391 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
3392 0600. The
0600 class is a host bridge. Other useful bus values are
3393 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
3395 <p
>Not sure how to figure out the interface value, nor what it
3398 <p
><strong
>USB subtype
</strong
></p
>
3400 <p
>Some typical USB entries can look like this. This is an internal
3401 USB hub in a laptop:
</p
>
3403 <p
><blockquote
>
3404 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3405 </blockquote
></p
>
3407 <p
>Here is the values included in this alias:
</p
>
3410 v
1D6B (device vendor)
3411 p
0001 (device product)
3413 dc
09 (device class)
3414 dsc
00 (device subclass)
3415 dp
00 (device protocol)
3416 ic
09 (interface class)
3417 isc
00 (interface subclass)
3418 ip
00 (interface protocol)
3421 <p
>The
0900 device class/subclass means hub. Some times the relevant
3422 class is in the interface class section. For a simple USB web camera,
3423 these alias entries show up:
</p
>
3425 <p
><blockquote
>
3426 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3427 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3428 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3429 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3430 </blockquote
></p
>
3432 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
3433 camera),
0101 is audio control device and
0102 is audio streaming (aka
3434 microphone). Thus this is a camera with microphone included.
</p
>
3436 <p
><strong
>ACPI subtype
</strong
></p
>
3438 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
3439 receiver in a Thinkpad X40:
</p
>
3441 <p
><blockquote
>
3442 acpi:IBM0071:PNP0511:
3443 </blockquote
></p
>
3445 <p
>The values between the colons are IDs.
</p
>
3447 <p
><strong
>DMI subtype
</strong
></p
>
3449 <p
>The DMI table contain lots of information about the computer case
3450 and model. This is an entry for a IBM Thinkpad X40, fetched from
3451 /sys/devices/virtual/dmi/id/modalias:
</p
>
3453 <p
><blockquote
>
3454 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3455 </blockquote
></p
>
3457 <p
>The values present are
</p
>
3460 bvn IBM (BIOS vendor)
3461 bvr
1UETB
6WW(
1.66) (BIOS version)
3462 bd
06/
15/
2005 (BIOS date)
3463 svn IBM (system vendor)
3464 pn
2371H4G (product name)
3465 pvr ThinkPadX40 (product version)
3466 rvn IBM (board vendor)
3467 rn
2371H4G (board name)
3468 rvr NotAvailable (board version)
3469 cvn IBM (chassis vendor)
3470 ct
10 (chassis type)
3471 cvr NotAvailable (chassis version)
3474 <p
>The chassis type
10 is Notebook. Other interesting values can be
3475 found in the dmidecode source:
</p
>
3479 4 Low Profile Desktop
3492 17 Main Server Chassis
3493 18 Expansion Chassis
3495 20 Bus Expansion Chassis
3496 21 Peripheral Chassis
3498 23 Rack Mount Chassis
3507 <p
>The chassis type values are not always accurately set in the DMI
3508 table. For example my home server is a tower, but the DMI modalias
3509 claim it is a desktop.
</p
>
3511 <p
><strong
>SerIO subtype
</strong
></p
>
3513 <p
>This type is used for PS/
2 mouse plugs. One example is from my
3514 test machine:
</p
>
3516 <p
><blockquote
>
3517 serio:ty01pr00id00ex00
3518 </blockquote
></p
>
3520 <p
>The values present are
</p
>
3529 <p
>This type is supported by the psmouse driver. I am not sure what
3530 the valid values are.
</p
>
3532 <p
><strong
>Other subtypes
</strong
></p
>
3534 <p
>There are heaps of other modalias subtypes according to
3535 file2alias.c. There is the rest of the list from that source: amba,
3536 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3537 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3538 vmbus, x86cpu and zorro. I did not spend time documenting all of
3539 these, as they do not seem relevant for my intended use with mapping
3540 hardware to packages when new stuff is inserted during run time.
</p
>
3542 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
3544 <p
>To check which kernel modules provide support for a given modalias,
3545 one can use the following shell script:
</p
>
3548 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
3549 echo
"$id
" ; \
3550 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
3554 <p
>The output can look like this (only the first few entries as the
3555 list is very long on my test machine):
</p
>
3559 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
3561 FATAL: Module acpi:device: not found.
3563 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
3564 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
3565 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
3566 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3567 acpi:IBM0071:PNP0511:
3568 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
3569 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
3570 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
3574 <p
>If you want to help implementing a system to let us propose what
3575 packages to install when new hardware is plugged into a Debian
3576 machine, please send me an email or talk to me on
3577 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
3579 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
3580 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
3581 in /sys/ with space in them.
</p
>
3586 <title>Moved the pymissile Debian packaging to collab-maint
</title>
3587 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
3588 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
3589 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
3590 <description><p
>As part of my investigation on how to improve the support in Debian
3591 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3592 Launcher and updated the Debian package
3593 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
3594 sure udev will fix the device permissions when it is plugged in. I
3595 also added a
"Modaliases
" header to test it in the Debian archive and
3596 hopefully make the package be proposed by jockey in Ubuntu when a user
3597 plug in his rocket launcher. In the process I moved the source to a
3598 git repository under collab-maint, to make it easier for any DD to
3599 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
3600 is not very active, but the software still work for me even after five
3601 years of relative silence. The new git repository is not listed in
3602 the uploaded package yet, because I want to test the other changes a
3603 bit more before I upload the new version. If you want to check out
3604 the new version with a .desktop file included, visit the
3605 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
3606 view
</a
> or use
"<tt
>git clone
3607 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
3612 <title>Lets make hardware dongles easier to use in Debian
</title>
3613 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
3614 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
3615 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
3616 <description><p
>One thing that annoys me with Debian and Linux distributions in
3617 general, is that there is a great package management system with the
3618 ability to automatically install software packages by downloading them
3619 from the distribution mirrors, but no way to get it to automatically
3620 install the packages I need to use the hardware I plug into my
3621 machine. Even if the package to use it is easily available from the
3622 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3623 suggest to automatically install the python-nxt, nbc and t2n packages
3624 I need to talk to it. When I plug in a Yubikey, it could propose the
3625 yubikey-personalization package. The information required to do this
3626 is available, but no-one have pulled all the pieces together.
</p
>
3628 <p
>Some years ago, I proposed to
3629 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
3630 the discover subsystem to implement this
</a
>. The idea is fairly
3635 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
3636 starting when a user log in.
</li
>
3638 <li
>Set this program up to listen for kernel events emitted when new
3639 hardware is inserted into the computer.
</li
>
3641 <li
>When new hardware is inserted, look up the hardware ID in a
3642 database mapping to packages, and take note of any non-installed
3643 packages.
</li
>
3645 <li
>Show a message to the user proposing to install the discovered
3646 package, and make it easy to install it.
</li
>
3650 <p
>I am not sure what the best way to implement this is, but my
3651 initial idea was to use dbus events to discover new hardware, the
3652 discover database to find packages and
3653 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
3656 <p
>Yesterday, I found time to try to implement this idea, and the
3657 draft package is now checked into
3658 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
3659 Debian Edu subversion repository
</a
>. In the process, I updated the
3660 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
3661 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3662 the relevant packages in Debian, and uploaded a new version
3663 2.2013.01.09 to unstable. I also discovered that the current
3664 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
3665 package in Debian no longer discovered any USB devices, because
3666 /proc/bus/usb/devices is no longer present. I ported it to use
3667 libusb as a fall back option to get it working. The fixed package
3668 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
3669 because of the freeze).
</p
>
3671 <p
>With this prototype in place, I can insert my Yubikey, and get this
3672 desktop notification to show up (only once, the first time it is
3673 inserted):
</p
>
3675 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
3677 <p
>For this prototype to be really useful, some way to automatically
3678 install the proposed packages by pressing the
"Please install
3679 program(s)
" button should to be implemented.
</p
>
3681 <p
>If this idea seem useful to you, and you want to help make it
3682 happen, please help me update the discover-data database with mappings
3683 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
3684 list the package you would like to have installed when a given
3685 hardware device is inserted into your computer, and report bugs using
3686 reportbug if it isn
't. Or, if you know of a better way to provide
3687 such mapping, please let me know.
</p
>
3689 <p
>This prototype need more work, and there are several questions that
3690 should be considered before it is ready for production use. Is dbus
3691 the correct way to detect new hardware? At the moment I look for HAL
3692 dbus events on the system bus, because that is the events I could see
3693 on my Debian Squeeze KDE desktop. Are there better events to use?
3694 How should the user be notified? Is the desktop notification
3695 mechanism the best option, or should the background daemon raise a
3696 popup instead? How should packages be installed? When should they
3697 not be installed?
</p
>
3699 <p
>If you want to help getting such feature implemented in Debian,
3700 please send me an email. :)
</p
>
3705 <title>New IRC channel for LEGO designers using Debian
</title>
3706 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
3707 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
3708 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
3709 <description><p
>During Christmas, I have worked a bit on the Debian support for
3710 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
3711 NXT
</a
>. My son and I have played a bit with my NXT set, and I
3712 discovered I had to build all the tools myself because none were
3713 already in Debian Squeeze. If Debian support for LEGO is something
3714 you care about, please join me on the IRC channel
3715 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
3716 irc.debian.org). There is a lot that could be done to improve the
3717 Debian support for LEGO designers. For example both CAD software
3718 and Mindstorm compilers are missing. :)
</p
>
3720 <p
>Update
2012-
01-
03: A
3721 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
3722 including links to Lego related packages is now available.
</p
>
3727 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
3728 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
3729 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
3730 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
3731 <description><p
>Let me start by wishing you all marry Christmas and a happy new
3732 year! I hope next year will prove to be a good year.
</p
>
3734 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
3735 decentralised
"currency
" that allow people to transfer bitcoins
3736 between each other with minimal overhead, is a very interesting
3737 experiment. And as I wrote a few days ago, the bitcoin situation in
3738 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
3739 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
3740 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
3741 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
3742 for one of the ftpmasters to approve the new bitcoin-qt package
3745 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
3746 team in Debian, you can easily test the package in Debian Squeeze
3747 using the following steps to get a set of working packages:
</p
>
3749 <blockquote
><pre
>
3750 git clone git://git.debian.org/git/collab-maint/bitcoin
3752 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3753 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3754 </pre
></blockquote
>
3756 <p
>You might have to install some build dependencies as well. The
3757 list of commands should give you two packages, bitcoind and
3758 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3759 client will download the complete set of bitcoin
"blocks
", which need
3760 around
5.6 GiB of data on my machine at the moment. Make sure your
3761 ~/.bitcoin/ directory have lots of spare room if you want to download
3762 all the blocks. The client will warn if the disk is getting full, so
3763 there is not really a problem if you got too little room, but you will
3764 not be able to get all the features out of the client.
</p
>
3766 <p
>As usual, if you use bitcoin and want to show your support of my
3767 activities, please send Bitcoin donations to my address
3768 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3773 <title>A word on bitcoin support in Debian
</title>
3774 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
3775 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
3776 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
3777 <description><p
>It has been a while since I wrote about
3778 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
3779 peer-to-peer based crypto-currency, and the reason is simply that I
3780 have been busy elsewhere. But two days ago, I started looking at the
3781 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
3782 Debian
</a
> again to try to recover my old bitcoin wallet. The package
3783 is now maintained by a
3784 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
3785 people
</a
>, and the grunt work had already been done by this team. We
3786 owe a huge thank you to all these team members. :)
3787 But I was sad to discover that the bitcoin client is missing in
3788 Wheezy. It is only available in Sid (and an outdated client from
3789 backports). The client had several RC bugs registered in BTS blocking
3790 it from entering testing. To try to help the team and improve the
3791 situation, I spent some time providing patches and triaging the bug
3792 reports. I also had a look at the bitcoin package available from Matt
3794 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
3795 Ubuntu
</a
>, and moved the useful pieces from that version into the
3796 Debian package.
</p
>
3798 <p
>After checking with the main package maintainer Jonas Smedegaard on
3799 IRC, I pushed several patches into the collab-maint git repository to
3800 improve the package. It now contains fixes for the RC issues (not from
3801 me, but fixed by Scott Howard), build rules for a Qt GUI client
3802 package, konqueror support for the bitcoin: URI and bash completion
3803 setup. As I work on Debian Squeeze, I also created
3804 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
3805 patch to backport
</a
> the latest version. Jonas is going to look at
3806 it and try to integrate it into the git repository before uploading a
3807 new version to unstable.
3809 <p
>I would very much like bitcoin to succeed, to get rid of the
3810 centralized control currently exercised in the monetary system. I
3811 find it completely unacceptable that the USA government is collecting
3812 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
3813 that the major credit card companies can block legal money
3814 transactions to Wikileaks. But for bitcoin to succeed, more people
3815 need to use bitcoins, and more people need to accept bitcoins when
3816 they sell products and services. Improving the bitcoin support in
3817 Debian is a small step in the right direction, but not enough.
3818 Unfortunately the user experience when browsing the web and wanting to
3819 pay with bitcoin is still not very good. The bitcoin: URI is a step
3820 in the right direction, but need to work in most or every browser in
3821 use. Also the bitcoin-qt client is too heavy to fire up to do a
3822 quick transaction. I believe there are other clients available, but
3823 have not tested them.
</p
>
3826 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
3827 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
3828 I received
20.15 BTC so far on the address I provided in my blog two
3829 years ago, as can be
3830 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
3831 on the blockexplorer service
</a
>. Thank you everyone for your
3832 donation. The blockexplorer service demonstrates quite well that
3833 bitcoin is not quite anonymous and untracked. :) I wonder if the
3834 number of users have gone up since then. If you use bitcoin and want
3835 to show your support of my activity, please send Bitcoin donations to
3836 the same address as last time,
3837 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3842 <title>Git repository for song book for Computer Scientists
</title>
3843 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
3844 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
3845 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
3846 <description><p
>As I
3847 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
3848 this summer
</a
>, I have created a Computer Science song book a few
3849 years ago, and today I finally found time to create a public
3850 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
3851 repository for the project
</a
>.
</p
>
3853 <p
>If you want to help out, please clone the source and submit patches
3854 to the HTML version. To generate the PDF and PostScript version,
3855 please use prince XML, or let me know about a useful free software
3856 processor capable of creating a good looking PDF from the HTML.
</p
>
3858 <p
>Want to sing? You can still find the song book in HTML, PDF and
3859 PostScript formats at
3860 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
3861 Science Songbook
</a
>.
</p
>
3866 <title>Gratulerer med
19-årsdagen, Debian!
</title>
3867 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
3868 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
3869 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
3870 <description><p
>I dag fyller
3871 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
3872 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
3873 si gratulerer med dagen, Debian!
</p
>
3878 <title>Song book for Computer Scientists
</title>
3879 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
3880 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
3881 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
3882 <description><p
>Many years ago, while studying Computer Science at the
3883 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
3884 collecting computer related songs for use at parties. The original
3885 version was written in LaTeX, but a few years ago I got help from
3886 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
3887 while keeping the ability to create a nice book in PDF format. I have
3888 not had time to maintain the book for a while now, and guess I should
3889 put it up on some public version control repository where others can
3890 help me extend and update the book. If anyone is volunteering to help
3891 me with this, send me an email. Also let me know if there are songs
3892 missing in my book.
</p
>
3894 <p
>I have not mentioned the book on my blog so far, and it occured to
3895 me today that I really should let all my readers share the joys of
3896 singing out load about programming, computers and computer networks.
3897 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
3898 12</a
> is about to start (and I am not going). Want to sing? Check
3899 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
3900 Computer Science Songbook
</a
>.
3905 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
3906 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
3907 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
3908 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
3909 <description><p
>At work we have heaps of servers. I believe the total count is
3910 around
1000 at the moment. To be able to get help from the vendors
3911 when something go wrong, we want to keep the firmware on the servers
3912 up to date. If the firmware isn
't the latest and greatest, the
3913 vendors typically refuse to start debugging any problems until the
3914 firmware is upgraded. So before every reboot, we want to upgrade the
3915 firmware, and we would really like everyone handling servers at the
3916 university to do this themselves when they plan to reboot a machine.
3917 For that to happen we at the unix server admin group need to provide
3918 the tools to do so.
</p
>
3920 <p
>To make firmware upgrading easier, I am working on a script to
3921 fetch and install the latest firmware for the servers we got. Most of
3922 our hardware are from Dell and HP, so I have focused on these servers
3923 so far. This blog post is about the Dell part.
</P
>
3925 <p
>On the Dell FTP site I was lucky enough to find
3926 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
3927 with firmware information for all
11th generation servers, listing
3928 which firmware should be used on a given model and where on the FTP
3929 site I can find it. Using a simple perl XML parser I can then
3930 download the shell scripts Dell provides to do firmware upgrades from
3931 within Linux and reboot when all the firmware is primed and ready to
3932 be activated on the first reboot.
</p
>
3934 <p
>This is the Dell related fragment of the perl code I am working on.
3935 Are there anyone working on similar tools for firmware upgrading all
3936 servers at a site? Please get in touch and lets share resources.
</p
>
3938 <p
><pre
>
3942 use File::Temp qw(tempdir);
3944 # Install needed RHEL packages if missing
3946 'XML::Simple
' =
> 'perl-XML-Simple
',
3948 for my $module (keys %rhelmodules) {
3949 eval
"use $module;
";
3951 my $pkg = $rhelmodules{$module};
3952 system(
"yum install -y $pkg
");
3953 eval
"use $module;
";
3957 my $errorsto =
'pere@hungry.com
';
3963 sub run_firmware_script {
3964 my ($opts, $script) = @_;
3966 print STDERR
"fail: missing script name\n
";
3969 print STDERR
"Running $script\n\n
";
3971 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
3972 print STDERR
"success: firmware script ran succcessfully\n
";
3974 print STDERR
"fail: firmware script returned error\n
";
3978 sub run_firmware_scripts {
3979 my ($opts, @dirs) = @_;
3980 # Run firmware packages
3981 for my $dir (@dirs) {
3982 print STDERR
"info: Running scripts in $dir\n
";
3983 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
3984 while (my $s = readdir $dh) {
3985 next if $s =~ m/^\.\.?/;
3986 run_firmware_script($opts,
"$dir/$s
");
3994 print STDERR
"info: Downloading $url\n
";
3995 system(
"wget --quiet \
"$url\
"");
4000 my $product = `dmidecode -s system-product-name`;
4003 if ($product =~ m/PowerEdge/) {
4005 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4006 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
4008 my $tmpdir = tempdir(
4012 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
4013 system(
'gunzip Catalog.xml.gz
');
4014 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
4015 # -q is quiet, disabling interactivity and reducing console output
4016 my $fwopts =
"-q
";
4018 for my $url (@paths) {
4019 fetch_dell_fw($url);
4021 run_firmware_scripts($fwopts, $tmpdir);
4023 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
4024 print STDERR
"error: Please report to $errorsto.\n
";
4028 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
4029 print STDERR
"error: Please report to $errorsto.\n
";
4035 my $url =
"ftp://ftp.us.dell.com/$path
";
4039 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4040 # firmware packages to download from Dell. Only work for Linux
4041 # machines and
11th generation Dell servers.
4042 sub fetch_dell_fw_list {
4043 my $filename = shift;
4045 my $product = `dmidecode -s system-product-name`;
4047 my ($mybrand, $mymodel) = split(/\s+/, $product);
4049 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
4051 my $xml = XMLin($filename);
4053 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
4054 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
4055 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
4057 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
4058 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
4060 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
4062 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
4064 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
4067 for my $component (@{$xml-
>{SoftwareComponent}}) {
4068 my $componenttype = $component-
>{ComponentType}-
>{value};
4070 # Drop application packages, only firmware and BIOS
4071 next if
'APAC
' eq $componenttype;
4073 my $cpath = $component-
>{path};
4074 for my $path (@paths) {
4075 if ($cpath =~ m%/$path$%) {
4076 push(@paths, $cpath);
4084 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
4085 it could work on other platforms with some tweaking. Anyone know a
4086 index like Catalog.xml is available from HP for HP servers? At the
4087 moment I maintain a similar list manually and it is quickly getting
4093 <title>How is booting into runlevel
1 different from single user boots?
</title>
4094 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
4095 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
4096 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
4097 <description><p
>Wouter Verhelst have some
4098 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
4099 comments and opinions
</a
> on my blog post on
4100 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
4101 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
4102 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
4103 default KDE desktop in Debian
</a
>. I only have time to address one
4104 small piece of his comment now, and though it best to address the
4105 misunderstanding he bring forward:
</p
>
4107 <p
><blockquote
>
4108 Currently, a system admin has four options: [...] boot to a
4109 single-user system (by adding
'single
' to the kernel command line;
4110 this runs rcS and rc1 scripts)
4111 </blockquote
></p
>
4113 <p
>This make me believe Wouter believe booting into single user mode
4114 and booting into runlevel
1 is the same. I am not surprised he
4115 believe this, because it would make sense and is a quite sensible
4116 thing to believe. But because the boot in Debian is slightly broken,
4117 runlevel
1 do not work properly and it isn
't the same as single user
4118 mode. I
'll try to explain what is actually happing, but it is a bit
4119 hard to explain.
</p
>
4121 <p
>Single user mode is defined like this in /etc/inittab:
4122 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
4123 executed in single user mode is sulogin. Single user mode is a boot
4124 state
"between
" the runlevels, and when booting into single user mode,
4125 only the scripts in /etc/rcS.d/ are executed before the init process
4126 enters the single user state. When switching to runlevel
1, the state
4127 is in fact not ending in runlevel
1, but it passes through runlevel
1
4128 and end up in the single user mode (see /etc/rc1.d/S03single, which
4129 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
4130 1. It is confusing that the
'S
' (single user) init mode is not the
4131 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4134 <p
>This summary might make it clearer. When booting for the first
4135 time into single user mode, the following commands are executed:
4136 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
4137 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
4138 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
4139 trying to continue after visiting single user mode. Not all services
4140 are started again as they should, causing the machine to end up in an
4141 unpredicatble state. This is why Debian admins recommend rebooting
4142 after visiting single user mode.
</p
>
4144 <p
>A similar problem with runlevel
1 is caused by the amount of
4145 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
4146 to runlevel
1, the services started from /etc/rcS.d/ are not properly
4147 stopped when passing through the scripts in /etc/rc1.d/, and not
4148 started again when switching away from runlevel
1 to the runlevels
4149 2-
5. I believe the problem is best fixed by moving all the scripts
4150 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
4151 functioning single user mode during boot.
</p
>
4153 <p
>I have spent several years investigating the Debian boot system,
4154 and discovered this problem a few years ago. I suspect it originates
4155 from when sysvinit was introduced into Debian, a long time ago.
</p
>
4160 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
4161 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
4162 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
4163 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
4164 <description><p
>In the Debian boot system, several packages include scripts that
4165 are started from /etc/rcS.d/. In fact, there is a bite more of them
4166 than make sense, and this causes a few problems. What kind of
4167 problems, you might ask. There are at least two problems. The first
4168 is that it is not possible to recover a machine after switching to
4169 runlevel
1. One need to actually reboot to get the machine back to
4170 the expected state. The other is that single user boot will sometimes
4171 run into problems because some of the subsystems are activated before
4172 the root login is presented, causing problems when trying to recover a
4173 machine from a problem in that subsystem. A minor additional point is
4174 that moving more scripts out of rcS.d/ and into the other rc#.d/
4175 directories will increase the amount of scripts that can run in
4176 parallel during boot, and thus decrease the boot time.
</p
>
4178 <p
>So, which scripts should start from rcS.d/. In short, only the
4179 scripts that _have_ to execute before the root login prompt is
4180 presented during a single user boot should go there. Everything else
4181 should go into the numeric runlevels. This means things like
4182 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4183 the numeric runlevels. Today in Debian, there are around
115 init.d
4184 scripts that are started from rcS.d/, and most of them should be moved
4185 out. Do your package have one of them? Please help us make single
4186 user and runlevel
1 better by moving it.
</p
>
4188 <p
>Scripts setting up the screen, keyboard, system partitions
4189 etc. should still be started from rcS.d/, but there is for example no
4190 need to have the network enabled before the single user login prompt
4191 is presented.
</p
>
4193 <p
>As always, things are not so easy to fix as they sound. To keep
4194 Debian systems working while scripts migrate and during upgrades, the
4195 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4196 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4197 and the next ones can only be moved when their dependencies have been
4198 moved first. This migration must be done sequentially while we ensure
4199 that the package system upgrade packages in the right order to keep
4200 the system state correct. This will require some coordination when it
4201 comes to network related packages, but most of the packages with
4202 scripts that should migrate do not have anything in rcS.d/ depending
4203 on them. Some packages have already been updated, like the sudo
4204 package, while others are still left to do. I wish I had time to work
4205 on this myself, but real live constrains make it unlikely that I will
4206 find time to push this forward.
</p
>
4211 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
4212 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
4213 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
4214 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
4215 <description><p
>While at Debconf11, I have several times during discussions
4216 mentioned the issues I believe should be improved in Debian for its
4217 desktop to be useful for more people. The use case for this is my
4218 parents, which are currently running Kubuntu which solve the
4221 <p
>I suspect these four missing features are not very hard to
4222 implement. After all, they are present in Ubuntu, so if we wanted to
4223 do this in Debian we would have a source.
</p
>
4227 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
4228 are new packages available for upgrades, a icon in the KDE status bar
4229 indicate this, and clicking on it will activate the simple upgrade
4230 tool to handle it. I have no problem guiding both of my parents
4231 through the process over the phone. If a kernel reboot is required,
4232 this too is indicated by the status bars and the upgrade tool. Last
4233 time I checked, nothing with the same features was working in KDE in
4236 <li
><strong
>Simple handling of missing Firefox browser
4237 plugins.
</strong
> When the browser encounter a MIME type it do not
4238 currently have a handler for, it will ask the user if the system
4239 should search for a package that would add support for this MIME type,
4240 and if the user say yes, the APT sources will be searched for packages
4241 advertising the MIME type in their control file (visible in the
4242 Packages file in the APT archive). If one or more packages are found,
4243 it is a simple click of the mouse to add support for the missing mime
4244 type. If the package require the user to accept some non-free
4245 license, this is explained to the user. The entire process make it
4246 more clear to the user why something do not work in the browser, and
4247 make the chances higher for the user to blame the web page authors and
4248 not the browser for any missing features.
</li
>
4250 <li
><strong
>Simple handling of missing multimedia codec/format
4251 handlers.
</strong
> When the media players encounter a format or codec
4252 it is not supporting, a dialog pop up asking the user if the system
4253 should search for a package that would add support for it. This
4254 happen with things like MP3, Windows Media or H
.264. The selection
4255 and installation procedure is very similar to the Firefox browser
4256 plugin handling. This is as far as I know implemented using a
4257 gstreamer hook. The end result is that the user easily get access to
4258 the codecs that are present from the APT archives available, while
4259 explaining more on why a given format is unsupported by Ubuntu.
</li
>
4261 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
4262 displaying a text/plain file in my Debian browser, it will propose to
4263 start emacs to show it. If I remember correctly, when doing the same
4264 in Kunbutu it show the file as a text file in the browser. At least I
4265 know Opera will show text files within the browser. I much prefer the
4266 latter behaviour.
</li
>
4270 <p
>There are other nice features as well, like the simplified suite
4271 upgrader, but given that I am the one mostly doing the dist-upgrade,
4272 it do not matter much.
</p
>
4274 <p
>I really hope we could get these features in place for the next
4275 Debian release. It would require the coordinated effort of several
4276 maintainers, but would make the end user experience a lot better.
</p
>
4281 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
4282 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
4283 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
4284 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
4285 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
4286 site is build on Debian/Squeeze, and this platform was chosen because
4287 I am most familiar with Debian (being a Debian Developer for around
10
4288 years) because it is the latest stable Debian release which should get
4289 security support for a few years.
</p
>
4291 <p
>The web service is written in Perl, and depend on some perl modules
4292 that are missing in Debian at the moment. It would be great if these
4293 modules were added to the Debian archive, allowing anyone to set up
4294 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
4295 in their own country using only Debian packages. The list of modules
4296 missing in Debian/Squeeze isn
't very long, and I hope the perl group
4297 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
4298 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4299 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4300 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4301 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4302 easier in the future.
</p
>
4304 <p
>Thanks to the great tools in Debian, getting the missing modules
4305 installed on my server was a simple call to
'cpan2deb Module::Name
'
4306 and
'dpkg -i
' to install the resulting package. But this leave me
4307 with the responsibility of tracking security problems, which I really
4308 do not have time for.
</p
>
4313 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
4314 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
4315 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
4316 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
4317 <description><p
>Here is a small update for my English readers. Most of my blog
4318 posts have been in Norwegian the last few weeks, so here is a short
4319 update in English.
</p
>
4321 <p
>The kids still keep me too busy to get much free software work
4322 done, but I did manage to organise a project to get a Norwegian port
4323 of the British service
4324 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
4325 and it has been running for a month now. The entire project has been
4326 organised by me and two others. Around Christmas we gathered sponsors
4327 to fund the development work. In January I drafted a contract with
4328 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
4329 and in February the development took place. Most of it involved
4330 converting the source to use GPS coordinates instead of British
4331 easting/northing, and the resulting code should be a lot easier to get
4332 running in any country by now. The Norwegian
4333 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
4334 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
4335 source and the source for administrative borders in Norway, and
4336 support for this had to be added/fixed.
</p
>
4338 <p
>The Norwegian version went live March
3th, and we spent the weekend
4339 polishing the system before we announced it March
7th. The system is
4340 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
4341 problem reports in a few weeks. Soon we hope to announce the Android
4342 and iPhone versions making it even easier to report problems with the
4343 public infrastructure.
</p
>
4345 <p
>Perhaps something to consider for those of you in countries without
4346 such service?
</p
>
4351 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
4352 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
4353 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
4354 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
4355 <description><p
>The last few days I have looked at ways to track open security
4356 issues here at my work with the University of Oslo. My idea is that
4357 it should be possible to use the information about security issues
4358 available on the Internet, and check our locally
4359 maintained/distributed software against this information. It should
4360 allow us to verify that no known security issues are forgotten. The
4361 CVE database listing vulnerabilities seem like a great central point,
4362 and by using the package lists from Debian mapped to CVEs provided by
4363 the testing security team, I believed it should be possible to figure
4364 out which security holes were present in our free software
4365 collection.
</p
>
4367 <p
>After reading up on the topic, it became obvious that the first
4368 building block is to be able to name software packages in a unique and
4369 consistent way across data sources. I considered several ways to do
4370 this, for example coming up with my own naming scheme like using URLs
4371 to project home pages or URLs to the Freshmeat entries, or using some
4372 existing naming scheme. And it seem like I am not the first one to
4373 come across this problem, as MITRE already proposed and implemented a
4374 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
4375 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
4376 software, hardware and other platform components. The CPE ids are
4377 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
4378 Vulnerability Database
</a
>, allowing me to look up know security
4379 issues for any CPE name. With this in place, all I need to do is to
4380 locate the CPE id for the software packages we use at the university.
4381 This is fairly trivial (I google for
'cve cpe $package
' and check the
4382 NVD entry if a CVE for the package exist).
</p
>
4384 <p
>To give you an example. The GNU gzip source package have the CPE
4385 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
4386 check out, one could look up
4387 <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
4388 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
4389 The most recent one is
4390 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
4391 and at the bottom of the NVD page for this vulnerability the complete
4392 list of affected versions is provided.
</p
>
4394 <p
>The NVD database of CVEs is also available as a XML dump, allowing
4395 for offline processing of issues. Using this dump, I
've written a
4396 small script taking a list of CPEs as input and list all CVEs
4397 affecting the packages represented by these CPEs. One give it CPEs
4398 with version numbers as specified above and get a list of open
4399 security issues out.
</p
>
4401 <p
>Of course for this approach to be useful, the quality of the NVD
4402 information need to be high. For that to happen, I believe as many as
4403 possible need to use and contribute to the NVD database. I notice
4405 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
4406 map from CVE to CPE
</a
>, indicating that they are using the CPE
4407 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
4409 <p
>To get an idea about the quality for free software, I spent some
4410 time making it possible to compare the CVE database from Debian with
4411 the CVE database in NVD. The result look fairly good, but there are
4412 some inconsistencies in NVD (same software package having several
4413 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4414 Debian believe are affected by a CVE). Hope to find time to improve
4415 the quality of NVD, but that require being able to get in touch with
4416 someone maintaining it. So far my three emails with questions and
4417 corrections have not seen any reply, but I hope contact can be
4418 established soon.
</p
>
4420 <p
>An interesting application for CPEs is cross platform package
4421 mapping. It would be useful to know which packages in for example
4422 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4423 this would be trivial if all linux distributions provided CPE entries
4424 for their packages.
</p
>
4429 <title>Which module is loaded for a given PCI and USB device?
</title>
4430 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
4431 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
4432 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
4433 <description><p
>In the
4434 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
4435 package in Debian, there is a script to report useful information
4436 about the running hardware for use when people report missing
4437 information. One part of this script that I find very useful when
4438 debugging hardware problems, is the part mapping loaded kernel module
4439 to the PCI device it claims. It allow me to quickly see if the kernel
4440 module I expect is driving the hardware I am struggling with. To see
4441 the output, make sure discover-data is installed and run
4442 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
4443 one of my machines like this:
</p
>
4447 10de:
03eb i2c_nforce2
4450 10de:
03f0 snd_hda_intel
4459 <p
>The code in question look like this, slightly modified for
4460 readability and to drop the output to file descriptor
3:
</p
>
4463 if [ -d /sys/bus/pci/devices/ ] ; then
4464 echo loaded pci modules:
4466 cd /sys/bus/pci/devices/
4467 for address in * ; do
4468 if [ -d
"$address/driver/module
" ] ; then
4469 module=`cd $address/driver/module ; pwd -P | xargs basename`
4470 if grep -q
"^$module
" /proc/modules ; then
4471 address=$(echo $address |sed s/
0000://)
4472 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
4473 echo
"$id $module
"
4482 <p
>Similar code could be used to extract USB device module
4486 if [ -d /sys/bus/usb/devices/ ] ; then
4487 echo loaded usb modules:
4489 cd /sys/bus/usb/devices/
4490 for address in * ; do
4491 if [ -d
"$address/driver/module
" ] ; then
4492 module=`cd $address/driver/module ; pwd -P | xargs basename`
4493 if grep -q
"^$module
" /proc/modules ; then
4494 address=$(echo $address |sed s/
0000://)
4495 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
4496 if [
"$id
" ] ; then
4497 echo
"$id $module
"
4507 <p
>This might perhaps be something to include in other tools as
4513 <title>How to test if a laptop is working with Linux
</title>
4514 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
4515 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
4516 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
4517 <description><p
>The last few days I have spent at work here at the
<a
4518 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
4519 batch of computers will work with Linux. Every year for the last few
4520 years the university have organised shared bid of a few thousand
4521 computers, and this year HP won the bid. Two different desktops and
4522 five different laptops are on the list this year. We in the UNIX
4523 group want to know which one of these computers work well with RHEL
4524 and Ubuntu, the two Linux distributions we currently handle at the
4525 university.
</p
>
4527 <p
>My test method is simple, and I share it here to get feedback and
4528 perhaps inspire others to test hardware as well. To test, I PXE
4529 install the OS version of choice, and log in as my normal user and run
4530 a few applications and plug in selected pieces of hardware. When
4531 something fail, I make a note about this in the test matrix and move
4532 on. If I have some spare time I try to report the bug to the OS
4533 vendor, but as I only have the machines for a short time, I rarely
4534 have the time to do this for all the problems I find.
</p
>
4536 <p
>Anyway, to get to the point of this post. Here is the simple tests
4537 I perform on a new model.
</p
>
4541 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
4542 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4543 RHEL5 and Debian Edu/Squeeze.
</li
>
4545 <li
>Is X.org working? If the graphical login screen show up after
4546 installation, X.org is working.
</li
>
4548 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
4549 package mesa-utils on Ubuntu) and writing down the frames per second
4550 reported by the program.
</li
>
4552 <li
>Is sound working? With Gnome and KDE, a sound is played when
4553 logging in, and if I can hear this the test is successful. If there
4554 are several audio exits on the machine, I try them all and check if
4555 the Gnome/KDE audio mixer can control where to send the sound. I
4556 normally test this by playing
4557 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
4558 video
</a
> in Firefox/Iceweasel.
</li
>
4560 <li
>Is the USB subsystem working? I test this by plugging in a USB
4561 memory stick and see if Gnome/KDE notices this.
</li
>
4563 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
4564 I have lying around, and see if Gnome/KDE notices this.
</li
>
4566 <li
>Is any built in camera working? Test using cheese, and see if a
4567 picture from the v4l device show up.
</li
>
4569 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4570 any bluetooth devices are discovered. In my office, I normally see a
4573 <li
>For laptops, is the SD or Compaq Flash reader working. I have
4574 memory modules lying around, and stick them in and see if Gnome/KDE
4575 notice this.
</li
>
4577 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
4578 special button work, and if the laptop continue to work after
4581 <li
>For laptops, is the extra buttons working, like audio level,
4582 adjusting background light, switching on/off external video output,
4583 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4584 laptop to laptop, so I just write down which are working and which are
4587 <li
>Some laptops have smart card readers, finger print readers,
4588 acceleration sensors etc. I rarely test these, as I do not know how
4589 to quickly test if they are working or not, so I only document their
4590 existence.
</li
>
4594 <p
>By now I suspect you are really curious what the test results are
4595 for the HP machines I am testing. I
'm not done yet, so I will report
4596 the test results later. For now I can report that HP
8100 Elite work
4597 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
4598 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
4599 can see, I have most machines left to test. One interesting
4600 observation is that Ubuntu Lucid has almost twice the frame rate than
4601 RHEL6 with glxgears. No idea why.
</p
>
4606 <title>Some thoughts on BitCoins
</title>
4607 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
4608 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
4609 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
4610 <description><p
>As I continue to explore
4611 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
4612 what properties the system have, and how it will be affected by laws
4613 and regulations here in Norway. Here are some random notes.
</p
>
4615 <p
>One interesting thing to note is that since the transactions are
4616 verified using a peer to peer network, all details about a transaction
4617 is known to everyone. This means that if a BitCoin address has been
4618 published like I did with mine in my initial post about BitCoin, it is
4619 possible for everyone to see how many BitCoins have been transfered to
4620 that address. There is even a web service to look at the details for
4621 all transactions. There I can see that my address
4622 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
4623 have received
16.06 Bitcoin, the
4624 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
4625 address of Simon Phipps have received
181.97 BitCoin and the address
4626 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
4627 of EFF have received
2447.38 BitCoins so far. Thank you to each and
4628 every one of you that donated bitcoins to support my activity. The
4629 fact that anyone can see how much money was transfered to a given
4630 address make it more obvious why the BitCoin community recommend to
4631 generate and hand out a new address for each transaction. I
'm told
4632 there is no way to track which addresses belong to a given person or
4633 organisation without the person or organisation revealing it
4634 themselves, as Simon, EFF and I have done.
</p
>
4636 <p
>In Norway, and in most other countries, there are laws and
4637 regulations limiting how much money one can transfer across the border
4638 without declaring it. There are money laundering, tax and accounting
4639 laws and regulations I would expect to apply to the use of BitCoin.
4640 If the Skolelinux foundation
4641 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
4642 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
4643 normal bank transfers like EFF is doing, how should this be accounted?
4644 Given that it is impossible to know if money can cross the border or
4645 not, should everything or nothing be declared? What exchange rate
4646 should be used when calculating taxes? Would receivers have to pay
4647 income tax if the foundation were to pay Skolelinux contributors in
4648 BitCoin? I have no idea, but it would be interesting to know.
</p
>
4650 <p
>For a currency to be useful and successful, it must be trusted and
4651 accepted by a lot of users. It must be possible to get easy access to
4652 the currency (as a wage or using currency exchanges), and it must be
4653 easy to spend it. At the moment BitCoin seem fairly easy to get
4654 access to, but there are very few places to spend it. I am not really
4655 a regular user of any of the vendor types currently accepting BitCoin,
4656 so I wonder when my kind of shop would start accepting BitCoins. I
4657 would like to buy electronics, travels and subway tickets, not herbs
4658 and books. :) The currency is young, and this will improve over time
4659 if it become popular, but I suspect regular banks will start to lobby
4660 to get BitCoin declared illegal if it become popular. I
'm sure they
4661 will claim it is helping fund terrorism and money laundering (which
4662 probably would be true, as is any currency in existence), but I
4663 believe the problems should be solved elsewhere and not by blaming
4664 currencies.
</p
>
4666 <p
>The process of creating new BitCoins is called mining, and it is
4667 CPU intensive process that depend on a bit of luck as well (as one is
4668 competing against all the other miners currently spending CPU cycles
4669 to see which one get the next lump of cash). The
"winner
" get
50
4670 BitCoin when this happen. Yesterday I came across the obvious way to
4671 join forces to increase ones changes of getting at least some coins,
4672 by coordinating the work on mining BitCoins across several machines
4673 and people, and sharing the result if one is lucky and get the
50
4675 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
4676 if this sounds interesting. I have not had time to try to set up a
4677 machine to participate there yet, but have seen that running on ones
4678 own for a few days have not yield any BitCoins througth mining
4681 <p
>Update
2010-
12-
15: Found an
<a
4682 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
4683 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
4684 it was interesting to read. The arguments presented seem to be
4685 equally valid for gold, which was used as a currency for many years.
</p
>
4690 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
4691 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
4692 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
4693 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
4694 <description><p
>With this weeks lawless
4695 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
4696 attacks
</a
> on Wikileak and
4697 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
4698 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
4699 not be trusted to handle money transactions.
4701 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
4702 Phipps on bitcoin
</a
> reminded me about a project that a friend of
4703 mine mentioned earlier. I decided to follow Simon
's example, and get
4704 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
4705 some help from my friend to get it all running, and he even handed me
4706 some bitcoins to get started. I even donated a few bitcoins to Simon
4707 for helping me remember BitCoin.
</p
>
4709 <p
>So, what is bitcoins, you probably wonder? It is a digital
4710 crypto-currency, decentralised and handled using peer-to-peer
4711 networks. It allows anonymous transactions and prohibits central
4712 control over the transactions, making it impossible for governments
4713 and companies alike to block donations and other transactions. The
4714 source is free software, and while the key dependency wxWidgets
2.9
4715 for the graphical user interface is missing in Debian, the command
4716 line client builds just fine. Hopefully Jonas
4717 <a href=
"http://bugs.debian.org/
578157">will get the package into
4718 Debian
</a
> soon.
</p
>
4720 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
4721 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
4722 bitcoins
</a
> when selling services and goods, and there are even
4723 currency
"stock
" markets where the exchange rate is decided. There
4724 are not many users so far, but the concept seems promising. If you
4725 want to get started and lack a friend with any bitcoins to spare,
4727 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
4728 bitcoin at the time of writing). Use
4729 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
4730 on the current exchange rates.
</p
>
4732 <p
>As an experiment, I have decided to set up bitcoind on one of my
4733 machines. If you want to support my activity, please send Bitcoin
4734 donations to the address
4735 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
4740 <title>Why isn
't Debian Edu using VLC?
</title>
4741 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
4742 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
4743 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
4744 <description><p
>In the latest issue of Linux Journal, the readers choices were
4745 presented, and the winner among the multimedia player were VLC.
4746 Personally, I like VLC, and it is my player of choice when I first try
4747 to play a video file or stream. Only if VLC fail will I drag out
4748 gmplayer to see if it can do better. The reason is mostly the failure
4749 model and trust. When VLC fail, it normally pop up a error message
4750 reporting the problem. When mplayer fail, it normally segfault or
4751 just hangs. The latter failure mode drain my trust in the program.
<p
>
4753 <p
>But even if VLC is my player of choice, we have choosen to use
4754 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
4755 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
4756 plugin to play web videos seamlessly, and the VLC browser plugin is
4757 not very good. For example, it lack in-line control buttons, so there
4758 is no way for the user to pause the video. Also, when I
4759 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
4760 tested the browser plugins
</a
> available in Debian, the VLC plugin
4761 failed on several video pages where mplayer based plugins worked. If
4762 the browser plugin for VLC was as good as the gecko-mediaplayer
4763 package (which uses mplayer), we would switch.
</P
>
4765 <p
>While VLC is a good player, its user interface is slightly
4766 annoying. The most annoying feature is its inconsistent use of
4767 keyboard shortcuts. When the player is in full screen mode, its
4768 shortcuts are different from when it is playing the video in a window.
4769 For example, space only work as pause when in full screen mode. I
4770 wish it had consisten shortcuts and that space also would work when in
4771 window mode. Another nice shortcut in gmplayer is [enter] to restart
4772 the current video. It is very nice when playing short videos from the
4773 web and want to restart it when new people arrive to have a look at
4774 what is going on.
</p
>
4779 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
4780 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
4781 <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>
4782 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
4783 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
4784 upgrade testing of the
4785 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
4786 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
4787 This seem like a very good idea, so I adjusted by test scripts and
4788 can now present the updated result from today:
</p
>
4790 <p
>This is for Gnome:
</p
>
4792 <p
>Installed using apt-get, missing with aptitude
</p
>
4794 <blockquote
><p
>
4799 browser-plugin-gnash
4806 freedesktop-sound-theme
4808 gconf-defaults-service
4823 gnome-desktop-environment
4827 gnome-session-canberra
4832 gstreamer0.10-fluendo-mp3
4838 libapache2-mod-dnssd
4841 libaprutil1-dbd-sqlite3
4844 libboost-date-time1.42
.0
4845 libboost-python1.42
.0
4846 libboost-thread1.42
.0
4848 libchamplain-gtk-
0.4-
0
4850 libclutter-gtk-
0.10-
0
4857 libfreerdp-plugins-standard
4872 libgnomepanel2.24-cil
4877 libgtksourceview2.0-common
4878 libmono-addins-gui0.2-cil
4879 libmono-addins0.2-cil
4880 libmono-cairo2.0-cil
4881 libmono-corlib2.0-cil
4882 libmono-i18n-west2.0-cil
4883 libmono-posix2.0-cil
4884 libmono-security2.0-cil
4885 libmono-sharpzip2.84-cil
4886 libmono-system2.0-cil
4889 libndesk-dbus-glib1.0-cil
4890 libndesk-dbus1.0-cil
4900 libtelepathy-farsight0
4909 nautilus-sendto-empathy
4913 python-aptdaemon-gtk
4915 python-beautifulsoup
4930 python-gtksourceview2
4941 python-pkg-resources
4948 python-twisted-conch
4954 python-zope.interface
4959 rhythmbox-plugin-cdrecorder
4966 system-config-printer-udev
4968 telepathy-mission-control-
5
4979 </p
></blockquote
>
4981 <p
>Installed using apt-get, removed with aptitude
</p
>
4983 <blockquote
><p
>
4989 fast-user-switch-applet
5008 libgtksourceview2.0-
0
5010 libsdl1.2debian-alsa
5016 system-config-printer
5021 </p
></blockquote
>
5023 <p
>Installed using aptitude, missing with apt-get
</p
>
5025 <blockquote
><p
>
5026 gstreamer0.10-gnomevfs
5027 </p
></blockquote
>
5029 <p
>Installed using aptitude, removed with apt-get
</p
>
5031 <blockquote
><p
>
5033 </p
></blockquote
>
5035 <p
>This is for KDE:
</p
>
5037 <p
>Installed using apt-get, missing with aptitude
</p
>
5039 <blockquote
><p
>
5041 </p
></blockquote
>
5043 <p
>Installed using apt-get, removed with aptitude
</p
>
5045 <blockquote
><p
>
5048 </p
></blockquote
>
5050 <p
>Installed using aptitude, missing with apt-get
</p
>
5052 <blockquote
><p
>
5066 kdeartwork-emoticons
5068 kdeartwork-theme-icon
5072 kdebase-workspace-bin
5073 kdebase-workspace-data
5087 kscreensaver-xsavers
5102 plasma-dataengines-workspace
5104 plasma-desktopthemes-artwork
5105 plasma-runners-addons
5106 plasma-scriptengine-googlegadgets
5107 plasma-scriptengine-python
5108 plasma-scriptengine-qedje
5109 plasma-scriptengine-ruby
5110 plasma-scriptengine-webkit
5111 plasma-scriptengines
5112 plasma-wallpapers-addons
5113 plasma-widget-folderview
5114 plasma-widget-networkmanagement
5118 xscreensaver-data-extra
5120 xscreensaver-gl-extra
5121 xscreensaver-screensaver-bsod
5122 </p
></blockquote
>
5124 <p
>Installed using aptitude, removed with apt-get
</p
>
5126 <blockquote
><p
>
5128 google-gadgets-common
5146 libggadget-qt-
1.0-
0b
5151 libkonqsidebarplugin4a
5160 libplasma-geolocation-interface4
5162 libplasmagenericshell4
5176 libsmokeknewstuff2-
3
5177 libsmokeknewstuff3-
3
5179 libsmokektexteditor3
5187 libsmokeqtnetwork4-
3
5193 libsmokeqtuitools4-
3
5205 plasma-dataengines-addons
5206 plasma-scriptengine-superkaramba
5207 plasma-widget-lancelot
5208 plasma-widgets-addons
5209 plasma-widgets-workspace
5213 update-notifier-common
5214 </p
></blockquote
>
5216 <p
>Running apt-get autoremove made the results using apt-get and
5217 aptitude a bit more similar, but there are still quite a lott of
5218 differences. I have no idea what packages should be installed after
5219 the upgrade, but hope those that do can have a look.
</p
>
5224 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
5225 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
5226 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
5227 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
5228 <description><p
>Most of the computers in use by the
5229 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
5230 are virtual machines. And they have been Xen machines running on a
5231 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
5232 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
5233 bit harder that it could have been, because we set up the Xen virtual
5234 machines to get the virtual partitions from LVM, which as far as I
5235 know is not supported by KVM. So to migrate, we had to convert
5236 several LVM logical volumes to partitions on a virtual disk file.
</p
>
5239 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
5240 nice recipe
</a
> to do this, and wrote the following script to do the
5241 migration. It uses qemu-img from the qemu package to make the disk
5242 image, parted to partition it, losetup and kpartx to present the disk
5243 image partions as devices, and dd to copy the data. I NFS mounted the
5244 new servers storage area on the old server to do the migration.
</p
>
5250 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5255 if [ -z
"$
1" ] ; then
5256 echo
"Usage: $
0 &lt;hostname
&gt;
"
5262 if [ ! -e /dev/vg_data/$host-disk ] ; then
5263 echo
"error: unable to find LVM volume for $host
"
5267 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5268 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
5269 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
5270 totalsize=$(( ( $disksize + $swapsize ) ))
5273 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
5274 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5276 parted $img mklabel msdos
5277 parted $img mkpart primary linux-swap
0 $disksize
5278 parted $img mkpart primary ext2 $disksize $totalsize
5279 parted $img set
1 boot on
5282 losetup /dev/loop0 $img
5283 kpartx -a /dev/loop0
5285 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
5286 fsck.ext3 -f /dev/mapper/loop0p1 || true
5287 mkswap /dev/mapper/loop0p2
5289 kpartx -d /dev/loop0
5290 losetup -d /dev/loop0
5293 <p
>The script is perhaps so simple that it is not copyrightable, but
5294 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
5296 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
5297 the new disk image attached, installed grub-pc and linux-image-
686 and
5298 set up grub to boot from the disk image. After this, the KVM machines
5299 seem to work just fine.
</p
>
5304 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
5305 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
5306 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
5307 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
5308 <description><p
>I
'm still running upgrade testing of the
5309 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
5310 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
5311 status. Here is a short update based on a test I ran
20101118.
</p
>
5313 <p
>I still do not know what a correct migration should look like, so I
5314 report any differences between apt and aptitude and hope someone else
5315 can see if anything should be changed.
</p
>
5317 <p
>This is for Gnome:
</p
>
5319 <p
>Installed using apt-get, missing with aptitude
</p
>
5321 <blockquote
><p
>
5322 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5323 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
5324 dmz-cursor-theme empathy empathy-common finger
5325 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5326 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5327 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5328 gnome-cards-data gnome-codec-install gnome-core
5329 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5330 gnome-search-tool gnome-session-canberra gnome-spell
5331 gnome-system-log gnome-themes-extras gnome-themes-more
5332 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5333 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5334 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5335 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5336 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
5337 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
5338 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
5339 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
5340 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
5341 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5342 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
5343 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5344 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5345 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5346 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5347 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5348 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5349 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5350 libmono-security2.0-cil libmono-sharpzip2.84-cil
5351 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
5352 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
5353 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
5354 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
5355 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
5356 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
5357 libxalan2-java libxerces2-java media-player-info mesa-utils
5358 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
5359 nautilus-sendto-empathy openoffice.org-writer2latex
5360 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
5361 python-aptdaemon python-aptdaemon-gtk python-axiom
5362 python-beautifulsoup python-bugbuddy python-clientform
5363 python-coherence python-configobj python-crypto python-cupshelpers
5364 python-cupsutils python-eggtrayicon python-elementtree
5365 python-epsilon python-evolution python-feedparser python-gdata
5366 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5367 python-gtksourceview2 python-httplib2 python-louie python-mako
5368 python-markupsafe python-mechanize python-nevow python-notify
5369 python-opengl python-openssl python-pam python-pkg-resources
5370 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5371 python-tagpy python-twisted-bin python-twisted-conch
5372 python-twisted-core python-twisted-web python-utidylib python-webkit
5373 python-xdg python-zope.interface remmina remmina-plugin-data
5374 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5375 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5376 software-center svgalibg1 system-config-printer-udev
5377 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
5378 totem totem-coherence totem-mozilla totem-plugins
5379 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5381 </p
></blockquote
>
5383 Installed using apt-get, removed with aptitude
5385 <blockquote
><p
>
5386 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5387 epiphany-extensions epiphany-gecko evolution-exchange
5388 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5389 gedit-common gnome-app-install gnome-games gnome-games-data
5390 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5391 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5392 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5393 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
5394 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
5395 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
5396 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
5397 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
5398 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
5399 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
5400 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
5401 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
5402 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5403 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5404 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5405 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5406 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
5407 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
5408 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
5409 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
5410 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
5411 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5412 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5413 sound-juicer swfdec-gnome system-config-printer totem-common
5414 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5415 </p
></blockquote
>
5417 <p
>Installed using aptitude, missing with apt-get
</p
>
5419 <blockquote
><p
>
5420 gstreamer0.10-gnomevfs
5421 </p
></blockquote
>
5423 <p
>Installed using aptitude, removed with apt-get
</p
>
5425 <blockquote
><p
>
5427 </p
></blockquote
>
5429 <p
>This is for KDE:
</p
>
5431 <p
>Installed using apt-get, missing with aptitude
</p
>
5433 <blockquote
><p
>
5434 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
5435 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5436 ghostscript-x git gnome-audio gnugo granatier gs-common
5437 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5438 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5439 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5440 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5441 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5442 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5443 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5444 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5445 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5446 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5447 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5448 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
5449 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5450 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5451 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5452 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5453 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5454 libkrossui4 libmailtools-perl libmime-tools-perl
5455 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5456 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5457 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5458 lirc luatex marble networkstatus noatun-plugins
5459 openoffice.org-writer2latex palapeli palapeli-data parley
5460 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5461 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5462 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5464 </p
></blockquote
>
5466 <p
>Installed using apt-get, removed with aptitude
</p
>
5468 <blockquote
><p
>
5469 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5470 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5471 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5472 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5473 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5474 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5475 kitchensync kiten kjumpingcube klatin klettres klickety klines
5476 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5477 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5478 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5479 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5480 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5481 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5482 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5483 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5484 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5485 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
5486 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
5487 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5488 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
5489 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
5490 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5491 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5492 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5493 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5494 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5495 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5496 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
5497 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
5498 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5499 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5500 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5501 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5502 </p
></blockquote
>
5504 <p
>Installed using aptitude, missing with apt-get
</p
>
5506 <blockquote
><p
>
5507 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5508 kdeartwork kdebase kdebase-apps kdebase-workspace
5509 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5510 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5511 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5512 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5513 xscreensaver-screensaver-bsod
5514 </p
></blockquote
>
5516 <p
>Installed using aptitude, removed with apt-get
</p
>
5518 <blockquote
><p
>
5519 kdebase-bin konq-plugins konqueror
5520 </p
></blockquote
>
5525 <title>Gnash buildbot slave and Debian kfreebsd
</title>
5526 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
5527 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
5528 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
5529 <description><p
>Answering
5530 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
5531 call from the Gnash project
</a
> for
5532 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
5533 current source, I have set up a virtual KVM machine on the Debian
5534 Edu/Skolelinux virtualization host to test the git source on
5535 Debian/Squeeze. I hope this can help the developers in getting new
5536 releases out more often.
</p
>
5538 <p
>As the developers want less main-stream build platforms tested to,
5539 I have considered setting up a
<a
5540 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
5541 machine as well. I have also considered using the kfreebsd
5542 architecture in Debian as a file server in NUUG to get access to the
5
5543 TB zfs volume we currently use to store DV video. Because of this, I
5544 finally got around to do a test installation of Debian/Squeeze with
5545 kfreebsd. Installation went fairly smooth, thought I noticed some
5546 visual glitches in the cdebconf dialogs (black cursor left on the
5547 screen at random locations). Have not gotten very far with the
5548 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5549 fatal problem. Have to spend some more time on it to see if it is
5550 useful as a file server for NUUG. Will try to find time to set up a
5551 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
5556 <title>Debian in
3D
</title>
5557 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
5558 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
5559 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
5560 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
5562 <p
>3D printing is just great. I just came across this Debian logo in
5564 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
5565 thingiverse blog
</a
>.
</p
>
5570 <title>Software updates
2010-
10-
24</title>
5571 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
5572 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
5573 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
5574 <description><p
>Some updates.
</p
>
5576 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
5577 raise money for the project is going well. The lower limit of
10
5578 signers was reached in
24 hours, and so far
13 people have signed it.
5579 More signers and more funding is most welcome, and I am really curious
5580 how far we can get before the time limit of December
24 is reached.
5583 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
5584 about what appear to be a great code coverage tool capable of
5585 generating code coverage stats without any changes to the source code.
5587 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
5588 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
5589 It is missing in Debian, but the git source built just fine in Squeeze
5590 after I installed libelf-dev, libdwarf-dev, pkg-config and
5591 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5592 solvable. I hope kcov make it into Debian soon.
</p
>
5594 <p
>Finally found time to wrap up the release notes for
<a
5595 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
5596 new alpha release of Debian Edu
</a
>, and just published the second
5597 alpha test release of the Squeeze based Debian Edu /
5598 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
5599 release. Give it a try if you need a complete linux solution for your
5600 school, including central infrastructure server, workstations, thin
5601 client servers and diskless workstations. A nice touch added
5602 yesterday is RDP support on the thin client servers, for windows
5603 clients to get a Linux desktop on request.
</p
>
5608 <title>Some notes on Flash in Debian and Debian Edu
</title>
5609 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
5610 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
5611 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
5612 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
5613 popularity-contest numbers
</a
>, the adobe-flashplugin package the
5614 second most popular used package that is missing in Debian. The sixth
5615 most popular is flashplayer-mozilla. This is a clear indication that
5616 working flash is important for Debian users. Around
10 percent of the
5617 users submitting data to popcon.debian.org have this package
5618 installed.
</p
>
5620 <p
>In the report written by Lars Risan in August
2008
5621 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
5622 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5623 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
5624 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
5625 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
5626 web sites require Flash to work, and lacking working Flash support in
5627 the web browser and the problems with installing it was perceived as a
5628 good reason to stay with Windows.
</p
>
5630 <p
>I once saw a funny and sad comment in a web forum, where Linux was
5631 said to be the retarded cousin that did not really understand
5632 everything you told him but could work fairly well. This was a
5633 comment regarding the problems Linux have with proprietary formats and
5634 non-standard web pages, and is sad because it exposes a fairly common
5635 understanding of whose fault it is if web pages that only work in for
5636 example Internet Explorer
6 fail to work on Firefox, and funny because
5637 it explain very well how annoying it is for users when Linux
5638 distributions do not work with the documents they receive or the web
5639 pages they want to visit.
</p
>
5641 <p
>This is part of the reason why I believe it is important for Debian
5642 and Debian Edu to have a well working Flash implementation in the
5643 distribution, to get at least popular sites as Youtube and Google
5644 Video to working out of the box. For Squeeze, Debian have the chance
5645 to include the latest version of Gnash that will make this happen, as
5646 the new release
0.8.8 was published a few weeks ago and is resting in
5647 unstable. The new version work with more sites that version
0.8.7.
5648 The Gnash maintainers have asked for a freeze exception, but the
5649 release team have not had time to reply to it yet. I hope they agree
5650 with me that Flash is important for the Debian desktop users, and thus
5651 accept the new package into Squeeze.
</p
>
5656 <title>Circular package dependencies harms apt recovery
</title>
5657 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
5658 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
5659 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
5660 <description><p
>I discovered this while doing
5661 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
5662 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
5663 in Debian still got circular dependencies, and it is often claimed
5664 that apt and aptitude should be able to handle this just fine, but
5665 some times these dependency loops causes apt to fail.
</p
>
5667 <p
>An example is from todays
5668 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
5669 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
5670 causes perl-modules to fail to upgrade. The cause is simple. If a
5671 package fail to unpack, then only part of packages with the circular
5672 dependency might end up being unpacked when unpacking aborts, and the
5673 ones already unpacked will fail to configure in the recovery phase
5674 because its dependencies are unavailable.
</p
>
5676 <p
>In this log, the problem manifest itself with this error:
</p
>
5678 <blockquote
><pre
>
5679 dpkg: dependency problems prevent configuration of perl-modules:
5680 perl-modules depends on perl (
>=
5.10.1-
1); however:
5681 Version of perl on system is
5.10.0-
19lenny
2.
5682 dpkg: error processing perl-modules (--configure):
5683 dependency problems - leaving unconfigured
5684 </pre
></blockquote
>
5686 <p
>The perl/perl-modules circular dependency is already
5687 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
5688 hopefully be solved as soon as possible, but it is not the only one,
5689 and each one of these loops in the dependency tree can cause similar
5690 failures. Of course, they only occur when there are bugs in other
5691 packages causing the unpacking to fail, but it is rather nasty when
5692 the failure of one package causes the problem to become worse because
5693 of dependency loops.
</p
>
5696 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
5697 tireless effort by Bill Allombert
</a
>, the number of circular
5699 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
5700 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
5702 <p
>Todays testing also exposed a bug in
5703 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
5704 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
5705 apt-get and aptitude, the latter possibly caused by some circular
5706 dependency. Reported both to BTS to try to get someone to look at
5712 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
5713 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
5714 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
5715 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
5716 <description><p
>This is a
5717 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
5719 <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
5721 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
5722 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
5724 <p
>As a step to try to see if it possible to merge the DNS and DHCP
5725 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5726 and dhcp3-server-ldap in Debian use the LDAP server. The two
5727 implementations are quite different in how they use LDAP.
</p
>
5729 To get this information, I started slapd with debugging enabled and
5730 dumped the debug output to a file to get the LDAP searches performed
5731 on a Debian Edu main-server. Here is a summary.
5733 <p
><strong
>powerdns
</strong
></p
>
5735 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
5736 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
5739 <p
>PowerDNS have two modes of operation using LDAP as its backend.
5740 One
"strict
" mode where the forward and reverse DNS lookups are done
5741 using the same LDAP objects, and a
"tree
" mode where the forward and
5742 reverse entries are in two different subtrees in LDAP with a structure
5743 based on the DNS names, as in tjener.intern and
5744 2.2.0.10.in-addr.arpa.
</p
>
5746 <p
>In tree mode, the server is set up to use a LDAP subtree as its
5747 base, and uses a
"base
" scoped search for the DNS name by adding
5748 "dc=tjener,dc=intern,
" to the base with a filter for
5749 "(associateddomain=tjener.intern)
" for the forward entry and
5750 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
5751 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
5752 forward entries, it is looking for attributes named dnsttl, arecord,
5753 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5754 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5755 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5756 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5757 spfrecord and modifytimestamp. For reverse entries it is looking for
5758 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5759 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5760 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5761 ldapsearch commands could look like this:
</p
>
5763 <blockquote
><pre
>
5764 ldapsearch -h ldap \
5765 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5766 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
5767 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5768 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5769 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5770 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5772 ldapsearch -h ldap \
5773 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5774 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
5775 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
5776 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
5777 srvrecord naptrrecord modifytimestamp
5778 </pre
></blockquote
>
5780 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
5781 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
5782 example LDAP objects used there. In addition to these objects, the
5783 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
5784 also exist.
</p
>
5786 <blockquote
><pre
>
5787 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
5789 objectclass: dnsdomain
5790 objectclass: domainrelatedobject
5793 associateddomain: tjener.intern
5795 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
5797 objectclass: dnsdomain2
5798 objectclass: domainrelatedobject
5800 ptrrecord: tjener.intern
5801 associateddomain:
2.2.0.10.in-addr.arpa
5802 </pre
></blockquote
>
5804 <p
>In strict mode, the server behaves differently. When looking for
5805 forward DNS entries, it is doing a
"subtree
" scoped search with the
5806 same base as in the tree mode for a object with filter
5807 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
5808 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
5809 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
5810 naptrrecord and modifytimestamp. For reverse entires it also do a
5811 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
5812 and the requested attributes are associateddomain, dnsttl and
5813 modifytimestamp. In short, in strict mode the objects with ptrrecord
5814 go away, and the arecord attribute in the forward object is used
5817 <p
>The forward and reverse searches can be simulated using ldapsearch
5818 like this:
</p
>
5820 <blockquote
><pre
>
5821 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5822 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
5823 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5824 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5825 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5826 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5828 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5829 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
5830 </pre
></blockquote
>
5832 <p
>In addition to the forward and reverse searches , there is also a
5833 search for SOA records, which behave similar to the forward and
5834 reverse lookups.
</p
>
5836 <p
>A thing to note with the PowerDNS behaviour is that it do not
5837 specify any objectclass names, and instead look for the attributes it
5838 need to generate a DNS reply. This make it able to work with any
5839 objectclass that provide the needed attributes.
</p
>
5841 <p
>The attributes are normally provided in the cosine (RFC
1274) and
5842 dnsdomain2 schemas. The latter is used for reverse entries like
5843 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
5845 <p
>In Debian Edu, we have created DNS objects using the object classes
5846 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
5847 attributes) and domainrelatedobject (for associatedDomain). The use
5848 of structural object classes make it impossible to combine these
5849 classes with the object classes used by DHCP.
</p
>
5851 <p
>There are other schemas that could be used too, for example the
5852 dnszone structural object class used by Gosa and bind-sdb for the DNS
5853 attributes combined with the domainrelatedobject object class, but in
5854 this case some unused attributes would have to be included as well
5855 (zonename and relativedomainname).
</p
>
5857 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
5858 mode and not use any of the existing objectclasses (dnsdomain,
5859 dnsdomain2 and dnszone) when one want to combine the DNS information
5860 with DHCP information, and instead create a auxiliary object class
5861 defined something like this (using the attributes defined for
5862 dnsdomain and dnsdomain2 or dnszone):
</p
>
5864 <blockquote
><pre
>
5865 objectclass ( some-oid NAME
'dnsDomainAux
'
5868 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
5869 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
5870 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
5871 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
5872 A6Record $ DNAMERecord
5874 </pre
></blockquote
>
5876 <p
>This will allow any object to become a DNS entry when combined with
5877 the domainrelatedobject object class, and allow any entity to include
5878 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
5879 developers asking for their view on this schema and if they are
5880 interested in providing such schema with PowerDNS, and I hope my
5881 message will be accepted into their mailing list soon.
</p
>
5883 <p
><strong
>ISC dhcp
</strong
></p
>
5885 <p
>The DHCP server searches for specific objectclass and requests all
5886 the object attributes, and then uses the attributes it want. This
5887 make it harder to figure out exactly what attributes are used, but
5888 thanks to the working example in Debian Edu I can at least get an idea
5889 what is needed without having to read the source code.
</p
>
5891 <p
>In the DHCP server configuration, the LDAP base to use and the
5892 search filter to use to locate the correct dhcpServer entity is
5893 stored. These are the relevant entries from
5894 /etc/dhcp3/dhcpd.conf:
</p
>
5896 <blockquote
><pre
>
5897 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
5898 ldap-dhcp-server-cn
"dhcp
";
5899 </pre
></blockquote
>
5901 <p
>The DHCP server uses this information to nest all the DHCP
5902 configuration it need. The cn
"dhcp
" is located using the given LDAP
5903 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
5904 search result is this entry:
</p
>
5906 <blockquote
><pre
>
5907 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
5910 objectClass: dhcpServer
5911 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5912 </pre
></blockquote
>
5914 <p
>The content of the dhcpServiceDN attribute is next used to locate the
5915 subtree with DHCP configuration. The DHCP configuration subtree base
5916 is located using a base scope search with base
"cn=DHCP
5917 Config,dc=skole,dc=skolelinux,dc=no
" and filter
5918 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
5919 The search result is this entry:
</p
>
5921 <blockquote
><pre
>
5922 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5925 objectClass: dhcpService
5926 objectClass: dhcpOptions
5927 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
5928 dhcpStatements: ddns-update-style none
5929 dhcpStatements: authoritative
5930 dhcpOption: smtp-server code
69 = array of ip-address
5931 dhcpOption: www-server code
72 = array of ip-address
5932 dhcpOption: wpad-url code
252 = text
5933 </pre
></blockquote
>
5935 <p
>Next, the entire subtree is processed, one level at the time. When
5936 all the DHCP configuration is loaded, it is ready to receive requests.
5937 The subtree in Debian Edu contain objects with object classes
5938 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
5939 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
5940 and information about netmasks, dynamic range etc. Leaving out the
5941 details here because it is not relevant for the focus of my
5942 investigation, which is to see if it is possible to merge dns and dhcp
5943 related computer objects.
</p
>
5945 <p
>When a DHCP request come in, LDAP is searched for the MAC address
5946 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
5947 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
5948 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
5949 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
5952 <blockquote
><pre
>
5953 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5956 objectClass: dhcpHost
5957 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
5958 dhcpStatements: fixed-address hostname
5959 </pre
></blockquote
>
5961 <p
>There is less flexiblity in the way LDAP searches are done here.
5962 The object classes need to have fixed names, and the configuration
5963 need to be stored in a fairly specific LDAP structure. On the
5964 positive side, the invidiual dhcpHost entires can be anywhere without
5965 the DN pointed to by the dhcpServer entries. The latter should make
5966 it possible to group all host entries in a subtree next to the
5967 configuration entries, and this subtree can also be shared with the
5968 DNS server if the schema proposed above is combined with the dhcpHost
5969 structural object class.
5971 <p
><strong
>Conclusion
</strong
></p
>
5973 <p
>The PowerDNS implementation seem to be very flexible when it come
5974 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
5975 come to the the LDAP structure, the
"strict
" mode is very flexible,
5976 allowing DNS objects to be stored anywhere under the base cn specified
5977 in the configuration.
</p
>
5979 <p
>The DHCP implementation on the other hand is very inflexible, both
5980 regarding which LDAP schemas to use and which LDAP structure to use.
5981 I guess one could implement ones own schema, as long as the
5982 objectclasses and attributes have the names used, but this do not
5983 really help when the DHCP subtree need to have a fairly fixed
5984 structure.
</p
>
5986 <p
>Based on the observed behaviour, I suspect a LDAP structure like
5987 this might work for Debian Edu:
</p
>
5989 <blockquote
><pre
>
5991 cn=machine-info (dhcpService) - dhcpServiceDN points here
5992 cn=dhcp (dhcpServer)
5993 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
5994 cn=
10.0.2.0 (dhcpSubnet)
5995 cn=group1 (dhcpGroup/dhcpOptions)
5996 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
5997 cn=
192.168.0.0 (dhcpSubnet)
5998 cn=group1 (dhcpGroup/dhcpOptions)
5999 ou=machines - PowerDNS base points here
6000 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6001 </pre
></blockquote
>
6003 <P
>This is not tested yet. If the DHCP server require the dhcpHost
6004 entries to be in the dhcpGroup subtrees, the entries can be stored
6005 there instead of a common machines subtree, and the PowerDNS base
6006 would have to be moved one level up to the machine-info subtree.
</p
>
6008 <p
>The combined object under the machines subtree would look something
6009 like this:
</p
>
6011 <blockquote
><pre
>
6012 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6015 objectClass: dhcpHost
6016 objectclass: domainrelatedobject
6017 objectclass: dnsDomainAux
6018 associateddomain: hostname.intern
6019 arecord:
10.11.12.13
6020 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
6021 dhcpStatements: fixed-address hostname.intern
6022 </pre
></blockquote
>
6024 </p
>One could even add the LTSP configuration associated with a given
6025 machine, as long as the required attributes are available in a
6026 auxiliary object class.
</p
>
6031 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
6032 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
6033 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
6034 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
6035 <description><p
>For a while now, I have wanted to find a way to change the DNS and
6036 DHCP services in Debian Edu to use the same LDAP objects for a given
6037 computer, to avoid the possibility of having a inconsistent state for
6038 a computer in LDAP (as in DHCP but no DNS entry or the other way
6039 around) and make it easier to add computers to LDAP.
</p
>
6041 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
6042 information finally found a solution that seem to work.
</p
>
6044 <p
>The old setup required three LDAP objects for a given computer.
6045 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6046 we switch powerdns to use its strict LDAP method (ldap-method=strict
6047 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6048 merged into one while making it impossible to transfer the reverse map
6049 to a slave DNS server.
</p
>
6051 <p
>If we also replace the object class used to get the DNS related
6052 attributes to one allowing these attributes to be combined with the
6053 dhcphost object class, we can merge the DNS and DHCP entries into one.
6054 I
've written such object class in the dnsdomainaux.schema file (need
6055 proper OIDs, but that is a minor issue), and tested the setup. It
6056 seem to work.
</p
>
6058 <p
>With this test setup in place, we can get away with one LDAP object
6059 for both DNS and DHCP, and even the LTSP configuration I suggested in
6060 an earlier email. The combined LDAP object will look something like
6063 <blockquote
><pre
>
6064 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6066 objectClass: dhcphost
6067 objectclass: domainrelatedobject
6068 objectclass: dnsdomainaux
6069 associateddomain: hostname.intern
6070 arecord:
10.11.12.13
6071 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
6072 dhcpstatements: fixed-address hostname
6074 </pre
></blockquote
>
6076 <p
>The DNS server uses the associateddomain and arecord entries, while
6077 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6078 before asking DNS to resolve the fixed-adddress. LTSP will use
6079 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
6081 <p
>I am not yet sure if I can get the DHCP server to look for its
6082 dhcphost in a different location, to allow us to put the objects
6083 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
6084 that. If I can
't figure out a way to do that, we can still get rid of
6085 the hosts subtree and move all its content into the DHCP Config tree
6086 (which probably should be renamed to be more related to the new
6087 content. I suspect cn=dnsdhcp,ou=services or something like that
6088 might be a good place to put it.
</p
>
6090 <p
>If you want to help out with implementing this for Debian Edu,
6091 please contact us on debian-edu@lists.debian.org.
</p
>
6096 <title>Idea for storing LTSP configuration in LDAP
</title>
6097 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
6098 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
6099 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
6100 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
6101 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6102 clients, and that this can be used to fetch configuration from LDAP if
6103 Debian Edu choose to store configuration there.
</p
>
6105 <p
>Armed with this information, I got inspired and wrote a test module
6106 to get configuration from LDAP. The idea is to look up the MAC
6107 address of the client in LDAP, and look for attributes on the form
6108 ltspconfigsetting=value, and use this to export SETTING=value to the
6109 LTSP clients.
</p
>
6111 <p
>The goal is to be able to store the LTSP configuration attributes
6112 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
6113 allowing us to store all information about a computer in one place.
</p
>
6115 <p
>This is a untested draft implementation, and I welcome feedback on
6116 this approach. A real LDAP schema for the ltspClientAux objectclass
6117 need to be written. Comments, suggestions, etc?
</p
>
6119 <blockquote
><pre
>
6120 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6122 # Fetch LTSP client settings from LDAP based on MAC address
6124 # Uses ethernet address as stored in the dhcpHost objectclass using
6125 # the dhcpHWAddress attribute or ethernet address stored in the
6126 # ieee802Device objectclass with the macAddress attribute.
6128 # This module is written to be schema agnostic, and only depend on the
6129 # existence of attribute names.
6131 # The LTSP configuration variables are saved directly using a
6132 # ltspConfig prefix and uppercasing the rest of the attribute name.
6133 # To set the SERVER variable, set the ltspConfigServer attribute.
6135 # Some LDAP schema should be created with all the relevant
6136 # configuration settings. Something like this should work:
6138 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
6141 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6143 LDAPSERVER=$(debian-edu-ldapserver)
6144 if [
"$LDAPSERVER
" ] ; then
6145 LDAPBASE=$(debian-edu-ldapserver -b)
6146 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
6147 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
6148 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
6149 grep
'^ltspConfig
' | while read attr value ; do
6150 # Remove prefix and convert to upper case
6151 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
6152 # bass value on to clients
6153 eval
"$attr=$value; export $attr
"
6157 </pre
></blockquote
>
6159 <p
>I
'm not sure this shell construction will work, because I suspect
6160 the while block might end up in a subshell causing the variables set
6161 there to not show up in ltsp-config, but if that is the case I am sure
6162 the code can be restructured to make sure the variables are passed on.
6163 I expect that can be solved with some testing. :)
</p
>
6165 <p
>If you want to help out with implementing this for Debian Edu,
6166 please contact us on debian-edu@lists.debian.org.
</p
>
6168 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
6169 configuration in LDAP that was created around year
2000 by
6170 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
6171 Xperience, Inc.,
2000</a
>. I found its
6172 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
6173 personal home page over at redhat.com.
</p
>
6178 <title>jXplorer, a very nice LDAP GUI
</title>
6179 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
6180 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
6181 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
6182 <description><p
>Since
6183 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
6184 last post
</a
> about available LDAP tools in Debian, I was told about a
6185 LDAP GUI that is even better than luma. The java application
6186 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
6187 moving LDAP objects and subtrees using drag-and-drop, and can
6188 authenticate using Kerberos. I have only tested the Kerberos
6189 authentication, but do not have a LDAP setup allowing me to rewrite
6190 LDAP with my test user yet. It is
6191 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
6192 Debian
</a
> testing and unstable at the moment. The only problem I
6193 have with it is how it handle errors. If something go wrong, its
6194 non-intuitive behaviour require me to go through some query work list
6195 and remove the failing query. Nothing big, but very annoying.
</p
>
6200 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
6201 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
6202 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
6203 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
6204 <description><p
>Here is a short update on my
<a
6205 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
6206 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
6207 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
6208 not reporting the status for KDE, because the upgrade crashes when
6209 aptitude try because of missing conflicts
6210 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
6211 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
6213 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
6214 complete list of the installed packages. Based on this I see these
6215 differences when I did a test run today. As usual, I do not really
6216 know what the correct set of packages would be, but thought it best to
6217 publish the difference.
</p
>
6219 <p
>Installed using apt-get, missing with aptitude
</p
>
6221 <blockquote
><p
>
6222 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
6223 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
6224 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6225 libgtksourceview-common libpt-
1.10.10-plugins-alsa
6226 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6227 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6228 python-
4suite-xml python-eggtrayicon python-gtkhtml2
6229 python-gtkmozembed svgalibg1 xserver-xephyr zip
6230 </p
></blockquote
>
6232 <p
>Installed using apt-get, removed with aptitude
</p
>
6234 <blockquote
><p
>
6235 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6236 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6237 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
6238 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
6239 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
6240 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
6241 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
6242 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
6243 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
6244 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
6245 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
6246 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
6247 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6248 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
6249 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6250 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
6251 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
6252 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6253 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6254 mysql-common swfdec-gnome totem-gstreamer wodim
6255 </p
></blockquote
>
6257 <p
>Installed using aptitude, missing with apt-get
</p
>
6259 <blockquote
><p
>
6260 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6261 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6262 xserver-xorg-input-all xserver-xorg-input-evdev
6263 xserver-xorg-input-kbd xserver-xorg-input-mouse
6264 xserver-xorg-input-synaptics xserver-xorg-video-all
6265 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6266 xserver-xorg-video-chips xserver-xorg-video-cirrus
6267 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6268 xserver-xorg-video-glint xserver-xorg-video-i128
6269 xserver-xorg-video-i740 xserver-xorg-video-mach64
6270 xserver-xorg-video-mga xserver-xorg-video-neomagic
6271 xserver-xorg-video-nouveau xserver-xorg-video-nv
6272 xserver-xorg-video-r128 xserver-xorg-video-radeon
6273 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6274 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6275 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6276 xserver-xorg-video-sis xserver-xorg-video-sisusb
6277 xserver-xorg-video-tdfx xserver-xorg-video-tga
6278 xserver-xorg-video-trident xserver-xorg-video-tseng
6279 xserver-xorg-video-vesa xserver-xorg-video-vmware
6280 xserver-xorg-video-voodoo
6281 </p
></blockquote
>
6283 <p
>Installed using aptitude, removed with apt-get
</p
>
6285 <blockquote
><p
>
6286 deskbar-applet xserver-xorg xserver-xorg-core
6287 xserver-xorg-input-wacom xserver-xorg-video-intel
6288 xserver-xorg-video-openchrome
6289 </p
></blockquote
>
6291 <p
>I was told on IRC that the xorg-xserver package was
6292 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
6293 in git
</a
> today to try to get apt-get to not remove xorg completely.
6294 No idea when it hits Squeeze, but when it does I hope it will reduce
6295 the difference somewhat.
6300 <title>LUMA, a very nice LDAP GUI
</title>
6301 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
6302 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
6303 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
6304 <description><p
>The last few days I have been looking into the status of the LDAP
6305 directory in Debian Edu, and in the process I started to miss a GUI
6306 tool to browse the LDAP tree. The only one I was able to find in
6307 Debian/Squeeze and Lenny is
6308 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
6309 be a great tool to get a overview of the current LDAP directory
6310 populated by default in Skolelinux. Thanks to it, I have been able to
6311 find empty and obsolete subtrees, misplaced objects and duplicate
6312 objects. It will be installed by default in Debian/Squeeze. If you
6313 are working with LDAP, give it a go. :)
</p
>
6315 <p
>I did notice one problem with it I have not had time to report to
6316 the BTS yet. There is no .desktop file in the package, so the tool do
6317 not show up in the Gnome and KDE menus, but only deep down in in the
6318 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6321 <p
>I have not yet been able to get it to modify the tree yet. I would
6322 like to move objects and remove subtrees directly in the GUI, but have
6323 not found a way to do that with LUMA yet. So in the mean time, I use
6324 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
6326 <p
>If you have tips on other GUI tools for LDAP that might be useful
6327 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
6329 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
6330 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
6331 useful GUI alternative. It seem like a good tool, but is unmaintained
6332 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6333 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
6338 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
6339 <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>
6340 <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>
6341 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
6342 <description><p
>A while back, I
6343 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
6344 about the fact
</a
> that it is not possible with the provided schemas
6345 for storing DNS and DHCP information in LDAP to combine the two sets
6346 of information into one LDAP object representing a computer.
</p
>
6348 <p
>In the mean time, I discovered that a simple fix would be to make
6349 the dhcpHost object class auxiliary, to allow it to be combined with
6350 the dNSDomain object class, and thus forming one object for one
6351 computer when storing both DHCP and DNS information in LDAP.
</p
>
6353 <p
>If I understand this correctly, it is not safe to do this change
6354 without also changing the assigned number for the object class, and I
6355 do not know enough about LDAP schema design to do that properly for
6356 Debian Edu.
</p
>
6358 <p
>Anyway, for future reference, this is how I believe we could change
6360 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
6361 schema
</a
> to solve at least part of the problem with the LDAP schemas
6362 available today from IETF.
</p
>
6365 --- dhcp.schema (revision
65192)
6366 +++ dhcp.schema (working copy)
6368 objectclass (
2.16.840.1.113719.1.203.6.6
6369 NAME
'dhcpHost
'
6370 DESC
'This represents information about a particular client
'
6374 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6375 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
6378 <p
>I very much welcome clues on how to do this properly for Debian
6379 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6380 package, and should thus be free to rewrite it as we see fit.
</p
>
6382 <p
>If you want to help out with implementing this for Debian Edu,
6383 please contact us on debian-edu@lists.debian.org.
</p
>
6388 <title>Calling tasksel like the installer, while still getting useful output
</title>
6389 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
6390 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
6391 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
6392 <description><p
>A few times I have had the need to simulate the way tasksel
6393 installs packages during the normal debian-installer run. Until now,
6394 I have ended up letting tasksel do the work, with the annoying problem
6395 of not getting any feedback at all when something fails (like a
6396 conffile question from dpkg or a download that fails), using code like
6399 <blockquote
><pre
>
6400 export DEBIAN_FRONTEND=noninteractive
6401 tasksel --new-install
6402 </pre
></blockquote
>
6404 This would invoke tasksel, let its automatic task selection pick the
6405 tasks to install, and continue to install the requested tasks without
6406 any output what so ever.
6408 Recently I revisited this problem while working on the automatic
6409 package upgrade testing, because tasksel would some times hang without
6410 any useful feedback, and I want to see what is going on when it
6411 happen. Then it occured to me, I can parse the output from tasksel
6412 when asked to run in test mode, and use that aptitude command line
6413 printed by tasksel then to simulate the tasksel run. I ended up using
6416 <blockquote
><pre
>
6417 export DEBIAN_FRONTEND=noninteractive
6418 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
6420 </pre
></blockquote
>
6422 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
6423 --without-recommends -o APT::Install-Recommends=no -y install
6424 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6425 ~pimportant
</tt
>", which will install the gnome desktop task, the
6426 laptop task and all packages with priority standard , required and
6427 important, just like tasksel would have done it during
6428 installation.
</p
>
6430 <p
>A better approach is probably to extend tasksel to be able to
6431 install packages without using debconf-apt-progress, for use cases
6432 like this.
</p
>
6437 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
6438 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
6439 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
6440 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
6441 <description><p
>My
6442 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
6443 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
6444 finally made the upgrade logs available from
6445 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
6446 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6447 apt and aptitude, and found their differences interesting. This time
6448 I will only focus on their removal plans.
</p
>
6450 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
6451 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
6452 surprising part is that it want to remove xorg and all
6453 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6454 sure why. When asking aptitude to do the same, it want to remove
129
6455 packages, but most of them are library packages I suspect are no
6456 longer needed. Both of them want to remove bluetooth packages, which
6457 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
6459 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
6460 which seem like a bad idea and xorg the same way as with Gnome. Asking
6461 aptitude for the same, it wants to remove
192 packages, none which are
6462 too surprising.
</p
>
6464 <p
>I guess the removal of xorg during upgrades should be investigated
6465 and avoided, and perhaps others as well. Here are the complete list
6466 of planned removals. The complete logs is available from the URL
6467 above. Note if you want to repeat these tests, that the upgrade test
6468 for kde+apt-get hung in the tasksel setup because of dpkg asking
6469 conffile questions. No idea why. I worked around it by using
6470 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
6473 <p
><b
>apt-get gnome
72</b
>
6474 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
6475 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6476 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
6477 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6478 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6479 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6480 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6481 xserver-xorg-input-kbd xserver-xorg-input-mouse
6482 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6483 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6484 xserver-xorg-video-ati xserver-xorg-video-chips
6485 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6486 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6487 xserver-xorg-video-glint xserver-xorg-video-i128
6488 xserver-xorg-video-i740 xserver-xorg-video-imstt
6489 xserver-xorg-video-intel xserver-xorg-video-mach64
6490 xserver-xorg-video-mga xserver-xorg-video-neomagic
6491 xserver-xorg-video-nsc xserver-xorg-video-nv
6492 xserver-xorg-video-openchrome xserver-xorg-video-r128
6493 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6494 xserver-xorg-video-rendition xserver-xorg-video-s3
6495 xserver-xorg-video-s3virge xserver-xorg-video-savage
6496 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6497 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6498 xserver-xorg-video-tga xserver-xorg-video-trident
6499 xserver-xorg-video-tseng xserver-xorg-video-v4l
6500 xserver-xorg-video-vesa xserver-xorg-video-vga
6501 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
6502 xulrunner-
1.9-gnome-support
</p
>
6504 <p
><b
>aptitude gnome
129</b
>
6506 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
6507 djvulibre-desktop finger gnome-app-install gnome-mount
6508 gnome-network-admin gnome-spell gnome-vfs-obexftp
6509 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6510 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6511 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6512 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
6513 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
6514 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
6515 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
6516 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
6517 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
6518 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
6519 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
6520 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
6521 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6522 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
6523 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
6524 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
6525 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
6526 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
6527 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6528 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6529 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6530 openoffice.org-writer2latex openssl-blacklist p7zip
6531 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
6532 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6533 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6534 swfdec-mozilla totem-gstreamer update-manager wodim
6535 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6536 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6539 <p
><b
>apt-get kde
82</b
>
6541 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6542 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6543 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6544 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6545 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6546 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6547 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6548 xserver-xorg-input-kbd xserver-xorg-input-mouse
6549 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6550 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6551 xserver-xorg-video-ati xserver-xorg-video-chips
6552 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6553 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6554 xserver-xorg-video-glint xserver-xorg-video-i128
6555 xserver-xorg-video-i740 xserver-xorg-video-imstt
6556 xserver-xorg-video-intel xserver-xorg-video-mach64
6557 xserver-xorg-video-mga xserver-xorg-video-neomagic
6558 xserver-xorg-video-nsc xserver-xorg-video-nv
6559 xserver-xorg-video-openchrome xserver-xorg-video-r128
6560 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6561 xserver-xorg-video-rendition xserver-xorg-video-s3
6562 xserver-xorg-video-s3virge xserver-xorg-video-savage
6563 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6564 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6565 xserver-xorg-video-tga xserver-xorg-video-trident
6566 xserver-xorg-video-tseng xserver-xorg-video-v4l
6567 xserver-xorg-video-vesa xserver-xorg-video-vga
6568 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
6570 <p
><b
>aptitude kde
192</b
>
6571 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
6572 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6573 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6574 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6575 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6576 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6577 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6578 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6579 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6580 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6581 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6582 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6583 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6584 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6585 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6586 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6587 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6588 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6589 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
6590 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6591 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6592 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
6593 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6594 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6595 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6596 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6597 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6598 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
6599 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
6600 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6601 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6602 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6603 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6604 texlive-common texlive-doc-base texlive-fonts-recommended
6605 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6606 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6607 xulrunner-
1.9</p
>
6613 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
6614 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
6615 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
6616 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
6617 <description><p
>The last few days I have done some upgrade testing in Debian, to
6618 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6619 have been discovered and reported in the process
6620 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
6621 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
6622 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
6623 kdebase-workspace-data), and to get a more regular testing going on, I
6624 am working on a script to automate the test.
</p
>
6626 <p
>The idea is to create a Lenny chroot and use tasksel to install a
6627 Gnome or KDE desktop installation inside the chroot before upgrading
6628 it. To ensure no services are started in the chroot, a policy-rc.d
6629 script is inserted. To make sure tasksel believe it is to install a
6630 desktop on a laptop, the tasksel tests are replaced in the chroot
6631 (only acceptable because this is a throw-away chroot).
</p
>
6633 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6634 currently always fail because udev refuses to upgrade with the kernel
6635 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6636 is created. The bug report
6637 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
6638 this problem do not trigger in a chroot, but I touch the file anyway
6639 to make sure the upgrade go well. Testing on virtual and real
6640 hardware have failed me because of udev so far, and creating this file
6641 do the trick in such settings anyway. This is a
6642 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
6643 issue
</a
> and the current udev behaviour is intended by the udev
6644 maintainer because he lack the resources to rewrite udev to keep
6645 working with old kernels or something like that. I really wish the
6646 udev upstream would keep udev backwards compatible, to avoid such
6647 upgrade problem, but given that they fail to do so, I guess
6648 documenting the way out of this mess is the best option we got for
6649 Debian Squeeze.
</p
>
6651 <p
>Anyway, back to the task at hand, testing upgrades. This test
6652 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
6655 <blockquote
><pre
>
6659 if [
"$
1" ] ; then
6668 exec
&lt; /dev/null
6670 mirror=http://ftp.skolelinux.org/debian
6671 tmpdir=chroot-$from-upgrade-$to-$desktop
6673 debootstrap $from $tmpdir $mirror
6674 chroot $tmpdir aptitude update
6675 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
6679 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6683 mount -t proc proc $tmpdir/proc
6684 # Make sure proc is unmounted also on failure
6685 trap exit_cleanup EXIT INT
6687 chroot $tmpdir aptitude -y install debconf-utils
6689 # Make sure tasksel autoselection trigger. It need the test scripts
6690 # to return the correct answers.
6691 echo tasksel tasksel/desktop multiselect $desktop | \
6692 chroot $tmpdir debconf-set-selections
6694 # Include the desktop and laptop task
6695 for test in desktop laptop ; do
6696 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
6700 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6703 DEBIAN_FRONTEND=noninteractive
6704 DEBIAN_PRIORITY=critical
6705 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6706 chroot $tmpdir tasksel --new-install
6708 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
6709 chroot $tmpdir aptitude update
6710 touch $tmpdir/etc/udev/kernel-upgrade
6711 chroot $tmpdir aptitude -y dist-upgrade
6713 </pre
></blockquote
>
6715 <p
>I suspect it would be useful to test upgrades with both apt-get and
6716 with aptitude, but I have not had time to look at how they behave
6717 differently so far. I hope to get a cron job running to do the test
6718 regularly and post the result on the web. The Gnome upgrade currently
6719 work, while the KDE upgrade fail because of the bug in
6720 kdebase-workspace-data
</p
>
6722 <p
>I am not quite sure what kind of extract from the huge upgrade logs
6723 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
6724 post, so I will refrain from trying. I can report that for Gnome,
6725 aptitude report
760 packages upgraded,
448 newly installed,
129 to
6726 remove and
1 not upgraded and
1024MB need to be downloaded while for
6727 KDE the same numbers are
702 packages upgraded,
507 newly installed,
6728 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
6730 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
6731 is able to migrate to dependency based boot sequencing and parallel
6732 booting without a hitch. Was unsure if there were still bugs with
6733 packages failing to clean up their obsolete init.d script during
6734 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6740 <title>Upstart or sysvinit - as init.d scripts see it
</title>
6741 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
6742 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
6743 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
6744 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
6745 scripts to migrate (some of) their operations to upstart job while
6746 keeping the init.d for hurd and kfreebsd. The packages with such
6747 needs will need a way to get their init.d scripts to behave
6748 differently when used with sysvinit and with upstart. Because of
6749 this, I had a look at the environment variables set when a init.d
6750 script is running under upstart, and when it is not.
</p
>
6752 <p
>With upstart, I notice these environment variables are set when a
6753 script is started from rcS.d/ (ignoring some irrelevant ones like
6756 <blockquote
><pre
>
6762 UPSTART_EVENTS=startup
6764 UPSTART_JOB=rc-sysinit
6765 </pre
></blockquote
>
6767 <p
>With sysvinit, these environment variables are set for the same
6770 <blockquote
><pre
>
6771 INIT_VERSION=sysvinit-
2.88
6776 </pre
></blockquote
>
6778 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
6779 sysvinit are not set by upstart. Not sure if it is intentional or not
6780 to not be compatible with sysvinit in this regard.
</p
>
6782 <p
>For scripts needing to behave differently when upstart is used,
6783 looking for the UPSTART_JOB environment variable seem to be a good
6789 <title>A manual for standards wars...
</title>
6790 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
6791 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
6792 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
6793 <description><p
>Via the
6794 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
6795 of Rob Weir
</a
> I came across the very interesting essay named
6796 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
6797 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
6798 following the standards wars of today.
</p
>
6803 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
6804 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
6805 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
6806 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
6807 <description><p
>When using sitesummary at a site to track machines, it is possible
6808 to get a list of the machine types in use thanks to the DMI
6809 information extracted from each machine. The script to do so is
6810 included in the sitesummary package, and here is example output from
6811 the Skolelinux build servers:
</p
>
6813 <blockquote
><pre
>
6814 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
6816 Dell Computer Corporation
1
6819 eserver xSeries
345 -[
8670M1X]-
1
6823 </pre
></blockquote
>
6825 <p
>The quality of the report depend on the quality of the DMI tables
6826 provided in each machine. Here there are Intel machines without model
6827 information listed with Intel as vendor and no model, and virtual Xen
6828 machines listed as [no-dmi-info]. One can add -l as a command line
6829 option to list the individual machines.
</p
>
6831 <p
>A larger list is
6832 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
6833 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
6834 provide the basic sitesummary report publicly. In their report there
6835 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
6836 their machines, and as sitesummary is available in both distributions,
6837 it is trivial to get all of them to report to the same central
6838 collector.
</p
>
6843 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
6844 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
6845 <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>
6846 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
6847 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
6848 start at boot when an NVidia video card is used is handled. The
6849 problem seem to be that the nvidia X.org driver uses a long time to
6850 initialize, and this duration is longer than kdm is configured to
6853 <p
>I came across two bugs related to this issue,
6854 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
6855 against initscripts and passed on to nvidia-glx when it became obvious
6856 that the nvidia drivers were involved, and
6857 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
6858 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
6860 <p
>To me, it seem that no-one is interested in actually solving the
6861 problem nvidia video card owners experience and make sure the Debian
6862 distribution work out of the box for these users. The nvidia driver
6863 maintainers expect kdm to be set up to wait longer, while kdm expect
6864 the nvidia driver maintainers to fix the driver to start faster, and
6865 while they wait for each other I guess the users end up switching to a
6866 distribution that work for them. I have no idea what the solution is,
6867 but I am pretty sure that waiting for each other is not it.
</p
>
6869 <p
>I wonder why we end up handling bugs this way.
</p
>
6874 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
6875 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
6876 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
6877 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
6878 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
6879 The feature seem to hold up pretty well, but three fairly serious
6880 issues are known and should be solved:
6884 <li
>The wicd package seen to
6885 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
6886 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
6887 parallel booting is enabled. No idea why, but the wicd maintainer
6888 seem to be on the case.
</li
>
6890 <li
>The nvidia X driver seem to
6891 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
6892 triggered more easily when parallel booting is in effect. The
6893 maintainer is on the case.
</li
>
6895 <li
>The sysv-rc package fail to properly enable dependency based boot
6896 sequencing (the shutdown is broken) when old file-rc users
6897 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
6898 sysv-rc. One way to solve it would be for file-rc to create
6899 /etc/init.d/.legacy-bootordering, and another is to try to make
6900 sysv-rc more robust. Will investigate some more and probably upload a
6901 workaround in sysv-rc to help those trying to move from file-rc to
6902 sysv-rc get a working shutdown.
</li
>
6904 </ul
></p
>
6906 <p
>All in all not many surprising issues, and all of them seem
6907 solvable before Squeeze is released. In addition to these there are
6908 some packages with bugs in their dependencies and run level settings,
6909 which I expect will be fixed in a reasonable time span.
</p
>
6911 <p
>If you report any problems with dependencies in init.d scripts to
6912 the BTS, please usertag the report to get it to show up at
6913 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
6914 list of usertagged bugs related to this
</a
>.
</p
>
6916 <p
>Update: Correct bug number to file-rc issue.
</p
>
6921 <title>More flexible firmware handling in debian-installer
</title>
6922 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
6923 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
6924 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
6925 <description><p
>After a long break from debian-installer development, I finally
6926 found time today to return to the project. Having to spend less time
6927 working dependency based boot in debian, as it is almost complete now,
6928 definitely helped freeing some time.
</p
>
6930 <p
>A while back, I ran into a problem while working on Debian Edu. We
6931 include some firmware packages on the Debian Edu CDs, those needed to
6932 get disk and network controllers working. Without having these
6933 firmware packages available during installation, it is impossible to
6934 install Debian Edu on the given machine, and because our target group
6935 are non-technical people, asking them to provide firmware packages on
6936 an external medium is a support pain. Initially, I expected it to be
6937 enough to include the firmware packages on the CD to get
6938 debian-installer to find and use them. This proved to be wrong.
6939 Next, I hoped it was enough to symlink the relevant firmware packages
6940 to some useful location on the CD (tried /cdrom/ and
6941 /cdrom/firmware/). This also proved to not work, and at this point I
6942 found time to look at the debian-installer code to figure out what was
6943 going to work.
</p
>
6945 <p
>The firmware loading code is in the hw-detect package, and a closer
6946 look revealed that it would only look for firmware packages outside
6947 the installation media, so the CD was never checked for firmware
6948 packages. It would only check USB sticks, floppies and other
6949 "external
" media devices. Today I changed it to also look in the
6950 /cdrom/firmware/ directory on the mounted CD or DVD, which should
6951 solve the problem I ran into with Debian edu. I also changed it to
6952 look in /firmware/, to make sure the installer also find firmware
6953 provided in the initrd when booting the installer via PXE, to allow us
6954 to provide the same feature in the PXE setup included in Debian
6957 <p
>To make sure firmware deb packages with a license questions are not
6958 activated without asking if the license is accepted, I extended
6959 hw-detect to look for preinst scripts in the firmware packages, and
6960 run these before activating the firmware during installation. The
6961 license question is asked using debconf in the preinst, so this should
6962 solve the issue for the firmware packages I have looked at so far.
</p
>
6964 <p
>If you want to discuss the details of these features, please
6965 contact us on debian-boot@lists.debian.org.
</p
>
6970 <title>Parallellized boot is now the default in Debian/unstable
</title>
6971 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
6972 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
6973 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
6974 <description><p
>Since this evening, parallel booting is the default in
6975 Debian/unstable for machines using dependency based boot sequencing.
6976 Apparently the testing of concurrent booting has been wider than
6977 expected, if I am to believe the
6978 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
6979 on debian-devel@
</a
>, and I concluded a few days ago to move forward
6980 with the feature this weekend, to give us some time to detect any
6981 remaining problems before Squeeze is frozen. If serious problems are
6982 detected, it is simple to change the default back to sequential boot.
6983 The upload of the new sysvinit package also activate a new upstream
6986 More information about
6987 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
6988 based boot sequencing
</a
> is available from the Debian wiki. It is
6989 currently possible to disable parallel booting when one run into
6990 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
6992 <blockquote
><pre
>
6994 </pre
></blockquote
>
6996 <p
>If you report any problems with dependencies in init.d scripts to
6997 the BTS, please usertag the report to get it to show up at
6998 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
6999 list of usertagged bugs related to this
</a
>.
</p
>
7004 <title>Sitesummary tip: Listing MAC address of all clients
</title>
7005 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
7006 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
7007 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
7008 <description><p
>In the recent Debian Edu versions, the
7009 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
7010 system
</a
> is used to keep track of the machines in the school
7011 network. Each machine will automatically report its status to the
7012 central server after boot and once per night. The network setup is
7013 also reported, and using this information it is possible to get the
7014 MAC address of all network interfaces in the machines. This is useful
7015 to update the DHCP configuration.
</p
>
7017 <p
>To give some idea how to use sitesummary, here is a one-liner to
7018 ist all MAC addresses of all machines reporting to sitesummary. Run
7019 this on the collector host:
</p
>
7021 <blockquote
><pre
>
7022 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
7023 </pre
></blockquote
>
7025 <p
>This will list all MAC addresses assosiated with all machine, one
7026 line per machine and with space between the MAC addresses.
</p
>
7028 <p
>To allow system administrators easier job at adding static DHCP
7029 addresses for hosts, it would be possible to extend this to fetch
7030 machine information from sitesummary and update the DHCP and DNS
7031 tables in LDAP using this information. Such tool is unfortunately not
7032 written yet.
</p
>
7037 <title>systemd, an interesting alternative to upstart
</title>
7038 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
7039 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
7040 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
7041 <description><p
>The last few days a new boot system called
7042 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
7044 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
7046 to the free software world. I have not yet had time to play around
7047 with it, but it seem to be a very interesting alternative to
7048 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
7049 a good alternative for Debian when we are able to switch to an event
7050 based boot system. Tollef is
7051 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
7052 systemd into Debian, and I look forward to seeing how well it work. I
7053 like the fact that systemd handles init.d scripts with dependency
7054 information natively, allowing them to run in parallel where upstart
7055 at the moment do not.
</p
>
7057 <p
>Unfortunately do systemd have the same problem as upstart regarding
7058 platform support. It only work on recent Linux kernels, and also need
7059 some new kernel features enabled to function properly. This means
7060 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7061 system. Not sure how that will be handled if systemd proves to be the
7062 way forward.
</p
>
7064 <p
>In the mean time, based on the
7065 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
7066 on debian-devel@
</a
> regarding parallel booting in Debian, I have
7067 decided to enable full parallel booting as the default in Debian as
7068 soon as possible (probably this weekend or early next week), to see if
7069 there are any remaining serious bugs in the init.d dependencies. A
7070 new version of the sysvinit package implementing this change is
7071 already in experimental. If all go well, Squeeze will be released
7072 with parallel booting enabled by default.
</p
>
7077 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
7078 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
7079 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
7080 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
7081 <description><p
>These days, the init.d script dependencies in Squeeze are quite
7082 complete, so complete that it is actually possible to run all the
7083 init.d scripts in parallell based on these dependencies. If you want
7084 to test your Squeeze system, make sure
7085 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
7086 based boot sequencing
</a
> is enabled, and add this line to
7087 /etc/default/rcS:
</p
>
7089 <blockquote
><pre
>
7090 CONCURRENCY=makefile
7091 </pre
></blockquote
>
7093 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
7094 scripts in parallel using the dependency information stored in
7095 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7096 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7097 to try to start the kdm and gdm scripts as early as possible, and will
7098 start the facilities required by kdm or gdm as early as possible to
7099 make this happen.
</p
>
7101 <p
>Give it a try, and see if you like the result. If some services
7102 fail to start properly, it is most likely because they have incomplete
7103 init.d script dependencies in their startup script (or some of their
7104 dependent scripts have incomplete dependencies). Report bugs and get
7105 the package maintainers to fix it. :)
</p
>
7107 <p
>Running scripts in parallel could be the default in Debian when we
7108 manage to get the init.d script dependencies complete and correct. I
7109 expect we will get there in Squeeze+
1, if we get manage to test and
7110 fix the remaining issues.
</p
>
7112 <p
>If you report any problems with dependencies in init.d scripts to
7113 the BTS, please usertag the report to get it to show up at
7114 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7115 list of usertagged bugs related to this
</a
>.
</p
>
7120 <title>Debian has switched to dependency based boot sequencing
</title>
7121 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
7122 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
7123 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
7124 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
7125 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
7126 have been migrated to using dependency based boot sequencing. This
7127 conclude work me and others have been doing for the last three days.
7128 It feels great to see this finally part of the default Debian
7129 installation. Now we just need to weed out the last few problems that
7130 are bound to show up, to get everything ready for Squeeze.
</p
>
7132 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
7133 fixing the more fundamental problem of handing the event based
7134 non-predictable kernel in the early boot.
</p
>
7139 <title>Taking over sysvinit development
</title>
7140 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
7141 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
7142 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
7143 <description><p
>After several years of frustration with the lack of activity from
7144 the existing sysvinit upstream developer, I decided a few weeks ago to
7145 take over the package and become the new upstream. The number of
7146 patches to track for the Debian package was becoming a burden, and the
7147 lack of synchronization between the distribution made it hard to keep
7148 the package up to date.
</p
>
7150 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7151 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
7152 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
7153 and Fedora), based on the patches currently in use in these
7154 distributions. We Debian maintainers plan to move to this tarball as
7155 the new upstream as soon as we find time to do the merge. Since the
7156 new tarball was created, we agreed with Werner at SuSe to make a new
7157 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
7158 development there. The project is registered and currently waiting
7159 for approval by the Savannah administrators, and as soon as it is
7160 approved, we will import the old versions from svn and continue
7161 working on the future release.
</p
>
7163 <p
>It is a bit ironic that this is done now, when some of the involved
7164 distributions are moving to upstart as a syvinit replacement.
</p
>
7169 <title>Debian boots quicker and quicker
</title>
7170 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
7171 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
7172 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
7173 <description><p
>I spent Monday and tuesday this week in London with a lot of the
7174 people involved in the boot system on Debian and Ubuntu, to see if we
7175 could find more ways to speed up the boot system. This was an Ubuntu
7177 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
7178 gathering
</a
>. It was quite productive. We also discussed the future
7179 of boot systems, and ways to handle the increasing number of boot
7180 issues introduced by the Linux kernel becoming more and more
7181 asynchronous and event base. The Ubuntu approach using udev and
7182 upstart might be a good way forward. Time will show.
</p
>
7184 <p
>Anyway, there are a few ways at the moment to speed up the boot
7185 process in Debian. All of these should be applied to get a quick
7190 <li
>Use dash as /bin/sh.
</li
>
7192 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
7193 clock is in UTC.
</li
>
7195 <li
>Install and activate the insserv package to enable
7196 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
7197 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
7201 These points are based on the Google summer of code work done by
7202 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
7205 <p
>Support for makefile-style concurrency during boot was uploaded to
7206 unstable yesterday. When we tested it, we were able to cut
6 seconds
7207 from the boot sequence. It depend on very correct dependency
7208 declaration in all init.d scripts, so I expect us to find edge cases
7209 where the dependences in some scripts are slightly wrong when we start
7210 using this.
</p
>
7212 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7213 introduced by Raphael Geissert today, one that could affect the
7214 startup speed as well. Instead of starting some scripts concurrently
7215 from rcS.d/ and another set of scripts from rc2.d/, it would be
7216 possible to run a of them in the same process. A quick way to test
7217 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
7218 insserv
'. Will need to test if that work. :)
</p
>
7223 <title>BSAs påstander om piratkopiering møter motstand
</title>
7224 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
7225 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
7226 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
7227 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
7228 programvareselskapene som Microsoft og Apple, publisert en rapport der
7229 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7230 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7232 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
7233 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
7234 dagene. Et spesielt interessant kommentar fra Sverige,
7235 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
7236 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
7239 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
7240 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7241 företag.
"Man bör nog kanske inte se de här siffrorna som helt
7242 exakta
", säger BSAs Sverigechef John Hugosson.
7245 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
7246 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
7247 piracy figures need a shot of reality
</a
> og
<a
7248 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
7249 Copyright Treaty Work?
</a
></p
>
7251 <p
>Fant lenkene via
<a
7252 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
7253 på Slashdot
</a
>.
</p
>
7258 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
7259 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
7260 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
7261 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
7262 <description><p
>Kom over
7263 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
7264 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7265 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7266 jobber til daglig. En rask opptelling forteller meg at vi har
490
7267 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
7268 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
7269 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
7274 <title>Kryptert harddisk - naturligvis
</title>
7275 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
7276 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
7277 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
7278 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
7279 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
7280 når en tar tap av arbeidstid, fortrolige dokumenter,
7281 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7282 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7283 til at jeg har kryptert harddisken på både kontormaskinen og min
7284 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7285 komme på avveie, den første informasjon relatert til jobben min ved
7286 Universitetet i Oslo, og den andre relatert til blant annet
7287 foreningsarbeide. Kryptering av diskene gjør at det er lite
7288 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7289 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7290 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7291 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7292 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7293 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7294 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7295 det er gjort slik jeg gjør det er minimale, og gevinstene er
7296 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7297 maskinen reinstalleres og alt er tapt.
</p
>
7299 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7300 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7301 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7302 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7303 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7304 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7305 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7306 betydelige.
</p
>
7311 <title>Two projects that have improved the quality of free software a lot
</title>
7312 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
7313 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
7314 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
7315 <description><p
>There are two software projects that have had huge influence on the
7316 quality of free software, and I wanted to mention both in case someone
7317 do not yet know them.
</p
>
7319 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
7320 tool to detect and expose errors in the memory handling of programs.
7321 It is easy to use, all one need to do is to run
'valgrind program
',
7322 and it will report any problems on stdout. It is even better if the
7323 program include debug information. With debug information, it is able
7324 to report the source file name and line number where the problem
7325 occurs. It can report things like
'reading past memory block in file
7326 X line N, the memory block was allocated in file Y, line M
', and
7327 'using uninitialised value in control logic
'. This tool has made it
7328 trivial to investigate reproducible crash bugs in programs, and have
7329 reduced the number of this kind of bugs in free software a lot.
7331 <p
>The second one is
7332 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
7333 a source code checker. It is able to process the source of a program
7334 and find problems in the logic without running the program. It
7335 started out as the Stanford Checker and became well known when it was
7336 used to find bugs in the Linux kernel. It is now a commercial tool
7337 and the company behind it is running
7338 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
7339 free software community, where a lot of free software projects get
7340 their source checked for free. Several thousand defects have been
7341 found and fixed so far. It can find errors like
'lock L taken in file
7342 X line N is never released if exiting in line M
', or
'the code in file
7343 Y lines O to P can never be executed
'. The projects included in the
7344 community service project have managed to get rid of a lot of
7345 reliability problems thanks to Coverity.
</p
>
7347 <p
>I believe tools like this, that are able to automatically find
7348 errors in the source, are vital to improve the quality of software and
7349 make sure we can get rid of the crashing and failing software we are
7350 surrounded by today.
</p
>
7355 <title>No patch is not better than a useless patch
</title>
7356 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
7357 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
7358 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
7359 <description><p
>Julien Blache
7360 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
7361 patch is better than a useless patch
</a
>. I completely disagree, as a
7362 patch allow one to discuss a concrete and proposed solution, and also
7363 prove that the issue at hand is important enough for someone to spent
7364 time on fixing it. No patch do not provide any of these positive
7365 properties.
</p
>
7370 <title>Standardize on protocols and formats, not vendors and applications
</title>
7371 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
7372 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
7373 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
7374 <description><p
>Where I work at the University of Oslo, one decision stand out as a
7375 very good one to form a long lived computer infrastructure. It is the
7376 simple one, lost by many in todays computer industry: Standardize on
7377 open network protocols and open exchange/storage formats, not applications.
7378 Applications come and go, while protocols and files tend to stay, and
7379 thus one want to make it easy to change application and vendor, while
7380 avoiding conversion costs and locking users to a specific platform or
7381 application.
</p
>
7383 <p
>This approach make it possible to replace the client applications
7384 independently of the server applications. One can even allow users to
7385 use several different applications as long as they handle the selected
7386 protocol and format. In the normal case, only one client application
7387 is recommended and users only get help if they choose to use this
7388 application, but those that want to deviate from the easy path are not
7389 blocked from doing so.
</p
>
7391 <p
>It also allow us to replace the server side without forcing the
7392 users to replace their applications, and thus allow us to select the
7393 best server implementation at any moment, when scale and resouce
7394 requirements change.
</p
>
7396 <p
>I strongly recommend standardizing - on open network protocols and
7397 open formats, but I would never recommend standardizing on a single
7398 application that do not use open network protocol or open formats.
</p
>
7403 <title>Returning from Skolelinux developer gathering
</title>
7404 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
7405 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
7406 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
7407 <description><p
>I
'm sitting on the train going home from this weekends Debian
7408 Edu/Skolelinux development gathering. I got a bit done tuning the
7409 desktop, and looked into the dynamic service location protocol
7410 implementation avahi. It look like it could be useful for us. Almost
7411 30 people participated, and I believe it was a great environment to
7412 get to know the Skolelinux system. Walter Bender, involved in the
7413 development of the Sugar educational platform, presented his stuff and
7414 also helped me improve my OLPC installation. He also showed me that
7415 his Turtle Art application can be used in standalone mode, and we
7416 agreed that I would help getting it packaged for Debian. As a
7417 standalone application it would be great for Debian Edu. We also
7418 tried to get the video conferencing working with two OLPCs, but that
7419 proved to be too hard for us. The application seem to need more work
7420 before it is ready for me. I look forward to getting home and relax
7426 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
7427 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
7428 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
7429 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
7430 <description><p
>The state of standardized LDAP schemas on Linux is far from
7431 optimal. There is RFC
2307 documenting one way to store NIS maps in
7432 LDAP, and a modified version of this normally called RFC
2307bis, with
7433 some modifications to be compatible with Active Directory. The RFC
7434 specification handle the content of a lot of system databases, but do
7435 not handle DNS zones and DHCP configuration.
</p
>
7437 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
7438 we would like to store information about users, SMB clients/hosts,
7439 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7440 and LTSP configuration in LDAP. These objects have a lot in common,
7441 but with the current LDAP schemas it is not possible to have one
7442 object per entity. For example, one need to have at least three LDAP
7443 objects for a given computer, one with the SMB related stuff, one with
7444 DNS information and another with DHCP information. The schemas
7445 provided for DNS and DHCP are impossible to combine into one LDAP
7446 object. In addition, it is impossible to implement quick queries for
7447 netgroup membership, because of the way NIS triples are implemented.
7448 It just do not scale. I believe it is time for a few RFC
7449 specifications to cleam up this mess.
</p
>
7451 <p
>I would like to have one LDAP object representing each computer in
7452 the network, and this object can then keep the SMB (ie host key), DHCP
7453 (mac address/name) and DNS (name/IP address) settings in one place.
7454 It need to be efficently stored to make sure it scale well.
</p
>
7456 <p
>I would also like to have a quick way to map from a user or
7457 computer and to the net group this user or computer is a member.
</p
>
7459 <p
>Active Directory have done a better job than unix heads like myself
7460 in this regard, and the unix side need to catch up. Time to start a
7461 new IETF work group?
</p
>
7466 <title>Endelig er Debian Lenny gitt ut
</title>
7467 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
7468 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
7469 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
7470 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
7471 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
7472 Et langt steg videre for Debian-prosjektet, og en rekke nye
7473 programpakker blir nå tilgjengelig for de av oss som bruker den
7474 stabile utgaven av Debian. Neste steg er nå å få
7475 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
7476 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
7477 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7478 slippes løs på skolene. Takk til alle debian-utviklerne som har
7479 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7480 bootsekvens tilgjengelig i stabil utgave, vha pakken
7481 <tt
>insserv
</tt
>.
</p
>
7486 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
7487 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
7488 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
7489 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
7490 <description><p
>This weekend we had a small developer gathering for Debian Edu in
7491 Oslo. Most of Saturday was used for the general assemly for the
7492 member organization, but the rest of the weekend I used to tune the
7493 LTSP installation. LTSP now work out of the box on the
10-network.
7494 Acer Aspire One proved to be a very nice thin client, with both
7495 screen, mouse and keybard in a small box. Was working on getting the
7496 diskless workstation setup configured out of the box, but did not
7497 finish it before the weekend was up.
</p
>
7499 <p
>Did not find time to look at the
4 VGA cards in one box we got from
7500 the Brazilian group, so that will have to wait for the next
7501 development gathering. Would love to have the Debian Edu installer
7502 automatically detect and configure a multiseat setup when it find one
7503 of these cards.
</p
>
7508 <title>The sorry state of multimedia browser plugins in Debian
</title>
7509 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
7510 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
7511 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
7512 <description><p
>Recently I have spent some time evaluating the multimedia browser
7513 plugins available in Debian Lenny, to see which one we should use by
7514 default in Debian Edu. We need an embedded video playing plugin with
7515 control buttons to pause or stop the video, and capable of streaming
7516 all the multimedia content available on the web. The test results and
7517 notes are available on
7518 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
7519 Debian wiki
</a
>. I was surprised how few of the plugins are able to
7520 fill this need. My personal video player favorite, VLC, has a really
7521 bad plugin which fail on a lot of the test pages. A lot of the MIME
7522 types I would expect to work with any free software player (like
7523 video/ogg), just do not work. And simple formats like the
7524 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
7525 totem and vlc plugins. I hope the situation will improve soon. No
7526 wonder sites use the proprietary Adobe flash to play video.
</p
>
7528 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
7529 be the only one fitting our needs. :/
</p
>