]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
6f3b26ff24b72e9f3888157931f45ea7d63080f7
[homepage.git] / blog / tags / debian / debian.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
3 <channel>
4 <title>Petter Reinholdtsen - Entries tagged debian</title>
5 <description>Entries tagged debian</description>
6 <link>http://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>New chrpath release 0.16</title>
11 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
13 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
14 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
15 find problems in C, C++ and Java code using static source code
16 analysis. It can detect a lot of different problems, and is very
17 useful to find memory and locking bugs in the error handling part of
18 the source. The company behind it provide
19 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
20 a community service&lt;/a&gt;, and many hundred free software projects are
21 already checked. A few days ago I decided to have a closer look at
22 the Coverity system, and discovered that the
23 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
24 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
25 projects I am involved with was already registered. But these are
26 fairly big, and I would also like to have a small and easy project to
27 check, and decided to &lt;ahref=&quot;scan.coverity.com/projects/1179&quot;&gt;request
28 checking of the chrpath project&lt;/a&gt;. It was
29 added to the checker and discovered seven potential defects. Six of
30 these were real, mostly resource &quot;leak&quot; when the program detected an
31 error. Nothing serious, as the resources would be released a fraction
32 of a second later when the program exited because of the error, but it
33 is nice to do it right in case the source of the program some time in
34 the future end up in a library. Having fixed all defects and added
35 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
36 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
37 publish a new release. These are the release notes:&lt;/p&gt;
38
39 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
40
41 &lt;ul&gt;
42
43 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
44 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
45 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
46
47 &lt;/ul&gt;
48
49 &lt;p&gt;You can
50 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
51 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
52 project if something is wrong with the new release. The test suite
53 did not discover any old errors, so if you find a new one, please also
54 include a test suite check.&lt;/p&gt;
55 </description>
56 </item>
57
58 <item>
59 <title>New chrpath release 0.15</title>
60 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
61 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
62 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
63 <description>&lt;p&gt;After many years break from the package and a vain hope that
64 development would be continued by someone else, I finally pulled my
65 acts together this morning and wrapped up a new release of chrpath,
66 the command line tool to modify the rpath and runpath of already
67 compiled ELF programs. The update was triggered by the persistence of
68 Isha Vishnoi at IBM, which needed a new config.guess file to get
69 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
70 is working on. I checked the
71 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
72 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
73 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
74 packages for interesting patches (failed to find the source from
75 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
76 These are the release notes:&lt;/p&gt;
77
78 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
79
80 &lt;ul&gt;
81
82 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
83 with newer architectures. Thanks to isha vishnoi for the heads
84 up.&lt;/li&gt;
85
86 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
87
88 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
89 Matthias Klose.&lt;/li&gt;
90
91 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
92 Petr Machata found in Fedora.&lt;/li&gt;
93
94 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
95 .dynamic is a NULL terminated string. Based on patch found in
96 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
97
98 &lt;/ul&gt;
99
100 &lt;p&gt;You can
101 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
102 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
103 project if something is wrong with the new release. The test suite
104 did not discover any old errors, so if you find a new one, please also
105 include a testsuite check.&lt;/p&gt;
106 </description>
107 </item>
108
109 <item>
110 <title>Debian init.d boot script example for rsyslog</title>
111 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
112 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
113 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
114 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
115 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
116 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
117 init.d scripts at all. Here is an example init.d script, ie a rewrite
118 of /etc/init.d/rsyslog:&lt;/p&gt;
119
120 &lt;p&gt;&lt;pre&gt;
121 #!/lib/init/init-d-script
122 ### BEGIN INIT INFO
123 # Provides: rsyslog
124 # Required-Start: $remote_fs $time
125 # Required-Stop: umountnfs $time
126 # X-Stop-After: sendsigs
127 # Default-Start: 2 3 4 5
128 # Default-Stop: 0 1 6
129 # Short-Description: enhanced syslogd
130 # Description: Rsyslog is an enhanced multi-threaded syslogd.
131 # It is quite compatible to stock sysklogd and can be
132 # used as a drop-in replacement.
133 ### END INIT INFO
134 DESC=&quot;enhanced syslogd&quot;
135 DAEMON=/usr/sbin/rsyslogd
136 &lt;/pre&gt;&lt;/p&gt;
137
138 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
139 script was 137 lines, and the above is just 15 lines, most of it meta
140 info/comments.&lt;/p&gt;
141
142 &lt;p&gt;How to do this, you ask? Well, one create a new script
143 /lib/init/init-d-script looking something like this:
144
145 &lt;p&gt;&lt;pre&gt;
146 #!/bin/sh
147
148 # Define LSB log_* functions.
149 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
150 # and status_of_proc is working.
151 . /lib/lsb/init-functions
152
153 #
154 # Function that starts the daemon/service
155
156 #
157 do_start()
158 {
159 # Return
160 # 0 if daemon has been started
161 # 1 if daemon was already running
162 # 2 if daemon could not be started
163 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
164 || return 1
165 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
166 $DAEMON_ARGS \
167 || return 2
168 # Add code here, if necessary, that waits for the process to be ready
169 # to handle requests from services started subsequently which depend
170 # on this one. As a last resort, sleep for some time.
171 }
172
173 #
174 # Function that stops the daemon/service
175 #
176 do_stop()
177 {
178 # Return
179 # 0 if daemon has been stopped
180 # 1 if daemon was already stopped
181 # 2 if daemon could not be stopped
182 # other if a failure occurred
183 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
184 RETVAL=&quot;$?&quot;
185 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
186 # Wait for children to finish too if this is a daemon that forks
187 # and if the daemon is only ever run from this initscript.
188 # If the above conditions are not satisfied then add some other code
189 # that waits for the process to drop all resources that could be
190 # needed by services started subsequently. A last resort is to
191 # sleep for some time.
192 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
193 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
194 # Many daemons don&#39;t delete their pidfiles when they exit.
195 rm -f $PIDFILE
196 return &quot;$RETVAL&quot;
197 }
198
199 #
200 # Function that sends a SIGHUP to the daemon/service
201 #
202 do_reload() {
203 #
204 # If the daemon can reload its configuration without
205 # restarting (for example, when it is sent a SIGHUP),
206 # then implement that here.
207 #
208 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
209 return 0
210 }
211
212 SCRIPTNAME=$1
213 scriptbasename=&quot;$(basename $1)&quot;
214 echo &quot;SN: $scriptbasename&quot;
215 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
216 script=&quot;$1&quot;
217 shift
218 . $script
219 else
220 exit 0
221 fi
222
223 NAME=$(basename $DAEMON)
224 PIDFILE=/var/run/$NAME.pid
225
226 # Exit if the package is not installed
227 #[ -x &quot;$DAEMON&quot; ] || exit 0
228
229 # Read configuration variable file if it is present
230 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
231
232 # Load the VERBOSE setting and other rcS variables
233 . /lib/init/vars.sh
234
235 case &quot;$1&quot; in
236 start)
237 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
238 do_start
239 case &quot;$?&quot; in
240 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
241 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
242 esac
243 ;;
244 stop)
245 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
246 do_stop
247 case &quot;$?&quot; in
248 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
249 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
250 esac
251 ;;
252 status)
253 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
254 ;;
255 #reload|force-reload)
256 #
257 # If do_reload() is not implemented then leave this commented out
258 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
259 #
260 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
261 #do_reload
262 #log_end_msg $?
263 #;;
264 restart|force-reload)
265 #
266 # If the &quot;reload&quot; option is implemented then remove the
267 # &#39;force-reload&#39; alias
268 #
269 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
270 do_stop
271 case &quot;$?&quot; in
272 0|1)
273 do_start
274 case &quot;$?&quot; in
275 0) log_end_msg 0 ;;
276 1) log_end_msg 1 ;; # Old process is still running
277 *) log_end_msg 1 ;; # Failed to start
278 esac
279 ;;
280 *)
281 # Failed to stop
282 log_end_msg 1
283 ;;
284 esac
285 ;;
286 *)
287 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
288 exit 3
289 ;;
290 esac
291
292 :
293 &lt;/pre&gt;&lt;/p&gt;
294
295 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
296 lot. I did not really polish the approach, so it might not always
297 work out of the box, but you get the idea. I did not try very hard to
298 optimize it nor make it more robust either.&lt;/p&gt;
299
300 &lt;p&gt;A better argument for switching init system in Debian than reducing
301 the size of init scripts (which is a good thing to do anyway), is to
302 get boot system that is able to handle the kernel events sensibly and
303 robustly, and do not depend on the boot to run sequentially. The boot
304 and the kernel have not behaved sequentially in years.&lt;/p&gt;
305 </description>
306 </item>
307
308 <item>
309 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
310 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
311 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
312 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
313 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
314 remote display access is the preferred solution with oVirt and RedHat
315 Enterprise Virtualization, and I was sad to discover the other day
316 that the browser plugin needed to use these systems seamlessly was
317 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
318 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
319 2013-04-01, so I decided to wrap up a package based on the great work
320 from Cajus Pollmeier and put it in a collab-maint maintained git
321 repository to get a package I could use. I would very much like
322 others to help me maintain the package (or just take over, I do not
323 mind), but as no-one had volunteered so far, I just uploaded it to
324 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
325
326 &lt;p&gt;The source is now available from
327 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary&quot;&gt;http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary&lt;/a&gt;.&lt;/p&gt;
328 </description>
329 </item>
330
331 <item>
332 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
333 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
334 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
335 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
336 <description>&lt;p&gt;The
337 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
338 program is a a very nice system to create virtual machine images. It
339 create a image file, add a partition table, mount it and run
340 debootstrap in the mounted directory to create a Debian system on a
341 stick. Yesterday, I decided to try to teach it how to make images for
342 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
343 of a plan to simplify the build system for
344 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
345 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
346 the virtualbox images, but its current build system made multistrap
347 based system for Dreamplug images, and it is lacking support for
348 Raspberry Pi.&lt;/p&gt;
349
350 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
351 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
352 code and adjusted it to be able to build armel images on my amd64
353 Debian laptop. I ended up giving vmdebootstrap five new options,
354 allowing me to replicate the image creation process I use to make
355 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
356 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
357 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
358 call debootstrap with --foreign and to copy the handler into the
359 generated chroot before running the second stage. This allow
360 vmdebootstrap to create armel images on an amd64 host. Next I added
361 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
362 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
363 given file system type, allowing me to create an image with a vfat
364 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
365 variant&lt;/tt&gt; option to allow me to create smaller images without the
366 Debian base system packages installed. Finally, I added an option
367 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
368 as a boot loader. It is not needed on the Raspberry Pi and probably
369 most other non-x86 architectures. The changes were accepted by the
370 upstream author of vmdebootstrap yesterday and today, and is now
371 available from
372 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
373 upstream project page&lt;/a&gt;.&lt;/p&gt;
374
375 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
376 create a small script (the customize script) to add the non-free
377 binary blob needed to boot the Raspberry Pi and the APT source
378 list:&lt;/p&gt;
379
380 &lt;p&gt;&lt;pre&gt;
381 #!/bin/sh
382 set -e # Exit on first error
383 rootdir=&quot;$1&quot;
384 cd &quot;$rootdir&quot;
385 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
386 deb http://http.debian.net/debian/ jessie main contrib non-free
387 EOF
388 # Install non-free binary blob needed to boot Raspberry Pi. This
389 # install a kernel somewhere too.
390 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
391 -O $rootdir/usr/bin/rpi-update
392 chmod a+x $rootdir/usr/bin/rpi-update
393 mkdir -p $rootdir/lib/modules
394 touch $rootdir/boot/start.elf
395 chroot $rootdir rpi-update
396 &lt;/pre&gt;&lt;/p&gt;
397
398 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
399 to build the image:&lt;/p&gt;
400
401 &lt;pre&gt;
402 sudo ./vmdebootstrap \
403 --variant minbase \
404 --arch armel \
405 --distribution jessie \
406 --mirror http://http.debian.net/debian \
407 --image test.img \
408 --size 600M \
409 --bootsize 64M \
410 --boottype vfat \
411 --log-level debug \
412 --verbose \
413 --no-kernel \
414 --no-extlinux \
415 --root-password raspberry \
416 --hostname raspberrypi \
417 --foreign /usr/bin/qemu-arm-static \
418 --customize `pwd`/customize \
419 --package netbase \
420 --package git-core \
421 --package binutils \
422 --package ca-certificates \
423 --package wget \
424 --package kmod
425 &lt;/pre&gt;&lt;/p&gt;
426
427 &lt;p&gt;The list of packages being installed are the ones needed by
428 rpi-update to make the image bootable on the Raspberry Pi, with the
429 exception of netbase, which is needed by debootstrap to find
430 /etc/hosts with the minbase variant. I really wish there was a way to
431 set up an Raspberry Pi using only packages in the Debian archive, but
432 that is not possible as far as I know, because it boots from the GPU
433 using a non-free binary blob.&lt;/p&gt;
434
435 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
436 probably a few others installed. I have not checked the complete
437 build dependency list.&lt;/p&gt;
438
439 &lt;p&gt;The resulting image will not use the hardware floating point unit
440 on the Raspberry PI, because the armel architecture in Debian is not
441 optimized for that use. So the images created will be a bit slower
442 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
443 </description>
444 </item>
445
446 <item>
447 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
448 <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>
449 <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>
450 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
451 <description>&lt;p&gt;The last few days I came across a few good causes that should get
452 wider attention. I recommend signing and donating to each one of
453 these. :)&lt;/p&gt;
454
455 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
456 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
457 Women program which is a Google Summer of Code like initiative to get
458 more women involved in free software. One debian sponsor has offered
459 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
460 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
461 hope you will to. :)&lt;/p&gt;
462
463 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
464 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
465 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
466 take place these days, and their need to fund the work. I&#39;ve already
467 donated. Are you next?&lt;/p&gt;
468
469 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
470 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
471 statement under the heading
472 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
473 Access&lt;/a&gt; for those of us asking for more focus on open access in the
474 Norwegian government. So far 499 signatures. I hope you will sign it
475 too.&lt;/p&gt;
476 </description>
477 </item>
478
479 <item>
480 <title>Videos about the Freedombox project - for inspiration and learning</title>
481 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
482 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
483 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
484 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
485 project&lt;/a&gt; have been going on for a while, and have presented the
486 vision, ideas and solution several places. Here is a little
487 collection of videos of talks and presentation of the project.&lt;/p&gt;
488
489 &lt;ul&gt;
490
491 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
492 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
493
494 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
495 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
496
497 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
498 Freedom in the Cloud - Software Freedom, Privacy and and Security for
499 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
500 (Youtube)&lt;/li&gt;
501
502 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
503 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
504
505 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
506 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
507
508 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
509 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
510 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
511
512 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
513 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
514 (Youtube)&lt;/li&gt;
515
516 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
517 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
518
519 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
520 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
521
522 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
523 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
524 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
525
526 &lt;/ul&gt;
527
528 &lt;p&gt;A larger list is available from
529 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
530 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
531
532 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
533 Jessie is coming along quite well, and soon both Owncloud and using
534 Tor should be available for testers of the Freedombox solution. :) In
535 a few weeks I hope everything needed to test it is included in Debian.
536 The withsqlite package is already in Debian, and the plinth package is
537 pending in NEW. The third and vital part of that puzzle is the
538 metapackage/setup framework, which is still pending an upload. Join
539 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
540 (#freedombox on irc.debian.org)&lt;/a&gt; and
541 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
542 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
543 </description>
544 </item>
545
546 <item>
547 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
548 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
549 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
550 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
551 <description>&lt;p&gt;I was introduced to the
552 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
553 in 2010, when Eben Moglen presented his vision about serving the need
554 of non-technical people to keep their personal information private and
555 within the legal protection of their own homes. The idea is to give
556 people back the power over their network and machines, and return
557 Internet back to its intended peer-to-peer architecture. Instead of
558 depending on a central service, the Freedombox will give everyone
559 control over their own basic infrastructure.&lt;/p&gt;
560
561 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
562 taken priority. But this summers nasty news about the misuse of trust
563 and privilege exercised by the &quot;western&quot; intelligence gathering
564 communities increased my eagerness to contribute to a point where I
565 actually started working on the project a while back.&lt;/p&gt;
566
567 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
568 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
569 create a simple and cheap Debian based appliance that anyone can hook
570 up in their home and get access to secure and private services and
571 communication. The initial deployment platform have been the
572 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
573 which is a piece of hardware I do not own. So to be able to test what
574 the current Freedombox setup look like, I had to come up with a way to install
575 it on some hardware I do have access to. I have rewritten the
576 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
577 image build framework to use .deb packages instead of only copying
578 setup into the boot images, and thanks to this rewrite I am able to
579 set up any machine supported by Debian Wheezy as a Freedombox, using
580 the previously mentioned deb (and a few support debs for packages
581 missing in Debian).&lt;/p&gt;
582
583 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
584 scripts
585 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
586 and a administrative web interface
587 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
588 withsqlite), as well as a privacy enhancing proxy based on
589 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
590 (freedombox-privoxy). There is also a web/javascript based XMPP
591 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
592 trying (unsuccessfully so far) to talk to the XMPP server
593 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
594 web interface is pluggable, and the goal is to use it to enable OpenID
595 services, mesh network connectivity, use of TOR, etc, etc. Not much of
596 this is really working yet, see
597 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
598 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
599 on github at the moment. The HTTP proxy is operational out of the
600 box, and the admin web interface can be used to add/remove plinth
601 users. I&#39;ve not been able to do anything else with it so far, but
602 know there are several branches spread around github and other places
603 with lots of half baked features.&lt;/p&gt;
604
605 &lt;p&gt;Anyway, if you want to have a look at the current state, the
606 following recipes should work to give you a test machine to poke
607 at.&lt;/p&gt;
608
609 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
610
611 &lt;ol&gt;
612
613 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
614 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
615 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
616 to the Debian installer:&lt;p&gt;
617 &lt;pre&gt;url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat&lt;/a&gt;&lt;/pre&gt;&lt;/li&gt;
618
619 &lt;li&gt;Answer the few language/region/password questions and pick disk to
620 install on.&lt;/li&gt;
621
622 &lt;li&gt;When the installation is finished and the machine have rebooted a
623 few times, your Freedombox is ready for testing.&lt;/li&gt;
624
625 &lt;/ol&gt;
626
627 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
628
629 &lt;ol&gt;
630
631 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
632 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
633 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
634 &lt;pre&gt;
635 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
636 &lt;/pre&gt;&lt;/li&gt;
637 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
638 &lt;pre&gt;
639 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
640 apt-key add -
641 apt-get update
642 apt-get install freedombox-setup
643 /usr/lib/freedombox/setup
644 &lt;/pre&gt;&lt;/li&gt;
645 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
646
647 &lt;/ol&gt;
648
649 &lt;p&gt;You can test it on other architectures too, but because the
650 freedombox-privoxy package is binary, it will only work as intended on
651 the architectures where I have had time to build the binary and put it
652 in my APT repository. But do not let this stop you. It is only a
653 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
654
655 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
656 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
657 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
658 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
659
660 &lt;p&gt;Please let me know if this works for you, or if you have any
661 problems. We gather on the IRC channel
662 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
663 irc.debian.org and the
664 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
665 mailing list&lt;/a&gt;.&lt;/p&gt;
666
667 &lt;p&gt;Once you get your freedombox operational, you can visit
668 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
669 welcome screen (dead end - do not be surprised if you are unable to
670 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
671 to look at the rest of plinth. The default user is &#39;admin&#39; and the
672 default password is &#39;secret&#39;.&lt;/p&gt;
673 </description>
674 </item>
675
676 <item>
677 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
678 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
679 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
680 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
681 <description>&lt;p&gt;Earlier, I reported about
682 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html&quot;&gt;my
683 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
684 told by IBM that the original disk should be thrown away. And as
685 there no longer was a problem if I bricked the firmware, I decided
686 today to try to install Intel firmware to replace the Lenovo firmware
687 currently on the disk.&lt;/p&gt;
688
689 &lt;p&gt;I searched the Intel site for firmware, and found
690 &lt;a href=&quot;https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&amp;ProdId=3472&amp;DwnldID=18363&amp;ProductFamily=Solid-State+Drives+and+Caching&amp;ProductLine=Intel%c2%ae+High+Performance+Solid-State+Drive&amp;ProductProduct=Intel%c2%ae+SSD+520+Series+(180GB%2c+2.5in+SATA+6Gb%2fs%2c+25nm%2c+MLC)&amp;lang=eng&quot;&gt;issdfut_2.0.4.iso&lt;/a&gt;
691 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
692 according to the site should contain the latest firmware for SSD
693 disks. I inserted the broken disk in one of my spare laptops and
694 booted the ISO from a USB stick. The disk was recognized, but the
695 program claimed the newest firmware already were installed and refused
696 to insert any Intel firmware. So no change, and the disk is still
697 unable to handle write load. :( I guess the only way to get them
698 working would be if Lenovo releases new firmware. No idea how likely
699 that is. Anyway, just blogging about this test for completeness. I
700 got a working Samsung disk, and see no point in spending more time on
701 the broken disks.&lt;/p&gt;
702 </description>
703 </item>
704
705 <item>
706 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
707 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
708 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
709 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
710 <description>&lt;p&gt;Today I switched to
711 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
712 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
713 my new Thinkpad X230, which was delivered with an
714 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html&quot;&gt;180
715 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
716 sustained writes. My hardware supplier have been very forthcoming in
717 trying to find a solution, and after first trying with another
718 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
719 disk instead to fix it once and for all. The Samsung disk survived
720 the installation of Debian with encrypted disks (filling the disk with
721 random data during installation killed the first two), and I thus
722 decided to trust it with my data. I have installed it as a Debian Edu
723 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
724 server at home using Kerberos and LDAP, and will use it as my work
725 station from now on.&lt;/p&gt;
726
727 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
728 Debian Wheezy default installation need to be tuned a bit to increase
729 performance and increase life time of the disk. The Linux kernel and
730 user space applications do not yet adjust automatically to such
731 environment. To make it easier for my self, I created a draft Debian
732 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
733 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
734 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
735 is set up to adjust the setup of the machine by just installing the
736 package. If there is any non-SSD disk in the machine, the package
737 will refuse to install, as I did not try to write any logic to sort
738 file systems in SSD and non-SSD file systems.&lt;/p&gt;
739
740 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
741 set up Debian Wheezy with an SSD. It is adjusted to my use case,
742 where I set up the machine with one large encrypted partition (in
743 addition to /boot), put LVM on top of this and set up partitions on
744 top of this again. See the README file in the package source for the
745 references I used to pick the settings. At the moment these
746 parameters are tuned:&lt;/p&gt;
747
748 &lt;ul&gt;
749
750 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
751 (adding discard to /etc/crypttab)&lt;/li&gt;
752
753 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
754 this case a cryptsetup partition) by changing issue_discards from
755 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
756
757 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
758 systems.&lt;/li&gt;
759
760 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
761 /etc/fstab.&lt;/li&gt;
762
763 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
764
765 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
766 cron.daily).&lt;/li&gt;
767
768 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
769 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
770
771 &lt;/ul&gt;
772
773 &lt;p&gt;During installation, I cancelled the part where the installer fill
774 the disk with random data, as this would kill the SSD performance for
775 little gain. My goal with the encrypted file system is to ensure
776 those stealing my laptop end up with a brick and not a working
777 computer. I have no hope in keeping the really resourceful people
778 from getting the data on the disk (see
779 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
780 Thus I concluded that adding the discard option to crypttab is the
781 right thing to do.&lt;/p&gt;
782
783 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
784 it for SSD, but others recommended deadline and a benchmark I found
785 indicated that deadline might be better for interactive use.&lt;/p&gt;
786
787 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
788 and ext4, but read that it would give a performance hit ever time a
789 file is removed, and thought it best to that that slowdown once a day
790 instead of during my work.&lt;/p&gt;
791
792 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
793 this is already done by Debian Edu.&lt;/p&gt;
794
795 &lt;p&gt;I have not yet started on the user space tuning. I expect
796 iceweasel need some tuning, and perhaps other applications too, but
797 have not yet had time to investigate those parts.&lt;/p&gt;
798
799 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
800 there.&lt;/p&gt;
801
802 &lt;p&gt;As for the answer to the question in the title of this blog post,
803 as far as I know, the only solution I know about is to replace the
804 disk. It might be possible to flash it with Intel firmware instead of
805 the Lenovo firmware. But I have not tried and did not want to do so
806 without approval from Lenovo as I wanted to keep the warranty on the
807 disk until a solution was found and they wanted the broken disks
808 back.&lt;/p&gt;
809 </description>
810 </item>
811
812 <item>
813 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
814 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
815 <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>
816 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
817 <description>&lt;p&gt;A few days ago, I wrote about
818 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
819 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
820 was dying during installation because it is unable to cope with
821 sustained write. My supplier is in contact with
822 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
823 replacement disk to try to fix the problem. They decided to send an
824 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
825
826 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
827 Debian Edu Wheezy with encrypted disk on it. The new disk have the
828 same firmware version as the original. This time my hope raised
829 slightly as the installation progressed, as the original disk used to
830 die after 4-7% of the disk was written to, while this time it kept
831 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
832 died again and I was back on square one. I still do not have a new
833 laptop with a disk I can trust. I can not live with a disk that might
834 lock up when I download a new
835 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
836 other large files. I look forward to hearing from my supplier with
837 the next proposal from Lenovo.&lt;/p&gt;
838
839 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
840 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
841 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
842 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
843 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
844 P/N 45N8295, P0C38732.&lt;/p&gt;
845
846 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
847 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
848 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
849 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
850 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
851 P/N 45N8295, P0C38732.&lt;/p&gt;
852
853 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
854 SA, date and WNPP values. Mentioning all the details here in case
855 someone is able to use the information to find a way to identify the
856 failing disk among working ones (if any such working disk actually
857 exist).&lt;/p&gt;
858 </description>
859 </item>
860
861 <item>
862 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
863 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
864 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
865 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
866 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
867 Debian Edu developer gathering and Debian and Ubuntu bug squashing
868 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
869 member assosiation NUUG&lt;/a&gt; and
870 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
871 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
872 Bitraf&lt;/a&gt;.&lt;/p&gt;
873
874 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
875 welcome, and there is no fee to participate. There is on the other
876 hand limited space, and only room for 30 people. Please put your name
877 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
878 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
879 </description>
880 </item>
881
882 <item>
883 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
884 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
885 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
886 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
887 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
888 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
889 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
890 time to spend on it, and it took a while to find a model I believe
891 will do the job, but two days ago the replacement finally arrived. I
892 ended up picking a
893 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
894 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
895 a roaming workstation, and it seemed to work flawlessly. But my
896 second installation with encrypted disk was not as successful. More
897 on that below.&lt;/p&gt;
898
899 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
900 important requirements (robust and with a good keyboard) are never
901 listed in the feature list. But I did get good help from the search
902 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
903 allowed me to limit the list of interesting laptops based on my other
904 requirements. A bit surprising that SSD disk are not disks according
905 to that search interface, so I had to drop specifying the number of
906 disks from my search parameters. I also asked around among friends to
907 get their impression on keyboards and robustness.&lt;/p&gt;
908
909 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
910 X41. I am not quite convinced about the keyboard, as it is
911 significantly wider than my old keyboard, and I have to stretch my
912 hand a lot more to reach the edges. But the key response is fairly
913 good and the individual key shape is fairly easy to handle, so I hope
914 I will get used to it. My old X40 was starting to fail, and I really
915 needed a new laptop now. :)&lt;/p&gt;
916
917 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
918 visit to the BIOS during boot it disable it.&lt;/p&gt;
919
920 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
921 lock up during load. And this happen when installing Debian Wheezy
922 with encrypted disk, while the disk is being filled with random data.
923 I also tested to install Ubuntu Raring, and it happen there too if I
924 reenable the code to fill the disk with random data (it is disabled by
925 default in Ubuntu). And the bug with is already known. It was
926 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
927 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
928 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
929 kernel developers as
930 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
931 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
932 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
933 Lenovo forums, both for
934 &lt;a href=&quot;http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-520-180GB-issue/m-p/1070549&quot;&gt;T430
935 2012-11-10&lt;/a&gt; and for
936 &lt;a href=&quot;http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/x230-SATA-errors-with-180GB-Intel-520-SSD-under-heavy-write-load/m-p/1068147&quot;&gt;X230
937 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
938 reports state that the disk lock up during use if many writes are done
939 on the disk, so it is much no use to work around the installation
940 problem and end up with a computer that can lock up at any moment.
941 There is even a
942 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
943 available&lt;/a&gt; that will lock up the hard drive after running a few
944 minutes by writing to a file.&lt;/p&gt;
945
946 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
947 contacting PCHELP Norway (request 01D1FDP) which handle support
948 requests for Lenovo, his first suggestion was to upgrade the disk
949 firmware. Unfortunately there is no newer firmware available from
950 Lenovo, as my disk already have the most recent one (version LF1i). I
951 hope to hear more from him today and hope the problem can be
952 fixed. :)&lt;/p&gt;
953 </description>
954 </item>
955
956 <item>
957 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
958 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
959 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
960 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
961 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
962 trusty old Thinkpad X41. Unfortunately I did not have much time to
963 spend on it, but today the replacement finally arrived. I ended up
964 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
965 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
966 Wheezy as a roaming workstation, and it worked flawlessly. As I write
967 this, it is installing what I hope will be a more final installation,
968 with a encrypted hard drive to ensure any dope head stealing it end up
969 with an expencive door stop.&lt;/p&gt;
970
971 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
972 important requirements (robust and with a good keyboard) are never
973 listed in the feature list. But I did get good help from the search
974 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
975 allowed me to limit the list of interesting laptops based on my other
976 requirements. A bit surprising that SSD disk are not disks, so I had
977 to drop number of disks from my search parameters.&lt;/p&gt;
978
979 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
980 wider than my old keyboard, and I have to stretch my hand a lot more
981 to reach the edges. But the key response is fairly good and the
982 individual key shape is fairly easy to handle, so I hope I will get
983 used to it. My old X40 was starting to fail, and I really needed a
984 new laptop now. :)&lt;/p&gt;
985
986 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
987 </description>
988 </item>
989
990 <item>
991 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
992 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
993 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
994 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
995 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
996 perfectly capable of, and I have to do it manually to get things
997 working. One such task is to find out what firmware packages are
998 needed to get the hardware on my computer working. Most often this
999 affect the wifi card, but some times it even affect the RAID
1000 controller or the ethernet card. Today I pushed version 0.4 of the
1001 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
1002 including a new script isenkram-autoinstall-firmware handling the
1003 process of asking all the loaded kernel modules what firmware files
1004 they want, find debian packages providing these files and install the
1005 debian packages. Here is a test run on my laptop:&lt;/p&gt;
1006
1007 &lt;p&gt;&lt;pre&gt;
1008 # isenkram-autoinstall-firmware
1009 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
1010 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
1011 info: locating packages with the requested firmware files
1012 info: Updating APT sources after adding non-free APT source
1013 info: trying to install firmware-ipw2x00
1014 firmware-ipw2x00
1015 firmware-ipw2x00
1016 Preconfiguring packages ...
1017 Selecting previously deselected package firmware-ipw2x00.
1018 (Reading database ... 259727 files and directories currently installed.)
1019 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
1020 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
1021 #
1022 &lt;/pre&gt;&lt;/p&gt;
1023
1024 &lt;p&gt;When all the requested firmware is present, a simple message is
1025 printed instead:&lt;/p&gt;
1026
1027 &lt;p&gt;&lt;pre&gt;
1028 # isenkram-autoinstall-firmware
1029 info: did not find any firmware files requested by loaded kernel modules. exiting
1030 #
1031 &lt;/pre&gt;&lt;/p&gt;
1032
1033 &lt;p&gt;It could use some polish, but it is already working well and saving
1034 me some time when setting up new machines. :)&lt;/p&gt;
1035
1036 &lt;p&gt;So, how does it work? It look at the set of currently loaded
1037 kernel modules, and look up each one of them using modinfo, to find
1038 the firmware files listed in the module meta-information. Next, it
1039 download the Contents file from a nearby APT mirror, and search for
1040 the firmware files in this file to locate the package with the
1041 requested firmware file. If the package is in the non-free section, a
1042 non-free APT source is added and the package is installed using
1043 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
1044 machine.&lt;/p&gt;
1045
1046 &lt;p&gt;I hope someone find time to implement a more polished version of
1047 this script as part of the hw-detect debian-installer module, to
1048 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
1049 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
1050 firmware during a PXE install when the packages already are available
1051 from the nearby Debian mirror.&lt;/p&gt;
1052 </description>
1053 </item>
1054
1055 <item>
1056 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
1057 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
1058 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
1059 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
1060 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
1061 the screen just turn black when Linux boot, either during installation
1062 or on first boot from the hard disk. I&#39;ve seen it once in a while the
1063 last few years, but only recently understood the cause. I&#39;ve seen it
1064 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
1065 The reason seem to be in the wiring of some laptops. The system to
1066 control the screen background light is inverted, so when Linux try to
1067 turn the brightness fully on, it end up turning it off instead. I do
1068 not know which Linux drivers are affected, but this post is about the
1069 i915 driver used by the
1070 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
1071 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
1072
1073 &lt;p&gt;The problem can be worked around two ways. Either by adding
1074 i915.invert_brightness=1 as a kernel option, or by adding a file in
1075 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
1076 option when it load the i915 kernel module. On Debian and Ubuntu, it
1077 can be done by running these commands as root:&lt;/p&gt;
1078
1079 &lt;pre&gt;
1080 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
1081 update-initramfs -u -k all
1082 &lt;/pre&gt;
1083
1084 &lt;p&gt;Since March 2012 there is
1085 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
1086 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
1087 hardware have this problem, and get the driver to invert the
1088 brightness setting automatically. To use it, one need to add a row in
1089 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c&quot;&gt;the
1090 intel_quirks array&lt;/a&gt; in the driver source
1091 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
1092 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
1093 number (vendor number 8086 is assumed) and subdevice vendor and device
1094 number.&lt;/p&gt;
1095
1096 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
1097 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
1098
1099 &lt;p&gt;&lt;pre&gt;
1100 00:02.0 VGA compatible controller [0300]: Intel Corporation \
1101 3rd Gen Core processor Graphics Controller [8086:0156] \
1102 (rev 09) (prog-if 00 [VGA controller])
1103 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
1104 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
1105 ParErr- Stepping- SE RR- FastB2B- DisINTx+
1106 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
1107 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
1108 Latency: 0
1109 Interrupt: pin A routed to IRQ 42
1110 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
1111 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
1112 Region 4: I/O ports at 4000 [size=64]
1113 Expansion ROM at &lt;unassigned&gt; [disabled]
1114 Capabilities: &lt;access denied&gt;
1115 Kernel driver in use: i915
1116 &lt;/pre&gt;&lt;/p&gt;
1117
1118 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
1119
1120 &lt;p&gt;&lt;pre&gt;
1121 struct intel_quirk intel_quirks[] = {
1122 ...
1123 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
1124 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
1125 ...
1126 }
1127 &lt;/pre&gt;&lt;/p&gt;
1128
1129 &lt;p&gt;According to the kernel module instructions (as seen using
1130 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
1131 invert_brightness flag should be sent to the
1132 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
1133 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
1134 developers. But my email about the laptop sent 2013-06-03 have not
1135 yet shown up in
1136 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
1137 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
1138 emails from non-subscribers. Because of this, I sent my patch also to
1139 the Debian bug tracking system instead as
1140 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
1141 sure the patch is not lost.&lt;/p&gt;
1142
1143 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
1144 with this problem working properly with Linux. If you use Gnome, your
1145 worries should be over at this point. But if you use KDE, there is
1146 something in KDE ignoring the invert_brightness setting and turning on
1147 the screen during login. I&#39;ve reported it to Debian as
1148 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
1149 have no idea yet how to figure out exactly what subsystem is doing
1150 this. Perhaps you can help? Perhaps you know what the Gnome
1151 developers did to handle this, and this can give a clue to the KDE
1152 developers? Or you know where in KDE the screen brightness is changed
1153 during login? If so, please update the BTS report (or get in touch if
1154 you do not know how to update BTS).&lt;/p&gt;
1155
1156 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
1157 acpi_backlight=vendor, to disable ACPI backlight support completely,
1158 as the ACPI information on the machine is trash and it is better to
1159 leave it to the intel video driver to control the screen
1160 backlight.&lt;/p&gt;
1161 </description>
1162 </item>
1163
1164 <item>
1165 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
1166 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
1167 <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>
1168 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
1169 <description>&lt;p&gt;Two days ago, I asked
1170 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html&quot;&gt;how
1171 I could install Linux on a Packard Bell EasyNote LV computer
1172 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
1173 with the obstacles put in the way of Linux users on a laptop with UEFI
1174 and Windows 8.&lt;/p&gt;
1175
1176 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
1177 secure booting or fast boot. I suspect fast boot was the problem,
1178 causing the firmware to boot directly from HD without considering any
1179 key presses and alternative devices, but do not know UEFI settings
1180 enough to tell.&lt;/p&gt;
1181
1182 &lt;p&gt;There is no way to install Linux on the machine in question without
1183 opening the box and disconnecting the hard drive! This is as far as I
1184 can tell, the only way to get access to the firmware setup menu
1185 without accepting the Windows 8 license agreement. I am told (and
1186 found description on how to) that it is possible to configure the
1187 firmware setup once booted into Windows 8. But as I believe the terms
1188 of that agreement are completely unacceptable, accepting the license
1189 was never an alternative. I do not enter agreements I do not intend
1190 to follow.&lt;/p&gt;
1191
1192 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
1193 waste many hours on this, but luckily there was a way to get it to
1194 work. But I would not recommend it to anyone planning to run Linux on
1195 it, and I have become sceptical to Windows 8 certified laptops. Is
1196 this the way Linux will be forced out of the market place, by making
1197 it close to impossible for &quot;normal&quot; users to install Linux without
1198 accepting the Microsoft Windows license terms? Or at least not
1199 without risking to loose the warranty?&lt;/p&gt;
1200
1201 &lt;p&gt;I&#39;ve updated the
1202 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
1203 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
1204 do not have to struggle as much as I did to get Linux into the
1205 machine.&lt;/p&gt;
1206
1207 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
1208 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
1209 </description>
1210 </item>
1211
1212 <item>
1213 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
1214 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
1215 <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>
1216 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
1217 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
1218 new laptops for my parents and a few others. I bought Packard Bell
1219 Easynote LV to run Kubuntu on and use as their home computer. But I
1220 am completely unable to figure out how to install Linux on it. The
1221 computer is preinstalled with Windows 8, and I suspect it uses UEFI
1222 instead of a BIOS to boot.&lt;/p&gt;
1223
1224 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
1225 to get it to boot the Linux installer from my USB stick. I have yet
1226 to try the DVD install, and still hope it will work. when I turn on
1227 the computer, there is no information on what buttons to press to get
1228 the normal boot menu. I expect to get some boot menu to select PXE or
1229 USB stick booting. When booting, it first ask for the language to
1230 use, then for some regional settings, and finally if I will accept the
1231 Windows 8 terms of use. As these terms are completely unacceptable to
1232 me, I have no other choice but to turn off the computer and try again
1233 to get it to boot the Linux installer.&lt;/p&gt;
1234
1235 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
1236 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
1237 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
1238 installed on this machine, please get in touch or update that wiki
1239 page. If I can&#39;t find a way to install Linux, I will have to return
1240 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
1241
1242 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
1243 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
1244 on new Laptops?&lt;/p&gt;
1245 </description>
1246 </item>
1247
1248 <item>
1249 <title>How to transform a Debian based system to a Debian Edu installation</title>
1250 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
1251 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
1252 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
1253 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
1254 an operating system based on Debian intended for use in schools. It
1255 contain a turn-key solution for the computer network provided to
1256 pupils in the primary schools. It provide both the central server,
1257 network boot servers and desktop environments with heaps of
1258 educational software. The project was founded almost 12 years ago,
1259 2001-07-02. If you want to support the project, which is in need for
1260 cash to fund developer gatherings and other project related activity,
1261 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
1262 donate some money&lt;/a&gt;.
1263
1264 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
1265 lists and elsewhere, is the question on how to transform a Debian or
1266 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
1267 hard, and last week I wrote a script to replicate the steps done by
1268 the Debian Edu installer.&lt;/p&gt;
1269
1270 &lt;p&gt;The script,
1271 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/branches/wheezy/debian-edu-config/share/debian-edu-config/tools/debian-edu-bless?view=markup&quot;&gt;debian-edu-bless&lt;a/&gt;
1272 in the debian-edu-config package, will go through these six steps and
1273 transform an existing Debian Wheezy or Ubuntu (untested) installation
1274 into a Debian Edu Workstation:&lt;/p&gt;
1275
1276 &lt;ol&gt;
1277
1278 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
1279 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
1280 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
1281 our configuration.&lt;/li&gt;
1282 &lt;li&gt;Preseed debconf database with profile setup in
1283 /etc/debian-edu/config, and run tasksel to install packages
1284 according to the profile specified in the config above,
1285 overriding some of the Debian automation machinery.&lt;/li&gt;
1286 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
1287 that could not be done using preseeding.&lt;/li&gt;
1288 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
1289
1290 &lt;/ol&gt;
1291
1292 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
1293 replicated like this. Disk partitioning and LVM setup, for example.
1294 So this script just assume there is enough disk space to install all
1295 the needed packages.&lt;/p&gt;
1296
1297 &lt;p&gt;The script was created to help a Debian Edu student working on
1298 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
1299 Debian Edu client, and using it he can take the existing
1300 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
1301 transform it into a fully functioning Debian Edu Workstation (or
1302 Roaming Workstation, or whatever :).&lt;/p&gt;
1303
1304 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
1305 If a LXDE based Roaming workstation is wanted instead, modify the
1306 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
1307
1308 &lt;p&gt;&lt;pre&gt;
1309 PROFILE=&quot;Roaming-Workstation&quot;
1310 DESKTOP=&quot;lxde&quot;
1311 &lt;/pre&gt;&lt;/p&gt;
1312
1313 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
1314 the cloud, by starting with a virtual Debian installation at some
1315 virtual hosting service and setting up all the services on first
1316 boot.&lt;/p&gt;
1317 </description>
1318 </item>
1319
1320 <item>
1321 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
1322 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
1323 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
1324 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
1325 <description>&lt;P&gt;In January,
1326 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
1327 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
1328 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
1329 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
1330 marvellous construction system from Denmark. We also created
1331 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
1332 a place to take notes and write down our plans and hopes. And several
1333 people showed up to help. I was very happy to see the effect of my
1334 call. Since the small start, we have a debtags tag
1335 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
1336 tag for LEGO related packages, and now count 10 packages related to
1337 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
1338
1339 &lt;p&gt;&lt;table&gt;
1340 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/brickos&quot;&gt;brickos&lt;/a&gt;&lt;/td&gt;&lt;td&gt;alternative OS for LEGO Mindstorms RCX. Supports development in C/C++&lt;/td&gt;&lt;/tr&gt;
1341 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/leocad&quot;&gt;leocad&lt;/a&gt;&lt;/td&gt;&lt;td&gt;virtual brick CAD software&lt;/td&gt;&lt;/tr&gt;
1342 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/libnxt&quot;&gt;libnxt&lt;/a&gt;&lt;/td&gt;&lt;td&gt;utility library for talking to the LEGO Mindstorms NX&lt;/td&gt;&lt;/tr&gt;
1343 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/lnpd&quot;&gt;lnpd&lt;/a&gt;&lt;/td&gt;&lt;td&gt;daemon for LNP communication with BrickOS&lt;/td&gt;&lt;/tr&gt;
1344 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/nbc&quot;&gt;nbc&lt;/a&gt;&lt;/td&gt;&lt;td&gt;compiler for LEGO Mindstorms NXT bricks&lt;/td&gt;&lt;/tr&gt;
1345 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/nqc&quot;&gt;nqc&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Not Quite C compiler for LEGO Mindstorms RCX&lt;/td&gt;&lt;/tr&gt;
1346 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/python-nxt&quot;&gt;python-nxt&lt;/a&gt;&lt;/td&gt;&lt;td&gt;python driver/interface/wrapper for the Lego Mindstorms NXT robot&lt;/td&gt;&lt;/tr&gt;
1347 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/python-nxt-filer&quot;&gt;python-nxt-filer&lt;/a&gt;&lt;/td&gt;&lt;td&gt;simple GUI to manage files on a LEGO Mindstorms NXT&lt;/td&gt;&lt;/tr&gt;
1348 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/scratch&quot;&gt;scratch&lt;/a&gt;&lt;/td&gt;&lt;td&gt;easy to use programming environment for ages 8 and up&lt;/td&gt;&lt;/tr&gt;
1349 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/t2n&quot;&gt;t2n&lt;/a&gt;&lt;/td&gt;&lt;td&gt;simple command-line tool for Lego NXT&lt;/td&gt;&lt;/tr&gt;
1350 &lt;/table&gt;&lt;/p&gt;
1351
1352 &lt;p&gt;Some of these are available in Wheezy, and all but one are
1353 currently available in Jessie/testing. leocad is so far only
1354 available in experimental.&lt;/p&gt;
1355
1356 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
1357 adding the rest of the great free software tools available on Linux
1358 for LEGO designers.&lt;/p&gt;
1359 </description>
1360 </item>
1361
1362 <item>
1363 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
1364 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
1365 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
1366 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
1367 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
1368 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
1369 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
1370 Debian release, and I expect to move my machines at home over to it fairly
1371 soon.&lt;/p&gt;
1372
1373 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
1374 in particular make me very happy to see included. The
1375 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
1376 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
1377 included for the first time. Alongside similar programs like
1378 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
1379 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
1380 it allow for visual programming where syntax errors can not happen,
1381 and a friendly programming environment for learning to control the
1382 computer. Scratch will also be included in the next release of Debian
1383 Edu.&lt;/a&gt;
1384
1385 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
1386 Edu/Skolelinux release too. The
1387 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
1388 alpha release&lt;/a&gt; went out last week, and the next should soon
1389 follow.&lt;p&gt;
1390 </description>
1391 </item>
1392
1393 <item>
1394 <title>Isenkram 0.2 finally in the Debian archive</title>
1395 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
1396 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
1397 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
1398 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
1399 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
1400 for many months. I uploaded it to the Debian experimental suite
1401 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
1402
1403 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
1404 install to work with a pluggable hardware device. The suggestion pop
1405 up when the device is plugged in. For example if a Lego Mindstorm NXT
1406 is inserted, it will suggest to install the program needed to program
1407 the NXT controller. Give it a go, and report bugs and suggestions to
1408 BTS. :)&lt;/p&gt;
1409 </description>
1410 </item>
1411
1412 <item>
1413 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
1414 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
1415 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
1416 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
1417 <description>&lt;p&gt;My
1418 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html&quot;&gt;last
1419 bitcoin related blog post&lt;/a&gt; mentioned that the new
1420 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
1421 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
1422 2013-01-19, and have been available in unstable since then. It was
1423 automatically copied to Ubuntu, and is available in their Raring
1424 version too.&lt;/p&gt;
1425
1426 &lt;p&gt;But there is a strange problem with the build that block this new
1427 version from being available on the i386 and kfreebsd-i386
1428 architectures. For some strange reason, the autobuilders in Debian
1429 for these architectures fail to run the test suite on these
1430 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
1431 We are so far unable to reproduce it when building it manually, and
1432 no-one have been able to propose a fix. If you got an idea what is
1433 failing, please let us know via the BTS.&lt;/p&gt;
1434
1435 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
1436 I often run low on disk space, is the fact that the client will exit
1437 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
1438 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
1439 it. :)&lt;/p&gt;
1440
1441 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
1442 activities, please send Bitcoin donations to my address
1443 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1444 </description>
1445 </item>
1446
1447 <item>
1448 <title>Welcome to the world, Isenkram!</title>
1449 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
1450 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
1451 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
1452 <description>&lt;p&gt;Yesterday, I
1453 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
1454 for testers&lt;/a&gt; for my prototype for making Debian better at handling
1455 pluggable hardware devices, which I
1456 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
1457 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
1458 up, and caused me to really want to to open up the development to more
1459 people. But before I did this, I want to come up with a sensible name
1460 for this project. Today I finally decided on a new name, and I have
1461 renamed the project from hw-support-handler to this new name. In the
1462 process, I moved the source to git and made it available as a
1463 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
1464 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
1465 To fetch and build the latest version of the source, use&lt;/p&gt;
1466
1467 &lt;pre&gt;
1468 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
1469 cd isenkram &amp;&amp; git-buildpackage -us -uc
1470 &lt;/pre&gt;
1471
1472 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
1473 want to hack on the source or improve the package, please go ahead.
1474 But please talk to me first on IRC or via email before you do major
1475 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
1476
1477 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
1478 stuff, typically meaning tools, nails, screws, etc. Typical hardware
1479 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
1480 the German word eisenkram, for those that are familiar with that
1481 word.&lt;/p&gt;
1482
1483 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
1484 instructions, to avoid confusing people with an error from the signing
1485 process.&lt;/p&gt;
1486
1487 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
1488 clone argument to avoid the need for authentication.&lt;/p&gt;
1489 </description>
1490 </item>
1491
1492 <item>
1493 <title>First prototype ready making hardware easier to use in Debian</title>
1494 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
1495 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
1496 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
1497 <description>&lt;p&gt;Early this month I set out to try to
1498 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
1499 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
1500 prototype is working, and it is ready for a larger audience. To test
1501 it, fetch the
1502 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
1503 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
1504 package. You might have to log out and in again activate the
1505 autostart script.&lt;/p&gt;
1506
1507 &lt;p&gt;The design is simple:&lt;/p&gt;
1508
1509 &lt;ul&gt;
1510
1511 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
1512 hw-support-handlerd to start when the user log in.&lt;/li&gt;
1513
1514 &lt;li&gt;This program listen for kernel events about new hardware (directly
1515 from the kernel like udev does), not using HAL dbus events as I
1516 initially did.&lt;/li&gt;
1517
1518 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
1519 the APT database, a database
1520 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
1521 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
1522
1523 &lt;li&gt;If a package is mapped to the hardware in question, the package
1524 isn&#39;t installed yet and this is the first time the hardware was
1525 plugged in, show a desktop notification suggesting to install the
1526 package or packages.&lt;/li&gt;
1527
1528 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
1529 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
1530
1531 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
1532 package while showing progress information in a window.&lt;/li&gt;
1533
1534 &lt;/ul&gt;
1535
1536 &lt;p&gt;I still need to come up with a better name for the system. Here
1537 are some screen shots showing the prototype in action. First the
1538 notification, then the password request, and finally the request to
1539 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
1540
1541 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
1542 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
1543 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
1544 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
1545 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-5-installing-details.png&quot; width=&quot;70%&quot;&gt;&lt;/p&gt;
1546
1547 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
1548 is already useful. The database of hardware to package mappings also
1549 need more work. It is currently compatible with the Ubuntu way of
1550 storing such information in the package control file, but could be
1551 changed to use other formats instead or in addition to the current
1552 method. I&#39;ve dropped the use of discover for this mapping, as the
1553 modalias approach is more flexible and easier to use on Linux as long
1554 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
1555
1556 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
1557 here is the command required to check out and build the source: Use
1558 &#39;&lt;tt&gt;svn checkout
1559 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
1560 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
1561 devscripts package.&lt;/p&gt;
1562
1563 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
1564 renamed to Isenkram and the source moved from the Debian Edu
1565 subversion repository to a Debian collab-maint git repository. See
1566 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
1567 instructions&lt;/a&gt; for details.&lt;/p&gt;
1568 </description>
1569 </item>
1570
1571 <item>
1572 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
1573 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
1574 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
1575 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
1576 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
1577 suddenly in bed. With a quiet whimper, it went completely quiet and
1578 black. The power button was no longer able to turn it on. It was a
1579 IBM Thinkpad X41, and the best laptop I ever had. Better than both
1580 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
1581 Compaq I had before that. Now I need to find a replacement. To keep
1582 going during Christmas, I moved the one year old SSD disk to my old
1583 X40 where it fitted (only one I had left that could use it), but it is
1584 not a durable solution.
1585
1586 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
1587 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
1588
1589 &lt;ul&gt;
1590
1591 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
1592 than A4).&lt;/li&gt;
1593 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
1594 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
1595 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
1596 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
1597 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
1598 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
1599 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
1600 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
1601 size).&lt;/li&gt;
1602 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
1603 X.org packages.&lt;/li&gt;
1604 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
1605 the time).
1606
1607 &lt;/ul&gt;
1608
1609 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
1610 list. The reason is simply that the specifications on laptops the
1611 last 10-15 years have been sufficient for my needs, and I have to look
1612 at other features to choose my laptop. But are there still made as
1613 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
1614 robust, and Thinkpads seem to be heading in the wrong direction since
1615 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
1616 still be useful.&lt;/p&gt;
1617
1618 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
1619 external keyboard? I&#39;ll have to check the
1620 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
1621 well-supported laptops, or perhaps just buy one preinstalled from one
1622 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
1623 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
1624 </description>
1625 </item>
1626
1627 <item>
1628 <title>How to find a browser plugin supporting a given MIME type</title>
1629 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
1630 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
1631 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
1632 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
1633 install to get support for a given MIME type. Thanks to
1634 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
1635 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
1636 Unfortunately, not very many packages provide the needed meta
1637 information, Anyway, here is a small script to look up all browser
1638 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
1639
1640 &lt;pre&gt;
1641 #!/usr/bin/python
1642 import sys
1643 import apt
1644 def pkgs_handling_mimetype(mimetype):
1645 cache = apt.Cache()
1646 cache.open(None)
1647 thepkgs = []
1648 for pkg in cache:
1649 version = pkg.candidate
1650 if version is None:
1651 version = pkg.installed
1652 if version is None:
1653 continue
1654 record = version.record
1655 if not record.has_key(&#39;Npp-MimeType&#39;):
1656 continue
1657 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
1658 for t in mime_types:
1659 t = t.rstrip().strip()
1660 if t == mimetype:
1661 thepkgs.append(pkg.name)
1662 return thepkgs
1663 mimetype = &quot;audio/ogg&quot;
1664 if 1 &lt; len(sys.argv):
1665 mimetype = sys.argv[1]
1666 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
1667 for pkg in pkgs_handling_mimetype(mimetype):
1668 print &quot; %s&quot; %pkg
1669 &lt;/pre&gt;
1670
1671 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
1672
1673 &lt;pre&gt;
1674 % ./apt-find-browserplug-for-mimetype
1675 Browser plugin packages supporting audio/ogg:
1676 gecko-mediaplayer
1677 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
1678 Browser plugin packages supporting application/x-shockwave-flash:
1679 browser-plugin-gnash
1680 %
1681 &lt;/pre&gt;
1682
1683 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
1684 itself to query for plugins and propose to install the needed
1685 packages. It would be great if Debian supported such feature too. Is
1686 anyone working on adding it?&lt;/p&gt;
1687
1688 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
1689 request for icweasel support for this feature is
1690 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
1691 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
1692 of manpower and wish for a different design is the reason thus feature
1693 is not yet in iceweasel from Debian.&lt;/p&gt;
1694 </description>
1695 </item>
1696
1697 <item>
1698 <title>What is the most supported MIME type in Debian?</title>
1699 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
1700 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
1701 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
1702 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
1703 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
1704 proposal to make it possible for a Desktop application to propose to
1705 the user some package to install to gain support for a given MIME
1706 type, font, library etc. that is currently missing. With such
1707 mechanism in place, it would be possible for the desktop to
1708 automatically propose and install leocad if some LDraw file is
1709 downloaded by the browser.&lt;/p&gt;
1710
1711 &lt;p&gt;To get some idea about the current content of the archive, I decided
1712 to write a simple program to extract all .desktop files from the
1713 Debian archive and look up the claimed MIME support there. The result
1714 can be found on the
1715 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
1716 site&lt;/a&gt;. Using the collected information, it become possible to
1717 answer the question in the title. Here are the 20 most supported MIME
1718 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
1719 The complete list is available from the link above.&lt;/p&gt;
1720
1721 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
1722
1723 &lt;pre&gt;
1724 count MIME type
1725 ----- -----------------------
1726 32 text/plain
1727 30 audio/mpeg
1728 29 image/png
1729 28 image/jpeg
1730 27 application/ogg
1731 26 audio/x-mp3
1732 25 image/tiff
1733 25 image/gif
1734 22 image/bmp
1735 22 audio/x-wav
1736 20 audio/x-flac
1737 19 audio/x-mpegurl
1738 18 video/x-ms-asf
1739 18 audio/x-musepack
1740 18 audio/x-mpeg
1741 18 application/x-ogg
1742 17 video/mpeg
1743 17 audio/x-scpls
1744 17 audio/ogg
1745 16 video/x-ms-wmv
1746 &lt;/pre&gt;
1747
1748 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
1749
1750 &lt;pre&gt;
1751 count MIME type
1752 ----- -----------------------
1753 33 text/plain
1754 32 image/png
1755 32 image/jpeg
1756 29 audio/mpeg
1757 27 image/gif
1758 26 image/tiff
1759 26 application/ogg
1760 25 audio/x-mp3
1761 22 image/bmp
1762 21 audio/x-wav
1763 19 audio/x-mpegurl
1764 19 audio/x-mpeg
1765 18 video/mpeg
1766 18 audio/x-scpls
1767 18 audio/x-flac
1768 18 application/x-ogg
1769 17 video/x-ms-asf
1770 17 text/html
1771 17 audio/x-musepack
1772 16 image/x-xbitmap
1773 &lt;/pre&gt;
1774
1775 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
1776
1777 &lt;pre&gt;
1778 count MIME type
1779 ----- -----------------------
1780 31 text/plain
1781 31 image/png
1782 31 image/jpeg
1783 29 audio/mpeg
1784 28 application/ogg
1785 27 image/gif
1786 26 image/tiff
1787 26 audio/x-mp3
1788 23 audio/x-wav
1789 22 image/bmp
1790 21 audio/x-flac
1791 20 audio/x-mpegurl
1792 19 audio/x-mpeg
1793 18 video/x-ms-asf
1794 18 video/mpeg
1795 18 audio/x-scpls
1796 18 application/x-ogg
1797 17 audio/x-musepack
1798 16 video/x-ms-wmv
1799 16 video/x-msvideo
1800 &lt;/pre&gt;
1801
1802 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
1803 information mentioned in DEP-11. I have not yet had time to look at
1804 it, but hope the PackageKit people in Debian are on top of these
1805 issues.&lt;/p&gt;
1806
1807 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
1808 discovering a typo in my script.&lt;/p&gt;
1809 </description>
1810 </item>
1811
1812 <item>
1813 <title>Using modalias info to find packages handling my hardware</title>
1814 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
1815 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
1816 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
1817 <description>&lt;p&gt;Yesterday, I wrote about the
1818 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
1819 values provided by the Linux kernel&lt;/a&gt; following my hope for
1820 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
1821 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
1822 modalias values attached to package names can be used to map packages
1823 to hardware. This allow the system to look up and suggest relevant
1824 packages when I plug in some new hardware into my machine, and replace
1825 discover and discover-data as the database used to map hardware to
1826 packages.&lt;/p&gt;
1827
1828 &lt;p&gt;I create a modaliases file with entries like the following,
1829 containing package name, kernel module name (if relevant, otherwise
1830 the package name) and globs matching the relevant hardware
1831 modalias.&lt;/p&gt;
1832
1833 &lt;p&gt;&lt;blockquote&gt;
1834 Package: package-name
1835 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
1836 &lt;/blockquote&gt;&lt;/p&gt;
1837
1838 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
1839 for a given modalias value using this file.&lt;/p&gt;
1840
1841 &lt;p&gt;An entry like this would suggest the video and picture application
1842 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
1843
1844 &lt;p&gt;&lt;blockquote&gt;
1845 Package: cheese
1846 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
1847 &lt;/blockquote&gt;&lt;/p&gt;
1848
1849 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
1850 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
1851
1852 &lt;p&gt;&lt;blockquote&gt;
1853 Package: pcmciautils
1854 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
1855 &lt;/blockquote&gt;&lt;/p&gt;
1856
1857 &lt;p&gt;An entry like this would suggest the package colorhug-client when
1858 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
1859
1860 &lt;p&gt;&lt;blockquote&gt;
1861 Package: colorhug-client
1862 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
1863 &lt;/blockquote&gt;&lt;/p&gt;
1864
1865 &lt;p&gt;I believe the format is compatible with the format of the Packages
1866 file in the Debian archive. Ubuntu already uses their Packages file
1867 to store their mappings from packages to hardware.&lt;/p&gt;
1868
1869 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
1870 announce the hardware it support in a way my prototype understand.
1871 This allow those publishing packages in an APT source outside the
1872 Debian archive as well as those backporting packages to make sure the
1873 hardware mapping are included in the package meta information. I&#39;ve
1874 tested such header in the pymissile package, and its modalias mapping
1875 is working as it should with my prototype. It even made it to Ubuntu
1876 Raring.&lt;/p&gt;
1877
1878 &lt;p&gt;To test if it was possible to look up supported hardware using only
1879 the shell tools available in the Debian installer, I wrote a shell
1880 implementation of the lookup code. The idea is to create files for
1881 each modalias and let the shell do the matching. Please check out and
1882 try the
1883 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co&quot;&gt;hw-support-lookup&lt;/a&gt;
1884 shell script. It run without any extra dependencies and fetch the
1885 hardware mappings from the Debian archive and the subversion
1886 repository where I currently work on my prototype.&lt;/p&gt;
1887
1888 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
1889 install yubikey-personalization:&lt;/p&gt;
1890
1891 &lt;p&gt;&lt;blockquote&gt;
1892 % ./hw-support-lookup
1893 &lt;br&gt;yubikey-personalization
1894 &lt;br&gt;%
1895 &lt;/blockquote&gt;&lt;/p&gt;
1896
1897 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
1898 propose to install the pcmciautils package:&lt;/p&gt;
1899
1900 &lt;p&gt;&lt;blockquote&gt;
1901 % ./hw-support-lookup
1902 &lt;br&gt;pcmciautils
1903 &lt;br&gt;%
1904 &lt;/blockquote&gt;&lt;/p&gt;
1905
1906 &lt;p&gt;If you know of any hardware-package mapping that should be added to
1907 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
1908 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
1909
1910 &lt;p&gt;It could be possible to generate several of the mappings between
1911 packages and hardware. One source would be to look at packages with
1912 kernel modules, ie packages with *.ko files in /lib/modules/, and
1913 extract their modalias information. Another would be to look at
1914 packages with udev rules, ie packages with files in
1915 /lib/udev/rules.d/, and extract their vendor/model information to
1916 generate a modalias matching rule. I have not tested any of these to
1917 see if it work.&lt;/p&gt;
1918
1919 &lt;p&gt;If you want to help implementing a system to let us propose what
1920 packages to install when new hardware is plugged into a Debian
1921 machine, please send me an email or talk to me on
1922 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
1923 </description>
1924 </item>
1925
1926 <item>
1927 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
1928 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
1929 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
1930 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
1931 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
1932 information, to find the packages that support a given piece of
1933 hardware, I refreshed my memory regarding modalias values, and decided
1934 to document the details. Here are my findings so far, also available
1935 in
1936 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
1937 Debian Edu subversion repository&lt;/a&gt;:
1938
1939 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
1940
1941 &lt;p&gt;This document try to explain what the different types of modalias
1942 values stands for. It is in part based on information from
1943 &amp;lt;URL: &lt;a href=&quot;https://wiki.archlinux.org/index.php/Modalias&quot;&gt;https://wiki.archlinux.org/index.php/Modalias&lt;/a&gt; &amp;gt;,
1944 &amp;lt;URL: &lt;a href=&quot;http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device&quot;&gt;http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device&lt;/a&gt; &amp;gt;,
1945 &amp;lt;URL: &lt;a href=&quot;http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c&quot;&gt;http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c&lt;/a&gt; &amp;gt; and
1946 &amp;lt;URL: &lt;a href=&quot;http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&amp;view=markup&quot;&gt;http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&amp;view=markup&lt;/a&gt; &amp;gt;.
1947
1948 &lt;p&gt;The modalias entries for a given Linux machine can be found using
1949 this shell script:&lt;/p&gt;
1950
1951 &lt;pre&gt;
1952 find /sys -name modalias -print0 | xargs -0 cat | sort -u
1953 &lt;/pre&gt;
1954
1955 &lt;p&gt;The supported modalias globs for a given kernel module can be found
1956 using modinfo:&lt;/p&gt;
1957
1958 &lt;pre&gt;
1959 % /sbin/modinfo psmouse | grep alias:
1960 alias: serio:ty05pr*id*ex*
1961 alias: serio:ty01pr*id*ex*
1962 %
1963 &lt;/pre&gt;
1964
1965 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
1966
1967 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
1968 Bridge memory controller:&lt;/p&gt;
1969
1970 &lt;p&gt;&lt;blockquote&gt;
1971 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
1972 &lt;/blockquote&gt;&lt;/p&gt;
1973
1974 &lt;p&gt;This represent these values:&lt;/p&gt;
1975
1976 &lt;pre&gt;
1977 v 00008086 (vendor)
1978 d 00002770 (device)
1979 sv 00001028 (subvendor)
1980 sd 000001AD (subdevice)
1981 bc 06 (bus class)
1982 sc 00 (bus subclass)
1983 i 00 (interface)
1984 &lt;/pre&gt;
1985
1986 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
1987 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
1988 0600. The 0600 class is a host bridge. Other useful bus values are
1989 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
1990
1991 &lt;p&gt;Not sure how to figure out the interface value, nor what it
1992 means.&lt;/p&gt;
1993
1994 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
1995
1996 &lt;p&gt;Some typical USB entries can look like this. This is an internal
1997 USB hub in a laptop:&lt;/p&gt;
1998
1999 &lt;p&gt;&lt;blockquote&gt;
2000 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
2001 &lt;/blockquote&gt;&lt;/p&gt;
2002
2003 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
2004
2005 &lt;pre&gt;
2006 v 1D6B (device vendor)
2007 p 0001 (device product)
2008 d 0206 (bcddevice)
2009 dc 09 (device class)
2010 dsc 00 (device subclass)
2011 dp 00 (device protocol)
2012 ic 09 (interface class)
2013 isc 00 (interface subclass)
2014 ip 00 (interface protocol)
2015 &lt;/pre&gt;
2016
2017 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
2018 class is in the interface class section. For a simple USB web camera,
2019 these alias entries show up:&lt;/p&gt;
2020
2021 &lt;p&gt;&lt;blockquote&gt;
2022 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
2023 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
2024 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
2025 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
2026 &lt;/blockquote&gt;&lt;/p&gt;
2027
2028 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
2029 camera), 0101 is audio control device and 0102 is audio streaming (aka
2030 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
2031
2032 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
2033
2034 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
2035 receiver in a Thinkpad X40:&lt;/p&gt;
2036
2037 &lt;p&gt;&lt;blockquote&gt;
2038 acpi:IBM0071:PNP0511:
2039 &lt;/blockquote&gt;&lt;/p&gt;
2040
2041 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
2042
2043 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
2044
2045 &lt;p&gt;The DMI table contain lots of information about the computer case
2046 and model. This is an entry for a IBM Thinkpad X40, fetched from
2047 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
2048
2049 &lt;p&gt;&lt;blockquote&gt;
2050 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
2051 &lt;/blockquote&gt;&lt;/p&gt;
2052
2053 &lt;p&gt;The values present are&lt;/p&gt;
2054
2055 &lt;pre&gt;
2056 bvn IBM (BIOS vendor)
2057 bvr 1UETB6WW(1.66) (BIOS version)
2058 bd 06/15/2005 (BIOS date)
2059 svn IBM (system vendor)
2060 pn 2371H4G (product name)
2061 pvr ThinkPadX40 (product version)
2062 rvn IBM (board vendor)
2063 rn 2371H4G (board name)
2064 rvr NotAvailable (board version)
2065 cvn IBM (chassis vendor)
2066 ct 10 (chassis type)
2067 cvr NotAvailable (chassis version)
2068 &lt;/pre&gt;
2069
2070 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
2071 found in the dmidecode source:&lt;/p&gt;
2072
2073 &lt;pre&gt;
2074 3 Desktop
2075 4 Low Profile Desktop
2076 5 Pizza Box
2077 6 Mini Tower
2078 7 Tower
2079 8 Portable
2080 9 Laptop
2081 10 Notebook
2082 11 Hand Held
2083 12 Docking Station
2084 13 All In One
2085 14 Sub Notebook
2086 15 Space-saving
2087 16 Lunch Box
2088 17 Main Server Chassis
2089 18 Expansion Chassis
2090 19 Sub Chassis
2091 20 Bus Expansion Chassis
2092 21 Peripheral Chassis
2093 22 RAID Chassis
2094 23 Rack Mount Chassis
2095 24 Sealed-case PC
2096 25 Multi-system
2097 26 CompactPCI
2098 27 AdvancedTCA
2099 28 Blade
2100 29 Blade Enclosing
2101 &lt;/pre&gt;
2102
2103 &lt;p&gt;The chassis type values are not always accurately set in the DMI
2104 table. For example my home server is a tower, but the DMI modalias
2105 claim it is a desktop.&lt;/p&gt;
2106
2107 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
2108
2109 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
2110 test machine:&lt;/p&gt;
2111
2112 &lt;p&gt;&lt;blockquote&gt;
2113 serio:ty01pr00id00ex00
2114 &lt;/blockquote&gt;&lt;/p&gt;
2115
2116 &lt;p&gt;The values present are&lt;/p&gt;
2117
2118 &lt;pre&gt;
2119 ty 01 (type)
2120 pr 00 (prototype)
2121 id 00 (id)
2122 ex 00 (extra)
2123 &lt;/pre&gt;
2124
2125 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
2126 the valid values are.&lt;/p&gt;
2127
2128 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
2129
2130 &lt;p&gt;There are heaps of other modalias subtypes according to
2131 file2alias.c. There is the rest of the list from that source: amba,
2132 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
2133 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
2134 vmbus, x86cpu and zorro. I did not spend time documenting all of
2135 these, as they do not seem relevant for my intended use with mapping
2136 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
2137
2138 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
2139
2140 &lt;p&gt;To check which kernel modules provide support for a given modalias,
2141 one can use the following shell script:&lt;/p&gt;
2142
2143 &lt;pre&gt;
2144 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
2145 echo &quot;$id&quot; ; \
2146 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
2147 done
2148 &lt;/pre&gt;
2149
2150 &lt;p&gt;The output can look like this (only the first few entries as the
2151 list is very long on my test machine):&lt;/p&gt;
2152
2153 &lt;pre&gt;
2154 acpi:ACPI0003:
2155 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
2156 acpi:device:
2157 FATAL: Module acpi:device: not found.
2158 acpi:IBM0068:
2159 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
2160 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
2161 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
2162 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
2163 acpi:IBM0071:PNP0511:
2164 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
2165 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
2166 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
2167 [...]
2168 &lt;/pre&gt;
2169
2170 &lt;p&gt;If you want to help implementing a system to let us propose what
2171 packages to install when new hardware is plugged into a Debian
2172 machine, please send me an email or talk to me on
2173 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
2174
2175 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
2176 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
2177 in /sys/ with space in them.&lt;/p&gt;
2178 </description>
2179 </item>
2180
2181 <item>
2182 <title>Moved the pymissile Debian packaging to collab-maint</title>
2183 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
2184 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
2185 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
2186 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
2187 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
2188 Launcher and updated the Debian package
2189 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
2190 sure udev will fix the device permissions when it is plugged in. I
2191 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
2192 hopefully make the package be proposed by jockey in Ubuntu when a user
2193 plug in his rocket launcher. In the process I moved the source to a
2194 git repository under collab-maint, to make it easier for any DD to
2195 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
2196 is not very active, but the software still work for me even after five
2197 years of relative silence. The new git repository is not listed in
2198 the uploaded package yet, because I want to test the other changes a
2199 bit more before I upload the new version. If you want to check out
2200 the new version with a .desktop file included, visit the
2201 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
2202 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
2203 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
2204 </description>
2205 </item>
2206
2207 <item>
2208 <title>Lets make hardware dongles easier to use in Debian</title>
2209 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
2210 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
2211 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
2212 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
2213 general, is that there is a great package management system with the
2214 ability to automatically install software packages by downloading them
2215 from the distribution mirrors, but no way to get it to automatically
2216 install the packages I need to use the hardware I plug into my
2217 machine. Even if the package to use it is easily available from the
2218 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
2219 suggest to automatically install the python-nxt, nbc and t2n packages
2220 I need to talk to it. When I plug in a Yubikey, it could propose the
2221 yubikey-personalization package. The information required to do this
2222 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
2223
2224 &lt;p&gt;Some years ago, I proposed to
2225 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
2226 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
2227 simple:
2228
2229 &lt;ul&gt;
2230
2231 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
2232 starting when a user log in.&lt;/li&gt;
2233
2234 &lt;li&gt;Set this program up to listen for kernel events emitted when new
2235 hardware is inserted into the computer.&lt;/li&gt;
2236
2237 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
2238 database mapping to packages, and take note of any non-installed
2239 packages.&lt;/li&gt;
2240
2241 &lt;li&gt;Show a message to the user proposing to install the discovered
2242 package, and make it easy to install it.&lt;/li&gt;
2243
2244 &lt;/ul&gt;
2245
2246 &lt;p&gt;I am not sure what the best way to implement this is, but my
2247 initial idea was to use dbus events to discover new hardware, the
2248 discover database to find packages and
2249 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
2250 packages.&lt;/p&gt;
2251
2252 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
2253 draft package is now checked into
2254 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
2255 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
2256 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
2257 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
2258 the relevant packages in Debian, and uploaded a new version
2259 2.2013.01.09 to unstable. I also discovered that the current
2260 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
2261 package in Debian no longer discovered any USB devices, because
2262 /proc/bus/usb/devices is no longer present. I ported it to use
2263 libusb as a fall back option to get it working. The fixed package
2264 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
2265 because of the freeze).&lt;/p&gt;
2266
2267 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
2268 desktop notification to show up (only once, the first time it is
2269 inserted):&lt;/p&gt;
2270
2271 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-09-hw-autoinstall.png&quot;&gt;&lt;/p&gt;
2272
2273 &lt;p&gt;For this prototype to be really useful, some way to automatically
2274 install the proposed packages by pressing the &quot;Please install
2275 program(s)&quot; button should to be implemented.&lt;/p&gt;
2276
2277 &lt;p&gt;If this idea seem useful to you, and you want to help make it
2278 happen, please help me update the discover-data database with mappings
2279 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
2280 list the package you would like to have installed when a given
2281 hardware device is inserted into your computer, and report bugs using
2282 reportbug if it isn&#39;t. Or, if you know of a better way to provide
2283 such mapping, please let me know.&lt;/p&gt;
2284
2285 &lt;p&gt;This prototype need more work, and there are several questions that
2286 should be considered before it is ready for production use. Is dbus
2287 the correct way to detect new hardware? At the moment I look for HAL
2288 dbus events on the system bus, because that is the events I could see
2289 on my Debian Squeeze KDE desktop. Are there better events to use?
2290 How should the user be notified? Is the desktop notification
2291 mechanism the best option, or should the background daemon raise a
2292 popup instead? How should packages be installed? When should they
2293 not be installed?&lt;/p&gt;
2294
2295 &lt;p&gt;If you want to help getting such feature implemented in Debian,
2296 please send me an email. :)&lt;/p&gt;
2297 </description>
2298 </item>
2299
2300 <item>
2301 <title>New IRC channel for LEGO designers using Debian</title>
2302 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
2303 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
2304 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
2305 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
2306 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
2307 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
2308 discovered I had to build all the tools myself because none were
2309 already in Debian Squeeze. If Debian support for LEGO is something
2310 you care about, please join me on the IRC channel
2311 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
2312 irc.debian.org). There is a lot that could be done to improve the
2313 Debian support for LEGO designers. For example both CAD software
2314 and Mindstorm compilers are missing. :)&lt;/p&gt;
2315
2316 &lt;p&gt;Update 2012-01-03: A
2317 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
2318 including links to Lego related packages is now available.&lt;/p&gt;
2319 </description>
2320 </item>
2321
2322 <item>
2323 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
2324 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
2325 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
2326 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
2327 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
2328 year! I hope next year will prove to be a good year.&lt;/p&gt;
2329
2330 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
2331 decentralised &quot;currency&quot; that allow people to transfer bitcoins
2332 between each other with minimal overhead, is a very interesting
2333 experiment. And as I wrote a few days ago, the bitcoin situation in
2334 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
2335 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
2336 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
2337 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
2338 for one of the ftpmasters to approve the new bitcoin-qt package
2339 name.&lt;/p&gt;
2340
2341 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
2342 team in Debian, you can easily test the package in Debian Squeeze
2343 using the following steps to get a set of working packages:&lt;/p&gt;
2344
2345 &lt;blockquote&gt;&lt;pre&gt;
2346 git clone git://git.debian.org/git/collab-maint/bitcoin
2347 cd bitcoin
2348 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
2349 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
2350 &lt;/pre&gt;&lt;/blockquote&gt;
2351
2352 &lt;p&gt;You might have to install some build dependencies as well. The
2353 list of commands should give you two packages, bitcoind and
2354 bitcoin-qt, ready for use in a Squeeze environment. Note that the
2355 client will download the complete set of bitcoin &quot;blocks&quot;, which need
2356 around 5.6 GiB of data on my machine at the moment. Make sure your
2357 ~/.bitcoin/ directory have lots of spare room if you want to download
2358 all the blocks. The client will warn if the disk is getting full, so
2359 there is not really a problem if you got too little room, but you will
2360 not be able to get all the features out of the client.&lt;/p&gt;
2361
2362 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
2363 activities, please send Bitcoin donations to my address
2364 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2365 </description>
2366 </item>
2367
2368 <item>
2369 <title>A word on bitcoin support in Debian</title>
2370 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
2371 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
2372 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
2373 <description>&lt;p&gt;It has been a while since I wrote about
2374 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
2375 peer-to-peer based crypto-currency, and the reason is simply that I
2376 have been busy elsewhere. But two days ago, I started looking at the
2377 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
2378 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
2379 is now maintained by a
2380 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
2381 people&lt;/a&gt;, and the grunt work had already been done by this team. We
2382 owe a huge thank you to all these team members. :)
2383 But I was sad to discover that the bitcoin client is missing in
2384 Wheezy. It is only available in Sid (and an outdated client from
2385 backports). The client had several RC bugs registered in BTS blocking
2386 it from entering testing. To try to help the team and improve the
2387 situation, I spent some time providing patches and triaging the bug
2388 reports. I also had a look at the bitcoin package available from Matt
2389 Corallo in a
2390 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
2391 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
2392 Debian package.&lt;/p&gt;
2393
2394 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
2395 IRC, I pushed several patches into the collab-maint git repository to
2396 improve the package. It now contains fixes for the RC issues (not from
2397 me, but fixed by Scott Howard), build rules for a Qt GUI client
2398 package, konqueror support for the bitcoin: URI and bash completion
2399 setup. As I work on Debian Squeeze, I also created
2400 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
2401 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
2402 it and try to integrate it into the git repository before uploading a
2403 new version to unstable.
2404
2405 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
2406 centralized control currently exercised in the monetary system. I
2407 find it completely unacceptable that the USA government is collecting
2408 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
2409 that the major credit card companies can block legal money
2410 transactions to Wikileaks. But for bitcoin to succeed, more people
2411 need to use bitcoins, and more people need to accept bitcoins when
2412 they sell products and services. Improving the bitcoin support in
2413 Debian is a small step in the right direction, but not enough.
2414 Unfortunately the user experience when browsing the web and wanting to
2415 pay with bitcoin is still not very good. The bitcoin: URI is a step
2416 in the right direction, but need to work in most or every browser in
2417 use. Also the bitcoin-qt client is too heavy to fire up to do a
2418 quick transaction. I believe there are other clients available, but
2419 have not tested them.&lt;/p&gt;
2420
2421 &lt;p&gt;My
2422 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
2423 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
2424 I received 20.15 BTC so far on the address I provided in my blog two
2425 years ago, as can be
2426 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
2427 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
2428 donation. The blockexplorer service demonstrates quite well that
2429 bitcoin is not quite anonymous and untracked. :) I wonder if the
2430 number of users have gone up since then. If you use bitcoin and want
2431 to show your support of my activity, please send Bitcoin donations to
2432 the same address as last time,
2433 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2434 </description>
2435 </item>
2436
2437 <item>
2438 <title>Git repository for song book for Computer Scientists</title>
2439 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
2440 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
2441 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
2442 <description>&lt;p&gt;As I
2443 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
2444 this summer&lt;/a&gt;, I have created a Computer Science song book a few
2445 years ago, and today I finally found time to create a public
2446 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
2447 repository for the project&lt;/a&gt;.&lt;/p&gt;
2448
2449 &lt;p&gt;If you want to help out, please clone the source and submit patches
2450 to the HTML version. To generate the PDF and PostScript version,
2451 please use prince XML, or let me know about a useful free software
2452 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
2453
2454 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
2455 PostScript formats at
2456 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
2457 Science Songbook&lt;/a&gt;.&lt;/p&gt;
2458 </description>
2459 </item>
2460
2461 <item>
2462 <title>Gratulerer med 19-årsdagen, Debian!</title>
2463 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
2464 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
2465 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
2466 <description>&lt;p&gt;I dag fyller
2467 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
2468 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
2469 si gratulerer med dagen, Debian!&lt;/p&gt;
2470 </description>
2471 </item>
2472
2473 <item>
2474 <title>Song book for Computer Scientists</title>
2475 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
2476 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
2477 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
2478 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
2479 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
2480 collecting computer related songs for use at parties. The original
2481 version was written in LaTeX, but a few years ago I got help from
2482 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
2483 while keeping the ability to create a nice book in PDF format. I have
2484 not had time to maintain the book for a while now, and guess I should
2485 put it up on some public version control repository where others can
2486 help me extend and update the book. If anyone is volunteering to help
2487 me with this, send me an email. Also let me know if there are songs
2488 missing in my book.&lt;/p&gt;
2489
2490 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
2491 me today that I really should let all my readers share the joys of
2492 singing out load about programming, computers and computer networks.
2493 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
2494 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
2495 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
2496 Computer Science Songbook&lt;/a&gt;.
2497 </description>
2498 </item>
2499
2500 <item>
2501 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
2502 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
2503 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
2504 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
2505 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
2506 around 1000 at the moment. To be able to get help from the vendors
2507 when something go wrong, we want to keep the firmware on the servers
2508 up to date. If the firmware isn&#39;t the latest and greatest, the
2509 vendors typically refuse to start debugging any problems until the
2510 firmware is upgraded. So before every reboot, we want to upgrade the
2511 firmware, and we would really like everyone handling servers at the
2512 university to do this themselves when they plan to reboot a machine.
2513 For that to happen we at the unix server admin group need to provide
2514 the tools to do so.&lt;/p&gt;
2515
2516 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
2517 fetch and install the latest firmware for the servers we got. Most of
2518 our hardware are from Dell and HP, so I have focused on these servers
2519 so far. This blog post is about the Dell part.&lt;/P&gt;
2520
2521 &lt;p&gt;On the Dell FTP site I was lucky enough to find
2522 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
2523 with firmware information for all 11th generation servers, listing
2524 which firmware should be used on a given model and where on the FTP
2525 site I can find it. Using a simple perl XML parser I can then
2526 download the shell scripts Dell provides to do firmware upgrades from
2527 within Linux and reboot when all the firmware is primed and ready to
2528 be activated on the first reboot.&lt;/p&gt;
2529
2530 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
2531 Are there anyone working on similar tools for firmware upgrading all
2532 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
2533
2534 &lt;p&gt;&lt;pre&gt;
2535 #!/usr/bin/perl
2536 use strict;
2537 use warnings;
2538 use File::Temp qw(tempdir);
2539 BEGIN {
2540 # Install needed RHEL packages if missing
2541 my %rhelmodules = (
2542 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
2543 );
2544 for my $module (keys %rhelmodules) {
2545 eval &quot;use $module;&quot;;
2546 if ($@) {
2547 my $pkg = $rhelmodules{$module};
2548 system(&quot;yum install -y $pkg&quot;);
2549 eval &quot;use $module;&quot;;
2550 }
2551 }
2552 }
2553 my $errorsto = &#39;pere@hungry.com&#39;;
2554
2555 upgrade_dell();
2556
2557 exit 0;
2558
2559 sub run_firmware_script {
2560 my ($opts, $script) = @_;
2561 unless ($script) {
2562 print STDERR &quot;fail: missing script name\n&quot;;
2563 exit 1
2564 }
2565 print STDERR &quot;Running $script\n\n&quot;;
2566
2567 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
2568 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
2569 } else {
2570 print STDERR &quot;fail: firmware script returned error\n&quot;;
2571 }
2572 }
2573
2574 sub run_firmware_scripts {
2575 my ($opts, @dirs) = @_;
2576 # Run firmware packages
2577 for my $dir (@dirs) {
2578 print STDERR &quot;info: Running scripts in $dir\n&quot;;
2579 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
2580 while (my $s = readdir $dh) {
2581 next if $s =~ m/^\.\.?/;
2582 run_firmware_script($opts, &quot;$dir/$s&quot;);
2583 }
2584 closedir $dh;
2585 }
2586 }
2587
2588 sub download {
2589 my $url = shift;
2590 print STDERR &quot;info: Downloading $url\n&quot;;
2591 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
2592 }
2593
2594 sub upgrade_dell {
2595 my @dirs;
2596 my $product = `dmidecode -s system-product-name`;
2597 chomp $product;
2598
2599 if ($product =~ m/PowerEdge/) {
2600
2601 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
2602 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
2603
2604 my $tmpdir = tempdir(
2605 CLEANUP =&gt; 1
2606 );
2607 chdir($tmpdir);
2608 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
2609 system(&#39;gunzip Catalog.xml.gz&#39;);
2610 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
2611 # -q is quiet, disabling interactivity and reducing console output
2612 my $fwopts = &quot;-q&quot;;
2613 if (@paths) {
2614 for my $url (@paths) {
2615 fetch_dell_fw($url);
2616 }
2617 run_firmware_scripts($fwopts, $tmpdir);
2618 } else {
2619 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
2620 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
2621 }
2622 chdir(&#39;/&#39;);
2623 } else {
2624 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
2625 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
2626 }
2627 }
2628
2629 sub fetch_dell_fw {
2630 my $path = shift;
2631 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
2632 download($url);
2633 }
2634
2635 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
2636 # firmware packages to download from Dell. Only work for Linux
2637 # machines and 11th generation Dell servers.
2638 sub fetch_dell_fw_list {
2639 my $filename = shift;
2640
2641 my $product = `dmidecode -s system-product-name`;
2642 chomp $product;
2643 my ($mybrand, $mymodel) = split(/\s+/, $product);
2644
2645 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
2646
2647 my $xml = XMLin($filename);
2648 my @paths;
2649 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
2650 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
2651 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
2652 my $oscode;
2653 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
2654 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
2655 } else {
2656 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
2657 }
2658 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
2659 {
2660 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
2661 }
2662 }
2663 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
2664 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
2665
2666 # Drop application packages, only firmware and BIOS
2667 next if &#39;APAC&#39; eq $componenttype;
2668
2669 my $cpath = $component-&gt;{path};
2670 for my $path (@paths) {
2671 if ($cpath =~ m%/$path$%) {
2672 push(@paths, $cpath);
2673 }
2674 }
2675 }
2676 return @paths;
2677 }
2678 &lt;/pre&gt;
2679
2680 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
2681 it could work on other platforms with some tweaking. Anyone know a
2682 index like Catalog.xml is available from HP for HP servers? At the
2683 moment I maintain a similar list manually and it is quickly getting
2684 outdated.&lt;/p&gt;
2685 </description>
2686 </item>
2687
2688 <item>
2689 <title>How is booting into runlevel 1 different from single user boots?</title>
2690 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
2691 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
2692 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
2693 <description>&lt;p&gt;Wouter Verhelst have some
2694 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
2695 comments and opinions&lt;/a&gt; on my blog post on
2696 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html&quot;&gt;the
2697 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
2698 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html&quot;&gt;the
2699 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
2700 small piece of his comment now, and though it best to address the
2701 misunderstanding he bring forward:&lt;/p&gt;
2702
2703 &lt;p&gt;&lt;blockquote&gt;
2704 Currently, a system admin has four options: [...] boot to a
2705 single-user system (by adding &#39;single&#39; to the kernel command line;
2706 this runs rcS and rc1 scripts)
2707 &lt;/blockquote&gt;&lt;/p&gt;
2708
2709 &lt;p&gt;This make me believe Wouter believe booting into single user mode
2710 and booting into runlevel 1 is the same. I am not surprised he
2711 believe this, because it would make sense and is a quite sensible
2712 thing to believe. But because the boot in Debian is slightly broken,
2713 runlevel 1 do not work properly and it isn&#39;t the same as single user
2714 mode. I&#39;ll try to explain what is actually happing, but it is a bit
2715 hard to explain.&lt;/p&gt;
2716
2717 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
2718 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
2719 executed in single user mode is sulogin. Single user mode is a boot
2720 state &quot;between&quot; the runlevels, and when booting into single user mode,
2721 only the scripts in /etc/rcS.d/ are executed before the init process
2722 enters the single user state. When switching to runlevel 1, the state
2723 is in fact not ending in runlevel 1, but it passes through runlevel 1
2724 and end up in the single user mode (see /etc/rc1.d/S03single, which
2725 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
2726 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
2727 mode enabled by /etc/rcS.d/ (which is more like the initial boot
2728 mode).&lt;/p&gt;
2729
2730 &lt;p&gt;This summary might make it clearer. When booting for the first
2731 time into single user mode, the following commands are executed:
2732 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
2733 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
2734 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
2735 trying to continue after visiting single user mode. Not all services
2736 are started again as they should, causing the machine to end up in an
2737 unpredicatble state. This is why Debian admins recommend rebooting
2738 after visiting single user mode.&lt;/p&gt;
2739
2740 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
2741 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
2742 to runlevel 1, the services started from /etc/rcS.d/ are not properly
2743 stopped when passing through the scripts in /etc/rc1.d/, and not
2744 started again when switching away from runlevel 1 to the runlevels
2745 2-5. I believe the problem is best fixed by moving all the scripts
2746 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
2747 functioning single user mode during boot.&lt;/p&gt;
2748
2749 &lt;p&gt;I have spent several years investigating the Debian boot system,
2750 and discovered this problem a few years ago. I suspect it originates
2751 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
2752 </description>
2753 </item>
2754
2755 <item>
2756 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
2757 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
2758 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
2759 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
2760 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
2761 are started from /etc/rcS.d/. In fact, there is a bite more of them
2762 than make sense, and this causes a few problems. What kind of
2763 problems, you might ask. There are at least two problems. The first
2764 is that it is not possible to recover a machine after switching to
2765 runlevel 1. One need to actually reboot to get the machine back to
2766 the expected state. The other is that single user boot will sometimes
2767 run into problems because some of the subsystems are activated before
2768 the root login is presented, causing problems when trying to recover a
2769 machine from a problem in that subsystem. A minor additional point is
2770 that moving more scripts out of rcS.d/ and into the other rc#.d/
2771 directories will increase the amount of scripts that can run in
2772 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
2773
2774 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
2775 scripts that _have_ to execute before the root login prompt is
2776 presented during a single user boot should go there. Everything else
2777 should go into the numeric runlevels. This means things like
2778 lm-sensors, fuse and x11-common should not run from rcS.d, but from
2779 the numeric runlevels. Today in Debian, there are around 115 init.d
2780 scripts that are started from rcS.d/, and most of them should be moved
2781 out. Do your package have one of them? Please help us make single
2782 user and runlevel 1 better by moving it.&lt;/p&gt;
2783
2784 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
2785 etc. should still be started from rcS.d/, but there is for example no
2786 need to have the network enabled before the single user login prompt
2787 is presented.&lt;/p&gt;
2788
2789 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
2790 Debian systems working while scripts migrate and during upgrades, the
2791 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
2792 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
2793 and the next ones can only be moved when their dependencies have been
2794 moved first. This migration must be done sequentially while we ensure
2795 that the package system upgrade packages in the right order to keep
2796 the system state correct. This will require some coordination when it
2797 comes to network related packages, but most of the packages with
2798 scripts that should migrate do not have anything in rcS.d/ depending
2799 on them. Some packages have already been updated, like the sudo
2800 package, while others are still left to do. I wish I had time to work
2801 on this myself, but real live constrains make it unlikely that I will
2802 find time to push this forward.&lt;/p&gt;
2803 </description>
2804 </item>
2805
2806 <item>
2807 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
2808 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
2809 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
2810 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
2811 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
2812 mentioned the issues I believe should be improved in Debian for its
2813 desktop to be useful for more people. The use case for this is my
2814 parents, which are currently running Kubuntu which solve the
2815 issues.&lt;/p&gt;
2816
2817 &lt;p&gt;I suspect these four missing features are not very hard to
2818 implement. After all, they are present in Ubuntu, so if we wanted to
2819 do this in Debian we would have a source.&lt;/p&gt;
2820
2821 &lt;ol&gt;
2822
2823 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
2824 are new packages available for upgrades, a icon in the KDE status bar
2825 indicate this, and clicking on it will activate the simple upgrade
2826 tool to handle it. I have no problem guiding both of my parents
2827 through the process over the phone. If a kernel reboot is required,
2828 this too is indicated by the status bars and the upgrade tool. Last
2829 time I checked, nothing with the same features was working in KDE in
2830 Debian.&lt;/li&gt;
2831
2832 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
2833 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
2834 currently have a handler for, it will ask the user if the system
2835 should search for a package that would add support for this MIME type,
2836 and if the user say yes, the APT sources will be searched for packages
2837 advertising the MIME type in their control file (visible in the
2838 Packages file in the APT archive). If one or more packages are found,
2839 it is a simple click of the mouse to add support for the missing mime
2840 type. If the package require the user to accept some non-free
2841 license, this is explained to the user. The entire process make it
2842 more clear to the user why something do not work in the browser, and
2843 make the chances higher for the user to blame the web page authors and
2844 not the browser for any missing features.&lt;/li&gt;
2845
2846 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
2847 handlers.&lt;/strong&gt; When the media players encounter a format or codec
2848 it is not supporting, a dialog pop up asking the user if the system
2849 should search for a package that would add support for it. This
2850 happen with things like MP3, Windows Media or H.264. The selection
2851 and installation procedure is very similar to the Firefox browser
2852 plugin handling. This is as far as I know implemented using a
2853 gstreamer hook. The end result is that the user easily get access to
2854 the codecs that are present from the APT archives available, while
2855 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
2856
2857 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
2858 displaying a text/plain file in my Debian browser, it will propose to
2859 start emacs to show it. If I remember correctly, when doing the same
2860 in Kunbutu it show the file as a text file in the browser. At least I
2861 know Opera will show text files within the browser. I much prefer the
2862 latter behaviour.&lt;/li&gt;
2863
2864 &lt;/ol&gt;
2865
2866 &lt;p&gt;There are other nice features as well, like the simplified suite
2867 upgrader, but given that I am the one mostly doing the dist-upgrade,
2868 it do not matter much.&lt;/p&gt;
2869
2870 &lt;p&gt;I really hope we could get these features in place for the next
2871 Debian release. It would require the coordinated effort of several
2872 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
2873 </description>
2874 </item>
2875
2876 <item>
2877 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
2878 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
2879 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
2880 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
2881 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
2882 site is build on Debian/Squeeze, and this platform was chosen because
2883 I am most familiar with Debian (being a Debian Developer for around 10
2884 years) because it is the latest stable Debian release which should get
2885 security support for a few years.&lt;/p&gt;
2886
2887 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
2888 that are missing in Debian at the moment. It would be great if these
2889 modules were added to the Debian archive, allowing anyone to set up
2890 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
2891 in their own country using only Debian packages. The list of modules
2892 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
2893 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
2894 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
2895 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
2896 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
2897 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
2898 easier in the future.&lt;/p&gt;
2899
2900 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
2901 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
2902 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
2903 with the responsibility of tracking security problems, which I really
2904 do not have time for.&lt;/p&gt;
2905 </description>
2906 </item>
2907
2908 <item>
2909 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
2910 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
2911 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
2912 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
2913 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
2914 posts have been in Norwegian the last few weeks, so here is a short
2915 update in English.&lt;/p&gt;
2916
2917 &lt;p&gt;The kids still keep me too busy to get much free software work
2918 done, but I did manage to organise a project to get a Norwegian port
2919 of the British service
2920 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
2921 and it has been running for a month now. The entire project has been
2922 organised by me and two others. Around Christmas we gathered sponsors
2923 to fund the development work. In January I drafted a contract with
2924 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
2925 and in February the development took place. Most of it involved
2926 converting the source to use GPS coordinates instead of British
2927 easting/northing, and the resulting code should be a lot easier to get
2928 running in any country by now. The Norwegian
2929 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
2930 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
2931 source and the source for administrative borders in Norway, and
2932 support for this had to be added/fixed.&lt;/p&gt;
2933
2934 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
2935 polishing the system before we announced it March 7th. The system is
2936 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
2937 problem reports in a few weeks. Soon we hope to announce the Android
2938 and iPhone versions making it even easier to report problems with the
2939 public infrastructure.&lt;/p&gt;
2940
2941 &lt;p&gt;Perhaps something to consider for those of you in countries without
2942 such service?&lt;/p&gt;
2943 </description>
2944 </item>
2945
2946 <item>
2947 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
2948 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
2949 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
2950 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
2951 <description>&lt;p&gt;The last few days I have looked at ways to track open security
2952 issues here at my work with the University of Oslo. My idea is that
2953 it should be possible to use the information about security issues
2954 available on the Internet, and check our locally
2955 maintained/distributed software against this information. It should
2956 allow us to verify that no known security issues are forgotten. The
2957 CVE database listing vulnerabilities seem like a great central point,
2958 and by using the package lists from Debian mapped to CVEs provided by
2959 the testing security team, I believed it should be possible to figure
2960 out which security holes were present in our free software
2961 collection.&lt;/p&gt;
2962
2963 &lt;p&gt;After reading up on the topic, it became obvious that the first
2964 building block is to be able to name software packages in a unique and
2965 consistent way across data sources. I considered several ways to do
2966 this, for example coming up with my own naming scheme like using URLs
2967 to project home pages or URLs to the Freshmeat entries, or using some
2968 existing naming scheme. And it seem like I am not the first one to
2969 come across this problem, as MITRE already proposed and implemented a
2970 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
2971 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
2972 software, hardware and other platform components. The CPE ids are
2973 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
2974 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
2975 issues for any CPE name. With this in place, all I need to do is to
2976 locate the CPE id for the software packages we use at the university.
2977 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
2978 NVD entry if a CVE for the package exist).&lt;/p&gt;
2979
2980 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
2981 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
2982 check out, one could look up
2983 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/search?cpe=cpe%3A%2Fa%3Agnu%3Agzip:1.3.3&quot;&gt;cpe:/a:gnu:gzip:1.3.3
2984 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
2985 The most recent one is
2986 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
2987 and at the bottom of the NVD page for this vulnerability the complete
2988 list of affected versions is provided.&lt;/p&gt;
2989
2990 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
2991 for offline processing of issues. Using this dump, I&#39;ve written a
2992 small script taking a list of CPEs as input and list all CVEs
2993 affecting the packages represented by these CPEs. One give it CPEs
2994 with version numbers as specified above and get a list of open
2995 security issues out.&lt;/p&gt;
2996
2997 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
2998 information need to be high. For that to happen, I believe as many as
2999 possible need to use and contribute to the NVD database. I notice
3000 RHEL is providing
3001 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
3002 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
3003 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
3004
3005 &lt;p&gt;To get an idea about the quality for free software, I spent some
3006 time making it possible to compare the CVE database from Debian with
3007 the CVE database in NVD. The result look fairly good, but there are
3008 some inconsistencies in NVD (same software package having several
3009 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
3010 Debian believe are affected by a CVE). Hope to find time to improve
3011 the quality of NVD, but that require being able to get in touch with
3012 someone maintaining it. So far my three emails with questions and
3013 corrections have not seen any reply, but I hope contact can be
3014 established soon.&lt;/p&gt;
3015
3016 &lt;p&gt;An interesting application for CPEs is cross platform package
3017 mapping. It would be useful to know which packages in for example
3018 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
3019 this would be trivial if all linux distributions provided CPE entries
3020 for their packages.&lt;/p&gt;
3021 </description>
3022 </item>
3023
3024 <item>
3025 <title>Which module is loaded for a given PCI and USB device?</title>
3026 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
3027 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
3028 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
3029 <description>&lt;p&gt;In the
3030 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
3031 package in Debian, there is a script to report useful information
3032 about the running hardware for use when people report missing
3033 information. One part of this script that I find very useful when
3034 debugging hardware problems, is the part mapping loaded kernel module
3035 to the PCI device it claims. It allow me to quickly see if the kernel
3036 module I expect is driving the hardware I am struggling with. To see
3037 the output, make sure discover-data is installed and run
3038 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
3039 one of my machines like this:&lt;/p&gt;
3040
3041 &lt;pre&gt;
3042 loaded modules:
3043 10de:03eb i2c_nforce2
3044 10de:03f1 ohci_hcd
3045 10de:03f2 ehci_hcd
3046 10de:03f0 snd_hda_intel
3047 10de:03ec pata_amd
3048 10de:03f6 sata_nv
3049 1022:1103 k8temp
3050 109e:036e bttv
3051 109e:0878 snd_bt87x
3052 11ab:4364 sky2
3053 &lt;/pre&gt;
3054
3055 &lt;p&gt;The code in question look like this, slightly modified for
3056 readability and to drop the output to file descriptor 3:&lt;/p&gt;
3057
3058 &lt;pre&gt;
3059 if [ -d /sys/bus/pci/devices/ ] ; then
3060 echo loaded pci modules:
3061 (
3062 cd /sys/bus/pci/devices/
3063 for address in * ; do
3064 if [ -d &quot;$address/driver/module&quot; ] ; then
3065 module=`cd $address/driver/module ; pwd -P | xargs basename`
3066 if grep -q &quot;^$module &quot; /proc/modules ; then
3067 address=$(echo $address |sed s/0000://)
3068 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
3069 echo &quot;$id $module&quot;
3070 fi
3071 fi
3072 done
3073 )
3074 echo
3075 fi
3076 &lt;/pre&gt;
3077
3078 &lt;p&gt;Similar code could be used to extract USB device module
3079 mappings:&lt;/p&gt;
3080
3081 &lt;pre&gt;
3082 if [ -d /sys/bus/usb/devices/ ] ; then
3083 echo loaded usb modules:
3084 (
3085 cd /sys/bus/usb/devices/
3086 for address in * ; do
3087 if [ -d &quot;$address/driver/module&quot; ] ; then
3088 module=`cd $address/driver/module ; pwd -P | xargs basename`
3089 if grep -q &quot;^$module &quot; /proc/modules ; then
3090 address=$(echo $address |sed s/0000://)
3091 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
3092 if [ &quot;$id&quot; ] ; then
3093 echo &quot;$id $module&quot;
3094 fi
3095 fi
3096 fi
3097 done
3098 )
3099 echo
3100 fi
3101 &lt;/pre&gt;
3102
3103 &lt;p&gt;This might perhaps be something to include in other tools as
3104 well.&lt;/p&gt;
3105 </description>
3106 </item>
3107
3108 <item>
3109 <title>How to test if a laptop is working with Linux</title>
3110 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
3111 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
3112 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
3113 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
3114 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
3115 batch of computers will work with Linux. Every year for the last few
3116 years the university have organised shared bid of a few thousand
3117 computers, and this year HP won the bid. Two different desktops and
3118 five different laptops are on the list this year. We in the UNIX
3119 group want to know which one of these computers work well with RHEL
3120 and Ubuntu, the two Linux distributions we currently handle at the
3121 university.&lt;/p&gt;
3122
3123 &lt;p&gt;My test method is simple, and I share it here to get feedback and
3124 perhaps inspire others to test hardware as well. To test, I PXE
3125 install the OS version of choice, and log in as my normal user and run
3126 a few applications and plug in selected pieces of hardware. When
3127 something fail, I make a note about this in the test matrix and move
3128 on. If I have some spare time I try to report the bug to the OS
3129 vendor, but as I only have the machines for a short time, I rarely
3130 have the time to do this for all the problems I find.&lt;/p&gt;
3131
3132 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
3133 I perform on a new model.&lt;/p&gt;
3134
3135 &lt;ul&gt;
3136
3137 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
3138 and Ubuntu Maverik at the moment. If I feel like it, I also test with
3139 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
3140
3141 &lt;li&gt;Is X.org working? If the graphical login screen show up after
3142 installation, X.org is working.&lt;/li&gt;
3143
3144 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
3145 package mesa-utils on Ubuntu) and writing down the frames per second
3146 reported by the program.&lt;/li&gt;
3147
3148 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
3149 logging in, and if I can hear this the test is successful. If there
3150 are several audio exits on the machine, I try them all and check if
3151 the Gnome/KDE audio mixer can control where to send the sound. I
3152 normally test this by playing
3153 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
3154 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
3155
3156 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
3157 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
3158
3159 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
3160 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
3161
3162 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
3163 picture from the v4l device show up.&lt;/li&gt;
3164
3165 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
3166 any bluetooth devices are discovered. In my office, I normally see a
3167 few.&lt;/li&gt;
3168
3169 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
3170 memory modules lying around, and stick them in and see if Gnome/KDE
3171 notice this.&lt;/li&gt;
3172
3173 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
3174 special button work, and if the laptop continue to work after
3175 resume.&lt;/li&gt;
3176
3177 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
3178 adjusting background light, switching on/off external video output,
3179 switching on/off wifi, bluetooth, etc? The set of buttons differ from
3180 laptop to laptop, so I just write down which are working and which are
3181 not.&lt;/li&gt;
3182
3183 &lt;li&gt;Some laptops have smart card readers, finger print readers,
3184 acceleration sensors etc. I rarely test these, as I do not know how
3185 to quickly test if they are working or not, so I only document their
3186 existence.&lt;/li&gt;
3187
3188 &lt;/ul&gt;
3189
3190 &lt;p&gt;By now I suspect you are really curious what the test results are
3191 for the HP machines I am testing. I&#39;m not done yet, so I will report
3192 the test results later. For now I can report that HP 8100 Elite work
3193 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
3194 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
3195 can see, I have most machines left to test. One interesting
3196 observation is that Ubuntu Lucid has almost twice the frame rate than
3197 RHEL6 with glxgears. No idea why.&lt;/p&gt;
3198 </description>
3199 </item>
3200
3201 <item>
3202 <title>Some thoughts on BitCoins</title>
3203 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
3204 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
3205 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
3206 <description>&lt;p&gt;As I continue to explore
3207 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
3208 what properties the system have, and how it will be affected by laws
3209 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
3210
3211 &lt;p&gt;One interesting thing to note is that since the transactions are
3212 verified using a peer to peer network, all details about a transaction
3213 is known to everyone. This means that if a BitCoin address has been
3214 published like I did with mine in my initial post about BitCoin, it is
3215 possible for everyone to see how many BitCoins have been transfered to
3216 that address. There is even a web service to look at the details for
3217 all transactions. There I can see that my address
3218 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
3219 have received 16.06 Bitcoin, the
3220 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
3221 address of Simon Phipps have received 181.97 BitCoin and the address
3222 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
3223 of EFF have received 2447.38 BitCoins so far. Thank you to each and
3224 every one of you that donated bitcoins to support my activity. The
3225 fact that anyone can see how much money was transfered to a given
3226 address make it more obvious why the BitCoin community recommend to
3227 generate and hand out a new address for each transaction. I&#39;m told
3228 there is no way to track which addresses belong to a given person or
3229 organisation without the person or organisation revealing it
3230 themselves, as Simon, EFF and I have done.&lt;/p&gt;
3231
3232 &lt;p&gt;In Norway, and in most other countries, there are laws and
3233 regulations limiting how much money one can transfer across the border
3234 without declaring it. There are money laundering, tax and accounting
3235 laws and regulations I would expect to apply to the use of BitCoin.
3236 If the Skolelinux foundation
3237 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
3238 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
3239 normal bank transfers like EFF is doing, how should this be accounted?
3240 Given that it is impossible to know if money can cross the border or
3241 not, should everything or nothing be declared? What exchange rate
3242 should be used when calculating taxes? Would receivers have to pay
3243 income tax if the foundation were to pay Skolelinux contributors in
3244 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
3245
3246 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
3247 accepted by a lot of users. It must be possible to get easy access to
3248 the currency (as a wage or using currency exchanges), and it must be
3249 easy to spend it. At the moment BitCoin seem fairly easy to get
3250 access to, but there are very few places to spend it. I am not really
3251 a regular user of any of the vendor types currently accepting BitCoin,
3252 so I wonder when my kind of shop would start accepting BitCoins. I
3253 would like to buy electronics, travels and subway tickets, not herbs
3254 and books. :) The currency is young, and this will improve over time
3255 if it become popular, but I suspect regular banks will start to lobby
3256 to get BitCoin declared illegal if it become popular. I&#39;m sure they
3257 will claim it is helping fund terrorism and money laundering (which
3258 probably would be true, as is any currency in existence), but I
3259 believe the problems should be solved elsewhere and not by blaming
3260 currencies.&lt;/p&gt;
3261
3262 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
3263 CPU intensive process that depend on a bit of luck as well (as one is
3264 competing against all the other miners currently spending CPU cycles
3265 to see which one get the next lump of cash). The &quot;winner&quot; get 50
3266 BitCoin when this happen. Yesterday I came across the obvious way to
3267 join forces to increase ones changes of getting at least some coins,
3268 by coordinating the work on mining BitCoins across several machines
3269 and people, and sharing the result if one is lucky and get the 50
3270 BitCoins. Check out
3271 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
3272 if this sounds interesting. I have not had time to try to set up a
3273 machine to participate there yet, but have seen that running on ones
3274 own for a few days have not yield any BitCoins througth mining
3275 yet.&lt;/p&gt;
3276
3277 &lt;p&gt;Update 2010-12-15: Found an &lt;a
3278 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
3279 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
3280 it was interesting to read. The arguments presented seem to be
3281 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
3282 </description>
3283 </item>
3284
3285 <item>
3286 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
3287 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
3288 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
3289 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
3290 <description>&lt;p&gt;With this weeks lawless
3291 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
3292 attacks&lt;/a&gt; on Wikileak and
3293 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
3294 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
3295 not be trusted to handle money transactions.
3296 A blog post from
3297 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
3298 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
3299 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
3300 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
3301 some help from my friend to get it all running, and he even handed me
3302 some bitcoins to get started. I even donated a few bitcoins to Simon
3303 for helping me remember BitCoin.&lt;/p&gt;
3304
3305 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
3306 crypto-currency, decentralised and handled using peer-to-peer
3307 networks. It allows anonymous transactions and prohibits central
3308 control over the transactions, making it impossible for governments
3309 and companies alike to block donations and other transactions. The
3310 source is free software, and while the key dependency wxWidgets 2.9
3311 for the graphical user interface is missing in Debian, the command
3312 line client builds just fine. Hopefully Jonas
3313 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
3314 Debian&lt;/a&gt; soon.&lt;/p&gt;
3315
3316 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
3317 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
3318 bitcoins&lt;/a&gt; when selling services and goods, and there are even
3319 currency &quot;stock&quot; markets where the exchange rate is decided. There
3320 are not many users so far, but the concept seems promising. If you
3321 want to get started and lack a friend with any bitcoins to spare,
3322 you can even get
3323 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
3324 bitcoin at the time of writing). Use
3325 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
3326 on the current exchange rates.&lt;/p&gt;
3327
3328 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
3329 machines. If you want to support my activity, please send Bitcoin
3330 donations to the address
3331 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
3332 </description>
3333 </item>
3334
3335 <item>
3336 <title>Why isn&#39;t Debian Edu using VLC?</title>
3337 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
3338 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
3339 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
3340 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
3341 presented, and the winner among the multimedia player were VLC.
3342 Personally, I like VLC, and it is my player of choice when I first try
3343 to play a video file or stream. Only if VLC fail will I drag out
3344 gmplayer to see if it can do better. The reason is mostly the failure
3345 model and trust. When VLC fail, it normally pop up a error message
3346 reporting the problem. When mplayer fail, it normally segfault or
3347 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
3348
3349 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
3350 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
3351 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
3352 plugin to play web videos seamlessly, and the VLC browser plugin is
3353 not very good. For example, it lack in-line control buttons, so there
3354 is no way for the user to pause the video. Also, when I
3355 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
3356 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
3357 failed on several video pages where mplayer based plugins worked. If
3358 the browser plugin for VLC was as good as the gecko-mediaplayer
3359 package (which uses mplayer), we would switch.&lt;/P&gt;
3360
3361 &lt;p&gt;While VLC is a good player, its user interface is slightly
3362 annoying. The most annoying feature is its inconsistent use of
3363 keyboard shortcuts. When the player is in full screen mode, its
3364 shortcuts are different from when it is playing the video in a window.
3365 For example, space only work as pause when in full screen mode. I
3366 wish it had consisten shortcuts and that space also would work when in
3367 window mode. Another nice shortcut in gmplayer is [enter] to restart
3368 the current video. It is very nice when playing short videos from the
3369 web and want to restart it when new people arrive to have a look at
3370 what is going on.&lt;/p&gt;
3371 </description>
3372 </item>
3373
3374 <item>
3375 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
3376 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
3377 <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>
3378 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
3379 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
3380 upgrade testing of the
3381 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
3382 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
3383 This seem like a very good idea, so I adjusted by test scripts and
3384 can now present the updated result from today:&lt;/p&gt;
3385
3386 &lt;p&gt;This is for Gnome:&lt;/p&gt;
3387
3388 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
3389
3390 &lt;blockquote&gt;&lt;p&gt;
3391 apache2.2-bin
3392 aptdaemon
3393 baobab
3394 binfmt-support
3395 browser-plugin-gnash
3396 cheese-common
3397 cli-common
3398 cups-pk-helper
3399 dmz-cursor-theme
3400 empathy
3401 empathy-common
3402 freedesktop-sound-theme
3403 freeglut3
3404 gconf-defaults-service
3405 gdm-themes
3406 gedit-plugins
3407 geoclue
3408 geoclue-hostip
3409 geoclue-localnet
3410 geoclue-manual
3411 geoclue-yahoo
3412 gnash
3413 gnash-common
3414 gnome
3415 gnome-backgrounds
3416 gnome-cards-data
3417 gnome-codec-install
3418 gnome-core
3419 gnome-desktop-environment
3420 gnome-disk-utility
3421 gnome-screenshot
3422 gnome-search-tool
3423 gnome-session-canberra
3424 gnome-system-log
3425 gnome-themes-extras
3426 gnome-themes-more
3427 gnome-user-share
3428 gstreamer0.10-fluendo-mp3
3429 gstreamer0.10-tools
3430 gtk2-engines
3431 gtk2-engines-pixbuf
3432 gtk2-engines-smooth
3433 hamster-applet
3434 libapache2-mod-dnssd
3435 libapr1
3436 libaprutil1
3437 libaprutil1-dbd-sqlite3
3438 libaprutil1-ldap
3439 libart2.0-cil
3440 libboost-date-time1.42.0
3441 libboost-python1.42.0
3442 libboost-thread1.42.0
3443 libchamplain-0.4-0
3444 libchamplain-gtk-0.4-0
3445 libcheese-gtk18
3446 libclutter-gtk-0.10-0
3447 libcryptui0
3448 libdiscid0
3449 libelf1
3450 libepc-1.0-2
3451 libepc-common
3452 libepc-ui-1.0-2
3453 libfreerdp-plugins-standard
3454 libfreerdp0
3455 libgconf2.0-cil
3456 libgdata-common
3457 libgdata7
3458 libgdu-gtk0
3459 libgee2
3460 libgeoclue0
3461 libgexiv2-0
3462 libgif4
3463 libglade2.0-cil
3464 libglib2.0-cil
3465 libgmime2.4-cil
3466 libgnome-vfs2.0-cil
3467 libgnome2.24-cil
3468 libgnomepanel2.24-cil
3469 libgpod-common
3470 libgpod4
3471 libgtk2.0-cil
3472 libgtkglext1
3473 libgtksourceview2.0-common
3474 libmono-addins-gui0.2-cil
3475 libmono-addins0.2-cil
3476 libmono-cairo2.0-cil
3477 libmono-corlib2.0-cil
3478 libmono-i18n-west2.0-cil
3479 libmono-posix2.0-cil
3480 libmono-security2.0-cil
3481 libmono-sharpzip2.84-cil
3482 libmono-system2.0-cil
3483 libmtp8
3484 libmusicbrainz3-6
3485 libndesk-dbus-glib1.0-cil
3486 libndesk-dbus1.0-cil
3487 libopal3.6.8
3488 libpolkit-gtk-1-0
3489 libpt2.6.7
3490 libpython2.6
3491 librpm1
3492 librpmio1
3493 libsdl1.2debian
3494 libsrtp0
3495 libssh-4
3496 libtelepathy-farsight0
3497 libtelepathy-glib0
3498 libtidy-0.99-0
3499 media-player-info
3500 mesa-utils
3501 mono-2.0-gac
3502 mono-gac
3503 mono-runtime
3504 nautilus-sendto
3505 nautilus-sendto-empathy
3506 p7zip-full
3507 pkg-config
3508 python-aptdaemon
3509 python-aptdaemon-gtk
3510 python-axiom
3511 python-beautifulsoup
3512 python-bugbuddy
3513 python-clientform
3514 python-coherence
3515 python-configobj
3516 python-crypto
3517 python-cupshelpers
3518 python-elementtree
3519 python-epsilon
3520 python-evolution
3521 python-feedparser
3522 python-gdata
3523 python-gdbm
3524 python-gst0.10
3525 python-gtkglext1
3526 python-gtksourceview2
3527 python-httplib2
3528 python-louie
3529 python-mako
3530 python-markupsafe
3531 python-mechanize
3532 python-nevow
3533 python-notify
3534 python-opengl
3535 python-openssl
3536 python-pam
3537 python-pkg-resources
3538 python-pyasn1
3539 python-pysqlite2
3540 python-rdflib
3541 python-serial
3542 python-tagpy
3543 python-twisted-bin
3544 python-twisted-conch
3545 python-twisted-core
3546 python-twisted-web
3547 python-utidylib
3548 python-webkit
3549 python-xdg
3550 python-zope.interface
3551 remmina
3552 remmina-plugin-data
3553 remmina-plugin-rdp
3554 remmina-plugin-vnc
3555 rhythmbox-plugin-cdrecorder
3556 rhythmbox-plugins
3557 rpm-common
3558 rpm2cpio
3559 seahorse-plugins
3560 shotwell
3561 software-center
3562 system-config-printer-udev
3563 telepathy-gabble
3564 telepathy-mission-control-5
3565 telepathy-salut
3566 tomboy
3567 totem
3568 totem-coherence
3569 totem-mozilla
3570 totem-plugins
3571 transmission-common
3572 xdg-user-dirs
3573 xdg-user-dirs-gtk
3574 xserver-xephyr
3575 &lt;/p&gt;&lt;/blockquote&gt;
3576
3577 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
3578
3579 &lt;blockquote&gt;&lt;p&gt;
3580 cheese
3581 ekiga
3582 eog
3583 epiphany-extensions
3584 evolution-exchange
3585 fast-user-switch-applet
3586 file-roller
3587 gcalctool
3588 gconf-editor
3589 gdm
3590 gedit
3591 gedit-common
3592 gnome-games
3593 gnome-games-data
3594 gnome-nettool
3595 gnome-system-tools
3596 gnome-themes
3597 gnuchess
3598 gucharmap
3599 guile-1.8-libs
3600 libavahi-ui0
3601 libdmx1
3602 libgalago3
3603 libgtk-vnc-1.0-0
3604 libgtksourceview2.0-0
3605 liblircclient0
3606 libsdl1.2debian-alsa
3607 libspeexdsp1
3608 libsvga1
3609 rhythmbox
3610 seahorse
3611 sound-juicer
3612 system-config-printer
3613 totem-common
3614 transmission-gtk
3615 vinagre
3616 vino
3617 &lt;/p&gt;&lt;/blockquote&gt;
3618
3619 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
3620
3621 &lt;blockquote&gt;&lt;p&gt;
3622 gstreamer0.10-gnomevfs
3623 &lt;/p&gt;&lt;/blockquote&gt;
3624
3625 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
3626
3627 &lt;blockquote&gt;&lt;p&gt;
3628 [nothing]
3629 &lt;/p&gt;&lt;/blockquote&gt;
3630
3631 &lt;p&gt;This is for KDE:&lt;/p&gt;
3632
3633 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
3634
3635 &lt;blockquote&gt;&lt;p&gt;
3636 ksmserver
3637 &lt;/p&gt;&lt;/blockquote&gt;
3638
3639 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
3640
3641 &lt;blockquote&gt;&lt;p&gt;
3642 kwin
3643 network-manager-kde
3644 &lt;/p&gt;&lt;/blockquote&gt;
3645
3646 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
3647
3648 &lt;blockquote&gt;&lt;p&gt;
3649 arts
3650 dolphin
3651 freespacenotifier
3652 google-gadgets-gst
3653 google-gadgets-xul
3654 kappfinder
3655 kcalc
3656 kcharselect
3657 kde-core
3658 kde-plasma-desktop
3659 kde-standard
3660 kde-window-manager
3661 kdeartwork
3662 kdeartwork-emoticons
3663 kdeartwork-style
3664 kdeartwork-theme-icon
3665 kdebase
3666 kdebase-apps
3667 kdebase-workspace
3668 kdebase-workspace-bin
3669 kdebase-workspace-data
3670 kdeeject
3671 kdelibs
3672 kdeplasma-addons
3673 kdeutils
3674 kdewallpapers
3675 kdf
3676 kfloppy
3677 kgpg
3678 khelpcenter4
3679 kinfocenter
3680 konq-plugins-l10n
3681 konqueror-nsplugins
3682 kscreensaver
3683 kscreensaver-xsavers
3684 ktimer
3685 kwrite
3686 libgle3
3687 libkde4-ruby1.8
3688 libkonq5
3689 libkonq5-templates
3690 libnetpbm10
3691 libplasma-ruby
3692 libplasma-ruby1.8
3693 libqt4-ruby1.8
3694 marble-data
3695 marble-plugins
3696 netpbm
3697 nuvola-icon-theme
3698 plasma-dataengines-workspace
3699 plasma-desktop
3700 plasma-desktopthemes-artwork
3701 plasma-runners-addons
3702 plasma-scriptengine-googlegadgets
3703 plasma-scriptengine-python
3704 plasma-scriptengine-qedje
3705 plasma-scriptengine-ruby
3706 plasma-scriptengine-webkit
3707 plasma-scriptengines
3708 plasma-wallpapers-addons
3709 plasma-widget-folderview
3710 plasma-widget-networkmanagement
3711 ruby
3712 sweeper
3713 update-notifier-kde
3714 xscreensaver-data-extra
3715 xscreensaver-gl
3716 xscreensaver-gl-extra
3717 xscreensaver-screensaver-bsod
3718 &lt;/p&gt;&lt;/blockquote&gt;
3719
3720 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
3721
3722 &lt;blockquote&gt;&lt;p&gt;
3723 ark
3724 google-gadgets-common
3725 google-gadgets-qt
3726 htdig
3727 kate
3728 kdebase-bin
3729 kdebase-data
3730 kdepasswd
3731 kfind
3732 klipper
3733 konq-plugins
3734 konqueror
3735 ksysguard
3736 ksysguardd
3737 libarchive1
3738 libcln6
3739 libeet1
3740 libeina-svn-06
3741 libggadget-1.0-0b
3742 libggadget-qt-1.0-0b
3743 libgps19
3744 libkdecorations4
3745 libkephal4
3746 libkonq4
3747 libkonqsidebarplugin4a
3748 libkscreensaver5
3749 libksgrd4
3750 libksignalplotter4
3751 libkunitconversion4
3752 libkwineffects1a
3753 libmarblewidget4
3754 libntrack-qt4-1
3755 libntrack0
3756 libplasma-geolocation-interface4
3757 libplasmaclock4a
3758 libplasmagenericshell4
3759 libprocesscore4a
3760 libprocessui4a
3761 libqalculate5
3762 libqedje0a
3763 libqtruby4shared2
3764 libqzion0a
3765 libruby1.8
3766 libscim8c2a
3767 libsmokekdecore4-3
3768 libsmokekdeui4-3
3769 libsmokekfile3
3770 libsmokekhtml3
3771 libsmokekio3
3772 libsmokeknewstuff2-3
3773 libsmokeknewstuff3-3
3774 libsmokekparts3
3775 libsmokektexteditor3
3776 libsmokekutils3
3777 libsmokenepomuk3
3778 libsmokephonon3
3779 libsmokeplasma3
3780 libsmokeqtcore4-3
3781 libsmokeqtdbus4-3
3782 libsmokeqtgui4-3
3783 libsmokeqtnetwork4-3
3784 libsmokeqtopengl4-3
3785 libsmokeqtscript4-3
3786 libsmokeqtsql4-3
3787 libsmokeqtsvg4-3
3788 libsmokeqttest4-3
3789 libsmokeqtuitools4-3
3790 libsmokeqtwebkit4-3
3791 libsmokeqtxml4-3
3792 libsmokesolid3
3793 libsmokesoprano3
3794 libtaskmanager4a
3795 libtidy-0.99-0
3796 libweather-ion4a
3797 libxklavier16
3798 libxxf86misc1
3799 okteta
3800 oxygencursors
3801 plasma-dataengines-addons
3802 plasma-scriptengine-superkaramba
3803 plasma-widget-lancelot
3804 plasma-widgets-addons
3805 plasma-widgets-workspace
3806 polkit-kde-1
3807 ruby1.8
3808 systemsettings
3809 update-notifier-common
3810 &lt;/p&gt;&lt;/blockquote&gt;
3811
3812 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
3813 aptitude a bit more similar, but there are still quite a lott of
3814 differences. I have no idea what packages should be installed after
3815 the upgrade, but hope those that do can have a look.&lt;/p&gt;
3816 </description>
3817 </item>
3818
3819 <item>
3820 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
3821 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
3822 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
3823 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
3824 <description>&lt;p&gt;Most of the computers in use by the
3825 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
3826 are virtual machines. And they have been Xen machines running on a
3827 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
3828 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
3829 bit harder that it could have been, because we set up the Xen virtual
3830 machines to get the virtual partitions from LVM, which as far as I
3831 know is not supported by KVM. So to migrate, we had to convert
3832 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
3833
3834 &lt;p&gt;I found
3835 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
3836 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
3837 migration. It uses qemu-img from the qemu package to make the disk
3838 image, parted to partition it, losetup and kpartx to present the disk
3839 image partions as devices, and dd to copy the data. I NFS mounted the
3840 new servers storage area on the old server to do the migration.&lt;/p&gt;
3841
3842 &lt;pre&gt;
3843 #!/bin/sh
3844
3845 # Based on
3846 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
3847
3848 set -e
3849 set -x
3850
3851 if [ -z &quot;$1&quot; ] ; then
3852 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
3853 exit 1
3854 else
3855 host=&quot;$1&quot;
3856 fi
3857
3858 if [ ! -e /dev/vg_data/$host-disk ] ; then
3859 echo &quot;error: unable to find LVM volume for $host&quot;
3860 exit 1
3861 fi
3862
3863 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
3864 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
3865 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
3866 totalsize=$(( ( $disksize + $swapsize ) ))
3867
3868 img=$host.img
3869 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
3870 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
3871
3872 parted $img mklabel msdos
3873 parted $img mkpart primary linux-swap 0 $disksize
3874 parted $img mkpart primary ext2 $disksize $totalsize
3875 parted $img set 1 boot on
3876
3877 modprobe dm-mod
3878 losetup /dev/loop0 $img
3879 kpartx -a /dev/loop0
3880
3881 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
3882 fsck.ext3 -f /dev/mapper/loop0p1 || true
3883 mkswap /dev/mapper/loop0p2
3884
3885 kpartx -d /dev/loop0
3886 losetup -d /dev/loop0
3887 &lt;/pre&gt;
3888
3889 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
3890 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
3891
3892 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
3893 the new disk image attached, installed grub-pc and linux-image-686 and
3894 set up grub to boot from the disk image. After this, the KVM machines
3895 seem to work just fine.&lt;/p&gt;
3896 </description>
3897 </item>
3898
3899 <item>
3900 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
3901 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
3902 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
3903 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
3904 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
3905 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
3906 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
3907 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
3908
3909 &lt;p&gt;I still do not know what a correct migration should look like, so I
3910 report any differences between apt and aptitude and hope someone else
3911 can see if anything should be changed.&lt;/p&gt;
3912
3913 &lt;p&gt;This is for Gnome:&lt;/p&gt;
3914
3915 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
3916
3917 &lt;blockquote&gt;&lt;p&gt;
3918 apache2.2-bin aptdaemon at-spi baobab binfmt-support
3919 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
3920 dmz-cursor-theme empathy empathy-common finger
3921 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
3922 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
3923 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
3924 gnome-cards-data gnome-codec-install gnome-core
3925 gnome-desktop-environment gnome-disk-utility gnome-screenshot
3926 gnome-search-tool gnome-session-canberra gnome-spell
3927 gnome-system-log gnome-themes-extras gnome-themes-more
3928 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
3929 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
3930 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
3931 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
3932 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
3933 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
3934 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
3935 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
3936 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
3937 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
3938 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
3939 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
3940 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
3941 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
3942 libgtk2.0-cil libgtkglext1 libgtksourceview-common
3943 libgtksourceview2.0-common libmono-addins-gui0.2-cil
3944 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
3945 libmono-i18n-west2.0-cil libmono-posix2.0-cil
3946 libmono-security2.0-cil libmono-sharpzip2.84-cil
3947 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
3948 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
3949 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
3950 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
3951 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
3952 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
3953 libxalan2-java libxerces2-java media-player-info mesa-utils
3954 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
3955 nautilus-sendto-empathy openoffice.org-writer2latex
3956 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
3957 python-aptdaemon python-aptdaemon-gtk python-axiom
3958 python-beautifulsoup python-bugbuddy python-clientform
3959 python-coherence python-configobj python-crypto python-cupshelpers
3960 python-cupsutils python-eggtrayicon python-elementtree
3961 python-epsilon python-evolution python-feedparser python-gdata
3962 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
3963 python-gtksourceview2 python-httplib2 python-louie python-mako
3964 python-markupsafe python-mechanize python-nevow python-notify
3965 python-opengl python-openssl python-pam python-pkg-resources
3966 python-pyasn1 python-pysqlite2 python-rdflib python-serial
3967 python-tagpy python-twisted-bin python-twisted-conch
3968 python-twisted-core python-twisted-web python-utidylib python-webkit
3969 python-xdg python-zope.interface remmina remmina-plugin-data
3970 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
3971 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
3972 software-center svgalibg1 system-config-printer-udev
3973 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
3974 totem totem-coherence totem-mozilla totem-plugins
3975 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
3976 zip
3977 &lt;/p&gt;&lt;/blockquote&gt;
3978
3979 Installed using apt-get, removed with aptitude
3980
3981 &lt;blockquote&gt;&lt;p&gt;
3982 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
3983 epiphany-extensions epiphany-gecko evolution-exchange
3984 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
3985 gedit-common gnome-app-install gnome-games gnome-games-data
3986 gnome-nettool gnome-system-tools gnome-themes gnome-utils
3987 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
3988 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
3989 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
3990 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
3991 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
3992 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
3993 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
3994 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
3995 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
3996 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
3997 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
3998 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
3999 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
4000 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
4001 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
4002 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
4003 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
4004 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
4005 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
4006 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
4007 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
4008 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
4009 sound-juicer swfdec-gnome system-config-printer totem-common
4010 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
4011 &lt;/p&gt;&lt;/blockquote&gt;
4012
4013 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4014
4015 &lt;blockquote&gt;&lt;p&gt;
4016 gstreamer0.10-gnomevfs
4017 &lt;/p&gt;&lt;/blockquote&gt;
4018
4019 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4020
4021 &lt;blockquote&gt;&lt;p&gt;
4022 [nothing]
4023 &lt;/p&gt;&lt;/blockquote&gt;
4024
4025 &lt;p&gt;This is for KDE:&lt;/p&gt;
4026
4027 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4028
4029 &lt;blockquote&gt;&lt;p&gt;
4030 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
4031 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
4032 ghostscript-x git gnome-audio gnugo granatier gs-common
4033 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
4034 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
4035 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
4036 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
4037 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
4038 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
4039 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
4040 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
4041 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
4042 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
4043 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
4044 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
4045 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
4046 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
4047 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
4048 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
4049 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
4050 libkrossui4 libmailtools-perl libmime-tools-perl
4051 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
4052 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
4053 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
4054 lirc luatex marble networkstatus noatun-plugins
4055 openoffice.org-writer2latex palapeli palapeli-data parley
4056 parley-data poster psutils pulseaudio pulseaudio-esound-compat
4057 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
4058 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
4059 ttf-sazanami-gothic
4060 &lt;/p&gt;&lt;/blockquote&gt;
4061
4062 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4063
4064 &lt;blockquote&gt;&lt;p&gt;
4065 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
4066 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
4067 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
4068 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
4069 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
4070 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
4071 kitchensync kiten kjumpingcube klatin klettres klickety klines
4072 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
4073 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
4074 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
4075 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
4076 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
4077 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
4078 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
4079 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
4080 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
4081 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
4082 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
4083 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
4084 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
4085 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
4086 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
4087 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
4088 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
4089 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
4090 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
4091 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
4092 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
4093 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
4094 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
4095 mpeglib network-manager-kde noatun pmount tex-common texlive-base
4096 texlive-common texlive-doc-base texlive-fonts-recommended tidy
4097 ttf-dustin ttf-kochi-gothic ttf-sjfonts
4098 &lt;/p&gt;&lt;/blockquote&gt;
4099
4100 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4101
4102 &lt;blockquote&gt;&lt;p&gt;
4103 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
4104 kdeartwork kdebase kdebase-apps kdebase-workspace
4105 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
4106 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
4107 netpbm plasma-widget-folderview plasma-widget-networkmanagement
4108 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
4109 xscreensaver-screensaver-bsod
4110 &lt;/p&gt;&lt;/blockquote&gt;
4111
4112 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4113
4114 &lt;blockquote&gt;&lt;p&gt;
4115 kdebase-bin konq-plugins konqueror
4116 &lt;/p&gt;&lt;/blockquote&gt;
4117 </description>
4118 </item>
4119
4120 <item>
4121 <title>Gnash buildbot slave and Debian kfreebsd</title>
4122 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
4123 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
4124 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
4125 <description>&lt;p&gt;Answering
4126 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
4127 call from the Gnash project&lt;/a&gt; for
4128 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
4129 current source, I have set up a virtual KVM machine on the Debian
4130 Edu/Skolelinux virtualization host to test the git source on
4131 Debian/Squeeze. I hope this can help the developers in getting new
4132 releases out more often.&lt;/p&gt;
4133
4134 &lt;p&gt;As the developers want less main-stream build platforms tested to,
4135 I have considered setting up a &lt;a
4136 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
4137 machine as well. I have also considered using the kfreebsd
4138 architecture in Debian as a file server in NUUG to get access to the 5
4139 TB zfs volume we currently use to store DV video. Because of this, I
4140 finally got around to do a test installation of Debian/Squeeze with
4141 kfreebsd. Installation went fairly smooth, thought I noticed some
4142 visual glitches in the cdebconf dialogs (black cursor left on the
4143 screen at random locations). Have not gotten very far with the
4144 testing. Noticed cfdisk did not work, but fdisk did so it was not a
4145 fatal problem. Have to spend some more time on it to see if it is
4146 useful as a file server for NUUG. Will try to find time to set up a
4147 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
4148 </description>
4149 </item>
4150
4151 <item>
4152 <title>Debian in 3D</title>
4153 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
4154 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
4155 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
4156 <description>&lt;p&gt;&lt;img src=&quot;http://thingiverse-production.s3.amazonaws.com/renders/23/e0/c4/f9/2b/debswagtdose_preview_medium.jpg&quot;&gt;&lt;/p&gt;
4157
4158 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
4159 3D linked in from
4160 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
4161 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
4162 </description>
4163 </item>
4164
4165 <item>
4166 <title>Software updates 2010-10-24</title>
4167 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
4168 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
4169 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
4170 <description>&lt;p&gt;Some updates.&lt;/p&gt;
4171
4172 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
4173 raise money for the project is going well. The lower limit of 10
4174 signers was reached in 24 hours, and so far 13 people have signed it.
4175 More signers and more funding is most welcome, and I am really curious
4176 how far we can get before the time limit of December 24 is reached.
4177 :)&lt;/p&gt;
4178
4179 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
4180 about what appear to be a great code coverage tool capable of
4181 generating code coverage stats without any changes to the source code.
4182 It is called
4183 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
4184 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
4185 It is missing in Debian, but the git source built just fine in Squeeze
4186 after I installed libelf-dev, libdwarf-dev, pkg-config and
4187 libglib2.0-dev. Failed to build in Lenny, but suspect that is
4188 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
4189
4190 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
4191 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
4192 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
4193 alpha test release of the Squeeze based Debian Edu /
4194 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
4195 release. Give it a try if you need a complete linux solution for your
4196 school, including central infrastructure server, workstations, thin
4197 client servers and diskless workstations. A nice touch added
4198 yesterday is RDP support on the thin client servers, for windows
4199 clients to get a Linux desktop on request.&lt;/p&gt;
4200 </description>
4201 </item>
4202
4203 <item>
4204 <title>Some notes on Flash in Debian and Debian Edu</title>
4205 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
4206 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
4207 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
4208 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
4209 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
4210 second most popular used package that is missing in Debian. The sixth
4211 most popular is flashplayer-mozilla. This is a clear indication that
4212 working flash is important for Debian users. Around 10 percent of the
4213 users submitting data to popcon.debian.org have this package
4214 installed.&lt;/p&gt;
4215
4216 &lt;p&gt;In the report written by Lars Risan in August 2008
4217&lt;a href=&quot;http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile&amp;do=view&amp;target=Skolelinux_i_bruk_rapport_1.0.pdf&quot;&gt;Skolelinux
4218 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
4219 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
4220 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
4221 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
4222 web sites require Flash to work, and lacking working Flash support in
4223 the web browser and the problems with installing it was perceived as a
4224 good reason to stay with Windows.&lt;/p&gt;
4225
4226 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
4227 said to be the retarded cousin that did not really understand
4228 everything you told him but could work fairly well. This was a
4229 comment regarding the problems Linux have with proprietary formats and
4230 non-standard web pages, and is sad because it exposes a fairly common
4231 understanding of whose fault it is if web pages that only work in for
4232 example Internet Explorer 6 fail to work on Firefox, and funny because
4233 it explain very well how annoying it is for users when Linux
4234 distributions do not work with the documents they receive or the web
4235 pages they want to visit.&lt;/p&gt;
4236
4237 &lt;p&gt;This is part of the reason why I believe it is important for Debian
4238 and Debian Edu to have a well working Flash implementation in the
4239 distribution, to get at least popular sites as Youtube and Google
4240 Video to working out of the box. For Squeeze, Debian have the chance
4241 to include the latest version of Gnash that will make this happen, as
4242 the new release 0.8.8 was published a few weeks ago and is resting in
4243 unstable. The new version work with more sites that version 0.8.7.
4244 The Gnash maintainers have asked for a freeze exception, but the
4245 release team have not had time to reply to it yet. I hope they agree
4246 with me that Flash is important for the Debian desktop users, and thus
4247 accept the new package into Squeeze.&lt;/p&gt;
4248 </description>
4249 </item>
4250
4251 <item>
4252 <title>Circular package dependencies harms apt recovery</title>
4253 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
4254 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
4255 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
4256 <description>&lt;p&gt;I discovered this while doing
4257 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
4258 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
4259 in Debian still got circular dependencies, and it is often claimed
4260 that apt and aptitude should be able to handle this just fine, but
4261 some times these dependency loops causes apt to fail.&lt;/p&gt;
4262
4263 &lt;p&gt;An example is from todays
4264 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
4265 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
4266 causes perl-modules to fail to upgrade. The cause is simple. If a
4267 package fail to unpack, then only part of packages with the circular
4268 dependency might end up being unpacked when unpacking aborts, and the
4269 ones already unpacked will fail to configure in the recovery phase
4270 because its dependencies are unavailable.&lt;/p&gt;
4271
4272 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
4273
4274 &lt;blockquote&gt;&lt;pre&gt;
4275 dpkg: dependency problems prevent configuration of perl-modules:
4276 perl-modules depends on perl (&gt;= 5.10.1-1); however:
4277 Version of perl on system is 5.10.0-19lenny2.
4278 dpkg: error processing perl-modules (--configure):
4279 dependency problems - leaving unconfigured
4280 &lt;/pre&gt;&lt;/blockquote&gt;
4281
4282 &lt;p&gt;The perl/perl-modules circular dependency is already
4283 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
4284 hopefully be solved as soon as possible, but it is not the only one,
4285 and each one of these loops in the dependency tree can cause similar
4286 failures. Of course, they only occur when there are bugs in other
4287 packages causing the unpacking to fail, but it is rather nasty when
4288 the failure of one package causes the problem to become worse because
4289 of dependency loops.&lt;/p&gt;
4290
4291 &lt;p&gt;Thanks to
4292 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
4293 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
4294 dependencies
4295 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
4296 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
4297
4298 &lt;p&gt;Todays testing also exposed a bug in
4299 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
4300 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
4301 apt-get and aptitude, the latter possibly caused by some circular
4302 dependency. Reported both to BTS to try to get someone to look at
4303 it.&lt;/p&gt;
4304 </description>
4305 </item>
4306
4307 <item>
4308 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
4309 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
4310 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
4311 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
4312 <description>&lt;p&gt;This is a
4313 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;followup&lt;/a&gt;
4314 on my
4315 &lt;a href=&quot;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&quot;&gt;previous
4316 work&lt;/a&gt; on
4317 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
4318 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
4319
4320 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
4321 LDAP objects, I have had a look at how the packages pdns-backend-ldap
4322 and dhcp3-server-ldap in Debian use the LDAP server. The two
4323 implementations are quite different in how they use LDAP.&lt;/p&gt;
4324
4325 To get this information, I started slapd with debugging enabled and
4326 dumped the debug output to a file to get the LDAP searches performed
4327 on a Debian Edu main-server. Here is a summary.
4328
4329 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
4330
4331 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
4332 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
4333 the web.
4334
4335 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
4336 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
4337 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
4338 reverse entries are in two different subtrees in LDAP with a structure
4339 based on the DNS names, as in tjener.intern and
4340 2.2.0.10.in-addr.arpa.&lt;/p&gt;
4341
4342 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
4343 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
4344 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
4345 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
4346 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
4347 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
4348 forward entries, it is looking for attributes named dnsttl, arecord,
4349 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
4350 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
4351 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
4352 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
4353 spfrecord and modifytimestamp. For reverse entries it is looking for
4354 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
4355 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
4356 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
4357 ldapsearch commands could look like this:&lt;/p&gt;
4358
4359 &lt;blockquote&gt;&lt;pre&gt;
4360 ldapsearch -h ldap \
4361 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
4362 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
4363 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
4364 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
4365 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
4366 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
4367
4368 ldapsearch -h ldap \
4369 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
4370 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
4371 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
4372 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
4373 srvrecord naptrrecord modifytimestamp
4374 &lt;/pre&gt;&lt;/blockquote&gt;
4375
4376 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
4377 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
4378 example LDAP objects used there. In addition to these objects, the
4379 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
4380 also exist.&lt;/p&gt;
4381
4382 &lt;blockquote&gt;&lt;pre&gt;
4383 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
4384 objectclass: top
4385 objectclass: dnsdomain
4386 objectclass: domainrelatedobject
4387 dc: tjener
4388 arecord: 10.0.2.2
4389 associateddomain: tjener.intern
4390
4391 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
4392 objectclass: top
4393 objectclass: dnsdomain2
4394 objectclass: domainrelatedobject
4395 dc: 2
4396 ptrrecord: tjener.intern
4397 associateddomain: 2.2.0.10.in-addr.arpa
4398 &lt;/pre&gt;&lt;/blockquote&gt;
4399
4400 &lt;p&gt;In strict mode, the server behaves differently. When looking for
4401 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
4402 same base as in the tree mode for a object with filter
4403 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
4404 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
4405 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
4406 naptrrecord and modifytimestamp. For reverse entires it also do a
4407 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
4408 and the requested attributes are associateddomain, dnsttl and
4409 modifytimestamp. In short, in strict mode the objects with ptrrecord
4410 go away, and the arecord attribute in the forward object is used
4411 instead.&lt;/p&gt;
4412
4413 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
4414 like this:&lt;/p&gt;
4415
4416 &lt;blockquote&gt;&lt;pre&gt;
4417 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
4418 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
4419 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
4420 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
4421 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
4422 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
4423
4424 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
4425 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
4426 &lt;/pre&gt;&lt;/blockquote&gt;
4427
4428 &lt;p&gt;In addition to the forward and reverse searches , there is also a
4429 search for SOA records, which behave similar to the forward and
4430 reverse lookups.&lt;/p&gt;
4431
4432 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
4433 specify any objectclass names, and instead look for the attributes it
4434 need to generate a DNS reply. This make it able to work with any
4435 objectclass that provide the needed attributes.&lt;/p&gt;
4436
4437 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
4438 dnsdomain2 schemas. The latter is used for reverse entries like
4439 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
4440
4441 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
4442 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
4443 attributes) and domainrelatedobject (for associatedDomain). The use
4444 of structural object classes make it impossible to combine these
4445 classes with the object classes used by DHCP.&lt;/p&gt;
4446
4447 &lt;p&gt;There are other schemas that could be used too, for example the
4448 dnszone structural object class used by Gosa and bind-sdb for the DNS
4449 attributes combined with the domainrelatedobject object class, but in
4450 this case some unused attributes would have to be included as well
4451 (zonename and relativedomainname).&lt;/p&gt;
4452
4453 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
4454 mode and not use any of the existing objectclasses (dnsdomain,
4455 dnsdomain2 and dnszone) when one want to combine the DNS information
4456 with DHCP information, and instead create a auxiliary object class
4457 defined something like this (using the attributes defined for
4458 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
4459
4460 &lt;blockquote&gt;&lt;pre&gt;
4461 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
4462 SUP top
4463 AUXILIARY
4464 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
4465 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
4466 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
4467 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
4468 A6Record $ DNAMERecord
4469 ))
4470 &lt;/pre&gt;&lt;/blockquote&gt;
4471
4472 &lt;p&gt;This will allow any object to become a DNS entry when combined with
4473 the domainrelatedobject object class, and allow any entity to include
4474 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
4475 developers asking for their view on this schema and if they are
4476 interested in providing such schema with PowerDNS, and I hope my
4477 message will be accepted into their mailing list soon.&lt;/p&gt;
4478
4479 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
4480
4481 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
4482 the object attributes, and then uses the attributes it want. This
4483 make it harder to figure out exactly what attributes are used, but
4484 thanks to the working example in Debian Edu I can at least get an idea
4485 what is needed without having to read the source code.&lt;/p&gt;
4486
4487 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
4488 search filter to use to locate the correct dhcpServer entity is
4489 stored. These are the relevant entries from
4490 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
4491
4492 &lt;blockquote&gt;&lt;pre&gt;
4493 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
4494 ldap-dhcp-server-cn &quot;dhcp&quot;;
4495 &lt;/pre&gt;&lt;/blockquote&gt;
4496
4497 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
4498 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
4499 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
4500 search result is this entry:&lt;/p&gt;
4501
4502 &lt;blockquote&gt;&lt;pre&gt;
4503 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
4504 cn: dhcp
4505 objectClass: top
4506 objectClass: dhcpServer
4507 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
4508 &lt;/pre&gt;&lt;/blockquote&gt;
4509
4510 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
4511 subtree with DHCP configuration. The DHCP configuration subtree base
4512 is located using a base scope search with base &quot;cn=DHCP
4513 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
4514 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
4515 The search result is this entry:&lt;/p&gt;
4516
4517 &lt;blockquote&gt;&lt;pre&gt;
4518 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
4519 cn: DHCP Config
4520 objectClass: top
4521 objectClass: dhcpService
4522 objectClass: dhcpOptions
4523 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
4524 dhcpStatements: ddns-update-style none
4525 dhcpStatements: authoritative
4526 dhcpOption: smtp-server code 69 = array of ip-address
4527 dhcpOption: www-server code 72 = array of ip-address
4528 dhcpOption: wpad-url code 252 = text
4529 &lt;/pre&gt;&lt;/blockquote&gt;
4530
4531 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
4532 all the DHCP configuration is loaded, it is ready to receive requests.
4533 The subtree in Debian Edu contain objects with object classes
4534 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
4535 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
4536 and information about netmasks, dynamic range etc. Leaving out the
4537 details here because it is not relevant for the focus of my
4538 investigation, which is to see if it is possible to merge dns and dhcp
4539 related computer objects.&lt;/p&gt;
4540
4541 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
4542 of the client (00:00:00:00:00:00 in this example), using a subtree
4543 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
4544 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
4545 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
4546 like:&lt;/p&gt;
4547
4548 &lt;blockquote&gt;&lt;pre&gt;
4549 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
4550 cn: hostname
4551 objectClass: top
4552 objectClass: dhcpHost
4553 dhcpHWAddress: ethernet 00:00:00:00:00:00
4554 dhcpStatements: fixed-address hostname
4555 &lt;/pre&gt;&lt;/blockquote&gt;
4556
4557 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
4558 The object classes need to have fixed names, and the configuration
4559 need to be stored in a fairly specific LDAP structure. On the
4560 positive side, the invidiual dhcpHost entires can be anywhere without
4561 the DN pointed to by the dhcpServer entries. The latter should make
4562 it possible to group all host entries in a subtree next to the
4563 configuration entries, and this subtree can also be shared with the
4564 DNS server if the schema proposed above is combined with the dhcpHost
4565 structural object class.
4566
4567 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
4568
4569 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
4570 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
4571 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
4572 allowing DNS objects to be stored anywhere under the base cn specified
4573 in the configuration.&lt;/p&gt;
4574
4575 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
4576 regarding which LDAP schemas to use and which LDAP structure to use.
4577 I guess one could implement ones own schema, as long as the
4578 objectclasses and attributes have the names used, but this do not
4579 really help when the DHCP subtree need to have a fairly fixed
4580 structure.&lt;/p&gt;
4581
4582 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
4583 this might work for Debian Edu:&lt;/p&gt;
4584
4585 &lt;blockquote&gt;&lt;pre&gt;
4586 ou=services
4587 cn=machine-info (dhcpService) - dhcpServiceDN points here
4588 cn=dhcp (dhcpServer)
4589 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
4590 cn=10.0.2.0 (dhcpSubnet)
4591 cn=group1 (dhcpGroup/dhcpOptions)
4592 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
4593 cn=192.168.0.0 (dhcpSubnet)
4594 cn=group1 (dhcpGroup/dhcpOptions)
4595 ou=machines - PowerDNS base points here
4596 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
4597 &lt;/pre&gt;&lt;/blockquote&gt;
4598
4599 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
4600 entries to be in the dhcpGroup subtrees, the entries can be stored
4601 there instead of a common machines subtree, and the PowerDNS base
4602 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
4603
4604 &lt;p&gt;The combined object under the machines subtree would look something
4605 like this:&lt;/p&gt;
4606
4607 &lt;blockquote&gt;&lt;pre&gt;
4608 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
4609 dc: hostname
4610 objectClass: top
4611 objectClass: dhcpHost
4612 objectclass: domainrelatedobject
4613 objectclass: dnsDomainAux
4614 associateddomain: hostname.intern
4615 arecord: 10.11.12.13
4616 dhcpHWAddress: ethernet 00:00:00:00:00:00
4617 dhcpStatements: fixed-address hostname.intern
4618 &lt;/pre&gt;&lt;/blockquote&gt;
4619
4620 &lt;/p&gt;One could even add the LTSP configuration associated with a given
4621 machine, as long as the required attributes are available in a
4622 auxiliary object class.&lt;/p&gt;
4623 </description>
4624 </item>
4625
4626 <item>
4627 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
4628 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
4629 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
4630 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
4631 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
4632 DHCP services in Debian Edu to use the same LDAP objects for a given
4633 computer, to avoid the possibility of having a inconsistent state for
4634 a computer in LDAP (as in DHCP but no DNS entry or the other way
4635 around) and make it easier to add computers to LDAP.&lt;/p&gt;
4636
4637 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
4638 information finally found a solution that seem to work.&lt;/p&gt;
4639
4640 &lt;p&gt;The old setup required three LDAP objects for a given computer.
4641 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
4642 we switch powerdns to use its strict LDAP method (ldap-method=strict
4643 in pdns-debian-edu.conf), the forward and reverse DNS entries are
4644 merged into one while making it impossible to transfer the reverse map
4645 to a slave DNS server.&lt;/p&gt;
4646
4647 &lt;p&gt;If we also replace the object class used to get the DNS related
4648 attributes to one allowing these attributes to be combined with the
4649 dhcphost object class, we can merge the DNS and DHCP entries into one.
4650 I&#39;ve written such object class in the dnsdomainaux.schema file (need
4651 proper OIDs, but that is a minor issue), and tested the setup. It
4652 seem to work.&lt;/p&gt;
4653
4654 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
4655 for both DNS and DHCP, and even the LTSP configuration I suggested in
4656 an earlier email. The combined LDAP object will look something like
4657 this:&lt;/p&gt;
4658
4659 &lt;blockquote&gt;&lt;pre&gt;
4660 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
4661 cn: hostname
4662 objectClass: dhcphost
4663 objectclass: domainrelatedobject
4664 objectclass: dnsdomainaux
4665 associateddomain: hostname.intern
4666 arecord: 10.11.12.13
4667 dhcphwaddress: ethernet 00:00:00:00:00:00
4668 dhcpstatements: fixed-address hostname
4669 ldapconfigsound: Y
4670 &lt;/pre&gt;&lt;/blockquote&gt;
4671
4672 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
4673 the DHCP server uses the dhcphwaddress and dhcpstatements entries
4674 before asking DNS to resolve the fixed-adddress. LTSP will use
4675 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
4676
4677 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
4678 dhcphost in a different location, to allow us to put the objects
4679 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
4680 that. If I can&#39;t figure out a way to do that, we can still get rid of
4681 the hosts subtree and move all its content into the DHCP Config tree
4682 (which probably should be renamed to be more related to the new
4683 content. I suspect cn=dnsdhcp,ou=services or something like that
4684 might be a good place to put it.&lt;/p&gt;
4685
4686 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
4687 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
4688 </description>
4689 </item>
4690
4691 <item>
4692 <title>Idea for storing LTSP configuration in LDAP</title>
4693 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
4694 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
4695 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
4696 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
4697 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
4698 clients, and that this can be used to fetch configuration from LDAP if
4699 Debian Edu choose to store configuration there.&lt;/p&gt;
4700
4701 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
4702 to get configuration from LDAP. The idea is to look up the MAC
4703 address of the client in LDAP, and look for attributes on the form
4704 ltspconfigsetting=value, and use this to export SETTING=value to the
4705 LTSP clients.&lt;/p&gt;
4706
4707 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
4708 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
4709 allowing us to store all information about a computer in one place.&lt;/p&gt;
4710
4711 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
4712 this approach. A real LDAP schema for the ltspClientAux objectclass
4713 need to be written. Comments, suggestions, etc?&lt;/p&gt;
4714
4715 &lt;blockquote&gt;&lt;pre&gt;
4716 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
4717 #
4718 # Fetch LTSP client settings from LDAP based on MAC address
4719 #
4720 # Uses ethernet address as stored in the dhcpHost objectclass using
4721 # the dhcpHWAddress attribute or ethernet address stored in the
4722 # ieee802Device objectclass with the macAddress attribute.
4723 #
4724 # This module is written to be schema agnostic, and only depend on the
4725 # existence of attribute names.
4726 #
4727 # The LTSP configuration variables are saved directly using a
4728 # ltspConfig prefix and uppercasing the rest of the attribute name.
4729 # To set the SERVER variable, set the ltspConfigServer attribute.
4730 #
4731 # Some LDAP schema should be created with all the relevant
4732 # configuration settings. Something like this should work:
4733 #
4734 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
4735 # SUP top
4736 # AUXILIARY
4737 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
4738
4739 LDAPSERVER=$(debian-edu-ldapserver)
4740 if [ &quot;$LDAPSERVER&quot; ] ; then
4741 LDAPBASE=$(debian-edu-ldapserver -b)
4742 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
4743 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
4744 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
4745 grep &#39;^ltspConfig&#39; | while read attr value ; do
4746 # Remove prefix and convert to upper case
4747 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
4748 # bass value on to clients
4749 eval &quot;$attr=$value; export $attr&quot;
4750 done
4751 done
4752 fi
4753 &lt;/pre&gt;&lt;/blockquote&gt;
4754
4755 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
4756 the while block might end up in a subshell causing the variables set
4757 there to not show up in ltsp-config, but if that is the case I am sure
4758 the code can be restructured to make sure the variables are passed on.
4759 I expect that can be solved with some testing. :)&lt;/p&gt;
4760
4761 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
4762 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
4763
4764 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
4765 configuration in LDAP that was created around year 2000 by
4766 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
4767 Xperience, Inc., 2000&lt;/a&gt;. I found its
4768 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
4769 personal home page over at redhat.com.&lt;/p&gt;
4770 </description>
4771 </item>
4772
4773 <item>
4774 <title>jXplorer, a very nice LDAP GUI</title>
4775 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
4776 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
4777 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
4778 <description>&lt;p&gt;Since
4779 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
4780 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
4781 LDAP GUI that is even better than luma. The java application
4782 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
4783 moving LDAP objects and subtrees using drag-and-drop, and can
4784 authenticate using Kerberos. I have only tested the Kerberos
4785 authentication, but do not have a LDAP setup allowing me to rewrite
4786 LDAP with my test user yet. It is
4787 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
4788 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
4789 have with it is how it handle errors. If something go wrong, its
4790 non-intuitive behaviour require me to go through some query work list
4791 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
4792 </description>
4793 </item>
4794
4795 <item>
4796 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
4797 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
4798 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
4799 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
4800 <description>&lt;p&gt;Here is a short update on my &lt;a
4801 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
4802 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
4803 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
4804 not reporting the status for KDE, because the upgrade crashes when
4805 aptitude try because of missing conflicts
4806 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
4807 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
4808
4809 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
4810 complete list of the installed packages. Based on this I see these
4811 differences when I did a test run today. As usual, I do not really
4812 know what the correct set of packages would be, but thought it best to
4813 publish the difference.&lt;/p&gt;
4814
4815 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4816
4817 &lt;blockquote&gt;&lt;p&gt;
4818 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
4819 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
4820 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
4821 libgtksourceview-common libpt-1.10.10-plugins-alsa
4822 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
4823 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
4824 python-4suite-xml python-eggtrayicon python-gtkhtml2
4825 python-gtkmozembed svgalibg1 xserver-xephyr zip
4826 &lt;/p&gt;&lt;/blockquote&gt;
4827
4828 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4829
4830 &lt;blockquote&gt;&lt;p&gt;
4831 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
4832 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
4833 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
4834 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
4835 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
4836 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
4837 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
4838 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
4839 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
4840 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
4841 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
4842 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
4843 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
4844 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
4845 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
4846 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
4847 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
4848 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
4849 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
4850 mysql-common swfdec-gnome totem-gstreamer wodim
4851 &lt;/p&gt;&lt;/blockquote&gt;
4852
4853 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4854
4855 &lt;blockquote&gt;&lt;p&gt;
4856 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
4857 python-gnomekeyring python-wnck rhythmbox-plugins xorg
4858 xserver-xorg-input-all xserver-xorg-input-evdev
4859 xserver-xorg-input-kbd xserver-xorg-input-mouse
4860 xserver-xorg-input-synaptics xserver-xorg-video-all
4861 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
4862 xserver-xorg-video-chips xserver-xorg-video-cirrus
4863 xserver-xorg-video-dummy xserver-xorg-video-fbdev
4864 xserver-xorg-video-glint xserver-xorg-video-i128
4865 xserver-xorg-video-i740 xserver-xorg-video-mach64
4866 xserver-xorg-video-mga xserver-xorg-video-neomagic
4867 xserver-xorg-video-nouveau xserver-xorg-video-nv
4868 xserver-xorg-video-r128 xserver-xorg-video-radeon
4869 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
4870 xserver-xorg-video-s3 xserver-xorg-video-s3virge
4871 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
4872 xserver-xorg-video-sis xserver-xorg-video-sisusb
4873 xserver-xorg-video-tdfx xserver-xorg-video-tga
4874 xserver-xorg-video-trident xserver-xorg-video-tseng
4875 xserver-xorg-video-vesa xserver-xorg-video-vmware
4876 xserver-xorg-video-voodoo
4877 &lt;/p&gt;&lt;/blockquote&gt;
4878
4879 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4880
4881 &lt;blockquote&gt;&lt;p&gt;
4882 deskbar-applet xserver-xorg xserver-xorg-core
4883 xserver-xorg-input-wacom xserver-xorg-video-intel
4884 xserver-xorg-video-openchrome
4885 &lt;/p&gt;&lt;/blockquote&gt;
4886
4887 &lt;p&gt;I was told on IRC that the xorg-xserver package was
4888 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
4889 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
4890 No idea when it hits Squeeze, but when it does I hope it will reduce
4891 the difference somewhat.
4892 </description>
4893 </item>
4894
4895 <item>
4896 <title>LUMA, a very nice LDAP GUI</title>
4897 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
4898 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
4899 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
4900 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
4901 directory in Debian Edu, and in the process I started to miss a GUI
4902 tool to browse the LDAP tree. The only one I was able to find in
4903 Debian/Squeeze and Lenny is
4904 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
4905 be a great tool to get a overview of the current LDAP directory
4906 populated by default in Skolelinux. Thanks to it, I have been able to
4907 find empty and obsolete subtrees, misplaced objects and duplicate
4908 objects. It will be installed by default in Debian/Squeeze. If you
4909 are working with LDAP, give it a go. :)&lt;/p&gt;
4910
4911 &lt;p&gt;I did notice one problem with it I have not had time to report to
4912 the BTS yet. There is no .desktop file in the package, so the tool do
4913 not show up in the Gnome and KDE menus, but only deep down in in the
4914 Debian submenu in KDE. I hope that can be fixed before Squeeze is
4915 released.&lt;/p&gt;
4916
4917 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
4918 like to move objects and remove subtrees directly in the GUI, but have
4919 not found a way to do that with LUMA yet. So in the mean time, I use
4920 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
4921
4922 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
4923 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
4924
4925 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
4926 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
4927 useful GUI alternative. It seem like a good tool, but is unmaintained
4928 in Debian and got a RC bug keeping it out of Squeeze. Unless that
4929 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
4930 </description>
4931 </item>
4932
4933 <item>
4934 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
4935 <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>
4936 <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>
4937 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
4938 <description>&lt;p&gt;A while back, I
4939 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
4940 about the fact&lt;/a&gt; that it is not possible with the provided schemas
4941 for storing DNS and DHCP information in LDAP to combine the two sets
4942 of information into one LDAP object representing a computer.&lt;/p&gt;
4943
4944 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
4945 the dhcpHost object class auxiliary, to allow it to be combined with
4946 the dNSDomain object class, and thus forming one object for one
4947 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
4948
4949 &lt;p&gt;If I understand this correctly, it is not safe to do this change
4950 without also changing the assigned number for the object class, and I
4951 do not know enough about LDAP schema design to do that properly for
4952 Debian Edu.&lt;/p&gt;
4953
4954 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
4955 the
4956 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
4957 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
4958 available today from IETF.&lt;/p&gt;
4959
4960 &lt;pre&gt;
4961 --- dhcp.schema (revision 65192)
4962 +++ dhcp.schema (working copy)
4963 @@ -376,7 +376,7 @@
4964 objectclass ( 2.16.840.1.113719.1.203.6.6
4965 NAME &#39;dhcpHost&#39;
4966 DESC &#39;This represents information about a particular client&#39;
4967 - SUP top
4968 + SUP top AUXILIARY
4969 MUST cn
4970 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
4971 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
4972 &lt;/pre&gt;
4973
4974 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
4975 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
4976 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
4977
4978 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
4979 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
4980 </description>
4981 </item>
4982
4983 <item>
4984 <title>Calling tasksel like the installer, while still getting useful output</title>
4985 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
4986 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
4987 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
4988 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
4989 installs packages during the normal debian-installer run. Until now,
4990 I have ended up letting tasksel do the work, with the annoying problem
4991 of not getting any feedback at all when something fails (like a
4992 conffile question from dpkg or a download that fails), using code like
4993 this:
4994
4995 &lt;blockquote&gt;&lt;pre&gt;
4996 export DEBIAN_FRONTEND=noninteractive
4997 tasksel --new-install
4998 &lt;/pre&gt;&lt;/blockquote&gt;
4999
5000 This would invoke tasksel, let its automatic task selection pick the
5001 tasks to install, and continue to install the requested tasks without
5002 any output what so ever.
5003
5004 Recently I revisited this problem while working on the automatic
5005 package upgrade testing, because tasksel would some times hang without
5006 any useful feedback, and I want to see what is going on when it
5007 happen. Then it occured to me, I can parse the output from tasksel
5008 when asked to run in test mode, and use that aptitude command line
5009 printed by tasksel then to simulate the tasksel run. I ended up using
5010 code like this:
5011
5012 &lt;blockquote&gt;&lt;pre&gt;
5013 export DEBIAN_FRONTEND=noninteractive
5014 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
5015 $cmd
5016 &lt;/pre&gt;&lt;/blockquote&gt;
5017
5018 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
5019 --without-recommends -o APT::Install-Recommends=no -y install
5020 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
5021 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
5022 laptop task and all packages with priority standard , required and
5023 important, just like tasksel would have done it during
5024 installation.&lt;/p&gt;
5025
5026 &lt;p&gt;A better approach is probably to extend tasksel to be able to
5027 install packages without using debconf-apt-progress, for use cases
5028 like this.&lt;/p&gt;
5029 </description>
5030 </item>
5031
5032 <item>
5033 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
5034 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
5035 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
5036 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
5037 <description>&lt;p&gt;My
5038 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
5039 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
5040 finally made the upgrade logs available from
5041 &lt;a href=&quot;http://people.skolelinux.org/pere/debian-upgrade-testing/&quot;&gt;http://people.skolelinux.org/pere/debian-upgrade-testing/&lt;/a&gt;.
5042 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
5043 apt and aptitude, and found their differences interesting. This time
5044 I will only focus on their removal plans.&lt;/p&gt;
5045
5046 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
5047 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
5048 surprising part is that it want to remove xorg and all
5049 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
5050 sure why. When asking aptitude to do the same, it want to remove 129
5051 packages, but most of them are library packages I suspect are no
5052 longer needed. Both of them want to remove bluetooth packages, which
5053 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
5054
5055 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
5056 which seem like a bad idea and xorg the same way as with Gnome. Asking
5057 aptitude for the same, it wants to remove 192 packages, none which are
5058 too surprising.&lt;/p&gt;
5059
5060 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
5061 and avoided, and perhaps others as well. Here are the complete list
5062 of planned removals. The complete logs is available from the URL
5063 above. Note if you want to repeat these tests, that the upgrade test
5064 for kde+apt-get hung in the tasksel setup because of dpkg asking
5065 conffile questions. No idea why. I worked around it by using
5066 &#39;&lt;tt&gt;echo &gt;&gt; /proc/&lt;em&gt;pidofdpkg&lt;/em&gt;/fd/0&lt;/tt&gt;&#39; to tell dpkg to
5067 continue.&lt;/p&gt;
5068
5069 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
5070 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
5071 gnome-desktop-environment gnome-network-admin gtkhtml3.14
5072 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
5073 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
5074 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
5075 serpentine swfdec-mozilla update-manager xorg xserver-xorg
5076 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
5077 xserver-xorg-input-kbd xserver-xorg-input-mouse
5078 xserver-xorg-input-synaptics xserver-xorg-input-wacom
5079 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
5080 xserver-xorg-video-ati xserver-xorg-video-chips
5081 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
5082 xserver-xorg-video-dummy xserver-xorg-video-fbdev
5083 xserver-xorg-video-glint xserver-xorg-video-i128
5084 xserver-xorg-video-i740 xserver-xorg-video-imstt
5085 xserver-xorg-video-intel xserver-xorg-video-mach64
5086 xserver-xorg-video-mga xserver-xorg-video-neomagic
5087 xserver-xorg-video-nsc xserver-xorg-video-nv
5088 xserver-xorg-video-openchrome xserver-xorg-video-r128
5089 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
5090 xserver-xorg-video-rendition xserver-xorg-video-s3
5091 xserver-xorg-video-s3virge xserver-xorg-video-savage
5092 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
5093 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
5094 xserver-xorg-video-tga xserver-xorg-video-trident
5095 xserver-xorg-video-tseng xserver-xorg-video-v4l
5096 xserver-xorg-video-vesa xserver-xorg-video-vga
5097 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
5098 xulrunner-1.9-gnome-support&lt;/p&gt;
5099
5100 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
5101
5102 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
5103 djvulibre-desktop finger gnome-app-install gnome-mount
5104 gnome-network-admin gnome-spell gnome-vfs-obexftp
5105 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
5106 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
5107 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
5108 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
5109 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
5110 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
5111 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
5112 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
5113 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
5114 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
5115 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
5116 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
5117 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
5118 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
5119 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
5120 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
5121 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
5122 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
5123 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
5124 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
5125 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
5126 openoffice.org-writer2latex openssl-blacklist p7zip
5127 python-4suite-xml python-eggtrayicon python-gnome2-desktop
5128 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
5129 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
5130 swfdec-mozilla totem-gstreamer update-manager wodim
5131 xserver-xorg-video-cyrix xserver-xorg-video-imstt
5132 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
5133 zip&lt;/p&gt;
5134
5135 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
5136
5137 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
5138 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
5139 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
5140 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
5141 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
5142 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
5143 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
5144 xserver-xorg-input-kbd xserver-xorg-input-mouse
5145 xserver-xorg-input-synaptics xserver-xorg-input-wacom
5146 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
5147 xserver-xorg-video-ati xserver-xorg-video-chips
5148 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
5149 xserver-xorg-video-dummy xserver-xorg-video-fbdev
5150 xserver-xorg-video-glint xserver-xorg-video-i128
5151 xserver-xorg-video-i740 xserver-xorg-video-imstt
5152 xserver-xorg-video-intel xserver-xorg-video-mach64
5153 xserver-xorg-video-mga xserver-xorg-video-neomagic
5154 xserver-xorg-video-nsc xserver-xorg-video-nv
5155 xserver-xorg-video-openchrome xserver-xorg-video-r128
5156 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
5157 xserver-xorg-video-rendition xserver-xorg-video-s3
5158 xserver-xorg-video-s3virge xserver-xorg-video-savage
5159 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
5160 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
5161 xserver-xorg-video-tga xserver-xorg-video-trident
5162 xserver-xorg-video-tseng xserver-xorg-video-v4l
5163 xserver-xorg-video-vesa xserver-xorg-video-vga
5164 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
5165
5166 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
5167 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
5168 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
5169 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
5170 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
5171 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5172 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
5173 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
5174 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5175 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
5176 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
5177 kghostview khelpcenter khexedit kiconedit kitchensync klatin
5178 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
5179 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
5180 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
5181 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
5182 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
5183 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
5184 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5185 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
5186 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
5187 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5188 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
5189 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
5190 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
5191 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5192 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
5193 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
5194 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
5195 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
5196 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
5197 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
5198 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
5199 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
5200 texlive-common texlive-doc-base texlive-fonts-recommended
5201 xserver-xorg-video-cyrix xserver-xorg-video-imstt
5202 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
5203 xulrunner-1.9&lt;/p&gt;
5204
5205 </description>
5206 </item>
5207
5208 <item>
5209 <title>Automatic upgrade testing from Lenny to Squeeze</title>
5210 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
5211 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
5212 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
5213 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
5214 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
5215 have been discovered and reported in the process
5216 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
5217 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
5218 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
5219 kdebase-workspace-data), and to get a more regular testing going on, I
5220 am working on a script to automate the test.&lt;/p&gt;
5221
5222 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
5223 Gnome or KDE desktop installation inside the chroot before upgrading
5224 it. To ensure no services are started in the chroot, a policy-rc.d
5225 script is inserted. To make sure tasksel believe it is to install a
5226 desktop on a laptop, the tasksel tests are replaced in the chroot
5227 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
5228
5229 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
5230 currently always fail because udev refuses to upgrade with the kernel
5231 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
5232 is created. The bug report
5233 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
5234 this problem do not trigger in a chroot, but I touch the file anyway
5235 to make sure the upgrade go well. Testing on virtual and real
5236 hardware have failed me because of udev so far, and creating this file
5237 do the trick in such settings anyway. This is a
5238 &lt;a href=&quot;http://www.linuxquestions.org/questions/debian-26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-804130/&quot;&gt;known
5239 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
5240 maintainer because he lack the resources to rewrite udev to keep
5241 working with old kernels or something like that. I really wish the
5242 udev upstream would keep udev backwards compatible, to avoid such
5243 upgrade problem, but given that they fail to do so, I guess
5244 documenting the way out of this mess is the best option we got for
5245 Debian Squeeze.&lt;/p&gt;
5246
5247 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
5248 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
5249 trick:&lt;/p&gt;
5250
5251 &lt;blockquote&gt;&lt;pre&gt;
5252 #!/bin/sh
5253 set -ex
5254
5255 if [ &quot;$1&quot; ] ; then
5256 desktop=$1
5257 else
5258 desktop=gnome
5259 fi
5260
5261 from=lenny
5262 to=squeeze
5263
5264 exec &amp;lt; /dev/null
5265 unset LANG
5266 mirror=http://ftp.skolelinux.org/debian
5267 tmpdir=chroot-$from-upgrade-$to-$desktop
5268 fuser -mv .
5269 debootstrap $from $tmpdir $mirror
5270 chroot $tmpdir aptitude update
5271 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
5272 #!/bin/sh
5273 exit 101
5274 EOF
5275 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
5276 exit_cleanup() {
5277 umount $tmpdir/proc
5278 }
5279 mount -t proc proc $tmpdir/proc
5280 # Make sure proc is unmounted also on failure
5281 trap exit_cleanup EXIT INT
5282
5283 chroot $tmpdir aptitude -y install debconf-utils
5284
5285 # Make sure tasksel autoselection trigger. It need the test scripts
5286 # to return the correct answers.
5287 echo tasksel tasksel/desktop multiselect $desktop | \
5288 chroot $tmpdir debconf-set-selections
5289
5290 # Include the desktop and laptop task
5291 for test in desktop laptop ; do
5292 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
5293 #!/bin/sh
5294 exit 2
5295 EOF
5296 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
5297 done
5298
5299 DEBIAN_FRONTEND=noninteractive
5300 DEBIAN_PRIORITY=critical
5301 export DEBIAN_FRONTEND DEBIAN_PRIORITY
5302 chroot $tmpdir tasksel --new-install
5303
5304 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
5305 chroot $tmpdir aptitude update
5306 touch $tmpdir/etc/udev/kernel-upgrade
5307 chroot $tmpdir aptitude -y dist-upgrade
5308 fuser -mv
5309 &lt;/pre&gt;&lt;/blockquote&gt;
5310
5311 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
5312 with aptitude, but I have not had time to look at how they behave
5313 differently so far. I hope to get a cron job running to do the test
5314 regularly and post the result on the web. The Gnome upgrade currently
5315 work, while the KDE upgrade fail because of the bug in
5316 kdebase-workspace-data&lt;/p&gt;
5317
5318 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
5319 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
5320 post, so I will refrain from trying. I can report that for Gnome,
5321 aptitude report 760 packages upgraded, 448 newly installed, 129 to
5322 remove and 1 not upgraded and 1024MB need to be downloaded while for
5323 KDE the same numbers are 702 packages upgraded, 507 newly installed,
5324 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
5325
5326 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
5327 is able to migrate to dependency based boot sequencing and parallel
5328 booting without a hitch. Was unsure if there were still bugs with
5329 packages failing to clean up their obsolete init.d script during
5330 upgrades, and no such problem seem to affect the Gnome desktop+laptop
5331 packages.&lt;/p&gt;
5332 </description>
5333 </item>
5334
5335 <item>
5336 <title>Upstart or sysvinit - as init.d scripts see it</title>
5337 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
5338 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
5339 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
5340 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
5341 scripts to migrate (some of) their operations to upstart job while
5342 keeping the init.d for hurd and kfreebsd. The packages with such
5343 needs will need a way to get their init.d scripts to behave
5344 differently when used with sysvinit and with upstart. Because of
5345 this, I had a look at the environment variables set when a init.d
5346 script is running under upstart, and when it is not.&lt;/p&gt;
5347
5348 &lt;p&gt;With upstart, I notice these environment variables are set when a
5349 script is started from rcS.d/ (ignoring some irrelevant ones like
5350 COLUMNS):&lt;/p&gt;
5351
5352 &lt;blockquote&gt;&lt;pre&gt;
5353 DEFAULT_RUNLEVEL=2
5354 previous=N
5355 PREVLEVEL=
5356 RUNLEVEL=
5357 runlevel=S
5358 UPSTART_EVENTS=startup
5359 UPSTART_INSTANCE=
5360 UPSTART_JOB=rc-sysinit
5361 &lt;/pre&gt;&lt;/blockquote&gt;
5362
5363 &lt;p&gt;With sysvinit, these environment variables are set for the same
5364 script.&lt;/p&gt;
5365
5366 &lt;blockquote&gt;&lt;pre&gt;
5367 INIT_VERSION=sysvinit-2.88
5368 previous=N
5369 PREVLEVEL=N
5370 RUNLEVEL=S
5371 runlevel=S
5372 &lt;/pre&gt;&lt;/blockquote&gt;
5373
5374 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
5375 sysvinit are not set by upstart. Not sure if it is intentional or not
5376 to not be compatible with sysvinit in this regard.&lt;/p&gt;
5377
5378 &lt;p&gt;For scripts needing to behave differently when upstart is used,
5379 looking for the UPSTART_JOB environment variable seem to be a good
5380 choice.&lt;/p&gt;
5381 </description>
5382 </item>
5383
5384 <item>
5385 <title>A manual for standards wars...</title>
5386 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
5387 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
5388 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
5389 <description>&lt;p&gt;Via the
5390 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
5391 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
5392 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
5393 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
5394 following the standards wars of today.&lt;/p&gt;
5395 </description>
5396 </item>
5397
5398 <item>
5399 <title>Sitesummary tip: Listing computer hardware models used at site</title>
5400 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
5401 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
5402 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
5403 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
5404 to get a list of the machine types in use thanks to the DMI
5405 information extracted from each machine. The script to do so is
5406 included in the sitesummary package, and here is example output from
5407 the Skolelinux build servers:&lt;/p&gt;
5408
5409 &lt;blockquote&gt;&lt;pre&gt;
5410 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
5411 vendor count
5412 Dell Computer Corporation 1
5413 PowerEdge 1750 1
5414 IBM 1
5415 eserver xSeries 345 -[8670M1X]- 1
5416 Intel 2
5417 [no-dmi-info] 3
5418 maintainer:~#
5419 &lt;/pre&gt;&lt;/blockquote&gt;
5420
5421 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
5422 provided in each machine. Here there are Intel machines without model
5423 information listed with Intel as vendor and no model, and virtual Xen
5424 machines listed as [no-dmi-info]. One can add -l as a command line
5425 option to list the individual machines.&lt;/p&gt;
5426
5427 &lt;p&gt;A larger list is
5428 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
5429 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
5430 provide the basic sitesummary report publicly. In their report there
5431 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
5432 their machines, and as sitesummary is available in both distributions,
5433 it is trivial to get all of them to report to the same central
5434 collector.&lt;/p&gt;
5435 </description>
5436 </item>
5437
5438 <item>
5439 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
5440 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
5441 <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>
5442 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
5443 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
5444 start at boot when an NVidia video card is used is handled. The
5445 problem seem to be that the nvidia X.org driver uses a long time to
5446 initialize, and this duration is longer than kdm is configured to
5447 wait.&lt;/p&gt;
5448
5449 &lt;p&gt;I came across two bugs related to this issue,
5450 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
5451 against initscripts and passed on to nvidia-glx when it became obvious
5452 that the nvidia drivers were involved, and
5453 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
5454 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
5455
5456 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
5457 problem nvidia video card owners experience and make sure the Debian
5458 distribution work out of the box for these users. The nvidia driver
5459 maintainers expect kdm to be set up to wait longer, while kdm expect
5460 the nvidia driver maintainers to fix the driver to start faster, and
5461 while they wait for each other I guess the users end up switching to a
5462 distribution that work for them. I have no idea what the solution is,
5463 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
5464
5465 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
5466 </description>
5467 </item>
5468
5469 <item>
5470 <title>Parallellized boot seem to hold up well in Debian/testing</title>
5471 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
5472 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
5473 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
5474 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
5475 The feature seem to hold up pretty well, but three fairly serious
5476 issues are known and should be solved:
5477
5478 &lt;p&gt;&lt;ul&gt;
5479
5480 &lt;li&gt;The wicd package seen to
5481 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
5482 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
5483 parallel booting is enabled. No idea why, but the wicd maintainer
5484 seem to be on the case.&lt;/li&gt;
5485
5486 &lt;li&gt;The nvidia X driver seem to
5487 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
5488 triggered more easily when parallel booting is in effect. The
5489 maintainer is on the case.&lt;/li&gt;
5490
5491 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
5492 sequencing (the shutdown is broken) when old file-rc users
5493 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
5494 sysv-rc. One way to solve it would be for file-rc to create
5495 /etc/init.d/.legacy-bootordering, and another is to try to make
5496 sysv-rc more robust. Will investigate some more and probably upload a
5497 workaround in sysv-rc to help those trying to move from file-rc to
5498 sysv-rc get a working shutdown.&lt;/li&gt;
5499
5500 &lt;/ul&gt;&lt;/p&gt;
5501
5502 &lt;p&gt;All in all not many surprising issues, and all of them seem
5503 solvable before Squeeze is released. In addition to these there are
5504 some packages with bugs in their dependencies and run level settings,
5505 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
5506
5507 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
5508 the BTS, please usertag the report to get it to show up at
5509 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
5510 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
5511
5512 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
5513 </description>
5514 </item>
5515
5516 <item>
5517 <title>More flexible firmware handling in debian-installer</title>
5518 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
5519 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
5520 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
5521 <description>&lt;p&gt;After a long break from debian-installer development, I finally
5522 found time today to return to the project. Having to spend less time
5523 working dependency based boot in debian, as it is almost complete now,
5524 definitely helped freeing some time.&lt;/p&gt;
5525
5526 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
5527 include some firmware packages on the Debian Edu CDs, those needed to
5528 get disk and network controllers working. Without having these
5529 firmware packages available during installation, it is impossible to
5530 install Debian Edu on the given machine, and because our target group
5531 are non-technical people, asking them to provide firmware packages on
5532 an external medium is a support pain. Initially, I expected it to be
5533 enough to include the firmware packages on the CD to get
5534 debian-installer to find and use them. This proved to be wrong.
5535 Next, I hoped it was enough to symlink the relevant firmware packages
5536 to some useful location on the CD (tried /cdrom/ and
5537 /cdrom/firmware/). This also proved to not work, and at this point I
5538 found time to look at the debian-installer code to figure out what was
5539 going to work.&lt;/p&gt;
5540
5541 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
5542 look revealed that it would only look for firmware packages outside
5543 the installation media, so the CD was never checked for firmware
5544 packages. It would only check USB sticks, floppies and other
5545 &quot;external&quot; media devices. Today I changed it to also look in the
5546 /cdrom/firmware/ directory on the mounted CD or DVD, which should
5547 solve the problem I ran into with Debian edu. I also changed it to
5548 look in /firmware/, to make sure the installer also find firmware
5549 provided in the initrd when booting the installer via PXE, to allow us
5550 to provide the same feature in the PXE setup included in Debian
5551 Edu.&lt;/p&gt;
5552
5553 &lt;p&gt;To make sure firmware deb packages with a license questions are not
5554 activated without asking if the license is accepted, I extended
5555 hw-detect to look for preinst scripts in the firmware packages, and
5556 run these before activating the firmware during installation. The
5557 license question is asked using debconf in the preinst, so this should
5558 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
5559
5560 &lt;p&gt;If you want to discuss the details of these features, please
5561 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
5562 </description>
5563 </item>
5564
5565 <item>
5566 <title>Parallellized boot is now the default in Debian/unstable</title>
5567 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
5568 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
5569 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
5570 <description>&lt;p&gt;Since this evening, parallel booting is the default in
5571 Debian/unstable for machines using dependency based boot sequencing.
5572 Apparently the testing of concurrent booting has been wider than
5573 expected, if I am to believe the
5574 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
5575 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
5576 with the feature this weekend, to give us some time to detect any
5577 remaining problems before Squeeze is frozen. If serious problems are
5578 detected, it is simple to change the default back to sequential boot.
5579 The upload of the new sysvinit package also activate a new upstream
5580 version.&lt;/p&gt;
5581
5582 More information about
5583 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
5584 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
5585 currently possible to disable parallel booting when one run into
5586 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
5587
5588 &lt;blockquote&gt;&lt;pre&gt;
5589 CONCURRENCY=none
5590 &lt;/pre&gt;&lt;/blockquote&gt;
5591
5592 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
5593 the BTS, please usertag the report to get it to show up at
5594 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
5595 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
5596 </description>
5597 </item>
5598
5599 <item>
5600 <title>Sitesummary tip: Listing MAC address of all clients</title>
5601 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
5602 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
5603 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
5604 <description>&lt;p&gt;In the recent Debian Edu versions, the
5605 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
5606 system&lt;/a&gt; is used to keep track of the machines in the school
5607 network. Each machine will automatically report its status to the
5608 central server after boot and once per night. The network setup is
5609 also reported, and using this information it is possible to get the
5610 MAC address of all network interfaces in the machines. This is useful
5611 to update the DHCP configuration.&lt;/p&gt;
5612
5613 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
5614 ist all MAC addresses of all machines reporting to sitesummary. Run
5615 this on the collector host:&lt;/p&gt;
5616
5617 &lt;blockquote&gt;&lt;pre&gt;
5618 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
5619 &lt;/pre&gt;&lt;/blockquote&gt;
5620
5621 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
5622 line per machine and with space between the MAC addresses.&lt;/p&gt;
5623
5624 &lt;p&gt;To allow system administrators easier job at adding static DHCP
5625 addresses for hosts, it would be possible to extend this to fetch
5626 machine information from sitesummary and update the DHCP and DNS
5627 tables in LDAP using this information. Such tool is unfortunately not
5628 written yet.&lt;/p&gt;
5629 </description>
5630 </item>
5631
5632 <item>
5633 <title>systemd, an interesting alternative to upstart</title>
5634 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
5635 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
5636 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
5637 <description>&lt;p&gt;The last few days a new boot system called
5638 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
5639 has been
5640 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
5641
5642 to the free software world. I have not yet had time to play around
5643 with it, but it seem to be a very interesting alternative to
5644 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
5645 a good alternative for Debian when we are able to switch to an event
5646 based boot system. Tollef is
5647 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
5648 systemd into Debian, and I look forward to seeing how well it work. I
5649 like the fact that systemd handles init.d scripts with dependency
5650 information natively, allowing them to run in parallel where upstart
5651 at the moment do not.&lt;/p&gt;
5652
5653 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
5654 platform support. It only work on recent Linux kernels, and also need
5655 some new kernel features enabled to function properly. This means
5656 kFreeBSD and Hurd ports of Debian will need a port or a different boot
5657 system. Not sure how that will be handled if systemd proves to be the
5658 way forward.&lt;/p&gt;
5659
5660 &lt;p&gt;In the mean time, based on the
5661 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
5662 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
5663 decided to enable full parallel booting as the default in Debian as
5664 soon as possible (probably this weekend or early next week), to see if
5665 there are any remaining serious bugs in the init.d dependencies. A
5666 new version of the sysvinit package implementing this change is
5667 already in experimental. If all go well, Squeeze will be released
5668 with parallel booting enabled by default.&lt;/p&gt;
5669 </description>
5670 </item>
5671
5672 <item>
5673 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
5674 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
5675 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
5676 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
5677 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
5678 complete, so complete that it is actually possible to run all the
5679 init.d scripts in parallell based on these dependencies. If you want
5680 to test your Squeeze system, make sure
5681 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
5682 based boot sequencing&lt;/a&gt; is enabled, and add this line to
5683 /etc/default/rcS:&lt;/p&gt;
5684
5685 &lt;blockquote&gt;&lt;pre&gt;
5686 CONCURRENCY=makefile
5687 &lt;/pre&gt;&lt;/blockquote&gt;
5688
5689 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
5690 scripts in parallel using the dependency information stored in
5691 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
5692 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
5693 to try to start the kdm and gdm scripts as early as possible, and will
5694 start the facilities required by kdm or gdm as early as possible to
5695 make this happen.&lt;/p&gt;
5696
5697 &lt;p&gt;Give it a try, and see if you like the result. If some services
5698 fail to start properly, it is most likely because they have incomplete
5699 init.d script dependencies in their startup script (or some of their
5700 dependent scripts have incomplete dependencies). Report bugs and get
5701 the package maintainers to fix it. :)&lt;/p&gt;
5702
5703 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
5704 manage to get the init.d script dependencies complete and correct. I
5705 expect we will get there in Squeeze+1, if we get manage to test and
5706 fix the remaining issues.&lt;/p&gt;
5707
5708 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
5709 the BTS, please usertag the report to get it to show up at
5710 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
5711 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
5712 </description>
5713 </item>
5714
5715 <item>
5716 <title>Debian has switched to dependency based boot sequencing</title>
5717 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
5718 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
5719 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
5720 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
5721 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
5722 have been migrated to using dependency based boot sequencing. This
5723 conclude work me and others have been doing for the last three days.
5724 It feels great to see this finally part of the default Debian
5725 installation. Now we just need to weed out the last few problems that
5726 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
5727
5728 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
5729 fixing the more fundamental problem of handing the event based
5730 non-predictable kernel in the early boot.&lt;/p&gt;
5731 </description>
5732 </item>
5733
5734 <item>
5735 <title>Taking over sysvinit development</title>
5736 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
5737 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
5738 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
5739 <description>&lt;p&gt;After several years of frustration with the lack of activity from
5740 the existing sysvinit upstream developer, I decided a few weeks ago to
5741 take over the package and become the new upstream. The number of
5742 patches to track for the Debian package was becoming a burden, and the
5743 lack of synchronization between the distribution made it hard to keep
5744 the package up to date.&lt;/p&gt;
5745
5746 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
5747 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
5748 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
5749 and Fedora), based on the patches currently in use in these
5750 distributions. We Debian maintainers plan to move to this tarball as
5751 the new upstream as soon as we find time to do the merge. Since the
5752 new tarball was created, we agreed with Werner at SuSe to make a new
5753 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
5754 development there. The project is registered and currently waiting
5755 for approval by the Savannah administrators, and as soon as it is
5756 approved, we will import the old versions from svn and continue
5757 working on the future release.&lt;/p&gt;
5758
5759 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
5760 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
5761 </description>
5762 </item>
5763
5764 <item>
5765 <title>Debian boots quicker and quicker</title>
5766 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
5767 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
5768 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
5769 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
5770 people involved in the boot system on Debian and Ubuntu, to see if we
5771 could find more ways to speed up the boot system. This was an Ubuntu
5772 funded
5773 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
5774 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
5775 of boot systems, and ways to handle the increasing number of boot
5776 issues introduced by the Linux kernel becoming more and more
5777 asynchronous and event base. The Ubuntu approach using udev and
5778 upstart might be a good way forward. Time will show.&lt;/p&gt;
5779
5780 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
5781 process in Debian. All of these should be applied to get a quick
5782 boot:&lt;/p&gt;
5783
5784 &lt;ul&gt;
5785
5786 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
5787
5788 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
5789 clock is in UTC.&lt;/li&gt;
5790
5791 &lt;li&gt;Install and activate the insserv package to enable
5792 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
5793 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
5794
5795 &lt;/ul&gt;
5796
5797 These points are based on the Google summer of code work done by
5798 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
5799 Villegas&lt;/a&gt;.
5800
5801 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
5802 unstable yesterday. When we tested it, we were able to cut 6 seconds
5803 from the boot sequence. It depend on very correct dependency
5804 declaration in all init.d scripts, so I expect us to find edge cases
5805 where the dependences in some scripts are slightly wrong when we start
5806 using this.&lt;/p&gt;
5807
5808 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
5809 introduced by Raphael Geissert today, one that could affect the
5810 startup speed as well. Instead of starting some scripts concurrently
5811 from rcS.d/ and another set of scripts from rc2.d/, it would be
5812 possible to run a of them in the same process. A quick way to test
5813 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
5814 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
5815 </description>
5816 </item>
5817
5818 <item>
5819 <title>BSAs påstander om piratkopiering møter motstand</title>
5820 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
5821 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
5822 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
5823 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
5824 programvareselskapene som Microsoft og Apple, publisert en rapport der
5825 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
5826 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
5827 dager siden kom
5828 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
5829 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
5830 dagene. Et spesielt interessant kommentar fra Sverige,
5831 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
5832 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
5833
5834 &lt;blockquote&gt;
5835 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
5836 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
5837 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
5838 exakta&quot;, säger BSAs Sverigechef John Hugosson.
5839 &lt;/blockquote&gt;
5840
5841 &lt;p&gt;Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er &lt;a
5842 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
5843 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
5844 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
5845 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
5846
5847 &lt;p&gt;Fant lenkene via &lt;a
5848 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
5849 på Slashdot&lt;/a&gt;.&lt;/p&gt;
5850 </description>
5851 </item>
5852
5853 <item>
5854 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
5855 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
5856 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
5857 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
5858 <description>&lt;p&gt;Kom over
5859 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
5860 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
5861 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
5862 jobber til daglig. En rask opptelling forteller meg at vi har 490
5863 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
5864 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
5865 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
5866 </description>
5867 </item>
5868
5869 <item>
5870 <title>Kryptert harddisk - naturligvis</title>
5871 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
5872 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
5873 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
5874 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
5875 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
5876 når en tar tap av arbeidstid, fortrolige dokumenter,
5877 personopplysninger og alt annet det innebærer. Det er ingen tvil om
5878 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
5879 til at jeg har kryptert harddisken på både kontormaskinen og min
5880 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
5881 komme på avveie, den første informasjon relatert til jobben min ved
5882 Universitetet i Oslo, og den andre relatert til blant annet
5883 foreningsarbeide. Kryptering av diskene gjør at det er lite
5884 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
5885 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
5886 og en reboot vil gjøre at de ber om passord før de vil starte opp.
5887 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
5888 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
5889 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
5890 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
5891 det er gjort slik jeg gjør det er minimale, og gevinstene er
5892 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
5893 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
5894
5895 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
5896 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
5897 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
5898 er for min del høyere enn gevinsten. Jeg tror oddsene for at
5899 f.eks. etteretningsorganisasjoner har glede av å titte på mine
5900 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
5901 gjøre det vanskeligere for angripere med kompetanse og ressurser er
5902 betydelige.&lt;/p&gt;
5903 </description>
5904 </item>
5905
5906 <item>
5907 <title>Two projects that have improved the quality of free software a lot</title>
5908 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
5909 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
5910 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
5911 <description>&lt;p&gt;There are two software projects that have had huge influence on the
5912 quality of free software, and I wanted to mention both in case someone
5913 do not yet know them.&lt;/p&gt;
5914
5915 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
5916 tool to detect and expose errors in the memory handling of programs.
5917 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
5918 and it will report any problems on stdout. It is even better if the
5919 program include debug information. With debug information, it is able
5920 to report the source file name and line number where the problem
5921 occurs. It can report things like &#39;reading past memory block in file
5922 X line N, the memory block was allocated in file Y, line M&#39;, and
5923 &#39;using uninitialised value in control logic&#39;. This tool has made it
5924 trivial to investigate reproducible crash bugs in programs, and have
5925 reduced the number of this kind of bugs in free software a lot.
5926
5927 &lt;p&gt;The second one is
5928 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
5929 a source code checker. It is able to process the source of a program
5930 and find problems in the logic without running the program. It
5931 started out as the Stanford Checker and became well known when it was
5932 used to find bugs in the Linux kernel. It is now a commercial tool
5933 and the company behind it is running
5934 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
5935 free software community, where a lot of free software projects get
5936 their source checked for free. Several thousand defects have been
5937 found and fixed so far. It can find errors like &#39;lock L taken in file
5938 X line N is never released if exiting in line M&#39;, or &#39;the code in file
5939 Y lines O to P can never be executed&#39;. The projects included in the
5940 community service project have managed to get rid of a lot of
5941 reliability problems thanks to Coverity.&lt;/p&gt;
5942
5943 &lt;p&gt;I believe tools like this, that are able to automatically find
5944 errors in the source, are vital to improve the quality of software and
5945 make sure we can get rid of the crashing and failing software we are
5946 surrounded by today.&lt;/p&gt;
5947 </description>
5948 </item>
5949
5950 <item>
5951 <title>No patch is not better than a useless patch</title>
5952 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
5953 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
5954 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
5955 <description>&lt;p&gt;Julien Blache
5956 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
5957 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
5958 patch allow one to discuss a concrete and proposed solution, and also
5959 prove that the issue at hand is important enough for someone to spent
5960 time on fixing it. No patch do not provide any of these positive
5961 properties.&lt;/p&gt;
5962 </description>
5963 </item>
5964
5965 <item>
5966 <title>Standardize on protocols and formats, not vendors and applications</title>
5967 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
5968 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
5969 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
5970 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
5971 very good one to form a long lived computer infrastructure. It is the
5972 simple one, lost by many in todays computer industry: Standardize on
5973 open network protocols and open exchange/storage formats, not applications.
5974 Applications come and go, while protocols and files tend to stay, and
5975 thus one want to make it easy to change application and vendor, while
5976 avoiding conversion costs and locking users to a specific platform or
5977 application.&lt;/p&gt;
5978
5979 &lt;p&gt;This approach make it possible to replace the client applications
5980 independently of the server applications. One can even allow users to
5981 use several different applications as long as they handle the selected
5982 protocol and format. In the normal case, only one client application
5983 is recommended and users only get help if they choose to use this
5984 application, but those that want to deviate from the easy path are not
5985 blocked from doing so.&lt;/p&gt;
5986
5987 &lt;p&gt;It also allow us to replace the server side without forcing the
5988 users to replace their applications, and thus allow us to select the
5989 best server implementation at any moment, when scale and resouce
5990 requirements change.&lt;/p&gt;
5991
5992 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
5993 open formats, but I would never recommend standardizing on a single
5994 application that do not use open network protocol or open formats.&lt;/p&gt;
5995 </description>
5996 </item>
5997
5998 <item>
5999 <title>Returning from Skolelinux developer gathering</title>
6000 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
6001 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
6002 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
6003 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
6004 Edu/Skolelinux development gathering. I got a bit done tuning the
6005 desktop, and looked into the dynamic service location protocol
6006 implementation avahi. It look like it could be useful for us. Almost
6007 30 people participated, and I believe it was a great environment to
6008 get to know the Skolelinux system. Walter Bender, involved in the
6009 development of the Sugar educational platform, presented his stuff and
6010 also helped me improve my OLPC installation. He also showed me that
6011 his Turtle Art application can be used in standalone mode, and we
6012 agreed that I would help getting it packaged for Debian. As a
6013 standalone application it would be great for Debian Edu. We also
6014 tried to get the video conferencing working with two OLPCs, but that
6015 proved to be too hard for us. The application seem to need more work
6016 before it is ready for me. I look forward to getting home and relax
6017 now. :)&lt;/p&gt;
6018 </description>
6019 </item>
6020
6021 <item>
6022 <title>Time for new LDAP schemas replacing RFC 2307?</title>
6023 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
6024 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
6025 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
6026 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
6027 optimal. There is RFC 2307 documenting one way to store NIS maps in
6028 LDAP, and a modified version of this normally called RFC 2307bis, with
6029 some modifications to be compatible with Active Directory. The RFC
6030 specification handle the content of a lot of system databases, but do
6031 not handle DNS zones and DHCP configuration.&lt;/p&gt;
6032
6033 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
6034 we would like to store information about users, SMB clients/hosts,
6035 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
6036 and LTSP configuration in LDAP. These objects have a lot in common,
6037 but with the current LDAP schemas it is not possible to have one
6038 object per entity. For example, one need to have at least three LDAP
6039 objects for a given computer, one with the SMB related stuff, one with
6040 DNS information and another with DHCP information. The schemas
6041 provided for DNS and DHCP are impossible to combine into one LDAP
6042 object. In addition, it is impossible to implement quick queries for
6043 netgroup membership, because of the way NIS triples are implemented.
6044 It just do not scale. I believe it is time for a few RFC
6045 specifications to cleam up this mess.&lt;/p&gt;
6046
6047 &lt;p&gt;I would like to have one LDAP object representing each computer in
6048 the network, and this object can then keep the SMB (ie host key), DHCP
6049 (mac address/name) and DNS (name/IP address) settings in one place.
6050 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
6051
6052 &lt;p&gt;I would also like to have a quick way to map from a user or
6053 computer and to the net group this user or computer is a member.&lt;/p&gt;
6054
6055 &lt;p&gt;Active Directory have done a better job than unix heads like myself
6056 in this regard, and the unix side need to catch up. Time to start a
6057 new IETF work group?&lt;/p&gt;
6058 </description>
6059 </item>
6060
6061 <item>
6062 <title>Endelig er Debian Lenny gitt ut</title>
6063 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
6064 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
6065 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
6066 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
6067 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
6068 Et langt steg videre for Debian-prosjektet, og en rekke nye
6069 programpakker blir nå tilgjengelig for de av oss som bruker den
6070 stabile utgaven av Debian. Neste steg er nå å få
6071 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
6072 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
6073 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
6074 slippes løs på skolene. Takk til alle debian-utviklerne som har
6075 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
6076 bootsekvens tilgjengelig i stabil utgave, vha pakken
6077 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
6078 </description>
6079 </item>
6080
6081 <item>
6082 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
6083 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
6084 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
6085 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
6086 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
6087 Oslo. Most of Saturday was used for the general assemly for the
6088 member organization, but the rest of the weekend I used to tune the
6089 LTSP installation. LTSP now work out of the box on the 10-network.
6090 Acer Aspire One proved to be a very nice thin client, with both
6091 screen, mouse and keybard in a small box. Was working on getting the
6092 diskless workstation setup configured out of the box, but did not
6093 finish it before the weekend was up.&lt;/p&gt;
6094
6095 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
6096 the Brazilian group, so that will have to wait for the next
6097 development gathering. Would love to have the Debian Edu installer
6098 automatically detect and configure a multiseat setup when it find one
6099 of these cards.&lt;/p&gt;
6100 </description>
6101 </item>
6102
6103 <item>
6104 <title>The sorry state of multimedia browser plugins in Debian</title>
6105 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
6106 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
6107 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
6108 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
6109 plugins available in Debian Lenny, to see which one we should use by
6110 default in Debian Edu. We need an embedded video playing plugin with
6111 control buttons to pause or stop the video, and capable of streaming
6112 all the multimedia content available on the web. The test results and
6113 notes are available on
6114 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
6115 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
6116 fill this need. My personal video player favorite, VLC, has a really
6117 bad plugin which fail on a lot of the test pages. A lot of the MIME
6118 types I would expect to work with any free software player (like
6119 video/ogg), just do not work. And simple formats like the
6120 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
6121 totem and vlc plugins. I hope the situation will improve soon. No
6122 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
6123
6124 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
6125 be the only one fitting our needs. :/&lt;/p&gt;
6126 </description>
6127 </item>
6128
6129 </channel>
6130 </rss>