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