]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
646ea5158f30eaa61033aa0b6eab00b95b2826e3
[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>Using appstream in Debian to locate packages with firmware and mime type support</title>
11 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
13 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
14 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
15 is taking shape in Debian, and one provided feature is a very
16 convenient way to tell you which package to install to make a given
17 firmware file available when the kernel is looking for it. This can
18 be done using apt-file too, but that is for someone else to blog
19 about. :)&lt;/p&gt;
20
21 &lt;p&gt;Here is a small recipe to find the package with a given firmware
22 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
23 picked from the set of firmware announced using appstream in Debian
24 unstable. In general you would be looking for the firmware requested
25 by the kernel during kernel module loading. To find the package
26 providing the example file, do like this:&lt;/p&gt;
27
28 &lt;blockquote&gt;&lt;pre&gt;
29 % apt install appstream
30 [...]
31 % apt update
32 [...]
33 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
34 awk &#39;/Package:/ {print $2}&#39;
35 firmware-qlogic
36 %
37 &lt;/pre&gt;&lt;/blockquote&gt;
38
39 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
40 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
41 a way appstream can use.&lt;/p&gt;
42
43 &lt;p&gt;This same approach can be used to find any package supporting a
44 given MIME type. This is very useful when you get a file you do not
45 know how to handle. First find the mime type using &lt;tt&gt;file
46 --mime-type&lt;/tt&gt;, and next look up the package providing support for
47 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
48 and you can find all packages handling this type like this:&lt;/p&gt;
49
50 &lt;blockquote&gt;&lt;pre&gt;
51 % apt install appstream
52 [...]
53 % apt update
54 [...]
55 % appstreamcli what-provides mimetype image/svg+xml | \
56 awk &#39;/Package:/ {print $2}&#39;
57 bkchem
58 phototonic
59 inkscape
60 shutter
61 tetzle
62 geeqie
63 xia
64 pinta
65 gthumb
66 karbon
67 comix
68 mirage
69 viewnior
70 postr
71 ristretto
72 kolourpaint4
73 eog
74 eom
75 gimagereader
76 midori
77 %
78 &lt;/pre&gt;&lt;/blockquote&gt;
79
80 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
81 packages providing appstream metadata.&lt;/p&gt;
82 </description>
83 </item>
84
85 <item>
86 <title>Creepy, visualise geotagged social media information - nice free software</title>
87 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
88 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
89 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
90 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
91 with the computerised radio beacon known as a mobile phone their
92 position is tracked by the phone company and often stored for a long
93 time (like every time a SMS is received or sent). And if their
94 computerised radio beacon is capable of running programs (often called
95 mobile apps) downloaded from the Internet, these programs are often
96 also capable of tracking their location (if the app requested access
97 during installation). And when these programs send out information to
98 central collection points, the location is often included, unless
99 extra care is taken to not send the location. The provided
100 information is used by several entities, for good and bad (what is
101 good and bad, depend on your point of view). What is certain, is that
102 the private sphere and the right to free movement is challenged and
103 perhaps even eradicated for those announcing their location this way,
104 when they share their whereabouts with private and public
105 entities.&lt;/p&gt;
106
107 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-01-24-nice-creepy-desktop-window.png&quot;&gt;&lt;/p&gt;
108
109 &lt;p&gt;The phone company logs provide a register of locations to check out
110 when one want to figure out what the tracked person was doing. It is
111 unavailable for most of us, but provided to selected government
112 officials, company staff, those illegally buying information from
113 unfaithful servants and crackers stealing the information. But the
114 public information can be collected and analysed, and a free software
115 tool to do so is called
116 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
117 discovered it when I read
118 &lt;a href=&quot;http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-7787884.html&quot;&gt;an
119 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
120 November 2014, and decided to check if it was available in Debian.
121 The python program was in Debian, but
122 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
123 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
124 uploaded a new version which did not work quite right, but did not
125 have time to fix it then. This Christmas I decided to finally try to
126 get Creepy operational in Debian. Now a fixed version is available in
127 Debian unstable and testing, and almost all Debian specific patches
128 are now included
129 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
130
131 &lt;p&gt;The Creepy program visualises geolocation information fetched from
132 Twitter, Instagram, Flickr and Google+, and allow one to get a
133 complete picture of every social media message posted recently in a
134 given area, or track the movement of a given individual across all
135 these services. Earlier it was possible to use the search API of at
136 least some of these services without identifying oneself, but these
137 days it is impossible. This mean that to use Creepy, you need to
138 configure it to log in as yourself on these services, and provide
139 information to them about your search interests. This should be taken
140 into account when using Creepy, as it will also share information
141 about yourself with the services.&lt;/p&gt;
142
143 &lt;p&gt;The picture above show the twitter messages sent from (or at least
144 geotagged with a position from) the city centre of Oslo, the capital
145 of Norway. One useful way to use Creepy is to first look at
146 information tagged with an area of interest, and next look at all the
147 information provided by one or more individuals who was in the area.
148 I tested it by checking out which celebrity provide their location in
149 twitter messages by checkout out who sent twitter messages near a
150 Norwegian TV station, and next could track their position over time,
151 making it possible to locate their home and work place, among other
152 things. A similar technique have been
153 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
154 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
155 tool to discover lying governments, and a useful tool to help people
156 understand the value of the private information they provide to the
157 public.&lt;/p&gt;
158
159 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
160 it depend on several python modules currently missing in Jessie (at
161 least python-instagram, python-flickrapi and
162 python-requests-toolbelt).&lt;/p&gt;
163
164 &lt;p&gt;(I have uploaded
165 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
166 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
167 Creepy program in Debian.)&lt;/p&gt;
168 </description>
169 </item>
170
171 <item>
172 <title>Always download Debian packages using Tor - the simple recipe</title>
173 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
174 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
175 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
176 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
177 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
178 that those listening on the Internet lines would have good reason to
179 believe a computer have a given security hole&lt;/a&gt; if it download a
180 security fix from a Debian mirror. This is a good reason to always
181 use encrypted connections to the Debian mirror, to make sure those
182 listening do not know which IP address to attack. In August, Richard
183 Hartmann observed that encryption was not enough, when it was possible
184 to interfere download size to security patches or the fact that
185 download took place shortly after a security fix was released, and
186 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
187 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
188 was not the first to propose this, as the
189 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/apt-transport-tor&quot;&gt;apt-transport-tor&lt;/a&gt;&lt;/tt&gt;
190 package by Tim Retout already existed to make it easy to convince apt
191 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
192 aware of that package when I read the blog post from Richard.&lt;/p&gt;
193
194 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
195 sysadmins, and he set up a Tor hidden service on one of the central
196 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
197 it possible to download packages directly between two tor nodes,
198 making sure the network traffic always were encrypted.&lt;/p&gt;
199
200 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
201 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
202 urls with tor+http and tor+https, and using the hidden service instead
203 of the official Debian mirror site. I recommend installing
204 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
205 done in /etc/.&lt;/p&gt;
206
207 &lt;blockquote&gt;&lt;pre&gt;
208 apt install apt-transport-tor
209 sed -i &#39;s% http://ftp.debian.org/%tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
210 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
211 &lt;/pre&gt;&lt;/blockquote&gt;
212
213 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
214 the sed commands for these too. The sed command is assuming your are
215 using the ftp.debian.org Debian mirror. Adjust the command (or just
216 edit the file manually) to match your mirror.&lt;/p&gt;
217
218 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
219 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
220 system, and do not work with these tor+http URLs. For
221 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
222 which need a recent apt version currently only in unstable. So if you
223 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
224
225 &lt;p&gt;Another advantage from this change is that your machine will start
226 using Tor regularly and at fairly random intervals (every time you
227 update the package lists or upgrade or install a new package), thus
228 masking other Tor traffic done from the same machine. Using Tor will
229 become normal for the machine in question.&lt;/p&gt;
230
231 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
232 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
233 enabled. It would be great if it was the default on any Debian
234 system.&lt;/p&gt;
235 </description>
236 </item>
237
238 <item>
239 <title>OpenALPR, find car license plates in video streams - nice free software</title>
240 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
241 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
242 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
243 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
244 call the car license plate numbers in those days. I would write the
245 numbers down in my little book and compare notes with the other kids
246 to see how many region codes we had seen and if we had seen some
247 exotic or special region codes and numbers. It was a fun game to pass
248 time, as we kids have plenty of it.&lt;/p&gt;
249
250 &lt;p&gt;A few days I came across
251 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
252 project&lt;/a&gt;, a free software project to automatically discover and
253 report license plates in images and video streams, and provide the
254 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
255 such system for a while now, because I believe it is a bad idea that the
256 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
257 number plate recognition&lt;/a&gt; tool only is available in the hands of
258 the powerful, and want it to be available also for the powerless to
259 even the score when it comes to surveillance and sousveillance. I
260 discovered the developer
261 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
262 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
263 help him get it into shape to get the package uploaded into the Debian
264 archive.&lt;/p&gt;
265
266 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
267 it into Debian, where it currently
268 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
269 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
270
271 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
272 for the common folks, ie those not running a large government
273 surveillance system? Well, I plan to put it in a computer on my bike
274 and in my car, tracking the cars nearby and allowing me to be notified
275 when number plates on my watch list are discovered. Another use case
276 was suggested by a friend of mine, who wanted to set it up at his home
277 to open the car port automatically when it discovered the plate on his
278 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
279 capable of placing his license plate number of a piece of cardboard to
280 open his car port, men replied that it was always unlocked anyway. I
281 guess for such use case it make sense. I am sure there are other use
282 cases too, for those with imagination and a vision.&lt;/p&gt;
283
284 &lt;p&gt;If you want to build your own version of the Debian package, check
285 out the upstream git source and symlink ./distros/debian to ./debian/
286 before running &quot;debuild&quot; to build the source. Or wait a bit until the
287 package show up in unstable.&lt;/p&gt;
288 </description>
289 </item>
290
291 <item>
292 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
293 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
294 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
295 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
296 <description>&lt;p&gt;Around three years ago, I created
297 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
298 system&lt;/a&gt; to get a more practical solution in Debian for handing
299 hardware related packages. A GUI system in the isenkram package will
300 present a pop-up dialog when some hardware dongle supported by
301 relevant packages in Debian is inserted into the machine. The same
302 lookup mechanism to detect packages is available as command line
303 tools in the isenkram-cli package. In addition to mapping hardware,
304 it will also map kernel firmware files to packages and make it easy to
305 install needed firmware packages automatically. The key for this
306 system to work is a good way to map hardware to packages, in other
307 words, allow packages to announce what hardware they will work
308 with.&lt;/p&gt;
309
310 &lt;p&gt;I started by providing data files in the isenkram source, and
311 adding code to download the latest version of these data files at run
312 time, to ensure every user had the most up to date mapping available.
313 I also added support for storing the mapping in the Packages file in
314 the apt repositories, but did not push this approach because while I
315 was trying to figure out how to best store hardware/package mappings,
316 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
317 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
318 add the hardware mapping into that data set to be able to use
319 appstream as a data source, and this was accepted at least for the
320 Debian version of appstream.&lt;/p&gt;
321
322 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
323 and today I uploaded a new version 0.20 of isenkram adding support for
324 appstream as a data source for mapping hardware to packages. The only
325 package so far using appstream to announce its hardware support is my
326 pymissile package. I got help from Matthias Klumpp with figuring out
327 how do add the required
328 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
329 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
330 this content:&lt;/p&gt;
331
332 &lt;blockquote&gt;&lt;pre&gt;
333 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
334 &amp;lt;component&amp;gt;
335 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
336 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
337 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
338 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
339 &amp;lt;description&amp;gt;
340 &amp;lt;p&amp;gt;
341 Pymissile provides a curses interface to control an original
342 Marks and Spencer / Striker USB Missile Launcher, as well as a
343 motion control script to allow a webcamera to control the
344 launcher.
345 &amp;lt;/p&amp;gt;
346 &amp;lt;/description&amp;gt;
347 &amp;lt;provides&amp;gt;
348 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
349 &amp;lt;/provides&amp;gt;
350 &amp;lt;/component&amp;gt;
351 &lt;/pre&gt;&lt;/blockquote&gt;
352
353 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
354 which is a glob style match rule for hardware specific strings
355 (modalias strings) provided by the Linux kernel. In this case, it
356 will map to all USB devices with vendor code 1130 and product code
357 0202.&lt;/p&gt;
358
359 &lt;p&gt;Note, it is important that the license of all the metadata files
360 are compatible to have permissions to aggregate them into archive wide
361 appstream files. Matthias suggested to use MIT or BSD licenses for
362 these files. A challenge is figuring out a good id for the data, as
363 it is supposed to be globally unique and shared across distributions
364 (in other words, best to coordinate with upstream what to use). But
365 it can be changed later or, so we went with the package name as
366 upstream for this project is dormant.&lt;/p&gt;
367
368 &lt;p&gt;To get the metadata file installed in the correct location for the
369 mirror update scripts to pick it up and include its content the
370 appstream data source, the file must be installed in the binary
371 package under /usr/share/appdata/. I did this by adding the following
372 line to debian/pymissile.install:&lt;/p&gt;
373
374 &lt;blockquote&gt;&lt;pre&gt;
375 debian/pymissile.metainfo.xml usr/share/appdata
376 &lt;/pre&gt;&lt;/blockquote&gt;
377
378 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
379 all packages useful on the current computer automatically, and the GUI
380 pop-up handler will propose to install the package not already
381 installed if a hardware dongle is inserted into the machine in
382 question.&lt;/p&gt;
383
384 &lt;p&gt;Details of the modalias field in appstream is available from the
385 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
386
387 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
388 try running this command on the command line:&lt;/p&gt;
389
390 &lt;blockquote&gt;&lt;pre&gt;
391 cat $(find /sys/devices/|grep modalias)
392 &lt;/pre&gt;&lt;/blockquote&gt;
393
394 &lt;p&gt;To learn more about the isenkram system, please check out
395 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
396 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
397 </description>
398 </item>
399
400 <item>
401 <title>The GNU General Public License is not magic pixie dust</title>
402 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
403 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
404 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
405 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
406 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
407 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
408 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
409 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
410
411 &lt;blockquote&gt;
412
413 &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;
414
415 &lt;blockquote&gt;
416 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
417
418 The first step is to choose a
419 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
420 code.&lt;br/&gt;
421
422 The next step is, when someone fails to follow that copyleft license,
423 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
424
425 and its a simple fact of our modern society that such type of
426 work&lt;br/&gt;
427
428 is incredibly expensive to do and incredibly difficult to do.
429 &lt;/blockquote&gt;
430
431 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
432 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
433 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
434 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
435
436 &lt;p&gt;As the Debian Website
437 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
438 &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;
439 imply, public domain and permissively licensed software can lead to
440 the production of more proprietary software as people discover useful
441 software, extend it and or incorporate it into their hardware or
442 software products. Copyleft licenses such as the GNU GPL were created
443 to close off this avenue to the production of proprietary software but
444 such licenses are not enough. With the ongoing adoption of Free
445 Software by individuals and groups, inevitably the community&#39;s
446 expectations of license compliance are violated, usually out of
447 ignorance of the way Free Software works, but not always. As Karen
448 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
449 Freedom&quot;&gt;FaiF&lt;/a&gt;
450 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
451 copyleft is nothing if no-one is willing and able to stand up in court
452 to protect it. The reality of today&#39;s world is that legal
453 representation is expensive, difficult and time consuming. With
454 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
455 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
456 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
457 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
458 of the Linux project, Debian and other groups against GPL violations.
459 In March the SFC supported a
460 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
461 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
462 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
463 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
464 kernel. Since then two of their sponsors pulled corporate funding and
465 conferences
466 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
467 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
468 less on corporate funding and more on the broad community of
469 individuals who support Free Software and copyleft. So the SFC has
470 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
471 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
472 a community of folks who stand up for copyleft and the GPL by
473 supporting their work on promoting and supporting copyleft and Free
474 Software.&lt;/p&gt;
475
476 &lt;p&gt;If you support Free Software,
477 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
478 what the SFC do, agree with their
479 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
480 principles&lt;/a&gt;, are happy about their
481 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
482 work on a project that is an SFC
483 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
484 just want to stand up for copyleft, please join
485 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
486 Allan Webber&lt;/a&gt;,
487 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
488 Smith&lt;/a&gt;,
489 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
490 Bacon&lt;/a&gt;, myself and
491 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
492 becoming a
493 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
494 next week your donation will be
495 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
496 by an anonymous donor. Please also consider asking your employer to
497 match your donation or become a sponsor of SFC. Don&#39;t forget to
498 spread the word about your support for SFC via email, your blog and or
499 social media accounts.&lt;/p&gt;
500
501 &lt;/blockquote&gt;
502
503 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
504 of Software Freedom Conservancy myself. Perhaps you should be a
505 supporter too?&lt;/p&gt;
506 </description>
507 </item>
508
509 <item>
510 <title>PGP key transition statement for key EE4E02F9</title>
511 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
512 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
513 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
514 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
515 set it up properly. I wanted to generate it offline and have it
516 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
517 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
518 time to sit down with an offline machine almost took forever. But
519 finally I&#39;ve been able to complete the process, and have now moved
520 from my old GPG key to a new GPG key. See
521 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
522 full transition statement, signed with both my old and new key&lt;/a&gt; for
523 the details. This is my new key:&lt;/p&gt;
524
525 &lt;pre&gt;
526 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]
527 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
528 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
529 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
530 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
531 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
532 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
533 &lt;/pre&gt;
534
535 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
536 my old key.&lt;/p&gt;
537
538 &lt;p&gt;If you signed my old key
539 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
540 I&#39;d very much appreciate a signature on my new key, details and
541 instructions in the transition statement. I m happy to reciprocate if
542 you have a similarly signed transition statement to present.&lt;/p&gt;
543 </description>
544 </item>
545
546 <item>
547 <title>The life and death of a laptop battery</title>
548 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
549 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
550 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
551 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
552 But this do not last. The last few laptops gave me a feeling that
553 within a year, the life time is just a fraction of what it used to be,
554 and it slowly become painful to use the laptop without power connected
555 all the time. Because of this, when I got a new Thinkpad X230 laptop
556 about two years ago, I decided to monitor its battery state to have
557 more hard facts when the battery started to fail.&lt;/p&gt;
558
559 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
560
561 &lt;p&gt;First I tried to find a sensible Debian package to record the
562 battery status, assuming that this must be a problem already handled
563 by someone else. I found
564 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
565 which collects statistics from the battery, but it was completely
566 broken. I sent a few suggestions to the maintainer, but decided to
567 write my own collector as a shell script while I waited for feedback
568 from him. Via
569 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
570 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
571 discovered
572 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
573 available in Debian.&lt;/p&gt;
574
575 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
576 battery stats ever since. Now my
577 /var/log/hjemmenett-battery-status.log file contain around 115,000
578 measurements, from the time the battery was working great until now,
579 when it is unable to charge above 7% of original capacity. My
580 collector shell script is quite simple and look like this:&lt;/p&gt;
581
582 &lt;pre&gt;
583 #!/bin/sh
584 # Inspired by
585 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
586 # See also
587 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
588 logfile=/var/log/hjemmenett-battery-status.log
589
590 files=&quot;manufacturer model_name technology serial_number \
591 energy_full energy_full_design energy_now cycle_count status&quot;
592
593 if [ ! -e &quot;$logfile&quot; ] ; then
594 (
595 printf &quot;timestamp,&quot;
596 for f in $files; do
597 printf &quot;%s,&quot; $f
598 done
599 echo
600 ) &gt; &quot;$logfile&quot;
601 fi
602
603 log_battery() {
604 # Print complete message in one echo call, to avoid race condition
605 # when several log processes run in parallel.
606 msg=$(printf &quot;%s,&quot; $(date +%s); \
607 for f in $files; do \
608 printf &quot;%s,&quot; $(cat $f); \
609 done)
610 echo &quot;$msg&quot;
611 }
612
613 cd /sys/class/power_supply
614
615 for bat in BAT*; do
616 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
617 done
618 &lt;/pre&gt;
619
620 &lt;p&gt;The script is called when the power management system detect a
621 change in the power status (power plug in or out), and when going into
622 and out of hibernation and suspend. In addition, it collect a value
623 every 10 minutes. This make it possible for me know when the battery
624 is discharging, charging and how the maximum charge change over time.
625 The code for the Debian package
626 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
627 available on github&lt;/a&gt;.&lt;/p&gt;
628
629 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
630
631 &lt;pre&gt;
632 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
633 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
634 [...]
635 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
636 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
637 &lt;/pre&gt;
638
639 &lt;p&gt;I wrote a small script to create a graph of the charge development
640 over time. This graph depicted above show the slow death of my laptop
641 battery.&lt;/p&gt;
642
643 &lt;p&gt;But why is this happening? Why are my laptop batteries always
644 dying in a year or two, while the batteries of space probes and
645 satellites keep working year after year. If we are to believe
646 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
647 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
648 chance, and the fix is to not charge the Lithium-ion batteries to 100%
649 all the time, but to stay below 90% of full charge most of the time.
650 I&#39;ve been told that the Tesla electric cars
651 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
652 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
653 100% when preparing for a longer trip (not that I would want a car
654 like Tesla where rights to privacy is abandoned, but that is another
655 story), which I guess is the option we should have for laptops on
656 Linux too.&lt;/p&gt;
657
658 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
659 stop charging at 80%, unless requested to charge to 100% once in
660 preparation for a longer trip? I found
661 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
662 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
663 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
664 load).&lt;/p&gt;
665
666 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
667 at the start. I also wonder why the &quot;full capacity&quot; increases some
668 times, and if it is possible to repeat the process to get the battery
669 back to design capacity. And I wonder if the discharge and charge
670 speed change over time, or if this stay the same. I did not yet try
671 to write a tool to calculate the derivative values of the battery
672 level, but suspect some interesting insights might be learned from
673 those.&lt;/p&gt;
674
675 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
676 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
677 packages instead of the tp-smapi-dkms package I had tried to use
678 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
679 and stop. I&#39;ve done so now, but expect my existing battery is toast
680 and need to be replaced. The proposal is unfortunately Thinkpad
681 specific.&lt;/p&gt;
682 </description>
683 </item>
684
685 <item>
686 <title>New laptop - some more clues and ideas based on feedback</title>
687 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
688 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
689 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
690 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
691 need for a new laptop, and provided very useful feedback. I wish to
692 thank every one of these. Several pointed me to the possibility of
693 fixing my X230, and I am already in the process of getting Lenovo to
694 do so thanks to the on site, next day support contract covering the
695 machine. But the battery is almost useless (I expect to replace it
696 with a non-official battery) and I do not expect the machine to live
697 for many more years, so it is time to plan its replacement. If I did
698 not have a support contract, it was suggested to find replacement parts
699 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
700 might present a language barrier as I do not understand French.&lt;/p&gt;
701
702 &lt;p&gt;One tip I got was to use the
703 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
704 compare laptop models. It seem to have more models available than
705 prisjakt.no. Another tip I got from someone I know have similar
706 keyboard preferences was that the HP EliteBook 840 keyboard is not
707 very good, and this matches my experience with earlier EliteBook
708 keyboards I tested. Because of this, I will not consider it any further.
709
710 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
711 newest Thinkpad X model. The keyboard reintroduces mouse buttons
712 (which is missing from the X240), and is working fairly well with
713 Debian Sid/Unstable according to
714 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
715 got on the keyboard quality are not consistent. Some say the keyboard
716 is good, others say it is ok, while others say it is not very good.
717 Those with experience from X41 and and X60 agree that the X250
718 keyboard is not as good as those trusty old laptops, and suggest I
719 keep and fix my X230 instead of upgrading, or get a used X230 to
720 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
721 activity and battery status, which is very convenient on my X230. I&#39;m
722 also told that the CPU fan is running very often, making it a bit
723 noisy. In any case, the X250 do not work out of the box with Debian
724 Stable/Jessie, one of my requirements.&lt;/p&gt;
725
726 &lt;p&gt;I have also gotten a few vendor proposals, one was
727 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
728 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
729 The latter look very attractive to me.&lt;/p&gt;
730
731 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
732 as I keep looking for a replacement.&lt;/p&gt;
733
734 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
735 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
736 different
737 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
738 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
739 </description>
740 </item>
741
742 <item>
743 <title>Time to find a new laptop, as the old one is broken after only two years</title>
744 <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>
745 <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>
746 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
747 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
748 replacement soon. The left 5 cm of the screen on my Thinkpad X230
749 started flickering yesterday, and I suspect the cause is a broken
750 cable, as changing the angle of the screen some times get rid of the
751 flickering.&lt;/p&gt;
752
753 &lt;p&gt;My requirements have not really changed since I bought it, and is
754 still as
755 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
756 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
757 good help from
758 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
759 where I could select at least a few of the requirements (mouse pin,
760 wifi, weight) and go through the rest manually. Three button mouse
761 and a good keyboard is not available as an option, and all the three
762 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
763 G2) lack three mouse buttons). It is also unclear to me how good the
764 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
765 the keyboard, even if the quality and robustness in the X series have
766 deteriorated since X41.&lt;/p&gt;
767
768 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
769 seem sensible to me? Are there better services around to search the
770 set of available laptops for features? Please send me an email if you
771 have suggestions.&lt;/p&gt;
772
773 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
774 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
775 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
776 </description>
777 </item>
778
779 <item>
780 <title>How to stay with sysvinit in Debian Jessie</title>
781 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
782 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
783 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
784 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
785 sysvinit as its boot system by default. But how can one keep using
786 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
787 courtesy of
788 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
789 Schubert&lt;/a&gt; and
790 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
791 McVittie&lt;/a&gt;.
792
793 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
794 keep sysvinit as your boot system, create a file
795 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
796 you upgrade:&lt;/p&gt;
797
798 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
799 Package: systemd-sysv
800 Pin: release o=Debian
801 Pin-Priority: -1
802 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
803
804 &lt;p&gt;This file content will tell apt and aptitude to not consider
805 installing systemd-sysv as part of any installation and upgrade
806 solution when resolving dependencies, and thus tell it to avoid
807 systemd as a default boot system. The end result should be that the
808 upgraded system keep using sysvinit.&lt;/p&gt;
809
810 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
811 get sysvinit installed by default (debootstrap used by
812 debian-installer have no option for this), but one can tell the
813 installer to switch to sysvinit before the first boot. Either by
814 using a kernel argument to the installer, or by adding a line to the
815 preseed file used. First, the kernel command line argument:
816
817 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
818 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
819 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
820
821 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
822
823 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
824 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
825 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
826
827 &lt;p&gt;One can of course also do this after the first boot by installing
828 the sysvinit-core package.&lt;/p&gt;
829
830 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
831 sysvinit boot sequence in Debian have several hardware specific bugs
832 on Linux caused by the fact that it is unpredictable when hardware
833 devices show up during boot. But on the other hand, the new default
834 boot system still have a few rough edges I hope will be fixed before
835 Jessie is released.&lt;/p&gt;
836
837 &lt;p&gt;Update 2014-11-26: Inspired by
838 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
839 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
840 line.&lt;/p&gt;
841 </description>
842 </item>
843
844 <item>
845 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
846 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
847 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
848 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
849 <description>&lt;p&gt;The right to communicate with your friends and family in private,
850 without anyone snooping, is a right every citicen have in a liberal
851 democracy. But this right is under serious attack these days.&lt;/p&gt;
852
853 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
854 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
855 the whisleblower Snowden) more expensive for Internet email,
856 is to deliver all email using SMTP via Tor. Such SMTP option would be
857 a nice addition to the FreedomBox project if we could send email
858 between FreedomBox machines without leaking metadata about the emails
859 to the people peeking on the wire. I
860 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
861 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
862 lot of useful feedback and suggestions. It also became obvious to me
863 that this was not a novel idea, as the same idea was tested and
864 documented by Johannes Berg as early as 2006, and both
865 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
866 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
867 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
868
869 &lt;p&gt;To implement such system one need to set up a Tor hidden service
870 providing the SMTP protocol on port 25, and use email addresses
871 looking like username@hidden-service-name.onion. With such addresses
872 the connections to port 25 on hidden-service-name.onion using Tor will
873 go to the correct SMTP server. To do this, one need to configure the
874 Tor daemon to provide the hidden service and the mail server to accept
875 emails for this .onion domain. To learn more about Exim configuration
876 in Debian and test the design provided by Johannes Berg in his FAQ, I
877 set out yesterday to create a Debian package for making it trivial to
878 set up such SMTP over Tor service based on Debian. Getting it to work
879 were fairly easy, and
880 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
881 source code for the Debian package&lt;/a&gt; is available from github. I
882 plan to move it into Debian if further testing prove this to be a
883 useful approach.&lt;/p&gt;
884
885 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
886 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
887 get rid of exim4). Install tor, clone the git repository mentioned
888 above, build the deb and install it on the machine. Next, run
889 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
890 the instructions to get the service up and running. Restart tor and
891 exim when it is done, and test mail delivery using swaks like
892 this:&lt;/p&gt;
893
894 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
895 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
896 --to fbx@dutlqrrmjhtfa3vp.onion
897 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
898
899 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
900 address with your own address to test your server. :)&lt;/p&gt;
901
902 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
903 easier and more automatic. Especially the tor setup need more work.
904 Also, the package include a tor-smtp tool written in C, but its task
905 should probably be rewritten in some script language to make the deb
906 architecture independent. It would probably also make the code easier
907 to review. The tor-smtp tool currently need to listen on a socket for
908 exim to talk to it and is started using xinetd. It would be better if
909 no daemon and no socket is needed. I suspect it is possible to get
910 exim to run a command line tool for delivery instead of talking to a
911 socket, and hope to figure out how in a future version of this
912 system.&lt;/p&gt;
913
914 &lt;p&gt;Until I wipe my test machine, I can be reached using the
915 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
916 SMTorP. :)&lt;/p&gt;
917 </description>
918 </item>
919
920 <item>
921 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
922 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
923 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
924 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
925 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
926 alioth.debian.org, you know the web interface is fairly slow to
927 operate. First you visit one web page, enter the moderation password
928 and get a new page shown with a list of all the messages to moderate
929 and various options for each email address. This take a while for
930 every list you moderate, and you need to do it regularly to do a good
931 job as a list moderator. But there is a quick alternative,
932 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
933 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
934 to moderate in a fraction of a second. Here is a test run on two
935 lists I recently took over:&lt;/p&gt;
936
937 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
938 % time listadmin xiph
939 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
940 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
941
942 real 0m1.709s
943 user 0m0.232s
944 sys 0m0.012s
945 %
946 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
947
948 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
949 there are no message in the moderation queue. Every morning I
950 currently moderate 68 mailman lists, and it normally take around two
951 minutes. When I took over the two pkg-xiph lists above a few days
952 ago, there were 400 emails waiting in the moderator queue. It took me
953 less than 15 minutes to process them all using the listadmin
954 program.&lt;/p&gt;
955
956 &lt;p&gt;If you install
957 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
958 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
959 with content like this, the moderation task is a breeze:&lt;/p&gt;
960
961 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
962 username username@example.org
963 spamlevel 23
964 default discard
965 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
966
967 password secret
968 adminurl https://{domain}/mailman/admindb/{list}
969 mailman-list@lists.example.com
970
971 password hidden
972 other-list@otherserver.example.org
973 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
974
975 &lt;p&gt;There are other options to set as well. Check the manual page to
976 learn the details.&lt;/p&gt;
977
978 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
979 the SSL certificate is self signed or not properly signed by a
980 generally accepted signing authority, you can set a environment
981 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
982
983 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
984 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
985 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
986
987 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
988 can provide an argument to the listadmin script like I do in the
989 initial screen dump (the xiph argument). Using an argument, only
990 lists matching the argument string will be processed. This make it
991 quick to accept messages if you notice the moderation request in your
992 email.&lt;/p&gt;
993
994 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
995 mailing lists, as I simply do not have time to spend on that if the
996 process was any slower. The listadmin program have saved me hours of
997 time I could spend elsewhere over the years. It truly is nice free
998 software.&lt;/p&gt;
999
1000 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1001 activities, please send Bitcoin donations to my address
1002 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1003
1004 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
1005 configuration example. Also, I&#39;ve been told that the
1006 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
1007 sure why.&lt;/p&gt;
1008 </description>
1009 </item>
1010
1011 <item>
1012 <title>Debian Jessie, PXE and automatic firmware installation</title>
1013 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
1014 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
1015 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
1016 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
1017 problem that the WiFi card require some firmware to work properly.
1018 And it has been a pain to fix this using preseeding in Debian.
1019 Normally something more is needed. But thanks to
1020 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
1021 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
1022 to do this using simple preseeding.&lt;/p&gt;
1023
1024 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
1025 firmware for the hardware found in the machine (actually, requested by
1026 the kernel modules for the hardware). (It can also install user space
1027 programs supporting the hardware detected, but that is not the focus
1028 of this story.)&lt;/p&gt;
1029
1030 &lt;p&gt;To get this working in the default installation, two preeseding
1031 values are needed. First, the isenkram-cli package must be installed
1032 into the target chroot (aka the hard drive) before tasksel is executed
1033 in the pkgsel step of the debian-installer system. This is done by
1034 preseeding the base-installer/includes debconf value to include the
1035 isenkram-cli package. The package name is next passed to debootstrap
1036 for installation. With the isenkram-cli package in place, tasksel
1037 will automatically use the isenkram tasks to detect hardware specific
1038 packages for the machine being installed and install them, because
1039 isenkram-cli contain tasksel tasks.&lt;/p&gt;
1040
1041 &lt;p&gt;Second, one need to enable the non-free APT repository, because
1042 most firmware unfortunately is non-free. This is done by preseeding
1043 the apt-mirror-setup step. This is unfortunate, but for a lot of
1044 hardware it is the only option in Debian.&lt;/p&gt;
1045
1046 &lt;p&gt;The end result is two lines needed in your preseeding file to get
1047 firmware installed automatically by the installer:&lt;/p&gt;
1048
1049 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1050 base-installer base-installer/includes string isenkram-cli
1051 apt-mirror-setup apt-setup/non-free boolean true
1052 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1053
1054 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
1055 both firmware and user space packages when using this method. It also
1056 do not work well, so use version 0.15 or later. Installing both
1057 firmware and user space packages might give you a bit more than you
1058 want, so I decided to split the tasksel task in two, one for firmware
1059 and one for user space programs. The firmware task is enabled by
1060 default, while the one for user space programs is not. This split is
1061 implemented in the package currently in unstable.&lt;/p&gt;
1062
1063 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
1064 this recipe work for you. :)&lt;/p&gt;
1065
1066 &lt;p&gt;So, I bet you are wondering, how can this work. First and
1067 foremost, it work because tasksel is modular, and driven by whatever
1068 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1069 isenkram-cli package place two files for tasksel to find. First there
1070 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
1071
1072 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1073 Task: isenkram-packages
1074 Section: hardware
1075 Description: Hardware specific packages (autodetected by isenkram)
1076 Based on the detected hardware various hardware specific packages are
1077 proposed.
1078 Test-new-install: show show
1079 Relevance: 8
1080 Packages: for-current-hardware
1081
1082 Task: isenkram-firmware
1083 Section: hardware
1084 Description: Hardware specific firmware packages (autodetected by isenkram)
1085 Based on the detected hardware various hardware specific firmware
1086 packages are proposed.
1087 Test-new-install: mark show
1088 Relevance: 8
1089 Packages: for-current-hardware-firmware
1090 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1091
1092 &lt;p&gt;The key parts are Test-new-install which indicate how the task
1093 should be handled and the Packages line referencing to a script in
1094 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1095 list of packages to install. The for-current-hardware-firmware script
1096 look like this to list relevant firmware for the machine:
1097
1098 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1099 #!/bin/sh
1100 #
1101 PATH=/usr/sbin:$PATH
1102 export PATH
1103 isenkram-autoinstall-firmware -l
1104 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1105
1106 &lt;p&gt;With those two pieces in place, the firmware is installed by
1107 tasksel during the normal d-i run. :)&lt;/p&gt;
1108
1109 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
1110 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
1111 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
1112 install.&lt;/p&gt;
1113
1114 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
1115 pilots in testing this feature, as isenkram is used there now to
1116 install firmware, replacing the earlier scripts.&lt;/p&gt;
1117 </description>
1118 </item>
1119
1120 <item>
1121 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
1122 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
1123 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
1124 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
1125 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
1126 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1127 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
1128 on a screen normally showing the bread types and prizes:&lt;/p&gt;
1129
1130 &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;
1131
1132 &lt;p&gt;If it had booted as it was supposed to, I would never had known
1133 about this hidden Linux installation. It is interesting what
1134 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
1135 </description>
1136 </item>
1137
1138 <item>
1139 <title>New lsdvd release version 0.17 is ready</title>
1140 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
1141 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
1142 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
1143 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
1144 got a new set of developers a few weeks ago, after the original
1145 developer decided to step down and pass the project to fresh blood.
1146 This project is now maintained by Petter Reinholdtsen and Steve
1147 Dibb.&lt;/p&gt;
1148
1149 &lt;p&gt;I just wrapped up
1150 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
1151 new lsdvd release&lt;/a&gt;, available in git or from
1152 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
1153 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
1154 0.17.&lt;/p&gt;
1155
1156 &lt;ul&gt;
1157
1158 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
1159 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
1160 non-existant, to work around additional copy protection&lt;/li&gt;
1161 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
1162 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
1163 &lt;li&gt;Fix include orders&lt;/li&gt;
1164 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
1165 &lt;li&gt;Fix the chapter count&lt;/li&gt;
1166 &lt;li&gt;Make sure the array size and the array limit used when initialising
1167 the palette size is the same.&lt;/li&gt;
1168 &lt;li&gt;Fix array printing.&lt;/li&gt;
1169 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
1170 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
1171 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
1172 with more GCC compiler warnings.&lt;/li&gt;
1173
1174 &lt;/ul&gt;
1175
1176 &lt;p&gt;This change bring together patches for lsdvd in use in various
1177 Linux and Unix distributions, as well as patches submitted to the
1178 project the last nine years. Please check it out. :)&lt;/p&gt;
1179 </description>
1180 </item>
1181
1182 <item>
1183 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
1184 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
1185 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
1186 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
1187 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1188 project&lt;/a&gt; provide a Linux solution for schools, including a
1189 powerful desktop with education software, a central server providing
1190 web pages, user database, user home directories, central login and PXE
1191 boot of both clients without disk and the installation to install Debian
1192 Edu on machines with disk (and a few other services perhaps to small
1193 to mention here). We in the Debian Edu team are currently working on
1194 the Jessie based version, trying to get everything in shape before the
1195 freeze, to avoid having to maintain our own package repository in the
1196 future. The
1197 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
1198 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
1199 work left. Some fatal problems block testing, breaking the installer,
1200 but it is possible to work around these to get anyway. Here is a
1201 recipe on how to get the installation limping along.&lt;/p&gt;
1202
1203 &lt;p&gt;First, download the test ISO via
1204 &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;,
1205 &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;
1206 or rsync (use
1207 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
1208 The ISO build was broken on Tuesday, so we do not get a new ISO every
1209 12 hours or so, but thankfully the ISO we already got we are able to
1210 install with some tweaking.&lt;/p&gt;
1211
1212 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
1213 (use Alt-Ctrl-F2), run&lt;/p&gt;
1214
1215 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1216 nano /usr/bin/edu-eatmydata-install
1217 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1218
1219 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
1220 optimization. Return to the installation, select the profile you want
1221 and continue. Without this change, exim4-config will fail to install
1222 due to a known bug in eatmydata.&lt;/p&gt;
1223
1224 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
1225 this do not work, figure out what your correct value would be. All my
1226 test machines need /dev/sda, so I have no advice if it do not fit
1227 your need.&lt;/p&gt;
1228
1229 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
1230 root after the initial boot from hard drive, and install the
1231 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1232 or mate. If you want several desktop options, install more than one
1233 metapackage. Once this is done, reboot and you should have a working
1234 graphical login screen. This workaround should no longer be needed
1235 once the education-tasks package version 1.801 enter testing in two
1236 days.&lt;/p&gt;
1237
1238 &lt;p&gt;I believe the ISO build will start working on two days when the new
1239 tasksel package enter testing and Steve McIntyre get a chance to
1240 update the debian-cd git repository. The eatmydata, grub and desktop
1241 issues are already fixed in unstable and testing, and should show up
1242 on the ISO as soon as the ISO build start working again. Well the
1243 eatmydata optimization is really just disabled. The proper fix
1244 require an upload by the eatmydata maintainer applying the patch
1245 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
1246 The rest have proper fixes in unstable.&lt;/p&gt;
1247
1248 &lt;p&gt;I hope this get you going with the installation testing, as we are
1249 quickly running out of time trying to get our Jessie based
1250 installation ready before the distribution freeze in a month.&lt;/p&gt;
1251 </description>
1252 </item>
1253
1254 <item>
1255 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
1256 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
1257 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
1258 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
1259 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
1260 to handle my fairly large DVD collection. It is a nice command line
1261 tool to get details about a DVD, like title, tracks, track length,
1262 etc, in XML, Perl or human readable format. But lsdvd have not seen
1263 any new development since 2006 and had a few irritating bugs affecting
1264 its use with some DVDs. Upstream seemed to be dead, and in January I
1265 sent a small probe asking for a version control repository for the
1266 project, without any reply. But I use it regularly and would like to
1267 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
1268 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
1269 the project admin, and after getting a reply from him explaining that
1270 he was no longer interested in the project, I asked if I could take
1271 over. And yesterday, I became project admin.&lt;/p&gt;
1272
1273 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
1274 maintainer interested in joining forces to maintain the upstream
1275 project, and I hope we can get a new release out fairly quickly,
1276 collecting the patches spread around on the internet into on place.
1277 I&#39;ve added the relevant Debian patches to the freshly created git
1278 repository, and expect the Gentoo patches to make it too. If you got
1279 a DVD collection and care about command line tools, check out
1280 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
1281 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
1282 list&lt;/a&gt;. :)&lt;/p&gt;
1283 </description>
1284 </item>
1285
1286 <item>
1287 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
1288 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
1289 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
1290 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
1291 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
1292 a lot quicker. When we install more than 2000 packages in
1293 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
1294 tasksel in the installer, unpacking the binary packages take forever.
1295 A part of the slow I/O issue was discussed in
1296 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
1297 much file system sync-ing done by dpkg, which is the package
1298 responsible for unpacking the binary packages. Other parts (like code
1299 executed by postinst scripts) might also sync to disk during
1300 installation. All this sync-ing to disk do not really make sense to
1301 me. If the machine crash half-way through, I start over, I do not try
1302 to salvage the half installed system. So the failure sync-ing is
1303 supposed to protect against, hardware or system crash, is not really
1304 relevant while the installer is running.&lt;/p&gt;
1305
1306 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
1307 system sync()-ing in a fairly non-intrusive way, without the need to
1308 change the code in several packages. The idea is not new, but I have
1309 not heard anyone propose the approach using dpkg-divert before. It
1310 depend on the small and clever package
1311 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
1312 uses LD_PRELOAD to replace the system functions for syncing data to
1313 disk with functions doing nothing, thus allowing programs to live
1314 dangerous while speeding up disk I/O significantly. Instead of
1315 modifying the implementation of dpkg, apt and tasksel (which are the
1316 packages responsible for selecting, fetching and installing packages),
1317 it occurred to me that we could just divert the programs away, replace
1318 them with a simple shell wrapper calling
1319 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
1320 Two days ago I decided to test the idea, and wrapped up a simple
1321 implementation for the Debian Edu udeb.&lt;/p&gt;
1322
1323 &lt;p&gt;The effect was stunning. In my first test it reduced the running
1324 time of the pkgsel step (installing tasks) from 64 to less than 44
1325 minutes (20 minutes shaved off the installation) on an old Dell
1326 Latitude D505 machine. I am not quite sure what the optimised time
1327 would have been, as I messed up the testing a bit, causing the debconf
1328 priority to get low enough for two questions to pop up during
1329 installation. As soon as I saw the questions I moved the installation
1330 along, but do not know how long the question were holding up the
1331 installation. I did some more measurements using Debian Edu Jessie,
1332 and got these results. The time measured is the time stamp in
1333 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
1334 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
1335 yourself. In Debian Edu, the tasksel dialog do not show up, and the
1336 timing thus do not depend on how quickly the user handle the tasksel
1337 dialog.&lt;/p&gt;
1338
1339 &lt;p&gt;&lt;table&gt;
1340
1341 &lt;tr&gt;
1342 &lt;th&gt;Machine/setup&lt;/th&gt;
1343 &lt;th&gt;Original tasksel&lt;/th&gt;
1344 &lt;th&gt;Optimised tasksel&lt;/th&gt;
1345 &lt;th&gt;Reduction&lt;/th&gt;
1346 &lt;/tr&gt;
1347
1348 &lt;tr&gt;
1349 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
1350 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
1351 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
1352 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
1353 &lt;/tr&gt;
1354
1355 &lt;tr&gt;
1356 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
1357 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
1358 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
1359 &lt;td&gt;23 min 40%&lt;/td&gt;
1360 &lt;/tr&gt;
1361
1362 &lt;tr&gt;
1363 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
1364 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
1365 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
1366 &lt;td&gt;11 min 50%&lt;/td&gt;
1367 &lt;/tr&gt;
1368
1369 &lt;tr&gt;
1370 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
1371 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
1372 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
1373 &lt;td&gt;2 min 33%&lt;/td&gt;
1374 &lt;/tr&gt;
1375
1376 &lt;tr&gt;
1377 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
1378 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
1379 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
1380 &lt;td&gt;4 min 21%&lt;/td&gt;
1381 &lt;/tr&gt;
1382
1383 &lt;/table&gt;&lt;/p&gt;
1384
1385 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
1386 time is spent downloading packages. The connection to the Internet
1387 was 100Mbit/s during testing, so downloading should not be a
1388 significant factor in the measurement. Download typically took a few
1389 seconds to a few minutes, depending on the amount of packages being
1390 installed.&lt;/p&gt;
1391
1392 &lt;p&gt;The speedup is implemented by using two hooks in
1393 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
1394 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
1395 finish-install.d hook to remove the divert at the end of the
1396 installation. I picked the pre-pkgsel.d hook instead of the
1397 post-base-installer.d hook because I test using an ISO without the
1398 eatmydata package included, and the post-base-installer.d hook in
1399 Debian Edu can only operate on packages included in the ISO. The
1400 negative effect of this is that I am unable to activate this
1401 optimization for the kernel installation step in d-i. If the code is
1402 moved to the post-base-installer.d hook, the speedup would be larger
1403 for the entire installation.&lt;/p&gt;
1404
1405 &lt;p&gt;I&#39;ve implemented this in the
1406 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
1407 git repository, and plan to provide the optimization as part of the
1408 Debian Edu installation. If you want to test this yourself, you can
1409 create two files in the installer (or in an udeb). One shell script
1410 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
1411
1412 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1413 #!/bin/sh
1414 set -e
1415 . /usr/share/debconf/confmodule
1416 info() {
1417 logger -t my-pkgsel &quot;info: $*&quot;
1418 }
1419 error() {
1420 logger -t my-pkgsel &quot;error: $*&quot;
1421 }
1422 override_install() {
1423 apt-install eatmydata || true
1424 if [ -x /target/usr/bin/eatmydata ] ; then
1425 for bin in dpkg apt-get aptitude tasksel ; do
1426 file=/usr/bin/$bin
1427 # Test that the file exist and have not been diverted already.
1428 if [ -f /target$file ] ; then
1429 info &quot;diverting $file using eatmydata&quot;
1430 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
1431 &gt; /target$file.edu
1432 chmod 755 /target$file.edu
1433 in-target dpkg-divert --package debian-edu-config \
1434 --rename --quiet --add $file
1435 ln -sf ./$bin.edu /target$file
1436 else
1437 error &quot;unable to divert $file, as it is missing.&quot;
1438 fi
1439 done
1440 else
1441 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
1442 fi
1443 }
1444
1445 override_install
1446 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1447
1448 &lt;p&gt;To clean up, another shell script should go into
1449 /usr/lib/finish-install.d/ with code like this:
1450
1451 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1452 #! /bin/sh -e
1453 . /usr/share/debconf/confmodule
1454 error() {
1455 logger -t my-finish-install &quot;error: $@&quot;
1456 }
1457 remove_install_override() {
1458 for bin in dpkg apt-get aptitude tasksel ; do
1459 file=/usr/bin/$bin
1460 if [ -x /target$file.edu ] ; then
1461 rm /target$file
1462 in-target dpkg-divert --package debian-edu-config \
1463 --rename --quiet --remove $file
1464 rm /target$file.edu
1465 else
1466 error &quot;Missing divert for $file.&quot;
1467 fi
1468 done
1469 sync # Flush file buffers before continuing
1470 }
1471
1472 remove_install_override
1473 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1474
1475 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
1476 edu-eatmydata-install and call it from the pre-pkgsel.d and
1477 finish-install.d scripts.&lt;/p&gt;
1478
1479 &lt;p&gt;By now you might ask if this change should get into the normal
1480 Debian installer too? I suspect it should, but am not sure the
1481 current debian-installer coordinators find it useful enough. It also
1482 depend on the side effects of the change. I&#39;m not aware of any, but I
1483 guess we will see if the change is safe after some more testing.
1484 Perhaps there is some package in Debian depending on sync() and
1485 fsync() having effect? Perhaps it should go into its own udeb, to
1486 allow those of us wanting to enable it to do so without affecting
1487 everyone.&lt;/p&gt;
1488
1489 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
1490 will break installation of all programs using gnutls because of
1491 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
1492 eatmydata package in Debian will solve it.&lt;/p&gt;
1493
1494 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
1495 the optimization work again. And I have discovered that the
1496 dpkg-divert trick is not really needed and implemented a slightly
1497 simpler approach as part of the debian-edu-install package. See
1498 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
1499
1500 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
1501 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
1502 triggering on i386 made it into testing, and broke this installation
1503 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
1504 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
1505 </description>
1506 </item>
1507
1508 <item>
1509 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
1510 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
1511 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
1512 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
1513 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
1514 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
1515 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
1516 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
1517 learn that there is a large set of publicly available key servers to
1518 use when looking for peoples public key. So far I have used
1519 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
1520 were misbehaving, but those days are ended. The servers I have used
1521 up until yesterday have been slow and some times unavailable. I hope
1522 those problems are gone now.&lt;/p&gt;
1523
1524 &lt;p&gt;Behind the round robin DNS entry of the
1525 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
1526 there is a pool of more than 100 keyservers which are checked every
1527 day to ensure they are well connected and up to date. It must be
1528 better than what I have used so far. :)&lt;/p&gt;
1529
1530 &lt;p&gt;Yesterdays speaker told me that the service is the default
1531 keyserver provided by the default configuration in GnuPG, but this do
1532 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
1533
1534 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
1535 line:&lt;/p&gt;
1536
1537 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1538 keyserver pool.sks-keyservers.net
1539 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1540
1541 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
1542 entries in DNS. Just for fun, I did just that at work, so now every
1543 user of GnuPG at the University of Oslo should find a OpenGPG
1544 keyserver automatically should their need it:&lt;/p&gt;
1545
1546 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1547 % host -t srv _pgpkey-http._tcp.uio.no
1548 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
1549 %
1550 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1551
1552 &lt;p&gt;Now if only
1553 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
1554 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
1555 very happy. It can look up a given key or search for a user ID, but I
1556 normally do not want that, but to find a trust path from my key to
1557 another key. Given a user ID or key ID, I would like to find (and
1558 download) the keys representing a signature path from my key to the
1559 key in question, to be able to get a trust path between the two keys.
1560 This is as far as I can tell not possible today. Perhaps something
1561 for a future version of the protocol?&lt;/p&gt;
1562 </description>
1563 </item>
1564
1565 <item>
1566 <title>From English wiki to translated PDF and epub via Docbook</title>
1567 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
1568 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
1569 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
1570 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1571 project&lt;/a&gt; provide an instruction manual for teachers, system
1572 administrators and other users that contain useful tips for setting up
1573 and maintaining a Debian Edu installation. This text is about how the
1574 text processing of this manual is handled in the project.&lt;/p&gt;
1575
1576 &lt;p&gt;One goal of the project is to provide information in the native
1577 language of its users, and for this we need to handle translations.
1578 But we also want to make sure each language contain the same
1579 information, so for this we need a good way to keep the translations
1580 in sync. And we want it to be easy for our users to improve the
1581 documentation, avoiding the need to learn special formats or tools to
1582 contribute, and the obvious way to do this is to make it possible to
1583 edit the documentation using a web browser. We also want it to be
1584 easy for translators to keep the translation up to date, and give them
1585 help in figuring out what need to be translated. Here is the list of
1586 tools and the process we have found trying to reach all these
1587 goals.&lt;/p&gt;
1588
1589 &lt;p&gt;We maintain the authoritative source of our manual in the
1590 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
1591 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
1592 front page with references to the different chapters, several pages
1593 for each chapter, and finally one &quot;collection page&quot; gluing all the
1594 chapters together into one large web page (aka
1595 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
1596 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
1597 processing and translations. Thanks to the fact that the
1598 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
1599 wiki.debian.org support exporting pages in
1600 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
1601 the list of pages to export using the raw version of the AllInOne
1602 page, loop over each of them to generate a Docbook XML version of the
1603 manual. This process also download images and transform image
1604 references to use the locally downloaded images. The generated
1605 Docbook XML files are slightly broken, so some post-processing is done
1606 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
1607 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
1608 a handfull of images. The XML file can now be used to generate PDF, HTML
1609 and epub versions of the English manual. This is the basic step of
1610 our process, making PDF (using dblatex), HTML (using xsltproc) and
1611 epub (using dbtoepub) version from Docbook XML, and the resulting files
1612 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
1613
1614 &lt;p&gt;But English documentation is not enough for us. We want translated
1615 documentation too, and we want to make it easy for translators to
1616 track the English original. For this we use the
1617 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
1618 which allow us to transform the English Docbook XML file into a
1619 translation file (a .pot file), usable with the normal gettext based
1620 translation tools used by those translating free software. The pot
1621 file is used to create and maintain translation files (several .po
1622 files), which the translations update with the native language
1623 translations of all titles, paragraphs and blocks of text in the
1624 original. The next step is combining the original English Docbook XML
1625 and the translation file (say debian-edu-wheezy-manual.nb.po), to
1626 create a translated Docbook XML file (in this case
1627 debian-edu-wheezy-manual.nb.xml). This translated (or partly
1628 translated, if the translation is not complete) Docbook XML file can
1629 then be used like the original to create a PDF, HTML and epub version
1630 of the documentation.&lt;/p&gt;
1631
1632 &lt;p&gt;The translators use different tools to edit the .po files. We
1633 recommend using
1634 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
1635 while some use emacs and vi, others can use web based editors like
1636 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
1637 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
1638 is where the .po file end up, in our git repository. Updated
1639 translations can either be committed directly to git, or submitted as
1640 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
1641 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
1642
1643 &lt;p&gt;One challenge is images, which both might need to be translated (if
1644 they show translated user applications), and are needed in different
1645 formats when creating PDF and HTML versions (epub is a HTML version in
1646 this regard). For this we transform the original PNG images to the
1647 needed density and format during build, and have a way to provide
1648 translated images by storing translated versions in
1649 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
1650 package maintainers know more.&lt;/p&gt;
1651
1652 &lt;p&gt;If you wonder what the result look like, we provide
1653 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
1654 of the documentation packages on the web&lt;/a&gt;. See for example the
1655 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
1656 PDF version&lt;/a&gt; or the
1657 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
1658 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
1659 but perhaps it will be done in the future.&lt;/p&gt;
1660
1661 &lt;p&gt;To learn more, check out
1662 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
1663 debian-edu-doc package&lt;/a&gt;,
1664 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
1665 manual on the wiki&lt;/a&gt; and
1666 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
1667 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
1668 </description>
1669 </item>
1670
1671 <item>
1672 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
1673 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
1674 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
1675 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
1676 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
1677 related packages relevant for the computer installed automatically.
1678 So I implemented one, using
1679 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
1680 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
1681 run tasksel as user root. You should be presented with a new option,
1682 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
1683 select it, tasksel will install the packages isenkram claim is fit for
1684 the current hardware, hot pluggable or not.&lt;p&gt;
1685
1686 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
1687 description, and the other is the script used to extract the list of
1688 packages to install. The first part is in
1689 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
1690 this:&lt;/p&gt;
1691
1692 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1693 Task: isenkram
1694 Section: hardware
1695 Description: Hardware specific packages (autodetected by isenkram)
1696 Based on the detected hardware various hardware specific packages are
1697 proposed.
1698 Test-new-install: mark show
1699 Relevance: 8
1700 Packages: for-current-hardware
1701 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1702
1703 &lt;p&gt;The second part is in
1704 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
1705 this:&lt;/p&gt;
1706
1707 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1708 #!/bin/sh
1709 #
1710 (
1711 isenkram-lookup
1712 isenkram-autoinstall-firmware -l
1713 ) | sort -u
1714 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1715
1716 &lt;p&gt;All in all, a very short and simple implementation making it
1717 trivial to install the hardware dependent package we all may want to
1718 have installed on our machines. I&#39;ve not been able to find a way to
1719 get tasksel to tell you exactly which packages it plan to install
1720 before doing the installation. So if you are curious or careful,
1721 check the output from the isenkram-* command line tools first.&lt;/p&gt;
1722
1723 &lt;p&gt;The information about which packages are handling which hardware is
1724 fetched either from the isenkram package itself in
1725 /usr/share/isenkram/, from git.debian.org or from the APT package
1726 database (using the Modaliases header). The APT package database
1727 parsing have caused a nasty resource leak in the isenkram daemon (bugs
1728 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
1729 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
1730 the python-apt code (bug
1731 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
1732 workaround I was able to get rid of the file descriptor leak and
1733 reduce the memory leak from ~30 MiB per hardware detection down to
1734 around 2 MiB per hardware detection. It should make the desktop
1735 daemon a lot more useful. The fix is in version 0.7 uploaded to
1736 unstable today.&lt;/p&gt;
1737
1738 &lt;p&gt;I believe the current way of mapping hardware to packages in
1739 Isenkram is is a good draft, but in the future I expect isenkram to
1740 use the AppStream data source for this. A proposal for getting proper
1741 AppStream support into Debian is floating around as
1742 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
1743 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
1744 project&lt;/a&gt; will take place this summer to improve the situation. I
1745 look forward to seeing the result, and welcome patches for isenkram to
1746 start using the information when it is ready.&lt;/p&gt;
1747
1748 &lt;p&gt;If you want your package to map to some specific hardware, either
1749 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
1750 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
1751 package&lt;/a&gt; or submit a bug report with the details to the isenkram
1752 package. See also
1753 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
1754 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
1755 the information will be migrated to AppStream eventually, but for the
1756 moment I got no better place to store it.&lt;/p&gt;
1757 </description>
1758 </item>
1759
1760 <item>
1761 <title>FreedomBox milestone - all packages now in Debian Sid</title>
1762 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
1763 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
1764 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
1765 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1766 project&lt;/a&gt; is working on providing the software and hardware to make
1767 it easy for non-technical people to host their data and communication
1768 at home, and being able to communicate with their friends and family
1769 encrypted and away from prying eyes. It is still going strong, and
1770 today a major mile stone was reached.&lt;/p&gt;
1771
1772 &lt;p&gt;Today, the last of the packages currently used by the project to
1773 created the system images were accepted into Debian Unstable. It was
1774 the freedombox-setup package, which is used to configure the images
1775 during build and on the first boot. Now all one need to get going is
1776 the build code from the freedom-maker git repository and packages from
1777 Debian. And once the freedombox-setup package enter testing, we can
1778 build everything directly from Debian. :)&lt;/p&gt;
1779
1780 &lt;p&gt;Some key packages used by Freedombox are
1781 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
1782 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
1783 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
1784 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
1785 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
1786 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
1787 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
1788 are plans to integrate more packages into the setup. User
1789 documentation is maintained on the Debian wiki. Please
1790 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
1791 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
1792
1793 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
1794 setup, run this on a Debian machine using a user with sudo rights to
1795 become root:&lt;/p&gt;
1796
1797 &lt;p&gt;&lt;pre&gt;
1798 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1799 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1800 u-boot-tools
1801 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1802 freedom-maker
1803 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1804 &lt;/pre&gt;&lt;/p&gt;
1805
1806 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1807 devices. See the README in the freedom-maker git repo for more
1808 details on the build. If you do not want all three images, trim the
1809 make line. Note that the virtualbox-image target is not really
1810 virtualbox specific. It create a x86 image usable in kvm, qemu,
1811 vmware and any other x86 virtual machine environment. You might need
1812 the version of vmdebootstrap in Jessie to get the build working, as it
1813 include fixes for a race condition with kpartx.&lt;/p&gt;
1814
1815 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1816 method, boot a Debian Wheezy ISO and use this boot argument to load
1817 the preseed values:&lt;/p&gt;
1818
1819 &lt;p&gt;&lt;pre&gt;
1820 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;
1821 &lt;/pre&gt;&lt;/p&gt;
1822
1823 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
1824 it still work.&lt;/p&gt;
1825
1826 &lt;p&gt;If you wonder how to help, one task you could look at is using
1827 systemd as the boot system. It will become the default for Linux in
1828 Jessie, so we need to make sure it is usable on the Freedombox. I did
1829 a simple test a few weeks ago, and noticed dnsmasq failed to start
1830 during boot when using systemd. I suspect there are other problems
1831 too. :) To detect problems, there is a test suite included, which can
1832 be run from the plinth web interface.&lt;/p&gt;
1833
1834 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1835 us get the new release published. :) Please join us on
1836 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1837 irc.debian.org)&lt;/a&gt; and
1838 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1839 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1840 </description>
1841 </item>
1842
1843 <item>
1844 <title>S3QL, a locally mounted cloud file system - nice free software</title>
1845 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
1846 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
1847 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
1848 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
1849 solution for use at home. My requirements are simple, it must be
1850 cheap and locally encrypted (in other words, I keep the encryption
1851 keys, the storage provider do not have access to my private files).
1852 One idea me and my friends had many years ago, before the cloud
1853 storage providers showed up, was to use Google mail as storage,
1854 writing a Linux block device storing blocks as emails in the mail
1855 service provided by Google, and thus get heaps of free space. On top
1856 of this one can add encryption, RAID and volume management to have
1857 lots of (fairly slow, I admit that) cheap and encrypted storage. But
1858 I never found time to implement such system. But the last few weeks I
1859 have looked at a system called
1860 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
1861 mounted network backed file system with the features I need.&lt;/p&gt;
1862
1863 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
1864 handling several different storage providers, any with Amazon S3,
1865 Google Drive or OpenStack API. There are heaps of such storage
1866 providers. S3QL can also use a local directory as storage, which
1867 combined with sshfs allow for file storage on any ssh server. S3QL
1868 include support for encryption, compression, de-duplication, snapshots
1869 and immutable file systems, allowing me to mount the remote storage as
1870 a local mount point, look at and use the files as if they were local,
1871 while the content is stored in the cloud as well. This allow me to
1872 have a backup that should survive fire. The file system can not be
1873 shared between several machines at the same time, as only one can
1874 mount it at the time, but any machine with the encryption key and
1875 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
1876
1877 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
1878 package is included already. So to get started, run &lt;tt&gt;apt-get
1879 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
1880 Greenqloud, after reading their nice recipe on
1881 &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
1882 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
1883 in Iceland more than those in USA when it come to keeping my personal
1884 data safe and private, and thus would rather spend money on a company
1885 in Iceland. Another nice recipe is available from the article
1886 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
1887 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
1888 Admin magazine. When the provider is picked, figure out how to get
1889 the API key needed to connect to the storage API. With Greencloud,
1890 the key did not show up until I had added payment details to my
1891 account.&lt;/p&gt;
1892
1893 &lt;p&gt;Armed with the API access details, it is time to create the file
1894 system. First, create a new bucket in the cloud. This bucket is the
1895 file system storage area. I picked a bucket name reflecting the
1896 machine that was going to store data there, but any name will do.
1897 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
1898 the API login and password, and a locally created password. Store it
1899 all in ~root/.s3ql/authinfo2 like this:
1900
1901 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1902 [s3c]
1903 storage-url: s3c://s.greenqloud.com:443/bucket-name
1904 backend-login: API-login
1905 backend-password: API-password
1906 fs-passphrase: local-password
1907 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1908
1909 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
1910 but any sensible way to create a fairly random password should do it.
1911 Armed with these details, it is now time to run mkfs, entering the API
1912 details and password to create it:&lt;/p&gt;
1913
1914 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1915 # mkdir -m 700 /var/lib/s3ql-cache
1916 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1917 --ssl s3c://s.greenqloud.com:443/bucket-name
1918 Enter backend login:
1919 Enter backend password:
1920 Before using S3QL, make sure to read the user&#39;s guide, especially
1921 the &#39;Important Rules to Avoid Loosing Data&#39; section.
1922 Enter encryption password:
1923 Confirm encryption password:
1924 Generating random encryption key...
1925 Creating metadata tables...
1926 Dumping metadata...
1927 ..objects..
1928 ..blocks..
1929 ..inodes..
1930 ..inode_blocks..
1931 ..symlink_targets..
1932 ..names..
1933 ..contents..
1934 ..ext_attributes..
1935 Compressing and uploading metadata...
1936 Wrote 0.00 MB of compressed metadata.
1937 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1938
1939 &lt;p&gt;The next step is mounting the file system to make the storage available.
1940
1941 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1942 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1943 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
1944 Using 4 upload threads.
1945 Downloading and decompressing metadata...
1946 Reading metadata...
1947 ..objects..
1948 ..blocks..
1949 ..inodes..
1950 ..inode_blocks..
1951 ..symlink_targets..
1952 ..names..
1953 ..contents..
1954 ..ext_attributes..
1955 Mounting filesystem...
1956 # df -h /s3ql
1957 Filesystem Size Used Avail Use% Mounted on
1958 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
1959 #
1960 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1961
1962 &lt;p&gt;The file system is now ready for use. I use rsync to store my
1963 backups in it, and as the metadata used by rsync is downloaded at
1964 mount time, no network traffic (and storage cost) is triggered by
1965 running rsync. To unmount, one should not use the normal umount
1966 command, as this will not flush the cache to the cloud storage, but
1967 instead running the umount.s3ql command like this:
1968
1969 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1970 # umount.s3ql /s3ql
1971 #
1972 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1973
1974 &lt;p&gt;There is a fsck command available to check the file system and
1975 correct any problems detected. This can be used if the local server
1976 crashes while the file system is mounted, to reset the &quot;already
1977 mounted&quot; flag. This is what it look like when processing a working
1978 file system:&lt;/p&gt;
1979
1980 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1981 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
1982 Using cached metadata.
1983 File system seems clean, checking anyway.
1984 Checking DB integrity...
1985 Creating temporary extra indices...
1986 Checking lost+found...
1987 Checking cached objects...
1988 Checking names (refcounts)...
1989 Checking contents (names)...
1990 Checking contents (inodes)...
1991 Checking contents (parent inodes)...
1992 Checking objects (reference counts)...
1993 Checking objects (backend)...
1994 ..processed 5000 objects so far..
1995 ..processed 10000 objects so far..
1996 ..processed 15000 objects so far..
1997 Checking objects (sizes)...
1998 Checking blocks (referenced objects)...
1999 Checking blocks (refcounts)...
2000 Checking inode-block mapping (blocks)...
2001 Checking inode-block mapping (inodes)...
2002 Checking inodes (refcounts)...
2003 Checking inodes (sizes)...
2004 Checking extended attributes (names)...
2005 Checking extended attributes (inodes)...
2006 Checking symlinks (inodes)...
2007 Checking directory reachability...
2008 Checking unix conventions...
2009 Checking referential integrity...
2010 Dropping temporary indices...
2011 Backing up old metadata...
2012 Dumping metadata...
2013 ..objects..
2014 ..blocks..
2015 ..inodes..
2016 ..inode_blocks..
2017 ..symlink_targets..
2018 ..names..
2019 ..contents..
2020 ..ext_attributes..
2021 Compressing and uploading metadata...
2022 Wrote 0.89 MB of compressed metadata.
2023 #
2024 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2025
2026 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
2027 quick, about the same speed as local file access. Uploading large
2028 amount of data is to me limited by the bandwidth out of and into my
2029 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
2030 which is very close to my upload speed, and downloading the same
2031 Debian installation ISO gave me 610 kiB/s, close to my download speed.
2032 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
2033 network, not the file system code. I do not know what a good cache
2034 size would be, but suspect that the cache should e larger than your
2035 working set.&lt;/p&gt;
2036
2037 &lt;p&gt;I mentioned that only one machine can mount the file system at the
2038 time. If another machine try, it is told that the file system is
2039 busy:&lt;/p&gt;
2040
2041 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2042 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2043 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2044 Using 8 upload threads.
2045 Backend reports that fs is still mounted elsewhere, aborting.
2046 #
2047 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2048
2049 &lt;p&gt;The file content is uploaded when the cache is full, while the
2050 metadata is uploaded once every 24 hour by default. To ensure the
2051 file system content is flushed to the cloud, one can either umount the
2052 file system, or ask S3QL to flush the cache and metadata using
2053 s3qlctrl:
2054
2055 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2056 # s3qlctrl upload-meta /s3ql
2057 # s3qlctrl flushcache /s3ql
2058 #
2059 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2060
2061 &lt;p&gt;If you are curious about how much space your data uses in the
2062 cloud, and how much compression and deduplication cut down on the
2063 storage usage, you can use s3qlstat on the mounted file system to get
2064 a report:&lt;/p&gt;
2065
2066 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2067 # s3qlstat /s3ql
2068 Directory entries: 9141
2069 Inodes: 9143
2070 Data blocks: 8851
2071 Total data size: 22049.38 MB
2072 After de-duplication: 21955.46 MB (99.57% of total)
2073 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
2074 Database size: 2.39 MB (uncompressed)
2075 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2076 #
2077 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2078
2079 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
2080 storage. I did not try to locate them all, but am aware of at least
2081 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
2082 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
2083 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
2084 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
2085 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
2086 accept payment in Bitcoin. Pick one that suit your need. Some of
2087 them provide several GiB of free storage, but the prize models are
2088 quite different and you will have to figure out what suits you
2089 best.&lt;/p&gt;
2090
2091 &lt;p&gt;While researching this blog post, I had a look at research papers
2092 and posters discussing the S3QL file system. There are several, which
2093 told me that the file system is getting a critical check by the
2094 science community and increased my confidence in using it. One nice
2095 poster is titled
2096 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
2097 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2098 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
2099 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2100 and Pamela Smith. Please have a look.&lt;/p&gt;
2101
2102 &lt;p&gt;Given my problems with different file systems earlier, I decided to
2103 check out the mounted S3QL file system to see if it would be usable as
2104 a home directory (in other word, that it provided POSIX semantics when
2105 it come to locking and umask handling etc). Running
2106 &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
2107 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
2108 no error was found. So the file system can be used for home
2109 directories, if one chooses to do so.&lt;/p&gt;
2110
2111 &lt;p&gt;If you do not want a locally file system, and want something that
2112 work without the Linux fuse file system, I would like to mention the
2113 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
2114 provide locally encrypted backup using a command line client. It have
2115 a nicer access control system, where one can split out read and write
2116 access, allowing some systems to write to the backup and others to
2117 only read from it.&lt;/p&gt;
2118
2119 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2120 activities, please send Bitcoin donations to my address
2121 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2122 </description>
2123 </item>
2124
2125 <item>
2126 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
2127 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
2128 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
2129 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
2130 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2131 project&lt;/a&gt; is working on providing the software and hardware for
2132 making it easy for non-technical people to host their data and
2133 communication at home, and being able to communicate with their
2134 friends and family encrypted and away from prying eyes. It has been
2135 going on for a while, and is slowly progressing towards a new test
2136 release (0.2).&lt;/p&gt;
2137
2138 &lt;p&gt;And what day could be better than the Pi day to announce that the
2139 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
2140 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2141 system), and can also be installed using a Debian installer preseed
2142 file. The Debian based Freedombox is now based on Debian Jessie,
2143 where most of the needed packages used are already present. Only one,
2144 the freedombox-setup package, is missing. To try to build your own
2145 boot image to test the current status, fetch the freedom-maker scripts
2146 and build using
2147 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
2148 with a user with sudo access to become root:
2149
2150 &lt;pre&gt;
2151 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2152 freedom-maker
2153 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2154 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2155 u-boot-tools
2156 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2157 &lt;/pre&gt;
2158
2159 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2160 devices. See the README for more details on the build. If you do not
2161 want all three images, trim the make line. But note that thanks to &lt;a
2162 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
2163 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
2164 kpartx call.&lt;/p&gt;
2165
2166 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2167 method, boot a Debian Wheezy ISO and use this boot argument to load
2168 the preseed values:&lt;/p&gt;
2169
2170 &lt;pre&gt;
2171 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;
2172 &lt;/pre&gt;
2173
2174 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
2175 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
2176 currently hang while setting up APT sources. Killing the
2177 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
2178 installation will get the installation going. This affect all
2179 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
2180
2181 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2182 us get the new release published. :) Please join us on
2183 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2184 irc.debian.org)&lt;/a&gt; and
2185 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2186 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2187 </description>
2188 </item>
2189
2190 <item>
2191 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
2192 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
2193 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
2194 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
2195 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
2196 innetgr tools, because I needed them in
2197 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
2198 ng-utils, and it has served me well. I placed the project under the
2199 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
2200 repository. But many years ago, the CVS repository was dropped (lost,
2201 not migrated to new hardware, not sure), and the project have lacked a
2202 proper home since then.&lt;/p&gt;
2203
2204 &lt;p&gt;Last summer, I had a look at the package and made a new release
2205 fixing a irritating crash bug, but was unable to store the changes in
2206 a proper source control system. I applied for a project on
2207 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
2208 to follow up on it. Until today. :)&lt;/p&gt;
2209
2210 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
2211 now have a new home, and a git repository with the highlight of the
2212 history of the project. I published all release tarballs and imported
2213 them into the git repository. As the project is really stable and not
2214 expected to gain new features any time soon, I decided to make a new
2215 release and call it 1.0. Visit the new project home on
2216 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
2217 if you want to check it out. The new version is also uploaded into
2218 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
2219 </description>
2220 </item>
2221
2222 <item>
2223 <title>Testing sysvinit from experimental in Debian Hurd</title>
2224 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
2225 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
2226 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
2227 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
2228 their changes into sysvinit, to allow them to use the normal sysvinit
2229 boot system instead of their old one. This follow up on the
2230 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
2231 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
2232 get Debian on Hurd working more like Debian on Linux. To get started,
2233 I downloaded a prebuilt hard disk image from
2234 &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;,
2235 and started it using virt-manager.&lt;/p&gt;
2236
2237 &lt;p&gt;The first think I had to do after logging in (root without any
2238 password) was to get the network operational. I followed
2239 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
2240 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
2241 commands as root to get the machine to accept a IP address from the
2242 kvm internal DHCP server:&lt;/p&gt;
2243
2244 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2245 settrans -fgap /dev/netdde /hurd/netdde
2246 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
2247 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
2248 dhclient /dev/eth0
2249 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2250
2251 &lt;p&gt;After this, the machine had internet connectivity, and I could
2252 upgrade it and install the sysvinit packages from experimental and
2253 enable it as the default boot system in Hurd.&lt;/p&gt;
2254
2255 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
2256 running on the machine it for ssh login to work a password need to be
2257 set. Also, note that a bug somewhere in openssh on Hurd block
2258 compression from working. Remember to turn that off on the client
2259 side.&lt;/p&gt;
2260
2261 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
2262 stuff:&lt;/p&gt;
2263
2264 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2265 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
2266 deb http://http.debian.net/debian/ experimental main
2267 EOF
2268 apt-get update
2269 apt-get dist-upgrade
2270 apt-get install -t experimental initscripts sysv-rc sysvinit \
2271 sysvinit-core sysvinit-utils
2272 update-alternatives --config runsystem
2273 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2274
2275 &lt;p&gt;To reboot after switching boot system, you have to use
2276 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
2277 yet a sysvinit process able to receive the signals from the normal
2278 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
2279 upgrading every package and rebooting, the network come up with DHCP
2280 after boot as it should, and the settrans/pkill hack mentioned at the
2281 start is no longer needed. But for some strange reason, there are no
2282 longer any login prompt in the virtual console, so I logged in using
2283 ssh instead.
2284
2285 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
2286 fail some times. No idea what the cause is, but hope the Hurd porters
2287 figure it out. At least Justus said on IRC (#debian-hurd on
2288 irc.debian.org) that they are aware of the problem. A way to reduce
2289 the impact is to upgrade to the Hurd packages built by Justus by
2290 adding this repository to the machine:&lt;/p&gt;
2291
2292 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2293 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
2294 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
2295 EOF
2296 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2297
2298 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
2299 http://ftp.debian-ports.org/debian, because some of the packages in
2300 unstable do not yet include the required patches that are lingering in
2301 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
2302
2303 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2304 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
2305 i emacs - GNU Emacs editor (metapackage)
2306 i gdb - GNU Debugger
2307 i hurd-recommended - Miscellaneous translators
2308 i isc-dhcp-client - ISC DHCP client
2309 i isc-dhcp-common - common files used by all the isc-dhcp* packages
2310 i libc-bin - Embedded GNU C Library: Binaries
2311 i libc-dev-bin - Embedded GNU C Library: Development binaries
2312 i libc0.3 - Embedded GNU C Library: Shared libraries
2313 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
2314 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
2315 i multiarch-support - Transitional package to ensure multiarch compatibilit
2316 i A x11-common - X Window System (X.Org) infrastructure
2317 i xorg - X.Org X Window System
2318 i A xserver-xorg - X.Org X server
2319 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
2320 #
2321 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2322
2323 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
2324 X.org did not work out of the box and I never took the time to follow
2325 the porters instructions to fix it. This time I was interested in the
2326 command line stuff.&lt;p&gt;
2327 </description>
2328 </item>
2329
2330 <item>
2331 <title>New chrpath release 0.16</title>
2332 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
2333 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
2334 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
2335 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
2336 find problems in C, C++ and Java code using static source code
2337 analysis. It can detect a lot of different problems, and is very
2338 useful to find memory and locking bugs in the error handling part of
2339 the source. The company behind it provide
2340 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
2341 a community service&lt;/a&gt;, and many hundred free software projects are
2342 already checked. A few days ago I decided to have a closer look at
2343 the Coverity system, and discovered that the
2344 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
2345 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
2346 projects I am involved with was already registered. But these are
2347 fairly big, and I would also like to have a small and easy project to
2348 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
2349 checking of the chrpath project&lt;/a&gt;. It was
2350 added to the checker and discovered seven potential defects. Six of
2351 these were real, mostly resource &quot;leak&quot; when the program detected an
2352 error. Nothing serious, as the resources would be released a fraction
2353 of a second later when the program exited because of the error, but it
2354 is nice to do it right in case the source of the program some time in
2355 the future end up in a library. Having fixed all defects and added
2356 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
2357 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
2358 publish a new release. These are the release notes:&lt;/p&gt;
2359
2360 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
2361
2362 &lt;ul&gt;
2363
2364 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
2365 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
2366 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
2367
2368 &lt;/ul&gt;
2369
2370 &lt;p&gt;You can
2371 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2372 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
2373 project if something is wrong with the new release. The test suite
2374 did not discover any old errors, so if you find a new one, please also
2375 include a test suite check.&lt;/p&gt;
2376 </description>
2377 </item>
2378
2379 <item>
2380 <title>New chrpath release 0.15</title>
2381 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
2382 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
2383 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
2384 <description>&lt;p&gt;After many years break from the package and a vain hope that
2385 development would be continued by someone else, I finally pulled my
2386 acts together this morning and wrapped up a new release of chrpath,
2387 the command line tool to modify the rpath and runpath of already
2388 compiled ELF programs. The update was triggered by the persistence of
2389 Isha Vishnoi at IBM, which needed a new config.guess file to get
2390 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
2391 is working on. I checked the
2392 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
2393 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
2394 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
2395 packages for interesting patches (failed to find the source from
2396 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
2397 These are the release notes:&lt;/p&gt;
2398
2399 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
2400
2401 &lt;ul&gt;
2402
2403 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
2404 with newer architectures. Thanks to isha vishnoi for the heads
2405 up.&lt;/li&gt;
2406
2407 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
2408
2409 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
2410 Matthias Klose.&lt;/li&gt;
2411
2412 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
2413 Petr Machata found in Fedora.&lt;/li&gt;
2414
2415 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
2416 .dynamic is a NULL terminated string. Based on patch found in
2417 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
2418
2419 &lt;/ul&gt;
2420
2421 &lt;p&gt;You can
2422 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
2423 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
2424 project if something is wrong with the new release. The test suite
2425 did not discover any old errors, so if you find a new one, please also
2426 include a testsuite check.&lt;/p&gt;
2427 </description>
2428 </item>
2429
2430 <item>
2431 <title>Debian init.d boot script example for rsyslog</title>
2432 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
2433 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
2434 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
2435 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
2436 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
2437 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
2438 init.d scripts at all. Here is an example init.d script, ie a rewrite
2439 of /etc/init.d/rsyslog:&lt;/p&gt;
2440
2441 &lt;p&gt;&lt;pre&gt;
2442 #!/lib/init/init-d-script
2443 ### BEGIN INIT INFO
2444 # Provides: rsyslog
2445 # Required-Start: $remote_fs $time
2446 # Required-Stop: umountnfs $time
2447 # X-Stop-After: sendsigs
2448 # Default-Start: 2 3 4 5
2449 # Default-Stop: 0 1 6
2450 # Short-Description: enhanced syslogd
2451 # Description: Rsyslog is an enhanced multi-threaded syslogd.
2452 # It is quite compatible to stock sysklogd and can be
2453 # used as a drop-in replacement.
2454 ### END INIT INFO
2455 DESC=&quot;enhanced syslogd&quot;
2456 DAEMON=/usr/sbin/rsyslogd
2457 &lt;/pre&gt;&lt;/p&gt;
2458
2459 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
2460 script was 137 lines, and the above is just 15 lines, most of it meta
2461 info/comments.&lt;/p&gt;
2462
2463 &lt;p&gt;How to do this, you ask? Well, one create a new script
2464 /lib/init/init-d-script looking something like this:
2465
2466 &lt;p&gt;&lt;pre&gt;
2467 #!/bin/sh
2468
2469 # Define LSB log_* functions.
2470 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
2471 # and status_of_proc is working.
2472 . /lib/lsb/init-functions
2473
2474 #
2475 # Function that starts the daemon/service
2476
2477 #
2478 do_start()
2479 {
2480 # Return
2481 # 0 if daemon has been started
2482 # 1 if daemon was already running
2483 # 2 if daemon could not be started
2484 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
2485 || return 1
2486 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
2487 $DAEMON_ARGS \
2488 || return 2
2489 # Add code here, if necessary, that waits for the process to be ready
2490 # to handle requests from services started subsequently which depend
2491 # on this one. As a last resort, sleep for some time.
2492 }
2493
2494 #
2495 # Function that stops the daemon/service
2496 #
2497 do_stop()
2498 {
2499 # Return
2500 # 0 if daemon has been stopped
2501 # 1 if daemon was already stopped
2502 # 2 if daemon could not be stopped
2503 # other if a failure occurred
2504 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
2505 RETVAL=&quot;$?&quot;
2506 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
2507 # Wait for children to finish too if this is a daemon that forks
2508 # and if the daemon is only ever run from this initscript.
2509 # If the above conditions are not satisfied then add some other code
2510 # that waits for the process to drop all resources that could be
2511 # needed by services started subsequently. A last resort is to
2512 # sleep for some time.
2513 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
2514 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
2515 # Many daemons don&#39;t delete their pidfiles when they exit.
2516 rm -f $PIDFILE
2517 return &quot;$RETVAL&quot;
2518 }
2519
2520 #
2521 # Function that sends a SIGHUP to the daemon/service
2522 #
2523 do_reload() {
2524 #
2525 # If the daemon can reload its configuration without
2526 # restarting (for example, when it is sent a SIGHUP),
2527 # then implement that here.
2528 #
2529 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
2530 return 0
2531 }
2532
2533 SCRIPTNAME=$1
2534 scriptbasename=&quot;$(basename $1)&quot;
2535 echo &quot;SN: $scriptbasename&quot;
2536 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
2537 script=&quot;$1&quot;
2538 shift
2539 . $script
2540 else
2541 exit 0
2542 fi
2543
2544 NAME=$(basename $DAEMON)
2545 PIDFILE=/var/run/$NAME.pid
2546
2547 # Exit if the package is not installed
2548 #[ -x &quot;$DAEMON&quot; ] || exit 0
2549
2550 # Read configuration variable file if it is present
2551 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
2552
2553 # Load the VERBOSE setting and other rcS variables
2554 . /lib/init/vars.sh
2555
2556 case &quot;$1&quot; in
2557 start)
2558 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
2559 do_start
2560 case &quot;$?&quot; in
2561 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2562 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2563 esac
2564 ;;
2565 stop)
2566 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
2567 do_stop
2568 case &quot;$?&quot; in
2569 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
2570 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
2571 esac
2572 ;;
2573 status)
2574 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
2575 ;;
2576 #reload|force-reload)
2577 #
2578 # If do_reload() is not implemented then leave this commented out
2579 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
2580 #
2581 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
2582 #do_reload
2583 #log_end_msg $?
2584 #;;
2585 restart|force-reload)
2586 #
2587 # If the &quot;reload&quot; option is implemented then remove the
2588 # &#39;force-reload&#39; alias
2589 #
2590 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
2591 do_stop
2592 case &quot;$?&quot; in
2593 0|1)
2594 do_start
2595 case &quot;$?&quot; in
2596 0) log_end_msg 0 ;;
2597 1) log_end_msg 1 ;; # Old process is still running
2598 *) log_end_msg 1 ;; # Failed to start
2599 esac
2600 ;;
2601 *)
2602 # Failed to stop
2603 log_end_msg 1
2604 ;;
2605 esac
2606 ;;
2607 *)
2608 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
2609 exit 3
2610 ;;
2611 esac
2612
2613 :
2614 &lt;/pre&gt;&lt;/p&gt;
2615
2616 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
2617 lot. I did not really polish the approach, so it might not always
2618 work out of the box, but you get the idea. I did not try very hard to
2619 optimize it nor make it more robust either.&lt;/p&gt;
2620
2621 &lt;p&gt;A better argument for switching init system in Debian than reducing
2622 the size of init scripts (which is a good thing to do anyway), is to
2623 get boot system that is able to handle the kernel events sensibly and
2624 robustly, and do not depend on the boot to run sequentially. The boot
2625 and the kernel have not behaved sequentially in years.&lt;/p&gt;
2626 </description>
2627 </item>
2628
2629 <item>
2630 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
2631 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
2632 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
2633 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
2634 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
2635 remote display access is the preferred solution with oVirt and RedHat
2636 Enterprise Virtualization, and I was sad to discover the other day
2637 that the browser plugin needed to use these systems seamlessly was
2638 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
2639 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2640 2013-04-01, so I decided to wrap up a package based on the great work
2641 from Cajus Pollmeier and put it in a collab-maint maintained git
2642 repository to get a package I could use. I would very much like
2643 others to help me maintain the package (or just take over, I do not
2644 mind), but as no-one had volunteered so far, I just uploaded it to
2645 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
2646
2647 &lt;p&gt;The source is now available from
2648 &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;
2649 </description>
2650 </item>
2651
2652 <item>
2653 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
2654 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
2655 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
2656 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
2657 <description>&lt;p&gt;The
2658 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
2659 program is a a very nice system to create virtual machine images. It
2660 create a image file, add a partition table, mount it and run
2661 debootstrap in the mounted directory to create a Debian system on a
2662 stick. Yesterday, I decided to try to teach it how to make images for
2663 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
2664 of a plan to simplify the build system for
2665 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
2666 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
2667 the virtualbox images, but its current build system made multistrap
2668 based system for Dreamplug images, and it is lacking support for
2669 Raspberry Pi.&lt;/p&gt;
2670
2671 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
2672 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
2673 code and adjusted it to be able to build armel images on my amd64
2674 Debian laptop. I ended up giving vmdebootstrap five new options,
2675 allowing me to replicate the image creation process I use to make
2676 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
2677 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
2678 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
2679 call debootstrap with --foreign and to copy the handler into the
2680 generated chroot before running the second stage. This allow
2681 vmdebootstrap to create armel images on an amd64 host. Next I added
2682 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
2683 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
2684 given file system type, allowing me to create an image with a vfat
2685 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
2686 variant&lt;/tt&gt; option to allow me to create smaller images without the
2687 Debian base system packages installed. Finally, I added an option
2688 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
2689 as a boot loader. It is not needed on the Raspberry Pi and probably
2690 most other non-x86 architectures. The changes were accepted by the
2691 upstream author of vmdebootstrap yesterday and today, and is now
2692 available from
2693 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
2694 upstream project page&lt;/a&gt;.&lt;/p&gt;
2695
2696 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
2697 create a small script (the customize script) to add the non-free
2698 binary blob needed to boot the Raspberry Pi and the APT source
2699 list:&lt;/p&gt;
2700
2701 &lt;p&gt;&lt;pre&gt;
2702 #!/bin/sh
2703 set -e # Exit on first error
2704 rootdir=&quot;$1&quot;
2705 cd &quot;$rootdir&quot;
2706 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
2707 deb http://http.debian.net/debian/ jessie main contrib non-free
2708 EOF
2709 # Install non-free binary blob needed to boot Raspberry Pi. This
2710 # install a kernel somewhere too.
2711 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
2712 -O $rootdir/usr/bin/rpi-update
2713 chmod a+x $rootdir/usr/bin/rpi-update
2714 mkdir -p $rootdir/lib/modules
2715 touch $rootdir/boot/start.elf
2716 chroot $rootdir rpi-update
2717 &lt;/pre&gt;&lt;/p&gt;
2718
2719 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
2720 to build the image:&lt;/p&gt;
2721
2722 &lt;pre&gt;
2723 sudo ./vmdebootstrap \
2724 --variant minbase \
2725 --arch armel \
2726 --distribution jessie \
2727 --mirror http://http.debian.net/debian \
2728 --image test.img \
2729 --size 600M \
2730 --bootsize 64M \
2731 --boottype vfat \
2732 --log-level debug \
2733 --verbose \
2734 --no-kernel \
2735 --no-extlinux \
2736 --root-password raspberry \
2737 --hostname raspberrypi \
2738 --foreign /usr/bin/qemu-arm-static \
2739 --customize `pwd`/customize \
2740 --package netbase \
2741 --package git-core \
2742 --package binutils \
2743 --package ca-certificates \
2744 --package wget \
2745 --package kmod
2746 &lt;/pre&gt;&lt;/p&gt;
2747
2748 &lt;p&gt;The list of packages being installed are the ones needed by
2749 rpi-update to make the image bootable on the Raspberry Pi, with the
2750 exception of netbase, which is needed by debootstrap to find
2751 /etc/hosts with the minbase variant. I really wish there was a way to
2752 set up an Raspberry Pi using only packages in the Debian archive, but
2753 that is not possible as far as I know, because it boots from the GPU
2754 using a non-free binary blob.&lt;/p&gt;
2755
2756 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
2757 probably a few others installed. I have not checked the complete
2758 build dependency list.&lt;/p&gt;
2759
2760 &lt;p&gt;The resulting image will not use the hardware floating point unit
2761 on the Raspberry PI, because the armel architecture in Debian is not
2762 optimized for that use. So the images created will be a bit slower
2763 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
2764 </description>
2765 </item>
2766
2767 <item>
2768 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
2769 <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>
2770 <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>
2771 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
2772 <description>&lt;p&gt;The last few days I came across a few good causes that should get
2773 wider attention. I recommend signing and donating to each one of
2774 these. :)&lt;/p&gt;
2775
2776 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
2777 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
2778 Women program which is a Google Summer of Code like initiative to get
2779 more women involved in free software. One debian sponsor has offered
2780 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
2781 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
2782 hope you will to. :)&lt;/p&gt;
2783
2784 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
2785 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
2786 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
2787 take place these days, and their need to fund the work. I&#39;ve already
2788 donated. Are you next?&lt;/p&gt;
2789
2790 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
2791 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
2792 statement under the heading
2793 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
2794 Access&lt;/a&gt; for those of us asking for more focus on open access in the
2795 Norwegian government. So far 499 signatures. I hope you will sign it
2796 too.&lt;/p&gt;
2797 </description>
2798 </item>
2799
2800 <item>
2801 <title>Videos about the Freedombox project - for inspiration and learning</title>
2802 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
2803 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
2804 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
2805 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
2806 project&lt;/a&gt; have been going on for a while, and have presented the
2807 vision, ideas and solution several places. Here is a little
2808 collection of videos of talks and presentation of the project.&lt;/p&gt;
2809
2810 &lt;ul&gt;
2811
2812 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
2813 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
2814
2815 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
2816 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2817
2818 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
2819 Freedom in the Cloud - Software Freedom, Privacy and and Security for
2820 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
2821 (Youtube)&lt;/li&gt;
2822
2823 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
2824 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
2825
2826 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
2827 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
2828
2829 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
2830 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
2831 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
2832
2833 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
2834 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
2835 (Youtube)&lt;/li&gt;
2836
2837 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
2838 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
2839
2840 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
2841 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
2842
2843 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
2844 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
2845 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
2846
2847 &lt;/ul&gt;
2848
2849 &lt;p&gt;A larger list is available from
2850 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
2851 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
2852
2853 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
2854 Jessie is coming along quite well, and soon both Owncloud and using
2855 Tor should be available for testers of the Freedombox solution. :) In
2856 a few weeks I hope everything needed to test it is included in Debian.
2857 The withsqlite package is already in Debian, and the plinth package is
2858 pending in NEW. The third and vital part of that puzzle is the
2859 metapackage/setup framework, which is still pending an upload. Join
2860 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
2861 (#freedombox on irc.debian.org)&lt;/a&gt; and
2862 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2863 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2864 </description>
2865 </item>
2866
2867 <item>
2868 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
2869 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
2870 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
2871 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
2872 <description>&lt;p&gt;I was introduced to the
2873 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
2874 in 2010, when Eben Moglen presented his vision about serving the need
2875 of non-technical people to keep their personal information private and
2876 within the legal protection of their own homes. The idea is to give
2877 people back the power over their network and machines, and return
2878 Internet back to its intended peer-to-peer architecture. Instead of
2879 depending on a central service, the Freedombox will give everyone
2880 control over their own basic infrastructure.&lt;/p&gt;
2881
2882 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
2883 taken priority. But this summers nasty news about the misuse of trust
2884 and privilege exercised by the &quot;western&quot; intelligence gathering
2885 communities increased my eagerness to contribute to a point where I
2886 actually started working on the project a while back.&lt;/p&gt;
2887
2888 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
2889 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
2890 create a simple and cheap Debian based appliance that anyone can hook
2891 up in their home and get access to secure and private services and
2892 communication. The initial deployment platform have been the
2893 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
2894 which is a piece of hardware I do not own. So to be able to test what
2895 the current Freedombox setup look like, I had to come up with a way to install
2896 it on some hardware I do have access to. I have rewritten the
2897 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
2898 image build framework to use .deb packages instead of only copying
2899 setup into the boot images, and thanks to this rewrite I am able to
2900 set up any machine supported by Debian Wheezy as a Freedombox, using
2901 the previously mentioned deb (and a few support debs for packages
2902 missing in Debian).&lt;/p&gt;
2903
2904 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
2905 scripts
2906 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
2907 and a administrative web interface
2908 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
2909 withsqlite), as well as a privacy enhancing proxy based on
2910 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
2911 (freedombox-privoxy). There is also a web/javascript based XMPP
2912 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
2913 trying (unsuccessfully so far) to talk to the XMPP server
2914 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
2915 web interface is pluggable, and the goal is to use it to enable OpenID
2916 services, mesh network connectivity, use of TOR, etc, etc. Not much of
2917 this is really working yet, see
2918 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
2919 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
2920 on github at the moment. The HTTP proxy is operational out of the
2921 box, and the admin web interface can be used to add/remove plinth
2922 users. I&#39;ve not been able to do anything else with it so far, but
2923 know there are several branches spread around github and other places
2924 with lots of half baked features.&lt;/p&gt;
2925
2926 &lt;p&gt;Anyway, if you want to have a look at the current state, the
2927 following recipes should work to give you a test machine to poke
2928 at.&lt;/p&gt;
2929
2930 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
2931
2932 &lt;ol&gt;
2933
2934 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
2935 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
2936 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
2937 to the Debian installer:&lt;p&gt;
2938 &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;
2939
2940 &lt;li&gt;Answer the few language/region/password questions and pick disk to
2941 install on.&lt;/li&gt;
2942
2943 &lt;li&gt;When the installation is finished and the machine have rebooted a
2944 few times, your Freedombox is ready for testing.&lt;/li&gt;
2945
2946 &lt;/ol&gt;
2947
2948 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
2949
2950 &lt;ol&gt;
2951
2952 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
2953 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
2954 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
2955 &lt;pre&gt;
2956 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
2957 &lt;/pre&gt;&lt;/li&gt;
2958 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
2959 &lt;pre&gt;
2960 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
2961 apt-key add -
2962 apt-get update
2963 apt-get install freedombox-setup
2964 /usr/lib/freedombox/setup
2965 &lt;/pre&gt;&lt;/li&gt;
2966 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
2967
2968 &lt;/ol&gt;
2969
2970 &lt;p&gt;You can test it on other architectures too, but because the
2971 freedombox-privoxy package is binary, it will only work as intended on
2972 the architectures where I have had time to build the binary and put it
2973 in my APT repository. But do not let this stop you. It is only a
2974 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
2975
2976 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
2977 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
2978 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
2979 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
2980
2981 &lt;p&gt;Please let me know if this works for you, or if you have any
2982 problems. We gather on the IRC channel
2983 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
2984 irc.debian.org and the
2985 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
2986 mailing list&lt;/a&gt;.&lt;/p&gt;
2987
2988 &lt;p&gt;Once you get your freedombox operational, you can visit
2989 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
2990 welcome screen (dead end - do not be surprised if you are unable to
2991 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
2992 to look at the rest of plinth. The default user is &#39;admin&#39; and the
2993 default password is &#39;secret&#39;.&lt;/p&gt;
2994 </description>
2995 </item>
2996
2997 <item>
2998 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
2999 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
3000 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
3001 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
3002 <description>&lt;p&gt;Earlier, I reported about
3003 &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
3004 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
3005 told by IBM that the original disk should be thrown away. And as
3006 there no longer was a problem if I bricked the firmware, I decided
3007 today to try to install Intel firmware to replace the Lenovo firmware
3008 currently on the disk.&lt;/p&gt;
3009
3010 &lt;p&gt;I searched the Intel site for firmware, and found
3011 &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;
3012 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3013 according to the site should contain the latest firmware for SSD
3014 disks. I inserted the broken disk in one of my spare laptops and
3015 booted the ISO from a USB stick. The disk was recognized, but the
3016 program claimed the newest firmware already were installed and refused
3017 to insert any Intel firmware. So no change, and the disk is still
3018 unable to handle write load. :( I guess the only way to get them
3019 working would be if Lenovo releases new firmware. No idea how likely
3020 that is. Anyway, just blogging about this test for completeness. I
3021 got a working Samsung disk, and see no point in spending more time on
3022 the broken disks.&lt;/p&gt;
3023 </description>
3024 </item>
3025
3026 <item>
3027 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
3028 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
3029 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
3030 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
3031 <description>&lt;p&gt;Today I switched to
3032 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
3033 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
3034 my new Thinkpad X230, which was delivered with an
3035 &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
3036 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
3037 sustained writes. My hardware supplier have been very forthcoming in
3038 trying to find a solution, and after first trying with another
3039 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
3040 disk instead to fix it once and for all. The Samsung disk survived
3041 the installation of Debian with encrypted disks (filling the disk with
3042 random data during installation killed the first two), and I thus
3043 decided to trust it with my data. I have installed it as a Debian Edu
3044 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3045 server at home using Kerberos and LDAP, and will use it as my work
3046 station from now on.&lt;/p&gt;
3047
3048 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
3049 Debian Wheezy default installation need to be tuned a bit to increase
3050 performance and increase life time of the disk. The Linux kernel and
3051 user space applications do not yet adjust automatically to such
3052 environment. To make it easier for my self, I created a draft Debian
3053 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
3054 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
3055 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
3056 is set up to adjust the setup of the machine by just installing the
3057 package. If there is any non-SSD disk in the machine, the package
3058 will refuse to install, as I did not try to write any logic to sort
3059 file systems in SSD and non-SSD file systems.&lt;/p&gt;
3060
3061 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
3062 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3063 where I set up the machine with one large encrypted partition (in
3064 addition to /boot), put LVM on top of this and set up partitions on
3065 top of this again. See the README file in the package source for the
3066 references I used to pick the settings. At the moment these
3067 parameters are tuned:&lt;/p&gt;
3068
3069 &lt;ul&gt;
3070
3071 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
3072 (adding discard to /etc/crypttab)&lt;/li&gt;
3073
3074 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
3075 this case a cryptsetup partition) by changing issue_discards from
3076 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
3077
3078 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
3079 systems.&lt;/li&gt;
3080
3081 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
3082 /etc/fstab.&lt;/li&gt;
3083
3084 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
3085
3086 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
3087 cron.daily).&lt;/li&gt;
3088
3089 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
3090 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
3091
3092 &lt;/ul&gt;
3093
3094 &lt;p&gt;During installation, I cancelled the part where the installer fill
3095 the disk with random data, as this would kill the SSD performance for
3096 little gain. My goal with the encrypted file system is to ensure
3097 those stealing my laptop end up with a brick and not a working
3098 computer. I have no hope in keeping the really resourceful people
3099 from getting the data on the disk (see
3100 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
3101 Thus I concluded that adding the discard option to crypttab is the
3102 right thing to do.&lt;/p&gt;
3103
3104 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
3105 it for SSD, but others recommended deadline and a benchmark I found
3106 indicated that deadline might be better for interactive use.&lt;/p&gt;
3107
3108 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
3109 and ext4, but read that it would give a performance hit ever time a
3110 file is removed, and thought it best to that that slowdown once a day
3111 instead of during my work.&lt;/p&gt;
3112
3113 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3114 this is already done by Debian Edu.&lt;/p&gt;
3115
3116 &lt;p&gt;I have not yet started on the user space tuning. I expect
3117 iceweasel need some tuning, and perhaps other applications too, but
3118 have not yet had time to investigate those parts.&lt;/p&gt;
3119
3120 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
3121 there.&lt;/p&gt;
3122
3123 &lt;p&gt;As for the answer to the question in the title of this blog post,
3124 as far as I know, the only solution I know about is to replace the
3125 disk. It might be possible to flash it with Intel firmware instead of
3126 the Lenovo firmware. But I have not tried and did not want to do so
3127 without approval from Lenovo as I wanted to keep the warranty on the
3128 disk until a solution was found and they wanted the broken disks
3129 back.&lt;/p&gt;
3130 </description>
3131 </item>
3132
3133 <item>
3134 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
3135 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
3136 <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>
3137 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
3138 <description>&lt;p&gt;A few days ago, I wrote about
3139 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
3140 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
3141 was dying during installation because it is unable to cope with
3142 sustained write. My supplier is in contact with
3143 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
3144 replacement disk to try to fix the problem. They decided to send an
3145 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
3146
3147 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
3148 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3149 same firmware version as the original. This time my hope raised
3150 slightly as the installation progressed, as the original disk used to
3151 die after 4-7% of the disk was written to, while this time it kept
3152 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
3153 died again and I was back on square one. I still do not have a new
3154 laptop with a disk I can trust. I can not live with a disk that might
3155 lock up when I download a new
3156 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
3157 other large files. I look forward to hearing from my supplier with
3158 the next proposal from Lenovo.&lt;/p&gt;
3159
3160 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
3161 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3162 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3163 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
3164 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3165 P/N 45N8295, P0C38732.&lt;/p&gt;
3166
3167 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
3168 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
3169 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3170 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
3171 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3172 P/N 45N8295, P0C38732.&lt;/p&gt;
3173
3174 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
3175 SA, date and WNPP values. Mentioning all the details here in case
3176 someone is able to use the information to find a way to identify the
3177 failing disk among working ones (if any such working disk actually
3178 exist).&lt;/p&gt;
3179 </description>
3180 </item>
3181
3182 <item>
3183 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
3184 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
3185 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
3186 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
3187 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
3188 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3189 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
3190 member assosiation NUUG&lt;/a&gt; and
3191 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
3192 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
3193 Bitraf&lt;/a&gt;.&lt;/p&gt;
3194
3195 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
3196 welcome, and there is no fee to participate. There is on the other
3197 hand limited space, and only room for 30 people. Please put your name
3198 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
3199 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
3200 </description>
3201 </item>
3202
3203 <item>
3204 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
3205 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
3206 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
3207 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
3208 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
3209 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
3210 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
3211 time to spend on it, and it took a while to find a model I believe
3212 will do the job, but two days ago the replacement finally arrived. I
3213 ended up picking a
3214 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
3215 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3216 a roaming workstation, and it seemed to work flawlessly. But my
3217 second installation with encrypted disk was not as successful. More
3218 on that below.&lt;/p&gt;
3219
3220 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3221 important requirements (robust and with a good keyboard) are never
3222 listed in the feature list. But I did get good help from the search
3223 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3224 allowed me to limit the list of interesting laptops based on my other
3225 requirements. A bit surprising that SSD disk are not disks according
3226 to that search interface, so I had to drop specifying the number of
3227 disks from my search parameters. I also asked around among friends to
3228 get their impression on keyboards and robustness.&lt;/p&gt;
3229
3230 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
3231 X41. I am not quite convinced about the keyboard, as it is
3232 significantly wider than my old keyboard, and I have to stretch my
3233 hand a lot more to reach the edges. But the key response is fairly
3234 good and the individual key shape is fairly easy to handle, so I hope
3235 I will get used to it. My old X40 was starting to fail, and I really
3236 needed a new laptop now. :)&lt;/p&gt;
3237
3238 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
3239 visit to the BIOS during boot it disable it.&lt;/p&gt;
3240
3241 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
3242 lock up during load. And this happen when installing Debian Wheezy
3243 with encrypted disk, while the disk is being filled with random data.
3244 I also tested to install Ubuntu Raring, and it happen there too if I
3245 reenable the code to fill the disk with random data (it is disabled by
3246 default in Ubuntu). And the bug with is already known. It was
3247 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
3248 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
3249 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
3250 kernel developers as
3251 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
3252 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
3253 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
3254 Lenovo forums, both for
3255 &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
3256 2012-11-10&lt;/a&gt; and for
3257 &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
3258 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
3259 reports state that the disk lock up during use if many writes are done
3260 on the disk, so it is much no use to work around the installation
3261 problem and end up with a computer that can lock up at any moment.
3262 There is even a
3263 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
3264 available&lt;/a&gt; that will lock up the hard drive after running a few
3265 minutes by writing to a file.&lt;/p&gt;
3266
3267 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
3268 contacting PCHELP Norway (request 01D1FDP) which handle support
3269 requests for Lenovo, his first suggestion was to upgrade the disk
3270 firmware. Unfortunately there is no newer firmware available from
3271 Lenovo, as my disk already have the most recent one (version LF1i). I
3272 hope to hear more from him today and hope the problem can be
3273 fixed. :)&lt;/p&gt;
3274 </description>
3275 </item>
3276
3277 <item>
3278 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
3279 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
3280 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
3281 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
3282 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
3283 trusty old Thinkpad X41. Unfortunately I did not have much time to
3284 spend on it, but today the replacement finally arrived. I ended up
3285 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
3286 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
3287 Wheezy as a roaming workstation, and it worked flawlessly. As I write
3288 this, it is installing what I hope will be a more final installation,
3289 with a encrypted hard drive to ensure any dope head stealing it end up
3290 with an expencive door stop.&lt;/p&gt;
3291
3292 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3293 important requirements (robust and with a good keyboard) are never
3294 listed in the feature list. But I did get good help from the search
3295 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3296 allowed me to limit the list of interesting laptops based on my other
3297 requirements. A bit surprising that SSD disk are not disks, so I had
3298 to drop number of disks from my search parameters.&lt;/p&gt;
3299
3300 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
3301 wider than my old keyboard, and I have to stretch my hand a lot more
3302 to reach the edges. But the key response is fairly good and the
3303 individual key shape is fairly easy to handle, so I hope I will get
3304 used to it. My old X40 was starting to fail, and I really needed a
3305 new laptop now. :)&lt;/p&gt;
3306
3307 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
3308 </description>
3309 </item>
3310
3311 <item>
3312 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
3313 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
3314 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
3315 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
3316 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
3317 perfectly capable of, and I have to do it manually to get things
3318 working. One such task is to find out what firmware packages are
3319 needed to get the hardware on my computer working. Most often this
3320 affect the wifi card, but some times it even affect the RAID
3321 controller or the ethernet card. Today I pushed version 0.4 of the
3322 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
3323 including a new script isenkram-autoinstall-firmware handling the
3324 process of asking all the loaded kernel modules what firmware files
3325 they want, find debian packages providing these files and install the
3326 debian packages. Here is a test run on my laptop:&lt;/p&gt;
3327
3328 &lt;p&gt;&lt;pre&gt;
3329 # isenkram-autoinstall-firmware
3330 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
3331 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
3332 info: locating packages with the requested firmware files
3333 info: Updating APT sources after adding non-free APT source
3334 info: trying to install firmware-ipw2x00
3335 firmware-ipw2x00
3336 firmware-ipw2x00
3337 Preconfiguring packages ...
3338 Selecting previously deselected package firmware-ipw2x00.
3339 (Reading database ... 259727 files and directories currently installed.)
3340 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
3341 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
3342 #
3343 &lt;/pre&gt;&lt;/p&gt;
3344
3345 &lt;p&gt;When all the requested firmware is present, a simple message is
3346 printed instead:&lt;/p&gt;
3347
3348 &lt;p&gt;&lt;pre&gt;
3349 # isenkram-autoinstall-firmware
3350 info: did not find any firmware files requested by loaded kernel modules. exiting
3351 #
3352 &lt;/pre&gt;&lt;/p&gt;
3353
3354 &lt;p&gt;It could use some polish, but it is already working well and saving
3355 me some time when setting up new machines. :)&lt;/p&gt;
3356
3357 &lt;p&gt;So, how does it work? It look at the set of currently loaded
3358 kernel modules, and look up each one of them using modinfo, to find
3359 the firmware files listed in the module meta-information. Next, it
3360 download the Contents file from a nearby APT mirror, and search for
3361 the firmware files in this file to locate the package with the
3362 requested firmware file. If the package is in the non-free section, a
3363 non-free APT source is added and the package is installed using
3364 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
3365 machine.&lt;/p&gt;
3366
3367 &lt;p&gt;I hope someone find time to implement a more polished version of
3368 this script as part of the hw-detect debian-installer module, to
3369 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
3370 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
3371 firmware during a PXE install when the packages already are available
3372 from the nearby Debian mirror.&lt;/p&gt;
3373 </description>
3374 </item>
3375
3376 <item>
3377 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
3378 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
3379 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
3380 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
3381 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
3382 the screen just turn black when Linux boot, either during installation
3383 or on first boot from the hard disk. I&#39;ve seen it once in a while the
3384 last few years, but only recently understood the cause. I&#39;ve seen it
3385 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
3386 The reason seem to be in the wiring of some laptops. The system to
3387 control the screen background light is inverted, so when Linux try to
3388 turn the brightness fully on, it end up turning it off instead. I do
3389 not know which Linux drivers are affected, but this post is about the
3390 i915 driver used by the
3391 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3392 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
3393
3394 &lt;p&gt;The problem can be worked around two ways. Either by adding
3395 i915.invert_brightness=1 as a kernel option, or by adding a file in
3396 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
3397 option when it load the i915 kernel module. On Debian and Ubuntu, it
3398 can be done by running these commands as root:&lt;/p&gt;
3399
3400 &lt;pre&gt;
3401 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
3402 update-initramfs -u -k all
3403 &lt;/pre&gt;
3404
3405 &lt;p&gt;Since March 2012 there is
3406 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
3407 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
3408 hardware have this problem, and get the driver to invert the
3409 brightness setting automatically. To use it, one need to add a row in
3410 &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
3411 intel_quirks array&lt;/a&gt; in the driver source
3412 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
3413 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
3414 number (vendor number 8086 is assumed) and subdevice vendor and device
3415 number.&lt;/p&gt;
3416
3417 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
3418 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
3419
3420 &lt;p&gt;&lt;pre&gt;
3421 00:02.0 VGA compatible controller [0300]: Intel Corporation \
3422 3rd Gen Core processor Graphics Controller [8086:0156] \
3423 (rev 09) (prog-if 00 [VGA controller])
3424 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
3425 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
3426 ParErr- Stepping- SE RR- FastB2B- DisINTx+
3427 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
3428 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
3429 Latency: 0
3430 Interrupt: pin A routed to IRQ 42
3431 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
3432 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
3433 Region 4: I/O ports at 4000 [size=64]
3434 Expansion ROM at &lt;unassigned&gt; [disabled]
3435 Capabilities: &lt;access denied&gt;
3436 Kernel driver in use: i915
3437 &lt;/pre&gt;&lt;/p&gt;
3438
3439 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
3440
3441 &lt;p&gt;&lt;pre&gt;
3442 struct intel_quirk intel_quirks[] = {
3443 ...
3444 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
3445 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
3446 ...
3447 }
3448 &lt;/pre&gt;&lt;/p&gt;
3449
3450 &lt;p&gt;According to the kernel module instructions (as seen using
3451 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
3452 invert_brightness flag should be sent to the
3453 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
3454 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
3455 developers. But my email about the laptop sent 2013-06-03 have not
3456 yet shown up in
3457 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
3458 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
3459 emails from non-subscribers. Because of this, I sent my patch also to
3460 the Debian bug tracking system instead as
3461 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
3462 sure the patch is not lost.&lt;/p&gt;
3463
3464 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
3465 with this problem working properly with Linux. If you use Gnome, your
3466 worries should be over at this point. But if you use KDE, there is
3467 something in KDE ignoring the invert_brightness setting and turning on
3468 the screen during login. I&#39;ve reported it to Debian as
3469 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
3470 have no idea yet how to figure out exactly what subsystem is doing
3471 this. Perhaps you can help? Perhaps you know what the Gnome
3472 developers did to handle this, and this can give a clue to the KDE
3473 developers? Or you know where in KDE the screen brightness is changed
3474 during login? If so, please update the BTS report (or get in touch if
3475 you do not know how to update BTS).&lt;/p&gt;
3476
3477 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
3478 acpi_backlight=vendor, to disable ACPI backlight support completely,
3479 as the ACPI information on the machine is trash and it is better to
3480 leave it to the intel video driver to control the screen
3481 backlight.&lt;/p&gt;
3482 </description>
3483 </item>
3484
3485 <item>
3486 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
3487 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
3488 <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>
3489 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
3490 <description>&lt;p&gt;Two days ago, I asked
3491 &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
3492 I could install Linux on a Packard Bell EasyNote LV computer
3493 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
3494 with the obstacles put in the way of Linux users on a laptop with UEFI
3495 and Windows 8.&lt;/p&gt;
3496
3497 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
3498 secure booting or fast boot. I suspect fast boot was the problem,
3499 causing the firmware to boot directly from HD without considering any
3500 key presses and alternative devices, but do not know UEFI settings
3501 enough to tell.&lt;/p&gt;
3502
3503 &lt;p&gt;There is no way to install Linux on the machine in question without
3504 opening the box and disconnecting the hard drive! This is as far as I
3505 can tell, the only way to get access to the firmware setup menu
3506 without accepting the Windows 8 license agreement. I am told (and
3507 found description on how to) that it is possible to configure the
3508 firmware setup once booted into Windows 8. But as I believe the terms
3509 of that agreement are completely unacceptable, accepting the license
3510 was never an alternative. I do not enter agreements I do not intend
3511 to follow.&lt;/p&gt;
3512
3513 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
3514 waste many hours on this, but luckily there was a way to get it to
3515 work. But I would not recommend it to anyone planning to run Linux on
3516 it, and I have become sceptical to Windows 8 certified laptops. Is
3517 this the way Linux will be forced out of the market place, by making
3518 it close to impossible for &quot;normal&quot; users to install Linux without
3519 accepting the Microsoft Windows license terms? Or at least not
3520 without risking to loose the warranty?&lt;/p&gt;
3521
3522 &lt;p&gt;I&#39;ve updated the
3523 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
3524 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
3525 do not have to struggle as much as I did to get Linux into the
3526 machine.&lt;/p&gt;
3527
3528 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
3529 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
3530 </description>
3531 </item>
3532
3533 <item>
3534 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
3535 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
3536 <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>
3537 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
3538 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
3539 new laptops for my parents and a few others. I bought Packard Bell
3540 Easynote LV to run Kubuntu on and use as their home computer. But I
3541 am completely unable to figure out how to install Linux on it. The
3542 computer is preinstalled with Windows 8, and I suspect it uses UEFI
3543 instead of a BIOS to boot.&lt;/p&gt;
3544
3545 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
3546 to get it to boot the Linux installer from my USB stick. I have yet
3547 to try the DVD install, and still hope it will work. when I turn on
3548 the computer, there is no information on what buttons to press to get
3549 the normal boot menu. I expect to get some boot menu to select PXE or
3550 USB stick booting. When booting, it first ask for the language to
3551 use, then for some regional settings, and finally if I will accept the
3552 Windows 8 terms of use. As these terms are completely unacceptable to
3553 me, I have no other choice but to turn off the computer and try again
3554 to get it to boot the Linux installer.&lt;/p&gt;
3555
3556 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
3557 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
3558 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
3559 installed on this machine, please get in touch or update that wiki
3560 page. If I can&#39;t find a way to install Linux, I will have to return
3561 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
3562
3563 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
3564 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
3565 on new Laptops?&lt;/p&gt;
3566 </description>
3567 </item>
3568
3569 <item>
3570 <title>How to transform a Debian based system to a Debian Edu installation</title>
3571 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
3572 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
3573 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
3574 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
3575 an operating system based on Debian intended for use in schools. It
3576 contain a turn-key solution for the computer network provided to
3577 pupils in the primary schools. It provide both the central server,
3578 network boot servers and desktop environments with heaps of
3579 educational software. The project was founded almost 12 years ago,
3580 2001-07-02. If you want to support the project, which is in need for
3581 cash to fund developer gatherings and other project related activity,
3582 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
3583 donate some money&lt;/a&gt;.
3584
3585 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
3586 lists and elsewhere, is the question on how to transform a Debian or
3587 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
3588 hard, and last week I wrote a script to replicate the steps done by
3589 the Debian Edu installer.&lt;/p&gt;
3590
3591 &lt;p&gt;The script,
3592 &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;
3593 in the debian-edu-config package, will go through these six steps and
3594 transform an existing Debian Wheezy or Ubuntu (untested) installation
3595 into a Debian Edu Workstation:&lt;/p&gt;
3596
3597 &lt;ol&gt;
3598
3599 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
3600 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
3601 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
3602 our configuration.&lt;/li&gt;
3603 &lt;li&gt;Preseed debconf database with profile setup in
3604 /etc/debian-edu/config, and run tasksel to install packages
3605 according to the profile specified in the config above,
3606 overriding some of the Debian automation machinery.&lt;/li&gt;
3607 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
3608 that could not be done using preseeding.&lt;/li&gt;
3609 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
3610
3611 &lt;/ol&gt;
3612
3613 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
3614 replicated like this. Disk partitioning and LVM setup, for example.
3615 So this script just assume there is enough disk space to install all
3616 the needed packages.&lt;/p&gt;
3617
3618 &lt;p&gt;The script was created to help a Debian Edu student working on
3619 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
3620 Debian Edu client, and using it he can take the existing
3621 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
3622 transform it into a fully functioning Debian Edu Workstation (or
3623 Roaming Workstation, or whatever :).&lt;/p&gt;
3624
3625 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
3626 If a LXDE based Roaming workstation is wanted instead, modify the
3627 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
3628
3629 &lt;p&gt;&lt;pre&gt;
3630 PROFILE=&quot;Roaming-Workstation&quot;
3631 DESKTOP=&quot;lxde&quot;
3632 &lt;/pre&gt;&lt;/p&gt;
3633
3634 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
3635 the cloud, by starting with a virtual Debian installation at some
3636 virtual hosting service and setting up all the services on first
3637 boot.&lt;/p&gt;
3638 </description>
3639 </item>
3640
3641 <item>
3642 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
3643 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
3644 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
3645 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
3646 <description>&lt;P&gt;In January,
3647 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
3648 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
3649 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
3650 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
3651 marvellous construction system from Denmark. We also created
3652 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
3653 a place to take notes and write down our plans and hopes. And several
3654 people showed up to help. I was very happy to see the effect of my
3655 call. Since the small start, we have a debtags tag
3656 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
3657 tag for LEGO related packages, and now count 10 packages related to
3658 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
3659
3660 &lt;p&gt;&lt;table&gt;
3661 &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;
3662 &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;
3663 &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;
3664 &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;
3665 &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;
3666 &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;
3667 &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;
3668 &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;
3669 &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;
3670 &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;
3671 &lt;/table&gt;&lt;/p&gt;
3672
3673 &lt;p&gt;Some of these are available in Wheezy, and all but one are
3674 currently available in Jessie/testing. leocad is so far only
3675 available in experimental.&lt;/p&gt;
3676
3677 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
3678 adding the rest of the great free software tools available on Linux
3679 for LEGO designers.&lt;/p&gt;
3680 </description>
3681 </item>
3682
3683 <item>
3684 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
3685 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
3686 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
3687 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
3688 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
3689 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
3690 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
3691 Debian release, and I expect to move my machines at home over to it fairly
3692 soon.&lt;/p&gt;
3693
3694 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
3695 in particular make me very happy to see included. The
3696 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
3697 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
3698 included for the first time. Alongside similar programs like
3699 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
3700 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
3701 it allow for visual programming where syntax errors can not happen,
3702 and a friendly programming environment for learning to control the
3703 computer. Scratch will also be included in the next release of Debian
3704 Edu.&lt;/a&gt;
3705
3706 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
3707 Edu/Skolelinux release too. The
3708 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
3709 alpha release&lt;/a&gt; went out last week, and the next should soon
3710 follow.&lt;p&gt;
3711 </description>
3712 </item>
3713
3714 <item>
3715 <title>Isenkram 0.2 finally in the Debian archive</title>
3716 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
3717 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
3718 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
3719 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
3720 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
3721 for many months. I uploaded it to the Debian experimental suite
3722 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
3723
3724 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
3725 install to work with a pluggable hardware device. The suggestion pop
3726 up when the device is plugged in. For example if a Lego Mindstorm NXT
3727 is inserted, it will suggest to install the program needed to program
3728 the NXT controller. Give it a go, and report bugs and suggestions to
3729 BTS. :)&lt;/p&gt;
3730 </description>
3731 </item>
3732
3733 <item>
3734 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
3735 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
3736 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
3737 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
3738 <description>&lt;p&gt;My
3739 &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
3740 bitcoin related blog post&lt;/a&gt; mentioned that the new
3741 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
3742 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
3743 2013-01-19, and have been available in unstable since then. It was
3744 automatically copied to Ubuntu, and is available in their Raring
3745 version too.&lt;/p&gt;
3746
3747 &lt;p&gt;But there is a strange problem with the build that block this new
3748 version from being available on the i386 and kfreebsd-i386
3749 architectures. For some strange reason, the autobuilders in Debian
3750 for these architectures fail to run the test suite on these
3751 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
3752 We are so far unable to reproduce it when building it manually, and
3753 no-one have been able to propose a fix. If you got an idea what is
3754 failing, please let us know via the BTS.&lt;/p&gt;
3755
3756 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
3757 I often run low on disk space, is the fact that the client will exit
3758 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
3759 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
3760 it. :)&lt;/p&gt;
3761
3762 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3763 activities, please send Bitcoin donations to my address
3764 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3765 </description>
3766 </item>
3767
3768 <item>
3769 <title>Welcome to the world, Isenkram!</title>
3770 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
3771 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
3772 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
3773 <description>&lt;p&gt;Yesterday, I
3774 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
3775 for testers&lt;/a&gt; for my prototype for making Debian better at handling
3776 pluggable hardware devices, which I
3777 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
3778 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
3779 up, and caused me to really want to to open up the development to more
3780 people. But before I did this, I want to come up with a sensible name
3781 for this project. Today I finally decided on a new name, and I have
3782 renamed the project from hw-support-handler to this new name. In the
3783 process, I moved the source to git and made it available as a
3784 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
3785 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
3786 To fetch and build the latest version of the source, use&lt;/p&gt;
3787
3788 &lt;pre&gt;
3789 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
3790 cd isenkram &amp;&amp; git-buildpackage -us -uc
3791 &lt;/pre&gt;
3792
3793 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
3794 want to hack on the source or improve the package, please go ahead.
3795 But please talk to me first on IRC or via email before you do major
3796 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
3797
3798 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
3799 stuff, typically meaning tools, nails, screws, etc. Typical hardware
3800 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
3801 the German word eisenkram, for those that are familiar with that
3802 word.&lt;/p&gt;
3803
3804 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
3805 instructions, to avoid confusing people with an error from the signing
3806 process.&lt;/p&gt;
3807
3808 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
3809 clone argument to avoid the need for authentication.&lt;/p&gt;
3810 </description>
3811 </item>
3812
3813 <item>
3814 <title>First prototype ready making hardware easier to use in Debian</title>
3815 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
3816 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
3817 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
3818 <description>&lt;p&gt;Early this month I set out to try to
3819 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
3820 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
3821 prototype is working, and it is ready for a larger audience. To test
3822 it, fetch the
3823 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
3824 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
3825 package. You might have to log out and in again activate the
3826 autostart script.&lt;/p&gt;
3827
3828 &lt;p&gt;The design is simple:&lt;/p&gt;
3829
3830 &lt;ul&gt;
3831
3832 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
3833 hw-support-handlerd to start when the user log in.&lt;/li&gt;
3834
3835 &lt;li&gt;This program listen for kernel events about new hardware (directly
3836 from the kernel like udev does), not using HAL dbus events as I
3837 initially did.&lt;/li&gt;
3838
3839 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
3840 the APT database, a database
3841 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
3842 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
3843
3844 &lt;li&gt;If a package is mapped to the hardware in question, the package
3845 isn&#39;t installed yet and this is the first time the hardware was
3846 plugged in, show a desktop notification suggesting to install the
3847 package or packages.&lt;/li&gt;
3848
3849 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
3850 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
3851
3852 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
3853 package while showing progress information in a window.&lt;/li&gt;
3854
3855 &lt;/ul&gt;
3856
3857 &lt;p&gt;I still need to come up with a better name for the system. Here
3858 are some screen shots showing the prototype in action. First the
3859 notification, then the password request, and finally the request to
3860 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
3861
3862 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
3863 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
3864 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
3865 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
3866 &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;
3867
3868 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
3869 is already useful. The database of hardware to package mappings also
3870 need more work. It is currently compatible with the Ubuntu way of
3871 storing such information in the package control file, but could be
3872 changed to use other formats instead or in addition to the current
3873 method. I&#39;ve dropped the use of discover for this mapping, as the
3874 modalias approach is more flexible and easier to use on Linux as long
3875 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
3876
3877 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
3878 here is the command required to check out and build the source: Use
3879 &#39;&lt;tt&gt;svn checkout
3880 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
3881 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
3882 devscripts package.&lt;/p&gt;
3883
3884 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
3885 renamed to Isenkram and the source moved from the Debian Edu
3886 subversion repository to a Debian collab-maint git repository. See
3887 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
3888 instructions&lt;/a&gt; for details.&lt;/p&gt;
3889 </description>
3890 </item>
3891
3892 <item>
3893 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
3894 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
3895 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
3896 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
3897 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
3898 suddenly in bed. With a quiet whimper, it went completely quiet and
3899 black. The power button was no longer able to turn it on. It was a
3900 IBM Thinkpad X41, and the best laptop I ever had. Better than both
3901 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
3902 Compaq I had before that. Now I need to find a replacement. To keep
3903 going during Christmas, I moved the one year old SSD disk to my old
3904 X40 where it fitted (only one I had left that could use it), but it is
3905 not a durable solution.
3906
3907 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
3908 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
3909
3910 &lt;ul&gt;
3911
3912 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
3913 than A4).&lt;/li&gt;
3914 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
3915 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
3916 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
3917 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
3918 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
3919 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
3920 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
3921 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
3922 size).&lt;/li&gt;
3923 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
3924 X.org packages.&lt;/li&gt;
3925 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
3926 the time).
3927
3928 &lt;/ul&gt;
3929
3930 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
3931 list. The reason is simply that the specifications on laptops the
3932 last 10-15 years have been sufficient for my needs, and I have to look
3933 at other features to choose my laptop. But are there still made as
3934 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
3935 robust, and Thinkpads seem to be heading in the wrong direction since
3936 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
3937 still be useful.&lt;/p&gt;
3938
3939 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
3940 external keyboard? I&#39;ll have to check the
3941 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
3942 well-supported laptops, or perhaps just buy one preinstalled from one
3943 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
3944 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
3945 </description>
3946 </item>
3947
3948 <item>
3949 <title>How to find a browser plugin supporting a given MIME type</title>
3950 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
3951 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
3952 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
3953 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
3954 install to get support for a given MIME type. Thanks to
3955 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
3956 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
3957 Unfortunately, not very many packages provide the needed meta
3958 information, Anyway, here is a small script to look up all browser
3959 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
3960
3961 &lt;pre&gt;
3962 #!/usr/bin/python
3963 import sys
3964 import apt
3965 def pkgs_handling_mimetype(mimetype):
3966 cache = apt.Cache()
3967 cache.open(None)
3968 thepkgs = []
3969 for pkg in cache:
3970 version = pkg.candidate
3971 if version is None:
3972 version = pkg.installed
3973 if version is None:
3974 continue
3975 record = version.record
3976 if not record.has_key(&#39;Npp-MimeType&#39;):
3977 continue
3978 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
3979 for t in mime_types:
3980 t = t.rstrip().strip()
3981 if t == mimetype:
3982 thepkgs.append(pkg.name)
3983 return thepkgs
3984 mimetype = &quot;audio/ogg&quot;
3985 if 1 &lt; len(sys.argv):
3986 mimetype = sys.argv[1]
3987 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
3988 for pkg in pkgs_handling_mimetype(mimetype):
3989 print &quot; %s&quot; %pkg
3990 &lt;/pre&gt;
3991
3992 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
3993
3994 &lt;pre&gt;
3995 % ./apt-find-browserplug-for-mimetype
3996 Browser plugin packages supporting audio/ogg:
3997 gecko-mediaplayer
3998 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
3999 Browser plugin packages supporting application/x-shockwave-flash:
4000 browser-plugin-gnash
4001 %
4002 &lt;/pre&gt;
4003
4004 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
4005 itself to query for plugins and propose to install the needed
4006 packages. It would be great if Debian supported such feature too. Is
4007 anyone working on adding it?&lt;/p&gt;
4008
4009 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
4010 request for icweasel support for this feature is
4011 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
4012 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
4013 of manpower and wish for a different design is the reason thus feature
4014 is not yet in iceweasel from Debian.&lt;/p&gt;
4015 </description>
4016 </item>
4017
4018 <item>
4019 <title>What is the most supported MIME type in Debian?</title>
4020 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
4021 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
4022 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
4023 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
4024 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
4025 proposal to make it possible for a Desktop application to propose to
4026 the user some package to install to gain support for a given MIME
4027 type, font, library etc. that is currently missing. With such
4028 mechanism in place, it would be possible for the desktop to
4029 automatically propose and install leocad if some LDraw file is
4030 downloaded by the browser.&lt;/p&gt;
4031
4032 &lt;p&gt;To get some idea about the current content of the archive, I decided
4033 to write a simple program to extract all .desktop files from the
4034 Debian archive and look up the claimed MIME support there. The result
4035 can be found on the
4036 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
4037 site&lt;/a&gt;. Using the collected information, it become possible to
4038 answer the question in the title. Here are the 20 most supported MIME
4039 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4040 The complete list is available from the link above.&lt;/p&gt;
4041
4042 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
4043
4044 &lt;pre&gt;
4045 count MIME type
4046 ----- -----------------------
4047 32 text/plain
4048 30 audio/mpeg
4049 29 image/png
4050 28 image/jpeg
4051 27 application/ogg
4052 26 audio/x-mp3
4053 25 image/tiff
4054 25 image/gif
4055 22 image/bmp
4056 22 audio/x-wav
4057 20 audio/x-flac
4058 19 audio/x-mpegurl
4059 18 video/x-ms-asf
4060 18 audio/x-musepack
4061 18 audio/x-mpeg
4062 18 application/x-ogg
4063 17 video/mpeg
4064 17 audio/x-scpls
4065 17 audio/ogg
4066 16 video/x-ms-wmv
4067 &lt;/pre&gt;
4068
4069 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
4070
4071 &lt;pre&gt;
4072 count MIME type
4073 ----- -----------------------
4074 33 text/plain
4075 32 image/png
4076 32 image/jpeg
4077 29 audio/mpeg
4078 27 image/gif
4079 26 image/tiff
4080 26 application/ogg
4081 25 audio/x-mp3
4082 22 image/bmp
4083 21 audio/x-wav
4084 19 audio/x-mpegurl
4085 19 audio/x-mpeg
4086 18 video/mpeg
4087 18 audio/x-scpls
4088 18 audio/x-flac
4089 18 application/x-ogg
4090 17 video/x-ms-asf
4091 17 text/html
4092 17 audio/x-musepack
4093 16 image/x-xbitmap
4094 &lt;/pre&gt;
4095
4096 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
4097
4098 &lt;pre&gt;
4099 count MIME type
4100 ----- -----------------------
4101 31 text/plain
4102 31 image/png
4103 31 image/jpeg
4104 29 audio/mpeg
4105 28 application/ogg
4106 27 image/gif
4107 26 image/tiff
4108 26 audio/x-mp3
4109 23 audio/x-wav
4110 22 image/bmp
4111 21 audio/x-flac
4112 20 audio/x-mpegurl
4113 19 audio/x-mpeg
4114 18 video/x-ms-asf
4115 18 video/mpeg
4116 18 audio/x-scpls
4117 18 application/x-ogg
4118 17 audio/x-musepack
4119 16 video/x-ms-wmv
4120 16 video/x-msvideo
4121 &lt;/pre&gt;
4122
4123 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
4124 information mentioned in DEP-11. I have not yet had time to look at
4125 it, but hope the PackageKit people in Debian are on top of these
4126 issues.&lt;/p&gt;
4127
4128 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
4129 discovering a typo in my script.&lt;/p&gt;
4130 </description>
4131 </item>
4132
4133 <item>
4134 <title>Using modalias info to find packages handling my hardware</title>
4135 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
4136 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
4137 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
4138 <description>&lt;p&gt;Yesterday, I wrote about the
4139 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
4140 values provided by the Linux kernel&lt;/a&gt; following my hope for
4141 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
4142 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
4143 modalias values attached to package names can be used to map packages
4144 to hardware. This allow the system to look up and suggest relevant
4145 packages when I plug in some new hardware into my machine, and replace
4146 discover and discover-data as the database used to map hardware to
4147 packages.&lt;/p&gt;
4148
4149 &lt;p&gt;I create a modaliases file with entries like the following,
4150 containing package name, kernel module name (if relevant, otherwise
4151 the package name) and globs matching the relevant hardware
4152 modalias.&lt;/p&gt;
4153
4154 &lt;p&gt;&lt;blockquote&gt;
4155 Package: package-name
4156 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
4157 &lt;/blockquote&gt;&lt;/p&gt;
4158
4159 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
4160 for a given modalias value using this file.&lt;/p&gt;
4161
4162 &lt;p&gt;An entry like this would suggest the video and picture application
4163 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
4164
4165 &lt;p&gt;&lt;blockquote&gt;
4166 Package: cheese
4167 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
4168 &lt;/blockquote&gt;&lt;/p&gt;
4169
4170 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
4171 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
4172
4173 &lt;p&gt;&lt;blockquote&gt;
4174 Package: pcmciautils
4175 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4176 &lt;/blockquote&gt;&lt;/p&gt;
4177
4178 &lt;p&gt;An entry like this would suggest the package colorhug-client when
4179 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
4180
4181 &lt;p&gt;&lt;blockquote&gt;
4182 Package: colorhug-client
4183 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
4184 &lt;/blockquote&gt;&lt;/p&gt;
4185
4186 &lt;p&gt;I believe the format is compatible with the format of the Packages
4187 file in the Debian archive. Ubuntu already uses their Packages file
4188 to store their mappings from packages to hardware.&lt;/p&gt;
4189
4190 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
4191 announce the hardware it support in a way my prototype understand.
4192 This allow those publishing packages in an APT source outside the
4193 Debian archive as well as those backporting packages to make sure the
4194 hardware mapping are included in the package meta information. I&#39;ve
4195 tested such header in the pymissile package, and its modalias mapping
4196 is working as it should with my prototype. It even made it to Ubuntu
4197 Raring.&lt;/p&gt;
4198
4199 &lt;p&gt;To test if it was possible to look up supported hardware using only
4200 the shell tools available in the Debian installer, I wrote a shell
4201 implementation of the lookup code. The idea is to create files for
4202 each modalias and let the shell do the matching. Please check out and
4203 try the
4204 &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;
4205 shell script. It run without any extra dependencies and fetch the
4206 hardware mappings from the Debian archive and the subversion
4207 repository where I currently work on my prototype.&lt;/p&gt;
4208
4209 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
4210 install yubikey-personalization:&lt;/p&gt;
4211
4212 &lt;p&gt;&lt;blockquote&gt;
4213 % ./hw-support-lookup
4214 &lt;br&gt;yubikey-personalization
4215 &lt;br&gt;%
4216 &lt;/blockquote&gt;&lt;/p&gt;
4217
4218 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4219 propose to install the pcmciautils package:&lt;/p&gt;
4220
4221 &lt;p&gt;&lt;blockquote&gt;
4222 % ./hw-support-lookup
4223 &lt;br&gt;pcmciautils
4224 &lt;br&gt;%
4225 &lt;/blockquote&gt;&lt;/p&gt;
4226
4227 &lt;p&gt;If you know of any hardware-package mapping that should be added to
4228 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
4229 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
4230
4231 &lt;p&gt;It could be possible to generate several of the mappings between
4232 packages and hardware. One source would be to look at packages with
4233 kernel modules, ie packages with *.ko files in /lib/modules/, and
4234 extract their modalias information. Another would be to look at
4235 packages with udev rules, ie packages with files in
4236 /lib/udev/rules.d/, and extract their vendor/model information to
4237 generate a modalias matching rule. I have not tested any of these to
4238 see if it work.&lt;/p&gt;
4239
4240 &lt;p&gt;If you want to help implementing a system to let us propose what
4241 packages to install when new hardware is plugged into a Debian
4242 machine, please send me an email or talk to me on
4243 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4244 </description>
4245 </item>
4246
4247 <item>
4248 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
4249 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
4250 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
4251 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
4252 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
4253 information, to find the packages that support a given piece of
4254 hardware, I refreshed my memory regarding modalias values, and decided
4255 to document the details. Here are my findings so far, also available
4256 in
4257 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4258 Debian Edu subversion repository&lt;/a&gt;:
4259
4260 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
4261
4262 &lt;p&gt;This document try to explain what the different types of modalias
4263 values stands for. It is in part based on information from
4264 &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;,
4265 &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;,
4266 &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
4267 &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;.
4268
4269 &lt;p&gt;The modalias entries for a given Linux machine can be found using
4270 this shell script:&lt;/p&gt;
4271
4272 &lt;pre&gt;
4273 find /sys -name modalias -print0 | xargs -0 cat | sort -u
4274 &lt;/pre&gt;
4275
4276 &lt;p&gt;The supported modalias globs for a given kernel module can be found
4277 using modinfo:&lt;/p&gt;
4278
4279 &lt;pre&gt;
4280 % /sbin/modinfo psmouse | grep alias:
4281 alias: serio:ty05pr*id*ex*
4282 alias: serio:ty01pr*id*ex*
4283 %
4284 &lt;/pre&gt;
4285
4286 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
4287
4288 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
4289 Bridge memory controller:&lt;/p&gt;
4290
4291 &lt;p&gt;&lt;blockquote&gt;
4292 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
4293 &lt;/blockquote&gt;&lt;/p&gt;
4294
4295 &lt;p&gt;This represent these values:&lt;/p&gt;
4296
4297 &lt;pre&gt;
4298 v 00008086 (vendor)
4299 d 00002770 (device)
4300 sv 00001028 (subvendor)
4301 sd 000001AD (subdevice)
4302 bc 06 (bus class)
4303 sc 00 (bus subclass)
4304 i 00 (interface)
4305 &lt;/pre&gt;
4306
4307 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
4308 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
4309 0600. The 0600 class is a host bridge. Other useful bus values are
4310 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
4311
4312 &lt;p&gt;Not sure how to figure out the interface value, nor what it
4313 means.&lt;/p&gt;
4314
4315 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
4316
4317 &lt;p&gt;Some typical USB entries can look like this. This is an internal
4318 USB hub in a laptop:&lt;/p&gt;
4319
4320 &lt;p&gt;&lt;blockquote&gt;
4321 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
4322 &lt;/blockquote&gt;&lt;/p&gt;
4323
4324 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
4325
4326 &lt;pre&gt;
4327 v 1D6B (device vendor)
4328 p 0001 (device product)
4329 d 0206 (bcddevice)
4330 dc 09 (device class)
4331 dsc 00 (device subclass)
4332 dp 00 (device protocol)
4333 ic 09 (interface class)
4334 isc 00 (interface subclass)
4335 ip 00 (interface protocol)
4336 &lt;/pre&gt;
4337
4338 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
4339 class is in the interface class section. For a simple USB web camera,
4340 these alias entries show up:&lt;/p&gt;
4341
4342 &lt;p&gt;&lt;blockquote&gt;
4343 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
4344 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
4345 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
4346 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
4347 &lt;/blockquote&gt;&lt;/p&gt;
4348
4349 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
4350 camera), 0101 is audio control device and 0102 is audio streaming (aka
4351 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
4352
4353 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
4354
4355 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
4356 receiver in a Thinkpad X40:&lt;/p&gt;
4357
4358 &lt;p&gt;&lt;blockquote&gt;
4359 acpi:IBM0071:PNP0511:
4360 &lt;/blockquote&gt;&lt;/p&gt;
4361
4362 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
4363
4364 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
4365
4366 &lt;p&gt;The DMI table contain lots of information about the computer case
4367 and model. This is an entry for a IBM Thinkpad X40, fetched from
4368 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
4369
4370 &lt;p&gt;&lt;blockquote&gt;
4371 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
4372 &lt;/blockquote&gt;&lt;/p&gt;
4373
4374 &lt;p&gt;The values present are&lt;/p&gt;
4375
4376 &lt;pre&gt;
4377 bvn IBM (BIOS vendor)
4378 bvr 1UETB6WW(1.66) (BIOS version)
4379 bd 06/15/2005 (BIOS date)
4380 svn IBM (system vendor)
4381 pn 2371H4G (product name)
4382 pvr ThinkPadX40 (product version)
4383 rvn IBM (board vendor)
4384 rn 2371H4G (board name)
4385 rvr NotAvailable (board version)
4386 cvn IBM (chassis vendor)
4387 ct 10 (chassis type)
4388 cvr NotAvailable (chassis version)
4389 &lt;/pre&gt;
4390
4391 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
4392 found in the dmidecode source:&lt;/p&gt;
4393
4394 &lt;pre&gt;
4395 3 Desktop
4396 4 Low Profile Desktop
4397 5 Pizza Box
4398 6 Mini Tower
4399 7 Tower
4400 8 Portable
4401 9 Laptop
4402 10 Notebook
4403 11 Hand Held
4404 12 Docking Station
4405 13 All In One
4406 14 Sub Notebook
4407 15 Space-saving
4408 16 Lunch Box
4409 17 Main Server Chassis
4410 18 Expansion Chassis
4411 19 Sub Chassis
4412 20 Bus Expansion Chassis
4413 21 Peripheral Chassis
4414 22 RAID Chassis
4415 23 Rack Mount Chassis
4416 24 Sealed-case PC
4417 25 Multi-system
4418 26 CompactPCI
4419 27 AdvancedTCA
4420 28 Blade
4421 29 Blade Enclosing
4422 &lt;/pre&gt;
4423
4424 &lt;p&gt;The chassis type values are not always accurately set in the DMI
4425 table. For example my home server is a tower, but the DMI modalias
4426 claim it is a desktop.&lt;/p&gt;
4427
4428 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
4429
4430 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
4431 test machine:&lt;/p&gt;
4432
4433 &lt;p&gt;&lt;blockquote&gt;
4434 serio:ty01pr00id00ex00
4435 &lt;/blockquote&gt;&lt;/p&gt;
4436
4437 &lt;p&gt;The values present are&lt;/p&gt;
4438
4439 &lt;pre&gt;
4440 ty 01 (type)
4441 pr 00 (prototype)
4442 id 00 (id)
4443 ex 00 (extra)
4444 &lt;/pre&gt;
4445
4446 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
4447 the valid values are.&lt;/p&gt;
4448
4449 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
4450
4451 &lt;p&gt;There are heaps of other modalias subtypes according to
4452 file2alias.c. There is the rest of the list from that source: amba,
4453 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
4454 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
4455 vmbus, x86cpu and zorro. I did not spend time documenting all of
4456 these, as they do not seem relevant for my intended use with mapping
4457 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
4458
4459 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
4460
4461 &lt;p&gt;To check which kernel modules provide support for a given modalias,
4462 one can use the following shell script:&lt;/p&gt;
4463
4464 &lt;pre&gt;
4465 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
4466 echo &quot;$id&quot; ; \
4467 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
4468 done
4469 &lt;/pre&gt;
4470
4471 &lt;p&gt;The output can look like this (only the first few entries as the
4472 list is very long on my test machine):&lt;/p&gt;
4473
4474 &lt;pre&gt;
4475 acpi:ACPI0003:
4476 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
4477 acpi:device:
4478 FATAL: Module acpi:device: not found.
4479 acpi:IBM0068:
4480 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
4481 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
4482 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
4483 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
4484 acpi:IBM0071:PNP0511:
4485 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
4486 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
4487 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
4488 [...]
4489 &lt;/pre&gt;
4490
4491 &lt;p&gt;If you want to help implementing a system to let us propose what
4492 packages to install when new hardware is plugged into a Debian
4493 machine, please send me an email or talk to me on
4494 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4495
4496 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
4497 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
4498 in /sys/ with space in them.&lt;/p&gt;
4499 </description>
4500 </item>
4501
4502 <item>
4503 <title>Moved the pymissile Debian packaging to collab-maint</title>
4504 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
4505 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
4506 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
4507 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
4508 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
4509 Launcher and updated the Debian package
4510 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
4511 sure udev will fix the device permissions when it is plugged in. I
4512 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
4513 hopefully make the package be proposed by jockey in Ubuntu when a user
4514 plug in his rocket launcher. In the process I moved the source to a
4515 git repository under collab-maint, to make it easier for any DD to
4516 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
4517 is not very active, but the software still work for me even after five
4518 years of relative silence. The new git repository is not listed in
4519 the uploaded package yet, because I want to test the other changes a
4520 bit more before I upload the new version. If you want to check out
4521 the new version with a .desktop file included, visit the
4522 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
4523 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
4524 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
4525 </description>
4526 </item>
4527
4528 <item>
4529 <title>Lets make hardware dongles easier to use in Debian</title>
4530 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
4531 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
4532 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
4533 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
4534 general, is that there is a great package management system with the
4535 ability to automatically install software packages by downloading them
4536 from the distribution mirrors, but no way to get it to automatically
4537 install the packages I need to use the hardware I plug into my
4538 machine. Even if the package to use it is easily available from the
4539 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
4540 suggest to automatically install the python-nxt, nbc and t2n packages
4541 I need to talk to it. When I plug in a Yubikey, it could propose the
4542 yubikey-personalization package. The information required to do this
4543 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
4544
4545 &lt;p&gt;Some years ago, I proposed to
4546 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
4547 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
4548 simple:
4549
4550 &lt;ul&gt;
4551
4552 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
4553 starting when a user log in.&lt;/li&gt;
4554
4555 &lt;li&gt;Set this program up to listen for kernel events emitted when new
4556 hardware is inserted into the computer.&lt;/li&gt;
4557
4558 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
4559 database mapping to packages, and take note of any non-installed
4560 packages.&lt;/li&gt;
4561
4562 &lt;li&gt;Show a message to the user proposing to install the discovered
4563 package, and make it easy to install it.&lt;/li&gt;
4564
4565 &lt;/ul&gt;
4566
4567 &lt;p&gt;I am not sure what the best way to implement this is, but my
4568 initial idea was to use dbus events to discover new hardware, the
4569 discover database to find packages and
4570 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
4571 packages.&lt;/p&gt;
4572
4573 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
4574 draft package is now checked into
4575 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
4576 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
4577 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
4578 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
4579 the relevant packages in Debian, and uploaded a new version
4580 2.2013.01.09 to unstable. I also discovered that the current
4581 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
4582 package in Debian no longer discovered any USB devices, because
4583 /proc/bus/usb/devices is no longer present. I ported it to use
4584 libusb as a fall back option to get it working. The fixed package
4585 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
4586 because of the freeze).&lt;/p&gt;
4587
4588 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
4589 desktop notification to show up (only once, the first time it is
4590 inserted):&lt;/p&gt;
4591
4592 &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;
4593
4594 &lt;p&gt;For this prototype to be really useful, some way to automatically
4595 install the proposed packages by pressing the &quot;Please install
4596 program(s)&quot; button should to be implemented.&lt;/p&gt;
4597
4598 &lt;p&gt;If this idea seem useful to you, and you want to help make it
4599 happen, please help me update the discover-data database with mappings
4600 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
4601 list the package you would like to have installed when a given
4602 hardware device is inserted into your computer, and report bugs using
4603 reportbug if it isn&#39;t. Or, if you know of a better way to provide
4604 such mapping, please let me know.&lt;/p&gt;
4605
4606 &lt;p&gt;This prototype need more work, and there are several questions that
4607 should be considered before it is ready for production use. Is dbus
4608 the correct way to detect new hardware? At the moment I look for HAL
4609 dbus events on the system bus, because that is the events I could see
4610 on my Debian Squeeze KDE desktop. Are there better events to use?
4611 How should the user be notified? Is the desktop notification
4612 mechanism the best option, or should the background daemon raise a
4613 popup instead? How should packages be installed? When should they
4614 not be installed?&lt;/p&gt;
4615
4616 &lt;p&gt;If you want to help getting such feature implemented in Debian,
4617 please send me an email. :)&lt;/p&gt;
4618 </description>
4619 </item>
4620
4621 <item>
4622 <title>New IRC channel for LEGO designers using Debian</title>
4623 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
4624 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
4625 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
4626 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
4627 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
4628 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
4629 discovered I had to build all the tools myself because none were
4630 already in Debian Squeeze. If Debian support for LEGO is something
4631 you care about, please join me on the IRC channel
4632 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
4633 irc.debian.org). There is a lot that could be done to improve the
4634 Debian support for LEGO designers. For example both CAD software
4635 and Mindstorm compilers are missing. :)&lt;/p&gt;
4636
4637 &lt;p&gt;Update 2012-01-03: A
4638 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
4639 including links to Lego related packages is now available.&lt;/p&gt;
4640 </description>
4641 </item>
4642
4643 <item>
4644 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
4645 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
4646 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
4647 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
4648 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
4649 year! I hope next year will prove to be a good year.&lt;/p&gt;
4650
4651 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
4652 decentralised &quot;currency&quot; that allow people to transfer bitcoins
4653 between each other with minimal overhead, is a very interesting
4654 experiment. And as I wrote a few days ago, the bitcoin situation in
4655 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
4656 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
4657 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
4658 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
4659 for one of the ftpmasters to approve the new bitcoin-qt package
4660 name.&lt;/p&gt;
4661
4662 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
4663 team in Debian, you can easily test the package in Debian Squeeze
4664 using the following steps to get a set of working packages:&lt;/p&gt;
4665
4666 &lt;blockquote&gt;&lt;pre&gt;
4667 git clone git://git.debian.org/git/collab-maint/bitcoin
4668 cd bitcoin
4669 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
4670 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
4671 &lt;/pre&gt;&lt;/blockquote&gt;
4672
4673 &lt;p&gt;You might have to install some build dependencies as well. The
4674 list of commands should give you two packages, bitcoind and
4675 bitcoin-qt, ready for use in a Squeeze environment. Note that the
4676 client will download the complete set of bitcoin &quot;blocks&quot;, which need
4677 around 5.6 GiB of data on my machine at the moment. Make sure your
4678 ~/.bitcoin/ directory have lots of spare room if you want to download
4679 all the blocks. The client will warn if the disk is getting full, so
4680 there is not really a problem if you got too little room, but you will
4681 not be able to get all the features out of the client.&lt;/p&gt;
4682
4683 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4684 activities, please send Bitcoin donations to my address
4685 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4686 </description>
4687 </item>
4688
4689 <item>
4690 <title>A word on bitcoin support in Debian</title>
4691 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
4692 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
4693 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
4694 <description>&lt;p&gt;It has been a while since I wrote about
4695 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
4696 peer-to-peer based crypto-currency, and the reason is simply that I
4697 have been busy elsewhere. But two days ago, I started looking at the
4698 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
4699 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
4700 is now maintained by a
4701 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
4702 people&lt;/a&gt;, and the grunt work had already been done by this team. We
4703 owe a huge thank you to all these team members. :)
4704 But I was sad to discover that the bitcoin client is missing in
4705 Wheezy. It is only available in Sid (and an outdated client from
4706 backports). The client had several RC bugs registered in BTS blocking
4707 it from entering testing. To try to help the team and improve the
4708 situation, I spent some time providing patches and triaging the bug
4709 reports. I also had a look at the bitcoin package available from Matt
4710 Corallo in a
4711 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
4712 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
4713 Debian package.&lt;/p&gt;
4714
4715 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
4716 IRC, I pushed several patches into the collab-maint git repository to
4717 improve the package. It now contains fixes for the RC issues (not from
4718 me, but fixed by Scott Howard), build rules for a Qt GUI client
4719 package, konqueror support for the bitcoin: URI and bash completion
4720 setup. As I work on Debian Squeeze, I also created
4721 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
4722 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
4723 it and try to integrate it into the git repository before uploading a
4724 new version to unstable.
4725
4726 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
4727 centralized control currently exercised in the monetary system. I
4728 find it completely unacceptable that the USA government is collecting
4729 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
4730 that the major credit card companies can block legal money
4731 transactions to Wikileaks. But for bitcoin to succeed, more people
4732 need to use bitcoins, and more people need to accept bitcoins when
4733 they sell products and services. Improving the bitcoin support in
4734 Debian is a small step in the right direction, but not enough.
4735 Unfortunately the user experience when browsing the web and wanting to
4736 pay with bitcoin is still not very good. The bitcoin: URI is a step
4737 in the right direction, but need to work in most or every browser in
4738 use. Also the bitcoin-qt client is too heavy to fire up to do a
4739 quick transaction. I believe there are other clients available, but
4740 have not tested them.&lt;/p&gt;
4741
4742 &lt;p&gt;My
4743 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
4744 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
4745 I received 20.15 BTC so far on the address I provided in my blog two
4746 years ago, as can be
4747 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
4748 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
4749 donation. The blockexplorer service demonstrates quite well that
4750 bitcoin is not quite anonymous and untracked. :) I wonder if the
4751 number of users have gone up since then. If you use bitcoin and want
4752 to show your support of my activity, please send Bitcoin donations to
4753 the same address as last time,
4754 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4755 </description>
4756 </item>
4757
4758 <item>
4759 <title>Git repository for song book for Computer Scientists</title>
4760 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
4761 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
4762 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
4763 <description>&lt;p&gt;As I
4764 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
4765 this summer&lt;/a&gt;, I have created a Computer Science song book a few
4766 years ago, and today I finally found time to create a public
4767 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
4768 repository for the project&lt;/a&gt;.&lt;/p&gt;
4769
4770 &lt;p&gt;If you want to help out, please clone the source and submit patches
4771 to the HTML version. To generate the PDF and PostScript version,
4772 please use prince XML, or let me know about a useful free software
4773 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
4774
4775 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
4776 PostScript formats at
4777 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
4778 Science Songbook&lt;/a&gt;.&lt;/p&gt;
4779 </description>
4780 </item>
4781
4782 <item>
4783 <title>Gratulerer med 19-årsdagen, Debian!</title>
4784 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
4785 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
4786 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
4787 <description>&lt;p&gt;I dag fyller
4788 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
4789 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
4790 si gratulerer med dagen, Debian!&lt;/p&gt;
4791 </description>
4792 </item>
4793
4794 <item>
4795 <title>Song book for Computer Scientists</title>
4796 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
4797 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
4798 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
4799 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
4800 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
4801 collecting computer related songs for use at parties. The original
4802 version was written in LaTeX, but a few years ago I got help from
4803 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
4804 while keeping the ability to create a nice book in PDF format. I have
4805 not had time to maintain the book for a while now, and guess I should
4806 put it up on some public version control repository where others can
4807 help me extend and update the book. If anyone is volunteering to help
4808 me with this, send me an email. Also let me know if there are songs
4809 missing in my book.&lt;/p&gt;
4810
4811 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
4812 me today that I really should let all my readers share the joys of
4813 singing out load about programming, computers and computer networks.
4814 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
4815 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
4816 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
4817 Computer Science Songbook&lt;/a&gt;.
4818 </description>
4819 </item>
4820
4821 <item>
4822 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
4823 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
4824 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
4825 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
4826 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
4827 around 1000 at the moment. To be able to get help from the vendors
4828 when something go wrong, we want to keep the firmware on the servers
4829 up to date. If the firmware isn&#39;t the latest and greatest, the
4830 vendors typically refuse to start debugging any problems until the
4831 firmware is upgraded. So before every reboot, we want to upgrade the
4832 firmware, and we would really like everyone handling servers at the
4833 university to do this themselves when they plan to reboot a machine.
4834 For that to happen we at the unix server admin group need to provide
4835 the tools to do so.&lt;/p&gt;
4836
4837 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
4838 fetch and install the latest firmware for the servers we got. Most of
4839 our hardware are from Dell and HP, so I have focused on these servers
4840 so far. This blog post is about the Dell part.&lt;/P&gt;
4841
4842 &lt;p&gt;On the Dell FTP site I was lucky enough to find
4843 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
4844 with firmware information for all 11th generation servers, listing
4845 which firmware should be used on a given model and where on the FTP
4846 site I can find it. Using a simple perl XML parser I can then
4847 download the shell scripts Dell provides to do firmware upgrades from
4848 within Linux and reboot when all the firmware is primed and ready to
4849 be activated on the first reboot.&lt;/p&gt;
4850
4851 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
4852 Are there anyone working on similar tools for firmware upgrading all
4853 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
4854
4855 &lt;p&gt;&lt;pre&gt;
4856 #!/usr/bin/perl
4857 use strict;
4858 use warnings;
4859 use File::Temp qw(tempdir);
4860 BEGIN {
4861 # Install needed RHEL packages if missing
4862 my %rhelmodules = (
4863 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
4864 );
4865 for my $module (keys %rhelmodules) {
4866 eval &quot;use $module;&quot;;
4867 if ($@) {
4868 my $pkg = $rhelmodules{$module};
4869 system(&quot;yum install -y $pkg&quot;);
4870 eval &quot;use $module;&quot;;
4871 }
4872 }
4873 }
4874 my $errorsto = &#39;pere@hungry.com&#39;;
4875
4876 upgrade_dell();
4877
4878 exit 0;
4879
4880 sub run_firmware_script {
4881 my ($opts, $script) = @_;
4882 unless ($script) {
4883 print STDERR &quot;fail: missing script name\n&quot;;
4884 exit 1
4885 }
4886 print STDERR &quot;Running $script\n\n&quot;;
4887
4888 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
4889 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
4890 } else {
4891 print STDERR &quot;fail: firmware script returned error\n&quot;;
4892 }
4893 }
4894
4895 sub run_firmware_scripts {
4896 my ($opts, @dirs) = @_;
4897 # Run firmware packages
4898 for my $dir (@dirs) {
4899 print STDERR &quot;info: Running scripts in $dir\n&quot;;
4900 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
4901 while (my $s = readdir $dh) {
4902 next if $s =~ m/^\.\.?/;
4903 run_firmware_script($opts, &quot;$dir/$s&quot;);
4904 }
4905 closedir $dh;
4906 }
4907 }
4908
4909 sub download {
4910 my $url = shift;
4911 print STDERR &quot;info: Downloading $url\n&quot;;
4912 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
4913 }
4914
4915 sub upgrade_dell {
4916 my @dirs;
4917 my $product = `dmidecode -s system-product-name`;
4918 chomp $product;
4919
4920 if ($product =~ m/PowerEdge/) {
4921
4922 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
4923 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
4924
4925 my $tmpdir = tempdir(
4926 CLEANUP =&gt; 1
4927 );
4928 chdir($tmpdir);
4929 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
4930 system(&#39;gunzip Catalog.xml.gz&#39;);
4931 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
4932 # -q is quiet, disabling interactivity and reducing console output
4933 my $fwopts = &quot;-q&quot;;
4934 if (@paths) {
4935 for my $url (@paths) {
4936 fetch_dell_fw($url);
4937 }
4938 run_firmware_scripts($fwopts, $tmpdir);
4939 } else {
4940 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4941 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4942 }
4943 chdir(&#39;/&#39;);
4944 } else {
4945 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
4946 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
4947 }
4948 }
4949
4950 sub fetch_dell_fw {
4951 my $path = shift;
4952 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
4953 download($url);
4954 }
4955
4956 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
4957 # firmware packages to download from Dell. Only work for Linux
4958 # machines and 11th generation Dell servers.
4959 sub fetch_dell_fw_list {
4960 my $filename = shift;
4961
4962 my $product = `dmidecode -s system-product-name`;
4963 chomp $product;
4964 my ($mybrand, $mymodel) = split(/\s+/, $product);
4965
4966 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
4967
4968 my $xml = XMLin($filename);
4969 my @paths;
4970 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
4971 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
4972 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
4973 my $oscode;
4974 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
4975 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
4976 } else {
4977 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
4978 }
4979 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
4980 {
4981 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
4982 }
4983 }
4984 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
4985 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
4986
4987 # Drop application packages, only firmware and BIOS
4988 next if &#39;APAC&#39; eq $componenttype;
4989
4990 my $cpath = $component-&gt;{path};
4991 for my $path (@paths) {
4992 if ($cpath =~ m%/$path$%) {
4993 push(@paths, $cpath);
4994 }
4995 }
4996 }
4997 return @paths;
4998 }
4999 &lt;/pre&gt;
5000
5001 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
5002 it could work on other platforms with some tweaking. Anyone know a
5003 index like Catalog.xml is available from HP for HP servers? At the
5004 moment I maintain a similar list manually and it is quickly getting
5005 outdated.&lt;/p&gt;
5006 </description>
5007 </item>
5008
5009 <item>
5010 <title>How is booting into runlevel 1 different from single user boots?</title>
5011 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
5012 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
5013 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
5014 <description>&lt;p&gt;Wouter Verhelst have some
5015 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
5016 comments and opinions&lt;/a&gt; on my blog post on
5017 &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
5018 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
5019 &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
5020 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
5021 small piece of his comment now, and though it best to address the
5022 misunderstanding he bring forward:&lt;/p&gt;
5023
5024 &lt;p&gt;&lt;blockquote&gt;
5025 Currently, a system admin has four options: [...] boot to a
5026 single-user system (by adding &#39;single&#39; to the kernel command line;
5027 this runs rcS and rc1 scripts)
5028 &lt;/blockquote&gt;&lt;/p&gt;
5029
5030 &lt;p&gt;This make me believe Wouter believe booting into single user mode
5031 and booting into runlevel 1 is the same. I am not surprised he
5032 believe this, because it would make sense and is a quite sensible
5033 thing to believe. But because the boot in Debian is slightly broken,
5034 runlevel 1 do not work properly and it isn&#39;t the same as single user
5035 mode. I&#39;ll try to explain what is actually happing, but it is a bit
5036 hard to explain.&lt;/p&gt;
5037
5038 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
5039 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
5040 executed in single user mode is sulogin. Single user mode is a boot
5041 state &quot;between&quot; the runlevels, and when booting into single user mode,
5042 only the scripts in /etc/rcS.d/ are executed before the init process
5043 enters the single user state. When switching to runlevel 1, the state
5044 is in fact not ending in runlevel 1, but it passes through runlevel 1
5045 and end up in the single user mode (see /etc/rc1.d/S03single, which
5046 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
5047 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
5048 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5049 mode).&lt;/p&gt;
5050
5051 &lt;p&gt;This summary might make it clearer. When booting for the first
5052 time into single user mode, the following commands are executed:
5053 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
5054 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
5055 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
5056 trying to continue after visiting single user mode. Not all services
5057 are started again as they should, causing the machine to end up in an
5058 unpredicatble state. This is why Debian admins recommend rebooting
5059 after visiting single user mode.&lt;/p&gt;
5060
5061 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
5062 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
5063 to runlevel 1, the services started from /etc/rcS.d/ are not properly
5064 stopped when passing through the scripts in /etc/rc1.d/, and not
5065 started again when switching away from runlevel 1 to the runlevels
5066 2-5. I believe the problem is best fixed by moving all the scripts
5067 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
5068 functioning single user mode during boot.&lt;/p&gt;
5069
5070 &lt;p&gt;I have spent several years investigating the Debian boot system,
5071 and discovered this problem a few years ago. I suspect it originates
5072 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
5073 </description>
5074 </item>
5075
5076 <item>
5077 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
5078 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
5079 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
5080 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
5081 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
5082 are started from /etc/rcS.d/. In fact, there is a bite more of them
5083 than make sense, and this causes a few problems. What kind of
5084 problems, you might ask. There are at least two problems. The first
5085 is that it is not possible to recover a machine after switching to
5086 runlevel 1. One need to actually reboot to get the machine back to
5087 the expected state. The other is that single user boot will sometimes
5088 run into problems because some of the subsystems are activated before
5089 the root login is presented, causing problems when trying to recover a
5090 machine from a problem in that subsystem. A minor additional point is
5091 that moving more scripts out of rcS.d/ and into the other rc#.d/
5092 directories will increase the amount of scripts that can run in
5093 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
5094
5095 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
5096 scripts that _have_ to execute before the root login prompt is
5097 presented during a single user boot should go there. Everything else
5098 should go into the numeric runlevels. This means things like
5099 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5100 the numeric runlevels. Today in Debian, there are around 115 init.d
5101 scripts that are started from rcS.d/, and most of them should be moved
5102 out. Do your package have one of them? Please help us make single
5103 user and runlevel 1 better by moving it.&lt;/p&gt;
5104
5105 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
5106 etc. should still be started from rcS.d/, but there is for example no
5107 need to have the network enabled before the single user login prompt
5108 is presented.&lt;/p&gt;
5109
5110 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
5111 Debian systems working while scripts migrate and during upgrades, the
5112 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5113 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5114 and the next ones can only be moved when their dependencies have been
5115 moved first. This migration must be done sequentially while we ensure
5116 that the package system upgrade packages in the right order to keep
5117 the system state correct. This will require some coordination when it
5118 comes to network related packages, but most of the packages with
5119 scripts that should migrate do not have anything in rcS.d/ depending
5120 on them. Some packages have already been updated, like the sudo
5121 package, while others are still left to do. I wish I had time to work
5122 on this myself, but real live constrains make it unlikely that I will
5123 find time to push this forward.&lt;/p&gt;
5124 </description>
5125 </item>
5126
5127 <item>
5128 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
5129 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
5130 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
5131 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
5132 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
5133 mentioned the issues I believe should be improved in Debian for its
5134 desktop to be useful for more people. The use case for this is my
5135 parents, which are currently running Kubuntu which solve the
5136 issues.&lt;/p&gt;
5137
5138 &lt;p&gt;I suspect these four missing features are not very hard to
5139 implement. After all, they are present in Ubuntu, so if we wanted to
5140 do this in Debian we would have a source.&lt;/p&gt;
5141
5142 &lt;ol&gt;
5143
5144 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
5145 are new packages available for upgrades, a icon in the KDE status bar
5146 indicate this, and clicking on it will activate the simple upgrade
5147 tool to handle it. I have no problem guiding both of my parents
5148 through the process over the phone. If a kernel reboot is required,
5149 this too is indicated by the status bars and the upgrade tool. Last
5150 time I checked, nothing with the same features was working in KDE in
5151 Debian.&lt;/li&gt;
5152
5153 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
5154 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
5155 currently have a handler for, it will ask the user if the system
5156 should search for a package that would add support for this MIME type,
5157 and if the user say yes, the APT sources will be searched for packages
5158 advertising the MIME type in their control file (visible in the
5159 Packages file in the APT archive). If one or more packages are found,
5160 it is a simple click of the mouse to add support for the missing mime
5161 type. If the package require the user to accept some non-free
5162 license, this is explained to the user. The entire process make it
5163 more clear to the user why something do not work in the browser, and
5164 make the chances higher for the user to blame the web page authors and
5165 not the browser for any missing features.&lt;/li&gt;
5166
5167 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
5168 handlers.&lt;/strong&gt; When the media players encounter a format or codec
5169 it is not supporting, a dialog pop up asking the user if the system
5170 should search for a package that would add support for it. This
5171 happen with things like MP3, Windows Media or H.264. The selection
5172 and installation procedure is very similar to the Firefox browser
5173 plugin handling. This is as far as I know implemented using a
5174 gstreamer hook. The end result is that the user easily get access to
5175 the codecs that are present from the APT archives available, while
5176 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
5177
5178 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
5179 displaying a text/plain file in my Debian browser, it will propose to
5180 start emacs to show it. If I remember correctly, when doing the same
5181 in Kunbutu it show the file as a text file in the browser. At least I
5182 know Opera will show text files within the browser. I much prefer the
5183 latter behaviour.&lt;/li&gt;
5184
5185 &lt;/ol&gt;
5186
5187 &lt;p&gt;There are other nice features as well, like the simplified suite
5188 upgrader, but given that I am the one mostly doing the dist-upgrade,
5189 it do not matter much.&lt;/p&gt;
5190
5191 &lt;p&gt;I really hope we could get these features in place for the next
5192 Debian release. It would require the coordinated effort of several
5193 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
5194 </description>
5195 </item>
5196
5197 <item>
5198 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
5199 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
5200 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
5201 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
5202 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
5203 site is build on Debian/Squeeze, and this platform was chosen because
5204 I am most familiar with Debian (being a Debian Developer for around 10
5205 years) because it is the latest stable Debian release which should get
5206 security support for a few years.&lt;/p&gt;
5207
5208 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
5209 that are missing in Debian at the moment. It would be great if these
5210 modules were added to the Debian archive, allowing anyone to set up
5211 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
5212 in their own country using only Debian packages. The list of modules
5213 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
5214 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
5215 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5216 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5217 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5218 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5219 easier in the future.&lt;/p&gt;
5220
5221 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
5222 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
5223 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
5224 with the responsibility of tracking security problems, which I really
5225 do not have time for.&lt;/p&gt;
5226 </description>
5227 </item>
5228
5229 <item>
5230 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
5231 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
5232 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
5233 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
5234 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
5235 posts have been in Norwegian the last few weeks, so here is a short
5236 update in English.&lt;/p&gt;
5237
5238 &lt;p&gt;The kids still keep me too busy to get much free software work
5239 done, but I did manage to organise a project to get a Norwegian port
5240 of the British service
5241 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
5242 and it has been running for a month now. The entire project has been
5243 organised by me and two others. Around Christmas we gathered sponsors
5244 to fund the development work. In January I drafted a contract with
5245 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
5246 and in February the development took place. Most of it involved
5247 converting the source to use GPS coordinates instead of British
5248 easting/northing, and the resulting code should be a lot easier to get
5249 running in any country by now. The Norwegian
5250 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
5251 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
5252 source and the source for administrative borders in Norway, and
5253 support for this had to be added/fixed.&lt;/p&gt;
5254
5255 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
5256 polishing the system before we announced it March 7th. The system is
5257 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
5258 problem reports in a few weeks. Soon we hope to announce the Android
5259 and iPhone versions making it even easier to report problems with the
5260 public infrastructure.&lt;/p&gt;
5261
5262 &lt;p&gt;Perhaps something to consider for those of you in countries without
5263 such service?&lt;/p&gt;
5264 </description>
5265 </item>
5266
5267 <item>
5268 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
5269 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
5270 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
5271 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
5272 <description>&lt;p&gt;The last few days I have looked at ways to track open security
5273 issues here at my work with the University of Oslo. My idea is that
5274 it should be possible to use the information about security issues
5275 available on the Internet, and check our locally
5276 maintained/distributed software against this information. It should
5277 allow us to verify that no known security issues are forgotten. The
5278 CVE database listing vulnerabilities seem like a great central point,
5279 and by using the package lists from Debian mapped to CVEs provided by
5280 the testing security team, I believed it should be possible to figure
5281 out which security holes were present in our free software
5282 collection.&lt;/p&gt;
5283
5284 &lt;p&gt;After reading up on the topic, it became obvious that the first
5285 building block is to be able to name software packages in a unique and
5286 consistent way across data sources. I considered several ways to do
5287 this, for example coming up with my own naming scheme like using URLs
5288 to project home pages or URLs to the Freshmeat entries, or using some
5289 existing naming scheme. And it seem like I am not the first one to
5290 come across this problem, as MITRE already proposed and implemented a
5291 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
5292 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
5293 software, hardware and other platform components. The CPE ids are
5294 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
5295 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
5296 issues for any CPE name. With this in place, all I need to do is to
5297 locate the CPE id for the software packages we use at the university.
5298 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
5299 NVD entry if a CVE for the package exist).&lt;/p&gt;
5300
5301 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
5302 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
5303 check out, one could look up
5304 &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
5305 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
5306 The most recent one is
5307 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
5308 and at the bottom of the NVD page for this vulnerability the complete
5309 list of affected versions is provided.&lt;/p&gt;
5310
5311 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
5312 for offline processing of issues. Using this dump, I&#39;ve written a
5313 small script taking a list of CPEs as input and list all CVEs
5314 affecting the packages represented by these CPEs. One give it CPEs
5315 with version numbers as specified above and get a list of open
5316 security issues out.&lt;/p&gt;
5317
5318 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
5319 information need to be high. For that to happen, I believe as many as
5320 possible need to use and contribute to the NVD database. I notice
5321 RHEL is providing
5322 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
5323 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
5324 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
5325
5326 &lt;p&gt;To get an idea about the quality for free software, I spent some
5327 time making it possible to compare the CVE database from Debian with
5328 the CVE database in NVD. The result look fairly good, but there are
5329 some inconsistencies in NVD (same software package having several
5330 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
5331 Debian believe are affected by a CVE). Hope to find time to improve
5332 the quality of NVD, but that require being able to get in touch with
5333 someone maintaining it. So far my three emails with questions and
5334 corrections have not seen any reply, but I hope contact can be
5335 established soon.&lt;/p&gt;
5336
5337 &lt;p&gt;An interesting application for CPEs is cross platform package
5338 mapping. It would be useful to know which packages in for example
5339 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
5340 this would be trivial if all linux distributions provided CPE entries
5341 for their packages.&lt;/p&gt;
5342 </description>
5343 </item>
5344
5345 <item>
5346 <title>Which module is loaded for a given PCI and USB device?</title>
5347 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
5348 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
5349 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
5350 <description>&lt;p&gt;In the
5351 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
5352 package in Debian, there is a script to report useful information
5353 about the running hardware for use when people report missing
5354 information. One part of this script that I find very useful when
5355 debugging hardware problems, is the part mapping loaded kernel module
5356 to the PCI device it claims. It allow me to quickly see if the kernel
5357 module I expect is driving the hardware I am struggling with. To see
5358 the output, make sure discover-data is installed and run
5359 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
5360 one of my machines like this:&lt;/p&gt;
5361
5362 &lt;pre&gt;
5363 loaded modules:
5364 10de:03eb i2c_nforce2
5365 10de:03f1 ohci_hcd
5366 10de:03f2 ehci_hcd
5367 10de:03f0 snd_hda_intel
5368 10de:03ec pata_amd
5369 10de:03f6 sata_nv
5370 1022:1103 k8temp
5371 109e:036e bttv
5372 109e:0878 snd_bt87x
5373 11ab:4364 sky2
5374 &lt;/pre&gt;
5375
5376 &lt;p&gt;The code in question look like this, slightly modified for
5377 readability and to drop the output to file descriptor 3:&lt;/p&gt;
5378
5379 &lt;pre&gt;
5380 if [ -d /sys/bus/pci/devices/ ] ; then
5381 echo loaded pci modules:
5382 (
5383 cd /sys/bus/pci/devices/
5384 for address in * ; do
5385 if [ -d &quot;$address/driver/module&quot; ] ; then
5386 module=`cd $address/driver/module ; pwd -P | xargs basename`
5387 if grep -q &quot;^$module &quot; /proc/modules ; then
5388 address=$(echo $address |sed s/0000://)
5389 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
5390 echo &quot;$id $module&quot;
5391 fi
5392 fi
5393 done
5394 )
5395 echo
5396 fi
5397 &lt;/pre&gt;
5398
5399 &lt;p&gt;Similar code could be used to extract USB device module
5400 mappings:&lt;/p&gt;
5401
5402 &lt;pre&gt;
5403 if [ -d /sys/bus/usb/devices/ ] ; then
5404 echo loaded usb modules:
5405 (
5406 cd /sys/bus/usb/devices/
5407 for address in * ; do
5408 if [ -d &quot;$address/driver/module&quot; ] ; then
5409 module=`cd $address/driver/module ; pwd -P | xargs basename`
5410 if grep -q &quot;^$module &quot; /proc/modules ; then
5411 address=$(echo $address |sed s/0000://)
5412 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
5413 if [ &quot;$id&quot; ] ; then
5414 echo &quot;$id $module&quot;
5415 fi
5416 fi
5417 fi
5418 done
5419 )
5420 echo
5421 fi
5422 &lt;/pre&gt;
5423
5424 &lt;p&gt;This might perhaps be something to include in other tools as
5425 well.&lt;/p&gt;
5426 </description>
5427 </item>
5428
5429 <item>
5430 <title>How to test if a laptop is working with Linux</title>
5431 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
5432 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
5433 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
5434 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
5435 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
5436 batch of computers will work with Linux. Every year for the last few
5437 years the university have organised shared bid of a few thousand
5438 computers, and this year HP won the bid. Two different desktops and
5439 five different laptops are on the list this year. We in the UNIX
5440 group want to know which one of these computers work well with RHEL
5441 and Ubuntu, the two Linux distributions we currently handle at the
5442 university.&lt;/p&gt;
5443
5444 &lt;p&gt;My test method is simple, and I share it here to get feedback and
5445 perhaps inspire others to test hardware as well. To test, I PXE
5446 install the OS version of choice, and log in as my normal user and run
5447 a few applications and plug in selected pieces of hardware. When
5448 something fail, I make a note about this in the test matrix and move
5449 on. If I have some spare time I try to report the bug to the OS
5450 vendor, but as I only have the machines for a short time, I rarely
5451 have the time to do this for all the problems I find.&lt;/p&gt;
5452
5453 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
5454 I perform on a new model.&lt;/p&gt;
5455
5456 &lt;ul&gt;
5457
5458 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
5459 and Ubuntu Maverik at the moment. If I feel like it, I also test with
5460 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
5461
5462 &lt;li&gt;Is X.org working? If the graphical login screen show up after
5463 installation, X.org is working.&lt;/li&gt;
5464
5465 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
5466 package mesa-utils on Ubuntu) and writing down the frames per second
5467 reported by the program.&lt;/li&gt;
5468
5469 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
5470 logging in, and if I can hear this the test is successful. If there
5471 are several audio exits on the machine, I try them all and check if
5472 the Gnome/KDE audio mixer can control where to send the sound. I
5473 normally test this by playing
5474 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
5475 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
5476
5477 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
5478 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
5479
5480 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
5481 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
5482
5483 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
5484 picture from the v4l device show up.&lt;/li&gt;
5485
5486 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
5487 any bluetooth devices are discovered. In my office, I normally see a
5488 few.&lt;/li&gt;
5489
5490 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
5491 memory modules lying around, and stick them in and see if Gnome/KDE
5492 notice this.&lt;/li&gt;
5493
5494 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
5495 special button work, and if the laptop continue to work after
5496 resume.&lt;/li&gt;
5497
5498 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
5499 adjusting background light, switching on/off external video output,
5500 switching on/off wifi, bluetooth, etc? The set of buttons differ from
5501 laptop to laptop, so I just write down which are working and which are
5502 not.&lt;/li&gt;
5503
5504 &lt;li&gt;Some laptops have smart card readers, finger print readers,
5505 acceleration sensors etc. I rarely test these, as I do not know how
5506 to quickly test if they are working or not, so I only document their
5507 existence.&lt;/li&gt;
5508
5509 &lt;/ul&gt;
5510
5511 &lt;p&gt;By now I suspect you are really curious what the test results are
5512 for the HP machines I am testing. I&#39;m not done yet, so I will report
5513 the test results later. For now I can report that HP 8100 Elite work
5514 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
5515 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
5516 can see, I have most machines left to test. One interesting
5517 observation is that Ubuntu Lucid has almost twice the frame rate than
5518 RHEL6 with glxgears. No idea why.&lt;/p&gt;
5519 </description>
5520 </item>
5521
5522 <item>
5523 <title>Some thoughts on BitCoins</title>
5524 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
5525 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
5526 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
5527 <description>&lt;p&gt;As I continue to explore
5528 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
5529 what properties the system have, and how it will be affected by laws
5530 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
5531
5532 &lt;p&gt;One interesting thing to note is that since the transactions are
5533 verified using a peer to peer network, all details about a transaction
5534 is known to everyone. This means that if a BitCoin address has been
5535 published like I did with mine in my initial post about BitCoin, it is
5536 possible for everyone to see how many BitCoins have been transfered to
5537 that address. There is even a web service to look at the details for
5538 all transactions. There I can see that my address
5539 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
5540 have received 16.06 Bitcoin, the
5541 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
5542 address of Simon Phipps have received 181.97 BitCoin and the address
5543 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
5544 of EFF have received 2447.38 BitCoins so far. Thank you to each and
5545 every one of you that donated bitcoins to support my activity. The
5546 fact that anyone can see how much money was transfered to a given
5547 address make it more obvious why the BitCoin community recommend to
5548 generate and hand out a new address for each transaction. I&#39;m told
5549 there is no way to track which addresses belong to a given person or
5550 organisation without the person or organisation revealing it
5551 themselves, as Simon, EFF and I have done.&lt;/p&gt;
5552
5553 &lt;p&gt;In Norway, and in most other countries, there are laws and
5554 regulations limiting how much money one can transfer across the border
5555 without declaring it. There are money laundering, tax and accounting
5556 laws and regulations I would expect to apply to the use of BitCoin.
5557 If the Skolelinux foundation
5558 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
5559 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
5560 normal bank transfers like EFF is doing, how should this be accounted?
5561 Given that it is impossible to know if money can cross the border or
5562 not, should everything or nothing be declared? What exchange rate
5563 should be used when calculating taxes? Would receivers have to pay
5564 income tax if the foundation were to pay Skolelinux contributors in
5565 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
5566
5567 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
5568 accepted by a lot of users. It must be possible to get easy access to
5569 the currency (as a wage or using currency exchanges), and it must be
5570 easy to spend it. At the moment BitCoin seem fairly easy to get
5571 access to, but there are very few places to spend it. I am not really
5572 a regular user of any of the vendor types currently accepting BitCoin,
5573 so I wonder when my kind of shop would start accepting BitCoins. I
5574 would like to buy electronics, travels and subway tickets, not herbs
5575 and books. :) The currency is young, and this will improve over time
5576 if it become popular, but I suspect regular banks will start to lobby
5577 to get BitCoin declared illegal if it become popular. I&#39;m sure they
5578 will claim it is helping fund terrorism and money laundering (which
5579 probably would be true, as is any currency in existence), but I
5580 believe the problems should be solved elsewhere and not by blaming
5581 currencies.&lt;/p&gt;
5582
5583 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
5584 CPU intensive process that depend on a bit of luck as well (as one is
5585 competing against all the other miners currently spending CPU cycles
5586 to see which one get the next lump of cash). The &quot;winner&quot; get 50
5587 BitCoin when this happen. Yesterday I came across the obvious way to
5588 join forces to increase ones changes of getting at least some coins,
5589 by coordinating the work on mining BitCoins across several machines
5590 and people, and sharing the result if one is lucky and get the 50
5591 BitCoins. Check out
5592 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
5593 if this sounds interesting. I have not had time to try to set up a
5594 machine to participate there yet, but have seen that running on ones
5595 own for a few days have not yield any BitCoins througth mining
5596 yet.&lt;/p&gt;
5597
5598 &lt;p&gt;Update 2010-12-15: Found an &lt;a
5599 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
5600 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
5601 it was interesting to read. The arguments presented seem to be
5602 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
5603 </description>
5604 </item>
5605
5606 <item>
5607 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
5608 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
5609 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
5610 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
5611 <description>&lt;p&gt;With this weeks lawless
5612 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
5613 attacks&lt;/a&gt; on Wikileak and
5614 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
5615 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
5616 not be trusted to handle money transactions.
5617 A blog post from
5618 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
5619 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
5620 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
5621 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
5622 some help from my friend to get it all running, and he even handed me
5623 some bitcoins to get started. I even donated a few bitcoins to Simon
5624 for helping me remember BitCoin.&lt;/p&gt;
5625
5626 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
5627 crypto-currency, decentralised and handled using peer-to-peer
5628 networks. It allows anonymous transactions and prohibits central
5629 control over the transactions, making it impossible for governments
5630 and companies alike to block donations and other transactions. The
5631 source is free software, and while the key dependency wxWidgets 2.9
5632 for the graphical user interface is missing in Debian, the command
5633 line client builds just fine. Hopefully Jonas
5634 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
5635 Debian&lt;/a&gt; soon.&lt;/p&gt;
5636
5637 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
5638 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
5639 bitcoins&lt;/a&gt; when selling services and goods, and there are even
5640 currency &quot;stock&quot; markets where the exchange rate is decided. There
5641 are not many users so far, but the concept seems promising. If you
5642 want to get started and lack a friend with any bitcoins to spare,
5643 you can even get
5644 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
5645 bitcoin at the time of writing). Use
5646 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
5647 on the current exchange rates.&lt;/p&gt;
5648
5649 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
5650 machines. If you want to support my activity, please send Bitcoin
5651 donations to the address
5652 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
5653 </description>
5654 </item>
5655
5656 <item>
5657 <title>Why isn&#39;t Debian Edu using VLC?</title>
5658 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
5659 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
5660 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
5661 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
5662 presented, and the winner among the multimedia player were VLC.
5663 Personally, I like VLC, and it is my player of choice when I first try
5664 to play a video file or stream. Only if VLC fail will I drag out
5665 gmplayer to see if it can do better. The reason is mostly the failure
5666 model and trust. When VLC fail, it normally pop up a error message
5667 reporting the problem. When mplayer fail, it normally segfault or
5668 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
5669
5670 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
5671 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5672 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
5673 plugin to play web videos seamlessly, and the VLC browser plugin is
5674 not very good. For example, it lack in-line control buttons, so there
5675 is no way for the user to pause the video. Also, when I
5676 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
5677 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
5678 failed on several video pages where mplayer based plugins worked. If
5679 the browser plugin for VLC was as good as the gecko-mediaplayer
5680 package (which uses mplayer), we would switch.&lt;/P&gt;
5681
5682 &lt;p&gt;While VLC is a good player, its user interface is slightly
5683 annoying. The most annoying feature is its inconsistent use of
5684 keyboard shortcuts. When the player is in full screen mode, its
5685 shortcuts are different from when it is playing the video in a window.
5686 For example, space only work as pause when in full screen mode. I
5687 wish it had consisten shortcuts and that space also would work when in
5688 window mode. Another nice shortcut in gmplayer is [enter] to restart
5689 the current video. It is very nice when playing short videos from the
5690 web and want to restart it when new people arrive to have a look at
5691 what is going on.&lt;/p&gt;
5692 </description>
5693 </item>
5694
5695 <item>
5696 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
5697 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
5698 <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>
5699 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
5700 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
5701 upgrade testing of the
5702 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5703 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
5704 This seem like a very good idea, so I adjusted by test scripts and
5705 can now present the updated result from today:&lt;/p&gt;
5706
5707 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5708
5709 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5710
5711 &lt;blockquote&gt;&lt;p&gt;
5712 apache2.2-bin
5713 aptdaemon
5714 baobab
5715 binfmt-support
5716 browser-plugin-gnash
5717 cheese-common
5718 cli-common
5719 cups-pk-helper
5720 dmz-cursor-theme
5721 empathy
5722 empathy-common
5723 freedesktop-sound-theme
5724 freeglut3
5725 gconf-defaults-service
5726 gdm-themes
5727 gedit-plugins
5728 geoclue
5729 geoclue-hostip
5730 geoclue-localnet
5731 geoclue-manual
5732 geoclue-yahoo
5733 gnash
5734 gnash-common
5735 gnome
5736 gnome-backgrounds
5737 gnome-cards-data
5738 gnome-codec-install
5739 gnome-core
5740 gnome-desktop-environment
5741 gnome-disk-utility
5742 gnome-screenshot
5743 gnome-search-tool
5744 gnome-session-canberra
5745 gnome-system-log
5746 gnome-themes-extras
5747 gnome-themes-more
5748 gnome-user-share
5749 gstreamer0.10-fluendo-mp3
5750 gstreamer0.10-tools
5751 gtk2-engines
5752 gtk2-engines-pixbuf
5753 gtk2-engines-smooth
5754 hamster-applet
5755 libapache2-mod-dnssd
5756 libapr1
5757 libaprutil1
5758 libaprutil1-dbd-sqlite3
5759 libaprutil1-ldap
5760 libart2.0-cil
5761 libboost-date-time1.42.0
5762 libboost-python1.42.0
5763 libboost-thread1.42.0
5764 libchamplain-0.4-0
5765 libchamplain-gtk-0.4-0
5766 libcheese-gtk18
5767 libclutter-gtk-0.10-0
5768 libcryptui0
5769 libdiscid0
5770 libelf1
5771 libepc-1.0-2
5772 libepc-common
5773 libepc-ui-1.0-2
5774 libfreerdp-plugins-standard
5775 libfreerdp0
5776 libgconf2.0-cil
5777 libgdata-common
5778 libgdata7
5779 libgdu-gtk0
5780 libgee2
5781 libgeoclue0
5782 libgexiv2-0
5783 libgif4
5784 libglade2.0-cil
5785 libglib2.0-cil
5786 libgmime2.4-cil
5787 libgnome-vfs2.0-cil
5788 libgnome2.24-cil
5789 libgnomepanel2.24-cil
5790 libgpod-common
5791 libgpod4
5792 libgtk2.0-cil
5793 libgtkglext1
5794 libgtksourceview2.0-common
5795 libmono-addins-gui0.2-cil
5796 libmono-addins0.2-cil
5797 libmono-cairo2.0-cil
5798 libmono-corlib2.0-cil
5799 libmono-i18n-west2.0-cil
5800 libmono-posix2.0-cil
5801 libmono-security2.0-cil
5802 libmono-sharpzip2.84-cil
5803 libmono-system2.0-cil
5804 libmtp8
5805 libmusicbrainz3-6
5806 libndesk-dbus-glib1.0-cil
5807 libndesk-dbus1.0-cil
5808 libopal3.6.8
5809 libpolkit-gtk-1-0
5810 libpt2.6.7
5811 libpython2.6
5812 librpm1
5813 librpmio1
5814 libsdl1.2debian
5815 libsrtp0
5816 libssh-4
5817 libtelepathy-farsight0
5818 libtelepathy-glib0
5819 libtidy-0.99-0
5820 media-player-info
5821 mesa-utils
5822 mono-2.0-gac
5823 mono-gac
5824 mono-runtime
5825 nautilus-sendto
5826 nautilus-sendto-empathy
5827 p7zip-full
5828 pkg-config
5829 python-aptdaemon
5830 python-aptdaemon-gtk
5831 python-axiom
5832 python-beautifulsoup
5833 python-bugbuddy
5834 python-clientform
5835 python-coherence
5836 python-configobj
5837 python-crypto
5838 python-cupshelpers
5839 python-elementtree
5840 python-epsilon
5841 python-evolution
5842 python-feedparser
5843 python-gdata
5844 python-gdbm
5845 python-gst0.10
5846 python-gtkglext1
5847 python-gtksourceview2
5848 python-httplib2
5849 python-louie
5850 python-mako
5851 python-markupsafe
5852 python-mechanize
5853 python-nevow
5854 python-notify
5855 python-opengl
5856 python-openssl
5857 python-pam
5858 python-pkg-resources
5859 python-pyasn1
5860 python-pysqlite2
5861 python-rdflib
5862 python-serial
5863 python-tagpy
5864 python-twisted-bin
5865 python-twisted-conch
5866 python-twisted-core
5867 python-twisted-web
5868 python-utidylib
5869 python-webkit
5870 python-xdg
5871 python-zope.interface
5872 remmina
5873 remmina-plugin-data
5874 remmina-plugin-rdp
5875 remmina-plugin-vnc
5876 rhythmbox-plugin-cdrecorder
5877 rhythmbox-plugins
5878 rpm-common
5879 rpm2cpio
5880 seahorse-plugins
5881 shotwell
5882 software-center
5883 system-config-printer-udev
5884 telepathy-gabble
5885 telepathy-mission-control-5
5886 telepathy-salut
5887 tomboy
5888 totem
5889 totem-coherence
5890 totem-mozilla
5891 totem-plugins
5892 transmission-common
5893 xdg-user-dirs
5894 xdg-user-dirs-gtk
5895 xserver-xephyr
5896 &lt;/p&gt;&lt;/blockquote&gt;
5897
5898 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5899
5900 &lt;blockquote&gt;&lt;p&gt;
5901 cheese
5902 ekiga
5903 eog
5904 epiphany-extensions
5905 evolution-exchange
5906 fast-user-switch-applet
5907 file-roller
5908 gcalctool
5909 gconf-editor
5910 gdm
5911 gedit
5912 gedit-common
5913 gnome-games
5914 gnome-games-data
5915 gnome-nettool
5916 gnome-system-tools
5917 gnome-themes
5918 gnuchess
5919 gucharmap
5920 guile-1.8-libs
5921 libavahi-ui0
5922 libdmx1
5923 libgalago3
5924 libgtk-vnc-1.0-0
5925 libgtksourceview2.0-0
5926 liblircclient0
5927 libsdl1.2debian-alsa
5928 libspeexdsp1
5929 libsvga1
5930 rhythmbox
5931 seahorse
5932 sound-juicer
5933 system-config-printer
5934 totem-common
5935 transmission-gtk
5936 vinagre
5937 vino
5938 &lt;/p&gt;&lt;/blockquote&gt;
5939
5940 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5941
5942 &lt;blockquote&gt;&lt;p&gt;
5943 gstreamer0.10-gnomevfs
5944 &lt;/p&gt;&lt;/blockquote&gt;
5945
5946 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5947
5948 &lt;blockquote&gt;&lt;p&gt;
5949 [nothing]
5950 &lt;/p&gt;&lt;/blockquote&gt;
5951
5952 &lt;p&gt;This is for KDE:&lt;/p&gt;
5953
5954 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5955
5956 &lt;blockquote&gt;&lt;p&gt;
5957 ksmserver
5958 &lt;/p&gt;&lt;/blockquote&gt;
5959
5960 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5961
5962 &lt;blockquote&gt;&lt;p&gt;
5963 kwin
5964 network-manager-kde
5965 &lt;/p&gt;&lt;/blockquote&gt;
5966
5967 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5968
5969 &lt;blockquote&gt;&lt;p&gt;
5970 arts
5971 dolphin
5972 freespacenotifier
5973 google-gadgets-gst
5974 google-gadgets-xul
5975 kappfinder
5976 kcalc
5977 kcharselect
5978 kde-core
5979 kde-plasma-desktop
5980 kde-standard
5981 kde-window-manager
5982 kdeartwork
5983 kdeartwork-emoticons
5984 kdeartwork-style
5985 kdeartwork-theme-icon
5986 kdebase
5987 kdebase-apps
5988 kdebase-workspace
5989 kdebase-workspace-bin
5990 kdebase-workspace-data
5991 kdeeject
5992 kdelibs
5993 kdeplasma-addons
5994 kdeutils
5995 kdewallpapers
5996 kdf
5997 kfloppy
5998 kgpg
5999 khelpcenter4
6000 kinfocenter
6001 konq-plugins-l10n
6002 konqueror-nsplugins
6003 kscreensaver
6004 kscreensaver-xsavers
6005 ktimer
6006 kwrite
6007 libgle3
6008 libkde4-ruby1.8
6009 libkonq5
6010 libkonq5-templates
6011 libnetpbm10
6012 libplasma-ruby
6013 libplasma-ruby1.8
6014 libqt4-ruby1.8
6015 marble-data
6016 marble-plugins
6017 netpbm
6018 nuvola-icon-theme
6019 plasma-dataengines-workspace
6020 plasma-desktop
6021 plasma-desktopthemes-artwork
6022 plasma-runners-addons
6023 plasma-scriptengine-googlegadgets
6024 plasma-scriptengine-python
6025 plasma-scriptengine-qedje
6026 plasma-scriptengine-ruby
6027 plasma-scriptengine-webkit
6028 plasma-scriptengines
6029 plasma-wallpapers-addons
6030 plasma-widget-folderview
6031 plasma-widget-networkmanagement
6032 ruby
6033 sweeper
6034 update-notifier-kde
6035 xscreensaver-data-extra
6036 xscreensaver-gl
6037 xscreensaver-gl-extra
6038 xscreensaver-screensaver-bsod
6039 &lt;/p&gt;&lt;/blockquote&gt;
6040
6041 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6042
6043 &lt;blockquote&gt;&lt;p&gt;
6044 ark
6045 google-gadgets-common
6046 google-gadgets-qt
6047 htdig
6048 kate
6049 kdebase-bin
6050 kdebase-data
6051 kdepasswd
6052 kfind
6053 klipper
6054 konq-plugins
6055 konqueror
6056 ksysguard
6057 ksysguardd
6058 libarchive1
6059 libcln6
6060 libeet1
6061 libeina-svn-06
6062 libggadget-1.0-0b
6063 libggadget-qt-1.0-0b
6064 libgps19
6065 libkdecorations4
6066 libkephal4
6067 libkonq4
6068 libkonqsidebarplugin4a
6069 libkscreensaver5
6070 libksgrd4
6071 libksignalplotter4
6072 libkunitconversion4
6073 libkwineffects1a
6074 libmarblewidget4
6075 libntrack-qt4-1
6076 libntrack0
6077 libplasma-geolocation-interface4
6078 libplasmaclock4a
6079 libplasmagenericshell4
6080 libprocesscore4a
6081 libprocessui4a
6082 libqalculate5
6083 libqedje0a
6084 libqtruby4shared2
6085 libqzion0a
6086 libruby1.8
6087 libscim8c2a
6088 libsmokekdecore4-3
6089 libsmokekdeui4-3
6090 libsmokekfile3
6091 libsmokekhtml3
6092 libsmokekio3
6093 libsmokeknewstuff2-3
6094 libsmokeknewstuff3-3
6095 libsmokekparts3
6096 libsmokektexteditor3
6097 libsmokekutils3
6098 libsmokenepomuk3
6099 libsmokephonon3
6100 libsmokeplasma3
6101 libsmokeqtcore4-3
6102 libsmokeqtdbus4-3
6103 libsmokeqtgui4-3
6104 libsmokeqtnetwork4-3
6105 libsmokeqtopengl4-3
6106 libsmokeqtscript4-3
6107 libsmokeqtsql4-3
6108 libsmokeqtsvg4-3
6109 libsmokeqttest4-3
6110 libsmokeqtuitools4-3
6111 libsmokeqtwebkit4-3
6112 libsmokeqtxml4-3
6113 libsmokesolid3
6114 libsmokesoprano3
6115 libtaskmanager4a
6116 libtidy-0.99-0
6117 libweather-ion4a
6118 libxklavier16
6119 libxxf86misc1
6120 okteta
6121 oxygencursors
6122 plasma-dataengines-addons
6123 plasma-scriptengine-superkaramba
6124 plasma-widget-lancelot
6125 plasma-widgets-addons
6126 plasma-widgets-workspace
6127 polkit-kde-1
6128 ruby1.8
6129 systemsettings
6130 update-notifier-common
6131 &lt;/p&gt;&lt;/blockquote&gt;
6132
6133 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
6134 aptitude a bit more similar, but there are still quite a lott of
6135 differences. I have no idea what packages should be installed after
6136 the upgrade, but hope those that do can have a look.&lt;/p&gt;
6137 </description>
6138 </item>
6139
6140 <item>
6141 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
6142 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
6143 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
6144 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
6145 <description>&lt;p&gt;Most of the computers in use by the
6146 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
6147 are virtual machines. And they have been Xen machines running on a
6148 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
6149 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
6150 bit harder that it could have been, because we set up the Xen virtual
6151 machines to get the virtual partitions from LVM, which as far as I
6152 know is not supported by KVM. So to migrate, we had to convert
6153 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
6154
6155 &lt;p&gt;I found
6156 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
6157 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
6158 migration. It uses qemu-img from the qemu package to make the disk
6159 image, parted to partition it, losetup and kpartx to present the disk
6160 image partions as devices, and dd to copy the data. I NFS mounted the
6161 new servers storage area on the old server to do the migration.&lt;/p&gt;
6162
6163 &lt;pre&gt;
6164 #!/bin/sh
6165
6166 # Based on
6167 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6168
6169 set -e
6170 set -x
6171
6172 if [ -z &quot;$1&quot; ] ; then
6173 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
6174 exit 1
6175 else
6176 host=&quot;$1&quot;
6177 fi
6178
6179 if [ ! -e /dev/vg_data/$host-disk ] ; then
6180 echo &quot;error: unable to find LVM volume for $host&quot;
6181 exit 1
6182 fi
6183
6184 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6185 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6186 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6187 totalsize=$(( ( $disksize + $swapsize ) ))
6188
6189 img=$host.img
6190 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
6191 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6192
6193 parted $img mklabel msdos
6194 parted $img mkpart primary linux-swap 0 $disksize
6195 parted $img mkpart primary ext2 $disksize $totalsize
6196 parted $img set 1 boot on
6197
6198 modprobe dm-mod
6199 losetup /dev/loop0 $img
6200 kpartx -a /dev/loop0
6201
6202 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
6203 fsck.ext3 -f /dev/mapper/loop0p1 || true
6204 mkswap /dev/mapper/loop0p2
6205
6206 kpartx -d /dev/loop0
6207 losetup -d /dev/loop0
6208 &lt;/pre&gt;
6209
6210 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
6211 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
6212
6213 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
6214 the new disk image attached, installed grub-pc and linux-image-686 and
6215 set up grub to boot from the disk image. After this, the KVM machines
6216 seem to work just fine.&lt;/p&gt;
6217 </description>
6218 </item>
6219
6220 <item>
6221 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
6222 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
6223 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
6224 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
6225 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
6226 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6227 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
6228 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
6229
6230 &lt;p&gt;I still do not know what a correct migration should look like, so I
6231 report any differences between apt and aptitude and hope someone else
6232 can see if anything should be changed.&lt;/p&gt;
6233
6234 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6235
6236 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6237
6238 &lt;blockquote&gt;&lt;p&gt;
6239 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6240 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
6241 dmz-cursor-theme empathy empathy-common finger
6242 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6243 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6244 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6245 gnome-cards-data gnome-codec-install gnome-core
6246 gnome-desktop-environment gnome-disk-utility gnome-screenshot
6247 gnome-search-tool gnome-session-canberra gnome-spell
6248 gnome-system-log gnome-themes-extras gnome-themes-more
6249 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
6250 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
6251 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
6252 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
6253 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
6254 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
6255 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
6256 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
6257 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
6258 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
6259 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
6260 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
6261 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
6262 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
6263 libgtk2.0-cil libgtkglext1 libgtksourceview-common
6264 libgtksourceview2.0-common libmono-addins-gui0.2-cil
6265 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
6266 libmono-i18n-west2.0-cil libmono-posix2.0-cil
6267 libmono-security2.0-cil libmono-sharpzip2.84-cil
6268 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
6269 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
6270 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
6271 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
6272 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
6273 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
6274 libxalan2-java libxerces2-java media-player-info mesa-utils
6275 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
6276 nautilus-sendto-empathy openoffice.org-writer2latex
6277 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
6278 python-aptdaemon python-aptdaemon-gtk python-axiom
6279 python-beautifulsoup python-bugbuddy python-clientform
6280 python-coherence python-configobj python-crypto python-cupshelpers
6281 python-cupsutils python-eggtrayicon python-elementtree
6282 python-epsilon python-evolution python-feedparser python-gdata
6283 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
6284 python-gtksourceview2 python-httplib2 python-louie python-mako
6285 python-markupsafe python-mechanize python-nevow python-notify
6286 python-opengl python-openssl python-pam python-pkg-resources
6287 python-pyasn1 python-pysqlite2 python-rdflib python-serial
6288 python-tagpy python-twisted-bin python-twisted-conch
6289 python-twisted-core python-twisted-web python-utidylib python-webkit
6290 python-xdg python-zope.interface remmina remmina-plugin-data
6291 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
6292 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
6293 software-center svgalibg1 system-config-printer-udev
6294 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
6295 totem totem-coherence totem-mozilla totem-plugins
6296 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
6297 zip
6298 &lt;/p&gt;&lt;/blockquote&gt;
6299
6300 Installed using apt-get, removed with aptitude
6301
6302 &lt;blockquote&gt;&lt;p&gt;
6303 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
6304 epiphany-extensions epiphany-gecko evolution-exchange
6305 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
6306 gedit-common gnome-app-install gnome-games gnome-games-data
6307 gnome-nettool gnome-system-tools gnome-themes gnome-utils
6308 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
6309 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
6310 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
6311 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
6312 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
6313 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
6314 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6315 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6316 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6317 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
6318 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
6319 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
6320 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
6321 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
6322 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
6323 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
6324 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
6325 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
6326 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
6327 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
6328 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
6329 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
6330 sound-juicer swfdec-gnome system-config-printer totem-common
6331 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
6332 &lt;/p&gt;&lt;/blockquote&gt;
6333
6334 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6335
6336 &lt;blockquote&gt;&lt;p&gt;
6337 gstreamer0.10-gnomevfs
6338 &lt;/p&gt;&lt;/blockquote&gt;
6339
6340 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6341
6342 &lt;blockquote&gt;&lt;p&gt;
6343 [nothing]
6344 &lt;/p&gt;&lt;/blockquote&gt;
6345
6346 &lt;p&gt;This is for KDE:&lt;/p&gt;
6347
6348 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6349
6350 &lt;blockquote&gt;&lt;p&gt;
6351 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
6352 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
6353 ghostscript-x git gnome-audio gnugo granatier gs-common
6354 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
6355 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
6356 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
6357 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6358 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
6359 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
6360 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6361 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
6362 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
6363 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
6364 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
6365 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
6366 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
6367 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
6368 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
6369 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
6370 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
6371 libkrossui4 libmailtools-perl libmime-tools-perl
6372 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
6373 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
6374 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
6375 lirc luatex marble networkstatus noatun-plugins
6376 openoffice.org-writer2latex palapeli palapeli-data parley
6377 parley-data poster psutils pulseaudio pulseaudio-esound-compat
6378 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
6379 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
6380 ttf-sazanami-gothic
6381 &lt;/p&gt;&lt;/blockquote&gt;
6382
6383 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6384
6385 &lt;blockquote&gt;&lt;p&gt;
6386 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
6387 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
6388 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
6389 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
6390 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
6391 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
6392 kitchensync kiten kjumpingcube klatin klettres klickety klines
6393 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
6394 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
6395 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
6396 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
6397 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
6398 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
6399 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
6400 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
6401 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6402 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
6403 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
6404 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6405 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
6406 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
6407 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
6408 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
6409 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6410 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
6411 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
6412 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
6413 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
6414 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
6415 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
6416 mpeglib network-manager-kde noatun pmount tex-common texlive-base
6417 texlive-common texlive-doc-base texlive-fonts-recommended tidy
6418 ttf-dustin ttf-kochi-gothic ttf-sjfonts
6419 &lt;/p&gt;&lt;/blockquote&gt;
6420
6421 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6422
6423 &lt;blockquote&gt;&lt;p&gt;
6424 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
6425 kdeartwork kdebase kdebase-apps kdebase-workspace
6426 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
6427 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
6428 netpbm plasma-widget-folderview plasma-widget-networkmanagement
6429 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
6430 xscreensaver-screensaver-bsod
6431 &lt;/p&gt;&lt;/blockquote&gt;
6432
6433 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6434
6435 &lt;blockquote&gt;&lt;p&gt;
6436 kdebase-bin konq-plugins konqueror
6437 &lt;/p&gt;&lt;/blockquote&gt;
6438 </description>
6439 </item>
6440
6441 <item>
6442 <title>Gnash buildbot slave and Debian kfreebsd</title>
6443 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
6444 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
6445 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
6446 <description>&lt;p&gt;Answering
6447 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
6448 call from the Gnash project&lt;/a&gt; for
6449 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
6450 current source, I have set up a virtual KVM machine on the Debian
6451 Edu/Skolelinux virtualization host to test the git source on
6452 Debian/Squeeze. I hope this can help the developers in getting new
6453 releases out more often.&lt;/p&gt;
6454
6455 &lt;p&gt;As the developers want less main-stream build platforms tested to,
6456 I have considered setting up a &lt;a
6457 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
6458 machine as well. I have also considered using the kfreebsd
6459 architecture in Debian as a file server in NUUG to get access to the 5
6460 TB zfs volume we currently use to store DV video. Because of this, I
6461 finally got around to do a test installation of Debian/Squeeze with
6462 kfreebsd. Installation went fairly smooth, thought I noticed some
6463 visual glitches in the cdebconf dialogs (black cursor left on the
6464 screen at random locations). Have not gotten very far with the
6465 testing. Noticed cfdisk did not work, but fdisk did so it was not a
6466 fatal problem. Have to spend some more time on it to see if it is
6467 useful as a file server for NUUG. Will try to find time to set up a
6468 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
6469 </description>
6470 </item>
6471
6472 <item>
6473 <title>Debian in 3D</title>
6474 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
6475 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
6476 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
6477 <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;
6478
6479 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
6480 3D linked in from
6481 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
6482 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
6483 </description>
6484 </item>
6485
6486 <item>
6487 <title>Software updates 2010-10-24</title>
6488 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
6489 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
6490 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
6491 <description>&lt;p&gt;Some updates.&lt;/p&gt;
6492
6493 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
6494 raise money for the project is going well. The lower limit of 10
6495 signers was reached in 24 hours, and so far 13 people have signed it.
6496 More signers and more funding is most welcome, and I am really curious
6497 how far we can get before the time limit of December 24 is reached.
6498 :)&lt;/p&gt;
6499
6500 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
6501 about what appear to be a great code coverage tool capable of
6502 generating code coverage stats without any changes to the source code.
6503 It is called
6504 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
6505 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
6506 It is missing in Debian, but the git source built just fine in Squeeze
6507 after I installed libelf-dev, libdwarf-dev, pkg-config and
6508 libglib2.0-dev. Failed to build in Lenny, but suspect that is
6509 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
6510
6511 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
6512 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
6513 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
6514 alpha test release of the Squeeze based Debian Edu /
6515 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
6516 release. Give it a try if you need a complete linux solution for your
6517 school, including central infrastructure server, workstations, thin
6518 client servers and diskless workstations. A nice touch added
6519 yesterday is RDP support on the thin client servers, for windows
6520 clients to get a Linux desktop on request.&lt;/p&gt;
6521 </description>
6522 </item>
6523
6524 <item>
6525 <title>Some notes on Flash in Debian and Debian Edu</title>
6526 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
6527 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
6528 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
6529 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
6530 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
6531 second most popular used package that is missing in Debian. The sixth
6532 most popular is flashplayer-mozilla. This is a clear indication that
6533 working flash is important for Debian users. Around 10 percent of the
6534 users submitting data to popcon.debian.org have this package
6535 installed.&lt;/p&gt;
6536
6537 &lt;p&gt;In the report written by Lars Risan in August 2008
6538&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
6539 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
6540 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
6541 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6542 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
6543 web sites require Flash to work, and lacking working Flash support in
6544 the web browser and the problems with installing it was perceived as a
6545 good reason to stay with Windows.&lt;/p&gt;
6546
6547 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
6548 said to be the retarded cousin that did not really understand
6549 everything you told him but could work fairly well. This was a
6550 comment regarding the problems Linux have with proprietary formats and
6551 non-standard web pages, and is sad because it exposes a fairly common
6552 understanding of whose fault it is if web pages that only work in for
6553 example Internet Explorer 6 fail to work on Firefox, and funny because
6554 it explain very well how annoying it is for users when Linux
6555 distributions do not work with the documents they receive or the web
6556 pages they want to visit.&lt;/p&gt;
6557
6558 &lt;p&gt;This is part of the reason why I believe it is important for Debian
6559 and Debian Edu to have a well working Flash implementation in the
6560 distribution, to get at least popular sites as Youtube and Google
6561 Video to working out of the box. For Squeeze, Debian have the chance
6562 to include the latest version of Gnash that will make this happen, as
6563 the new release 0.8.8 was published a few weeks ago and is resting in
6564 unstable. The new version work with more sites that version 0.8.7.
6565 The Gnash maintainers have asked for a freeze exception, but the
6566 release team have not had time to reply to it yet. I hope they agree
6567 with me that Flash is important for the Debian desktop users, and thus
6568 accept the new package into Squeeze.&lt;/p&gt;
6569 </description>
6570 </item>
6571
6572 <item>
6573 <title>Circular package dependencies harms apt recovery</title>
6574 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
6575 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
6576 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
6577 <description>&lt;p&gt;I discovered this while doing
6578 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
6579 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
6580 in Debian still got circular dependencies, and it is often claimed
6581 that apt and aptitude should be able to handle this just fine, but
6582 some times these dependency loops causes apt to fail.&lt;/p&gt;
6583
6584 &lt;p&gt;An example is from todays
6585 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
6586 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
6587 causes perl-modules to fail to upgrade. The cause is simple. If a
6588 package fail to unpack, then only part of packages with the circular
6589 dependency might end up being unpacked when unpacking aborts, and the
6590 ones already unpacked will fail to configure in the recovery phase
6591 because its dependencies are unavailable.&lt;/p&gt;
6592
6593 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
6594
6595 &lt;blockquote&gt;&lt;pre&gt;
6596 dpkg: dependency problems prevent configuration of perl-modules:
6597 perl-modules depends on perl (&gt;= 5.10.1-1); however:
6598 Version of perl on system is 5.10.0-19lenny2.
6599 dpkg: error processing perl-modules (--configure):
6600 dependency problems - leaving unconfigured
6601 &lt;/pre&gt;&lt;/blockquote&gt;
6602
6603 &lt;p&gt;The perl/perl-modules circular dependency is already
6604 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
6605 hopefully be solved as soon as possible, but it is not the only one,
6606 and each one of these loops in the dependency tree can cause similar
6607 failures. Of course, they only occur when there are bugs in other
6608 packages causing the unpacking to fail, but it is rather nasty when
6609 the failure of one package causes the problem to become worse because
6610 of dependency loops.&lt;/p&gt;
6611
6612 &lt;p&gt;Thanks to
6613 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
6614 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
6615 dependencies
6616 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
6617 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
6618
6619 &lt;p&gt;Todays testing also exposed a bug in
6620 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
6621 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
6622 apt-get and aptitude, the latter possibly caused by some circular
6623 dependency. Reported both to BTS to try to get someone to look at
6624 it.&lt;/p&gt;
6625 </description>
6626 </item>
6627
6628 <item>
6629 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
6630 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
6631 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
6632 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
6633 <description>&lt;p&gt;This is a
6634 &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;
6635 on my
6636 &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
6637 work&lt;/a&gt; on
6638 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
6639 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
6640
6641 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
6642 LDAP objects, I have had a look at how the packages pdns-backend-ldap
6643 and dhcp3-server-ldap in Debian use the LDAP server. The two
6644 implementations are quite different in how they use LDAP.&lt;/p&gt;
6645
6646 To get this information, I started slapd with debugging enabled and
6647 dumped the debug output to a file to get the LDAP searches performed
6648 on a Debian Edu main-server. Here is a summary.
6649
6650 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
6651
6652 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
6653 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
6654 the web.
6655
6656 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
6657 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
6658 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
6659 reverse entries are in two different subtrees in LDAP with a structure
6660 based on the DNS names, as in tjener.intern and
6661 2.2.0.10.in-addr.arpa.&lt;/p&gt;
6662
6663 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
6664 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
6665 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
6666 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
6667 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
6668 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
6669 forward entries, it is looking for attributes named dnsttl, arecord,
6670 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
6671 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
6672 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
6673 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
6674 spfrecord and modifytimestamp. For reverse entries it is looking for
6675 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
6676 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
6677 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
6678 ldapsearch commands could look like this:&lt;/p&gt;
6679
6680 &lt;blockquote&gt;&lt;pre&gt;
6681 ldapsearch -h ldap \
6682 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6683 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6684 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6685 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6686 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6687 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6688
6689 ldapsearch -h ldap \
6690 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
6691 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
6692 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
6693 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
6694 srvrecord naptrrecord modifytimestamp
6695 &lt;/pre&gt;&lt;/blockquote&gt;
6696
6697 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
6698 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
6699 example LDAP objects used there. In addition to these objects, the
6700 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
6701 also exist.&lt;/p&gt;
6702
6703 &lt;blockquote&gt;&lt;pre&gt;
6704 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
6705 objectclass: top
6706 objectclass: dnsdomain
6707 objectclass: domainrelatedobject
6708 dc: tjener
6709 arecord: 10.0.2.2
6710 associateddomain: tjener.intern
6711
6712 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
6713 objectclass: top
6714 objectclass: dnsdomain2
6715 objectclass: domainrelatedobject
6716 dc: 2
6717 ptrrecord: tjener.intern
6718 associateddomain: 2.2.0.10.in-addr.arpa
6719 &lt;/pre&gt;&lt;/blockquote&gt;
6720
6721 &lt;p&gt;In strict mode, the server behaves differently. When looking for
6722 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
6723 same base as in the tree mode for a object with filter
6724 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
6725 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
6726 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
6727 naptrrecord and modifytimestamp. For reverse entires it also do a
6728 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
6729 and the requested attributes are associateddomain, dnsttl and
6730 modifytimestamp. In short, in strict mode the objects with ptrrecord
6731 go away, and the arecord attribute in the forward object is used
6732 instead.&lt;/p&gt;
6733
6734 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
6735 like this:&lt;/p&gt;
6736
6737 &lt;blockquote&gt;&lt;pre&gt;
6738 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6739 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
6740 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
6741 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
6742 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
6743 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
6744
6745 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
6746 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
6747 &lt;/pre&gt;&lt;/blockquote&gt;
6748
6749 &lt;p&gt;In addition to the forward and reverse searches , there is also a
6750 search for SOA records, which behave similar to the forward and
6751 reverse lookups.&lt;/p&gt;
6752
6753 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
6754 specify any objectclass names, and instead look for the attributes it
6755 need to generate a DNS reply. This make it able to work with any
6756 objectclass that provide the needed attributes.&lt;/p&gt;
6757
6758 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
6759 dnsdomain2 schemas. The latter is used for reverse entries like
6760 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
6761
6762 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
6763 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
6764 attributes) and domainrelatedobject (for associatedDomain). The use
6765 of structural object classes make it impossible to combine these
6766 classes with the object classes used by DHCP.&lt;/p&gt;
6767
6768 &lt;p&gt;There are other schemas that could be used too, for example the
6769 dnszone structural object class used by Gosa and bind-sdb for the DNS
6770 attributes combined with the domainrelatedobject object class, but in
6771 this case some unused attributes would have to be included as well
6772 (zonename and relativedomainname).&lt;/p&gt;
6773
6774 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
6775 mode and not use any of the existing objectclasses (dnsdomain,
6776 dnsdomain2 and dnszone) when one want to combine the DNS information
6777 with DHCP information, and instead create a auxiliary object class
6778 defined something like this (using the attributes defined for
6779 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
6780
6781 &lt;blockquote&gt;&lt;pre&gt;
6782 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
6783 SUP top
6784 AUXILIARY
6785 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
6786 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
6787 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
6788 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
6789 A6Record $ DNAMERecord
6790 ))
6791 &lt;/pre&gt;&lt;/blockquote&gt;
6792
6793 &lt;p&gt;This will allow any object to become a DNS entry when combined with
6794 the domainrelatedobject object class, and allow any entity to include
6795 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
6796 developers asking for their view on this schema and if they are
6797 interested in providing such schema with PowerDNS, and I hope my
6798 message will be accepted into their mailing list soon.&lt;/p&gt;
6799
6800 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
6801
6802 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
6803 the object attributes, and then uses the attributes it want. This
6804 make it harder to figure out exactly what attributes are used, but
6805 thanks to the working example in Debian Edu I can at least get an idea
6806 what is needed without having to read the source code.&lt;/p&gt;
6807
6808 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
6809 search filter to use to locate the correct dhcpServer entity is
6810 stored. These are the relevant entries from
6811 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
6812
6813 &lt;blockquote&gt;&lt;pre&gt;
6814 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
6815 ldap-dhcp-server-cn &quot;dhcp&quot;;
6816 &lt;/pre&gt;&lt;/blockquote&gt;
6817
6818 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
6819 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
6820 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
6821 search result is this entry:&lt;/p&gt;
6822
6823 &lt;blockquote&gt;&lt;pre&gt;
6824 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
6825 cn: dhcp
6826 objectClass: top
6827 objectClass: dhcpServer
6828 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6829 &lt;/pre&gt;&lt;/blockquote&gt;
6830
6831 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
6832 subtree with DHCP configuration. The DHCP configuration subtree base
6833 is located using a base scope search with base &quot;cn=DHCP
6834 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
6835 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
6836 The search result is this entry:&lt;/p&gt;
6837
6838 &lt;blockquote&gt;&lt;pre&gt;
6839 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6840 cn: DHCP Config
6841 objectClass: top
6842 objectClass: dhcpService
6843 objectClass: dhcpOptions
6844 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
6845 dhcpStatements: ddns-update-style none
6846 dhcpStatements: authoritative
6847 dhcpOption: smtp-server code 69 = array of ip-address
6848 dhcpOption: www-server code 72 = array of ip-address
6849 dhcpOption: wpad-url code 252 = text
6850 &lt;/pre&gt;&lt;/blockquote&gt;
6851
6852 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
6853 all the DHCP configuration is loaded, it is ready to receive requests.
6854 The subtree in Debian Edu contain objects with object classes
6855 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
6856 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
6857 and information about netmasks, dynamic range etc. Leaving out the
6858 details here because it is not relevant for the focus of my
6859 investigation, which is to see if it is possible to merge dns and dhcp
6860 related computer objects.&lt;/p&gt;
6861
6862 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
6863 of the client (00:00:00:00:00:00 in this example), using a subtree
6864 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
6865 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
6866 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
6867 like:&lt;/p&gt;
6868
6869 &lt;blockquote&gt;&lt;pre&gt;
6870 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6871 cn: hostname
6872 objectClass: top
6873 objectClass: dhcpHost
6874 dhcpHWAddress: ethernet 00:00:00:00:00:00
6875 dhcpStatements: fixed-address hostname
6876 &lt;/pre&gt;&lt;/blockquote&gt;
6877
6878 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
6879 The object classes need to have fixed names, and the configuration
6880 need to be stored in a fairly specific LDAP structure. On the
6881 positive side, the invidiual dhcpHost entires can be anywhere without
6882 the DN pointed to by the dhcpServer entries. The latter should make
6883 it possible to group all host entries in a subtree next to the
6884 configuration entries, and this subtree can also be shared with the
6885 DNS server if the schema proposed above is combined with the dhcpHost
6886 structural object class.
6887
6888 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
6889
6890 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
6891 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
6892 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
6893 allowing DNS objects to be stored anywhere under the base cn specified
6894 in the configuration.&lt;/p&gt;
6895
6896 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
6897 regarding which LDAP schemas to use and which LDAP structure to use.
6898 I guess one could implement ones own schema, as long as the
6899 objectclasses and attributes have the names used, but this do not
6900 really help when the DHCP subtree need to have a fairly fixed
6901 structure.&lt;/p&gt;
6902
6903 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
6904 this might work for Debian Edu:&lt;/p&gt;
6905
6906 &lt;blockquote&gt;&lt;pre&gt;
6907 ou=services
6908 cn=machine-info (dhcpService) - dhcpServiceDN points here
6909 cn=dhcp (dhcpServer)
6910 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
6911 cn=10.0.2.0 (dhcpSubnet)
6912 cn=group1 (dhcpGroup/dhcpOptions)
6913 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
6914 cn=192.168.0.0 (dhcpSubnet)
6915 cn=group1 (dhcpGroup/dhcpOptions)
6916 ou=machines - PowerDNS base points here
6917 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
6918 &lt;/pre&gt;&lt;/blockquote&gt;
6919
6920 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
6921 entries to be in the dhcpGroup subtrees, the entries can be stored
6922 there instead of a common machines subtree, and the PowerDNS base
6923 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
6924
6925 &lt;p&gt;The combined object under the machines subtree would look something
6926 like this:&lt;/p&gt;
6927
6928 &lt;blockquote&gt;&lt;pre&gt;
6929 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
6930 dc: hostname
6931 objectClass: top
6932 objectClass: dhcpHost
6933 objectclass: domainrelatedobject
6934 objectclass: dnsDomainAux
6935 associateddomain: hostname.intern
6936 arecord: 10.11.12.13
6937 dhcpHWAddress: ethernet 00:00:00:00:00:00
6938 dhcpStatements: fixed-address hostname.intern
6939 &lt;/pre&gt;&lt;/blockquote&gt;
6940
6941 &lt;/p&gt;One could even add the LTSP configuration associated with a given
6942 machine, as long as the required attributes are available in a
6943 auxiliary object class.&lt;/p&gt;
6944 </description>
6945 </item>
6946
6947 <item>
6948 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
6949 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
6950 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
6951 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
6952 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
6953 DHCP services in Debian Edu to use the same LDAP objects for a given
6954 computer, to avoid the possibility of having a inconsistent state for
6955 a computer in LDAP (as in DHCP but no DNS entry or the other way
6956 around) and make it easier to add computers to LDAP.&lt;/p&gt;
6957
6958 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
6959 information finally found a solution that seem to work.&lt;/p&gt;
6960
6961 &lt;p&gt;The old setup required three LDAP objects for a given computer.
6962 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
6963 we switch powerdns to use its strict LDAP method (ldap-method=strict
6964 in pdns-debian-edu.conf), the forward and reverse DNS entries are
6965 merged into one while making it impossible to transfer the reverse map
6966 to a slave DNS server.&lt;/p&gt;
6967
6968 &lt;p&gt;If we also replace the object class used to get the DNS related
6969 attributes to one allowing these attributes to be combined with the
6970 dhcphost object class, we can merge the DNS and DHCP entries into one.
6971 I&#39;ve written such object class in the dnsdomainaux.schema file (need
6972 proper OIDs, but that is a minor issue), and tested the setup. It
6973 seem to work.&lt;/p&gt;
6974
6975 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
6976 for both DNS and DHCP, and even the LTSP configuration I suggested in
6977 an earlier email. The combined LDAP object will look something like
6978 this:&lt;/p&gt;
6979
6980 &lt;blockquote&gt;&lt;pre&gt;
6981 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
6982 cn: hostname
6983 objectClass: dhcphost
6984 objectclass: domainrelatedobject
6985 objectclass: dnsdomainaux
6986 associateddomain: hostname.intern
6987 arecord: 10.11.12.13
6988 dhcphwaddress: ethernet 00:00:00:00:00:00
6989 dhcpstatements: fixed-address hostname
6990 ldapconfigsound: Y
6991 &lt;/pre&gt;&lt;/blockquote&gt;
6992
6993 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
6994 the DHCP server uses the dhcphwaddress and dhcpstatements entries
6995 before asking DNS to resolve the fixed-adddress. LTSP will use
6996 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
6997
6998 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
6999 dhcphost in a different location, to allow us to put the objects
7000 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
7001 that. If I can&#39;t figure out a way to do that, we can still get rid of
7002 the hosts subtree and move all its content into the DHCP Config tree
7003 (which probably should be renamed to be more related to the new
7004 content. I suspect cn=dnsdhcp,ou=services or something like that
7005 might be a good place to put it.&lt;/p&gt;
7006
7007 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7008 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7009 </description>
7010 </item>
7011
7012 <item>
7013 <title>Idea for storing LTSP configuration in LDAP</title>
7014 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
7015 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
7016 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
7017 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
7018 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7019 clients, and that this can be used to fetch configuration from LDAP if
7020 Debian Edu choose to store configuration there.&lt;/p&gt;
7021
7022 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
7023 to get configuration from LDAP. The idea is to look up the MAC
7024 address of the client in LDAP, and look for attributes on the form
7025 ltspconfigsetting=value, and use this to export SETTING=value to the
7026 LTSP clients.&lt;/p&gt;
7027
7028 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
7029 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
7030 allowing us to store all information about a computer in one place.&lt;/p&gt;
7031
7032 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
7033 this approach. A real LDAP schema for the ltspClientAux objectclass
7034 need to be written. Comments, suggestions, etc?&lt;/p&gt;
7035
7036 &lt;blockquote&gt;&lt;pre&gt;
7037 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7038 #
7039 # Fetch LTSP client settings from LDAP based on MAC address
7040 #
7041 # Uses ethernet address as stored in the dhcpHost objectclass using
7042 # the dhcpHWAddress attribute or ethernet address stored in the
7043 # ieee802Device objectclass with the macAddress attribute.
7044 #
7045 # This module is written to be schema agnostic, and only depend on the
7046 # existence of attribute names.
7047 #
7048 # The LTSP configuration variables are saved directly using a
7049 # ltspConfig prefix and uppercasing the rest of the attribute name.
7050 # To set the SERVER variable, set the ltspConfigServer attribute.
7051 #
7052 # Some LDAP schema should be created with all the relevant
7053 # configuration settings. Something like this should work:
7054 #
7055 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
7056 # SUP top
7057 # AUXILIARY
7058 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7059
7060 LDAPSERVER=$(debian-edu-ldapserver)
7061 if [ &quot;$LDAPSERVER&quot; ] ; then
7062 LDAPBASE=$(debian-edu-ldapserver -b)
7063 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
7064 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
7065 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
7066 grep &#39;^ltspConfig&#39; | while read attr value ; do
7067 # Remove prefix and convert to upper case
7068 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
7069 # bass value on to clients
7070 eval &quot;$attr=$value; export $attr&quot;
7071 done
7072 done
7073 fi
7074 &lt;/pre&gt;&lt;/blockquote&gt;
7075
7076 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
7077 the while block might end up in a subshell causing the variables set
7078 there to not show up in ltsp-config, but if that is the case I am sure
7079 the code can be restructured to make sure the variables are passed on.
7080 I expect that can be solved with some testing. :)&lt;/p&gt;
7081
7082 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7083 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7084
7085 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
7086 configuration in LDAP that was created around year 2000 by
7087 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
7088 Xperience, Inc., 2000&lt;/a&gt;. I found its
7089 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
7090 personal home page over at redhat.com.&lt;/p&gt;
7091 </description>
7092 </item>
7093
7094 <item>
7095 <title>jXplorer, a very nice LDAP GUI</title>
7096 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
7097 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
7098 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
7099 <description>&lt;p&gt;Since
7100 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
7101 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
7102 LDAP GUI that is even better than luma. The java application
7103 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
7104 moving LDAP objects and subtrees using drag-and-drop, and can
7105 authenticate using Kerberos. I have only tested the Kerberos
7106 authentication, but do not have a LDAP setup allowing me to rewrite
7107 LDAP with my test user yet. It is
7108 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
7109 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
7110 have with it is how it handle errors. If something go wrong, its
7111 non-intuitive behaviour require me to go through some query work list
7112 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
7113 </description>
7114 </item>
7115
7116 <item>
7117 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
7118 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
7119 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
7120 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
7121 <description>&lt;p&gt;Here is a short update on my &lt;a
7122 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
7123 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
7124 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
7125 not reporting the status for KDE, because the upgrade crashes when
7126 aptitude try because of missing conflicts
7127 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
7128 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
7129
7130 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
7131 complete list of the installed packages. Based on this I see these
7132 differences when I did a test run today. As usual, I do not really
7133 know what the correct set of packages would be, but thought it best to
7134 publish the difference.&lt;/p&gt;
7135
7136 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7137
7138 &lt;blockquote&gt;&lt;p&gt;
7139 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
7140 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
7141 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7142 libgtksourceview-common libpt-1.10.10-plugins-alsa
7143 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7144 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7145 python-4suite-xml python-eggtrayicon python-gtkhtml2
7146 python-gtkmozembed svgalibg1 xserver-xephyr zip
7147 &lt;/p&gt;&lt;/blockquote&gt;
7148
7149 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7150
7151 &lt;blockquote&gt;&lt;p&gt;
7152 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7153 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7154 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
7155 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
7156 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
7157 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
7158 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7159 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7160 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7161 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
7162 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
7163 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
7164 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7165 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
7166 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7167 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
7168 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
7169 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7170 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7171 mysql-common swfdec-gnome totem-gstreamer wodim
7172 &lt;/p&gt;&lt;/blockquote&gt;
7173
7174 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7175
7176 &lt;blockquote&gt;&lt;p&gt;
7177 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7178 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7179 xserver-xorg-input-all xserver-xorg-input-evdev
7180 xserver-xorg-input-kbd xserver-xorg-input-mouse
7181 xserver-xorg-input-synaptics xserver-xorg-video-all
7182 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7183 xserver-xorg-video-chips xserver-xorg-video-cirrus
7184 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7185 xserver-xorg-video-glint xserver-xorg-video-i128
7186 xserver-xorg-video-i740 xserver-xorg-video-mach64
7187 xserver-xorg-video-mga xserver-xorg-video-neomagic
7188 xserver-xorg-video-nouveau xserver-xorg-video-nv
7189 xserver-xorg-video-r128 xserver-xorg-video-radeon
7190 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7191 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7192 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7193 xserver-xorg-video-sis xserver-xorg-video-sisusb
7194 xserver-xorg-video-tdfx xserver-xorg-video-tga
7195 xserver-xorg-video-trident xserver-xorg-video-tseng
7196 xserver-xorg-video-vesa xserver-xorg-video-vmware
7197 xserver-xorg-video-voodoo
7198 &lt;/p&gt;&lt;/blockquote&gt;
7199
7200 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7201
7202 &lt;blockquote&gt;&lt;p&gt;
7203 deskbar-applet xserver-xorg xserver-xorg-core
7204 xserver-xorg-input-wacom xserver-xorg-video-intel
7205 xserver-xorg-video-openchrome
7206 &lt;/p&gt;&lt;/blockquote&gt;
7207
7208 &lt;p&gt;I was told on IRC that the xorg-xserver package was
7209 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
7210 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
7211 No idea when it hits Squeeze, but when it does I hope it will reduce
7212 the difference somewhat.
7213 </description>
7214 </item>
7215
7216 <item>
7217 <title>LUMA, a very nice LDAP GUI</title>
7218 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
7219 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
7220 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
7221 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
7222 directory in Debian Edu, and in the process I started to miss a GUI
7223 tool to browse the LDAP tree. The only one I was able to find in
7224 Debian/Squeeze and Lenny is
7225 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
7226 be a great tool to get a overview of the current LDAP directory
7227 populated by default in Skolelinux. Thanks to it, I have been able to
7228 find empty and obsolete subtrees, misplaced objects and duplicate
7229 objects. It will be installed by default in Debian/Squeeze. If you
7230 are working with LDAP, give it a go. :)&lt;/p&gt;
7231
7232 &lt;p&gt;I did notice one problem with it I have not had time to report to
7233 the BTS yet. There is no .desktop file in the package, so the tool do
7234 not show up in the Gnome and KDE menus, but only deep down in in the
7235 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7236 released.&lt;/p&gt;
7237
7238 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
7239 like to move objects and remove subtrees directly in the GUI, but have
7240 not found a way to do that with LUMA yet. So in the mean time, I use
7241 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
7242
7243 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
7244 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7245
7246 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
7247 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
7248 useful GUI alternative. It seem like a good tool, but is unmaintained
7249 in Debian and got a RC bug keeping it out of Squeeze. Unless that
7250 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
7251 </description>
7252 </item>
7253
7254 <item>
7255 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
7256 <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>
7257 <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>
7258 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
7259 <description>&lt;p&gt;A while back, I
7260 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
7261 about the fact&lt;/a&gt; that it is not possible with the provided schemas
7262 for storing DNS and DHCP information in LDAP to combine the two sets
7263 of information into one LDAP object representing a computer.&lt;/p&gt;
7264
7265 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
7266 the dhcpHost object class auxiliary, to allow it to be combined with
7267 the dNSDomain object class, and thus forming one object for one
7268 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
7269
7270 &lt;p&gt;If I understand this correctly, it is not safe to do this change
7271 without also changing the assigned number for the object class, and I
7272 do not know enough about LDAP schema design to do that properly for
7273 Debian Edu.&lt;/p&gt;
7274
7275 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
7276 the
7277 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
7278 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
7279 available today from IETF.&lt;/p&gt;
7280
7281 &lt;pre&gt;
7282 --- dhcp.schema (revision 65192)
7283 +++ dhcp.schema (working copy)
7284 @@ -376,7 +376,7 @@
7285 objectclass ( 2.16.840.1.113719.1.203.6.6
7286 NAME &#39;dhcpHost&#39;
7287 DESC &#39;This represents information about a particular client&#39;
7288 - SUP top
7289 + SUP top AUXILIARY
7290 MUST cn
7291 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
7292 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
7293 &lt;/pre&gt;
7294
7295 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
7296 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
7297 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
7298
7299 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7300 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7301 </description>
7302 </item>
7303
7304 <item>
7305 <title>Calling tasksel like the installer, while still getting useful output</title>
7306 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
7307 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
7308 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
7309 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
7310 installs packages during the normal debian-installer run. Until now,
7311 I have ended up letting tasksel do the work, with the annoying problem
7312 of not getting any feedback at all when something fails (like a
7313 conffile question from dpkg or a download that fails), using code like
7314 this:
7315
7316 &lt;blockquote&gt;&lt;pre&gt;
7317 export DEBIAN_FRONTEND=noninteractive
7318 tasksel --new-install
7319 &lt;/pre&gt;&lt;/blockquote&gt;
7320
7321 This would invoke tasksel, let its automatic task selection pick the
7322 tasks to install, and continue to install the requested tasks without
7323 any output what so ever.
7324
7325 Recently I revisited this problem while working on the automatic
7326 package upgrade testing, because tasksel would some times hang without
7327 any useful feedback, and I want to see what is going on when it
7328 happen. Then it occured to me, I can parse the output from tasksel
7329 when asked to run in test mode, and use that aptitude command line
7330 printed by tasksel then to simulate the tasksel run. I ended up using
7331 code like this:
7332
7333 &lt;blockquote&gt;&lt;pre&gt;
7334 export DEBIAN_FRONTEND=noninteractive
7335 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
7336 $cmd
7337 &lt;/pre&gt;&lt;/blockquote&gt;
7338
7339 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
7340 --without-recommends -o APT::Install-Recommends=no -y install
7341 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
7342 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
7343 laptop task and all packages with priority standard , required and
7344 important, just like tasksel would have done it during
7345 installation.&lt;/p&gt;
7346
7347 &lt;p&gt;A better approach is probably to extend tasksel to be able to
7348 install packages without using debconf-apt-progress, for use cases
7349 like this.&lt;/p&gt;
7350 </description>
7351 </item>
7352
7353 <item>
7354 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
7355 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
7356 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
7357 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
7358 <description>&lt;p&gt;My
7359 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
7360 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
7361 finally made the upgrade logs available from
7362 &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;.
7363 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
7364 apt and aptitude, and found their differences interesting. This time
7365 I will only focus on their removal plans.&lt;/p&gt;
7366
7367 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
7368 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
7369 surprising part is that it want to remove xorg and all
7370 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
7371 sure why. When asking aptitude to do the same, it want to remove 129
7372 packages, but most of them are library packages I suspect are no
7373 longer needed. Both of them want to remove bluetooth packages, which
7374 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
7375
7376 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
7377 which seem like a bad idea and xorg the same way as with Gnome. Asking
7378 aptitude for the same, it wants to remove 192 packages, none which are
7379 too surprising.&lt;/p&gt;
7380
7381 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
7382 and avoided, and perhaps others as well. Here are the complete list
7383 of planned removals. The complete logs is available from the URL
7384 above. Note if you want to repeat these tests, that the upgrade test
7385 for kde+apt-get hung in the tasksel setup because of dpkg asking
7386 conffile questions. No idea why. I worked around it by using
7387 &#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
7388 continue.&lt;/p&gt;
7389
7390 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
7391 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
7392 gnome-desktop-environment gnome-network-admin gtkhtml3.14
7393 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
7394 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
7395 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
7396 serpentine swfdec-mozilla update-manager xorg xserver-xorg
7397 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7398 xserver-xorg-input-kbd xserver-xorg-input-mouse
7399 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7400 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7401 xserver-xorg-video-ati xserver-xorg-video-chips
7402 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7403 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7404 xserver-xorg-video-glint xserver-xorg-video-i128
7405 xserver-xorg-video-i740 xserver-xorg-video-imstt
7406 xserver-xorg-video-intel xserver-xorg-video-mach64
7407 xserver-xorg-video-mga xserver-xorg-video-neomagic
7408 xserver-xorg-video-nsc xserver-xorg-video-nv
7409 xserver-xorg-video-openchrome xserver-xorg-video-r128
7410 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7411 xserver-xorg-video-rendition xserver-xorg-video-s3
7412 xserver-xorg-video-s3virge xserver-xorg-video-savage
7413 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7414 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7415 xserver-xorg-video-tga xserver-xorg-video-trident
7416 xserver-xorg-video-tseng xserver-xorg-video-v4l
7417 xserver-xorg-video-vesa xserver-xorg-video-vga
7418 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
7419 xulrunner-1.9-gnome-support&lt;/p&gt;
7420
7421 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
7422
7423 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
7424 djvulibre-desktop finger gnome-app-install gnome-mount
7425 gnome-network-admin gnome-spell gnome-vfs-obexftp
7426 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
7427 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
7428 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
7429 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
7430 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
7431 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
7432 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
7433 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
7434 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
7435 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
7436 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
7437 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
7438 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
7439 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
7440 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
7441 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
7442 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
7443 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
7444 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
7445 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
7446 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
7447 openoffice.org-writer2latex openssl-blacklist p7zip
7448 python-4suite-xml python-eggtrayicon python-gnome2-desktop
7449 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
7450 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
7451 swfdec-mozilla totem-gstreamer update-manager wodim
7452 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7453 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7454 zip&lt;/p&gt;
7455
7456 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
7457
7458 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
7459 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
7460 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
7461 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
7462 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
7463 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
7464 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
7465 xserver-xorg-input-kbd xserver-xorg-input-mouse
7466 xserver-xorg-input-synaptics xserver-xorg-input-wacom
7467 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
7468 xserver-xorg-video-ati xserver-xorg-video-chips
7469 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
7470 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7471 xserver-xorg-video-glint xserver-xorg-video-i128
7472 xserver-xorg-video-i740 xserver-xorg-video-imstt
7473 xserver-xorg-video-intel xserver-xorg-video-mach64
7474 xserver-xorg-video-mga xserver-xorg-video-neomagic
7475 xserver-xorg-video-nsc xserver-xorg-video-nv
7476 xserver-xorg-video-openchrome xserver-xorg-video-r128
7477 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
7478 xserver-xorg-video-rendition xserver-xorg-video-s3
7479 xserver-xorg-video-s3virge xserver-xorg-video-savage
7480 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
7481 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
7482 xserver-xorg-video-tga xserver-xorg-video-trident
7483 xserver-xorg-video-tseng xserver-xorg-video-v4l
7484 xserver-xorg-video-vesa xserver-xorg-video-vga
7485 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
7486
7487 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
7488 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
7489 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
7490 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
7491 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
7492 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7493 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
7494 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
7495 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7496 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
7497 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
7498 kghostview khelpcenter khexedit kiconedit kitchensync klatin
7499 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
7500 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
7501 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
7502 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
7503 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
7504 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
7505 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7506 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
7507 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
7508 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7509 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
7510 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
7511 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
7512 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7513 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
7514 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
7515 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
7516 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
7517 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
7518 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
7519 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
7520 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
7521 texlive-common texlive-doc-base texlive-fonts-recommended
7522 xserver-xorg-video-cyrix xserver-xorg-video-imstt
7523 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
7524 xulrunner-1.9&lt;/p&gt;
7525
7526 </description>
7527 </item>
7528
7529 <item>
7530 <title>Automatic upgrade testing from Lenny to Squeeze</title>
7531 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
7532 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
7533 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
7534 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
7535 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
7536 have been discovered and reported in the process
7537 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
7538 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
7539 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
7540 kdebase-workspace-data), and to get a more regular testing going on, I
7541 am working on a script to automate the test.&lt;/p&gt;
7542
7543 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
7544 Gnome or KDE desktop installation inside the chroot before upgrading
7545 it. To ensure no services are started in the chroot, a policy-rc.d
7546 script is inserted. To make sure tasksel believe it is to install a
7547 desktop on a laptop, the tasksel tests are replaced in the chroot
7548 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
7549
7550 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
7551 currently always fail because udev refuses to upgrade with the kernel
7552 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
7553 is created. The bug report
7554 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
7555 this problem do not trigger in a chroot, but I touch the file anyway
7556 to make sure the upgrade go well. Testing on virtual and real
7557 hardware have failed me because of udev so far, and creating this file
7558 do the trick in such settings anyway. This is a
7559 &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
7560 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
7561 maintainer because he lack the resources to rewrite udev to keep
7562 working with old kernels or something like that. I really wish the
7563 udev upstream would keep udev backwards compatible, to avoid such
7564 upgrade problem, but given that they fail to do so, I guess
7565 documenting the way out of this mess is the best option we got for
7566 Debian Squeeze.&lt;/p&gt;
7567
7568 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
7569 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
7570 trick:&lt;/p&gt;
7571
7572 &lt;blockquote&gt;&lt;pre&gt;
7573 #!/bin/sh
7574 set -ex
7575
7576 if [ &quot;$1&quot; ] ; then
7577 desktop=$1
7578 else
7579 desktop=gnome
7580 fi
7581
7582 from=lenny
7583 to=squeeze
7584
7585 exec &amp;lt; /dev/null
7586 unset LANG
7587 mirror=http://ftp.skolelinux.org/debian
7588 tmpdir=chroot-$from-upgrade-$to-$desktop
7589 fuser -mv .
7590 debootstrap $from $tmpdir $mirror
7591 chroot $tmpdir aptitude update
7592 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
7593 #!/bin/sh
7594 exit 101
7595 EOF
7596 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
7597 exit_cleanup() {
7598 umount $tmpdir/proc
7599 }
7600 mount -t proc proc $tmpdir/proc
7601 # Make sure proc is unmounted also on failure
7602 trap exit_cleanup EXIT INT
7603
7604 chroot $tmpdir aptitude -y install debconf-utils
7605
7606 # Make sure tasksel autoselection trigger. It need the test scripts
7607 # to return the correct answers.
7608 echo tasksel tasksel/desktop multiselect $desktop | \
7609 chroot $tmpdir debconf-set-selections
7610
7611 # Include the desktop and laptop task
7612 for test in desktop laptop ; do
7613 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
7614 #!/bin/sh
7615 exit 2
7616 EOF
7617 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
7618 done
7619
7620 DEBIAN_FRONTEND=noninteractive
7621 DEBIAN_PRIORITY=critical
7622 export DEBIAN_FRONTEND DEBIAN_PRIORITY
7623 chroot $tmpdir tasksel --new-install
7624
7625 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
7626 chroot $tmpdir aptitude update
7627 touch $tmpdir/etc/udev/kernel-upgrade
7628 chroot $tmpdir aptitude -y dist-upgrade
7629 fuser -mv
7630 &lt;/pre&gt;&lt;/blockquote&gt;
7631
7632 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
7633 with aptitude, but I have not had time to look at how they behave
7634 differently so far. I hope to get a cron job running to do the test
7635 regularly and post the result on the web. The Gnome upgrade currently
7636 work, while the KDE upgrade fail because of the bug in
7637 kdebase-workspace-data&lt;/p&gt;
7638
7639 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
7640 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
7641 post, so I will refrain from trying. I can report that for Gnome,
7642 aptitude report 760 packages upgraded, 448 newly installed, 129 to
7643 remove and 1 not upgraded and 1024MB need to be downloaded while for
7644 KDE the same numbers are 702 packages upgraded, 507 newly installed,
7645 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
7646
7647 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
7648 is able to migrate to dependency based boot sequencing and parallel
7649 booting without a hitch. Was unsure if there were still bugs with
7650 packages failing to clean up their obsolete init.d script during
7651 upgrades, and no such problem seem to affect the Gnome desktop+laptop
7652 packages.&lt;/p&gt;
7653 </description>
7654 </item>
7655
7656 <item>
7657 <title>Upstart or sysvinit - as init.d scripts see it</title>
7658 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
7659 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
7660 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
7661 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
7662 scripts to migrate (some of) their operations to upstart job while
7663 keeping the init.d for hurd and kfreebsd. The packages with such
7664 needs will need a way to get their init.d scripts to behave
7665 differently when used with sysvinit and with upstart. Because of
7666 this, I had a look at the environment variables set when a init.d
7667 script is running under upstart, and when it is not.&lt;/p&gt;
7668
7669 &lt;p&gt;With upstart, I notice these environment variables are set when a
7670 script is started from rcS.d/ (ignoring some irrelevant ones like
7671 COLUMNS):&lt;/p&gt;
7672
7673 &lt;blockquote&gt;&lt;pre&gt;
7674 DEFAULT_RUNLEVEL=2
7675 previous=N
7676 PREVLEVEL=
7677 RUNLEVEL=
7678 runlevel=S
7679 UPSTART_EVENTS=startup
7680 UPSTART_INSTANCE=
7681 UPSTART_JOB=rc-sysinit
7682 &lt;/pre&gt;&lt;/blockquote&gt;
7683
7684 &lt;p&gt;With sysvinit, these environment variables are set for the same
7685 script.&lt;/p&gt;
7686
7687 &lt;blockquote&gt;&lt;pre&gt;
7688 INIT_VERSION=sysvinit-2.88
7689 previous=N
7690 PREVLEVEL=N
7691 RUNLEVEL=S
7692 runlevel=S
7693 &lt;/pre&gt;&lt;/blockquote&gt;
7694
7695 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
7696 sysvinit are not set by upstart. Not sure if it is intentional or not
7697 to not be compatible with sysvinit in this regard.&lt;/p&gt;
7698
7699 &lt;p&gt;For scripts needing to behave differently when upstart is used,
7700 looking for the UPSTART_JOB environment variable seem to be a good
7701 choice.&lt;/p&gt;
7702 </description>
7703 </item>
7704
7705 <item>
7706 <title>A manual for standards wars...</title>
7707 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
7708 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
7709 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
7710 <description>&lt;p&gt;Via the
7711 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
7712 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
7713 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
7714 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
7715 following the standards wars of today.&lt;/p&gt;
7716 </description>
7717 </item>
7718
7719 <item>
7720 <title>Sitesummary tip: Listing computer hardware models used at site</title>
7721 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
7722 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
7723 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
7724 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
7725 to get a list of the machine types in use thanks to the DMI
7726 information extracted from each machine. The script to do so is
7727 included in the sitesummary package, and here is example output from
7728 the Skolelinux build servers:&lt;/p&gt;
7729
7730 &lt;blockquote&gt;&lt;pre&gt;
7731 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
7732 vendor count
7733 Dell Computer Corporation 1
7734 PowerEdge 1750 1
7735 IBM 1
7736 eserver xSeries 345 -[8670M1X]- 1
7737 Intel 2
7738 [no-dmi-info] 3
7739 maintainer:~#
7740 &lt;/pre&gt;&lt;/blockquote&gt;
7741
7742 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
7743 provided in each machine. Here there are Intel machines without model
7744 information listed with Intel as vendor and no model, and virtual Xen
7745 machines listed as [no-dmi-info]. One can add -l as a command line
7746 option to list the individual machines.&lt;/p&gt;
7747
7748 &lt;p&gt;A larger list is
7749 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
7750 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
7751 provide the basic sitesummary report publicly. In their report there
7752 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
7753 their machines, and as sitesummary is available in both distributions,
7754 it is trivial to get all of them to report to the same central
7755 collector.&lt;/p&gt;
7756 </description>
7757 </item>
7758
7759 <item>
7760 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
7761 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
7762 <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>
7763 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
7764 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
7765 start at boot when an NVidia video card is used is handled. The
7766 problem seem to be that the nvidia X.org driver uses a long time to
7767 initialize, and this duration is longer than kdm is configured to
7768 wait.&lt;/p&gt;
7769
7770 &lt;p&gt;I came across two bugs related to this issue,
7771 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
7772 against initscripts and passed on to nvidia-glx when it became obvious
7773 that the nvidia drivers were involved, and
7774 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
7775 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
7776
7777 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
7778 problem nvidia video card owners experience and make sure the Debian
7779 distribution work out of the box for these users. The nvidia driver
7780 maintainers expect kdm to be set up to wait longer, while kdm expect
7781 the nvidia driver maintainers to fix the driver to start faster, and
7782 while they wait for each other I guess the users end up switching to a
7783 distribution that work for them. I have no idea what the solution is,
7784 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
7785
7786 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
7787 </description>
7788 </item>
7789
7790 <item>
7791 <title>Parallellized boot seem to hold up well in Debian/testing</title>
7792 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
7793 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
7794 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
7795 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
7796 The feature seem to hold up pretty well, but three fairly serious
7797 issues are known and should be solved:
7798
7799 &lt;p&gt;&lt;ul&gt;
7800
7801 &lt;li&gt;The wicd package seen to
7802 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
7803 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
7804 parallel booting is enabled. No idea why, but the wicd maintainer
7805 seem to be on the case.&lt;/li&gt;
7806
7807 &lt;li&gt;The nvidia X driver seem to
7808 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
7809 triggered more easily when parallel booting is in effect. The
7810 maintainer is on the case.&lt;/li&gt;
7811
7812 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
7813 sequencing (the shutdown is broken) when old file-rc users
7814 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
7815 sysv-rc. One way to solve it would be for file-rc to create
7816 /etc/init.d/.legacy-bootordering, and another is to try to make
7817 sysv-rc more robust. Will investigate some more and probably upload a
7818 workaround in sysv-rc to help those trying to move from file-rc to
7819 sysv-rc get a working shutdown.&lt;/li&gt;
7820
7821 &lt;/ul&gt;&lt;/p&gt;
7822
7823 &lt;p&gt;All in all not many surprising issues, and all of them seem
7824 solvable before Squeeze is released. In addition to these there are
7825 some packages with bugs in their dependencies and run level settings,
7826 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
7827
7828 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7829 the BTS, please usertag the report to get it to show up at
7830 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7831 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7832
7833 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
7834 </description>
7835 </item>
7836
7837 <item>
7838 <title>More flexible firmware handling in debian-installer</title>
7839 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
7840 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
7841 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
7842 <description>&lt;p&gt;After a long break from debian-installer development, I finally
7843 found time today to return to the project. Having to spend less time
7844 working dependency based boot in debian, as it is almost complete now,
7845 definitely helped freeing some time.&lt;/p&gt;
7846
7847 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
7848 include some firmware packages on the Debian Edu CDs, those needed to
7849 get disk and network controllers working. Without having these
7850 firmware packages available during installation, it is impossible to
7851 install Debian Edu on the given machine, and because our target group
7852 are non-technical people, asking them to provide firmware packages on
7853 an external medium is a support pain. Initially, I expected it to be
7854 enough to include the firmware packages on the CD to get
7855 debian-installer to find and use them. This proved to be wrong.
7856 Next, I hoped it was enough to symlink the relevant firmware packages
7857 to some useful location on the CD (tried /cdrom/ and
7858 /cdrom/firmware/). This also proved to not work, and at this point I
7859 found time to look at the debian-installer code to figure out what was
7860 going to work.&lt;/p&gt;
7861
7862 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
7863 look revealed that it would only look for firmware packages outside
7864 the installation media, so the CD was never checked for firmware
7865 packages. It would only check USB sticks, floppies and other
7866 &quot;external&quot; media devices. Today I changed it to also look in the
7867 /cdrom/firmware/ directory on the mounted CD or DVD, which should
7868 solve the problem I ran into with Debian edu. I also changed it to
7869 look in /firmware/, to make sure the installer also find firmware
7870 provided in the initrd when booting the installer via PXE, to allow us
7871 to provide the same feature in the PXE setup included in Debian
7872 Edu.&lt;/p&gt;
7873
7874 &lt;p&gt;To make sure firmware deb packages with a license questions are not
7875 activated without asking if the license is accepted, I extended
7876 hw-detect to look for preinst scripts in the firmware packages, and
7877 run these before activating the firmware during installation. The
7878 license question is asked using debconf in the preinst, so this should
7879 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
7880
7881 &lt;p&gt;If you want to discuss the details of these features, please
7882 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
7883 </description>
7884 </item>
7885
7886 <item>
7887 <title>Parallellized boot is now the default in Debian/unstable</title>
7888 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
7889 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
7890 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
7891 <description>&lt;p&gt;Since this evening, parallel booting is the default in
7892 Debian/unstable for machines using dependency based boot sequencing.
7893 Apparently the testing of concurrent booting has been wider than
7894 expected, if I am to believe the
7895 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7896 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
7897 with the feature this weekend, to give us some time to detect any
7898 remaining problems before Squeeze is frozen. If serious problems are
7899 detected, it is simple to change the default back to sequential boot.
7900 The upload of the new sysvinit package also activate a new upstream
7901 version.&lt;/p&gt;
7902
7903 More information about
7904 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
7905 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
7906 currently possible to disable parallel booting when one run into
7907 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
7908
7909 &lt;blockquote&gt;&lt;pre&gt;
7910 CONCURRENCY=none
7911 &lt;/pre&gt;&lt;/blockquote&gt;
7912
7913 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
7914 the BTS, please usertag the report to get it to show up at
7915 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
7916 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
7917 </description>
7918 </item>
7919
7920 <item>
7921 <title>Sitesummary tip: Listing MAC address of all clients</title>
7922 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
7923 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
7924 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
7925 <description>&lt;p&gt;In the recent Debian Edu versions, the
7926 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
7927 system&lt;/a&gt; is used to keep track of the machines in the school
7928 network. Each machine will automatically report its status to the
7929 central server after boot and once per night. The network setup is
7930 also reported, and using this information it is possible to get the
7931 MAC address of all network interfaces in the machines. This is useful
7932 to update the DHCP configuration.&lt;/p&gt;
7933
7934 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
7935 ist all MAC addresses of all machines reporting to sitesummary. Run
7936 this on the collector host:&lt;/p&gt;
7937
7938 &lt;blockquote&gt;&lt;pre&gt;
7939 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
7940 &lt;/pre&gt;&lt;/blockquote&gt;
7941
7942 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
7943 line per machine and with space between the MAC addresses.&lt;/p&gt;
7944
7945 &lt;p&gt;To allow system administrators easier job at adding static DHCP
7946 addresses for hosts, it would be possible to extend this to fetch
7947 machine information from sitesummary and update the DHCP and DNS
7948 tables in LDAP using this information. Such tool is unfortunately not
7949 written yet.&lt;/p&gt;
7950 </description>
7951 </item>
7952
7953 <item>
7954 <title>systemd, an interesting alternative to upstart</title>
7955 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
7956 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
7957 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
7958 <description>&lt;p&gt;The last few days a new boot system called
7959 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
7960 has been
7961 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
7962
7963 to the free software world. I have not yet had time to play around
7964 with it, but it seem to be a very interesting alternative to
7965 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
7966 a good alternative for Debian when we are able to switch to an event
7967 based boot system. Tollef is
7968 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
7969 systemd into Debian, and I look forward to seeing how well it work. I
7970 like the fact that systemd handles init.d scripts with dependency
7971 information natively, allowing them to run in parallel where upstart
7972 at the moment do not.&lt;/p&gt;
7973
7974 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
7975 platform support. It only work on recent Linux kernels, and also need
7976 some new kernel features enabled to function properly. This means
7977 kFreeBSD and Hurd ports of Debian will need a port or a different boot
7978 system. Not sure how that will be handled if systemd proves to be the
7979 way forward.&lt;/p&gt;
7980
7981 &lt;p&gt;In the mean time, based on the
7982 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
7983 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
7984 decided to enable full parallel booting as the default in Debian as
7985 soon as possible (probably this weekend or early next week), to see if
7986 there are any remaining serious bugs in the init.d dependencies. A
7987 new version of the sysvinit package implementing this change is
7988 already in experimental. If all go well, Squeeze will be released
7989 with parallel booting enabled by default.&lt;/p&gt;
7990 </description>
7991 </item>
7992
7993 <item>
7994 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
7995 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
7996 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
7997 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
7998 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
7999 complete, so complete that it is actually possible to run all the
8000 init.d scripts in parallell based on these dependencies. If you want
8001 to test your Squeeze system, make sure
8002 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8003 based boot sequencing&lt;/a&gt; is enabled, and add this line to
8004 /etc/default/rcS:&lt;/p&gt;
8005
8006 &lt;blockquote&gt;&lt;pre&gt;
8007 CONCURRENCY=makefile
8008 &lt;/pre&gt;&lt;/blockquote&gt;
8009
8010 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
8011 scripts in parallel using the dependency information stored in
8012 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8013 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8014 to try to start the kdm and gdm scripts as early as possible, and will
8015 start the facilities required by kdm or gdm as early as possible to
8016 make this happen.&lt;/p&gt;
8017
8018 &lt;p&gt;Give it a try, and see if you like the result. If some services
8019 fail to start properly, it is most likely because they have incomplete
8020 init.d script dependencies in their startup script (or some of their
8021 dependent scripts have incomplete dependencies). Report bugs and get
8022 the package maintainers to fix it. :)&lt;/p&gt;
8023
8024 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
8025 manage to get the init.d script dependencies complete and correct. I
8026 expect we will get there in Squeeze+1, if we get manage to test and
8027 fix the remaining issues.&lt;/p&gt;
8028
8029 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8030 the BTS, please usertag the report to get it to show up at
8031 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8032 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8033 </description>
8034 </item>
8035
8036 <item>
8037 <title>Debian has switched to dependency based boot sequencing</title>
8038 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
8039 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
8040 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
8041 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
8042 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
8043 have been migrated to using dependency based boot sequencing. This
8044 conclude work me and others have been doing for the last three days.
8045 It feels great to see this finally part of the default Debian
8046 installation. Now we just need to weed out the last few problems that
8047 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
8048
8049 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
8050 fixing the more fundamental problem of handing the event based
8051 non-predictable kernel in the early boot.&lt;/p&gt;
8052 </description>
8053 </item>
8054
8055 <item>
8056 <title>Taking over sysvinit development</title>
8057 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
8058 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
8059 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
8060 <description>&lt;p&gt;After several years of frustration with the lack of activity from
8061 the existing sysvinit upstream developer, I decided a few weeks ago to
8062 take over the package and become the new upstream. The number of
8063 patches to track for the Debian package was becoming a burden, and the
8064 lack of synchronization between the distribution made it hard to keep
8065 the package up to date.&lt;/p&gt;
8066
8067 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8068 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
8069 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
8070 and Fedora), based on the patches currently in use in these
8071 distributions. We Debian maintainers plan to move to this tarball as
8072 the new upstream as soon as we find time to do the merge. Since the
8073 new tarball was created, we agreed with Werner at SuSe to make a new
8074 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
8075 development there. The project is registered and currently waiting
8076 for approval by the Savannah administrators, and as soon as it is
8077 approved, we will import the old versions from svn and continue
8078 working on the future release.&lt;/p&gt;
8079
8080 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
8081 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
8082 </description>
8083 </item>
8084
8085 <item>
8086 <title>Debian boots quicker and quicker</title>
8087 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
8088 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
8089 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
8090 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
8091 people involved in the boot system on Debian and Ubuntu, to see if we
8092 could find more ways to speed up the boot system. This was an Ubuntu
8093 funded
8094 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
8095 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
8096 of boot systems, and ways to handle the increasing number of boot
8097 issues introduced by the Linux kernel becoming more and more
8098 asynchronous and event base. The Ubuntu approach using udev and
8099 upstart might be a good way forward. Time will show.&lt;/p&gt;
8100
8101 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
8102 process in Debian. All of these should be applied to get a quick
8103 boot:&lt;/p&gt;
8104
8105 &lt;ul&gt;
8106
8107 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
8108
8109 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
8110 clock is in UTC.&lt;/li&gt;
8111
8112 &lt;li&gt;Install and activate the insserv package to enable
8113 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8114 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
8115
8116 &lt;/ul&gt;
8117
8118 These points are based on the Google summer of code work done by
8119 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
8120 Villegas&lt;/a&gt;.
8121
8122 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
8123 unstable yesterday. When we tested it, we were able to cut 6 seconds
8124 from the boot sequence. It depend on very correct dependency
8125 declaration in all init.d scripts, so I expect us to find edge cases
8126 where the dependences in some scripts are slightly wrong when we start
8127 using this.&lt;/p&gt;
8128
8129 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8130 introduced by Raphael Geissert today, one that could affect the
8131 startup speed as well. Instead of starting some scripts concurrently
8132 from rcS.d/ and another set of scripts from rc2.d/, it would be
8133 possible to run a of them in the same process. A quick way to test
8134 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
8135 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
8136 </description>
8137 </item>
8138
8139 <item>
8140 <title>BSAs påstander om piratkopiering møter motstand</title>
8141 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
8142 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
8143 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
8144 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
8145 programvareselskapene som Microsoft og Apple, publisert en rapport der
8146 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8147 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8148 dager siden kom
8149 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
8150 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
8151 dagene. Et spesielt interessant kommentar fra Sverige,
8152 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
8153 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
8154
8155 &lt;blockquote&gt;
8156 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
8157 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8158 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
8159 exakta&quot;, säger BSAs Sverigechef John Hugosson.
8160 &lt;/blockquote&gt;
8161
8162 &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
8163 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
8164 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
8165 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
8166 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
8167
8168 &lt;p&gt;Fant lenkene via &lt;a
8169 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
8170 på Slashdot&lt;/a&gt;.&lt;/p&gt;
8171 </description>
8172 </item>
8173
8174 <item>
8175 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
8176 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
8177 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
8178 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
8179 <description>&lt;p&gt;Kom over
8180 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
8181 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8182 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8183 jobber til daglig. En rask opptelling forteller meg at vi har 490
8184 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
8185 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
8186 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
8187 </description>
8188 </item>
8189
8190 <item>
8191 <title>Kryptert harddisk - naturligvis</title>
8192 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
8193 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
8194 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
8195 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
8196 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
8197 når en tar tap av arbeidstid, fortrolige dokumenter,
8198 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8199 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8200 til at jeg har kryptert harddisken på både kontormaskinen og min
8201 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8202 komme på avveie, den første informasjon relatert til jobben min ved
8203 Universitetet i Oslo, og den andre relatert til blant annet
8204 foreningsarbeide. Kryptering av diskene gjør at det er lite
8205 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8206 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8207 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8208 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8209 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8210 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8211 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8212 det er gjort slik jeg gjør det er minimale, og gevinstene er
8213 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8214 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
8215
8216 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8217 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8218 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8219 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8220 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8221 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8222 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8223 betydelige.&lt;/p&gt;
8224 </description>
8225 </item>
8226
8227 <item>
8228 <title>Two projects that have improved the quality of free software a lot</title>
8229 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
8230 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
8231 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
8232 <description>&lt;p&gt;There are two software projects that have had huge influence on the
8233 quality of free software, and I wanted to mention both in case someone
8234 do not yet know them.&lt;/p&gt;
8235
8236 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
8237 tool to detect and expose errors in the memory handling of programs.
8238 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
8239 and it will report any problems on stdout. It is even better if the
8240 program include debug information. With debug information, it is able
8241 to report the source file name and line number where the problem
8242 occurs. It can report things like &#39;reading past memory block in file
8243 X line N, the memory block was allocated in file Y, line M&#39;, and
8244 &#39;using uninitialised value in control logic&#39;. This tool has made it
8245 trivial to investigate reproducible crash bugs in programs, and have
8246 reduced the number of this kind of bugs in free software a lot.
8247
8248 &lt;p&gt;The second one is
8249 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
8250 a source code checker. It is able to process the source of a program
8251 and find problems in the logic without running the program. It
8252 started out as the Stanford Checker and became well known when it was
8253 used to find bugs in the Linux kernel. It is now a commercial tool
8254 and the company behind it is running
8255 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
8256 free software community, where a lot of free software projects get
8257 their source checked for free. Several thousand defects have been
8258 found and fixed so far. It can find errors like &#39;lock L taken in file
8259 X line N is never released if exiting in line M&#39;, or &#39;the code in file
8260 Y lines O to P can never be executed&#39;. The projects included in the
8261 community service project have managed to get rid of a lot of
8262 reliability problems thanks to Coverity.&lt;/p&gt;
8263
8264 &lt;p&gt;I believe tools like this, that are able to automatically find
8265 errors in the source, are vital to improve the quality of software and
8266 make sure we can get rid of the crashing and failing software we are
8267 surrounded by today.&lt;/p&gt;
8268 </description>
8269 </item>
8270
8271 <item>
8272 <title>No patch is not better than a useless patch</title>
8273 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
8274 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
8275 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
8276 <description>&lt;p&gt;Julien Blache
8277 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
8278 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
8279 patch allow one to discuss a concrete and proposed solution, and also
8280 prove that the issue at hand is important enough for someone to spent
8281 time on fixing it. No patch do not provide any of these positive
8282 properties.&lt;/p&gt;
8283 </description>
8284 </item>
8285
8286 <item>
8287 <title>Standardize on protocols and formats, not vendors and applications</title>
8288 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
8289 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
8290 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
8291 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
8292 very good one to form a long lived computer infrastructure. It is the
8293 simple one, lost by many in todays computer industry: Standardize on
8294 open network protocols and open exchange/storage formats, not applications.
8295 Applications come and go, while protocols and files tend to stay, and
8296 thus one want to make it easy to change application and vendor, while
8297 avoiding conversion costs and locking users to a specific platform or
8298 application.&lt;/p&gt;
8299
8300 &lt;p&gt;This approach make it possible to replace the client applications
8301 independently of the server applications. One can even allow users to
8302 use several different applications as long as they handle the selected
8303 protocol and format. In the normal case, only one client application
8304 is recommended and users only get help if they choose to use this
8305 application, but those that want to deviate from the easy path are not
8306 blocked from doing so.&lt;/p&gt;
8307
8308 &lt;p&gt;It also allow us to replace the server side without forcing the
8309 users to replace their applications, and thus allow us to select the
8310 best server implementation at any moment, when scale and resouce
8311 requirements change.&lt;/p&gt;
8312
8313 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
8314 open formats, but I would never recommend standardizing on a single
8315 application that do not use open network protocol or open formats.&lt;/p&gt;
8316 </description>
8317 </item>
8318
8319 <item>
8320 <title>Returning from Skolelinux developer gathering</title>
8321 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
8322 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
8323 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
8324 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
8325 Edu/Skolelinux development gathering. I got a bit done tuning the
8326 desktop, and looked into the dynamic service location protocol
8327 implementation avahi. It look like it could be useful for us. Almost
8328 30 people participated, and I believe it was a great environment to
8329 get to know the Skolelinux system. Walter Bender, involved in the
8330 development of the Sugar educational platform, presented his stuff and
8331 also helped me improve my OLPC installation. He also showed me that
8332 his Turtle Art application can be used in standalone mode, and we
8333 agreed that I would help getting it packaged for Debian. As a
8334 standalone application it would be great for Debian Edu. We also
8335 tried to get the video conferencing working with two OLPCs, but that
8336 proved to be too hard for us. The application seem to need more work
8337 before it is ready for me. I look forward to getting home and relax
8338 now. :)&lt;/p&gt;
8339 </description>
8340 </item>
8341
8342 <item>
8343 <title>Time for new LDAP schemas replacing RFC 2307?</title>
8344 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
8345 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
8346 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
8347 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
8348 optimal. There is RFC 2307 documenting one way to store NIS maps in
8349 LDAP, and a modified version of this normally called RFC 2307bis, with
8350 some modifications to be compatible with Active Directory. The RFC
8351 specification handle the content of a lot of system databases, but do
8352 not handle DNS zones and DHCP configuration.&lt;/p&gt;
8353
8354 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
8355 we would like to store information about users, SMB clients/hosts,
8356 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
8357 and LTSP configuration in LDAP. These objects have a lot in common,
8358 but with the current LDAP schemas it is not possible to have one
8359 object per entity. For example, one need to have at least three LDAP
8360 objects for a given computer, one with the SMB related stuff, one with
8361 DNS information and another with DHCP information. The schemas
8362 provided for DNS and DHCP are impossible to combine into one LDAP
8363 object. In addition, it is impossible to implement quick queries for
8364 netgroup membership, because of the way NIS triples are implemented.
8365 It just do not scale. I believe it is time for a few RFC
8366 specifications to cleam up this mess.&lt;/p&gt;
8367
8368 &lt;p&gt;I would like to have one LDAP object representing each computer in
8369 the network, and this object can then keep the SMB (ie host key), DHCP
8370 (mac address/name) and DNS (name/IP address) settings in one place.
8371 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
8372
8373 &lt;p&gt;I would also like to have a quick way to map from a user or
8374 computer and to the net group this user or computer is a member.&lt;/p&gt;
8375
8376 &lt;p&gt;Active Directory have done a better job than unix heads like myself
8377 in this regard, and the unix side need to catch up. Time to start a
8378 new IETF work group?&lt;/p&gt;
8379 </description>
8380 </item>
8381
8382 <item>
8383 <title>Endelig er Debian Lenny gitt ut</title>
8384 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
8385 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
8386 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
8387 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
8388 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
8389 Et langt steg videre for Debian-prosjektet, og en rekke nye
8390 programpakker blir nå tilgjengelig for de av oss som bruker den
8391 stabile utgaven av Debian. Neste steg er nå å få
8392 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
8393 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
8394 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
8395 slippes løs på skolene. Takk til alle debian-utviklerne som har
8396 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
8397 bootsekvens tilgjengelig i stabil utgave, vha pakken
8398 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
8399 </description>
8400 </item>
8401
8402 <item>
8403 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
8404 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
8405 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
8406 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
8407 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
8408 Oslo. Most of Saturday was used for the general assemly for the
8409 member organization, but the rest of the weekend I used to tune the
8410 LTSP installation. LTSP now work out of the box on the 10-network.
8411 Acer Aspire One proved to be a very nice thin client, with both
8412 screen, mouse and keybard in a small box. Was working on getting the
8413 diskless workstation setup configured out of the box, but did not
8414 finish it before the weekend was up.&lt;/p&gt;
8415
8416 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
8417 the Brazilian group, so that will have to wait for the next
8418 development gathering. Would love to have the Debian Edu installer
8419 automatically detect and configure a multiseat setup when it find one
8420 of these cards.&lt;/p&gt;
8421 </description>
8422 </item>
8423
8424 <item>
8425 <title>The sorry state of multimedia browser plugins in Debian</title>
8426 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
8427 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
8428 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
8429 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
8430 plugins available in Debian Lenny, to see which one we should use by
8431 default in Debian Edu. We need an embedded video playing plugin with
8432 control buttons to pause or stop the video, and capable of streaming
8433 all the multimedia content available on the web. The test results and
8434 notes are available on
8435 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
8436 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
8437 fill this need. My personal video player favorite, VLC, has a really
8438 bad plugin which fail on a lot of the test pages. A lot of the MIME
8439 types I would expect to work with any free software player (like
8440 video/ogg), just do not work. And simple formats like the
8441 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
8442 totem and vlc plugins. I hope the situation will improve soon. No
8443 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
8444
8445 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
8446 be the only one fitting our needs. :/&lt;/p&gt;
8447 </description>
8448 </item>
8449
8450 </channel>
8451 </rss>