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