]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
74596913a887f5f2965dea2ed934defe92c4c2cd
[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>Always download Debian packages using Tor - the simple recipe</title>
11 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
13 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
14 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Applebaum
15 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
16 that those listening on the Internet lines would have good reason to
17 believe a computer have a given security hole&lt;/a&gt; if it download a
18 security fix from a Debian mirror. This is a good reason to always
19 use encrypted connections to the Debian mirror, to make sure those
20 listening do not know which IP address to attack. In August, Richard
21 Hartmann observed that encryption was not enough, when it was possible
22 to interfere download size to security patches or the fact that
23 download took place shortly after a security fix was released, and
24 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
25 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
26 was not the first to propose this, as the &lt;tt&gt;apt-transport-tor&lt;/tt&gt;
27 package by Tim Retout already existed to make it easy to convince apt
28 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
29 aware of that package when I read the blog post from Richard.&lt;/p&gt;
30
31 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
32 sysadmins, and he set up a Tor hidden service on one of the central
33 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
34 it possible to download packages directly between two tor nodes,
35 making sure the network traffic always were encrypted.&lt;/p&gt;
36
37 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
38 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
39 urls with tor+http and https, and using the hidden service instead of
40 the official Debian mirror site. I recommend installing
41 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
42 done in /etc/.&lt;/p&gt;
43
44 &lt;blockquote&gt;&lt;pre&gt;
45 apt install apt-transport-tor
46 sed -i &#39;s% http://ftp.debian.org/%tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
47 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
48 &lt;/pre&gt;&lt;/blockquote&gt;
49
50 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
51 the sed commands for these too. The sed command is assuming your are
52 using the ftp.debian.org Debian mirror. Adjust the command (or just
53 edit the file manually) to match your mirror.&lt;/p&gt;
54
55 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
56 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
57 system, and do not work with these tor+http URLs. For
58 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
59 which need a recent apt version currently only in unstable. So if you
60 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
61
62 &lt;p&gt;Another advantage from this change is that your machine will start
63 using Tor regularly and at fairly random intervals (every time you
64 update the package lists or upgrade or install a new package), thus
65 masking other Tor traffic done from the same machine. Using Tor will
66 become normal for the machine in question.&lt;/p&gt;
67
68 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
69 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
70 enabled. It would be great if it was the default on any Debian
71 system.&lt;/p&gt;
72 </description>
73 </item>
74
75 <item>
76 <title>OpenALPR, find car license plates in video streams - nice free software</title>
77 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
78 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
79 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
80 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
81 call the car license plate numbers in those days. I would write the
82 numbers down in my little book and compare notes with the other kids
83 to see how many region codes we had seen and if we had seen some
84 exotic or special region codes and numbers. It was a fun game to pass
85 time, as we kids have plenty of it.&lt;/p&gt;
86
87 &lt;p&gt;A few days I came across
88 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
89 project&lt;/a&gt;, a free software project to automatically discover and
90 report license plates in images and video streams, and provide the
91 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
92 such system for a while now, because I believe it is a bad idea that the
93 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
94 number plate recognition&lt;/a&gt; tool only is available in the hands of
95 the powerful, and want it to be available also for the powerless to
96 even the score when it comes to surveillance and sousveillance. I
97 discovered the developer
98 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
99 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
100 help him get it into shape to get the package uploaded into the Debian
101 archive.&lt;/p&gt;
102
103 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
104 it into Debian, where it currently
105 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
106 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
107
108 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
109 for the common folks, ie those not running a large government
110 surveillance system? Well, I plan to put it in a computer on my bike
111 and in my car, tracking the cars nearby and allowing me to be notified
112 when number plates on my watch list are discovered. Another use case
113 was suggested by a friend of mine, who wanted to set it up at his home
114 to open the car port automatically when it discovered the plate on his
115 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
116 capable of placing his license plate number of a piece of cardboard to
117 open his car port, men replied that it was always unlocked anyway. I
118 guess for such use case it make sense. I am sure there are other use
119 cases too, for those with imagination and a vision.&lt;/p&gt;
120
121 &lt;p&gt;If you want to build your own version of the Debian package, check
122 out the upstream git source and symlink ./distros/debian to ./debian/
123 before running &quot;debuild&quot; to build the source. Or wait a bit until the
124 package show up in unstable.&lt;/p&gt;
125 </description>
126 </item>
127
128 <item>
129 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
130 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
131 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
132 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
133 <description>&lt;p&gt;Around three years ago, I created
134 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
135 system&lt;/a&gt; to get a more practical solution in Debian for handing
136 hardware related packages. A GUI system in the isenkram package will
137 present a pop-up dialog when some hardware dongle supported by
138 relevant packages in Debian is inserted into the machine. The same
139 lookup mechanism to detect packages is available as command line
140 tools in the isenkram-cli package. In addition to mapping hardware,
141 it will also map kernel firmware files to packages and make it easy to
142 install needed firmware packages automatically. The key for this
143 system to work is a good way to map hardware to packages, in other
144 words, allow packages to announce what hardware they will work
145 with.&lt;/p&gt;
146
147 &lt;p&gt;I started by providing data files in the isenkram source, and
148 adding code to download the latest version of these data files at run
149 time, to ensure every user had the most up to date mapping available.
150 I also added support for storing the mapping in the Packages file in
151 the apt repositories, but did not push this approach because while I
152 was trying to figure out how to best store hardware/package mappings,
153 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
154 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
155 add the hardware mapping into that data set to be able to use
156 appstream as a data source, and this was accepted at least for the
157 Debian version of appstream.&lt;/p&gt;
158
159 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
160 and today I uploaded a new version 0.20 of isenkram adding support for
161 appstream as a data source for mapping hardware to packages. The only
162 package so far using appstream to announce its hardware support is my
163 pymissile package. I got help from Matthias Klumpp with figuring out
164 how do add the required
165 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
166 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
167 this content:&lt;/p&gt;
168
169 &lt;blockquote&gt;&lt;pre&gt;
170 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
171 &amp;lt;component&amp;gt;
172 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
173 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
174 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
175 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
176 &amp;lt;description&amp;gt;
177 &amp;lt;p&amp;gt;
178 Pymissile provides a curses interface to control an original
179 Marks and Spencer / Striker USB Missile Launcher, as well as a
180 motion control script to allow a webcamera to control the
181 launcher.
182 &amp;lt;/p&amp;gt;
183 &amp;lt;/description&amp;gt;
184 &amp;lt;provides&amp;gt;
185 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
186 &amp;lt;/provides&amp;gt;
187 &amp;lt;/component&amp;gt;
188 &lt;/pre&gt;&lt;/blockquote&gt;
189
190 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
191 which is a glob style match rule for hardware specific strings
192 (modalias strings) provided by the Linux kernel. In this case, it
193 will map to all USB devices with vendor code 1130 and product code
194 0202.&lt;/p&gt;
195
196 &lt;p&gt;Note, it is important that the license of all the metadata files
197 are compatible to have permissions to aggregate them into archive wide
198 appstream files. Matthias suggested to use MIT or BSD licenses for
199 these files. A challenge is figuring out a good id for the data, as
200 it is supposed to be globally unique and shared across distributions
201 (in other words, best to coordinate with upstream what to use). But
202 it can be changed later or, so we went with the package name as
203 upstream for this project is dormant.&lt;/p&gt;
204
205 &lt;p&gt;To get the metadata file installed in the correct location for the
206 mirror update scripts to pick it up and include its content the
207 appstream data source, the file must be installed in the binary
208 package under /usr/share/appdata/. I did this by adding the following
209 line to debian/pymissile.install:&lt;/p&gt;
210
211 &lt;blockquote&gt;&lt;pre&gt;
212 debian/pymissile.metainfo.xml usr/share/appdata
213 &lt;/pre&gt;&lt;/blockquote&gt;
214
215 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
216 all packages useful on the current computer automatically, and the GUI
217 pop-up handler will propose to install the package not already
218 installed if a hardware dongle is inserted into the machine in
219 question.&lt;/p&gt;
220
221 &lt;p&gt;Details of the modalias field in appstream is available from the
222 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
223
224 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
225 try running this command on the command line:&lt;/p&gt;
226
227 &lt;blockquote&gt;&lt;pre&gt;
228 cat $(find /sys/devices/|grep modalias)
229 &lt;/pre&gt;&lt;/blockquote&gt;
230
231 &lt;p&gt;To learn more about the isenkram system, please check out
232 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
233 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
234 </description>
235 </item>
236
237 <item>
238 <title>The GNU General Public License is not magic pixie dust</title>
239 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
240 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
241 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
242 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
243 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
244 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
245 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
246 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
247
248 &lt;blockquote&gt;
249
250 &lt;p&gt;&lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;&lt;img src=&quot;https://sfconservancy.org/img/supporter-badge.png&quot; width=&quot;194&quot; height=&quot;90&quot; alt=&quot;Become a Software Freedom Conservancy Supporter!&quot; align=&quot;right&quot; border=&quot;0&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
251
252 &lt;blockquote&gt;
253 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
254
255 The first step is to choose a
256 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
257 code.&lt;br/&gt;
258
259 The next step is, when someone fails to follow that copyleft license,
260 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
261
262 and its a simple fact of our modern society that such type of
263 work&lt;br/&gt;
264
265 is incredibly expensive to do and incredibly difficult to do.
266 &lt;/blockquote&gt;
267
268 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
269 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
270 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
271 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
272
273 &lt;p&gt;As the Debian Website
274 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
275 &lt;a href=&quot;https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=1.24&amp;amp;r2=1.25&quot;&gt;to&lt;/a&gt;
276 imply, public domain and permissively licensed software can lead to
277 the production of more proprietary software as people discover useful
278 software, extend it and or incorporate it into their hardware or
279 software products. Copyleft licenses such as the GNU GPL were created
280 to close off this avenue to the production of proprietary software but
281 such licenses are not enough. With the ongoing adoption of Free
282 Software by individuals and groups, inevitably the community&#39;s
283 expectations of license compliance are violated, usually out of
284 ignorance of the way Free Software works, but not always. As Karen
285 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
286 Freedom&quot;&gt;FaiF&lt;/a&gt;
287 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
288 copyleft is nothing if no-one is willing and able to stand up in court
289 to protect it. The reality of today&#39;s world is that legal
290 representation is expensive, difficult and time consuming. With
291 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
292 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
293 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
294 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
295 of the Linux project, Debian and other groups against GPL violations.
296 In March the SFC supported a
297 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
298 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
299 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
300 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
301 kernel. Since then two of their sponsors pulled corporate funding and
302 conferences
303 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
304 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
305 less on corporate funding and more on the broad community of
306 individuals who support Free Software and copyleft. So the SFC has
307 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
308 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
309 a community of folks who stand up for copyleft and the GPL by
310 supporting their work on promoting and supporting copyleft and Free
311 Software.&lt;/p&gt;
312
313 &lt;p&gt;If you support Free Software,
314 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
315 what the SFC do, agree with their
316 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
317 principles&lt;/a&gt;, are happy about their
318 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
319 work on a project that is an SFC
320 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
321 just want to stand up for copyleft, please join
322 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
323 Allan Webber&lt;/a&gt;,
324 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
325 Smith&lt;/a&gt;,
326 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
327 Bacon&lt;/a&gt;, myself and
328 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
329 becoming a
330 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
331 next week your donation will be
332 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
333 by an anonymous donor. Please also consider asking your employer to
334 match your donation or become a sponsor of SFC. Don&#39;t forget to
335 spread the word about your support for SFC via email, your blog and or
336 social media accounts.&lt;/p&gt;
337
338 &lt;/blockquote&gt;
339
340 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
341 of Software Freedom Conservancy myself. Perhaps you should be a
342 supporter too?&lt;/p&gt;
343 </description>
344 </item>
345
346 <item>
347 <title>PGP key transition statement for key EE4E02F9</title>
348 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
349 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
350 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
351 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
352 set it up properly. I wanted to generate it offline and have it
353 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
354 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
355 time to sit down with an offline machine almost took forever. But
356 finally I&#39;ve been able to complete the process, and have now moved
357 from my old GPG key to a new GPG key. See
358 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
359 full transition statement, signed with both my old and new key&lt;/a&gt; for
360 the details. This is my new key:&lt;/p&gt;
361
362 &lt;pre&gt;
363 pub 3936R/&lt;a href=&quot;http://pgp.cs.uu.nl/stats/111D6B29EE4E02F9.html&quot;&gt;111D6B29EE4E02F9&lt;/a&gt; 2015-11-03 [expires: 2019-11-14]
364 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
365 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
366 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
367 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
368 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
369 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
370 &lt;/pre&gt;
371
372 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
373 my old key.&lt;/p&gt;
374
375 &lt;p&gt;If you signed my old key
376 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
377 I&#39;d very much appreciate a signature on my new key, details and
378 instructions in the transition statement. I m happy to reciprocate if
379 you have a similarly signed transition statement to present.&lt;/p&gt;
380 </description>
381 </item>
382
383 <item>
384 <title>The life and death of a laptop battery</title>
385 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
386 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
387 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
388 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
389 But this do not last. The last few laptops gave me a feeling that
390 within a year, the life time is just a fraction of what it used to be,
391 and it slowly become painful to use the laptop without power connected
392 all the time. Because of this, when I got a new Thinkpad X230 laptop
393 about two years ago, I decided to monitor its battery state to have
394 more hard facts when the battery started to fail.&lt;/p&gt;
395
396 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
397
398 &lt;p&gt;First I tried to find a sensible Debian package to record the
399 battery status, assuming that this must be a problem already handled
400 by someone else. I found
401 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
402 which collects statistics from the battery, but it was completely
403 broken. I sent a few suggestions to the maintainer, but decided to
404 write my own collector as a shell script while I waited for feedback
405 from him. Via
406 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
407 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
408 discovered
409 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
410 available in Debian.&lt;/p&gt;
411
412 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
413 battery stats ever since. Now my
414 /var/log/hjemmenett-battery-status.log file contain around 115,000
415 measurements, from the time the battery was working great until now,
416 when it is unable to charge above 7% of original capacity. My
417 collector shell script is quite simple and look like this:&lt;/p&gt;
418
419 &lt;pre&gt;
420 #!/bin/sh
421 # Inspired by
422 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
423 # See also
424 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
425 logfile=/var/log/hjemmenett-battery-status.log
426
427 files=&quot;manufacturer model_name technology serial_number \
428 energy_full energy_full_design energy_now cycle_count status&quot;
429
430 if [ ! -e &quot;$logfile&quot; ] ; then
431 (
432 printf &quot;timestamp,&quot;
433 for f in $files; do
434 printf &quot;%s,&quot; $f
435 done
436 echo
437 ) &gt; &quot;$logfile&quot;
438 fi
439
440 log_battery() {
441 # Print complete message in one echo call, to avoid race condition
442 # when several log processes run in parallel.
443 msg=$(printf &quot;%s,&quot; $(date +%s); \
444 for f in $files; do \
445 printf &quot;%s,&quot; $(cat $f); \
446 done)
447 echo &quot;$msg&quot;
448 }
449
450 cd /sys/class/power_supply
451
452 for bat in BAT*; do
453 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
454 done
455 &lt;/pre&gt;
456
457 &lt;p&gt;The script is called when the power management system detect a
458 change in the power status (power plug in or out), and when going into
459 and out of hibernation and suspend. In addition, it collect a value
460 every 10 minutes. This make it possible for me know when the battery
461 is discharging, charging and how the maximum charge change over time.
462 The code for the Debian package
463 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
464 available on github&lt;/a&gt;.&lt;/p&gt;
465
466 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
467
468 &lt;pre&gt;
469 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
470 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
471 [...]
472 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
473 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
474 &lt;/pre&gt;
475
476 &lt;p&gt;I wrote a small script to create a graph of the charge development
477 over time. This graph depicted above show the slow death of my laptop
478 battery.&lt;/p&gt;
479
480 &lt;p&gt;But why is this happening? Why are my laptop batteries always
481 dying in a year or two, while the batteries of space probes and
482 satellites keep working year after year. If we are to believe
483 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
484 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
485 chance, and the fix is to not charge the Lithium-ion batteries to 100%
486 all the time, but to stay below 90% of full charge most of the time.
487 I&#39;ve been told that the Tesla electric cars
488 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
489 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
490 100% when preparing for a longer trip (not that I would want a car
491 like Tesla where rights to privacy is abandoned, but that is another
492 story), which I guess is the option we should have for laptops on
493 Linux too.&lt;/p&gt;
494
495 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
496 stop charging at 80%, unless requested to charge to 100% once in
497 preparation for a longer trip? I found
498 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
499 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
500 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
501 load).&lt;/p&gt;
502
503 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
504 at the start. I also wonder why the &quot;full capacity&quot; increases some
505 times, and if it is possible to repeat the process to get the battery
506 back to design capacity. And I wonder if the discharge and charge
507 speed change over time, or if this stay the same. I did not yet try
508 to write a tool to calculate the derivative values of the battery
509 level, but suspect some interesting insights might be learned from
510 those.&lt;/p&gt;
511
512 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
513 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
514 packages instead of the tp-smapi-dkms package I had tried to use
515 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
516 and stop. I&#39;ve done so now, but expect my existing battery is toast
517 and need to be replaced. The proposal is unfortunately Thinkpad
518 specific.&lt;/p&gt;
519 </description>
520 </item>
521
522 <item>
523 <title>New laptop - some more clues and ideas based on feedback</title>
524 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
525 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
526 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
527 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
528 need for a new laptop, and provided very useful feedback. I wish to
529 thank every one of these. Several pointed me to the possibility of
530 fixing my X230, and I am already in the process of getting Lenovo to
531 do so thanks to the on site, next day support contract covering the
532 machine. But the battery is almost useless (I expect to replace it
533 with a non-official battery) and I do not expect the machine to live
534 for many more years, so it is time to plan its replacement. If I did
535 not have a support contract, it was suggested to find replacement parts
536 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
537 might present a language barrier as I do not understand French.&lt;/p&gt;
538
539 &lt;p&gt;One tip I got was to use the
540 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
541 compare laptop models. It seem to have more models available than
542 prisjakt.no. Another tip I got from someone I know have similar
543 keyboard preferences was that the HP EliteBook 840 keyboard is not
544 very good, and this matches my experience with earlier EliteBook
545 keyboards I tested. Because of this, I will not consider it any further.
546
547 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
548 newest Thinkpad X model. The keyboard reintroduces mouse buttons
549 (which is missing from the X240), and is working fairly well with
550 Debian Sid/Unstable according to
551 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
552 got on the keyboard quality are not consistent. Some say the keyboard
553 is good, others say it is ok, while others say it is not very good.
554 Those with experience from X41 and and X60 agree that the X250
555 keyboard is not as good as those trusty old laptops, and suggest I
556 keep and fix my X230 instead of upgrading, or get a used X230 to
557 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
558 activity and battery status, which is very convenient on my X230. I&#39;m
559 also told that the CPU fan is running very often, making it a bit
560 noisy. In any case, the X250 do not work out of the box with Debian
561 Stable/Jessie, one of my requirements.&lt;/p&gt;
562
563 &lt;p&gt;I have also gotten a few vendor proposals, one was
564 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
565 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
566 The latter look very attractive to me.&lt;/p&gt;
567
568 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
569 as I keep looking for a replacement.&lt;/p&gt;
570
571 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
572 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
573 different
574 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
575 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
576 </description>
577 </item>
578
579 <item>
580 <title>Time to find a new laptop, as the old one is broken after only two years</title>
581 <link>http://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</link>
582 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</guid>
583 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
584 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
585 replacement soon. The left 5 cm of the screen on my Thinkpad X230
586 started flickering yesterday, and I suspect the cause is a broken
587 cable, as changing the angle of the screen some times get rid of the
588 flickering.&lt;/p&gt;
589
590 &lt;p&gt;My requirements have not really changed since I bought it, and is
591 still as
592 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
593 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
594 good help from
595 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
596 where I could select at least a few of the requirements (mouse pin,
597 wifi, weight) and go through the rest manually. Three button mouse
598 and a good keyboard is not available as an option, and all the three
599 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
600 G2) lack three mouse buttons). It is also unclear to me how good the
601 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
602 the keyboard, even if the quality and robustness in the X series have
603 deteriorated since X41.&lt;/p&gt;
604
605 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
606 seem sensible to me? Are there better services around to search the
607 set of available laptops for features? Please send me an email if you
608 have suggestions.&lt;/p&gt;
609
610 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
611 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
612 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
613 </description>
614 </item>
615
616 <item>
617 <title>How to stay with sysvinit in Debian Jessie</title>
618 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
619 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
620 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
621 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
622 sysvinit as its boot system by default. But how can one keep using
623 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
624 courtesy of
625 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
626 Schubert&lt;/a&gt; and
627 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
628 McVittie&lt;/a&gt;.
629
630 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
631 keep sysvinit as your boot system, create a file
632 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
633 you upgrade:&lt;/p&gt;
634
635 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
636 Package: systemd-sysv
637 Pin: release o=Debian
638 Pin-Priority: -1
639 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
640
641 &lt;p&gt;This file content will tell apt and aptitude to not consider
642 installing systemd-sysv as part of any installation and upgrade
643 solution when resolving dependencies, and thus tell it to avoid
644 systemd as a default boot system. The end result should be that the
645 upgraded system keep using sysvinit.&lt;/p&gt;
646
647 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
648 get sysvinit installed by default (debootstrap used by
649 debian-installer have no option for this), but one can tell the
650 installer to switch to sysvinit before the first boot. Either by
651 using a kernel argument to the installer, or by adding a line to the
652 preseed file used. First, the kernel command line argument:
653
654 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
655 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
656 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
657
658 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
659
660 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
661 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
662 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
663
664 &lt;p&gt;One can of course also do this after the first boot by installing
665 the sysvinit-core package.&lt;/p&gt;
666
667 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
668 sysvinit boot sequence in Debian have several hardware specific bugs
669 on Linux caused by the fact that it is unpredictable when hardware
670 devices show up during boot. But on the other hand, the new default
671 boot system still have a few rough edges I hope will be fixed before
672 Jessie is released.&lt;/p&gt;
673
674 &lt;p&gt;Update 2014-11-26: Inspired by
675 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
676 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
677 line.&lt;/p&gt;
678 </description>
679 </item>
680
681 <item>
682 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
683 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
684 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
685 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
686 <description>&lt;p&gt;The right to communicate with your friends and family in private,
687 without anyone snooping, is a right every citicen have in a liberal
688 democracy. But this right is under serious attack these days.&lt;/p&gt;
689
690 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
691 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
692 the whisleblower Snowden) more expensive for Internet email,
693 is to deliver all email using SMTP via Tor. Such SMTP option would be
694 a nice addition to the FreedomBox project if we could send email
695 between FreedomBox machines without leaking metadata about the emails
696 to the people peeking on the wire. I
697 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
698 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
699 lot of useful feedback and suggestions. It also became obvious to me
700 that this was not a novel idea, as the same idea was tested and
701 documented by Johannes Berg as early as 2006, and both
702 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
703 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
704 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
705
706 &lt;p&gt;To implement such system one need to set up a Tor hidden service
707 providing the SMTP protocol on port 25, and use email addresses
708 looking like username@hidden-service-name.onion. With such addresses
709 the connections to port 25 on hidden-service-name.onion using Tor will
710 go to the correct SMTP server. To do this, one need to configure the
711 Tor daemon to provide the hidden service and the mail server to accept
712 emails for this .onion domain. To learn more about Exim configuration
713 in Debian and test the design provided by Johannes Berg in his FAQ, I
714 set out yesterday to create a Debian package for making it trivial to
715 set up such SMTP over Tor service based on Debian. Getting it to work
716 were fairly easy, and
717 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
718 source code for the Debian package&lt;/a&gt; is available from github. I
719 plan to move it into Debian if further testing prove this to be a
720 useful approach.&lt;/p&gt;
721
722 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
723 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
724 get rid of exim4). Install tor, clone the git repository mentioned
725 above, build the deb and install it on the machine. Next, run
726 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
727 the instructions to get the service up and running. Restart tor and
728 exim when it is done, and test mail delivery using swaks like
729 this:&lt;/p&gt;
730
731 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
732 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
733 --to fbx@dutlqrrmjhtfa3vp.onion
734 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
735
736 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
737 address with your own address to test your server. :)&lt;/p&gt;
738
739 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
740 easier and more automatic. Especially the tor setup need more work.
741 Also, the package include a tor-smtp tool written in C, but its task
742 should probably be rewritten in some script language to make the deb
743 architecture independent. It would probably also make the code easier
744 to review. The tor-smtp tool currently need to listen on a socket for
745 exim to talk to it and is started using xinetd. It would be better if
746 no daemon and no socket is needed. I suspect it is possible to get
747 exim to run a command line tool for delivery instead of talking to a
748 socket, and hope to figure out how in a future version of this
749 system.&lt;/p&gt;
750
751 &lt;p&gt;Until I wipe my test machine, I can be reached using the
752 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
753 SMTorP. :)&lt;/p&gt;
754 </description>
755 </item>
756
757 <item>
758 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
759 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
760 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
761 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
762 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
763 alioth.debian.org, you know the web interface is fairly slow to
764 operate. First you visit one web page, enter the moderation password
765 and get a new page shown with a list of all the messages to moderate
766 and various options for each email address. This take a while for
767 every list you moderate, and you need to do it regularly to do a good
768 job as a list moderator. But there is a quick alternative,
769 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
770 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
771 to moderate in a fraction of a second. Here is a test run on two
772 lists I recently took over:&lt;/p&gt;
773
774 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
775 % time listadmin xiph
776 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
777 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
778
779 real 0m1.709s
780 user 0m0.232s
781 sys 0m0.012s
782 %
783 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
784
785 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
786 there are no message in the moderation queue. Every morning I
787 currently moderate 68 mailman lists, and it normally take around two
788 minutes. When I took over the two pkg-xiph lists above a few days
789 ago, there were 400 emails waiting in the moderator queue. It took me
790 less than 15 minutes to process them all using the listadmin
791 program.&lt;/p&gt;
792
793 &lt;p&gt;If you install
794 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
795 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
796 with content like this, the moderation task is a breeze:&lt;/p&gt;
797
798 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
799 username username@example.org
800 spamlevel 23
801 default discard
802 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
803
804 password secret
805 adminurl https://{domain}/mailman/admindb/{list}
806 mailman-list@lists.example.com
807
808 password hidden
809 other-list@otherserver.example.org
810 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
811
812 &lt;p&gt;There are other options to set as well. Check the manual page to
813 learn the details.&lt;/p&gt;
814
815 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
816 the SSL certificate is self signed or not properly signed by a
817 generally accepted signing authority, you can set a environment
818 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
819
820 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
821 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
822 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
823
824 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
825 can provide an argument to the listadmin script like I do in the
826 initial screen dump (the xiph argument). Using an argument, only
827 lists matching the argument string will be processed. This make it
828 quick to accept messages if you notice the moderation request in your
829 email.&lt;/p&gt;
830
831 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
832 mailing lists, as I simply do not have time to spend on that if the
833 process was any slower. The listadmin program have saved me hours of
834 time I could spend elsewhere over the years. It truly is nice free
835 software.&lt;/p&gt;
836
837 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
838 activities, please send Bitcoin donations to my address
839 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
840
841 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
842 configuration example. Also, I&#39;ve been told that the
843 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
844 sure why.&lt;/p&gt;
845 </description>
846 </item>
847
848 <item>
849 <title>Debian Jessie, PXE and automatic firmware installation</title>
850 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
851 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
852 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
853 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
854 problem that the WiFi card require some firmware to work properly.
855 And it has been a pain to fix this using preseeding in Debian.
856 Normally something more is needed. But thanks to
857 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
858 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
859 to do this using simple preseeding.&lt;/p&gt;
860
861 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
862 firmware for the hardware found in the machine (actually, requested by
863 the kernel modules for the hardware). (It can also install user space
864 programs supporting the hardware detected, but that is not the focus
865 of this story.)&lt;/p&gt;
866
867 &lt;p&gt;To get this working in the default installation, two preeseding
868 values are needed. First, the isenkram-cli package must be installed
869 into the target chroot (aka the hard drive) before tasksel is executed
870 in the pkgsel step of the debian-installer system. This is done by
871 preseeding the base-installer/includes debconf value to include the
872 isenkram-cli package. The package name is next passed to debootstrap
873 for installation. With the isenkram-cli package in place, tasksel
874 will automatically use the isenkram tasks to detect hardware specific
875 packages for the machine being installed and install them, because
876 isenkram-cli contain tasksel tasks.&lt;/p&gt;
877
878 &lt;p&gt;Second, one need to enable the non-free APT repository, because
879 most firmware unfortunately is non-free. This is done by preseeding
880 the apt-mirror-setup step. This is unfortunate, but for a lot of
881 hardware it is the only option in Debian.&lt;/p&gt;
882
883 &lt;p&gt;The end result is two lines needed in your preseeding file to get
884 firmware installed automatically by the installer:&lt;/p&gt;
885
886 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
887 base-installer base-installer/includes string isenkram-cli
888 apt-mirror-setup apt-setup/non-free boolean true
889 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
890
891 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
892 both firmware and user space packages when using this method. It also
893 do not work well, so use version 0.15 or later. Installing both
894 firmware and user space packages might give you a bit more than you
895 want, so I decided to split the tasksel task in two, one for firmware
896 and one for user space programs. The firmware task is enabled by
897 default, while the one for user space programs is not. This split is
898 implemented in the package currently in unstable.&lt;/p&gt;
899
900 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
901 this recipe work for you. :)&lt;/p&gt;
902
903 &lt;p&gt;So, I bet you are wondering, how can this work. First and
904 foremost, it work because tasksel is modular, and driven by whatever
905 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
906 isenkram-cli package place two files for tasksel to find. First there
907 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
908
909 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
910 Task: isenkram-packages
911 Section: hardware
912 Description: Hardware specific packages (autodetected by isenkram)
913 Based on the detected hardware various hardware specific packages are
914 proposed.
915 Test-new-install: show show
916 Relevance: 8
917 Packages: for-current-hardware
918
919 Task: isenkram-firmware
920 Section: hardware
921 Description: Hardware specific firmware packages (autodetected by isenkram)
922 Based on the detected hardware various hardware specific firmware
923 packages are proposed.
924 Test-new-install: mark show
925 Relevance: 8
926 Packages: for-current-hardware-firmware
927 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
928
929 &lt;p&gt;The key parts are Test-new-install which indicate how the task
930 should be handled and the Packages line referencing to a script in
931 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
932 list of packages to install. The for-current-hardware-firmware script
933 look like this to list relevant firmware for the machine:
934
935 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
936 #!/bin/sh
937 #
938 PATH=/usr/sbin:$PATH
939 export PATH
940 isenkram-autoinstall-firmware -l
941 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
942
943 &lt;p&gt;With those two pieces in place, the firmware is installed by
944 tasksel during the normal d-i run. :)&lt;/p&gt;
945
946 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
947 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
948 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
949 install.&lt;/p&gt;
950
951 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
952 pilots in testing this feature, as isenkram is used there now to
953 install firmware, replacing the earlier scripts.&lt;/p&gt;
954 </description>
955 </item>
956
957 <item>
958 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
959 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
960 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
961 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
962 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
963 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
964 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
965 on a screen normally showing the bread types and prizes:&lt;/p&gt;
966
967 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2014-10-04-ubuntu-ica-storo-crop.jpeg&quot;&gt;&lt;/p&gt;
968
969 &lt;p&gt;If it had booted as it was supposed to, I would never had known
970 about this hidden Linux installation. It is interesting what
971 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
972 </description>
973 </item>
974
975 <item>
976 <title>New lsdvd release version 0.17 is ready</title>
977 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
978 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
979 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
980 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
981 got a new set of developers a few weeks ago, after the original
982 developer decided to step down and pass the project to fresh blood.
983 This project is now maintained by Petter Reinholdtsen and Steve
984 Dibb.&lt;/p&gt;
985
986 &lt;p&gt;I just wrapped up
987 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
988 new lsdvd release&lt;/a&gt;, available in git or from
989 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
990 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
991 0.17.&lt;/p&gt;
992
993 &lt;ul&gt;
994
995 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
996 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
997 non-existant, to work around additional copy protection&lt;/li&gt;
998 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
999 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
1000 &lt;li&gt;Fix include orders&lt;/li&gt;
1001 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
1002 &lt;li&gt;Fix the chapter count&lt;/li&gt;
1003 &lt;li&gt;Make sure the array size and the array limit used when initialising
1004 the palette size is the same.&lt;/li&gt;
1005 &lt;li&gt;Fix array printing.&lt;/li&gt;
1006 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
1007 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
1008 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
1009 with more GCC compiler warnings.&lt;/li&gt;
1010
1011 &lt;/ul&gt;
1012
1013 &lt;p&gt;This change bring together patches for lsdvd in use in various
1014 Linux and Unix distributions, as well as patches submitted to the
1015 project the last nine years. Please check it out. :)&lt;/p&gt;
1016 </description>
1017 </item>
1018
1019 <item>
1020 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
1021 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
1022 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
1023 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
1024 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1025 project&lt;/a&gt; provide a Linux solution for schools, including a
1026 powerful desktop with education software, a central server providing
1027 web pages, user database, user home directories, central login and PXE
1028 boot of both clients without disk and the installation to install Debian
1029 Edu on machines with disk (and a few other services perhaps to small
1030 to mention here). We in the Debian Edu team are currently working on
1031 the Jessie based version, trying to get everything in shape before the
1032 freeze, to avoid having to maintain our own package repository in the
1033 future. The
1034 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
1035 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
1036 work left. Some fatal problems block testing, breaking the installer,
1037 but it is possible to work around these to get anyway. Here is a
1038 recipe on how to get the installation limping along.&lt;/p&gt;
1039
1040 &lt;p&gt;First, download the test ISO via
1041 &lt;a href=&quot;ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso&quot;&gt;ftp&lt;/a&gt;,
1042 &lt;a href=&quot;http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso&quot;&gt;http&lt;/a&gt;
1043 or rsync (use
1044 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
1045 The ISO build was broken on Tuesday, so we do not get a new ISO every
1046 12 hours or so, but thankfully the ISO we already got we are able to
1047 install with some tweaking.&lt;/p&gt;
1048
1049 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
1050 (use Alt-Ctrl-F2), run&lt;/p&gt;
1051
1052 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1053 nano /usr/bin/edu-eatmydata-install
1054 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1055
1056 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
1057 optimization. Return to the installation, select the profile you want
1058 and continue. Without this change, exim4-config will fail to install
1059 due to a known bug in eatmydata.&lt;/p&gt;
1060
1061 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
1062 this do not work, figure out what your correct value would be. All my
1063 test machines need /dev/sda, so I have no advice if it do not fit
1064 your need.&lt;/p&gt;
1065
1066 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
1067 root after the initial boot from hard drive, and install the
1068 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1069 or mate. If you want several desktop options, install more than one
1070 metapackage. Once this is done, reboot and you should have a working
1071 graphical login screen. This workaround should no longer be needed
1072 once the education-tasks package version 1.801 enter testing in two
1073 days.&lt;/p&gt;
1074
1075 &lt;p&gt;I believe the ISO build will start working on two days when the new
1076 tasksel package enter testing and Steve McIntyre get a chance to
1077 update the debian-cd git repository. The eatmydata, grub and desktop
1078 issues are already fixed in unstable and testing, and should show up
1079 on the ISO as soon as the ISO build start working again. Well the
1080 eatmydata optimization is really just disabled. The proper fix
1081 require an upload by the eatmydata maintainer applying the patch
1082 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
1083 The rest have proper fixes in unstable.&lt;/p&gt;
1084
1085 &lt;p&gt;I hope this get you going with the installation testing, as we are
1086 quickly running out of time trying to get our Jessie based
1087 installation ready before the distribution freeze in a month.&lt;/p&gt;
1088 </description>
1089 </item>
1090
1091 <item>
1092 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
1093 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
1094 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
1095 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
1096 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
1097 to handle my fairly large DVD collection. It is a nice command line
1098 tool to get details about a DVD, like title, tracks, track length,
1099 etc, in XML, Perl or human readable format. But lsdvd have not seen
1100 any new development since 2006 and had a few irritating bugs affecting
1101 its use with some DVDs. Upstream seemed to be dead, and in January I
1102 sent a small probe asking for a version control repository for the
1103 project, without any reply. But I use it regularly and would like to
1104 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
1105 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
1106 the project admin, and after getting a reply from him explaining that
1107 he was no longer interested in the project, I asked if I could take
1108 over. And yesterday, I became project admin.&lt;/p&gt;
1109
1110 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
1111 maintainer interested in joining forces to maintain the upstream
1112 project, and I hope we can get a new release out fairly quickly,
1113 collecting the patches spread around on the internet into on place.
1114 I&#39;ve added the relevant Debian patches to the freshly created git
1115 repository, and expect the Gentoo patches to make it too. If you got
1116 a DVD collection and care about command line tools, check out
1117 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
1118 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
1119 list&lt;/a&gt;. :)&lt;/p&gt;
1120 </description>
1121 </item>
1122
1123 <item>
1124 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
1125 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
1126 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
1127 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
1128 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
1129 a lot quicker. When we install more than 2000 packages in
1130 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
1131 tasksel in the installer, unpacking the binary packages take forever.
1132 A part of the slow I/O issue was discussed in
1133 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
1134 much file system sync-ing done by dpkg, which is the package
1135 responsible for unpacking the binary packages. Other parts (like code
1136 executed by postinst scripts) might also sync to disk during
1137 installation. All this sync-ing to disk do not really make sense to
1138 me. If the machine crash half-way through, I start over, I do not try
1139 to salvage the half installed system. So the failure sync-ing is
1140 supposed to protect against, hardware or system crash, is not really
1141 relevant while the installer is running.&lt;/p&gt;
1142
1143 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
1144 system sync()-ing in a fairly non-intrusive way, without the need to
1145 change the code in several packages. The idea is not new, but I have
1146 not heard anyone propose the approach using dpkg-divert before. It
1147 depend on the small and clever package
1148 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
1149 uses LD_PRELOAD to replace the system functions for syncing data to
1150 disk with functions doing nothing, thus allowing programs to live
1151 dangerous while speeding up disk I/O significantly. Instead of
1152 modifying the implementation of dpkg, apt and tasksel (which are the
1153 packages responsible for selecting, fetching and installing packages),
1154 it occurred to me that we could just divert the programs away, replace
1155 them with a simple shell wrapper calling
1156 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
1157 Two days ago I decided to test the idea, and wrapped up a simple
1158 implementation for the Debian Edu udeb.&lt;/p&gt;
1159
1160 &lt;p&gt;The effect was stunning. In my first test it reduced the running
1161 time of the pkgsel step (installing tasks) from 64 to less than 44
1162 minutes (20 minutes shaved off the installation) on an old Dell
1163 Latitude D505 machine. I am not quite sure what the optimised time
1164 would have been, as I messed up the testing a bit, causing the debconf
1165 priority to get low enough for two questions to pop up during
1166 installation. As soon as I saw the questions I moved the installation
1167 along, but do not know how long the question were holding up the
1168 installation. I did some more measurements using Debian Edu Jessie,
1169 and got these results. The time measured is the time stamp in
1170 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
1171 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
1172 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1173 timing thus do not depend on how quickly the user handle the tasksel
1174 dialog.&lt;/p&gt;
1175
1176 &lt;p&gt;&lt;table&gt;
1177
1178 &lt;tr&gt;
1179 &lt;th&gt;Machine/setup&lt;/th&gt;
1180 &lt;th&gt;Original tasksel&lt;/th&gt;
1181 &lt;th&gt;Optimised tasksel&lt;/th&gt;
1182 &lt;th&gt;Reduction&lt;/th&gt;
1183 &lt;/tr&gt;
1184
1185 &lt;tr&gt;
1186 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
1187 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
1188 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
1189 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
1190 &lt;/tr&gt;
1191
1192 &lt;tr&gt;
1193 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
1194 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
1195 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
1196 &lt;td&gt;23 min 40%&lt;/td&gt;
1197 &lt;/tr&gt;
1198
1199 &lt;tr&gt;
1200 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
1201 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
1202 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
1203 &lt;td&gt;11 min 50%&lt;/td&gt;
1204 &lt;/tr&gt;
1205
1206 &lt;tr&gt;
1207 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
1208 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
1209 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
1210 &lt;td&gt;2 min 33%&lt;/td&gt;
1211 &lt;/tr&gt;
1212
1213 &lt;tr&gt;
1214 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
1215 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
1216 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
1217 &lt;td&gt;4 min 21%&lt;/td&gt;
1218 &lt;/tr&gt;
1219
1220 &lt;/table&gt;&lt;/p&gt;
1221
1222 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
1223 time is spent downloading packages. The connection to the Internet
1224 was 100Mbit/s during testing, so downloading should not be a
1225 significant factor in the measurement. Download typically took a few
1226 seconds to a few minutes, depending on the amount of packages being
1227 installed.&lt;/p&gt;
1228
1229 &lt;p&gt;The speedup is implemented by using two hooks in
1230 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
1231 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
1232 finish-install.d hook to remove the divert at the end of the
1233 installation. I picked the pre-pkgsel.d hook instead of the
1234 post-base-installer.d hook because I test using an ISO without the
1235 eatmydata package included, and the post-base-installer.d hook in
1236 Debian Edu can only operate on packages included in the ISO. The
1237 negative effect of this is that I am unable to activate this
1238 optimization for the kernel installation step in d-i. If the code is
1239 moved to the post-base-installer.d hook, the speedup would be larger
1240 for the entire installation.&lt;/p&gt;
1241
1242 &lt;p&gt;I&#39;ve implemented this in the
1243 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
1244 git repository, and plan to provide the optimization as part of the
1245 Debian Edu installation. If you want to test this yourself, you can
1246 create two files in the installer (or in an udeb). One shell script
1247 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
1248
1249 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1250 #!/bin/sh
1251 set -e
1252 . /usr/share/debconf/confmodule
1253 info() {
1254 logger -t my-pkgsel &quot;info: $*&quot;
1255 }
1256 error() {
1257 logger -t my-pkgsel &quot;error: $*&quot;
1258 }
1259 override_install() {
1260 apt-install eatmydata || true
1261 if [ -x /target/usr/bin/eatmydata ] ; then
1262 for bin in dpkg apt-get aptitude tasksel ; do
1263 file=/usr/bin/$bin
1264 # Test that the file exist and have not been diverted already.
1265 if [ -f /target$file ] ; then
1266 info &quot;diverting $file using eatmydata&quot;
1267 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
1268 &gt; /target$file.edu
1269 chmod 755 /target$file.edu
1270 in-target dpkg-divert --package debian-edu-config \
1271 --rename --quiet --add $file
1272 ln -sf ./$bin.edu /target$file
1273 else
1274 error &quot;unable to divert $file, as it is missing.&quot;
1275 fi
1276 done
1277 else
1278 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
1279 fi
1280 }
1281
1282 override_install
1283 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1284
1285 &lt;p&gt;To clean up, another shell script should go into
1286 /usr/lib/finish-install.d/ with code like this:
1287
1288 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1289 #! /bin/sh -e
1290 . /usr/share/debconf/confmodule
1291 error() {
1292 logger -t my-finish-install &quot;error: $@&quot;
1293 }
1294 remove_install_override() {
1295 for bin in dpkg apt-get aptitude tasksel ; do
1296 file=/usr/bin/$bin
1297 if [ -x /target$file.edu ] ; then
1298 rm /target$file
1299 in-target dpkg-divert --package debian-edu-config \
1300 --rename --quiet --remove $file
1301 rm /target$file.edu
1302 else
1303 error &quot;Missing divert for $file.&quot;
1304 fi
1305 done
1306 sync # Flush file buffers before continuing
1307 }
1308
1309 remove_install_override
1310 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1311
1312 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
1313 edu-eatmydata-install and call it from the pre-pkgsel.d and
1314 finish-install.d scripts.&lt;/p&gt;
1315
1316 &lt;p&gt;By now you might ask if this change should get into the normal
1317 Debian installer too? I suspect it should, but am not sure the
1318 current debian-installer coordinators find it useful enough. It also
1319 depend on the side effects of the change. I&#39;m not aware of any, but I
1320 guess we will see if the change is safe after some more testing.
1321 Perhaps there is some package in Debian depending on sync() and
1322 fsync() having effect? Perhaps it should go into its own udeb, to
1323 allow those of us wanting to enable it to do so without affecting
1324 everyone.&lt;/p&gt;
1325
1326 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
1327 will break installation of all programs using gnutls because of
1328 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
1329 eatmydata package in Debian will solve it.&lt;/p&gt;
1330
1331 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
1332 the optimization work again. And I have discovered that the
1333 dpkg-divert trick is not really needed and implemented a slightly
1334 simpler approach as part of the debian-edu-install package. See
1335 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
1336
1337 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1338 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1339 triggering on i386 made it into testing, and broke this installation
1340 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1341 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1342 </description>
1343 </item>
1344
1345 <item>
1346 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1347 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1348 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1349 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1350 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1351 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1352 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1353 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1354 learn that there is a large set of publicly available key servers to
1355 use when looking for peoples public key. So far I have used
1356 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1357 were misbehaving, but those days are ended. The servers I have used
1358 up until yesterday have been slow and some times unavailable. I hope
1359 those problems are gone now.&lt;/p&gt;
1360
1361 &lt;p&gt;Behind the round robin DNS entry of the
1362 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1363 there is a pool of more than 100 keyservers which are checked every
1364 day to ensure they are well connected and up to date. It must be
1365 better than what I have used so far. :)&lt;/p&gt;
1366
1367 &lt;p&gt;Yesterdays speaker told me that the service is the default
1368 keyserver provided by the default configuration in GnuPG, but this do
1369 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1370
1371 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1372 line:&lt;/p&gt;
1373
1374 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1375 keyserver pool.sks-keyservers.net
1376 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1377
1378 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1379 entries in DNS. Just for fun, I did just that at work, so now every
1380 user of GnuPG at the University of Oslo should find a OpenGPG
1381 keyserver automatically should their need it:&lt;/p&gt;
1382
1383 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1384 % host -t srv _pgpkey-http._tcp.uio.no
1385 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1386 %
1387 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1388
1389 &lt;p&gt;Now if only
1390 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1391 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1392 very happy. It can look up a given key or search for a user ID, but I
1393 normally do not want that, but to find a trust path from my key to
1394 another key. Given a user ID or key ID, I would like to find (and
1395 download) the keys representing a signature path from my key to the
1396 key in question, to be able to get a trust path between the two keys.
1397 This is as far as I can tell not possible today. Perhaps something
1398 for a future version of the protocol?&lt;/p&gt;
1399 </description>
1400 </item>
1401
1402 <item>
1403 <title>From English wiki to translated PDF and epub via Docbook</title>
1404 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1405 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1406 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1407 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1408 project&lt;/a&gt; provide an instruction manual for teachers, system
1409 administrators and other users that contain useful tips for setting up
1410 and maintaining a Debian Edu installation. This text is about how the
1411 text processing of this manual is handled in the project.&lt;/p&gt;
1412
1413 &lt;p&gt;One goal of the project is to provide information in the native
1414 language of its users, and for this we need to handle translations.
1415 But we also want to make sure each language contain the same
1416 information, so for this we need a good way to keep the translations
1417 in sync. And we want it to be easy for our users to improve the
1418 documentation, avoiding the need to learn special formats or tools to
1419 contribute, and the obvious way to do this is to make it possible to
1420 edit the documentation using a web browser. We also want it to be
1421 easy for translators to keep the translation up to date, and give them
1422 help in figuring out what need to be translated. Here is the list of
1423 tools and the process we have found trying to reach all these
1424 goals.&lt;/p&gt;
1425
1426 &lt;p&gt;We maintain the authoritative source of our manual in the
1427 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1428 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1429 front page with references to the different chapters, several pages
1430 for each chapter, and finally one &quot;collection page&quot; gluing all the
1431 chapters together into one large web page (aka
1432 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1433 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1434 processing and translations. Thanks to the fact that the
1435 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1436 wiki.debian.org support exporting pages in
1437 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1438 the list of pages to export using the raw version of the AllInOne
1439 page, loop over each of them to generate a Docbook XML version of the
1440 manual. This process also download images and transform image
1441 references to use the locally downloaded images. The generated
1442 Docbook XML files are slightly broken, so some post-processing is done
1443 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1444 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1445 a handfull of images. The XML file can now be used to generate PDF, HTML
1446 and epub versions of the English manual. This is the basic step of
1447 our process, making PDF (using dblatex), HTML (using xsltproc) and
1448 epub (using dbtoepub) version from Docbook XML, and the resulting files
1449 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1450
1451 &lt;p&gt;But English documentation is not enough for us. We want translated
1452 documentation too, and we want to make it easy for translators to
1453 track the English original. For this we use the
1454 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1455 which allow us to transform the English Docbook XML file into a
1456 translation file (a .pot file), usable with the normal gettext based
1457 translation tools used by those translating free software. The pot
1458 file is used to create and maintain translation files (several .po
1459 files), which the translations update with the native language
1460 translations of all titles, paragraphs and blocks of text in the
1461 original. The next step is combining the original English Docbook XML
1462 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1463 create a translated Docbook XML file (in this case
1464 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1465 translated, if the translation is not complete) Docbook XML file can
1466 then be used like the original to create a PDF, HTML and epub version
1467 of the documentation.&lt;/p&gt;
1468
1469 &lt;p&gt;The translators use different tools to edit the .po files. We
1470 recommend using
1471 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1472 while some use emacs and vi, others can use web based editors like
1473 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1474 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1475 is where the .po file end up, in our git repository. Updated
1476 translations can either be committed directly to git, or submitted as
1477 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1478 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1479
1480 &lt;p&gt;One challenge is images, which both might need to be translated (if
1481 they show translated user applications), and are needed in different
1482 formats when creating PDF and HTML versions (epub is a HTML version in
1483 this regard). For this we transform the original PNG images to the
1484 needed density and format during build, and have a way to provide
1485 translated images by storing translated versions in
1486 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1487 package maintainers know more.&lt;/p&gt;
1488
1489 &lt;p&gt;If you wonder what the result look like, we provide
1490 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1491 of the documentation packages on the web&lt;/a&gt;. See for example the
1492 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1493 PDF version&lt;/a&gt; or the
1494 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1495 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1496 but perhaps it will be done in the future.&lt;/p&gt;
1497
1498 &lt;p&gt;To learn more, check out
1499 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1500 debian-edu-doc package&lt;/a&gt;,
1501 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1502 manual on the wiki&lt;/a&gt; and
1503 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1504 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1505 </description>
1506 </item>
1507
1508 <item>
1509 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1510 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1511 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1512 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1513 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1514 related packages relevant for the computer installed automatically.
1515 So I implemented one, using
1516 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1517 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1518 run tasksel as user root. You should be presented with a new option,
1519 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1520 select it, tasksel will install the packages isenkram claim is fit for
1521 the current hardware, hot pluggable or not.&lt;p&gt;
1522
1523 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1524 description, and the other is the script used to extract the list of
1525 packages to install. The first part is in
1526 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1527 this:&lt;/p&gt;
1528
1529 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1530 Task: isenkram
1531 Section: hardware
1532 Description: Hardware specific packages (autodetected by isenkram)
1533 Based on the detected hardware various hardware specific packages are
1534 proposed.
1535 Test-new-install: mark show
1536 Relevance: 8
1537 Packages: for-current-hardware
1538 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1539
1540 &lt;p&gt;The second part is in
1541 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1542 this:&lt;/p&gt;
1543
1544 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1545 #!/bin/sh
1546 #
1547 (
1548 isenkram-lookup
1549 isenkram-autoinstall-firmware -l
1550 ) | sort -u
1551 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1552
1553 &lt;p&gt;All in all, a very short and simple implementation making it
1554 trivial to install the hardware dependent package we all may want to
1555 have installed on our machines. I&#39;ve not been able to find a way to
1556 get tasksel to tell you exactly which packages it plan to install
1557 before doing the installation. So if you are curious or careful,
1558 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1559
1560 &lt;p&gt;The information about which packages are handling which hardware is
1561 fetched either from the isenkram package itself in
1562 /usr/share/isenkram/, from git.debian.org or from the APT package
1563 database (using the Modaliases header). The APT package database
1564 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1565 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1566 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1567 the python-apt code (bug
1568 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1569 workaround I was able to get rid of the file descriptor leak and
1570 reduce the memory leak from ~30 MiB per hardware detection down to
1571 around 2 MiB per hardware detection. It should make the desktop
1572 daemon a lot more useful. The fix is in version 0.7 uploaded to
1573 unstable today.&lt;/p&gt;
1574
1575 &lt;p&gt;I believe the current way of mapping hardware to packages in
1576 Isenkram is is a good draft, but in the future I expect isenkram to
1577 use the AppStream data source for this. A proposal for getting proper
1578 AppStream support into Debian is floating around as
1579 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1580 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1581 project&lt;/a&gt; will take place this summer to improve the situation. I
1582 look forward to seeing the result, and welcome patches for isenkram to
1583 start using the information when it is ready.&lt;/p&gt;
1584
1585 &lt;p&gt;If you want your package to map to some specific hardware, either
1586 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1587 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1588 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1589 package. See also
1590 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1591 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1592 the information will be migrated to AppStream eventually, but for the
1593 moment I got no better place to store it.&lt;/p&gt;
1594 </description>
1595 </item>
1596
1597 <item>
1598 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1599 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1600 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1601 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1602 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1603 project&lt;/a&gt; is working on providing the software and hardware to make
1604 it easy for non-technical people to host their data and communication
1605 at home, and being able to communicate with their friends and family
1606 encrypted and away from prying eyes. It is still going strong, and
1607 today a major mile stone was reached.&lt;/p&gt;
1608
1609 &lt;p&gt;Today, the last of the packages currently used by the project to
1610 created the system images were accepted into Debian Unstable. It was
1611 the freedombox-setup package, which is used to configure the images
1612 during build and on the first boot. Now all one need to get going is
1613 the build code from the freedom-maker git repository and packages from
1614 Debian. And once the freedombox-setup package enter testing, we can
1615 build everything directly from Debian. :)&lt;/p&gt;
1616
1617 &lt;p&gt;Some key packages used by Freedombox are
1618 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1619 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1620 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1621 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1622 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1623 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1624 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1625 are plans to integrate more packages into the setup. User
1626 documentation is maintained on the Debian wiki. Please
1627 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1628 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1629
1630 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1631 setup, run this on a Debian machine using a user with sudo rights to
1632 become root:&lt;/p&gt;
1633
1634 &lt;p&gt;&lt;pre&gt;
1635 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1636 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1637 u-boot-tools
1638 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1639 freedom-maker
1640 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1641 &lt;/pre&gt;&lt;/p&gt;
1642
1643 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1644 devices. See the README in the freedom-maker git repo for more
1645 details on the build. If you do not want all three images, trim the
1646 make line. Note that the virtualbox-image target is not really
1647 virtualbox specific. It create a x86 image usable in kvm, qemu,
1648 vmware and any other x86 virtual machine environment. You might need
1649 the version of vmdebootstrap in Jessie to get the build working, as it
1650 include fixes for a race condition with kpartx.&lt;/p&gt;
1651
1652 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1653 method, boot a Debian Wheezy ISO and use this boot argument to load
1654 the preseed values:&lt;/p&gt;
1655
1656 &lt;p&gt;&lt;pre&gt;
1657 url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&lt;/a&gt;
1658 &lt;/pre&gt;&lt;/p&gt;
1659
1660 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1661 it still work.&lt;/p&gt;
1662
1663 &lt;p&gt;If you wonder how to help, one task you could look at is using
1664 systemd as the boot system. It will become the default for Linux in
1665 Jessie, so we need to make sure it is usable on the Freedombox. I did
1666 a simple test a few weeks ago, and noticed dnsmasq failed to start
1667 during boot when using systemd. I suspect there are other problems
1668 too. :) To detect problems, there is a test suite included, which can
1669 be run from the plinth web interface.&lt;/p&gt;
1670
1671 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1672 us get the new release published. :) Please join us on
1673 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1674 irc.debian.org)&lt;/a&gt; and
1675 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1676 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1677 </description>
1678 </item>
1679
1680 <item>
1681 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1682 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1683 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1684 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1685 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1686 solution for use at home. My requirements are simple, it must be
1687 cheap and locally encrypted (in other words, I keep the encryption
1688 keys, the storage provider do not have access to my private files).
1689 One idea me and my friends had many years ago, before the cloud
1690 storage providers showed up, was to use Google mail as storage,
1691 writing a Linux block device storing blocks as emails in the mail
1692 service provided by Google, and thus get heaps of free space. On top
1693 of this one can add encryption, RAID and volume management to have
1694 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1695 I never found time to implement such system. But the last few weeks I
1696 have looked at a system called
1697 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1698 mounted network backed file system with the features I need.&lt;/p&gt;
1699
1700 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1701 handling several different storage providers, any with Amazon S3,
1702 Google Drive or OpenStack API. There are heaps of such storage
1703 providers. S3QL can also use a local directory as storage, which
1704 combined with sshfs allow for file storage on any ssh server. S3QL
1705 include support for encryption, compression, de-duplication, snapshots
1706 and immutable file systems, allowing me to mount the remote storage as
1707 a local mount point, look at and use the files as if they were local,
1708 while the content is stored in the cloud as well. This allow me to
1709 have a backup that should survive fire. The file system can not be
1710 shared between several machines at the same time, as only one can
1711 mount it at the time, but any machine with the encryption key and
1712 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1713
1714 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1715 package is included already. So to get started, run &lt;tt&gt;apt-get
1716 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1717 Greenqloud, after reading their nice recipe on
1718 &lt;a href=&quot;https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy&quot;&gt;how
1719 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1720 in Iceland more than those in USA when it come to keeping my personal
1721 data safe and private, and thus would rather spend money on a company
1722 in Iceland. Another nice recipe is available from the article
1723 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1724 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1725 Admin magazine. When the provider is picked, figure out how to get
1726 the API key needed to connect to the storage API. With Greencloud,
1727 the key did not show up until I had added payment details to my
1728 account.&lt;/p&gt;
1729
1730 &lt;p&gt;Armed with the API access details, it is time to create the file
1731 system. First, create a new bucket in the cloud. This bucket is the
1732 file system storage area. I picked a bucket name reflecting the
1733 machine that was going to store data there, but any name will do.
1734 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1735 the API login and password, and a locally created password. Store it
1736 all in ~root/.s3ql/authinfo2 like this:
1737
1738 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1739 [s3c]
1740 storage-url: s3c://s.greenqloud.com:443/bucket-name
1741 backend-login: API-login
1742 backend-password: API-password
1743 fs-passphrase: local-password
1744 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1745
1746 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
1747 but any sensible way to create a fairly random password should do it.
1748 Armed with these details, it is now time to run mkfs, entering the API
1749 details and password to create it:&lt;/p&gt;
1750
1751 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1752 # mkdir -m 700 /var/lib/s3ql-cache
1753 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1754 --ssl s3c://s.greenqloud.com:443/bucket-name
1755 Enter backend login:
1756 Enter backend password:
1757 Before using S3QL, make sure to read the user&#39;s guide, especially
1758 the &#39;Important Rules to Avoid Loosing Data&#39; section.
1759 Enter encryption password:
1760 Confirm encryption password:
1761 Generating random encryption key...
1762 Creating metadata tables...
1763 Dumping metadata...
1764 ..objects..
1765 ..blocks..
1766 ..inodes..
1767 ..inode_blocks..
1768 ..symlink_targets..
1769 ..names..
1770 ..contents..
1771 ..ext_attributes..
1772 Compressing and uploading metadata...
1773 Wrote 0.00 MB of compressed metadata.
1774 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1775
1776 &lt;p&gt;The next step is mounting the file system to make the storage available.
1777
1778 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1779 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1780 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1781 Using 4 upload threads.
1782 Downloading and decompressing metadata...
1783 Reading metadata...
1784 ..objects..
1785 ..blocks..
1786 ..inodes..
1787 ..inode_blocks..
1788 ..symlink_targets..
1789 ..names..
1790 ..contents..
1791 ..ext_attributes..
1792 Mounting filesystem...
1793 # df -h /s3ql
1794 Filesystem Size Used Avail Use% Mounted on
1795 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
1796 #
1797 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1798
1799 &lt;p&gt;The file system is now ready for use. I use rsync to store my
1800 backups in it, and as the metadata used by rsync is downloaded at
1801 mount time, no network traffic (and storage cost) is triggered by
1802 running rsync. To unmount, one should not use the normal umount
1803 command, as this will not flush the cache to the cloud storage, but
1804 instead running the umount.s3ql command like this:
1805
1806 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1807 # umount.s3ql /s3ql
1808 #
1809 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1810
1811 &lt;p&gt;There is a fsck command available to check the file system and
1812 correct any problems detected. This can be used if the local server
1813 crashes while the file system is mounted, to reset the &quot;already
1814 mounted&quot; flag. This is what it look like when processing a working
1815 file system:&lt;/p&gt;
1816
1817 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1818 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
1819 Using cached metadata.
1820 File system seems clean, checking anyway.
1821 Checking DB integrity...
1822 Creating temporary extra indices...
1823 Checking lost+found...
1824 Checking cached objects...
1825 Checking names (refcounts)...
1826 Checking contents (names)...
1827 Checking contents (inodes)...
1828 Checking contents (parent inodes)...
1829 Checking objects (reference counts)...
1830 Checking objects (backend)...
1831 ..processed 5000 objects so far..
1832 ..processed 10000 objects so far..
1833 ..processed 15000 objects so far..
1834 Checking objects (sizes)...
1835 Checking blocks (referenced objects)...
1836 Checking blocks (refcounts)...
1837 Checking inode-block mapping (blocks)...
1838 Checking inode-block mapping (inodes)...
1839 Checking inodes (refcounts)...
1840 Checking inodes (sizes)...
1841 Checking extended attributes (names)...
1842 Checking extended attributes (inodes)...
1843 Checking symlinks (inodes)...
1844 Checking directory reachability...
1845 Checking unix conventions...
1846 Checking referential integrity...
1847 Dropping temporary indices...
1848 Backing up old metadata...
1849 Dumping metadata...
1850 ..objects..
1851 ..blocks..
1852 ..inodes..
1853 ..inode_blocks..
1854 ..symlink_targets..
1855 ..names..
1856 ..contents..
1857 ..ext_attributes..
1858 Compressing and uploading metadata...
1859 Wrote 0.89 MB of compressed metadata.
1860 #
1861 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1862
1863 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
1864 quick, about the same speed as local file access. Uploading large
1865 amount of data is to me limited by the bandwidth out of and into my
1866 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
1867 which is very close to my upload speed, and downloading the same
1868 Debian installation ISO gave me 610 kiB/s, close to my download speed.
1869 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
1870 network, not the file system code. I do not know what a good cache
1871 size would be, but suspect that the cache should e larger than your
1872 working set.&lt;/p&gt;
1873
1874 &lt;p&gt;I mentioned that only one machine can mount the file system at the
1875 time. If another machine try, it is told that the file system is
1876 busy:&lt;/p&gt;
1877
1878 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1879 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1880 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1881 Using 8 upload threads.
1882 Backend reports that fs is still mounted elsewhere, aborting.
1883 #
1884 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1885
1886 &lt;p&gt;The file content is uploaded when the cache is full, while the
1887 metadata is uploaded once every 24 hour by default. To ensure the
1888 file system content is flushed to the cloud, one can either umount the
1889 file system, or ask S3QL to flush the cache and metadata using
1890 s3qlctrl:
1891
1892 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1893 # s3qlctrl upload-meta /s3ql
1894 # s3qlctrl flushcache /s3ql
1895 #
1896 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1897
1898 &lt;p&gt;If you are curious about how much space your data uses in the
1899 cloud, and how much compression and deduplication cut down on the
1900 storage usage, you can use s3qlstat on the mounted file system to get
1901 a report:&lt;/p&gt;
1902
1903 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1904 # s3qlstat /s3ql
1905 Directory entries: 9141
1906 Inodes: 9143
1907 Data blocks: 8851
1908 Total data size: 22049.38 MB
1909 After de-duplication: 21955.46 MB (99.57% of total)
1910 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
1911 Database size: 2.39 MB (uncompressed)
1912 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1913 #
1914 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1915
1916 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
1917 storage. I did not try to locate them all, but am aware of at least
1918 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
1919 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
1920 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
1921 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
1922 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
1923 accept payment in Bitcoin. Pick one that suit your need. Some of
1924 them provide several GiB of free storage, but the prize models are
1925 quite different and you will have to figure out what suits you
1926 best.&lt;/p&gt;
1927
1928 &lt;p&gt;While researching this blog post, I had a look at research papers
1929 and posters discussing the S3QL file system. There are several, which
1930 told me that the file system is getting a critical check by the
1931 science community and increased my confidence in using it. One nice
1932 poster is titled
1933 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
1934 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1935 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
1936 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1937 and Pamela Smith. Please have a look.&lt;/p&gt;
1938
1939 &lt;p&gt;Given my problems with different file systems earlier, I decided to
1940 check out the mounted S3QL file system to see if it would be usable as
1941 a home directory (in other word, that it provided POSIX semantics when
1942 it come to locking and umask handling etc). Running
1943 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html&quot;&gt;my
1944 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
1945 no error was found. So the file system can be used for home
1946 directories, if one chooses to do so.&lt;/p&gt;
1947
1948 &lt;p&gt;If you do not want a locally file system, and want something that
1949 work without the Linux fuse file system, I would like to mention the
1950 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
1951 provide locally encrypted backup using a command line client. It have
1952 a nicer access control system, where one can split out read and write
1953 access, allowing some systems to write to the backup and others to
1954 only read from it.&lt;/p&gt;
1955
1956 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1957 activities, please send Bitcoin donations to my address
1958 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1959 </description>
1960 </item>
1961
1962 <item>
1963 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1964 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1965 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1966 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1967 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1968 project&lt;/a&gt; is working on providing the software and hardware for
1969 making it easy for non-technical people to host their data and
1970 communication at home, and being able to communicate with their
1971 friends and family encrypted and away from prying eyes. It has been
1972 going on for a while, and is slowly progressing towards a new test
1973 release (0.2).&lt;/p&gt;
1974
1975 &lt;p&gt;And what day could be better than the Pi day to announce that the
1976 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1977 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1978 system), and can also be installed using a Debian installer preseed
1979 file. The Debian based Freedombox is now based on Debian Jessie,
1980 where most of the needed packages used are already present. Only one,
1981 the freedombox-setup package, is missing. To try to build your own
1982 boot image to test the current status, fetch the freedom-maker scripts
1983 and build using
1984 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1985 with a user with sudo access to become root:
1986
1987 &lt;pre&gt;
1988 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1989 freedom-maker
1990 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1991 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1992 u-boot-tools
1993 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1994 &lt;/pre&gt;
1995
1996 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1997 devices. See the README for more details on the build. If you do not
1998 want all three images, trim the make line. But note that thanks to &lt;a
1999 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
2000 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
2001 kpartx call.&lt;/p&gt;
2002
2003 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2004 method, boot a Debian Wheezy ISO and use this boot argument to load
2005 the preseed values:&lt;/p&gt;
2006
2007 &lt;pre&gt;
2008 url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&lt;/a&gt;
2009 &lt;/pre&gt;
2010
2011 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
2012 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
2013 currently hang while setting up APT sources. Killing the
2014 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
2015 installation will get the installation going. This affect all
2016 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
2017
2018 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2019 us get the new release published. :) Please join us on
2020 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2021 irc.debian.org)&lt;/a&gt; and
2022 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2023 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2024 </description>
2025 </item>
2026
2027 <item>
2028 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
2029 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
2030 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
2031 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
2032 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
2033 innetgr tools, because I needed them in
2034 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
2035 ng-utils, and it has served me well. I placed the project under the
2036 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
2037 repository. But many years ago, the CVS repository was dropped (lost,
2038 not migrated to new hardware, not sure), and the project have lacked a
2039 proper home since then.&lt;/p&gt;
2040
2041 &lt;p&gt;Last summer, I had a look at the package and made a new release
2042 fixing a irritating crash bug, but was unable to store the changes in
2043 a proper source control system. I applied for a project on
2044 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
2045 to follow up on it. Until today. :)&lt;/p&gt;
2046
2047 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
2048 now have a new home, and a git repository with the highlight of the
2049 history of the project. I published all release tarballs and imported
2050 them into the git repository. As the project is really stable and not
2051 expected to gain new features any time soon, I decided to make a new
2052 release and call it 1.0. Visit the new project home on
2053 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
2054 if you want to check it out. The new version is also uploaded into
2055 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
2056 </description>
2057 </item>
2058
2059 <item>
2060 <title>Testing sysvinit from experimental in Debian Hurd</title>
2061 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
2062 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
2063 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
2064 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
2065 their changes into sysvinit, to allow them to use the normal sysvinit
2066 boot system instead of their old one. This follow up on the
2067 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
2068 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
2069 get Debian on Hurd working more like Debian on Linux. To get started,
2070 I downloaded a prebuilt hard disk image from
2071 &lt;a href=&quot;http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz&quot;&gt;http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz&lt;/a&gt;,
2072 and started it using virt-manager.&lt;/p&gt;
2073
2074 &lt;p&gt;The first think I had to do after logging in (root without any
2075 password) was to get the network operational. I followed
2076 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
2077 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
2078 commands as root to get the machine to accept a IP address from the
2079 kvm internal DHCP server:&lt;/p&gt;
2080
2081 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2082 settrans -fgap /dev/netdde /hurd/netdde
2083 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
2084 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
2085 dhclient /dev/eth0
2086 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2087
2088 &lt;p&gt;After this, the machine had internet connectivity, and I could
2089 upgrade it and install the sysvinit packages from experimental and
2090 enable it as the default boot system in Hurd.&lt;/p&gt;
2091
2092 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
2093 running on the machine it for ssh login to work a password need to be
2094 set. Also, note that a bug somewhere in openssh on Hurd block
2095 compression from working. Remember to turn that off on the client
2096 side.&lt;/p&gt;
2097
2098 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
2099 stuff:&lt;/p&gt;
2100
2101 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2102 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
2103 deb http://http.debian.net/debian/ experimental main
2104 EOF
2105 apt-get update
2106 apt-get dist-upgrade
2107 apt-get install -t experimental initscripts sysv-rc sysvinit \
2108 sysvinit-core sysvinit-utils
2109 update-alternatives --config runsystem
2110 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2111
2112 &lt;p&gt;To reboot after switching boot system, you have to use
2113 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
2114 yet a sysvinit process able to receive the signals from the normal
2115 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
2116 upgrading every package and rebooting, the network come up with DHCP
2117 after boot as it should, and the settrans/pkill hack mentioned at the
2118 start is no longer needed. But for some strange reason, there are no
2119 longer any login prompt in the virtual console, so I logged in using
2120 ssh instead.
2121
2122 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
2123 fail some times. No idea what the cause is, but hope the Hurd porters
2124 figure it out. At least Justus said on IRC (#debian-hurd on
2125 irc.debian.org) that they are aware of the problem. A way to reduce
2126 the impact is to upgrade to the Hurd packages built by Justus by
2127 adding this repository to the machine:&lt;/p&gt;
2128
2129 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2130 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
2131 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2132 EOF
2133 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2134
2135 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
2136 http://ftp.debian-ports.org/debian, because some of the packages in
2137 unstable do not yet include the required patches that are lingering in
2138 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
2139
2140 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2141 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
2142 i emacs - GNU Emacs editor (metapackage)
2143 i gdb - GNU Debugger
2144 i hurd-recommended - Miscellaneous translators
2145 i isc-dhcp-client - ISC DHCP client
2146 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2147 i libc-bin - Embedded GNU C Library: Binaries
2148 i libc-dev-bin - Embedded GNU C Library: Development binaries
2149 i libc0.3 - Embedded GNU C Library: Shared libraries
2150 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2151 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2152 i multiarch-support - Transitional package to ensure multiarch compatibilit
2153 i A x11-common - X Window System (X.Org) infrastructure
2154 i xorg - X.Org X Window System
2155 i A xserver-xorg - X.Org X server
2156 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2157 #
2158 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2159
2160 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
2161 X.org did not work out of the box and I never took the time to follow
2162 the porters instructions to fix it. This time I was interested in the
2163 command line stuff.&lt;p&gt;
2164 </description>
2165 </item>
2166
2167 <item>
2168 <title>New chrpath release 0.16</title>
2169 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
2170 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
2171 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
2172 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
2173 find problems in C, C++ and Java code using static source code
2174 analysis. It can detect a lot of different problems, and is very
2175 useful to find memory and locking bugs in the error handling part of
2176 the source. The company behind it provide
2177 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
2178 a community service&lt;/a&gt;, and many hundred free software projects are
2179 already checked. A few days ago I decided to have a closer look at
2180 the Coverity system, and discovered that the
2181 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
2182 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
2183 projects I am involved with was already registered. But these are
2184 fairly big, and I would also like to have a small and easy project to
2185 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
2186 checking of the chrpath project&lt;/a&gt;. It was
2187 added to the checker and discovered seven potential defects. Six of
2188 these were real, mostly resource &quot;leak&quot; when the program detected an
2189 error. Nothing serious, as the resources would be released a fraction
2190 of a second later when the program exited because of the error, but it
2191 is nice to do it right in case the source of the program some time in
2192 the future end up in a library. Having fixed all defects and added
2193 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
2194 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
2195 publish a new release. These are the release notes:&lt;/p&gt;
2196
2197 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
2198
2199 &lt;ul&gt;
2200
2201 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
2202 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
2203 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
2204
2205 &lt;/ul&gt;
2206
2207 &lt;p&gt;You can
2208 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2209 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
2210 project if something is wrong with the new release. The test suite
2211 did not discover any old errors, so if you find a new one, please also
2212 include a test suite check.&lt;/p&gt;
2213 </description>
2214 </item>
2215
2216 <item>
2217 <title>New chrpath release 0.15</title>
2218 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
2219 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
2220 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
2221 <description>&lt;p&gt;After many years break from the package and a vain hope that
2222 development would be continued by someone else, I finally pulled my
2223 acts together this morning and wrapped up a new release of chrpath,
2224 the command line tool to modify the rpath and runpath of already
2225 compiled ELF programs. The update was triggered by the persistence of
2226 Isha Vishnoi at IBM, which needed a new config.guess file to get
2227 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
2228 is working on. I checked the
2229 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
2230 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
2231 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
2232 packages for interesting patches (failed to find the source from
2233 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2234 These are the release notes:&lt;/p&gt;
2235
2236 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
2237
2238 &lt;ul&gt;
2239
2240 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
2241 with newer architectures. Thanks to isha vishnoi for the heads
2242 up.&lt;/li&gt;
2243
2244 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
2245
2246 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2247 Matthias Klose.&lt;/li&gt;
2248
2249 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
2250 Petr Machata found in Fedora.&lt;/li&gt;
2251
2252 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
2253 .dynamic is a NULL terminated string. Based on patch found in
2254 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
2255
2256 &lt;/ul&gt;
2257
2258 &lt;p&gt;You can
2259 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2260 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
2261 project if something is wrong with the new release. The test suite
2262 did not discover any old errors, so if you find a new one, please also
2263 include a testsuite check.&lt;/p&gt;
2264 </description>
2265 </item>
2266
2267 <item>
2268 <title>Debian init.d boot script example for rsyslog</title>
2269 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
2270 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
2271 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
2272 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
2273 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
2274 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
2275 init.d scripts at all. Here is an example init.d script, ie a rewrite
2276 of /etc/init.d/rsyslog:&lt;/p&gt;
2277
2278 &lt;p&gt;&lt;pre&gt;
2279 #!/lib/init/init-d-script
2280 ### BEGIN INIT INFO
2281 # Provides: rsyslog
2282 # Required-Start: $remote_fs $time
2283 # Required-Stop: umountnfs $time
2284 # X-Stop-After: sendsigs
2285 # Default-Start: 2 3 4 5
2286 # Default-Stop: 0 1 6
2287 # Short-Description: enhanced syslogd
2288 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2289 # It is quite compatible to stock sysklogd and can be
2290 # used as a drop-in replacement.
2291 ### END INIT INFO
2292 DESC=&quot;enhanced syslogd&quot;
2293 DAEMON=/usr/sbin/rsyslogd
2294 &lt;/pre&gt;&lt;/p&gt;
2295
2296 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
2297 script was 137 lines, and the above is just 15 lines, most of it meta
2298 info/comments.&lt;/p&gt;
2299
2300 &lt;p&gt;How to do this, you ask? Well, one create a new script
2301 /lib/init/init-d-script looking something like this:
2302
2303 &lt;p&gt;&lt;pre&gt;
2304 #!/bin/sh
2305
2306 # Define LSB log_* functions.
2307 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
2308 # and status_of_proc is working.
2309 . /lib/lsb/init-functions
2310
2311 #
2312 # Function that starts the daemon/service
2313
2314 #
2315 do_start()
2316 {
2317 # Return
2318 # 0 if daemon has been started
2319 # 1 if daemon was already running
2320 # 2 if daemon could not be started
2321 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
2322 || return 1
2323 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2324 $DAEMON_ARGS \
2325 || return 2
2326 # Add code here, if necessary, that waits for the process to be ready
2327 # to handle requests from services started subsequently which depend
2328 # on this one. As a last resort, sleep for some time.
2329 }
2330
2331 #
2332 # Function that stops the daemon/service
2333 #
2334 do_stop()
2335 {
2336 # Return
2337 # 0 if daemon has been stopped
2338 # 1 if daemon was already stopped
2339 # 2 if daemon could not be stopped
2340 # other if a failure occurred
2341 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2342 RETVAL=&quot;$?&quot;
2343 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2344 # Wait for children to finish too if this is a daemon that forks
2345 # and if the daemon is only ever run from this initscript.
2346 # If the above conditions are not satisfied then add some other code
2347 # that waits for the process to drop all resources that could be
2348 # needed by services started subsequently. A last resort is to
2349 # sleep for some time.
2350 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2351 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2352 # Many daemons don&#39;t delete their pidfiles when they exit.
2353 rm -f $PIDFILE
2354 return &quot;$RETVAL&quot;
2355 }
2356
2357 #
2358 # Function that sends a SIGHUP to the daemon/service
2359 #
2360 do_reload() {
2361 #
2362 # If the daemon can reload its configuration without
2363 # restarting (for example, when it is sent a SIGHUP),
2364 # then implement that here.
2365 #
2366 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2367 return 0
2368 }
2369
2370 SCRIPTNAME=$1
2371 scriptbasename=&quot;$(basename $1)&quot;
2372 echo &quot;SN: $scriptbasename&quot;
2373 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2374 script=&quot;$1&quot;
2375 shift
2376 . $script
2377 else
2378 exit 0
2379 fi
2380
2381 NAME=$(basename $DAEMON)
2382 PIDFILE=/var/run/$NAME.pid
2383
2384 # Exit if the package is not installed
2385 #[ -x &quot;$DAEMON&quot; ] || exit 0
2386
2387 # Read configuration variable file if it is present
2388 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2389
2390 # Load the VERBOSE setting and other rcS variables
2391 . /lib/init/vars.sh
2392
2393 case &quot;$1&quot; in
2394 start)
2395 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2396 do_start
2397 case &quot;$?&quot; in
2398 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2399 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2400 esac
2401 ;;
2402 stop)
2403 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2404 do_stop
2405 case &quot;$?&quot; in
2406 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2407 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2408 esac
2409 ;;
2410 status)
2411 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2412 ;;
2413 #reload|force-reload)
2414 #
2415 # If do_reload() is not implemented then leave this commented out
2416 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2417 #
2418 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2419 #do_reload
2420 #log_end_msg $?
2421 #;;
2422 restart|force-reload)
2423 #
2424 # If the &quot;reload&quot; option is implemented then remove the
2425 # &#39;force-reload&#39; alias
2426 #
2427 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2428 do_stop
2429 case &quot;$?&quot; in
2430 0|1)
2431 do_start
2432 case &quot;$?&quot; in
2433 0) log_end_msg 0 ;;
2434 1) log_end_msg 1 ;; # Old process is still running
2435 *) log_end_msg 1 ;; # Failed to start
2436 esac
2437 ;;
2438 *)
2439 # Failed to stop
2440 log_end_msg 1
2441 ;;
2442 esac
2443 ;;
2444 *)
2445 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2446 exit 3
2447 ;;
2448 esac
2449
2450 :
2451 &lt;/pre&gt;&lt;/p&gt;
2452
2453 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2454 lot. I did not really polish the approach, so it might not always
2455 work out of the box, but you get the idea. I did not try very hard to
2456 optimize it nor make it more robust either.&lt;/p&gt;
2457
2458 &lt;p&gt;A better argument for switching init system in Debian than reducing
2459 the size of init scripts (which is a good thing to do anyway), is to
2460 get boot system that is able to handle the kernel events sensibly and
2461 robustly, and do not depend on the boot to run sequentially. The boot
2462 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2463 </description>
2464 </item>
2465
2466 <item>
2467 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2468 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2469 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2470 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2471 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2472 remote display access is the preferred solution with oVirt and RedHat
2473 Enterprise Virtualization, and I was sad to discover the other day
2474 that the browser plugin needed to use these systems seamlessly was
2475 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2476 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2477 2013-04-01, so I decided to wrap up a package based on the great work
2478 from Cajus Pollmeier and put it in a collab-maint maintained git
2479 repository to get a package I could use. I would very much like
2480 others to help me maintain the package (or just take over, I do not
2481 mind), but as no-one had volunteered so far, I just uploaded it to
2482 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2483
2484 &lt;p&gt;The source is now available from
2485 &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;
2486 </description>
2487 </item>
2488
2489 <item>
2490 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2491 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2492 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2493 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2494 <description>&lt;p&gt;The
2495 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2496 program is a a very nice system to create virtual machine images. It
2497 create a image file, add a partition table, mount it and run
2498 debootstrap in the mounted directory to create a Debian system on a
2499 stick. Yesterday, I decided to try to teach it how to make images for
2500 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2501 of a plan to simplify the build system for
2502 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2503 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2504 the virtualbox images, but its current build system made multistrap
2505 based system for Dreamplug images, and it is lacking support for
2506 Raspberry Pi.&lt;/p&gt;
2507
2508 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2509 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2510 code and adjusted it to be able to build armel images on my amd64
2511 Debian laptop. I ended up giving vmdebootstrap five new options,
2512 allowing me to replicate the image creation process I use to make
2513 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2514 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2515 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2516 call debootstrap with --foreign and to copy the handler into the
2517 generated chroot before running the second stage. This allow
2518 vmdebootstrap to create armel images on an amd64 host. Next I added
2519 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2520 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2521 given file system type, allowing me to create an image with a vfat
2522 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2523 variant&lt;/tt&gt; option to allow me to create smaller images without the
2524 Debian base system packages installed. Finally, I added an option
2525 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2526 as a boot loader. It is not needed on the Raspberry Pi and probably
2527 most other non-x86 architectures. The changes were accepted by the
2528 upstream author of vmdebootstrap yesterday and today, and is now
2529 available from
2530 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2531 upstream project page&lt;/a&gt;.&lt;/p&gt;
2532
2533 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2534 create a small script (the customize script) to add the non-free
2535 binary blob needed to boot the Raspberry Pi and the APT source
2536 list:&lt;/p&gt;
2537
2538 &lt;p&gt;&lt;pre&gt;
2539 #!/bin/sh
2540 set -e # Exit on first error
2541 rootdir=&quot;$1&quot;
2542 cd &quot;$rootdir&quot;
2543 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2544 deb http://http.debian.net/debian/ jessie main contrib non-free
2545 EOF
2546 # Install non-free binary blob needed to boot Raspberry Pi. This
2547 # install a kernel somewhere too.
2548 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2549 -O $rootdir/usr/bin/rpi-update
2550 chmod a+x $rootdir/usr/bin/rpi-update
2551 mkdir -p $rootdir/lib/modules
2552 touch $rootdir/boot/start.elf
2553 chroot $rootdir rpi-update
2554 &lt;/pre&gt;&lt;/p&gt;
2555
2556 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2557 to build the image:&lt;/p&gt;
2558
2559 &lt;pre&gt;
2560 sudo ./vmdebootstrap \
2561 --variant minbase \
2562 --arch armel \
2563 --distribution jessie \
2564 --mirror http://http.debian.net/debian \
2565 --image test.img \
2566 --size 600M \
2567 --bootsize 64M \
2568 --boottype vfat \
2569 --log-level debug \
2570 --verbose \
2571 --no-kernel \
2572 --no-extlinux \
2573 --root-password raspberry \
2574 --hostname raspberrypi \
2575 --foreign /usr/bin/qemu-arm-static \
2576 --customize `pwd`/customize \
2577 --package netbase \
2578 --package git-core \
2579 --package binutils \
2580 --package ca-certificates \
2581 --package wget \
2582 --package kmod
2583 &lt;/pre&gt;&lt;/p&gt;
2584
2585 &lt;p&gt;The list of packages being installed are the ones needed by
2586 rpi-update to make the image bootable on the Raspberry Pi, with the
2587 exception of netbase, which is needed by debootstrap to find
2588 /etc/hosts with the minbase variant. I really wish there was a way to
2589 set up an Raspberry Pi using only packages in the Debian archive, but
2590 that is not possible as far as I know, because it boots from the GPU
2591 using a non-free binary blob.&lt;/p&gt;
2592
2593 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2594 probably a few others installed. I have not checked the complete
2595 build dependency list.&lt;/p&gt;
2596
2597 &lt;p&gt;The resulting image will not use the hardware floating point unit
2598 on the Raspberry PI, because the armel architecture in Debian is not
2599 optimized for that use. So the images created will be a bit slower
2600 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2601 </description>
2602 </item>
2603
2604 <item>
2605 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2606 <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>
2607 <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>
2608 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2609 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2610 wider attention. I recommend signing and donating to each one of
2611 these. :)&lt;/p&gt;
2612
2613 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2614 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2615 Women program which is a Google Summer of Code like initiative to get
2616 more women involved in free software. One debian sponsor has offered
2617 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2618 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2619 hope you will to. :)&lt;/p&gt;
2620
2621 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2622 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2623 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2624 take place these days, and their need to fund the work. I&#39;ve already
2625 donated. Are you next?&lt;/p&gt;
2626
2627 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2628 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2629 statement under the heading
2630 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2631 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2632 Norwegian government. So far 499 signatures. I hope you will sign it
2633 too.&lt;/p&gt;
2634 </description>
2635 </item>
2636
2637 <item>
2638 <title>Videos about the Freedombox project - for inspiration and learning</title>
2639 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2640 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2641 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2642 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2643 project&lt;/a&gt; have been going on for a while, and have presented the
2644 vision, ideas and solution several places. Here is a little
2645 collection of videos of talks and presentation of the project.&lt;/p&gt;
2646
2647 &lt;ul&gt;
2648
2649 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2650 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2651
2652 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2653 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2654
2655 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2656 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2657 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2658 (Youtube)&lt;/li&gt;
2659
2660 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2661 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2662
2663 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2664 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2665
2666 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2667 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2668 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2669
2670 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2671 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2672 (Youtube)&lt;/li&gt;
2673
2674 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2675 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2676
2677 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2678 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2679
2680 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2681 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2682 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2683
2684 &lt;/ul&gt;
2685
2686 &lt;p&gt;A larger list is available from
2687 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2688 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2689
2690 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2691 Jessie is coming along quite well, and soon both Owncloud and using
2692 Tor should be available for testers of the Freedombox solution. :) In
2693 a few weeks I hope everything needed to test it is included in Debian.
2694 The withsqlite package is already in Debian, and the plinth package is
2695 pending in NEW. The third and vital part of that puzzle is the
2696 metapackage/setup framework, which is still pending an upload. Join
2697 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2698 (#freedombox on irc.debian.org)&lt;/a&gt; and
2699 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2700 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2701 </description>
2702 </item>
2703
2704 <item>
2705 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2706 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2707 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2708 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2709 <description>&lt;p&gt;I was introduced to the
2710 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2711 in 2010, when Eben Moglen presented his vision about serving the need
2712 of non-technical people to keep their personal information private and
2713 within the legal protection of their own homes. The idea is to give
2714 people back the power over their network and machines, and return
2715 Internet back to its intended peer-to-peer architecture. Instead of
2716 depending on a central service, the Freedombox will give everyone
2717 control over their own basic infrastructure.&lt;/p&gt;
2718
2719 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2720 taken priority. But this summers nasty news about the misuse of trust
2721 and privilege exercised by the &quot;western&quot; intelligence gathering
2722 communities increased my eagerness to contribute to a point where I
2723 actually started working on the project a while back.&lt;/p&gt;
2724
2725 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2726 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2727 create a simple and cheap Debian based appliance that anyone can hook
2728 up in their home and get access to secure and private services and
2729 communication. The initial deployment platform have been the
2730 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2731 which is a piece of hardware I do not own. So to be able to test what
2732 the current Freedombox setup look like, I had to come up with a way to install
2733 it on some hardware I do have access to. I have rewritten the
2734 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2735 image build framework to use .deb packages instead of only copying
2736 setup into the boot images, and thanks to this rewrite I am able to
2737 set up any machine supported by Debian Wheezy as a Freedombox, using
2738 the previously mentioned deb (and a few support debs for packages
2739 missing in Debian).&lt;/p&gt;
2740
2741 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
2742 scripts
2743 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
2744 and a administrative web interface
2745 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
2746 withsqlite), as well as a privacy enhancing proxy based on
2747 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
2748 (freedombox-privoxy). There is also a web/javascript based XMPP
2749 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
2750 trying (unsuccessfully so far) to talk to the XMPP server
2751 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
2752 web interface is pluggable, and the goal is to use it to enable OpenID
2753 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2754 this is really working yet, see
2755 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
2756 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
2757 on github at the moment. The HTTP proxy is operational out of the
2758 box, and the admin web interface can be used to add/remove plinth
2759 users. I&#39;ve not been able to do anything else with it so far, but
2760 know there are several branches spread around github and other places
2761 with lots of half baked features.&lt;/p&gt;
2762
2763 &lt;p&gt;Anyway, if you want to have a look at the current state, the
2764 following recipes should work to give you a test machine to poke
2765 at.&lt;/p&gt;
2766
2767 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
2768
2769 &lt;ol&gt;
2770
2771 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
2772 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
2773 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
2774 to the Debian installer:&lt;p&gt;
2775 &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;
2776
2777 &lt;li&gt;Answer the few language/region/password questions and pick disk to
2778 install on.&lt;/li&gt;
2779
2780 &lt;li&gt;When the installation is finished and the machine have rebooted a
2781 few times, your Freedombox is ready for testing.&lt;/li&gt;
2782
2783 &lt;/ol&gt;
2784
2785 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
2786
2787 &lt;ol&gt;
2788
2789 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
2790 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
2791 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
2792 &lt;pre&gt;
2793 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
2794 &lt;/pre&gt;&lt;/li&gt;
2795 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
2796 &lt;pre&gt;
2797 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2798 apt-key add -
2799 apt-get update
2800 apt-get install freedombox-setup
2801 /usr/lib/freedombox/setup
2802 &lt;/pre&gt;&lt;/li&gt;
2803 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
2804
2805 &lt;/ol&gt;
2806
2807 &lt;p&gt;You can test it on other architectures too, but because the
2808 freedombox-privoxy package is binary, it will only work as intended on
2809 the architectures where I have had time to build the binary and put it
2810 in my APT repository. But do not let this stop you. It is only a
2811 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
2812
2813 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
2814 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
2815 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
2816 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
2817
2818 &lt;p&gt;Please let me know if this works for you, or if you have any
2819 problems. We gather on the IRC channel
2820 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
2821 irc.debian.org and the
2822 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
2823 mailing list&lt;/a&gt;.&lt;/p&gt;
2824
2825 &lt;p&gt;Once you get your freedombox operational, you can visit
2826 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
2827 welcome screen (dead end - do not be surprised if you are unable to
2828 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
2829 to look at the rest of plinth. The default user is &#39;admin&#39; and the
2830 default password is &#39;secret&#39;.&lt;/p&gt;
2831 </description>
2832 </item>
2833
2834 <item>
2835 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
2836 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
2837 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
2838 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
2839 <description>&lt;p&gt;Earlier, I reported about
2840 &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
2841 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
2842 told by IBM that the original disk should be thrown away. And as
2843 there no longer was a problem if I bricked the firmware, I decided
2844 today to try to install Intel firmware to replace the Lenovo firmware
2845 currently on the disk.&lt;/p&gt;
2846
2847 &lt;p&gt;I searched the Intel site for firmware, and found
2848 &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;
2849 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
2850 according to the site should contain the latest firmware for SSD
2851 disks. I inserted the broken disk in one of my spare laptops and
2852 booted the ISO from a USB stick. The disk was recognized, but the
2853 program claimed the newest firmware already were installed and refused
2854 to insert any Intel firmware. So no change, and the disk is still
2855 unable to handle write load. :( I guess the only way to get them
2856 working would be if Lenovo releases new firmware. No idea how likely
2857 that is. Anyway, just blogging about this test for completeness. I
2858 got a working Samsung disk, and see no point in spending more time on
2859 the broken disks.&lt;/p&gt;
2860 </description>
2861 </item>
2862
2863 <item>
2864 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
2865 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
2866 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
2867 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
2868 <description>&lt;p&gt;Today I switched to
2869 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
2870 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
2871 my new Thinkpad X230, which was delivered with an
2872 &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
2873 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
2874 sustained writes. My hardware supplier have been very forthcoming in
2875 trying to find a solution, and after first trying with another
2876 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
2877 disk instead to fix it once and for all. The Samsung disk survived
2878 the installation of Debian with encrypted disks (filling the disk with
2879 random data during installation killed the first two), and I thus
2880 decided to trust it with my data. I have installed it as a Debian Edu
2881 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2882 server at home using Kerberos and LDAP, and will use it as my work
2883 station from now on.&lt;/p&gt;
2884
2885 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
2886 Debian Wheezy default installation need to be tuned a bit to increase
2887 performance and increase life time of the disk. The Linux kernel and
2888 user space applications do not yet adjust automatically to such
2889 environment. To make it easier for my self, I created a draft Debian
2890 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
2891 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
2892 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
2893 is set up to adjust the setup of the machine by just installing the
2894 package. If there is any non-SSD disk in the machine, the package
2895 will refuse to install, as I did not try to write any logic to sort
2896 file systems in SSD and non-SSD file systems.&lt;/p&gt;
2897
2898 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
2899 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2900 where I set up the machine with one large encrypted partition (in
2901 addition to /boot), put LVM on top of this and set up partitions on
2902 top of this again. See the README file in the package source for the
2903 references I used to pick the settings. At the moment these
2904 parameters are tuned:&lt;/p&gt;
2905
2906 &lt;ul&gt;
2907
2908 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
2909 (adding discard to /etc/crypttab)&lt;/li&gt;
2910
2911 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
2912 this case a cryptsetup partition) by changing issue_discards from
2913 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
2914
2915 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
2916 systems.&lt;/li&gt;
2917
2918 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
2919 /etc/fstab.&lt;/li&gt;
2920
2921 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
2922
2923 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
2924 cron.daily).&lt;/li&gt;
2925
2926 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
2927 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
2928
2929 &lt;/ul&gt;
2930
2931 &lt;p&gt;During installation, I cancelled the part where the installer fill
2932 the disk with random data, as this would kill the SSD performance for
2933 little gain. My goal with the encrypted file system is to ensure
2934 those stealing my laptop end up with a brick and not a working
2935 computer. I have no hope in keeping the really resourceful people
2936 from getting the data on the disk (see
2937 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
2938 Thus I concluded that adding the discard option to crypttab is the
2939 right thing to do.&lt;/p&gt;
2940
2941 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
2942 it for SSD, but others recommended deadline and a benchmark I found
2943 indicated that deadline might be better for interactive use.&lt;/p&gt;
2944
2945 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
2946 and ext4, but read that it would give a performance hit ever time a
2947 file is removed, and thought it best to that that slowdown once a day
2948 instead of during my work.&lt;/p&gt;
2949
2950 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2951 this is already done by Debian Edu.&lt;/p&gt;
2952
2953 &lt;p&gt;I have not yet started on the user space tuning. I expect
2954 iceweasel need some tuning, and perhaps other applications too, but
2955 have not yet had time to investigate those parts.&lt;/p&gt;
2956
2957 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
2958 there.&lt;/p&gt;
2959
2960 &lt;p&gt;As for the answer to the question in the title of this blog post,
2961 as far as I know, the only solution I know about is to replace the
2962 disk. It might be possible to flash it with Intel firmware instead of
2963 the Lenovo firmware. But I have not tried and did not want to do so
2964 without approval from Lenovo as I wanted to keep the warranty on the
2965 disk until a solution was found and they wanted the broken disks
2966 back.&lt;/p&gt;
2967 </description>
2968 </item>
2969
2970 <item>
2971 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2972 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2973 <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>
2974 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2975 <description>&lt;p&gt;A few days ago, I wrote about
2976 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2977 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2978 was dying during installation because it is unable to cope with
2979 sustained write. My supplier is in contact with
2980 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2981 replacement disk to try to fix the problem. They decided to send an
2982 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2983
2984 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2985 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2986 same firmware version as the original. This time my hope raised
2987 slightly as the installation progressed, as the original disk used to
2988 die after 4-7% of the disk was written to, while this time it kept
2989 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2990 died again and I was back on square one. I still do not have a new
2991 laptop with a disk I can trust. I can not live with a disk that might
2992 lock up when I download a new
2993 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2994 other large files. I look forward to hearing from my supplier with
2995 the next proposal from Lenovo.&lt;/p&gt;
2996
2997 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2998 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2999 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3000 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
3001 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3002 P/N 45N8295, P0C38732.&lt;/p&gt;
3003
3004 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
3005 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
3006 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3007 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
3008 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3009 P/N 45N8295, P0C38732.&lt;/p&gt;
3010
3011 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
3012 SA, date and WNPP values. Mentioning all the details here in case
3013 someone is able to use the information to find a way to identify the
3014 failing disk among working ones (if any such working disk actually
3015 exist).&lt;/p&gt;
3016 </description>
3017 </item>
3018
3019 <item>
3020 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
3021 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
3022 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
3023 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
3024 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
3025 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3026 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
3027 member assosiation NUUG&lt;/a&gt; and
3028 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
3029 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
3030 Bitraf&lt;/a&gt;.&lt;/p&gt;
3031
3032 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
3033 welcome, and there is no fee to participate. There is on the other
3034 hand limited space, and only room for 30 people. Please put your name
3035 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
3036 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
3037 </description>
3038 </item>
3039
3040 <item>
3041 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
3042 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
3043 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
3044 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
3045 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
3046 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
3047 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
3048 time to spend on it, and it took a while to find a model I believe
3049 will do the job, but two days ago the replacement finally arrived. I
3050 ended up picking a
3051 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
3052 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3053 a roaming workstation, and it seemed to work flawlessly. But my
3054 second installation with encrypted disk was not as successful. More
3055 on that below.&lt;/p&gt;
3056
3057 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3058 important requirements (robust and with a good keyboard) are never
3059 listed in the feature list. But I did get good help from the search
3060 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3061 allowed me to limit the list of interesting laptops based on my other
3062 requirements. A bit surprising that SSD disk are not disks according
3063 to that search interface, so I had to drop specifying the number of
3064 disks from my search parameters. I also asked around among friends to
3065 get their impression on keyboards and robustness.&lt;/p&gt;
3066
3067 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
3068 X41. I am not quite convinced about the keyboard, as it is
3069 significantly wider than my old keyboard, and I have to stretch my
3070 hand a lot more to reach the edges. But the key response is fairly
3071 good and the individual key shape is fairly easy to handle, so I hope
3072 I will get used to it. My old X40 was starting to fail, and I really
3073 needed a new laptop now. :)&lt;/p&gt;
3074
3075 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
3076 visit to the BIOS during boot it disable it.&lt;/p&gt;
3077
3078 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
3079 lock up during load. And this happen when installing Debian Wheezy
3080 with encrypted disk, while the disk is being filled with random data.
3081 I also tested to install Ubuntu Raring, and it happen there too if I
3082 reenable the code to fill the disk with random data (it is disabled by
3083 default in Ubuntu). And the bug with is already known. It was
3084 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
3085 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
3086 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3087 kernel developers as
3088 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
3089 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
3090 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3091 Lenovo forums, both for
3092 &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
3093 2012-11-10&lt;/a&gt; and for
3094 &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
3095 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
3096 reports state that the disk lock up during use if many writes are done
3097 on the disk, so it is much no use to work around the installation
3098 problem and end up with a computer that can lock up at any moment.
3099 There is even a
3100 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
3101 available&lt;/a&gt; that will lock up the hard drive after running a few
3102 minutes by writing to a file.&lt;/p&gt;
3103
3104 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
3105 contacting PCHELP Norway (request 01D1FDP) which handle support
3106 requests for Lenovo, his first suggestion was to upgrade the disk
3107 firmware. Unfortunately there is no newer firmware available from
3108 Lenovo, as my disk already have the most recent one (version LF1i). I
3109 hope to hear more from him today and hope the problem can be
3110 fixed. :)&lt;/p&gt;
3111 </description>
3112 </item>
3113
3114 <item>
3115 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
3116 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
3117 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
3118 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
3119 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
3120 trusty old Thinkpad X41. Unfortunately I did not have much time to
3121 spend on it, but today the replacement finally arrived. I ended up
3122 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
3123 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
3124 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3125 this, it is installing what I hope will be a more final installation,
3126 with a encrypted hard drive to ensure any dope head stealing it end up
3127 with an expencive door stop.&lt;/p&gt;
3128
3129 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3130 important requirements (robust and with a good keyboard) are never
3131 listed in the feature list. But I did get good help from the search
3132 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3133 allowed me to limit the list of interesting laptops based on my other
3134 requirements. A bit surprising that SSD disk are not disks, so I had
3135 to drop number of disks from my search parameters.&lt;/p&gt;
3136
3137 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
3138 wider than my old keyboard, and I have to stretch my hand a lot more
3139 to reach the edges. But the key response is fairly good and the
3140 individual key shape is fairly easy to handle, so I hope I will get
3141 used to it. My old X40 was starting to fail, and I really needed a
3142 new laptop now. :)&lt;/p&gt;
3143
3144 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
3145 </description>
3146 </item>
3147
3148 <item>
3149 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
3150 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
3151 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
3152 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
3153 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
3154 perfectly capable of, and I have to do it manually to get things
3155 working. One such task is to find out what firmware packages are
3156 needed to get the hardware on my computer working. Most often this
3157 affect the wifi card, but some times it even affect the RAID
3158 controller or the ethernet card. Today I pushed version 0.4 of the
3159 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
3160 including a new script isenkram-autoinstall-firmware handling the
3161 process of asking all the loaded kernel modules what firmware files
3162 they want, find debian packages providing these files and install the
3163 debian packages. Here is a test run on my laptop:&lt;/p&gt;
3164
3165 &lt;p&gt;&lt;pre&gt;
3166 # isenkram-autoinstall-firmware
3167 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3168 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3169 info: locating packages with the requested firmware files
3170 info: Updating APT sources after adding non-free APT source
3171 info: trying to install firmware-ipw2x00
3172 firmware-ipw2x00
3173 firmware-ipw2x00
3174 Preconfiguring packages ...
3175 Selecting previously deselected package firmware-ipw2x00.
3176 (Reading database ... 259727 files and directories currently installed.)
3177 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3178 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
3179 #
3180 &lt;/pre&gt;&lt;/p&gt;
3181
3182 &lt;p&gt;When all the requested firmware is present, a simple message is
3183 printed instead:&lt;/p&gt;
3184
3185 &lt;p&gt;&lt;pre&gt;
3186 # isenkram-autoinstall-firmware
3187 info: did not find any firmware files requested by loaded kernel modules. exiting
3188 #
3189 &lt;/pre&gt;&lt;/p&gt;
3190
3191 &lt;p&gt;It could use some polish, but it is already working well and saving
3192 me some time when setting up new machines. :)&lt;/p&gt;
3193
3194 &lt;p&gt;So, how does it work? It look at the set of currently loaded
3195 kernel modules, and look up each one of them using modinfo, to find
3196 the firmware files listed in the module meta-information. Next, it
3197 download the Contents file from a nearby APT mirror, and search for
3198 the firmware files in this file to locate the package with the
3199 requested firmware file. If the package is in the non-free section, a
3200 non-free APT source is added and the package is installed using
3201 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
3202 machine.&lt;/p&gt;
3203
3204 &lt;p&gt;I hope someone find time to implement a more polished version of
3205 this script as part of the hw-detect debian-installer module, to
3206 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
3207 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
3208 firmware during a PXE install when the packages already are available
3209 from the nearby Debian mirror.&lt;/p&gt;
3210 </description>
3211 </item>
3212
3213 <item>
3214 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
3215 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
3216 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
3217 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
3218 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3219 the screen just turn black when Linux boot, either during installation
3220 or on first boot from the hard disk. I&#39;ve seen it once in a while the
3221 last few years, but only recently understood the cause. I&#39;ve seen it
3222 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3223 The reason seem to be in the wiring of some laptops. The system to
3224 control the screen background light is inverted, so when Linux try to
3225 turn the brightness fully on, it end up turning it off instead. I do
3226 not know which Linux drivers are affected, but this post is about the
3227 i915 driver used by the
3228 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3229 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
3230
3231 &lt;p&gt;The problem can be worked around two ways. Either by adding
3232 i915.invert_brightness=1 as a kernel option, or by adding a file in
3233 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
3234 option when it load the i915 kernel module. On Debian and Ubuntu, it
3235 can be done by running these commands as root:&lt;/p&gt;
3236
3237 &lt;pre&gt;
3238 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
3239 update-initramfs -u -k all
3240 &lt;/pre&gt;
3241
3242 &lt;p&gt;Since March 2012 there is
3243 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
3244 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
3245 hardware have this problem, and get the driver to invert the
3246 brightness setting automatically. To use it, one need to add a row in
3247 &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
3248 intel_quirks array&lt;/a&gt; in the driver source
3249 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
3250 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
3251 number (vendor number 8086 is assumed) and subdevice vendor and device
3252 number.&lt;/p&gt;
3253
3254 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
3255 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
3256
3257 &lt;p&gt;&lt;pre&gt;
3258 00:02.0 VGA compatible controller [0300]: Intel Corporation \
3259 3rd Gen Core processor Graphics Controller [8086:0156] \
3260 (rev 09) (prog-if 00 [VGA controller])
3261 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
3262 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3263 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3264 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
3265 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
3266 Latency: 0
3267 Interrupt: pin A routed to IRQ 42
3268 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
3269 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
3270 Region 4: I/O ports at 4000 [size=64]
3271 Expansion ROM at &lt;unassigned&gt; [disabled]
3272 Capabilities: &lt;access denied&gt;
3273 Kernel driver in use: i915
3274 &lt;/pre&gt;&lt;/p&gt;
3275
3276 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
3277
3278 &lt;p&gt;&lt;pre&gt;
3279 struct intel_quirk intel_quirks[] = {
3280 ...
3281 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3282 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
3283 ...
3284 }
3285 &lt;/pre&gt;&lt;/p&gt;
3286
3287 &lt;p&gt;According to the kernel module instructions (as seen using
3288 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
3289 invert_brightness flag should be sent to the
3290 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
3291 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
3292 developers. But my email about the laptop sent 2013-06-03 have not
3293 yet shown up in
3294 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
3295 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
3296 emails from non-subscribers. Because of this, I sent my patch also to
3297 the Debian bug tracking system instead as
3298 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
3299 sure the patch is not lost.&lt;/p&gt;
3300
3301 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
3302 with this problem working properly with Linux. If you use Gnome, your
3303 worries should be over at this point. But if you use KDE, there is
3304 something in KDE ignoring the invert_brightness setting and turning on
3305 the screen during login. I&#39;ve reported it to Debian as
3306 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
3307 have no idea yet how to figure out exactly what subsystem is doing
3308 this. Perhaps you can help? Perhaps you know what the Gnome
3309 developers did to handle this, and this can give a clue to the KDE
3310 developers? Or you know where in KDE the screen brightness is changed
3311 during login? If so, please update the BTS report (or get in touch if
3312 you do not know how to update BTS).&lt;/p&gt;
3313
3314 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
3315 acpi_backlight=vendor, to disable ACPI backlight support completely,
3316 as the ACPI information on the machine is trash and it is better to
3317 leave it to the intel video driver to control the screen
3318 backlight.&lt;/p&gt;
3319 </description>
3320 </item>
3321
3322 <item>
3323 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
3324 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
3325 <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>
3326 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
3327 <description>&lt;p&gt;Two days ago, I asked
3328 &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
3329 I could install Linux on a Packard Bell EasyNote LV computer
3330 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
3331 with the obstacles put in the way of Linux users on a laptop with UEFI
3332 and Windows 8.&lt;/p&gt;
3333
3334 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
3335 secure booting or fast boot. I suspect fast boot was the problem,
3336 causing the firmware to boot directly from HD without considering any
3337 key presses and alternative devices, but do not know UEFI settings
3338 enough to tell.&lt;/p&gt;
3339
3340 &lt;p&gt;There is no way to install Linux on the machine in question without
3341 opening the box and disconnecting the hard drive! This is as far as I
3342 can tell, the only way to get access to the firmware setup menu
3343 without accepting the Windows 8 license agreement. I am told (and
3344 found description on how to) that it is possible to configure the
3345 firmware setup once booted into Windows 8. But as I believe the terms
3346 of that agreement are completely unacceptable, accepting the license
3347 was never an alternative. I do not enter agreements I do not intend
3348 to follow.&lt;/p&gt;
3349
3350 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3351 waste many hours on this, but luckily there was a way to get it to
3352 work. But I would not recommend it to anyone planning to run Linux on
3353 it, and I have become sceptical to Windows 8 certified laptops. Is
3354 this the way Linux will be forced out of the market place, by making
3355 it close to impossible for &quot;normal&quot; users to install Linux without
3356 accepting the Microsoft Windows license terms? Or at least not
3357 without risking to loose the warranty?&lt;/p&gt;
3358
3359 &lt;p&gt;I&#39;ve updated the
3360 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3361 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3362 do not have to struggle as much as I did to get Linux into the
3363 machine.&lt;/p&gt;
3364
3365 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3366 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3367 </description>
3368 </item>
3369
3370 <item>
3371 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3372 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3373 <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>
3374 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3375 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3376 new laptops for my parents and a few others. I bought Packard Bell
3377 Easynote LV to run Kubuntu on and use as their home computer. But I
3378 am completely unable to figure out how to install Linux on it. The
3379 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3380 instead of a BIOS to boot.&lt;/p&gt;
3381
3382 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3383 to get it to boot the Linux installer from my USB stick. I have yet
3384 to try the DVD install, and still hope it will work. when I turn on
3385 the computer, there is no information on what buttons to press to get
3386 the normal boot menu. I expect to get some boot menu to select PXE or
3387 USB stick booting. When booting, it first ask for the language to
3388 use, then for some regional settings, and finally if I will accept the
3389 Windows 8 terms of use. As these terms are completely unacceptable to
3390 me, I have no other choice but to turn off the computer and try again
3391 to get it to boot the Linux installer.&lt;/p&gt;
3392
3393 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3394 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3395 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3396 installed on this machine, please get in touch or update that wiki
3397 page. If I can&#39;t find a way to install Linux, I will have to return
3398 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3399
3400 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3401 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3402 on new Laptops?&lt;/p&gt;
3403 </description>
3404 </item>
3405
3406 <item>
3407 <title>How to transform a Debian based system to a Debian Edu installation</title>
3408 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3409 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3410 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3411 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3412 an operating system based on Debian intended for use in schools. It
3413 contain a turn-key solution for the computer network provided to
3414 pupils in the primary schools. It provide both the central server,
3415 network boot servers and desktop environments with heaps of
3416 educational software. The project was founded almost 12 years ago,
3417 2001-07-02. If you want to support the project, which is in need for
3418 cash to fund developer gatherings and other project related activity,
3419 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3420 donate some money&lt;/a&gt;.
3421
3422 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3423 lists and elsewhere, is the question on how to transform a Debian or
3424 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3425 hard, and last week I wrote a script to replicate the steps done by
3426 the Debian Edu installer.&lt;/p&gt;
3427
3428 &lt;p&gt;The script,
3429 &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;
3430 in the debian-edu-config package, will go through these six steps and
3431 transform an existing Debian Wheezy or Ubuntu (untested) installation
3432 into a Debian Edu Workstation:&lt;/p&gt;
3433
3434 &lt;ol&gt;
3435
3436 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3437 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3438 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3439 our configuration.&lt;/li&gt;
3440 &lt;li&gt;Preseed debconf database with profile setup in
3441 /etc/debian-edu/config, and run tasksel to install packages
3442 according to the profile specified in the config above,
3443 overriding some of the Debian automation machinery.&lt;/li&gt;
3444 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3445 that could not be done using preseeding.&lt;/li&gt;
3446 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3447
3448 &lt;/ol&gt;
3449
3450 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3451 replicated like this. Disk partitioning and LVM setup, for example.
3452 So this script just assume there is enough disk space to install all
3453 the needed packages.&lt;/p&gt;
3454
3455 &lt;p&gt;The script was created to help a Debian Edu student working on
3456 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3457 Debian Edu client, and using it he can take the existing
3458 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3459 transform it into a fully functioning Debian Edu Workstation (or
3460 Roaming Workstation, or whatever :).&lt;/p&gt;
3461
3462 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3463 If a LXDE based Roaming workstation is wanted instead, modify the
3464 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3465
3466 &lt;p&gt;&lt;pre&gt;
3467 PROFILE=&quot;Roaming-Workstation&quot;
3468 DESKTOP=&quot;lxde&quot;
3469 &lt;/pre&gt;&lt;/p&gt;
3470
3471 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3472 the cloud, by starting with a virtual Debian installation at some
3473 virtual hosting service and setting up all the services on first
3474 boot.&lt;/p&gt;
3475 </description>
3476 </item>
3477
3478 <item>
3479 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3480 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3481 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3482 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3483 <description>&lt;P&gt;In January,
3484 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3485 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3486 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3487 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3488 marvellous construction system from Denmark. We also created
3489 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3490 a place to take notes and write down our plans and hopes. And several
3491 people showed up to help. I was very happy to see the effect of my
3492 call. Since the small start, we have a debtags tag
3493 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3494 tag for LEGO related packages, and now count 10 packages related to
3495 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3496
3497 &lt;p&gt;&lt;table&gt;
3498 &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;
3499 &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;
3500 &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;
3501 &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;
3502 &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;
3503 &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;
3504 &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;
3505 &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;
3506 &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;
3507 &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;
3508 &lt;/table&gt;&lt;/p&gt;
3509
3510 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3511 currently available in Jessie/testing. leocad is so far only
3512 available in experimental.&lt;/p&gt;
3513
3514 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3515 adding the rest of the great free software tools available on Linux
3516 for LEGO designers.&lt;/p&gt;
3517 </description>
3518 </item>
3519
3520 <item>
3521 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3522 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3523 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3524 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3525 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3526 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3527 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3528 Debian release, and I expect to move my machines at home over to it fairly
3529 soon.&lt;/p&gt;
3530
3531 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3532 in particular make me very happy to see included. The
3533 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3534 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3535 included for the first time. Alongside similar programs like
3536 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3537 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3538 it allow for visual programming where syntax errors can not happen,
3539 and a friendly programming environment for learning to control the
3540 computer. Scratch will also be included in the next release of Debian
3541 Edu.&lt;/a&gt;
3542
3543 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3544 Edu/Skolelinux release too. The
3545 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3546 alpha release&lt;/a&gt; went out last week, and the next should soon
3547 follow.&lt;p&gt;
3548 </description>
3549 </item>
3550
3551 <item>
3552 <title>Isenkram 0.2 finally in the Debian archive</title>
3553 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3554 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3555 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3556 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3557 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3558 for many months. I uploaded it to the Debian experimental suite
3559 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3560
3561 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3562 install to work with a pluggable hardware device. The suggestion pop
3563 up when the device is plugged in. For example if a Lego Mindstorm NXT
3564 is inserted, it will suggest to install the program needed to program
3565 the NXT controller. Give it a go, and report bugs and suggestions to
3566 BTS. :)&lt;/p&gt;
3567 </description>
3568 </item>
3569
3570 <item>
3571 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3572 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3573 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3574 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3575 <description>&lt;p&gt;My
3576 &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
3577 bitcoin related blog post&lt;/a&gt; mentioned that the new
3578 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3579 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3580 2013-01-19, and have been available in unstable since then. It was
3581 automatically copied to Ubuntu, and is available in their Raring
3582 version too.&lt;/p&gt;
3583
3584 &lt;p&gt;But there is a strange problem with the build that block this new
3585 version from being available on the i386 and kfreebsd-i386
3586 architectures. For some strange reason, the autobuilders in Debian
3587 for these architectures fail to run the test suite on these
3588 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3589 We are so far unable to reproduce it when building it manually, and
3590 no-one have been able to propose a fix. If you got an idea what is
3591 failing, please let us know via the BTS.&lt;/p&gt;
3592
3593 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3594 I often run low on disk space, is the fact that the client will exit
3595 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3596 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3597 it. :)&lt;/p&gt;
3598
3599 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3600 activities, please send Bitcoin donations to my address
3601 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3602 </description>
3603 </item>
3604
3605 <item>
3606 <title>Welcome to the world, Isenkram!</title>
3607 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3608 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3609 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3610 <description>&lt;p&gt;Yesterday, I
3611 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3612 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3613 pluggable hardware devices, which I
3614 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3615 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3616 up, and caused me to really want to to open up the development to more
3617 people. But before I did this, I want to come up with a sensible name
3618 for this project. Today I finally decided on a new name, and I have
3619 renamed the project from hw-support-handler to this new name. In the
3620 process, I moved the source to git and made it available as a
3621 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3622 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3623 To fetch and build the latest version of the source, use&lt;/p&gt;
3624
3625 &lt;pre&gt;
3626 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3627 cd isenkram &amp;&amp; git-buildpackage -us -uc
3628 &lt;/pre&gt;
3629
3630 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3631 want to hack on the source or improve the package, please go ahead.
3632 But please talk to me first on IRC or via email before you do major
3633 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3634
3635 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3636 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3637 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3638 the German word eisenkram, for those that are familiar with that
3639 word.&lt;/p&gt;
3640
3641 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3642 instructions, to avoid confusing people with an error from the signing
3643 process.&lt;/p&gt;
3644
3645 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3646 clone argument to avoid the need for authentication.&lt;/p&gt;
3647 </description>
3648 </item>
3649
3650 <item>
3651 <title>First prototype ready making hardware easier to use in Debian</title>
3652 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3653 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3654 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3655 <description>&lt;p&gt;Early this month I set out to try to
3656 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3657 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3658 prototype is working, and it is ready for a larger audience. To test
3659 it, fetch the
3660 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3661 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3662 package. You might have to log out and in again activate the
3663 autostart script.&lt;/p&gt;
3664
3665 &lt;p&gt;The design is simple:&lt;/p&gt;
3666
3667 &lt;ul&gt;
3668
3669 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3670 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3671
3672 &lt;li&gt;This program listen for kernel events about new hardware (directly
3673 from the kernel like udev does), not using HAL dbus events as I
3674 initially did.&lt;/li&gt;
3675
3676 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3677 the APT database, a database
3678 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3679 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3680
3681 &lt;li&gt;If a package is mapped to the hardware in question, the package
3682 isn&#39;t installed yet and this is the first time the hardware was
3683 plugged in, show a desktop notification suggesting to install the
3684 package or packages.&lt;/li&gt;
3685
3686 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3687 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3688
3689 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3690 package while showing progress information in a window.&lt;/li&gt;
3691
3692 &lt;/ul&gt;
3693
3694 &lt;p&gt;I still need to come up with a better name for the system. Here
3695 are some screen shots showing the prototype in action. First the
3696 notification, then the password request, and finally the request to
3697 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3698
3699 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3700 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3701 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3702 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3703 &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;
3704
3705 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3706 is already useful. The database of hardware to package mappings also
3707 need more work. It is currently compatible with the Ubuntu way of
3708 storing such information in the package control file, but could be
3709 changed to use other formats instead or in addition to the current
3710 method. I&#39;ve dropped the use of discover for this mapping, as the
3711 modalias approach is more flexible and easier to use on Linux as long
3712 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3713
3714 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3715 here is the command required to check out and build the source: Use
3716 &#39;&lt;tt&gt;svn checkout
3717 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3718 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3719 devscripts package.&lt;/p&gt;
3720
3721 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3722 renamed to Isenkram and the source moved from the Debian Edu
3723 subversion repository to a Debian collab-maint git repository. See
3724 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3725 instructions&lt;/a&gt; for details.&lt;/p&gt;
3726 </description>
3727 </item>
3728
3729 <item>
3730 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3731 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3732 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3733 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3734 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3735 suddenly in bed. With a quiet whimper, it went completely quiet and
3736 black. The power button was no longer able to turn it on. It was a
3737 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3738 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3739 Compaq I had before that. Now I need to find a replacement. To keep
3740 going during Christmas, I moved the one year old SSD disk to my old
3741 X40 where it fitted (only one I had left that could use it), but it is
3742 not a durable solution.
3743
3744 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
3745 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
3746
3747 &lt;ul&gt;
3748
3749 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
3750 than A4).&lt;/li&gt;
3751 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
3752 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
3753 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
3754 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
3755 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
3756 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
3757 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
3758 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
3759 size).&lt;/li&gt;
3760 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
3761 X.org packages.&lt;/li&gt;
3762 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
3763 the time).
3764
3765 &lt;/ul&gt;
3766
3767 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
3768 list. The reason is simply that the specifications on laptops the
3769 last 10-15 years have been sufficient for my needs, and I have to look
3770 at other features to choose my laptop. But are there still made as
3771 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3772 robust, and Thinkpads seem to be heading in the wrong direction since
3773 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
3774 still be useful.&lt;/p&gt;
3775
3776 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
3777 external keyboard? I&#39;ll have to check the
3778 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
3779 well-supported laptops, or perhaps just buy one preinstalled from one
3780 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
3781 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
3782 </description>
3783 </item>
3784
3785 <item>
3786 <title>How to find a browser plugin supporting a given MIME type</title>
3787 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
3788 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
3789 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
3790 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
3791 install to get support for a given MIME type. Thanks to
3792 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
3793 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
3794 Unfortunately, not very many packages provide the needed meta
3795 information, Anyway, here is a small script to look up all browser
3796 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
3797
3798 &lt;pre&gt;
3799 #!/usr/bin/python
3800 import sys
3801 import apt
3802 def pkgs_handling_mimetype(mimetype):
3803 cache = apt.Cache()
3804 cache.open(None)
3805 thepkgs = []
3806 for pkg in cache:
3807 version = pkg.candidate
3808 if version is None:
3809 version = pkg.installed
3810 if version is None:
3811 continue
3812 record = version.record
3813 if not record.has_key(&#39;Npp-MimeType&#39;):
3814 continue
3815 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
3816 for t in mime_types:
3817 t = t.rstrip().strip()
3818 if t == mimetype:
3819 thepkgs.append(pkg.name)
3820 return thepkgs
3821 mimetype = &quot;audio/ogg&quot;
3822 if 1 &lt; len(sys.argv):
3823 mimetype = sys.argv[1]
3824 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
3825 for pkg in pkgs_handling_mimetype(mimetype):
3826 print &quot; %s&quot; %pkg
3827 &lt;/pre&gt;
3828
3829 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
3830
3831 &lt;pre&gt;
3832 % ./apt-find-browserplug-for-mimetype
3833 Browser plugin packages supporting audio/ogg:
3834 gecko-mediaplayer
3835 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3836 Browser plugin packages supporting application/x-shockwave-flash:
3837 browser-plugin-gnash
3838 %
3839 &lt;/pre&gt;
3840
3841 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
3842 itself to query for plugins and propose to install the needed
3843 packages. It would be great if Debian supported such feature too. Is
3844 anyone working on adding it?&lt;/p&gt;
3845
3846 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
3847 request for icweasel support for this feature is
3848 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
3849 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
3850 of manpower and wish for a different design is the reason thus feature
3851 is not yet in iceweasel from Debian.&lt;/p&gt;
3852 </description>
3853 </item>
3854
3855 <item>
3856 <title>What is the most supported MIME type in Debian?</title>
3857 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
3858 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
3859 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
3860 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
3861 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
3862 proposal to make it possible for a Desktop application to propose to
3863 the user some package to install to gain support for a given MIME
3864 type, font, library etc. that is currently missing. With such
3865 mechanism in place, it would be possible for the desktop to
3866 automatically propose and install leocad if some LDraw file is
3867 downloaded by the browser.&lt;/p&gt;
3868
3869 &lt;p&gt;To get some idea about the current content of the archive, I decided
3870 to write a simple program to extract all .desktop files from the
3871 Debian archive and look up the claimed MIME support there. The result
3872 can be found on the
3873 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
3874 site&lt;/a&gt;. Using the collected information, it become possible to
3875 answer the question in the title. Here are the 20 most supported MIME
3876 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3877 The complete list is available from the link above.&lt;/p&gt;
3878
3879 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
3880
3881 &lt;pre&gt;
3882 count MIME type
3883 ----- -----------------------
3884 32 text/plain
3885 30 audio/mpeg
3886 29 image/png
3887 28 image/jpeg
3888 27 application/ogg
3889 26 audio/x-mp3
3890 25 image/tiff
3891 25 image/gif
3892 22 image/bmp
3893 22 audio/x-wav
3894 20 audio/x-flac
3895 19 audio/x-mpegurl
3896 18 video/x-ms-asf
3897 18 audio/x-musepack
3898 18 audio/x-mpeg
3899 18 application/x-ogg
3900 17 video/mpeg
3901 17 audio/x-scpls
3902 17 audio/ogg
3903 16 video/x-ms-wmv
3904 &lt;/pre&gt;
3905
3906 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
3907
3908 &lt;pre&gt;
3909 count MIME type
3910 ----- -----------------------
3911 33 text/plain
3912 32 image/png
3913 32 image/jpeg
3914 29 audio/mpeg
3915 27 image/gif
3916 26 image/tiff
3917 26 application/ogg
3918 25 audio/x-mp3
3919 22 image/bmp
3920 21 audio/x-wav
3921 19 audio/x-mpegurl
3922 19 audio/x-mpeg
3923 18 video/mpeg
3924 18 audio/x-scpls
3925 18 audio/x-flac
3926 18 application/x-ogg
3927 17 video/x-ms-asf
3928 17 text/html
3929 17 audio/x-musepack
3930 16 image/x-xbitmap
3931 &lt;/pre&gt;
3932
3933 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
3934
3935 &lt;pre&gt;
3936 count MIME type
3937 ----- -----------------------
3938 31 text/plain
3939 31 image/png
3940 31 image/jpeg
3941 29 audio/mpeg
3942 28 application/ogg
3943 27 image/gif
3944 26 image/tiff
3945 26 audio/x-mp3
3946 23 audio/x-wav
3947 22 image/bmp
3948 21 audio/x-flac
3949 20 audio/x-mpegurl
3950 19 audio/x-mpeg
3951 18 video/x-ms-asf
3952 18 video/mpeg
3953 18 audio/x-scpls
3954 18 application/x-ogg
3955 17 audio/x-musepack
3956 16 video/x-ms-wmv
3957 16 video/x-msvideo
3958 &lt;/pre&gt;
3959
3960 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3961 information mentioned in DEP-11. I have not yet had time to look at
3962 it, but hope the PackageKit people in Debian are on top of these
3963 issues.&lt;/p&gt;
3964
3965 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3966 discovering a typo in my script.&lt;/p&gt;
3967 </description>
3968 </item>
3969
3970 <item>
3971 <title>Using modalias info to find packages handling my hardware</title>
3972 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3973 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3974 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3975 <description>&lt;p&gt;Yesterday, I wrote about the
3976 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3977 values provided by the Linux kernel&lt;/a&gt; following my hope for
3978 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3979 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3980 modalias values attached to package names can be used to map packages
3981 to hardware. This allow the system to look up and suggest relevant
3982 packages when I plug in some new hardware into my machine, and replace
3983 discover and discover-data as the database used to map hardware to
3984 packages.&lt;/p&gt;
3985
3986 &lt;p&gt;I create a modaliases file with entries like the following,
3987 containing package name, kernel module name (if relevant, otherwise
3988 the package name) and globs matching the relevant hardware
3989 modalias.&lt;/p&gt;
3990
3991 &lt;p&gt;&lt;blockquote&gt;
3992 Package: package-name
3993 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3994 &lt;/blockquote&gt;&lt;/p&gt;
3995
3996 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3997 for a given modalias value using this file.&lt;/p&gt;
3998
3999 &lt;p&gt;An entry like this would suggest the video and picture application
4000 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
4001
4002 &lt;p&gt;&lt;blockquote&gt;
4003 Package: cheese
4004 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
4005 &lt;/blockquote&gt;&lt;/p&gt;
4006
4007 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
4008 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
4009
4010 &lt;p&gt;&lt;blockquote&gt;
4011 Package: pcmciautils
4012 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4013 &lt;/blockquote&gt;&lt;/p&gt;
4014
4015 &lt;p&gt;An entry like this would suggest the package colorhug-client when
4016 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
4017
4018 &lt;p&gt;&lt;blockquote&gt;
4019 Package: colorhug-client
4020 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
4021 &lt;/blockquote&gt;&lt;/p&gt;
4022
4023 &lt;p&gt;I believe the format is compatible with the format of the Packages
4024 file in the Debian archive. Ubuntu already uses their Packages file
4025 to store their mappings from packages to hardware.&lt;/p&gt;
4026
4027 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
4028 announce the hardware it support in a way my prototype understand.
4029 This allow those publishing packages in an APT source outside the
4030 Debian archive as well as those backporting packages to make sure the
4031 hardware mapping are included in the package meta information. I&#39;ve
4032 tested such header in the pymissile package, and its modalias mapping
4033 is working as it should with my prototype. It even made it to Ubuntu
4034 Raring.&lt;/p&gt;
4035
4036 &lt;p&gt;To test if it was possible to look up supported hardware using only
4037 the shell tools available in the Debian installer, I wrote a shell
4038 implementation of the lookup code. The idea is to create files for
4039 each modalias and let the shell do the matching. Please check out and
4040 try the
4041 &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;
4042 shell script. It run without any extra dependencies and fetch the
4043 hardware mappings from the Debian archive and the subversion
4044 repository where I currently work on my prototype.&lt;/p&gt;
4045
4046 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
4047 install yubikey-personalization:&lt;/p&gt;
4048
4049 &lt;p&gt;&lt;blockquote&gt;
4050 % ./hw-support-lookup
4051 &lt;br&gt;yubikey-personalization
4052 &lt;br&gt;%
4053 &lt;/blockquote&gt;&lt;/p&gt;
4054
4055 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4056 propose to install the pcmciautils package:&lt;/p&gt;
4057
4058 &lt;p&gt;&lt;blockquote&gt;
4059 % ./hw-support-lookup
4060 &lt;br&gt;pcmciautils
4061 &lt;br&gt;%
4062 &lt;/blockquote&gt;&lt;/p&gt;
4063
4064 &lt;p&gt;If you know of any hardware-package mapping that should be added to
4065 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
4066 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
4067
4068 &lt;p&gt;It could be possible to generate several of the mappings between
4069 packages and hardware. One source would be to look at packages with
4070 kernel modules, ie packages with *.ko files in /lib/modules/, and
4071 extract their modalias information. Another would be to look at
4072 packages with udev rules, ie packages with files in
4073 /lib/udev/rules.d/, and extract their vendor/model information to
4074 generate a modalias matching rule. I have not tested any of these to
4075 see if it work.&lt;/p&gt;
4076
4077 &lt;p&gt;If you want to help implementing a system to let us propose what
4078 packages to install when new hardware is plugged into a Debian
4079 machine, please send me an email or talk to me on
4080 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4081 </description>
4082 </item>
4083
4084 <item>
4085 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
4086 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
4087 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
4088 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
4089 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
4090 information, to find the packages that support a given piece of
4091 hardware, I refreshed my memory regarding modalias values, and decided
4092 to document the details. Here are my findings so far, also available
4093 in
4094 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4095 Debian Edu subversion repository&lt;/a&gt;:
4096
4097 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
4098
4099 &lt;p&gt;This document try to explain what the different types of modalias
4100 values stands for. It is in part based on information from
4101 &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;,
4102 &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;,
4103 &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
4104 &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;.
4105
4106 &lt;p&gt;The modalias entries for a given Linux machine can be found using
4107 this shell script:&lt;/p&gt;
4108
4109 &lt;pre&gt;
4110 find /sys -name modalias -print0 | xargs -0 cat | sort -u
4111 &lt;/pre&gt;
4112
4113 &lt;p&gt;The supported modalias globs for a given kernel module can be found
4114 using modinfo:&lt;/p&gt;
4115
4116 &lt;pre&gt;
4117 % /sbin/modinfo psmouse | grep alias:
4118 alias: serio:ty05pr*id*ex*
4119 alias: serio:ty01pr*id*ex*
4120 %
4121 &lt;/pre&gt;
4122
4123 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
4124
4125 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
4126 Bridge memory controller:&lt;/p&gt;
4127
4128 &lt;p&gt;&lt;blockquote&gt;
4129 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4130 &lt;/blockquote&gt;&lt;/p&gt;
4131
4132 &lt;p&gt;This represent these values:&lt;/p&gt;
4133
4134 &lt;pre&gt;
4135 v 00008086 (vendor)
4136 d 00002770 (device)
4137 sv 00001028 (subvendor)
4138 sd 000001AD (subdevice)
4139 bc 06 (bus class)
4140 sc 00 (bus subclass)
4141 i 00 (interface)
4142 &lt;/pre&gt;
4143
4144 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
4145 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
4146 0600. The 0600 class is a host bridge. Other useful bus values are
4147 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
4148
4149 &lt;p&gt;Not sure how to figure out the interface value, nor what it
4150 means.&lt;/p&gt;
4151
4152 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
4153
4154 &lt;p&gt;Some typical USB entries can look like this. This is an internal
4155 USB hub in a laptop:&lt;/p&gt;
4156
4157 &lt;p&gt;&lt;blockquote&gt;
4158 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4159 &lt;/blockquote&gt;&lt;/p&gt;
4160
4161 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
4162
4163 &lt;pre&gt;
4164 v 1D6B (device vendor)
4165 p 0001 (device product)
4166 d 0206 (bcddevice)
4167 dc 09 (device class)
4168 dsc 00 (device subclass)
4169 dp 00 (device protocol)
4170 ic 09 (interface class)
4171 isc 00 (interface subclass)
4172 ip 00 (interface protocol)
4173 &lt;/pre&gt;
4174
4175 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
4176 class is in the interface class section. For a simple USB web camera,
4177 these alias entries show up:&lt;/p&gt;
4178
4179 &lt;p&gt;&lt;blockquote&gt;
4180 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4181 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4182 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4183 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4184 &lt;/blockquote&gt;&lt;/p&gt;
4185
4186 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
4187 camera), 0101 is audio control device and 0102 is audio streaming (aka
4188 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
4189
4190 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
4191
4192 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
4193 receiver in a Thinkpad X40:&lt;/p&gt;
4194
4195 &lt;p&gt;&lt;blockquote&gt;
4196 acpi:IBM0071:PNP0511:
4197 &lt;/blockquote&gt;&lt;/p&gt;
4198
4199 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
4200
4201 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
4202
4203 &lt;p&gt;The DMI table contain lots of information about the computer case
4204 and model. This is an entry for a IBM Thinkpad X40, fetched from
4205 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
4206
4207 &lt;p&gt;&lt;blockquote&gt;
4208 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4209 &lt;/blockquote&gt;&lt;/p&gt;
4210
4211 &lt;p&gt;The values present are&lt;/p&gt;
4212
4213 &lt;pre&gt;
4214 bvn IBM (BIOS vendor)
4215 bvr 1UETB6WW(1.66) (BIOS version)
4216 bd 06/15/2005 (BIOS date)
4217 svn IBM (system vendor)
4218 pn 2371H4G (product name)
4219 pvr ThinkPadX40 (product version)
4220 rvn IBM (board vendor)
4221 rn 2371H4G (board name)
4222 rvr NotAvailable (board version)
4223 cvn IBM (chassis vendor)
4224 ct 10 (chassis type)
4225 cvr NotAvailable (chassis version)
4226 &lt;/pre&gt;
4227
4228 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
4229 found in the dmidecode source:&lt;/p&gt;
4230
4231 &lt;pre&gt;
4232 3 Desktop
4233 4 Low Profile Desktop
4234 5 Pizza Box
4235 6 Mini Tower
4236 7 Tower
4237 8 Portable
4238 9 Laptop
4239 10 Notebook
4240 11 Hand Held
4241 12 Docking Station
4242 13 All In One
4243 14 Sub Notebook
4244 15 Space-saving
4245 16 Lunch Box
4246 17 Main Server Chassis
4247 18 Expansion Chassis
4248 19 Sub Chassis
4249 20 Bus Expansion Chassis
4250 21 Peripheral Chassis
4251 22 RAID Chassis
4252 23 Rack Mount Chassis
4253 24 Sealed-case PC
4254 25 Multi-system
4255 26 CompactPCI
4256 27 AdvancedTCA
4257 28 Blade
4258 29 Blade Enclosing
4259 &lt;/pre&gt;
4260
4261 &lt;p&gt;The chassis type values are not always accurately set in the DMI
4262 table. For example my home server is a tower, but the DMI modalias
4263 claim it is a desktop.&lt;/p&gt;
4264
4265 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
4266
4267 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
4268 test machine:&lt;/p&gt;
4269
4270 &lt;p&gt;&lt;blockquote&gt;
4271 serio:ty01pr00id00ex00
4272 &lt;/blockquote&gt;&lt;/p&gt;
4273
4274 &lt;p&gt;The values present are&lt;/p&gt;
4275
4276 &lt;pre&gt;
4277 ty 01 (type)
4278 pr 00 (prototype)
4279 id 00 (id)
4280 ex 00 (extra)
4281 &lt;/pre&gt;
4282
4283 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
4284 the valid values are.&lt;/p&gt;
4285
4286 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
4287
4288 &lt;p&gt;There are heaps of other modalias subtypes according to
4289 file2alias.c. There is the rest of the list from that source: amba,
4290 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4291 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4292 vmbus, x86cpu and zorro. I did not spend time documenting all of
4293 these, as they do not seem relevant for my intended use with mapping
4294 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
4295
4296 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
4297
4298 &lt;p&gt;To check which kernel modules provide support for a given modalias,
4299 one can use the following shell script:&lt;/p&gt;
4300
4301 &lt;pre&gt;
4302 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
4303 echo &quot;$id&quot; ; \
4304 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
4305 done
4306 &lt;/pre&gt;
4307
4308 &lt;p&gt;The output can look like this (only the first few entries as the
4309 list is very long on my test machine):&lt;/p&gt;
4310
4311 &lt;pre&gt;
4312 acpi:ACPI0003:
4313 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
4314 acpi:device:
4315 FATAL: Module acpi:device: not found.
4316 acpi:IBM0068:
4317 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
4318 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
4319 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
4320 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4321 acpi:IBM0071:PNP0511:
4322 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
4323 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
4324 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
4325 [...]
4326 &lt;/pre&gt;
4327
4328 &lt;p&gt;If you want to help implementing a system to let us propose what
4329 packages to install when new hardware is plugged into a Debian
4330 machine, please send me an email or talk to me on
4331 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4332
4333 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
4334 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
4335 in /sys/ with space in them.&lt;/p&gt;
4336 </description>
4337 </item>
4338
4339 <item>
4340 <title>Moved the pymissile Debian packaging to collab-maint</title>
4341 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4342 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4343 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4344 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4345 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4346 Launcher and updated the Debian package
4347 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4348 sure udev will fix the device permissions when it is plugged in. I
4349 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4350 hopefully make the package be proposed by jockey in Ubuntu when a user
4351 plug in his rocket launcher. In the process I moved the source to a
4352 git repository under collab-maint, to make it easier for any DD to
4353 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4354 is not very active, but the software still work for me even after five
4355 years of relative silence. The new git repository is not listed in
4356 the uploaded package yet, because I want to test the other changes a
4357 bit more before I upload the new version. If you want to check out
4358 the new version with a .desktop file included, visit the
4359 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4360 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4361 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4362 </description>
4363 </item>
4364
4365 <item>
4366 <title>Lets make hardware dongles easier to use in Debian</title>
4367 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4368 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4369 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4370 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4371 general, is that there is a great package management system with the
4372 ability to automatically install software packages by downloading them
4373 from the distribution mirrors, but no way to get it to automatically
4374 install the packages I need to use the hardware I plug into my
4375 machine. Even if the package to use it is easily available from the
4376 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4377 suggest to automatically install the python-nxt, nbc and t2n packages
4378 I need to talk to it. When I plug in a Yubikey, it could propose the
4379 yubikey-personalization package. The information required to do this
4380 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4381
4382 &lt;p&gt;Some years ago, I proposed to
4383 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4384 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4385 simple:
4386
4387 &lt;ul&gt;
4388
4389 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4390 starting when a user log in.&lt;/li&gt;
4391
4392 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4393 hardware is inserted into the computer.&lt;/li&gt;
4394
4395 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4396 database mapping to packages, and take note of any non-installed
4397 packages.&lt;/li&gt;
4398
4399 &lt;li&gt;Show a message to the user proposing to install the discovered
4400 package, and make it easy to install it.&lt;/li&gt;
4401
4402 &lt;/ul&gt;
4403
4404 &lt;p&gt;I am not sure what the best way to implement this is, but my
4405 initial idea was to use dbus events to discover new hardware, the
4406 discover database to find packages and
4407 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4408 packages.&lt;/p&gt;
4409
4410 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4411 draft package is now checked into
4412 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4413 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4414 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4415 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4416 the relevant packages in Debian, and uploaded a new version
4417 2.2013.01.09 to unstable. I also discovered that the current
4418 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4419 package in Debian no longer discovered any USB devices, because
4420 /proc/bus/usb/devices is no longer present. I ported it to use
4421 libusb as a fall back option to get it working. The fixed package
4422 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4423 because of the freeze).&lt;/p&gt;
4424
4425 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4426 desktop notification to show up (only once, the first time it is
4427 inserted):&lt;/p&gt;
4428
4429 &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;
4430
4431 &lt;p&gt;For this prototype to be really useful, some way to automatically
4432 install the proposed packages by pressing the &quot;Please install
4433 program(s)&quot; button should to be implemented.&lt;/p&gt;
4434
4435 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4436 happen, please help me update the discover-data database with mappings
4437 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4438 list the package you would like to have installed when a given
4439 hardware device is inserted into your computer, and report bugs using
4440 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4441 such mapping, please let me know.&lt;/p&gt;
4442
4443 &lt;p&gt;This prototype need more work, and there are several questions that
4444 should be considered before it is ready for production use. Is dbus
4445 the correct way to detect new hardware? At the moment I look for HAL
4446 dbus events on the system bus, because that is the events I could see
4447 on my Debian Squeeze KDE desktop. Are there better events to use?
4448 How should the user be notified? Is the desktop notification
4449 mechanism the best option, or should the background daemon raise a
4450 popup instead? How should packages be installed? When should they
4451 not be installed?&lt;/p&gt;
4452
4453 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4454 please send me an email. :)&lt;/p&gt;
4455 </description>
4456 </item>
4457
4458 <item>
4459 <title>New IRC channel for LEGO designers using Debian</title>
4460 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4461 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4462 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4463 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4464 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4465 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4466 discovered I had to build all the tools myself because none were
4467 already in Debian Squeeze. If Debian support for LEGO is something
4468 you care about, please join me on the IRC channel
4469 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4470 irc.debian.org). There is a lot that could be done to improve the
4471 Debian support for LEGO designers. For example both CAD software
4472 and Mindstorm compilers are missing. :)&lt;/p&gt;
4473
4474 &lt;p&gt;Update 2012-01-03: A
4475 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4476 including links to Lego related packages is now available.&lt;/p&gt;
4477 </description>
4478 </item>
4479
4480 <item>
4481 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4482 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4483 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4484 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4485 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4486 year! I hope next year will prove to be a good year.&lt;/p&gt;
4487
4488 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4489 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4490 between each other with minimal overhead, is a very interesting
4491 experiment. And as I wrote a few days ago, the bitcoin situation in
4492 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4493 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4494 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4495 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4496 for one of the ftpmasters to approve the new bitcoin-qt package
4497 name.&lt;/p&gt;
4498
4499 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4500 team in Debian, you can easily test the package in Debian Squeeze
4501 using the following steps to get a set of working packages:&lt;/p&gt;
4502
4503 &lt;blockquote&gt;&lt;pre&gt;
4504 git clone git://git.debian.org/git/collab-maint/bitcoin
4505 cd bitcoin
4506 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4507 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4508 &lt;/pre&gt;&lt;/blockquote&gt;
4509
4510 &lt;p&gt;You might have to install some build dependencies as well. The
4511 list of commands should give you two packages, bitcoind and
4512 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4513 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4514 around 5.6 GiB of data on my machine at the moment. Make sure your
4515 ~/.bitcoin/ directory have lots of spare room if you want to download
4516 all the blocks. The client will warn if the disk is getting full, so
4517 there is not really a problem if you got too little room, but you will
4518 not be able to get all the features out of the client.&lt;/p&gt;
4519
4520 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4521 activities, please send Bitcoin donations to my address
4522 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4523 </description>
4524 </item>
4525
4526 <item>
4527 <title>A word on bitcoin support in Debian</title>
4528 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4529 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4530 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4531 <description>&lt;p&gt;It has been a while since I wrote about
4532 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4533 peer-to-peer based crypto-currency, and the reason is simply that I
4534 have been busy elsewhere. But two days ago, I started looking at the
4535 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4536 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4537 is now maintained by a
4538 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4539 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4540 owe a huge thank you to all these team members. :)
4541 But I was sad to discover that the bitcoin client is missing in
4542 Wheezy. It is only available in Sid (and an outdated client from
4543 backports). The client had several RC bugs registered in BTS blocking
4544 it from entering testing. To try to help the team and improve the
4545 situation, I spent some time providing patches and triaging the bug
4546 reports. I also had a look at the bitcoin package available from Matt
4547 Corallo in a
4548 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4549 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4550 Debian package.&lt;/p&gt;
4551
4552 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4553 IRC, I pushed several patches into the collab-maint git repository to
4554 improve the package. It now contains fixes for the RC issues (not from
4555 me, but fixed by Scott Howard), build rules for a Qt GUI client
4556 package, konqueror support for the bitcoin: URI and bash completion
4557 setup. As I work on Debian Squeeze, I also created
4558 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4559 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4560 it and try to integrate it into the git repository before uploading a
4561 new version to unstable.
4562
4563 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4564 centralized control currently exercised in the monetary system. I
4565 find it completely unacceptable that the USA government is collecting
4566 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4567 that the major credit card companies can block legal money
4568 transactions to Wikileaks. But for bitcoin to succeed, more people
4569 need to use bitcoins, and more people need to accept bitcoins when
4570 they sell products and services. Improving the bitcoin support in
4571 Debian is a small step in the right direction, but not enough.
4572 Unfortunately the user experience when browsing the web and wanting to
4573 pay with bitcoin is still not very good. The bitcoin: URI is a step
4574 in the right direction, but need to work in most or every browser in
4575 use. Also the bitcoin-qt client is too heavy to fire up to do a
4576 quick transaction. I believe there are other clients available, but
4577 have not tested them.&lt;/p&gt;
4578
4579 &lt;p&gt;My
4580 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4581 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4582 I received 20.15 BTC so far on the address I provided in my blog two
4583 years ago, as can be
4584 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4585 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4586 donation. The blockexplorer service demonstrates quite well that
4587 bitcoin is not quite anonymous and untracked. :) I wonder if the
4588 number of users have gone up since then. If you use bitcoin and want
4589 to show your support of my activity, please send Bitcoin donations to
4590 the same address as last time,
4591 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4592 </description>
4593 </item>
4594
4595 <item>
4596 <title>Git repository for song book for Computer Scientists</title>
4597 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4598 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4599 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4600 <description>&lt;p&gt;As I
4601 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4602 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4603 years ago, and today I finally found time to create a public
4604 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4605 repository for the project&lt;/a&gt;.&lt;/p&gt;
4606
4607 &lt;p&gt;If you want to help out, please clone the source and submit patches
4608 to the HTML version. To generate the PDF and PostScript version,
4609 please use prince XML, or let me know about a useful free software
4610 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4611
4612 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4613 PostScript formats at
4614 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4615 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4616 </description>
4617 </item>
4618
4619 <item>
4620 <title>Gratulerer med 19-årsdagen, Debian!</title>
4621 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4622 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4623 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4624 <description>&lt;p&gt;I dag fyller
4625 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4626 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4627 si gratulerer med dagen, Debian!&lt;/p&gt;
4628 </description>
4629 </item>
4630
4631 <item>
4632 <title>Song book for Computer Scientists</title>
4633 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4634 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4635 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4636 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4637 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4638 collecting computer related songs for use at parties. The original
4639 version was written in LaTeX, but a few years ago I got help from
4640 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4641 while keeping the ability to create a nice book in PDF format. I have
4642 not had time to maintain the book for a while now, and guess I should
4643 put it up on some public version control repository where others can
4644 help me extend and update the book. If anyone is volunteering to help
4645 me with this, send me an email. Also let me know if there are songs
4646 missing in my book.&lt;/p&gt;
4647
4648 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4649 me today that I really should let all my readers share the joys of
4650 singing out load about programming, computers and computer networks.
4651 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4652 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4653 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4654 Computer Science Songbook&lt;/a&gt;.
4655 </description>
4656 </item>
4657
4658 <item>
4659 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4660 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4661 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4662 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4663 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4664 around 1000 at the moment. To be able to get help from the vendors
4665 when something go wrong, we want to keep the firmware on the servers
4666 up to date. If the firmware isn&#39;t the latest and greatest, the
4667 vendors typically refuse to start debugging any problems until the
4668 firmware is upgraded. So before every reboot, we want to upgrade the
4669 firmware, and we would really like everyone handling servers at the
4670 university to do this themselves when they plan to reboot a machine.
4671 For that to happen we at the unix server admin group need to provide
4672 the tools to do so.&lt;/p&gt;
4673
4674 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4675 fetch and install the latest firmware for the servers we got. Most of
4676 our hardware are from Dell and HP, so I have focused on these servers
4677 so far. This blog post is about the Dell part.&lt;/P&gt;
4678
4679 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4680 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4681 with firmware information for all 11th generation servers, listing
4682 which firmware should be used on a given model and where on the FTP
4683 site I can find it. Using a simple perl XML parser I can then
4684 download the shell scripts Dell provides to do firmware upgrades from
4685 within Linux and reboot when all the firmware is primed and ready to
4686 be activated on the first reboot.&lt;/p&gt;
4687
4688 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4689 Are there anyone working on similar tools for firmware upgrading all
4690 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4691
4692 &lt;p&gt;&lt;pre&gt;
4693 #!/usr/bin/perl
4694 use strict;
4695 use warnings;
4696 use File::Temp qw(tempdir);
4697 BEGIN {
4698 # Install needed RHEL packages if missing
4699 my %rhelmodules = (
4700 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4701 );
4702 for my $module (keys %rhelmodules) {
4703 eval &quot;use $module;&quot;;
4704 if ($@) {
4705 my $pkg = $rhelmodules{$module};
4706 system(&quot;yum install -y $pkg&quot;);
4707 eval &quot;use $module;&quot;;
4708 }
4709 }
4710 }
4711 my $errorsto = &#39;pere@hungry.com&#39;;
4712
4713 upgrade_dell();
4714
4715 exit 0;
4716
4717 sub run_firmware_script {
4718 my ($opts, $script) = @_;
4719 unless ($script) {
4720 print STDERR &quot;fail: missing script name\n&quot;;
4721 exit 1
4722 }
4723 print STDERR &quot;Running $script\n\n&quot;;
4724
4725 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4726 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4727 } else {
4728 print STDERR &quot;fail: firmware script returned error\n&quot;;
4729 }
4730 }
4731
4732 sub run_firmware_scripts {
4733 my ($opts, @dirs) = @_;
4734 # Run firmware packages
4735 for my $dir (@dirs) {
4736 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4737 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4738 while (my $s = readdir $dh) {
4739 next if $s =~ m/^\.\.?/;
4740 run_firmware_script($opts, &quot;$dir/$s&quot;);
4741 }
4742 closedir $dh;
4743 }
4744 }
4745
4746 sub download {
4747 my $url = shift;
4748 print STDERR &quot;info: Downloading $url\n&quot;;
4749 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
4750 }
4751
4752 sub upgrade_dell {
4753 my @dirs;
4754 my $product = `dmidecode -s system-product-name`;
4755 chomp $product;
4756
4757 if ($product =~ m/PowerEdge/) {
4758
4759 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4760 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
4761
4762 my $tmpdir = tempdir(
4763 CLEANUP =&gt; 1
4764 );
4765 chdir($tmpdir);
4766 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
4767 system(&#39;gunzip Catalog.xml.gz&#39;);
4768 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
4769 # -q is quiet, disabling interactivity and reducing console output
4770 my $fwopts = &quot;-q&quot;;
4771 if (@paths) {
4772 for my $url (@paths) {
4773 fetch_dell_fw($url);
4774 }
4775 run_firmware_scripts($fwopts, $tmpdir);
4776 } else {
4777 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4778 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4779 }
4780 chdir(&#39;/&#39;);
4781 } else {
4782 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4783 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4784 }
4785 }
4786
4787 sub fetch_dell_fw {
4788 my $path = shift;
4789 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
4790 download($url);
4791 }
4792
4793 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4794 # firmware packages to download from Dell. Only work for Linux
4795 # machines and 11th generation Dell servers.
4796 sub fetch_dell_fw_list {
4797 my $filename = shift;
4798
4799 my $product = `dmidecode -s system-product-name`;
4800 chomp $product;
4801 my ($mybrand, $mymodel) = split(/\s+/, $product);
4802
4803 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
4804
4805 my $xml = XMLin($filename);
4806 my @paths;
4807 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
4808 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
4809 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
4810 my $oscode;
4811 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
4812 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
4813 } else {
4814 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
4815 }
4816 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
4817 {
4818 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
4819 }
4820 }
4821 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
4822 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
4823
4824 # Drop application packages, only firmware and BIOS
4825 next if &#39;APAC&#39; eq $componenttype;
4826
4827 my $cpath = $component-&gt;{path};
4828 for my $path (@paths) {
4829 if ($cpath =~ m%/$path$%) {
4830 push(@paths, $cpath);
4831 }
4832 }
4833 }
4834 return @paths;
4835 }
4836 &lt;/pre&gt;
4837
4838 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
4839 it could work on other platforms with some tweaking. Anyone know a
4840 index like Catalog.xml is available from HP for HP servers? At the
4841 moment I maintain a similar list manually and it is quickly getting
4842 outdated.&lt;/p&gt;
4843 </description>
4844 </item>
4845
4846 <item>
4847 <title>How is booting into runlevel 1 different from single user boots?</title>
4848 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
4849 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
4850 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
4851 <description>&lt;p&gt;Wouter Verhelst have some
4852 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
4853 comments and opinions&lt;/a&gt; on my blog post on
4854 &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
4855 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
4856 &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
4857 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
4858 small piece of his comment now, and though it best to address the
4859 misunderstanding he bring forward:&lt;/p&gt;
4860
4861 &lt;p&gt;&lt;blockquote&gt;
4862 Currently, a system admin has four options: [...] boot to a
4863 single-user system (by adding &#39;single&#39; to the kernel command line;
4864 this runs rcS and rc1 scripts)
4865 &lt;/blockquote&gt;&lt;/p&gt;
4866
4867 &lt;p&gt;This make me believe Wouter believe booting into single user mode
4868 and booting into runlevel 1 is the same. I am not surprised he
4869 believe this, because it would make sense and is a quite sensible
4870 thing to believe. But because the boot in Debian is slightly broken,
4871 runlevel 1 do not work properly and it isn&#39;t the same as single user
4872 mode. I&#39;ll try to explain what is actually happing, but it is a bit
4873 hard to explain.&lt;/p&gt;
4874
4875 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
4876 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
4877 executed in single user mode is sulogin. Single user mode is a boot
4878 state &quot;between&quot; the runlevels, and when booting into single user mode,
4879 only the scripts in /etc/rcS.d/ are executed before the init process
4880 enters the single user state. When switching to runlevel 1, the state
4881 is in fact not ending in runlevel 1, but it passes through runlevel 1
4882 and end up in the single user mode (see /etc/rc1.d/S03single, which
4883 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
4884 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
4885 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4886 mode).&lt;/p&gt;
4887
4888 &lt;p&gt;This summary might make it clearer. When booting for the first
4889 time into single user mode, the following commands are executed:
4890 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
4891 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
4892 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
4893 trying to continue after visiting single user mode. Not all services
4894 are started again as they should, causing the machine to end up in an
4895 unpredicatble state. This is why Debian admins recommend rebooting
4896 after visiting single user mode.&lt;/p&gt;
4897
4898 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
4899 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
4900 to runlevel 1, the services started from /etc/rcS.d/ are not properly
4901 stopped when passing through the scripts in /etc/rc1.d/, and not
4902 started again when switching away from runlevel 1 to the runlevels
4903 2-5. I believe the problem is best fixed by moving all the scripts
4904 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
4905 functioning single user mode during boot.&lt;/p&gt;
4906
4907 &lt;p&gt;I have spent several years investigating the Debian boot system,
4908 and discovered this problem a few years ago. I suspect it originates
4909 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
4910 </description>
4911 </item>
4912
4913 <item>
4914 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
4915 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
4916 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
4917 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
4918 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
4919 are started from /etc/rcS.d/. In fact, there is a bite more of them
4920 than make sense, and this causes a few problems. What kind of
4921 problems, you might ask. There are at least two problems. The first
4922 is that it is not possible to recover a machine after switching to
4923 runlevel 1. One need to actually reboot to get the machine back to
4924 the expected state. The other is that single user boot will sometimes
4925 run into problems because some of the subsystems are activated before
4926 the root login is presented, causing problems when trying to recover a
4927 machine from a problem in that subsystem. A minor additional point is
4928 that moving more scripts out of rcS.d/ and into the other rc#.d/
4929 directories will increase the amount of scripts that can run in
4930 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
4931
4932 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
4933 scripts that _have_ to execute before the root login prompt is
4934 presented during a single user boot should go there. Everything else
4935 should go into the numeric runlevels. This means things like
4936 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4937 the numeric runlevels. Today in Debian, there are around 115 init.d
4938 scripts that are started from rcS.d/, and most of them should be moved
4939 out. Do your package have one of them? Please help us make single
4940 user and runlevel 1 better by moving it.&lt;/p&gt;
4941
4942 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
4943 etc. should still be started from rcS.d/, but there is for example no
4944 need to have the network enabled before the single user login prompt
4945 is presented.&lt;/p&gt;
4946
4947 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
4948 Debian systems working while scripts migrate and during upgrades, the
4949 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4950 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4951 and the next ones can only be moved when their dependencies have been
4952 moved first. This migration must be done sequentially while we ensure
4953 that the package system upgrade packages in the right order to keep
4954 the system state correct. This will require some coordination when it
4955 comes to network related packages, but most of the packages with
4956 scripts that should migrate do not have anything in rcS.d/ depending
4957 on them. Some packages have already been updated, like the sudo
4958 package, while others are still left to do. I wish I had time to work
4959 on this myself, but real live constrains make it unlikely that I will
4960 find time to push this forward.&lt;/p&gt;
4961 </description>
4962 </item>
4963
4964 <item>
4965 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4966 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4967 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4968 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4969 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4970 mentioned the issues I believe should be improved in Debian for its
4971 desktop to be useful for more people. The use case for this is my
4972 parents, which are currently running Kubuntu which solve the
4973 issues.&lt;/p&gt;
4974
4975 &lt;p&gt;I suspect these four missing features are not very hard to
4976 implement. After all, they are present in Ubuntu, so if we wanted to
4977 do this in Debian we would have a source.&lt;/p&gt;
4978
4979 &lt;ol&gt;
4980
4981 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4982 are new packages available for upgrades, a icon in the KDE status bar
4983 indicate this, and clicking on it will activate the simple upgrade
4984 tool to handle it. I have no problem guiding both of my parents
4985 through the process over the phone. If a kernel reboot is required,
4986 this too is indicated by the status bars and the upgrade tool. Last
4987 time I checked, nothing with the same features was working in KDE in
4988 Debian.&lt;/li&gt;
4989
4990 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4991 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4992 currently have a handler for, it will ask the user if the system
4993 should search for a package that would add support for this MIME type,
4994 and if the user say yes, the APT sources will be searched for packages
4995 advertising the MIME type in their control file (visible in the
4996 Packages file in the APT archive). If one or more packages are found,
4997 it is a simple click of the mouse to add support for the missing mime
4998 type. If the package require the user to accept some non-free
4999 license, this is explained to the user. The entire process make it
5000 more clear to the user why something do not work in the browser, and
5001 make the chances higher for the user to blame the web page authors and
5002 not the browser for any missing features.&lt;/li&gt;
5003
5004 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
5005 handlers.&lt;/strong&gt; When the media players encounter a format or codec
5006 it is not supporting, a dialog pop up asking the user if the system
5007 should search for a package that would add support for it. This
5008 happen with things like MP3, Windows Media or H.264. The selection
5009 and installation procedure is very similar to the Firefox browser
5010 plugin handling. This is as far as I know implemented using a
5011 gstreamer hook. The end result is that the user easily get access to
5012 the codecs that are present from the APT archives available, while
5013 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
5014
5015 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
5016 displaying a text/plain file in my Debian browser, it will propose to
5017 start emacs to show it. If I remember correctly, when doing the same
5018 in Kunbutu it show the file as a text file in the browser. At least I
5019 know Opera will show text files within the browser. I much prefer the
5020 latter behaviour.&lt;/li&gt;
5021
5022 &lt;/ol&gt;
5023
5024 &lt;p&gt;There are other nice features as well, like the simplified suite
5025 upgrader, but given that I am the one mostly doing the dist-upgrade,
5026 it do not matter much.&lt;/p&gt;
5027
5028 &lt;p&gt;I really hope we could get these features in place for the next
5029 Debian release. It would require the coordinated effort of several
5030 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
5031 </description>
5032 </item>
5033
5034 <item>
5035 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
5036 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
5037 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
5038 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
5039 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
5040 site is build on Debian/Squeeze, and this platform was chosen because
5041 I am most familiar with Debian (being a Debian Developer for around 10
5042 years) because it is the latest stable Debian release which should get
5043 security support for a few years.&lt;/p&gt;
5044
5045 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
5046 that are missing in Debian at the moment. It would be great if these
5047 modules were added to the Debian archive, allowing anyone to set up
5048 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
5049 in their own country using only Debian packages. The list of modules
5050 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
5051 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
5052 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5053 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5054 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5055 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5056 easier in the future.&lt;/p&gt;
5057
5058 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
5059 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
5060 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
5061 with the responsibility of tracking security problems, which I really
5062 do not have time for.&lt;/p&gt;
5063 </description>
5064 </item>
5065
5066 <item>
5067 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
5068 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
5069 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
5070 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
5071 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
5072 posts have been in Norwegian the last few weeks, so here is a short
5073 update in English.&lt;/p&gt;
5074
5075 &lt;p&gt;The kids still keep me too busy to get much free software work
5076 done, but I did manage to organise a project to get a Norwegian port
5077 of the British service
5078 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
5079 and it has been running for a month now. The entire project has been
5080 organised by me and two others. Around Christmas we gathered sponsors
5081 to fund the development work. In January I drafted a contract with
5082 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
5083 and in February the development took place. Most of it involved
5084 converting the source to use GPS coordinates instead of British
5085 easting/northing, and the resulting code should be a lot easier to get
5086 running in any country by now. The Norwegian
5087 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
5088 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
5089 source and the source for administrative borders in Norway, and
5090 support for this had to be added/fixed.&lt;/p&gt;
5091
5092 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
5093 polishing the system before we announced it March 7th. The system is
5094 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
5095 problem reports in a few weeks. Soon we hope to announce the Android
5096 and iPhone versions making it even easier to report problems with the
5097 public infrastructure.&lt;/p&gt;
5098
5099 &lt;p&gt;Perhaps something to consider for those of you in countries without
5100 such service?&lt;/p&gt;
5101 </description>
5102 </item>
5103
5104 <item>
5105 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
5106 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
5107 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
5108 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
5109 <description>&lt;p&gt;The last few days I have looked at ways to track open security
5110 issues here at my work with the University of Oslo. My idea is that
5111 it should be possible to use the information about security issues
5112 available on the Internet, and check our locally
5113 maintained/distributed software against this information. It should
5114 allow us to verify that no known security issues are forgotten. The
5115 CVE database listing vulnerabilities seem like a great central point,
5116 and by using the package lists from Debian mapped to CVEs provided by
5117 the testing security team, I believed it should be possible to figure
5118 out which security holes were present in our free software
5119 collection.&lt;/p&gt;
5120
5121 &lt;p&gt;After reading up on the topic, it became obvious that the first
5122 building block is to be able to name software packages in a unique and
5123 consistent way across data sources. I considered several ways to do
5124 this, for example coming up with my own naming scheme like using URLs
5125 to project home pages or URLs to the Freshmeat entries, or using some
5126 existing naming scheme. And it seem like I am not the first one to
5127 come across this problem, as MITRE already proposed and implemented a
5128 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
5129 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
5130 software, hardware and other platform components. The CPE ids are
5131 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
5132 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
5133 issues for any CPE name. With this in place, all I need to do is to
5134 locate the CPE id for the software packages we use at the university.
5135 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
5136 NVD entry if a CVE for the package exist).&lt;/p&gt;
5137
5138 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
5139 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
5140 check out, one could look up
5141 &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
5142 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
5143 The most recent one is
5144 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
5145 and at the bottom of the NVD page for this vulnerability the complete
5146 list of affected versions is provided.&lt;/p&gt;
5147
5148 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
5149 for offline processing of issues. Using this dump, I&#39;ve written a
5150 small script taking a list of CPEs as input and list all CVEs
5151 affecting the packages represented by these CPEs. One give it CPEs
5152 with version numbers as specified above and get a list of open
5153 security issues out.&lt;/p&gt;
5154
5155 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
5156 information need to be high. For that to happen, I believe as many as
5157 possible need to use and contribute to the NVD database. I notice
5158 RHEL is providing
5159 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
5160 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
5161 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
5162
5163 &lt;p&gt;To get an idea about the quality for free software, I spent some
5164 time making it possible to compare the CVE database from Debian with
5165 the CVE database in NVD. The result look fairly good, but there are
5166 some inconsistencies in NVD (same software package having several
5167 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5168 Debian believe are affected by a CVE). Hope to find time to improve
5169 the quality of NVD, but that require being able to get in touch with
5170 someone maintaining it. So far my three emails with questions and
5171 corrections have not seen any reply, but I hope contact can be
5172 established soon.&lt;/p&gt;
5173
5174 &lt;p&gt;An interesting application for CPEs is cross platform package
5175 mapping. It would be useful to know which packages in for example
5176 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5177 this would be trivial if all linux distributions provided CPE entries
5178 for their packages.&lt;/p&gt;
5179 </description>
5180 </item>
5181
5182 <item>
5183 <title>Which module is loaded for a given PCI and USB device?</title>
5184 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
5185 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
5186 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
5187 <description>&lt;p&gt;In the
5188 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
5189 package in Debian, there is a script to report useful information
5190 about the running hardware for use when people report missing
5191 information. One part of this script that I find very useful when
5192 debugging hardware problems, is the part mapping loaded kernel module
5193 to the PCI device it claims. It allow me to quickly see if the kernel
5194 module I expect is driving the hardware I am struggling with. To see
5195 the output, make sure discover-data is installed and run
5196 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
5197 one of my machines like this:&lt;/p&gt;
5198
5199 &lt;pre&gt;
5200 loaded modules:
5201 10de:03eb i2c_nforce2
5202 10de:03f1 ohci_hcd
5203 10de:03f2 ehci_hcd
5204 10de:03f0 snd_hda_intel
5205 10de:03ec pata_amd
5206 10de:03f6 sata_nv
5207 1022:1103 k8temp
5208 109e:036e bttv
5209 109e:0878 snd_bt87x
5210 11ab:4364 sky2
5211 &lt;/pre&gt;
5212
5213 &lt;p&gt;The code in question look like this, slightly modified for
5214 readability and to drop the output to file descriptor 3:&lt;/p&gt;
5215
5216 &lt;pre&gt;
5217 if [ -d /sys/bus/pci/devices/ ] ; then
5218 echo loaded pci modules:
5219 (
5220 cd /sys/bus/pci/devices/
5221 for address in * ; do
5222 if [ -d &quot;$address/driver/module&quot; ] ; then
5223 module=`cd $address/driver/module ; pwd -P | xargs basename`
5224 if grep -q &quot;^$module &quot; /proc/modules ; then
5225 address=$(echo $address |sed s/0000://)
5226 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
5227 echo &quot;$id $module&quot;
5228 fi
5229 fi
5230 done
5231 )
5232 echo
5233 fi
5234 &lt;/pre&gt;
5235
5236 &lt;p&gt;Similar code could be used to extract USB device module
5237 mappings:&lt;/p&gt;
5238
5239 &lt;pre&gt;
5240 if [ -d /sys/bus/usb/devices/ ] ; then
5241 echo loaded usb modules:
5242 (
5243 cd /sys/bus/usb/devices/
5244 for address in * ; do
5245 if [ -d &quot;$address/driver/module&quot; ] ; then
5246 module=`cd $address/driver/module ; pwd -P | xargs basename`
5247 if grep -q &quot;^$module &quot; /proc/modules ; then
5248 address=$(echo $address |sed s/0000://)
5249 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
5250 if [ &quot;$id&quot; ] ; then
5251 echo &quot;$id $module&quot;
5252 fi
5253 fi
5254 fi
5255 done
5256 )
5257 echo
5258 fi
5259 &lt;/pre&gt;
5260
5261 &lt;p&gt;This might perhaps be something to include in other tools as
5262 well.&lt;/p&gt;
5263 </description>
5264 </item>
5265
5266 <item>
5267 <title>How to test if a laptop is working with Linux</title>
5268 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
5269 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
5270 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
5271 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
5272 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
5273 batch of computers will work with Linux. Every year for the last few
5274 years the university have organised shared bid of a few thousand
5275 computers, and this year HP won the bid. Two different desktops and
5276 five different laptops are on the list this year. We in the UNIX
5277 group want to know which one of these computers work well with RHEL
5278 and Ubuntu, the two Linux distributions we currently handle at the
5279 university.&lt;/p&gt;
5280
5281 &lt;p&gt;My test method is simple, and I share it here to get feedback and
5282 perhaps inspire others to test hardware as well. To test, I PXE
5283 install the OS version of choice, and log in as my normal user and run
5284 a few applications and plug in selected pieces of hardware. When
5285 something fail, I make a note about this in the test matrix and move
5286 on. If I have some spare time I try to report the bug to the OS
5287 vendor, but as I only have the machines for a short time, I rarely
5288 have the time to do this for all the problems I find.&lt;/p&gt;
5289
5290 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
5291 I perform on a new model.&lt;/p&gt;
5292
5293 &lt;ul&gt;
5294
5295 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
5296 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5297 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
5298
5299 &lt;li&gt;Is X.org working? If the graphical login screen show up after
5300 installation, X.org is working.&lt;/li&gt;
5301
5302 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
5303 package mesa-utils on Ubuntu) and writing down the frames per second
5304 reported by the program.&lt;/li&gt;
5305
5306 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
5307 logging in, and if I can hear this the test is successful. If there
5308 are several audio exits on the machine, I try them all and check if
5309 the Gnome/KDE audio mixer can control where to send the sound. I
5310 normally test this by playing
5311 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
5312 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
5313
5314 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
5315 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
5316
5317 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
5318 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
5319
5320 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
5321 picture from the v4l device show up.&lt;/li&gt;
5322
5323 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5324 any bluetooth devices are discovered. In my office, I normally see a
5325 few.&lt;/li&gt;
5326
5327 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
5328 memory modules lying around, and stick them in and see if Gnome/KDE
5329 notice this.&lt;/li&gt;
5330
5331 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
5332 special button work, and if the laptop continue to work after
5333 resume.&lt;/li&gt;
5334
5335 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
5336 adjusting background light, switching on/off external video output,
5337 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5338 laptop to laptop, so I just write down which are working and which are
5339 not.&lt;/li&gt;
5340
5341 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5342 acceleration sensors etc. I rarely test these, as I do not know how
5343 to quickly test if they are working or not, so I only document their
5344 existence.&lt;/li&gt;
5345
5346 &lt;/ul&gt;
5347
5348 &lt;p&gt;By now I suspect you are really curious what the test results are
5349 for the HP machines I am testing. I&#39;m not done yet, so I will report
5350 the test results later. For now I can report that HP 8100 Elite work
5351 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5352 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5353 can see, I have most machines left to test. One interesting
5354 observation is that Ubuntu Lucid has almost twice the frame rate than
5355 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5356 </description>
5357 </item>
5358
5359 <item>
5360 <title>Some thoughts on BitCoins</title>
5361 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5362 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5363 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5364 <description>&lt;p&gt;As I continue to explore
5365 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5366 what properties the system have, and how it will be affected by laws
5367 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5368
5369 &lt;p&gt;One interesting thing to note is that since the transactions are
5370 verified using a peer to peer network, all details about a transaction
5371 is known to everyone. This means that if a BitCoin address has been
5372 published like I did with mine in my initial post about BitCoin, it is
5373 possible for everyone to see how many BitCoins have been transfered to
5374 that address. There is even a web service to look at the details for
5375 all transactions. There I can see that my address
5376 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5377 have received 16.06 Bitcoin, the
5378 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5379 address of Simon Phipps have received 181.97 BitCoin and the address
5380 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5381 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5382 every one of you that donated bitcoins to support my activity. The
5383 fact that anyone can see how much money was transfered to a given
5384 address make it more obvious why the BitCoin community recommend to
5385 generate and hand out a new address for each transaction. I&#39;m told
5386 there is no way to track which addresses belong to a given person or
5387 organisation without the person or organisation revealing it
5388 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5389
5390 &lt;p&gt;In Norway, and in most other countries, there are laws and
5391 regulations limiting how much money one can transfer across the border
5392 without declaring it. There are money laundering, tax and accounting
5393 laws and regulations I would expect to apply to the use of BitCoin.
5394 If the Skolelinux foundation
5395 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5396 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5397 normal bank transfers like EFF is doing, how should this be accounted?
5398 Given that it is impossible to know if money can cross the border or
5399 not, should everything or nothing be declared? What exchange rate
5400 should be used when calculating taxes? Would receivers have to pay
5401 income tax if the foundation were to pay Skolelinux contributors in
5402 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5403
5404 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5405 accepted by a lot of users. It must be possible to get easy access to
5406 the currency (as a wage or using currency exchanges), and it must be
5407 easy to spend it. At the moment BitCoin seem fairly easy to get
5408 access to, but there are very few places to spend it. I am not really
5409 a regular user of any of the vendor types currently accepting BitCoin,
5410 so I wonder when my kind of shop would start accepting BitCoins. I
5411 would like to buy electronics, travels and subway tickets, not herbs
5412 and books. :) The currency is young, and this will improve over time
5413 if it become popular, but I suspect regular banks will start to lobby
5414 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5415 will claim it is helping fund terrorism and money laundering (which
5416 probably would be true, as is any currency in existence), but I
5417 believe the problems should be solved elsewhere and not by blaming
5418 currencies.&lt;/p&gt;
5419
5420 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5421 CPU intensive process that depend on a bit of luck as well (as one is
5422 competing against all the other miners currently spending CPU cycles
5423 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5424 BitCoin when this happen. Yesterday I came across the obvious way to
5425 join forces to increase ones changes of getting at least some coins,
5426 by coordinating the work on mining BitCoins across several machines
5427 and people, and sharing the result if one is lucky and get the 50
5428 BitCoins. Check out
5429 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5430 if this sounds interesting. I have not had time to try to set up a
5431 machine to participate there yet, but have seen that running on ones
5432 own for a few days have not yield any BitCoins througth mining
5433 yet.&lt;/p&gt;
5434
5435 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5436 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5437 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5438 it was interesting to read. The arguments presented seem to be
5439 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5440 </description>
5441 </item>
5442
5443 <item>
5444 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5445 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5446 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5447 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5448 <description>&lt;p&gt;With this weeks lawless
5449 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5450 attacks&lt;/a&gt; on Wikileak and
5451 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5452 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5453 not be trusted to handle money transactions.
5454 A blog post from
5455 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5456 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5457 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5458 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5459 some help from my friend to get it all running, and he even handed me
5460 some bitcoins to get started. I even donated a few bitcoins to Simon
5461 for helping me remember BitCoin.&lt;/p&gt;
5462
5463 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5464 crypto-currency, decentralised and handled using peer-to-peer
5465 networks. It allows anonymous transactions and prohibits central
5466 control over the transactions, making it impossible for governments
5467 and companies alike to block donations and other transactions. The
5468 source is free software, and while the key dependency wxWidgets 2.9
5469 for the graphical user interface is missing in Debian, the command
5470 line client builds just fine. Hopefully Jonas
5471 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5472 Debian&lt;/a&gt; soon.&lt;/p&gt;
5473
5474 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5475 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5476 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5477 currency &quot;stock&quot; markets where the exchange rate is decided. There
5478 are not many users so far, but the concept seems promising. If you
5479 want to get started and lack a friend with any bitcoins to spare,
5480 you can even get
5481 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5482 bitcoin at the time of writing). Use
5483 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5484 on the current exchange rates.&lt;/p&gt;
5485
5486 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5487 machines. If you want to support my activity, please send Bitcoin
5488 donations to the address
5489 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5490 </description>
5491 </item>
5492
5493 <item>
5494 <title>Why isn&#39;t Debian Edu using VLC?</title>
5495 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5496 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5497 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5498 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5499 presented, and the winner among the multimedia player were VLC.
5500 Personally, I like VLC, and it is my player of choice when I first try
5501 to play a video file or stream. Only if VLC fail will I drag out
5502 gmplayer to see if it can do better. The reason is mostly the failure
5503 model and trust. When VLC fail, it normally pop up a error message
5504 reporting the problem. When mplayer fail, it normally segfault or
5505 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5506
5507 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5508 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5509 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5510 plugin to play web videos seamlessly, and the VLC browser plugin is
5511 not very good. For example, it lack in-line control buttons, so there
5512 is no way for the user to pause the video. Also, when I
5513 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5514 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5515 failed on several video pages where mplayer based plugins worked. If
5516 the browser plugin for VLC was as good as the gecko-mediaplayer
5517 package (which uses mplayer), we would switch.&lt;/P&gt;
5518
5519 &lt;p&gt;While VLC is a good player, its user interface is slightly
5520 annoying. The most annoying feature is its inconsistent use of
5521 keyboard shortcuts. When the player is in full screen mode, its
5522 shortcuts are different from when it is playing the video in a window.
5523 For example, space only work as pause when in full screen mode. I
5524 wish it had consisten shortcuts and that space also would work when in
5525 window mode. Another nice shortcut in gmplayer is [enter] to restart
5526 the current video. It is very nice when playing short videos from the
5527 web and want to restart it when new people arrive to have a look at
5528 what is going on.&lt;/p&gt;
5529 </description>
5530 </item>
5531
5532 <item>
5533 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5534 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5535 <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>
5536 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5537 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5538 upgrade testing of the
5539 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5540 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5541 This seem like a very good idea, so I adjusted by test scripts and
5542 can now present the updated result from today:&lt;/p&gt;
5543
5544 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5545
5546 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5547
5548 &lt;blockquote&gt;&lt;p&gt;
5549 apache2.2-bin
5550 aptdaemon
5551 baobab
5552 binfmt-support
5553 browser-plugin-gnash
5554 cheese-common
5555 cli-common
5556 cups-pk-helper
5557 dmz-cursor-theme
5558 empathy
5559 empathy-common
5560 freedesktop-sound-theme
5561 freeglut3
5562 gconf-defaults-service
5563 gdm-themes
5564 gedit-plugins
5565 geoclue
5566 geoclue-hostip
5567 geoclue-localnet
5568 geoclue-manual
5569 geoclue-yahoo
5570 gnash
5571 gnash-common
5572 gnome
5573 gnome-backgrounds
5574 gnome-cards-data
5575 gnome-codec-install
5576 gnome-core
5577 gnome-desktop-environment
5578 gnome-disk-utility
5579 gnome-screenshot
5580 gnome-search-tool
5581 gnome-session-canberra
5582 gnome-system-log
5583 gnome-themes-extras
5584 gnome-themes-more
5585 gnome-user-share
5586 gstreamer0.10-fluendo-mp3
5587 gstreamer0.10-tools
5588 gtk2-engines
5589 gtk2-engines-pixbuf
5590 gtk2-engines-smooth
5591 hamster-applet
5592 libapache2-mod-dnssd
5593 libapr1
5594 libaprutil1
5595 libaprutil1-dbd-sqlite3
5596 libaprutil1-ldap
5597 libart2.0-cil
5598 libboost-date-time1.42.0
5599 libboost-python1.42.0
5600 libboost-thread1.42.0
5601 libchamplain-0.4-0
5602 libchamplain-gtk-0.4-0
5603 libcheese-gtk18
5604 libclutter-gtk-0.10-0
5605 libcryptui0
5606 libdiscid0
5607 libelf1
5608 libepc-1.0-2
5609 libepc-common
5610 libepc-ui-1.0-2
5611 libfreerdp-plugins-standard
5612 libfreerdp0
5613 libgconf2.0-cil
5614 libgdata-common
5615 libgdata7
5616 libgdu-gtk0
5617 libgee2
5618 libgeoclue0
5619 libgexiv2-0
5620 libgif4
5621 libglade2.0-cil
5622 libglib2.0-cil
5623 libgmime2.4-cil
5624 libgnome-vfs2.0-cil
5625 libgnome2.24-cil
5626 libgnomepanel2.24-cil
5627 libgpod-common
5628 libgpod4
5629 libgtk2.0-cil
5630 libgtkglext1
5631 libgtksourceview2.0-common
5632 libmono-addins-gui0.2-cil
5633 libmono-addins0.2-cil
5634 libmono-cairo2.0-cil
5635 libmono-corlib2.0-cil
5636 libmono-i18n-west2.0-cil
5637 libmono-posix2.0-cil
5638 libmono-security2.0-cil
5639 libmono-sharpzip2.84-cil
5640 libmono-system2.0-cil
5641 libmtp8
5642 libmusicbrainz3-6
5643 libndesk-dbus-glib1.0-cil
5644 libndesk-dbus1.0-cil
5645 libopal3.6.8
5646 libpolkit-gtk-1-0
5647 libpt2.6.7
5648 libpython2.6
5649 librpm1
5650 librpmio1
5651 libsdl1.2debian
5652 libsrtp0
5653 libssh-4
5654 libtelepathy-farsight0
5655 libtelepathy-glib0
5656 libtidy-0.99-0
5657 media-player-info
5658 mesa-utils
5659 mono-2.0-gac
5660 mono-gac
5661 mono-runtime
5662 nautilus-sendto
5663 nautilus-sendto-empathy
5664 p7zip-full
5665 pkg-config
5666 python-aptdaemon
5667 python-aptdaemon-gtk
5668 python-axiom
5669 python-beautifulsoup
5670 python-bugbuddy
5671 python-clientform
5672 python-coherence
5673 python-configobj
5674 python-crypto
5675 python-cupshelpers
5676 python-elementtree
5677 python-epsilon
5678 python-evolution
5679 python-feedparser
5680 python-gdata
5681 python-gdbm
5682 python-gst0.10
5683 python-gtkglext1
5684 python-gtksourceview2
5685 python-httplib2
5686 python-louie
5687 python-mako
5688 python-markupsafe
5689 python-mechanize
5690 python-nevow
5691 python-notify
5692 python-opengl
5693 python-openssl
5694 python-pam
5695 python-pkg-resources
5696 python-pyasn1
5697 python-pysqlite2
5698 python-rdflib
5699 python-serial
5700 python-tagpy
5701 python-twisted-bin
5702 python-twisted-conch
5703 python-twisted-core
5704 python-twisted-web
5705 python-utidylib
5706 python-webkit
5707 python-xdg
5708 python-zope.interface
5709 remmina
5710 remmina-plugin-data
5711 remmina-plugin-rdp
5712 remmina-plugin-vnc
5713 rhythmbox-plugin-cdrecorder
5714 rhythmbox-plugins
5715 rpm-common
5716 rpm2cpio
5717 seahorse-plugins
5718 shotwell
5719 software-center
5720 system-config-printer-udev
5721 telepathy-gabble
5722 telepathy-mission-control-5
5723 telepathy-salut
5724 tomboy
5725 totem
5726 totem-coherence
5727 totem-mozilla
5728 totem-plugins
5729 transmission-common
5730 xdg-user-dirs
5731 xdg-user-dirs-gtk
5732 xserver-xephyr
5733 &lt;/p&gt;&lt;/blockquote&gt;
5734
5735 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5736
5737 &lt;blockquote&gt;&lt;p&gt;
5738 cheese
5739 ekiga
5740 eog
5741 epiphany-extensions
5742 evolution-exchange
5743 fast-user-switch-applet
5744 file-roller
5745 gcalctool
5746 gconf-editor
5747 gdm
5748 gedit
5749 gedit-common
5750 gnome-games
5751 gnome-games-data
5752 gnome-nettool
5753 gnome-system-tools
5754 gnome-themes
5755 gnuchess
5756 gucharmap
5757 guile-1.8-libs
5758 libavahi-ui0
5759 libdmx1
5760 libgalago3
5761 libgtk-vnc-1.0-0
5762 libgtksourceview2.0-0
5763 liblircclient0
5764 libsdl1.2debian-alsa
5765 libspeexdsp1
5766 libsvga1
5767 rhythmbox
5768 seahorse
5769 sound-juicer
5770 system-config-printer
5771 totem-common
5772 transmission-gtk
5773 vinagre
5774 vino
5775 &lt;/p&gt;&lt;/blockquote&gt;
5776
5777 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5778
5779 &lt;blockquote&gt;&lt;p&gt;
5780 gstreamer0.10-gnomevfs
5781 &lt;/p&gt;&lt;/blockquote&gt;
5782
5783 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5784
5785 &lt;blockquote&gt;&lt;p&gt;
5786 [nothing]
5787 &lt;/p&gt;&lt;/blockquote&gt;
5788
5789 &lt;p&gt;This is for KDE:&lt;/p&gt;
5790
5791 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5792
5793 &lt;blockquote&gt;&lt;p&gt;
5794 ksmserver
5795 &lt;/p&gt;&lt;/blockquote&gt;
5796
5797 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5798
5799 &lt;blockquote&gt;&lt;p&gt;
5800 kwin
5801 network-manager-kde
5802 &lt;/p&gt;&lt;/blockquote&gt;
5803
5804 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5805
5806 &lt;blockquote&gt;&lt;p&gt;
5807 arts
5808 dolphin
5809 freespacenotifier
5810 google-gadgets-gst
5811 google-gadgets-xul
5812 kappfinder
5813 kcalc
5814 kcharselect
5815 kde-core
5816 kde-plasma-desktop
5817 kde-standard
5818 kde-window-manager
5819 kdeartwork
5820 kdeartwork-emoticons
5821 kdeartwork-style
5822 kdeartwork-theme-icon
5823 kdebase
5824 kdebase-apps
5825 kdebase-workspace
5826 kdebase-workspace-bin
5827 kdebase-workspace-data
5828 kdeeject
5829 kdelibs
5830 kdeplasma-addons
5831 kdeutils
5832 kdewallpapers
5833 kdf
5834 kfloppy
5835 kgpg
5836 khelpcenter4
5837 kinfocenter
5838 konq-plugins-l10n
5839 konqueror-nsplugins
5840 kscreensaver
5841 kscreensaver-xsavers
5842 ktimer
5843 kwrite
5844 libgle3
5845 libkde4-ruby1.8
5846 libkonq5
5847 libkonq5-templates
5848 libnetpbm10
5849 libplasma-ruby
5850 libplasma-ruby1.8
5851 libqt4-ruby1.8
5852 marble-data
5853 marble-plugins
5854 netpbm
5855 nuvola-icon-theme
5856 plasma-dataengines-workspace
5857 plasma-desktop
5858 plasma-desktopthemes-artwork
5859 plasma-runners-addons
5860 plasma-scriptengine-googlegadgets
5861 plasma-scriptengine-python
5862 plasma-scriptengine-qedje
5863 plasma-scriptengine-ruby
5864 plasma-scriptengine-webkit
5865 plasma-scriptengines
5866 plasma-wallpapers-addons
5867 plasma-widget-folderview
5868 plasma-widget-networkmanagement
5869 ruby
5870 sweeper
5871 update-notifier-kde
5872 xscreensaver-data-extra
5873 xscreensaver-gl
5874 xscreensaver-gl-extra
5875 xscreensaver-screensaver-bsod
5876 &lt;/p&gt;&lt;/blockquote&gt;
5877
5878 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5879
5880 &lt;blockquote&gt;&lt;p&gt;
5881 ark
5882 google-gadgets-common
5883 google-gadgets-qt
5884 htdig
5885 kate
5886 kdebase-bin
5887 kdebase-data
5888 kdepasswd
5889 kfind
5890 klipper
5891 konq-plugins
5892 konqueror
5893 ksysguard
5894 ksysguardd
5895 libarchive1
5896 libcln6
5897 libeet1
5898 libeina-svn-06
5899 libggadget-1.0-0b
5900 libggadget-qt-1.0-0b
5901 libgps19
5902 libkdecorations4
5903 libkephal4
5904 libkonq4
5905 libkonqsidebarplugin4a
5906 libkscreensaver5
5907 libksgrd4
5908 libksignalplotter4
5909 libkunitconversion4
5910 libkwineffects1a
5911 libmarblewidget4
5912 libntrack-qt4-1
5913 libntrack0
5914 libplasma-geolocation-interface4
5915 libplasmaclock4a
5916 libplasmagenericshell4
5917 libprocesscore4a
5918 libprocessui4a
5919 libqalculate5
5920 libqedje0a
5921 libqtruby4shared2
5922 libqzion0a
5923 libruby1.8
5924 libscim8c2a
5925 libsmokekdecore4-3
5926 libsmokekdeui4-3
5927 libsmokekfile3
5928 libsmokekhtml3
5929 libsmokekio3
5930 libsmokeknewstuff2-3
5931 libsmokeknewstuff3-3
5932 libsmokekparts3
5933 libsmokektexteditor3
5934 libsmokekutils3
5935 libsmokenepomuk3
5936 libsmokephonon3
5937 libsmokeplasma3
5938 libsmokeqtcore4-3
5939 libsmokeqtdbus4-3
5940 libsmokeqtgui4-3
5941 libsmokeqtnetwork4-3
5942 libsmokeqtopengl4-3
5943 libsmokeqtscript4-3
5944 libsmokeqtsql4-3
5945 libsmokeqtsvg4-3
5946 libsmokeqttest4-3
5947 libsmokeqtuitools4-3
5948 libsmokeqtwebkit4-3
5949 libsmokeqtxml4-3
5950 libsmokesolid3
5951 libsmokesoprano3
5952 libtaskmanager4a
5953 libtidy-0.99-0
5954 libweather-ion4a
5955 libxklavier16
5956 libxxf86misc1
5957 okteta
5958 oxygencursors
5959 plasma-dataengines-addons
5960 plasma-scriptengine-superkaramba
5961 plasma-widget-lancelot
5962 plasma-widgets-addons
5963 plasma-widgets-workspace
5964 polkit-kde-1
5965 ruby1.8
5966 systemsettings
5967 update-notifier-common
5968 &lt;/p&gt;&lt;/blockquote&gt;
5969
5970 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5971 aptitude a bit more similar, but there are still quite a lott of
5972 differences. I have no idea what packages should be installed after
5973 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5974 </description>
5975 </item>
5976
5977 <item>
5978 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5979 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5980 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5981 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5982 <description>&lt;p&gt;Most of the computers in use by the
5983 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5984 are virtual machines. And they have been Xen machines running on a
5985 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5986 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5987 bit harder that it could have been, because we set up the Xen virtual
5988 machines to get the virtual partitions from LVM, which as far as I
5989 know is not supported by KVM. So to migrate, we had to convert
5990 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5991
5992 &lt;p&gt;I found
5993 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5994 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5995 migration. It uses qemu-img from the qemu package to make the disk
5996 image, parted to partition it, losetup and kpartx to present the disk
5997 image partions as devices, and dd to copy the data. I NFS mounted the
5998 new servers storage area on the old server to do the migration.&lt;/p&gt;
5999
6000 &lt;pre&gt;
6001 #!/bin/sh
6002
6003 # Based on
6004 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6005
6006 set -e
6007 set -x
6008
6009 if [ -z &quot;$1&quot; ] ; then
6010 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
6011 exit 1
6012 else
6013 host=&quot;$1&quot;
6014 fi
6015
6016 if [ ! -e /dev/vg_data/$host-disk ] ; then
6017 echo &quot;error: unable to find LVM volume for $host&quot;
6018 exit 1
6019 fi
6020
6021 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6022 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6023 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6024 totalsize=$(( ( $disksize + $swapsize ) ))
6025
6026 img=$host.img
6027 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
6028 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6029
6030 parted $img mklabel msdos
6031 parted $img mkpart primary linux-swap 0 $disksize
6032 parted $img mkpart primary ext2 $disksize $totalsize
6033 parted $img set 1 boot on
6034
6035 modprobe dm-mod
6036 losetup /dev/loop0 $img
6037 kpartx -a /dev/loop0
6038
6039 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
6040 fsck.ext3 -f /dev/mapper/loop0p1 || true
6041 mkswap /dev/mapper/loop0p2
6042
6043 kpartx -d /dev/loop0
6044 losetup -d /dev/loop0
6045 &lt;/pre&gt;
6046
6047 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
6048 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
6049
6050 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
6051 the new disk image attached, installed grub-pc and linux-image-686 and
6052 set up grub to boot from the disk image. After this, the KVM machines
6053 seem to work just fine.&lt;/p&gt;
6054 </description>
6055 </item>
6056
6057 <item>
6058 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
6059 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
6060 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
6061 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
6062 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
6063 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6064 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
6065 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
6066
6067 &lt;p&gt;I still do not know what a correct migration should look like, so I
6068 report any differences between apt and aptitude and hope someone else
6069 can see if anything should be changed.&lt;/p&gt;
6070
6071 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6072
6073 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6074
6075 &lt;blockquote&gt;&lt;p&gt;
6076 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6077 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
6078 dmz-cursor-theme empathy empathy-common finger
6079 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6080 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6081 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6082 gnome-cards-data gnome-codec-install gnome-core
6083 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6084 gnome-search-tool gnome-session-canberra gnome-spell
6085 gnome-system-log gnome-themes-extras gnome-themes-more
6086 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6087 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6088 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6089 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6090 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
6091 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
6092 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
6093 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
6094 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
6095 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6096 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
6097 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6098 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6099 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6100 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6101 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6102 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6103 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6104 libmono-security2.0-cil libmono-sharpzip2.84-cil
6105 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
6106 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
6107 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
6108 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
6109 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
6110 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
6111 libxalan2-java libxerces2-java media-player-info mesa-utils
6112 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
6113 nautilus-sendto-empathy openoffice.org-writer2latex
6114 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
6115 python-aptdaemon python-aptdaemon-gtk python-axiom
6116 python-beautifulsoup python-bugbuddy python-clientform
6117 python-coherence python-configobj python-crypto python-cupshelpers
6118 python-cupsutils python-eggtrayicon python-elementtree
6119 python-epsilon python-evolution python-feedparser python-gdata
6120 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6121 python-gtksourceview2 python-httplib2 python-louie python-mako
6122 python-markupsafe python-mechanize python-nevow python-notify
6123 python-opengl python-openssl python-pam python-pkg-resources
6124 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6125 python-tagpy python-twisted-bin python-twisted-conch
6126 python-twisted-core python-twisted-web python-utidylib python-webkit
6127 python-xdg python-zope.interface remmina remmina-plugin-data
6128 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6129 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6130 software-center svgalibg1 system-config-printer-udev
6131 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
6132 totem totem-coherence totem-mozilla totem-plugins
6133 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6134 zip
6135 &lt;/p&gt;&lt;/blockquote&gt;
6136
6137 Installed using apt-get, removed with aptitude
6138
6139 &lt;blockquote&gt;&lt;p&gt;
6140 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6141 epiphany-extensions epiphany-gecko evolution-exchange
6142 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6143 gedit-common gnome-app-install gnome-games gnome-games-data
6144 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6145 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6146 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6147 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
6148 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
6149 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
6150 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
6151 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6152 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6153 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6154 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
6155 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
6156 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6157 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6158 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6159 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6160 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
6161 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
6162 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
6163 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
6164 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
6165 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6166 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6167 sound-juicer swfdec-gnome system-config-printer totem-common
6168 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6169 &lt;/p&gt;&lt;/blockquote&gt;
6170
6171 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6172
6173 &lt;blockquote&gt;&lt;p&gt;
6174 gstreamer0.10-gnomevfs
6175 &lt;/p&gt;&lt;/blockquote&gt;
6176
6177 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6178
6179 &lt;blockquote&gt;&lt;p&gt;
6180 [nothing]
6181 &lt;/p&gt;&lt;/blockquote&gt;
6182
6183 &lt;p&gt;This is for KDE:&lt;/p&gt;
6184
6185 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6186
6187 &lt;blockquote&gt;&lt;p&gt;
6188 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
6189 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6190 ghostscript-x git gnome-audio gnugo granatier gs-common
6191 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6192 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6193 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6194 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6195 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6196 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6197 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6198 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6199 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6200 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6201 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6202 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
6203 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6204 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6205 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6206 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6207 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6208 libkrossui4 libmailtools-perl libmime-tools-perl
6209 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6210 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6211 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6212 lirc luatex marble networkstatus noatun-plugins
6213 openoffice.org-writer2latex palapeli palapeli-data parley
6214 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6215 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6216 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6217 ttf-sazanami-gothic
6218 &lt;/p&gt;&lt;/blockquote&gt;
6219
6220 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6221
6222 &lt;blockquote&gt;&lt;p&gt;
6223 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6224 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6225 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6226 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6227 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6228 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6229 kitchensync kiten kjumpingcube klatin klettres klickety klines
6230 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6231 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6232 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6233 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6234 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6235 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6236 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6237 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6238 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6239 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
6240 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
6241 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6242 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
6243 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
6244 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6245 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6246 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6247 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6248 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6249 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6250 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
6251 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
6252 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6253 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6254 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6255 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6256 &lt;/p&gt;&lt;/blockquote&gt;
6257
6258 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6259
6260 &lt;blockquote&gt;&lt;p&gt;
6261 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6262 kdeartwork kdebase kdebase-apps kdebase-workspace
6263 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6264 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6265 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6266 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6267 xscreensaver-screensaver-bsod
6268 &lt;/p&gt;&lt;/blockquote&gt;
6269
6270 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6271
6272 &lt;blockquote&gt;&lt;p&gt;
6273 kdebase-bin konq-plugins konqueror
6274 &lt;/p&gt;&lt;/blockquote&gt;
6275 </description>
6276 </item>
6277
6278 <item>
6279 <title>Gnash buildbot slave and Debian kfreebsd</title>
6280 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
6281 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
6282 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
6283 <description>&lt;p&gt;Answering
6284 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
6285 call from the Gnash project&lt;/a&gt; for
6286 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
6287 current source, I have set up a virtual KVM machine on the Debian
6288 Edu/Skolelinux virtualization host to test the git source on
6289 Debian/Squeeze. I hope this can help the developers in getting new
6290 releases out more often.&lt;/p&gt;
6291
6292 &lt;p&gt;As the developers want less main-stream build platforms tested to,
6293 I have considered setting up a &lt;a
6294 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
6295 machine as well. I have also considered using the kfreebsd
6296 architecture in Debian as a file server in NUUG to get access to the 5
6297 TB zfs volume we currently use to store DV video. Because of this, I
6298 finally got around to do a test installation of Debian/Squeeze with
6299 kfreebsd. Installation went fairly smooth, thought I noticed some
6300 visual glitches in the cdebconf dialogs (black cursor left on the
6301 screen at random locations). Have not gotten very far with the
6302 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6303 fatal problem. Have to spend some more time on it to see if it is
6304 useful as a file server for NUUG. Will try to find time to set up a
6305 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
6306 </description>
6307 </item>
6308
6309 <item>
6310 <title>Debian in 3D</title>
6311 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
6312 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
6313 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
6314 <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;
6315
6316 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
6317 3D linked in from
6318 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
6319 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
6320 </description>
6321 </item>
6322
6323 <item>
6324 <title>Software updates 2010-10-24</title>
6325 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
6326 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
6327 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
6328 <description>&lt;p&gt;Some updates.&lt;/p&gt;
6329
6330 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
6331 raise money for the project is going well. The lower limit of 10
6332 signers was reached in 24 hours, and so far 13 people have signed it.
6333 More signers and more funding is most welcome, and I am really curious
6334 how far we can get before the time limit of December 24 is reached.
6335 :)&lt;/p&gt;
6336
6337 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6338 about what appear to be a great code coverage tool capable of
6339 generating code coverage stats without any changes to the source code.
6340 It is called
6341 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6342 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6343 It is missing in Debian, but the git source built just fine in Squeeze
6344 after I installed libelf-dev, libdwarf-dev, pkg-config and
6345 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6346 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6347
6348 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6349 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6350 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6351 alpha test release of the Squeeze based Debian Edu /
6352 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6353 release. Give it a try if you need a complete linux solution for your
6354 school, including central infrastructure server, workstations, thin
6355 client servers and diskless workstations. A nice touch added
6356 yesterday is RDP support on the thin client servers, for windows
6357 clients to get a Linux desktop on request.&lt;/p&gt;
6358 </description>
6359 </item>
6360
6361 <item>
6362 <title>Some notes on Flash in Debian and Debian Edu</title>
6363 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6364 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6365 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6366 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6367 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6368 second most popular used package that is missing in Debian. The sixth
6369 most popular is flashplayer-mozilla. This is a clear indication that
6370 working flash is important for Debian users. Around 10 percent of the
6371 users submitting data to popcon.debian.org have this package
6372 installed.&lt;/p&gt;
6373
6374 &lt;p&gt;In the report written by Lars Risan in August 2008
6375&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
6376 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6377 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6378 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6379 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6380 web sites require Flash to work, and lacking working Flash support in
6381 the web browser and the problems with installing it was perceived as a
6382 good reason to stay with Windows.&lt;/p&gt;
6383
6384 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6385 said to be the retarded cousin that did not really understand
6386 everything you told him but could work fairly well. This was a
6387 comment regarding the problems Linux have with proprietary formats and
6388 non-standard web pages, and is sad because it exposes a fairly common
6389 understanding of whose fault it is if web pages that only work in for
6390 example Internet Explorer 6 fail to work on Firefox, and funny because
6391 it explain very well how annoying it is for users when Linux
6392 distributions do not work with the documents they receive or the web
6393 pages they want to visit.&lt;/p&gt;
6394
6395 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6396 and Debian Edu to have a well working Flash implementation in the
6397 distribution, to get at least popular sites as Youtube and Google
6398 Video to working out of the box. For Squeeze, Debian have the chance
6399 to include the latest version of Gnash that will make this happen, as
6400 the new release 0.8.8 was published a few weeks ago and is resting in
6401 unstable. The new version work with more sites that version 0.8.7.
6402 The Gnash maintainers have asked for a freeze exception, but the
6403 release team have not had time to reply to it yet. I hope they agree
6404 with me that Flash is important for the Debian desktop users, and thus
6405 accept the new package into Squeeze.&lt;/p&gt;
6406 </description>
6407 </item>
6408
6409 <item>
6410 <title>Circular package dependencies harms apt recovery</title>
6411 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6412 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6413 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6414 <description>&lt;p&gt;I discovered this while doing
6415 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6416 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6417 in Debian still got circular dependencies, and it is often claimed
6418 that apt and aptitude should be able to handle this just fine, but
6419 some times these dependency loops causes apt to fail.&lt;/p&gt;
6420
6421 &lt;p&gt;An example is from todays
6422 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6423 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6424 causes perl-modules to fail to upgrade. The cause is simple. If a
6425 package fail to unpack, then only part of packages with the circular
6426 dependency might end up being unpacked when unpacking aborts, and the
6427 ones already unpacked will fail to configure in the recovery phase
6428 because its dependencies are unavailable.&lt;/p&gt;
6429
6430 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6431
6432 &lt;blockquote&gt;&lt;pre&gt;
6433 dpkg: dependency problems prevent configuration of perl-modules:
6434 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6435 Version of perl on system is 5.10.0-19lenny2.
6436 dpkg: error processing perl-modules (--configure):
6437 dependency problems - leaving unconfigured
6438 &lt;/pre&gt;&lt;/blockquote&gt;
6439
6440 &lt;p&gt;The perl/perl-modules circular dependency is already
6441 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6442 hopefully be solved as soon as possible, but it is not the only one,
6443 and each one of these loops in the dependency tree can cause similar
6444 failures. Of course, they only occur when there are bugs in other
6445 packages causing the unpacking to fail, but it is rather nasty when
6446 the failure of one package causes the problem to become worse because
6447 of dependency loops.&lt;/p&gt;
6448
6449 &lt;p&gt;Thanks to
6450 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6451 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6452 dependencies
6453 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6454 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6455
6456 &lt;p&gt;Todays testing also exposed a bug in
6457 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6458 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6459 apt-get and aptitude, the latter possibly caused by some circular
6460 dependency. Reported both to BTS to try to get someone to look at
6461 it.&lt;/p&gt;
6462 </description>
6463 </item>
6464
6465 <item>
6466 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6467 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6468 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6469 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6470 <description>&lt;p&gt;This is a
6471 &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;
6472 on my
6473 &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
6474 work&lt;/a&gt; on
6475 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6476 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6477
6478 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6479 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6480 and dhcp3-server-ldap in Debian use the LDAP server. The two
6481 implementations are quite different in how they use LDAP.&lt;/p&gt;
6482
6483 To get this information, I started slapd with debugging enabled and
6484 dumped the debug output to a file to get the LDAP searches performed
6485 on a Debian Edu main-server. Here is a summary.
6486
6487 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6488
6489 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6490 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6491 the web.
6492
6493 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6494 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6495 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6496 reverse entries are in two different subtrees in LDAP with a structure
6497 based on the DNS names, as in tjener.intern and
6498 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6499
6500 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6501 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6502 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6503 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6504 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6505 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6506 forward entries, it is looking for attributes named dnsttl, arecord,
6507 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6508 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6509 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6510 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6511 spfrecord and modifytimestamp. For reverse entries it is looking for
6512 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6513 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6514 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6515 ldapsearch commands could look like this:&lt;/p&gt;
6516
6517 &lt;blockquote&gt;&lt;pre&gt;
6518 ldapsearch -h ldap \
6519 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6520 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6521 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6522 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6523 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6524 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6525
6526 ldapsearch -h ldap \
6527 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6528 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6529 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6530 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6531 srvrecord naptrrecord modifytimestamp
6532 &lt;/pre&gt;&lt;/blockquote&gt;
6533
6534 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6535 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6536 example LDAP objects used there. In addition to these objects, the
6537 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6538 also exist.&lt;/p&gt;
6539
6540 &lt;blockquote&gt;&lt;pre&gt;
6541 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6542 objectclass: top
6543 objectclass: dnsdomain
6544 objectclass: domainrelatedobject
6545 dc: tjener
6546 arecord: 10.0.2.2
6547 associateddomain: tjener.intern
6548
6549 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6550 objectclass: top
6551 objectclass: dnsdomain2
6552 objectclass: domainrelatedobject
6553 dc: 2
6554 ptrrecord: tjener.intern
6555 associateddomain: 2.2.0.10.in-addr.arpa
6556 &lt;/pre&gt;&lt;/blockquote&gt;
6557
6558 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6559 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6560 same base as in the tree mode for a object with filter
6561 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6562 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6563 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6564 naptrrecord and modifytimestamp. For reverse entires it also do a
6565 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6566 and the requested attributes are associateddomain, dnsttl and
6567 modifytimestamp. In short, in strict mode the objects with ptrrecord
6568 go away, and the arecord attribute in the forward object is used
6569 instead.&lt;/p&gt;
6570
6571 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6572 like this:&lt;/p&gt;
6573
6574 &lt;blockquote&gt;&lt;pre&gt;
6575 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6576 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6577 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6578 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6579 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6580 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6581
6582 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6583 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6584 &lt;/pre&gt;&lt;/blockquote&gt;
6585
6586 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6587 search for SOA records, which behave similar to the forward and
6588 reverse lookups.&lt;/p&gt;
6589
6590 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6591 specify any objectclass names, and instead look for the attributes it
6592 need to generate a DNS reply. This make it able to work with any
6593 objectclass that provide the needed attributes.&lt;/p&gt;
6594
6595 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6596 dnsdomain2 schemas. The latter is used for reverse entries like
6597 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6598
6599 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6600 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6601 attributes) and domainrelatedobject (for associatedDomain). The use
6602 of structural object classes make it impossible to combine these
6603 classes with the object classes used by DHCP.&lt;/p&gt;
6604
6605 &lt;p&gt;There are other schemas that could be used too, for example the
6606 dnszone structural object class used by Gosa and bind-sdb for the DNS
6607 attributes combined with the domainrelatedobject object class, but in
6608 this case some unused attributes would have to be included as well
6609 (zonename and relativedomainname).&lt;/p&gt;
6610
6611 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6612 mode and not use any of the existing objectclasses (dnsdomain,
6613 dnsdomain2 and dnszone) when one want to combine the DNS information
6614 with DHCP information, and instead create a auxiliary object class
6615 defined something like this (using the attributes defined for
6616 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6617
6618 &lt;blockquote&gt;&lt;pre&gt;
6619 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6620 SUP top
6621 AUXILIARY
6622 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6623 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6624 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6625 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6626 A6Record $ DNAMERecord
6627 ))
6628 &lt;/pre&gt;&lt;/blockquote&gt;
6629
6630 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6631 the domainrelatedobject object class, and allow any entity to include
6632 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6633 developers asking for their view on this schema and if they are
6634 interested in providing such schema with PowerDNS, and I hope my
6635 message will be accepted into their mailing list soon.&lt;/p&gt;
6636
6637 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6638
6639 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6640 the object attributes, and then uses the attributes it want. This
6641 make it harder to figure out exactly what attributes are used, but
6642 thanks to the working example in Debian Edu I can at least get an idea
6643 what is needed without having to read the source code.&lt;/p&gt;
6644
6645 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6646 search filter to use to locate the correct dhcpServer entity is
6647 stored. These are the relevant entries from
6648 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6649
6650 &lt;blockquote&gt;&lt;pre&gt;
6651 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6652 ldap-dhcp-server-cn &quot;dhcp&quot;;
6653 &lt;/pre&gt;&lt;/blockquote&gt;
6654
6655 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6656 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6657 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6658 search result is this entry:&lt;/p&gt;
6659
6660 &lt;blockquote&gt;&lt;pre&gt;
6661 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6662 cn: dhcp
6663 objectClass: top
6664 objectClass: dhcpServer
6665 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6666 &lt;/pre&gt;&lt;/blockquote&gt;
6667
6668 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6669 subtree with DHCP configuration. The DHCP configuration subtree base
6670 is located using a base scope search with base &quot;cn=DHCP
6671 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6672 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6673 The search result is this entry:&lt;/p&gt;
6674
6675 &lt;blockquote&gt;&lt;pre&gt;
6676 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6677 cn: DHCP Config
6678 objectClass: top
6679 objectClass: dhcpService
6680 objectClass: dhcpOptions
6681 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6682 dhcpStatements: ddns-update-style none
6683 dhcpStatements: authoritative
6684 dhcpOption: smtp-server code 69 = array of ip-address
6685 dhcpOption: www-server code 72 = array of ip-address
6686 dhcpOption: wpad-url code 252 = text
6687 &lt;/pre&gt;&lt;/blockquote&gt;
6688
6689 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6690 all the DHCP configuration is loaded, it is ready to receive requests.
6691 The subtree in Debian Edu contain objects with object classes
6692 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6693 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6694 and information about netmasks, dynamic range etc. Leaving out the
6695 details here because it is not relevant for the focus of my
6696 investigation, which is to see if it is possible to merge dns and dhcp
6697 related computer objects.&lt;/p&gt;
6698
6699 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6700 of the client (00:00:00:00:00:00 in this example), using a subtree
6701 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6702 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6703 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6704 like:&lt;/p&gt;
6705
6706 &lt;blockquote&gt;&lt;pre&gt;
6707 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6708 cn: hostname
6709 objectClass: top
6710 objectClass: dhcpHost
6711 dhcpHWAddress: ethernet 00:00:00:00:00:00
6712 dhcpStatements: fixed-address hostname
6713 &lt;/pre&gt;&lt;/blockquote&gt;
6714
6715 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6716 The object classes need to have fixed names, and the configuration
6717 need to be stored in a fairly specific LDAP structure. On the
6718 positive side, the invidiual dhcpHost entires can be anywhere without
6719 the DN pointed to by the dhcpServer entries. The latter should make
6720 it possible to group all host entries in a subtree next to the
6721 configuration entries, and this subtree can also be shared with the
6722 DNS server if the schema proposed above is combined with the dhcpHost
6723 structural object class.
6724
6725 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6726
6727 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6728 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6729 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6730 allowing DNS objects to be stored anywhere under the base cn specified
6731 in the configuration.&lt;/p&gt;
6732
6733 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6734 regarding which LDAP schemas to use and which LDAP structure to use.
6735 I guess one could implement ones own schema, as long as the
6736 objectclasses and attributes have the names used, but this do not
6737 really help when the DHCP subtree need to have a fairly fixed
6738 structure.&lt;/p&gt;
6739
6740 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
6741 this might work for Debian Edu:&lt;/p&gt;
6742
6743 &lt;blockquote&gt;&lt;pre&gt;
6744 ou=services
6745 cn=machine-info (dhcpService) - dhcpServiceDN points here
6746 cn=dhcp (dhcpServer)
6747 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6748 cn=10.0.2.0 (dhcpSubnet)
6749 cn=group1 (dhcpGroup/dhcpOptions)
6750 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6751 cn=192.168.0.0 (dhcpSubnet)
6752 cn=group1 (dhcpGroup/dhcpOptions)
6753 ou=machines - PowerDNS base points here
6754 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6755 &lt;/pre&gt;&lt;/blockquote&gt;
6756
6757 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
6758 entries to be in the dhcpGroup subtrees, the entries can be stored
6759 there instead of a common machines subtree, and the PowerDNS base
6760 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
6761
6762 &lt;p&gt;The combined object under the machines subtree would look something
6763 like this:&lt;/p&gt;
6764
6765 &lt;blockquote&gt;&lt;pre&gt;
6766 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6767 dc: hostname
6768 objectClass: top
6769 objectClass: dhcpHost
6770 objectclass: domainrelatedobject
6771 objectclass: dnsDomainAux
6772 associateddomain: hostname.intern
6773 arecord: 10.11.12.13
6774 dhcpHWAddress: ethernet 00:00:00:00:00:00
6775 dhcpStatements: fixed-address hostname.intern
6776 &lt;/pre&gt;&lt;/blockquote&gt;
6777
6778 &lt;/p&gt;One could even add the LTSP configuration associated with a given
6779 machine, as long as the required attributes are available in a
6780 auxiliary object class.&lt;/p&gt;
6781 </description>
6782 </item>
6783
6784 <item>
6785 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
6786 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
6787 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
6788 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
6789 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
6790 DHCP services in Debian Edu to use the same LDAP objects for a given
6791 computer, to avoid the possibility of having a inconsistent state for
6792 a computer in LDAP (as in DHCP but no DNS entry or the other way
6793 around) and make it easier to add computers to LDAP.&lt;/p&gt;
6794
6795 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
6796 information finally found a solution that seem to work.&lt;/p&gt;
6797
6798 &lt;p&gt;The old setup required three LDAP objects for a given computer.
6799 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6800 we switch powerdns to use its strict LDAP method (ldap-method=strict
6801 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6802 merged into one while making it impossible to transfer the reverse map
6803 to a slave DNS server.&lt;/p&gt;
6804
6805 &lt;p&gt;If we also replace the object class used to get the DNS related
6806 attributes to one allowing these attributes to be combined with the
6807 dhcphost object class, we can merge the DNS and DHCP entries into one.
6808 I&#39;ve written such object class in the dnsdomainaux.schema file (need
6809 proper OIDs, but that is a minor issue), and tested the setup. It
6810 seem to work.&lt;/p&gt;
6811
6812 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
6813 for both DNS and DHCP, and even the LTSP configuration I suggested in
6814 an earlier email. The combined LDAP object will look something like
6815 this:&lt;/p&gt;
6816
6817 &lt;blockquote&gt;&lt;pre&gt;
6818 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6819 cn: hostname
6820 objectClass: dhcphost
6821 objectclass: domainrelatedobject
6822 objectclass: dnsdomainaux
6823 associateddomain: hostname.intern
6824 arecord: 10.11.12.13
6825 dhcphwaddress: ethernet 00:00:00:00:00:00
6826 dhcpstatements: fixed-address hostname
6827 ldapconfigsound: Y
6828 &lt;/pre&gt;&lt;/blockquote&gt;
6829
6830 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
6831 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6832 before asking DNS to resolve the fixed-adddress. LTSP will use
6833 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
6834
6835 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
6836 dhcphost in a different location, to allow us to put the objects
6837 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
6838 that. If I can&#39;t figure out a way to do that, we can still get rid of
6839 the hosts subtree and move all its content into the DHCP Config tree
6840 (which probably should be renamed to be more related to the new
6841 content. I suspect cn=dnsdhcp,ou=services or something like that
6842 might be a good place to put it.&lt;/p&gt;
6843
6844 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6845 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6846 </description>
6847 </item>
6848
6849 <item>
6850 <title>Idea for storing LTSP configuration in LDAP</title>
6851 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
6852 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
6853 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
6854 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
6855 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6856 clients, and that this can be used to fetch configuration from LDAP if
6857 Debian Edu choose to store configuration there.&lt;/p&gt;
6858
6859 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
6860 to get configuration from LDAP. The idea is to look up the MAC
6861 address of the client in LDAP, and look for attributes on the form
6862 ltspconfigsetting=value, and use this to export SETTING=value to the
6863 LTSP clients.&lt;/p&gt;
6864
6865 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
6866 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
6867 allowing us to store all information about a computer in one place.&lt;/p&gt;
6868
6869 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
6870 this approach. A real LDAP schema for the ltspClientAux objectclass
6871 need to be written. Comments, suggestions, etc?&lt;/p&gt;
6872
6873 &lt;blockquote&gt;&lt;pre&gt;
6874 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6875 #
6876 # Fetch LTSP client settings from LDAP based on MAC address
6877 #
6878 # Uses ethernet address as stored in the dhcpHost objectclass using
6879 # the dhcpHWAddress attribute or ethernet address stored in the
6880 # ieee802Device objectclass with the macAddress attribute.
6881 #
6882 # This module is written to be schema agnostic, and only depend on the
6883 # existence of attribute names.
6884 #
6885 # The LTSP configuration variables are saved directly using a
6886 # ltspConfig prefix and uppercasing the rest of the attribute name.
6887 # To set the SERVER variable, set the ltspConfigServer attribute.
6888 #
6889 # Some LDAP schema should be created with all the relevant
6890 # configuration settings. Something like this should work:
6891 #
6892 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
6893 # SUP top
6894 # AUXILIARY
6895 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6896
6897 LDAPSERVER=$(debian-edu-ldapserver)
6898 if [ &quot;$LDAPSERVER&quot; ] ; then
6899 LDAPBASE=$(debian-edu-ldapserver -b)
6900 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
6901 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
6902 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
6903 grep &#39;^ltspConfig&#39; | while read attr value ; do
6904 # Remove prefix and convert to upper case
6905 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
6906 # bass value on to clients
6907 eval &quot;$attr=$value; export $attr&quot;
6908 done
6909 done
6910 fi
6911 &lt;/pre&gt;&lt;/blockquote&gt;
6912
6913 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
6914 the while block might end up in a subshell causing the variables set
6915 there to not show up in ltsp-config, but if that is the case I am sure
6916 the code can be restructured to make sure the variables are passed on.
6917 I expect that can be solved with some testing. :)&lt;/p&gt;
6918
6919 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6920 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6921
6922 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
6923 configuration in LDAP that was created around year 2000 by
6924 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
6925 Xperience, Inc., 2000&lt;/a&gt;. I found its
6926 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
6927 personal home page over at redhat.com.&lt;/p&gt;
6928 </description>
6929 </item>
6930
6931 <item>
6932 <title>jXplorer, a very nice LDAP GUI</title>
6933 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
6934 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
6935 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
6936 <description>&lt;p&gt;Since
6937 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
6938 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
6939 LDAP GUI that is even better than luma. The java application
6940 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
6941 moving LDAP objects and subtrees using drag-and-drop, and can
6942 authenticate using Kerberos. I have only tested the Kerberos
6943 authentication, but do not have a LDAP setup allowing me to rewrite
6944 LDAP with my test user yet. It is
6945 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
6946 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
6947 have with it is how it handle errors. If something go wrong, its
6948 non-intuitive behaviour require me to go through some query work list
6949 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
6950 </description>
6951 </item>
6952
6953 <item>
6954 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
6955 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
6956 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
6957 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
6958 <description>&lt;p&gt;Here is a short update on my &lt;a
6959 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6960 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6961 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6962 not reporting the status for KDE, because the upgrade crashes when
6963 aptitude try because of missing conflicts
6964 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6965 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6966
6967 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6968 complete list of the installed packages. Based on this I see these
6969 differences when I did a test run today. As usual, I do not really
6970 know what the correct set of packages would be, but thought it best to
6971 publish the difference.&lt;/p&gt;
6972
6973 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6974
6975 &lt;blockquote&gt;&lt;p&gt;
6976 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6977 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6978 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6979 libgtksourceview-common libpt-1.10.10-plugins-alsa
6980 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6981 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6982 python-4suite-xml python-eggtrayicon python-gtkhtml2
6983 python-gtkmozembed svgalibg1 xserver-xephyr zip
6984 &lt;/p&gt;&lt;/blockquote&gt;
6985
6986 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6987
6988 &lt;blockquote&gt;&lt;p&gt;
6989 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6990 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6991 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6992 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6993 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6994 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6995 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6996 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6997 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6998 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6999 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
7000 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
7001 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7002 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
7003 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7004 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
7005 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
7006 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7007 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7008 mysql-common swfdec-gnome totem-gstreamer wodim
7009 &lt;/p&gt;&lt;/blockquote&gt;
7010
7011 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7012
7013 &lt;blockquote&gt;&lt;p&gt;
7014 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7015 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7016 xserver-xorg-input-all xserver-xorg-input-evdev
7017 xserver-xorg-input-kbd xserver-xorg-input-mouse
7018 xserver-xorg-input-synaptics xserver-xorg-video-all
7019 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7020 xserver-xorg-video-chips xserver-xorg-video-cirrus
7021 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7022 xserver-xorg-video-glint xserver-xorg-video-i128
7023 xserver-xorg-video-i740 xserver-xorg-video-mach64
7024 xserver-xorg-video-mga xserver-xorg-video-neomagic
7025 xserver-xorg-video-nouveau xserver-xorg-video-nv
7026 xserver-xorg-video-r128 xserver-xorg-video-radeon
7027 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7028 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7029 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7030 xserver-xorg-video-sis xserver-xorg-video-sisusb
7031 xserver-xorg-video-tdfx xserver-xorg-video-tga
7032 xserver-xorg-video-trident xserver-xorg-video-tseng
7033 xserver-xorg-video-vesa xserver-xorg-video-vmware
7034 xserver-xorg-video-voodoo
7035 &lt;/p&gt;&lt;/blockquote&gt;
7036
7037 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7038
7039 &lt;blockquote&gt;&lt;p&gt;
7040 deskbar-applet xserver-xorg xserver-xorg-core
7041 xserver-xorg-input-wacom xserver-xorg-video-intel
7042 xserver-xorg-video-openchrome
7043 &lt;/p&gt;&lt;/blockquote&gt;
7044
7045 &lt;p&gt;I was told on IRC that the xorg-xserver package was
7046 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
7047 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
7048 No idea when it hits Squeeze, but when it does I hope it will reduce
7049 the difference somewhat.
7050 </description>
7051 </item>
7052
7053 <item>
7054 <title>LUMA, a very nice LDAP GUI</title>
7055 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
7056 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
7057 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
7058 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
7059 directory in Debian Edu, and in the process I started to miss a GUI
7060 tool to browse the LDAP tree. The only one I was able to find in
7061 Debian/Squeeze and Lenny is
7062 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
7063 be a great tool to get a overview of the current LDAP directory
7064 populated by default in Skolelinux. Thanks to it, I have been able to
7065 find empty and obsolete subtrees, misplaced objects and duplicate
7066 objects. It will be installed by default in Debian/Squeeze. If you
7067 are working with LDAP, give it a go. :)&lt;/p&gt;
7068
7069 &lt;p&gt;I did notice one problem with it I have not had time to report to
7070 the BTS yet. There is no .desktop file in the package, so the tool do
7071 not show up in the Gnome and KDE menus, but only deep down in in the
7072 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7073 released.&lt;/p&gt;
7074
7075 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
7076 like to move objects and remove subtrees directly in the GUI, but have
7077 not found a way to do that with LUMA yet. So in the mean time, I use
7078 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
7079
7080 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
7081 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7082
7083 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
7084 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
7085 useful GUI alternative. It seem like a good tool, but is unmaintained
7086 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7087 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
7088 </description>
7089 </item>
7090
7091 <item>
7092 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
7093 <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>
7094 <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>
7095 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
7096 <description>&lt;p&gt;A while back, I
7097 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
7098 about the fact&lt;/a&gt; that it is not possible with the provided schemas
7099 for storing DNS and DHCP information in LDAP to combine the two sets
7100 of information into one LDAP object representing a computer.&lt;/p&gt;
7101
7102 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
7103 the dhcpHost object class auxiliary, to allow it to be combined with
7104 the dNSDomain object class, and thus forming one object for one
7105 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
7106
7107 &lt;p&gt;If I understand this correctly, it is not safe to do this change
7108 without also changing the assigned number for the object class, and I
7109 do not know enough about LDAP schema design to do that properly for
7110 Debian Edu.&lt;/p&gt;
7111
7112 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
7113 the
7114 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
7115 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
7116 available today from IETF.&lt;/p&gt;
7117
7118 &lt;pre&gt;
7119 --- dhcp.schema (revision 65192)
7120 +++ dhcp.schema (working copy)
7121 @@ -376,7 +376,7 @@
7122 objectclass ( 2.16.840.1.113719.1.203.6.6
7123 NAME &#39;dhcpHost&#39;
7124 DESC &#39;This represents information about a particular client&#39;
7125 - SUP top
7126 + SUP top AUXILIARY
7127 MUST cn
7128 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7129 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
7130 &lt;/pre&gt;
7131
7132 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
7133 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7134 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
7135
7136 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7137 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7138 </description>
7139 </item>
7140
7141 <item>
7142 <title>Calling tasksel like the installer, while still getting useful output</title>
7143 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
7144 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
7145 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
7146 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
7147 installs packages during the normal debian-installer run. Until now,
7148 I have ended up letting tasksel do the work, with the annoying problem
7149 of not getting any feedback at all when something fails (like a
7150 conffile question from dpkg or a download that fails), using code like
7151 this:
7152
7153 &lt;blockquote&gt;&lt;pre&gt;
7154 export DEBIAN_FRONTEND=noninteractive
7155 tasksel --new-install
7156 &lt;/pre&gt;&lt;/blockquote&gt;
7157
7158 This would invoke tasksel, let its automatic task selection pick the
7159 tasks to install, and continue to install the requested tasks without
7160 any output what so ever.
7161
7162 Recently I revisited this problem while working on the automatic
7163 package upgrade testing, because tasksel would some times hang without
7164 any useful feedback, and I want to see what is going on when it
7165 happen. Then it occured to me, I can parse the output from tasksel
7166 when asked to run in test mode, and use that aptitude command line
7167 printed by tasksel then to simulate the tasksel run. I ended up using
7168 code like this:
7169
7170 &lt;blockquote&gt;&lt;pre&gt;
7171 export DEBIAN_FRONTEND=noninteractive
7172 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
7173 $cmd
7174 &lt;/pre&gt;&lt;/blockquote&gt;
7175
7176 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
7177 --without-recommends -o APT::Install-Recommends=no -y install
7178 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7179 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
7180 laptop task and all packages with priority standard , required and
7181 important, just like tasksel would have done it during
7182 installation.&lt;/p&gt;
7183
7184 &lt;p&gt;A better approach is probably to extend tasksel to be able to
7185 install packages without using debconf-apt-progress, for use cases
7186 like this.&lt;/p&gt;
7187 </description>
7188 </item>
7189
7190 <item>
7191 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
7192 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
7193 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
7194 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
7195 <description>&lt;p&gt;My
7196 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
7197 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
7198 finally made the upgrade logs available from
7199 &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;.
7200 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7201 apt and aptitude, and found their differences interesting. This time
7202 I will only focus on their removal plans.&lt;/p&gt;
7203
7204 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
7205 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
7206 surprising part is that it want to remove xorg and all
7207 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7208 sure why. When asking aptitude to do the same, it want to remove 129
7209 packages, but most of them are library packages I suspect are no
7210 longer needed. Both of them want to remove bluetooth packages, which
7211 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
7212
7213 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
7214 which seem like a bad idea and xorg the same way as with Gnome. Asking
7215 aptitude for the same, it wants to remove 192 packages, none which are
7216 too surprising.&lt;/p&gt;
7217
7218 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
7219 and avoided, and perhaps others as well. Here are the complete list
7220 of planned removals. The complete logs is available from the URL
7221 above. Note if you want to repeat these tests, that the upgrade test
7222 for kde+apt-get hung in the tasksel setup because of dpkg asking
7223 conffile questions. No idea why. I worked around it by using
7224 &#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
7225 continue.&lt;/p&gt;
7226
7227 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
7228 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
7229 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7230 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
7231 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7232 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7233 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7234 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7235 xserver-xorg-input-kbd xserver-xorg-input-mouse
7236 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7237 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7238 xserver-xorg-video-ati xserver-xorg-video-chips
7239 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7240 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7241 xserver-xorg-video-glint xserver-xorg-video-i128
7242 xserver-xorg-video-i740 xserver-xorg-video-imstt
7243 xserver-xorg-video-intel xserver-xorg-video-mach64
7244 xserver-xorg-video-mga xserver-xorg-video-neomagic
7245 xserver-xorg-video-nsc xserver-xorg-video-nv
7246 xserver-xorg-video-openchrome xserver-xorg-video-r128
7247 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7248 xserver-xorg-video-rendition xserver-xorg-video-s3
7249 xserver-xorg-video-s3virge xserver-xorg-video-savage
7250 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7251 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7252 xserver-xorg-video-tga xserver-xorg-video-trident
7253 xserver-xorg-video-tseng xserver-xorg-video-v4l
7254 xserver-xorg-video-vesa xserver-xorg-video-vga
7255 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
7256 xulrunner-1.9-gnome-support&lt;/p&gt;
7257
7258 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
7259
7260 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
7261 djvulibre-desktop finger gnome-app-install gnome-mount
7262 gnome-network-admin gnome-spell gnome-vfs-obexftp
7263 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7264 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7265 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7266 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
7267 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
7268 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
7269 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
7270 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
7271 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
7272 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
7273 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
7274 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
7275 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7276 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
7277 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
7278 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
7279 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
7280 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
7281 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7282 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7283 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7284 openoffice.org-writer2latex openssl-blacklist p7zip
7285 python-4suite-xml python-eggtrayicon python-gnome2-desktop
7286 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7287 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7288 swfdec-mozilla totem-gstreamer update-manager wodim
7289 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7290 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7291 zip&lt;/p&gt;
7292
7293 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
7294
7295 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7296 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7297 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7298 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7299 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7300 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7301 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7302 xserver-xorg-input-kbd xserver-xorg-input-mouse
7303 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7304 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7305 xserver-xorg-video-ati xserver-xorg-video-chips
7306 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7307 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7308 xserver-xorg-video-glint xserver-xorg-video-i128
7309 xserver-xorg-video-i740 xserver-xorg-video-imstt
7310 xserver-xorg-video-intel xserver-xorg-video-mach64
7311 xserver-xorg-video-mga xserver-xorg-video-neomagic
7312 xserver-xorg-video-nsc xserver-xorg-video-nv
7313 xserver-xorg-video-openchrome xserver-xorg-video-r128
7314 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7315 xserver-xorg-video-rendition xserver-xorg-video-s3
7316 xserver-xorg-video-s3virge xserver-xorg-video-savage
7317 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7318 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7319 xserver-xorg-video-tga xserver-xorg-video-trident
7320 xserver-xorg-video-tseng xserver-xorg-video-v4l
7321 xserver-xorg-video-vesa xserver-xorg-video-vga
7322 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
7323
7324 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
7325 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
7326 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7327 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7328 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7329 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7330 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7331 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7332 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7333 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7334 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7335 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7336 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7337 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7338 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7339 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7340 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7341 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7342 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7343 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7344 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7345 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7346 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7347 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7348 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7349 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7350 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7351 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7352 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7353 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7354 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7355 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7356 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7357 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7358 texlive-common texlive-doc-base texlive-fonts-recommended
7359 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7360 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7361 xulrunner-1.9&lt;/p&gt;
7362
7363 </description>
7364 </item>
7365
7366 <item>
7367 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7368 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7369 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7370 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7371 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7372 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7373 have been discovered and reported in the process
7374 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7375 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7376 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7377 kdebase-workspace-data), and to get a more regular testing going on, I
7378 am working on a script to automate the test.&lt;/p&gt;
7379
7380 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7381 Gnome or KDE desktop installation inside the chroot before upgrading
7382 it. To ensure no services are started in the chroot, a policy-rc.d
7383 script is inserted. To make sure tasksel believe it is to install a
7384 desktop on a laptop, the tasksel tests are replaced in the chroot
7385 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7386
7387 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7388 currently always fail because udev refuses to upgrade with the kernel
7389 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7390 is created. The bug report
7391 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7392 this problem do not trigger in a chroot, but I touch the file anyway
7393 to make sure the upgrade go well. Testing on virtual and real
7394 hardware have failed me because of udev so far, and creating this file
7395 do the trick in such settings anyway. This is a
7396 &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
7397 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7398 maintainer because he lack the resources to rewrite udev to keep
7399 working with old kernels or something like that. I really wish the
7400 udev upstream would keep udev backwards compatible, to avoid such
7401 upgrade problem, but given that they fail to do so, I guess
7402 documenting the way out of this mess is the best option we got for
7403 Debian Squeeze.&lt;/p&gt;
7404
7405 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7406 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7407 trick:&lt;/p&gt;
7408
7409 &lt;blockquote&gt;&lt;pre&gt;
7410 #!/bin/sh
7411 set -ex
7412
7413 if [ &quot;$1&quot; ] ; then
7414 desktop=$1
7415 else
7416 desktop=gnome
7417 fi
7418
7419 from=lenny
7420 to=squeeze
7421
7422 exec &amp;lt; /dev/null
7423 unset LANG
7424 mirror=http://ftp.skolelinux.org/debian
7425 tmpdir=chroot-$from-upgrade-$to-$desktop
7426 fuser -mv .
7427 debootstrap $from $tmpdir $mirror
7428 chroot $tmpdir aptitude update
7429 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7430 #!/bin/sh
7431 exit 101
7432 EOF
7433 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7434 exit_cleanup() {
7435 umount $tmpdir/proc
7436 }
7437 mount -t proc proc $tmpdir/proc
7438 # Make sure proc is unmounted also on failure
7439 trap exit_cleanup EXIT INT
7440
7441 chroot $tmpdir aptitude -y install debconf-utils
7442
7443 # Make sure tasksel autoselection trigger. It need the test scripts
7444 # to return the correct answers.
7445 echo tasksel tasksel/desktop multiselect $desktop | \
7446 chroot $tmpdir debconf-set-selections
7447
7448 # Include the desktop and laptop task
7449 for test in desktop laptop ; do
7450 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7451 #!/bin/sh
7452 exit 2
7453 EOF
7454 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7455 done
7456
7457 DEBIAN_FRONTEND=noninteractive
7458 DEBIAN_PRIORITY=critical
7459 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7460 chroot $tmpdir tasksel --new-install
7461
7462 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7463 chroot $tmpdir aptitude update
7464 touch $tmpdir/etc/udev/kernel-upgrade
7465 chroot $tmpdir aptitude -y dist-upgrade
7466 fuser -mv
7467 &lt;/pre&gt;&lt;/blockquote&gt;
7468
7469 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7470 with aptitude, but I have not had time to look at how they behave
7471 differently so far. I hope to get a cron job running to do the test
7472 regularly and post the result on the web. The Gnome upgrade currently
7473 work, while the KDE upgrade fail because of the bug in
7474 kdebase-workspace-data&lt;/p&gt;
7475
7476 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7477 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7478 post, so I will refrain from trying. I can report that for Gnome,
7479 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7480 remove and 1 not upgraded and 1024MB need to be downloaded while for
7481 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7482 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7483
7484 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7485 is able to migrate to dependency based boot sequencing and parallel
7486 booting without a hitch. Was unsure if there were still bugs with
7487 packages failing to clean up their obsolete init.d script during
7488 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7489 packages.&lt;/p&gt;
7490 </description>
7491 </item>
7492
7493 <item>
7494 <title>Upstart or sysvinit - as init.d scripts see it</title>
7495 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7496 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7497 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7498 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7499 scripts to migrate (some of) their operations to upstart job while
7500 keeping the init.d for hurd and kfreebsd. The packages with such
7501 needs will need a way to get their init.d scripts to behave
7502 differently when used with sysvinit and with upstart. Because of
7503 this, I had a look at the environment variables set when a init.d
7504 script is running under upstart, and when it is not.&lt;/p&gt;
7505
7506 &lt;p&gt;With upstart, I notice these environment variables are set when a
7507 script is started from rcS.d/ (ignoring some irrelevant ones like
7508 COLUMNS):&lt;/p&gt;
7509
7510 &lt;blockquote&gt;&lt;pre&gt;
7511 DEFAULT_RUNLEVEL=2
7512 previous=N
7513 PREVLEVEL=
7514 RUNLEVEL=
7515 runlevel=S
7516 UPSTART_EVENTS=startup
7517 UPSTART_INSTANCE=
7518 UPSTART_JOB=rc-sysinit
7519 &lt;/pre&gt;&lt;/blockquote&gt;
7520
7521 &lt;p&gt;With sysvinit, these environment variables are set for the same
7522 script.&lt;/p&gt;
7523
7524 &lt;blockquote&gt;&lt;pre&gt;
7525 INIT_VERSION=sysvinit-2.88
7526 previous=N
7527 PREVLEVEL=N
7528 RUNLEVEL=S
7529 runlevel=S
7530 &lt;/pre&gt;&lt;/blockquote&gt;
7531
7532 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7533 sysvinit are not set by upstart. Not sure if it is intentional or not
7534 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7535
7536 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7537 looking for the UPSTART_JOB environment variable seem to be a good
7538 choice.&lt;/p&gt;
7539 </description>
7540 </item>
7541
7542 <item>
7543 <title>A manual for standards wars...</title>
7544 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7545 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7546 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7547 <description>&lt;p&gt;Via the
7548 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7549 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7550 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7551 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7552 following the standards wars of today.&lt;/p&gt;
7553 </description>
7554 </item>
7555
7556 <item>
7557 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7558 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7559 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7560 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7561 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7562 to get a list of the machine types in use thanks to the DMI
7563 information extracted from each machine. The script to do so is
7564 included in the sitesummary package, and here is example output from
7565 the Skolelinux build servers:&lt;/p&gt;
7566
7567 &lt;blockquote&gt;&lt;pre&gt;
7568 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7569 vendor count
7570 Dell Computer Corporation 1
7571 PowerEdge 1750 1
7572 IBM 1
7573 eserver xSeries 345 -[8670M1X]- 1
7574 Intel 2
7575 [no-dmi-info] 3
7576 maintainer:~#
7577 &lt;/pre&gt;&lt;/blockquote&gt;
7578
7579 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7580 provided in each machine. Here there are Intel machines without model
7581 information listed with Intel as vendor and no model, and virtual Xen
7582 machines listed as [no-dmi-info]. One can add -l as a command line
7583 option to list the individual machines.&lt;/p&gt;
7584
7585 &lt;p&gt;A larger list is
7586 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7587 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7588 provide the basic sitesummary report publicly. In their report there
7589 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7590 their machines, and as sitesummary is available in both distributions,
7591 it is trivial to get all of them to report to the same central
7592 collector.&lt;/p&gt;
7593 </description>
7594 </item>
7595
7596 <item>
7597 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7598 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7599 <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>
7600 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7601 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7602 start at boot when an NVidia video card is used is handled. The
7603 problem seem to be that the nvidia X.org driver uses a long time to
7604 initialize, and this duration is longer than kdm is configured to
7605 wait.&lt;/p&gt;
7606
7607 &lt;p&gt;I came across two bugs related to this issue,
7608 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7609 against initscripts and passed on to nvidia-glx when it became obvious
7610 that the nvidia drivers were involved, and
7611 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7612 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7613
7614 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7615 problem nvidia video card owners experience and make sure the Debian
7616 distribution work out of the box for these users. The nvidia driver
7617 maintainers expect kdm to be set up to wait longer, while kdm expect
7618 the nvidia driver maintainers to fix the driver to start faster, and
7619 while they wait for each other I guess the users end up switching to a
7620 distribution that work for them. I have no idea what the solution is,
7621 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7622
7623 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7624 </description>
7625 </item>
7626
7627 <item>
7628 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7629 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7630 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7631 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7632 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7633 The feature seem to hold up pretty well, but three fairly serious
7634 issues are known and should be solved:
7635
7636 &lt;p&gt;&lt;ul&gt;
7637
7638 &lt;li&gt;The wicd package seen to
7639 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7640 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7641 parallel booting is enabled. No idea why, but the wicd maintainer
7642 seem to be on the case.&lt;/li&gt;
7643
7644 &lt;li&gt;The nvidia X driver seem to
7645 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7646 triggered more easily when parallel booting is in effect. The
7647 maintainer is on the case.&lt;/li&gt;
7648
7649 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7650 sequencing (the shutdown is broken) when old file-rc users
7651 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7652 sysv-rc. One way to solve it would be for file-rc to create
7653 /etc/init.d/.legacy-bootordering, and another is to try to make
7654 sysv-rc more robust. Will investigate some more and probably upload a
7655 workaround in sysv-rc to help those trying to move from file-rc to
7656 sysv-rc get a working shutdown.&lt;/li&gt;
7657
7658 &lt;/ul&gt;&lt;/p&gt;
7659
7660 &lt;p&gt;All in all not many surprising issues, and all of them seem
7661 solvable before Squeeze is released. In addition to these there are
7662 some packages with bugs in their dependencies and run level settings,
7663 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7664
7665 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7666 the BTS, please usertag the report to get it to show up at
7667 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7668 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7669
7670 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7671 </description>
7672 </item>
7673
7674 <item>
7675 <title>More flexible firmware handling in debian-installer</title>
7676 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7677 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7678 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7679 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7680 found time today to return to the project. Having to spend less time
7681 working dependency based boot in debian, as it is almost complete now,
7682 definitely helped freeing some time.&lt;/p&gt;
7683
7684 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7685 include some firmware packages on the Debian Edu CDs, those needed to
7686 get disk and network controllers working. Without having these
7687 firmware packages available during installation, it is impossible to
7688 install Debian Edu on the given machine, and because our target group
7689 are non-technical people, asking them to provide firmware packages on
7690 an external medium is a support pain. Initially, I expected it to be
7691 enough to include the firmware packages on the CD to get
7692 debian-installer to find and use them. This proved to be wrong.
7693 Next, I hoped it was enough to symlink the relevant firmware packages
7694 to some useful location on the CD (tried /cdrom/ and
7695 /cdrom/firmware/). This also proved to not work, and at this point I
7696 found time to look at the debian-installer code to figure out what was
7697 going to work.&lt;/p&gt;
7698
7699 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7700 look revealed that it would only look for firmware packages outside
7701 the installation media, so the CD was never checked for firmware
7702 packages. It would only check USB sticks, floppies and other
7703 &quot;external&quot; media devices. Today I changed it to also look in the
7704 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7705 solve the problem I ran into with Debian edu. I also changed it to
7706 look in /firmware/, to make sure the installer also find firmware
7707 provided in the initrd when booting the installer via PXE, to allow us
7708 to provide the same feature in the PXE setup included in Debian
7709 Edu.&lt;/p&gt;
7710
7711 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7712 activated without asking if the license is accepted, I extended
7713 hw-detect to look for preinst scripts in the firmware packages, and
7714 run these before activating the firmware during installation. The
7715 license question is asked using debconf in the preinst, so this should
7716 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7717
7718 &lt;p&gt;If you want to discuss the details of these features, please
7719 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7720 </description>
7721 </item>
7722
7723 <item>
7724 <title>Parallellized boot is now the default in Debian/unstable</title>
7725 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7726 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7727 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7728 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7729 Debian/unstable for machines using dependency based boot sequencing.
7730 Apparently the testing of concurrent booting has been wider than
7731 expected, if I am to believe the
7732 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7733 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7734 with the feature this weekend, to give us some time to detect any
7735 remaining problems before Squeeze is frozen. If serious problems are
7736 detected, it is simple to change the default back to sequential boot.
7737 The upload of the new sysvinit package also activate a new upstream
7738 version.&lt;/p&gt;
7739
7740 More information about
7741 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7742 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
7743 currently possible to disable parallel booting when one run into
7744 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
7745
7746 &lt;blockquote&gt;&lt;pre&gt;
7747 CONCURRENCY=none
7748 &lt;/pre&gt;&lt;/blockquote&gt;
7749
7750 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7751 the BTS, please usertag the report to get it to show up at
7752 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7753 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7754 </description>
7755 </item>
7756
7757 <item>
7758 <title>Sitesummary tip: Listing MAC address of all clients</title>
7759 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
7760 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
7761 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
7762 <description>&lt;p&gt;In the recent Debian Edu versions, the
7763 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
7764 system&lt;/a&gt; is used to keep track of the machines in the school
7765 network. Each machine will automatically report its status to the
7766 central server after boot and once per night. The network setup is
7767 also reported, and using this information it is possible to get the
7768 MAC address of all network interfaces in the machines. This is useful
7769 to update the DHCP configuration.&lt;/p&gt;
7770
7771 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
7772 ist all MAC addresses of all machines reporting to sitesummary. Run
7773 this on the collector host:&lt;/p&gt;
7774
7775 &lt;blockquote&gt;&lt;pre&gt;
7776 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
7777 &lt;/pre&gt;&lt;/blockquote&gt;
7778
7779 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
7780 line per machine and with space between the MAC addresses.&lt;/p&gt;
7781
7782 &lt;p&gt;To allow system administrators easier job at adding static DHCP
7783 addresses for hosts, it would be possible to extend this to fetch
7784 machine information from sitesummary and update the DHCP and DNS
7785 tables in LDAP using this information. Such tool is unfortunately not
7786 written yet.&lt;/p&gt;
7787 </description>
7788 </item>
7789
7790 <item>
7791 <title>systemd, an interesting alternative to upstart</title>
7792 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
7793 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
7794 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
7795 <description>&lt;p&gt;The last few days a new boot system called
7796 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
7797 has been
7798 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
7799
7800 to the free software world. I have not yet had time to play around
7801 with it, but it seem to be a very interesting alternative to
7802 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
7803 a good alternative for Debian when we are able to switch to an event
7804 based boot system. Tollef is
7805 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
7806 systemd into Debian, and I look forward to seeing how well it work. I
7807 like the fact that systemd handles init.d scripts with dependency
7808 information natively, allowing them to run in parallel where upstart
7809 at the moment do not.&lt;/p&gt;
7810
7811 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
7812 platform support. It only work on recent Linux kernels, and also need
7813 some new kernel features enabled to function properly. This means
7814 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7815 system. Not sure how that will be handled if systemd proves to be the
7816 way forward.&lt;/p&gt;
7817
7818 &lt;p&gt;In the mean time, based on the
7819 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7820 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
7821 decided to enable full parallel booting as the default in Debian as
7822 soon as possible (probably this weekend or early next week), to see if
7823 there are any remaining serious bugs in the init.d dependencies. A
7824 new version of the sysvinit package implementing this change is
7825 already in experimental. If all go well, Squeeze will be released
7826 with parallel booting enabled by default.&lt;/p&gt;
7827 </description>
7828 </item>
7829
7830 <item>
7831 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
7832 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
7833 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
7834 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
7835 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
7836 complete, so complete that it is actually possible to run all the
7837 init.d scripts in parallell based on these dependencies. If you want
7838 to test your Squeeze system, make sure
7839 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7840 based boot sequencing&lt;/a&gt; is enabled, and add this line to
7841 /etc/default/rcS:&lt;/p&gt;
7842
7843 &lt;blockquote&gt;&lt;pre&gt;
7844 CONCURRENCY=makefile
7845 &lt;/pre&gt;&lt;/blockquote&gt;
7846
7847 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
7848 scripts in parallel using the dependency information stored in
7849 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
7850 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7851 to try to start the kdm and gdm scripts as early as possible, and will
7852 start the facilities required by kdm or gdm as early as possible to
7853 make this happen.&lt;/p&gt;
7854
7855 &lt;p&gt;Give it a try, and see if you like the result. If some services
7856 fail to start properly, it is most likely because they have incomplete
7857 init.d script dependencies in their startup script (or some of their
7858 dependent scripts have incomplete dependencies). Report bugs and get
7859 the package maintainers to fix it. :)&lt;/p&gt;
7860
7861 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
7862 manage to get the init.d script dependencies complete and correct. I
7863 expect we will get there in Squeeze+1, if we get manage to test and
7864 fix the remaining issues.&lt;/p&gt;
7865
7866 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7867 the BTS, please usertag the report to get it to show up at
7868 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7869 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7870 </description>
7871 </item>
7872
7873 <item>
7874 <title>Debian has switched to dependency based boot sequencing</title>
7875 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
7876 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
7877 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
7878 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
7879 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
7880 have been migrated to using dependency based boot sequencing. This
7881 conclude work me and others have been doing for the last three days.
7882 It feels great to see this finally part of the default Debian
7883 installation. Now we just need to weed out the last few problems that
7884 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
7885
7886 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
7887 fixing the more fundamental problem of handing the event based
7888 non-predictable kernel in the early boot.&lt;/p&gt;
7889 </description>
7890 </item>
7891
7892 <item>
7893 <title>Taking over sysvinit development</title>
7894 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
7895 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
7896 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
7897 <description>&lt;p&gt;After several years of frustration with the lack of activity from
7898 the existing sysvinit upstream developer, I decided a few weeks ago to
7899 take over the package and become the new upstream. The number of
7900 patches to track for the Debian package was becoming a burden, and the
7901 lack of synchronization between the distribution made it hard to keep
7902 the package up to date.&lt;/p&gt;
7903
7904 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7905 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
7906 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
7907 and Fedora), based on the patches currently in use in these
7908 distributions. We Debian maintainers plan to move to this tarball as
7909 the new upstream as soon as we find time to do the merge. Since the
7910 new tarball was created, we agreed with Werner at SuSe to make a new
7911 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
7912 development there. The project is registered and currently waiting
7913 for approval by the Savannah administrators, and as soon as it is
7914 approved, we will import the old versions from svn and continue
7915 working on the future release.&lt;/p&gt;
7916
7917 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
7918 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
7919 </description>
7920 </item>
7921
7922 <item>
7923 <title>Debian boots quicker and quicker</title>
7924 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
7925 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
7926 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
7927 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
7928 people involved in the boot system on Debian and Ubuntu, to see if we
7929 could find more ways to speed up the boot system. This was an Ubuntu
7930 funded
7931 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
7932 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
7933 of boot systems, and ways to handle the increasing number of boot
7934 issues introduced by the Linux kernel becoming more and more
7935 asynchronous and event base. The Ubuntu approach using udev and
7936 upstart might be a good way forward. Time will show.&lt;/p&gt;
7937
7938 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
7939 process in Debian. All of these should be applied to get a quick
7940 boot:&lt;/p&gt;
7941
7942 &lt;ul&gt;
7943
7944 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
7945
7946 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
7947 clock is in UTC.&lt;/li&gt;
7948
7949 &lt;li&gt;Install and activate the insserv package to enable
7950 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7951 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
7952
7953 &lt;/ul&gt;
7954
7955 These points are based on the Google summer of code work done by
7956 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
7957 Villegas&lt;/a&gt;.
7958
7959 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7960 unstable yesterday. When we tested it, we were able to cut 6 seconds
7961 from the boot sequence. It depend on very correct dependency
7962 declaration in all init.d scripts, so I expect us to find edge cases
7963 where the dependences in some scripts are slightly wrong when we start
7964 using this.&lt;/p&gt;
7965
7966 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7967 introduced by Raphael Geissert today, one that could affect the
7968 startup speed as well. Instead of starting some scripts concurrently
7969 from rcS.d/ and another set of scripts from rc2.d/, it would be
7970 possible to run a of them in the same process. A quick way to test
7971 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7972 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7973 </description>
7974 </item>
7975
7976 <item>
7977 <title>BSAs påstander om piratkopiering møter motstand</title>
7978 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7979 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7980 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7981 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7982 programvareselskapene som Microsoft og Apple, publisert en rapport der
7983 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7984 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7985 dager siden kom
7986 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7987 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7988 dagene. Et spesielt interessant kommentar fra Sverige,
7989 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7990 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7991
7992 &lt;blockquote&gt;
7993 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7994 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7995 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7996 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7997 &lt;/blockquote&gt;
7998
7999 &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
8000 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
8001 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
8002 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
8003 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
8004
8005 &lt;p&gt;Fant lenkene via &lt;a
8006 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
8007 på Slashdot&lt;/a&gt;.&lt;/p&gt;
8008 </description>
8009 </item>
8010
8011 <item>
8012 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
8013 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
8014 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
8015 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
8016 <description>&lt;p&gt;Kom over
8017 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
8018 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8019 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8020 jobber til daglig. En rask opptelling forteller meg at vi har 490
8021 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
8022 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
8023 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
8024 </description>
8025 </item>
8026
8027 <item>
8028 <title>Kryptert harddisk - naturligvis</title>
8029 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
8030 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
8031 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
8032 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
8033 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
8034 når en tar tap av arbeidstid, fortrolige dokumenter,
8035 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8036 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8037 til at jeg har kryptert harddisken på både kontormaskinen og min
8038 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8039 komme på avveie, den første informasjon relatert til jobben min ved
8040 Universitetet i Oslo, og den andre relatert til blant annet
8041 foreningsarbeide. Kryptering av diskene gjør at det er lite
8042 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8043 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8044 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8045 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8046 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8047 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8048 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8049 det er gjort slik jeg gjør det er minimale, og gevinstene er
8050 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8051 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
8052
8053 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8054 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8055 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8056 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8057 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8058 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8059 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8060 betydelige.&lt;/p&gt;
8061 </description>
8062 </item>
8063
8064 <item>
8065 <title>Two projects that have improved the quality of free software a lot</title>
8066 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
8067 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
8068 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
8069 <description>&lt;p&gt;There are two software projects that have had huge influence on the
8070 quality of free software, and I wanted to mention both in case someone
8071 do not yet know them.&lt;/p&gt;
8072
8073 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
8074 tool to detect and expose errors in the memory handling of programs.
8075 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
8076 and it will report any problems on stdout. It is even better if the
8077 program include debug information. With debug information, it is able
8078 to report the source file name and line number where the problem
8079 occurs. It can report things like &#39;reading past memory block in file
8080 X line N, the memory block was allocated in file Y, line M&#39;, and
8081 &#39;using uninitialised value in control logic&#39;. This tool has made it
8082 trivial to investigate reproducible crash bugs in programs, and have
8083 reduced the number of this kind of bugs in free software a lot.
8084
8085 &lt;p&gt;The second one is
8086 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
8087 a source code checker. It is able to process the source of a program
8088 and find problems in the logic without running the program. It
8089 started out as the Stanford Checker and became well known when it was
8090 used to find bugs in the Linux kernel. It is now a commercial tool
8091 and the company behind it is running
8092 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
8093 free software community, where a lot of free software projects get
8094 their source checked for free. Several thousand defects have been
8095 found and fixed so far. It can find errors like &#39;lock L taken in file
8096 X line N is never released if exiting in line M&#39;, or &#39;the code in file
8097 Y lines O to P can never be executed&#39;. The projects included in the
8098 community service project have managed to get rid of a lot of
8099 reliability problems thanks to Coverity.&lt;/p&gt;
8100
8101 &lt;p&gt;I believe tools like this, that are able to automatically find
8102 errors in the source, are vital to improve the quality of software and
8103 make sure we can get rid of the crashing and failing software we are
8104 surrounded by today.&lt;/p&gt;
8105 </description>
8106 </item>
8107
8108 <item>
8109 <title>No patch is not better than a useless patch</title>
8110 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
8111 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
8112 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
8113 <description>&lt;p&gt;Julien Blache
8114 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
8115 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
8116 patch allow one to discuss a concrete and proposed solution, and also
8117 prove that the issue at hand is important enough for someone to spent
8118 time on fixing it. No patch do not provide any of these positive
8119 properties.&lt;/p&gt;
8120 </description>
8121 </item>
8122
8123 <item>
8124 <title>Standardize on protocols and formats, not vendors and applications</title>
8125 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
8126 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
8127 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
8128 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
8129 very good one to form a long lived computer infrastructure. It is the
8130 simple one, lost by many in todays computer industry: Standardize on
8131 open network protocols and open exchange/storage formats, not applications.
8132 Applications come and go, while protocols and files tend to stay, and
8133 thus one want to make it easy to change application and vendor, while
8134 avoiding conversion costs and locking users to a specific platform or
8135 application.&lt;/p&gt;
8136
8137 &lt;p&gt;This approach make it possible to replace the client applications
8138 independently of the server applications. One can even allow users to
8139 use several different applications as long as they handle the selected
8140 protocol and format. In the normal case, only one client application
8141 is recommended and users only get help if they choose to use this
8142 application, but those that want to deviate from the easy path are not
8143 blocked from doing so.&lt;/p&gt;
8144
8145 &lt;p&gt;It also allow us to replace the server side without forcing the
8146 users to replace their applications, and thus allow us to select the
8147 best server implementation at any moment, when scale and resouce
8148 requirements change.&lt;/p&gt;
8149
8150 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
8151 open formats, but I would never recommend standardizing on a single
8152 application that do not use open network protocol or open formats.&lt;/p&gt;
8153 </description>
8154 </item>
8155
8156 <item>
8157 <title>Returning from Skolelinux developer gathering</title>
8158 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
8159 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
8160 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
8161 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
8162 Edu/Skolelinux development gathering. I got a bit done tuning the
8163 desktop, and looked into the dynamic service location protocol
8164 implementation avahi. It look like it could be useful for us. Almost
8165 30 people participated, and I believe it was a great environment to
8166 get to know the Skolelinux system. Walter Bender, involved in the
8167 development of the Sugar educational platform, presented his stuff and
8168 also helped me improve my OLPC installation. He also showed me that
8169 his Turtle Art application can be used in standalone mode, and we
8170 agreed that I would help getting it packaged for Debian. As a
8171 standalone application it would be great for Debian Edu. We also
8172 tried to get the video conferencing working with two OLPCs, but that
8173 proved to be too hard for us. The application seem to need more work
8174 before it is ready for me. I look forward to getting home and relax
8175 now. :)&lt;/p&gt;
8176 </description>
8177 </item>
8178
8179 <item>
8180 <title>Time for new LDAP schemas replacing RFC 2307?</title>
8181 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
8182 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
8183 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
8184 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
8185 optimal. There is RFC 2307 documenting one way to store NIS maps in
8186 LDAP, and a modified version of this normally called RFC 2307bis, with
8187 some modifications to be compatible with Active Directory. The RFC
8188 specification handle the content of a lot of system databases, but do
8189 not handle DNS zones and DHCP configuration.&lt;/p&gt;
8190
8191 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
8192 we would like to store information about users, SMB clients/hosts,
8193 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8194 and LTSP configuration in LDAP. These objects have a lot in common,
8195 but with the current LDAP schemas it is not possible to have one
8196 object per entity. For example, one need to have at least three LDAP
8197 objects for a given computer, one with the SMB related stuff, one with
8198 DNS information and another with DHCP information. The schemas
8199 provided for DNS and DHCP are impossible to combine into one LDAP
8200 object. In addition, it is impossible to implement quick queries for
8201 netgroup membership, because of the way NIS triples are implemented.
8202 It just do not scale. I believe it is time for a few RFC
8203 specifications to cleam up this mess.&lt;/p&gt;
8204
8205 &lt;p&gt;I would like to have one LDAP object representing each computer in
8206 the network, and this object can then keep the SMB (ie host key), DHCP
8207 (mac address/name) and DNS (name/IP address) settings in one place.
8208 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
8209
8210 &lt;p&gt;I would also like to have a quick way to map from a user or
8211 computer and to the net group this user or computer is a member.&lt;/p&gt;
8212
8213 &lt;p&gt;Active Directory have done a better job than unix heads like myself
8214 in this regard, and the unix side need to catch up. Time to start a
8215 new IETF work group?&lt;/p&gt;
8216 </description>
8217 </item>
8218
8219 <item>
8220 <title>Endelig er Debian Lenny gitt ut</title>
8221 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
8222 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
8223 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
8224 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
8225 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
8226 Et langt steg videre for Debian-prosjektet, og en rekke nye
8227 programpakker blir nå tilgjengelig for de av oss som bruker den
8228 stabile utgaven av Debian. Neste steg er nå å få
8229 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
8230 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
8231 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8232 slippes løs på skolene. Takk til alle debian-utviklerne som har
8233 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8234 bootsekvens tilgjengelig i stabil utgave, vha pakken
8235 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
8236 </description>
8237 </item>
8238
8239 <item>
8240 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
8241 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
8242 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
8243 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
8244 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
8245 Oslo. Most of Saturday was used for the general assemly for the
8246 member organization, but the rest of the weekend I used to tune the
8247 LTSP installation. LTSP now work out of the box on the 10-network.
8248 Acer Aspire One proved to be a very nice thin client, with both
8249 screen, mouse and keybard in a small box. Was working on getting the
8250 diskless workstation setup configured out of the box, but did not
8251 finish it before the weekend was up.&lt;/p&gt;
8252
8253 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
8254 the Brazilian group, so that will have to wait for the next
8255 development gathering. Would love to have the Debian Edu installer
8256 automatically detect and configure a multiseat setup when it find one
8257 of these cards.&lt;/p&gt;
8258 </description>
8259 </item>
8260
8261 <item>
8262 <title>The sorry state of multimedia browser plugins in Debian</title>
8263 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
8264 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
8265 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
8266 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
8267 plugins available in Debian Lenny, to see which one we should use by
8268 default in Debian Edu. We need an embedded video playing plugin with
8269 control buttons to pause or stop the video, and capable of streaming
8270 all the multimedia content available on the web. The test results and
8271 notes are available on
8272 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
8273 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
8274 fill this need. My personal video player favorite, VLC, has a really
8275 bad plugin which fail on a lot of the test pages. A lot of the MIME
8276 types I would expect to work with any free software player (like
8277 video/ogg), just do not work. And simple formats like the
8278 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
8279 totem and vlc plugins. I hope the situation will improve soon. No
8280 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
8281
8282 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
8283 be the only one fitting our needs. :/&lt;/p&gt;
8284 </description>
8285 </item>
8286
8287 </channel>
8288 </rss>