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