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