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