]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
26f8723723107c521ffaca2ce820ee43941b3b6e
[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>Detecting NFS hangs on Linux without hanging yourself...</title>
11 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
13 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
14 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
15 computers at the time, I often needed a way to detect if the machine
16 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
17 file or directory affected by the hang, the process (and possibly the
18 shell) will hang too. So you want to be able to detect this without
19 risking the detection process getting stuck too. It has not been
20 obvious how to do this. When the hang has lasted a while, it is
21 possible to find messages like these in dmesg:&lt;/p&gt;
22
23 &lt;p&gt;&lt;blockquote&gt;
24 nfs: server nfsserver not responding, still trying
25 &lt;br&gt;nfs: server nfsserver OK
26 &lt;/blockquote&gt;&lt;/p&gt;
27
28 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
29 be sure looking in dmesg is going to work. If there are lots of other
30 messages in dmesg the lines might have rotated out of site before they
31 are noticed.&lt;/p&gt;
32
33 &lt;p&gt;While reading through the nfs client implementation in linux kernel
34 code, I came across some statistics that seem to give a way to detect
35 it. The om_timeouts sunrpc value in the kernel will increase every
36 time the above log entry is inserted into dmesg. And after digging a
37 bit further, I discovered that this value show up in
38 /proc/self/mountstats on Linux.&lt;/p&gt;
39
40 &lt;p&gt;The mountstats content seem to be shared between files using the
41 same file system context, so it is enough to check one of the
42 mountstats files to get the state of the mount point for the machine.
43 I assume this will not show lazy umounted NFS points, nor NFS mount
44 points in a different process context (ie with a different filesystem
45 view), but that does not worry me.&lt;/p&gt;
46
47 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
48
49 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
50 [...]
51 device /dev/mapper/Debian-var mounted on /var with fstype ext3
52 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
53 opts: rw,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,soft,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=129.240.3.145,mountvers=3,mountport=4048,mountproto=udp,local_lock=all
54 age: 7863311
55 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
56 sec: flavor=1,pseudoflavor=1
57 events: 61063112 732346265 1028140 35486205 16220064 8162542 761447191 71714012 37189 3891185 45561809 110486139 4850138 420353 15449177 296502 52736725 13523379 0 52182 9016896 1231 0 0 0 0 0
58 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
59 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
60 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
61 per-op statistics
62 NULL: 0 0 0 0 0 0 0 0
63 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
64 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
65 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
66 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
67 READLINK: 125 125 0 20472 18620 0 1112 1118
68 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
69 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
70 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
71 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
72 SYMLINK: 903 903 0 233428 245488 6 5865 5917
73 MKNOD: 80 80 0 20148 21760 0 299 304
74 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
75 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
76 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
77 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
78 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
79 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
80 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
81 FSINFO: 2 2 0 232 328 0 1 1
82 PATHCONF: 1 1 0 116 140 0 0 0
83 COMMIT: 0 0 0 0 0 0 0 0
84
85 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
86 [...]
87 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
88
89 &lt;p&gt;The key number to look at is the third number in the per-op list.
90 It is the number of NFS timeouts experiences per file system
91 operation. Here 22 write timeouts and 5 access timeouts. If these
92 numbers are increasing, I believe the machine is experiencing NFS
93 hang. Unfortunately the timeout value do not start to increase right
94 away. The NFS operations need to time out first, and this can take a
95 while. The exact timeout value depend on the setup. For example the
96 defaults for TCP and UDP mount points are quite different, and the
97 timeout value is affected by the soft, hard, timeo and retrans NFS
98 mount options.&lt;/p&gt;
99
100 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
101 Enterprise Linux for getting the timeout count is to peek in /proc/.
102 But according to
103 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
104 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
105 command can be used to get these timeout values. But this do not work
106 on Linux, as far as I can tell. I
107 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
108 but have not seen any replies yet.&lt;/p&gt;
109
110 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
111 experiencing NFS hangs? Is there a way to detect which processes are
112 affected? Is there a way to get the NFS mount going quickly once the
113 network problem causing the NFS hang has been cleared? I would very
114 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
115 </description>
116 </item>
117
118 <item>
119 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
120 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
121 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</guid>
122 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
123 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
124 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
125 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
126 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
127 we are working on the proof reading to ensure consistent language and
128 use of correct computer science terms. The plan is to make the book
129 available on paper, as well as in electronic form. For that to
130 happen, the proof reading must be completed and all the figures need
131 to be translated. If you want to help out, get in touch.&lt;/p&gt;
132
133 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
134
135 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
136 pages) of the book created every morning is available for
137 proofreading. If you find any errors, please
138 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
139 Weblate and correct the error&lt;/a&gt;. The
140 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
141 of the translation including figures&lt;/a&gt; is a useful source for those
142 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
143 </description>
144 </item>
145
146 <item>
147 <title>Unlimited randomness with the ChaosKey?</title>
148 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
149 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
150 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
151 <description>&lt;p&gt;A few days ago I ordered a small batch of
152 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
153 USB dongle for generating entropy created by Bdale Garbee and Keith
154 Packard. Yesterday it arrived, and I am very happy to report that it
155 work great! According to its designers, to get it to work out of the
156 box, you need the Linux kernel version 4.1 or later. I tested on a
157 Debian Stretch machine (kernel version 4.9), and there it worked just
158 fine, increasing the available entropy very quickly. I wrote a small
159 test oneliner to test. It first print the current entropy level,
160 drain /dev/random, and then print the entropy level for five seconds.
161 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
162
163 &lt;blockquote&gt;&lt;pre&gt;
164 % cat /proc/sys/kernel/random/entropy_avail; \
165 dd bs=1M if=/dev/random of=/dev/null count=1; \
166 for n in $(seq 1 5); do \
167 cat /proc/sys/kernel/random/entropy_avail; \
168 sleep 1; \
169 done
170 300
171 0+1 oppføringer inn
172 0+1 oppføringer ut
173 28 byte kopiert, 0,000264565 s, 106 kB/s
174 4
175 8
176 12
177 17
178 21
179 %
180 &lt;/pre&gt;&lt;/blockquote&gt;
181
182 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
183 application requiring random bits (like a HTTPS enabled web server)
184 will halt and wait for more entrpy. And here is the situation with
185 the ChaosKey inserted:&lt;/p&gt;
186
187 &lt;blockquote&gt;&lt;pre&gt;
188 % cat /proc/sys/kernel/random/entropy_avail; \
189 dd bs=1M if=/dev/random of=/dev/null count=1; \
190 for n in $(seq 1 5); do \
191 cat /proc/sys/kernel/random/entropy_avail; \
192 sleep 1; \
193 done
194 1079
195 0+1 oppføringer inn
196 0+1 oppføringer ut
197 104 byte kopiert, 0,000487647 s, 213 kB/s
198 433
199 1028
200 1031
201 1035
202 1038
203 %
204 &lt;/pre&gt;&lt;/blockquote&gt;
205
206 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
207 someone want to buy one here in Norway. :)&lt;/p&gt;
208
209 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
210 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
211 recording illuminating&lt;/a&gt;. It explains exactly what the source of
212 randomness is, if you are unable to spot it from the schema drawing
213 available from the ChaosKey web site linked at the start of this blog
214 post.&lt;/p&gt;
215 </description>
216 </item>
217
218 <item>
219 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
220 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
221 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
222 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
223 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
224 web servers, and who own the network equipment it is flowing through?
225 It is possible to get a glimpse of this from using traceroute, but it
226 is hard to find all the details. Many years ago, I wrote a system to
227 map the Norwegian Internet (trying to figure out if our plans for a
228 network game service would get low enough latency, and who we needed
229 to talk to about setting up game servers close to the users. Back
230 then I used traceroute output from many locations (I asked my friends
231 to run a script and send me their traceroute output) to create the
232 graph and the map. The output from traceroute typically look like
233 this:
234
235 &lt;p&gt;&lt;pre&gt;
236 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
237 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
238 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
239 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
240 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
241 5 he16-1-1.cr1.san110.as2116.net (195.0.244.234) 2.627 ms he16-1-1.cr2.oslosda310.as2116.net (195.0.244.48) 3.172 ms he16-1-1.cr1.san110.as2116.net (195.0.244.234) 2.857 ms
242 6 ae1.ar8.oslosda310.as2116.net (195.0.242.39) 0.662 ms 0.637 ms ae0.ar8.oslosda310.as2116.net (195.0.242.23) 0.622 ms
243 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
244 8 * * *
245 9 * * *
246 [...]
247 &lt;/pre&gt;&lt;/p&gt;
248
249 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
250 network equipment involved in getting the data traffic from me to the
251 www.stortinget.no server, and how long it took in milliseconds for a
252 package to reach the equipment and return to me. Three packages are
253 sent, and some times the packages do not follow the same path. This
254 is shown for hop 5, where three different IP addresses replied to the
255 traceroute request.&lt;/p&gt;
256
257 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
258 implementations I use are traceroute (using ICMP packages) mtr (can do
259 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
260 traceroute and a lot of other capabilities). All of them are easily
261 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
262
263 &lt;p&gt;This time around, I wanted to know the geographic location of
264 different route points, to visualize how visiting a web page spread
265 information about the visit to a lot of servers around the globe. The
266 background is that a web site today often will ask the browser to get
267 from many servers the parts (for example HTML, JSON, fonts,
268 JavaScript, CSS, video) required to display the content. This will
269 leak information about the visit to those controlling these servers
270 and anyone able to peek at the data traffic passing by (like your ISP,
271 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
272
273 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
274 www.stortinget.no. It is read daily by all members of parliament and
275 their staff, as well as political journalists, activits and many other
276 citizens of Norway. A visit to the www.stortinget.no web site will
277 ask your browser to contact 8 other servers: ajax.googleapis.com,
278 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
279 stats.g.doubleclick.net, www.google-analytics.com,
280 www.googletagmanager.com and www.netigate.se. I extracted this by
281 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
282 Stortinget web page and tell me all the URLs PhantomJS downloaded to
283 render the page (in HAR format using
284 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
285 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
286 to do this). My goal is to visualize network traces to all IP
287 addresses behind these DNS names, do show where visitors personal
288 information is spread when visiting the page.&lt;/p&gt;
289
290 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
291 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geoip-small.png&quot; alt=&quot;map of combined traces for URLs used by www.stortinget.no using GeoIP&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
292
293 &lt;p&gt;When I had a look around for options, I could not find any good
294 free software tools to do this, and decided I needed my own traceroute
295 wrapper outputting KML based on locations looked up using GeoIP. KML
296 is easy to work with and easy to generate, and understood by several
297 of the GIS tools I have available. I got good help from by NUUG
298 colleague Anders Einar with this, and the result can be seen in
299 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
300 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
301 free GeoIP databases I could find (and the for-pay databases my
302 friends had access to) is not up to the task. The IP addresses of
303 central Internet infrastructure would typically be placed near the
304 controlling companies main office, and not where the router is really
305 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
306 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
307
308 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;&lt;img
309 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy-small.png&quot; alt=&quot;scapy traceroute graph for URLs used by www.stortinget.no&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
310
311 &lt;p&gt;I also had a look at the visual traceroute graph created by
312 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
313 showing IP network ownership (aka AS owner) for the IP address in
314 question.
315 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
316 graph display a lot of useful information about the traceroute in SVG
317 format&lt;/a&gt;, and give a good indication on who control the network
318 equipment involved, but it do not include geolocation. This graph
319 make it possible to see the information is made available at least for
320 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
321 3 Communications and NetDNA.&lt;/p&gt;
322
323 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;https://geotraceroute.com/index.php?node=4&amp;host=www.stortinget.no&quot;&gt;&lt;img
324 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-small.png&quot; alt=&quot;example geotraceroute view for www.stortinget.no&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
325
326 &lt;p&gt;In the process, I came across the
327 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
328 Salim Gasmi. Its methology of combining guesses based on DNS names,
329 various location databases and finally use latecy times to rule out
330 candidate locations seemed to do a very good job of guessing correct
331 geolocation. But it could only do one trace at the time, did not have
332 a sensor in Norway and did not make the geolocations easily available
333 for postprocessing. So I contacted the developer and asked if he
334 would be willing to share the code (he refused until he had time to
335 clean it up), but he was interested in providing the geolocations in a
336 machine readable format, and willing to set up a sensor in Norway. So
337 since yesterday, it is possible to run traces from Norway in this
338 service thanks to a sensor node set up by
339 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
340 trace in KML format for further processing.&lt;/p&gt;
341
342 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-kml-join.kml&quot;&gt;&lt;img
343 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-kml-join.png&quot; alt=&quot;map of combined traces for URLs used by www.stortinget.no using geotraceroute&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
344
345 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
346 Denmark, Germany, Holland and Ireland. Plenty of places where the
347 Snowden confirmations verified the traffic is read by various actors
348 without your best interest as their top priority.&lt;/p&gt;
349
350 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
351 over all the hosts behind the urls imported by www.stortinget.no and
352 ask for the KML file from GeoTraceroute, and create a combined KML
353 file with all the traces (unfortunately only one of the IP addresses
354 behind the DNS name is traced this time. To get them all, one would
355 have to request traces using IP number instead of DNS names from
356 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
357
358 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
359 the IP traffic moves and who control the boxes involved in moving it.
360 And every time the link crosses for example the Swedish border, we can
361 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
362 Britain and NSA in USA and cables around the globe. (Hm, what should
363 we tell them? :) Keep that in mind if you ever send anything
364 unencrypted over the Internet.&lt;/p&gt;
365
366 &lt;p&gt;PS: KML files are drawn using
367 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
368 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
369 Marble. There are heaps of other options too.&lt;/p&gt;
370
371 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
372 activities, please send Bitcoin donations to my address
373 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
374 </description>
375 </item>
376
377 <item>
378 <title>Appstream just learned how to map hardware to packages too!</title>
379 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
380 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
381 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
382 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
383 readers probably know, I have been working on the
384 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
385 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
386 it easier for users to figure out what to install to get a given piece
387 of hardware to work in Debian, and a key part of this system is a way
388 to map hardware to packages. Isenkram have its own mapping database,
389 and also uses data provided by each package using the AppStream
390 metadata format. And today,
391 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
392 Debian learned to look up hardware the same way Isenkram is doing it,
393 ie using fnmatch():&lt;/p&gt;
394
395 &lt;p&gt;&lt;pre&gt;
396 % appstreamcli what-provides modalias \
397 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
398 Identifier: pymissile [generic]
399 Name: pymissile
400 Summary: Control original Striker USB Missile Launcher
401 Package: pymissile
402 % appstreamcli what-provides modalias usb:v0694p0002d0000
403 Identifier: libnxt [generic]
404 Name: libnxt
405 Summary: utility library for talking to the LEGO Mindstorms NXT brick
406 Package: libnxt
407 ---
408 Identifier: t2n [generic]
409 Name: t2n
410 Summary: Simple command-line tool for Lego NXT
411 Package: t2n
412 ---
413 Identifier: python-nxt [generic]
414 Name: python-nxt
415 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
416 Package: python-nxt
417 ---
418 Identifier: nbc [generic]
419 Name: nbc
420 Summary: C compiler for LEGO Mindstorms NXT bricks
421 Package: nbc
422 %
423 &lt;/pre&gt;&lt;/p&gt;
424
425 &lt;p&gt;A similar query can be done using the combined AppStream and
426 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
427
428 &lt;p&gt;&lt;pre&gt;
429 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
430 pymissile
431 % isenkram-lookup usb:v0694p0002d0000
432 libnxt
433 nbc
434 python-nxt
435 t2n
436 %
437 &lt;/pre&gt;&lt;/p&gt;
438
439 &lt;p&gt;You can find modalias values relevant for your machine using
440 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
441
442 &lt;p&gt;If you want to make this system a success and help Debian users
443 make the most of the hardware they have, please
444 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
445 AppStream metadata for your package following the guidelines&lt;/a&gt;
446 documented in the wiki. So far only 11 packages provide such
447 information, among the several hundred hardware specific packages in
448 Debian. The Isenkram database on the other hand contain 101 packages,
449 mostly related to USB dongles. Most of the packages with hardware
450 mapping in AppStream are LEGO Mindstorms related, because I have, as
451 part of my involvement in
452 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
453 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
454 complete set of packages in Debian for that particular hardware. The
455 team also got a nice Christmas present today. The
456 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
457 package&lt;/a&gt; made it into Debian. With this package in place, it is
458 now possible to use the LEGO Mindstorms NXT unit with only free
459 software, as the nxt-firmware package contain the source and firmware
460 binaries for the NXT brick.&lt;/p&gt;
461
462 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
463 activities, please send Bitcoin donations to my address
464 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
465 </description>
466 </item>
467
468 <item>
469 <title>Isenkram updated with a lot more hardware-package mappings</title>
470 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
471 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
472 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
473 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
474 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
475 and install packages to get your hardware dongles to work, is still
476 going strong. It is a system to look up the hardware present on or
477 connected to the current system, and map the hardware to Debian
478 packages. It can either be done using the tools in isenkram-cli or
479 using the user space daemon in the isenkram package. The latter will
480 notify you, when inserting new hardware, about what packages to
481 install to get the dongle working. It will even provide a button to
482 click on to ask packagekit to install the packages.&lt;/p&gt;
483
484 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
485
486 &lt;p&gt;&lt;pre&gt;
487 % isenkram-lookup
488 bluez
489 cheese
490 ethtool
491 fprintd
492 fprintd-demo
493 gkrellm-thinkbat
494 hdapsd
495 libpam-fprintd
496 pidgin-blinklight
497 thinkfan
498 tlp
499 tp-smapi-dkms
500 tp-smapi-source
501 tpb
502 %
503 &lt;/pre&gt;&lt;/p&gt;
504
505 &lt;p&gt;It can also list the firware package providing firmware requested
506 by the load kernel modules, which in my case is an empty list because
507 I have all the firmware my machine need:
508
509 &lt;p&gt;&lt;pre&gt;
510 % /usr/sbin/isenkram-autoinstall-firmware -l
511 info: did not find any firmware files requested by loaded kernel modules. exiting
512 %
513 &lt;/pre&gt;&lt;/p&gt;
514
515 &lt;p&gt;The last few days I had a look at several of the around 250
516 packages in Debian with udev rules. These seem like good candidates
517 to install when a given hardware dongle is inserted, and I found
518 several that should be proposed by isenkram. I have not had time to
519 check all of them, but am happy to report that now there are 97
520 packages packages mapped to hardware by Isenkram. 11 of these
521 packages provide hardware mapping using AppStream, while the rest are
522 listed in the modaliases file provided in isenkram.&lt;/p&gt;
523
524 &lt;p&gt;These are the packages with hardware mappings at the moment. The
525 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
526 support using AppStream, for everyone to use:&lt;/p&gt;
527
528 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
529 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
530 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
531 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
532 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
533 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
534 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
535 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
536 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
537 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
538 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
539 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
540 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
541 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
542 pcscd, pidgin-blinklight, printer-driver-splix,
543 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
544 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
545 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
546 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
547 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
548 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
549 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
550 xserver-xorg-video-vmware, yubikey-personalization and
551 zd1211-firmware&lt;/p&gt;
552
553 &lt;p&gt;If you know of other packages, please let me know with a wishlist
554 bug report against the isenkram-cli package, and ask the package
555 maintainer to
556 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
557 metadata according to the guidelines&lt;/a&gt; to provide the information
558 for everyone. In time, I hope to get rid of the isenkram specific
559 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
560
561 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
562 much hardware, and suggest that the package with with any ethernet
563 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
564 the details. I hope the maintainer find time to address it soon. In
565 the mean time I provide an override in isenkram.&lt;/p&gt;
566 </description>
567 </item>
568
569 <item>
570 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
571 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
572 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
573 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
574 <description>&lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-12-11-nice-oolite.png&quot;/&gt;&lt;/p&gt;
575
576 &lt;p&gt;In my early years, I played
577 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
578 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
579 space, and reached the &#39;elite&#39; fighting status before I moved on. The
580 original Elite game was available on Commodore 64 and the IBM PC
581 edition I played had a 64 KB executable. I am still impressed today
582 that the authors managed to squeeze both a 3D engine and details about
583 more than 2000 planet systems across 7 galaxies into a binary so
584 small.&lt;/p&gt;
585
586 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
587 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
588 really have time to test it properly until a few days ago. It was
589 great to discover that my old knowledge about trading routes were
590 still valid. But my fighting and flying abilities were gone, so I had
591 to retrain to be able to dock on a space station. And I am still not
592 able to make much resistance when I am attacked by pirates, so I
593 bougth and mounted the most powerful laser in the rear to be able to
594 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
595
596 &lt;p&gt;When playing Elite in the late eighties, I had to discover
597 everything on my own, and I had long lists of prices seen on different
598 planets to be able to decide where to trade what. This time I had the
599 advantages of the
600 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
601 where information about each planet is easily available with common
602 price ranges and suggested trading routes. This improved my ability
603 to earn money and I have been able to earn enough to buy a lot of
604 useful equipent in a few days. I believe I originally played for
605 months before I could get a docking computer, while now I could get it
606 after less then a week.&lt;/p&gt;
607
608 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
609 space, you should try out Oolite. It is available for Linux, MacOSX
610 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
611
612 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
613 activities, please send Bitcoin donations to my address
614 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
615 </description>
616 </item>
617
618 <item>
619 <title>Quicker Debian installations using eatmydata</title>
620 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
621 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
622 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
623 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
624 installation system, observing how using
625 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
626 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
627 speedup around 20-40 percent for Debian Edu, where we install around
628 1000 packages from within the installer. The eatmydata package
629 provide a way to disable/delay file system flushing. This is a bit
630 risky in the general case, as files that should be stored on disk will
631 stay only in memory a bit longer than expected, causing problems if a
632 machine crashes at an inconvenient time. But for an installation, if
633 the machine crashes during installation the process is normally
634 restarted, and avoiding disk operations as much as possible to speed
635 up the process make perfect sense.
636
637 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
638 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
639 but did not have time to push it any further. But a few months ago I
640 picked it up again and worked with the libeatmydata package maintainer
641 Mattia Rizzolo to make it easier for everyone to get this installation
642 speedup in Debian. Thanks to our cooperation There is now an
643 eatmydata-udeb package in Debian testing and unstable, and simply
644 enabling/installing it in debian-installer (d-i) is enough to get the
645 quicker installations. It can be enabled using preseeding. The
646 following untested kernel argument should do the trick:&lt;/p&gt;
647
648 &lt;blockquote&gt;&lt;pre&gt;
649 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
650 &lt;/pre&gt;&lt;/blockquote&gt;
651
652 &lt;p&gt;This should ask d-i to install the package inside the d-i
653 environment early in the installation sequence. Having it installed
654 in d-i in turn will make sure the relevant scripts are called just
655 after debootstrap filled /target/ with the freshly installed Debian
656 system to configure apt to run dpkg with eatmydata. This is enough to
657 speed up the installation process. There is a proposal to
658 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
659 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
660 tested its impact.&lt;/p&gt;
661
662 </description>
663 </item>
664
665 <item>
666 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
667 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
668 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
669 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
670 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
671 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
672 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
673 elever over det ganske land skal levere inn hvert år. Det mange ikke
674 vet er at selv om de kommersielle alternativene
675 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
676 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
677 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
678 utmerket fri programvarealternativ som kan. Oversetterverktøyet
679 Apertium har støtte for en rekke språkkombinasjoner, og takket være
680 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
681 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
682 nynorsk, og få den automatoversatt til det andre skriftspråket.
683 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
684 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
685 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
686 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
687 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
688 teksten din i webskjemaet der.
689
690 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
691 teknologien kan du enten installere pakken
692 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
693 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
694 api.apertium.org. Se
695 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
696 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
697 denne teksten som ble skrevet på bokmål over maskinoversatt til
698 nynorsk.&lt;/p&gt;
699
700 &lt;hr/&gt;
701
702 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
703 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
704 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
705 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
706 veit er at sjølv om dei kommersielle alternativa
707 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
708 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
709 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
710 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
711 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
712 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
713 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
714 nynorsk, og få den *automatoversatt til det andre skriftspråket.
715 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
716 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
717 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
718 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
719 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
720 teksta di i *webskjemaet der.
721
722 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
723 teknologien kan du anten installera pakken
724 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
725 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
726 *api.*apertium.org. Sjå
727 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
728 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
729 for denne teksta som vart skreva på bokmål over *maskinoversatt til
730 nynorsk.&lt;/p&gt;
731 </description>
732 </item>
733
734 <item>
735 <title>Coz profiler for multi-threaded software is now in Debian</title>
736 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
737 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
738 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
739 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
740 profiler able to run benchmarking experiments on the instrumented
741 multi-threaded program, finally
742 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
743 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
744 months since
745 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html&quot;&gt;I
746 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
747 it suitable for Debian. There are still issues with clang
748 compatibility, inline assembly only working x86 and minimized
749 JavaScript libraries.&lt;/p&gt;
750
751 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
752
753 &lt;p&gt;&lt;blockquote&gt;
754 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
755 &lt;/blockquote&gt;&lt;/p&gt;
756
757 &lt;p&gt;This will produce a profile.coz file in the current working
758 directory with the profiling information. This is then given to a
759 JavaScript application provided in the package and available from
760 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
761 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
762
763 &lt;p&gt;&lt;blockquote&gt;
764 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
765 &lt;/blockquote&gt;&lt;/p&gt;
766
767 &lt;p&gt;See the project home page and the
768 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
769 ;login: article on Coz&lt;/a&gt; for more information on how it is
770 working.&lt;/p&gt;
771 </description>
772 </item>
773
774 <item>
775 <title>My own self balancing Lego Segway</title>
776 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
777 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
778 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
779 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
780 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
781 present. It had been on my wishlist for a while, because I wanted to
782 build a Segway like balancing lego robot. I had already built
783 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
784 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
785 NXT kit as the balance sensor, but it was not working very well. It
786 could balance for a while, but was very sensitive to the light
787 condition in the room and the reflective properties of the surface and
788 would fall over after a short while. I wanted something more robust,
789 and had
790 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
791 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
792 wishlist for some years before it suddenly showed up as a gift from my
793 loved ones. :)&lt;/p&gt;
794
795 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
796 since then. But that changed some days ago, when I was searching for
797 lego segway information and came across a recipe from HiTechnic for
798 building
799 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
800 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
801 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
802 code&lt;/a&gt; was included, so it was just a question of putting it all
803 together. And thanks to the great work of many Debian developers, the
804 compiler needed to build the source for the NXT is already included in
805 Debian, so I was read to go in less than an hour. The resulting robot
806 do not look very impressive in its simplicity:&lt;/p&gt;
807
808 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-robot.jpeg&quot;&gt;&lt;/p&gt;
809
810 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
811 design from HiTechnic, I had to comment out the last task
812 (taskControl). I simply placed /* and */ around it get the program
813 working without that sensor present. Now it balances just fine until
814 the battery status run low:&lt;/p&gt;
815
816 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
817 &lt;source src=&quot;http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-balancing.ogv&quot; type=&quot;video/ogg&quot;&gt;
818 &lt;/video&gt;&lt;/p&gt;
819
820 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
821 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
822
823 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
824 they need to work with LEGO in Debian and all our derivative
825 distributions like Ubuntu, check out
826 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
827 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
828 RCX and NXT controller (no EV3), and would like to make sure the
829 Debian tools needed to program the systems I own work as they
830 should.&lt;/p&gt;
831 </description>
832 </item>
833
834 <item>
835 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
836 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
837 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
838 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
839 <description>&lt;p&gt;In July
840 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html&quot;&gt;I
841 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
842 the ability to receive SMS messages (aka without a cell phone). It is
843 time to share some experiences and provide an updated setup.&lt;/p&gt;
844
845 &lt;p&gt;The Signal app have worked fine for several months now, and I use
846 it regularly to chat with my loved ones. I had a major snag at the
847 end of my summer vacation, when the the app completely forgot my
848 setup, identity and keys. The reason behind this major mess was
849 running out of disk space. To avoid that ever happening again I have
850 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
851 roll back to an earlier version if the files are wiped by mistake. I
852 had to use it once after introducing the git backup. When rolling
853 back to an earlier version, one need to use the &#39;reset session&#39; option
854 in Signal to get going, and notify the people you talk with about the
855 problem. I assume there is some sequence number tracking in the
856 protocol to detect rollback attacks. The git repository is rather big
857 (674 MiB so far), but I have not tried to figure out if some of the
858 content can be added to a .gitignore file due to lack of spare
859 time.&lt;/p&gt;
860
861 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
862 make it impossible to send messages using Signal. I could still
863 receive them, but had to patch the code with a new timestamp to send.
864 I believe the timeout is added by the developers to force people to
865 upgrade to the latest version of the app, even when there is no
866 protocol changes, to reduce the version skew among the user base and
867 thus try to keep the number of support requests down.&lt;/p&gt;
868
869 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
870 making the old patch fail to apply cleanly. Below is an updated
871 patch, including the shell wrapper I use to start Signal. The
872 original version required a new user to locate the JavaScript console
873 and call a function from there. I got help from a friend with more
874 JavaScript knowledge than me to modify the code to provide a GUI
875 button instead. This mean that to get started you just need to run
876 the wrapper and click the &#39;Register without mobile phone&#39; to get going
877 now. I&#39;ve also modified the timeout code to always set it to 90 days
878 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
879
880 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
881
882 &lt;ol&gt;
883
884 &lt;li&gt;First, install required packages to get the source code and the
885 browser you need. Signal only work with Chrome/Chromium, as far as I
886 know, so you need to install it.
887
888 &lt;pre&gt;
889 apt install git tor chromium
890 git clone https://github.com/WhisperSystems/Signal-Desktop.git
891 &lt;/pre&gt;&lt;/li&gt;
892
893 &lt;li&gt;Modify the source code using command listed in the the patch
894 block below.&lt;/li&gt;
895
896 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
897 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
898
899 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
900 number you can receive calls to the next minute, receive the
901 verification code and enter it into the form field and press
902 &#39;Register&#39;. Note, the phone number you use will be user Signal
903 username, ie the way others can find you on Signal.&lt;/li&gt;
904
905 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
906 not show up in the contact list until you restart Signal, and there is
907 no way to assign names to Contacts. There is also no way to create or
908 update chat groups. I suspect this is because the web app do not have
909 a associated contact database.&lt;/li&gt;
910
911 &lt;/ol&gt;
912
913 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
914 main author moxie0 reject federation and accept dependencies to major
915 corporations like Google (part of the code is fetched from Google) and
916 Amazon (the central coordination point is owned by Amazon). See for
917 example
918 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
919 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
920 view on these issues. But the network effect is strong in this case,
921 and several of the people I want to communicate with already use
922 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
923 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
924 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
925 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
926 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
927 working on Debian Stable.&lt;/p&gt;
928
929 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
930 working. It switch to the production servers, disable to timeout,
931 make registration easier and add the shell wrapper:&lt;/p&gt;
932
933 &lt;pre&gt;
934 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
935 diff --git a/js/background.js b/js/background.js
936 index 24b4c1d..579345f 100644
937 --- a/js/background.js
938 +++ b/js/background.js
939 @@ -33,9 +33,9 @@
940 });
941 });
942
943 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
944 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
945 var SERVER_PORTS = [80, 4433, 8443];
946 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
947 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
948 var messageReceiver;
949 window.getSocketStatus = function() {
950 if (messageReceiver) {
951 diff --git a/js/expire.js b/js/expire.js
952 index 639aeae..beb91c3 100644
953 --- a/js/expire.js
954 +++ b/js/expire.js
955 @@ -1,6 +1,6 @@
956 ;(function() {
957 &#39;use strict&#39;;
958 - var BUILD_EXPIRATION = 0;
959 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
960
961 window.extension = window.extension || {};
962
963 diff --git a/js/views/install_view.js b/js/views/install_view.js
964 index 7816f4f..1d6233b 100644
965 --- a/js/views/install_view.js
966 +++ b/js/views/install_view.js
967 @@ -38,7 +38,8 @@
968 return {
969 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
970 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
971 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
972 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
973 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
974 };
975 },
976 clearQR: function() {
977 diff --git a/options.html b/options.html
978 index dc0f28e..8d709f6 100644
979 --- a/options.html
980 +++ b/options.html
981 @@ -14,7 +14,10 @@
982 &amp;lt;div class=&#39;nav&#39;&gt;
983 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
984 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
985 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
986 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
987 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
988 +
989 + &amp;lt;/div&gt;
990 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
991 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
992 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
993 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
994 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
995 @@ -0,0 +1,12 @@
996 +#!/bin/sh
997 +set -e
998 +cd $(dirname $0)
999 +mkdir -p userdata
1000 +userdata=&quot;`pwd`/userdata&quot;
1001 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
1002 + (cd $userdata &amp;&amp; git init)
1003 +fi
1004 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
1005 +exec chromium \
1006 + --proxy-server=&quot;socks://localhost:9050&quot; \
1007 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1008 EOF
1009 chmod a+rx run-signal-app
1010 &lt;/pre&gt;
1011
1012 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1013 activities, please send Bitcoin donations to my address
1014 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1015 </description>
1016 </item>
1017
1018 <item>
1019 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
1020 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
1021 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
1022 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
1023 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
1024 system&lt;/a&gt; provide a practical and easy way to figure out which
1025 packages support the hardware in a given machine. The command line
1026 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
1027 convenient way to list and install packages relevant for the current
1028 hardware during system installation, both user space packages and
1029 firmware packages. The GUI background daemon on the other hand provide
1030 a pop-up proposing to install packages when a new dongle is inserted
1031 while using the computer. For example, if you plug in a smart card
1032 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
1033 that package isn&#39;t already installed, and if you plug in a USB video
1034 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
1035 cheese is currently missing. This already work just fine.&lt;/p&gt;
1036
1037 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
1038 package names. When I started no such database existed in Debian, so
1039 I made my own data set and included it with the isenkram package and
1040 made isenkram fetch the latest version of this database from git using
1041 http. This way the isenkram users would get updated package proposals
1042 as soon as I learned more about hardware related packages.&lt;/p&gt;
1043
1044 &lt;p&gt;The hardware is identified using modalias strings. The modalias
1045 design is from the Linux kernel where most hardware descriptors are
1046 made available as a strings that can be matched using filename style
1047 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1048 identifiers.&lt;/p&gt;
1049
1050 &lt;p&gt;The downside to the Isenkram specific database is that there is no
1051 information about relevant distribution / Debian version, making
1052 isenkram propose obsolete packages too. But along came AppStream, a
1053 cross distribution mechanism to store and collect metadata about
1054 software packages. When I heard about the proposal, I contacted the
1055 people involved and suggested to add a hardware matching rule using
1056 modalias strings in the specification, to be able to use AppStream for
1057 mapping hardware to packages. This idea was accepted and AppStream is
1058 now a great way for a package to announce the hardware it support in a
1059 distribution neutral way. I wrote
1060 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html&quot;&gt;a
1061 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
1062 December. If you have a hardware related package in Debian, please
1063 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
1064
1065 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
1066 RCX or NXT unit, announce this support using AppStream. The effect is
1067 that when you insert such LEGO robot controller into your Debian
1068 machine, Isenkram will propose to install the packages needed to get
1069 it working. The intention is that this should allow the local user to
1070 start programming his robot controller right away without having to
1071 guess what packages to use or which permissions to fix.&lt;/p&gt;
1072
1073 &lt;p&gt;But when I sat down with my son the other day to program our NXT
1074 unit using his Debian Stretch computer, I discovered something
1075 annoying. The local console user (ie my son) did not get access to
1076 the USB device for programming the unit. This used to work, but no
1077 longer in Jessie and Stretch. After some investigation and asking
1078 around on #debian-devel, I discovered that this was because udev had
1079 changed the mechanism used to grant access to local devices. The
1080 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
1081 no longer applied, because LDAP users no longer was added to the
1082 plugdev group during login. Michael Biebl told me that this method
1083 was obsolete and the new method used ACLs instead. This was good
1084 news, as the plugdev mechanism is a mess when using a remote user
1085 directory like LDAP. Using ACLs would make sure a user lost device
1086 access when she logged out, even if the user left behind a background
1087 process which would retain the plugdev membership with the ConsoleKit
1088 setup. Armed with this knowledge I moved on to fix the access problem
1089 for the LEGO Mindstorms related packages.&lt;/p&gt;
1090
1091 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
1092 applied directly for a device, or is applied in
1093 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
1094 LEGO Mindstorms udev rules did not have a class, I decided to add the
1095 tag directly in the udev rules files included in the packages. Here
1096 is one example. For the nqc C compiler for the RCX, the
1097 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
1098
1099 &lt;p&gt;&lt;pre&gt;
1100 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
1101 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
1102 &lt;/pre&gt;&lt;/p&gt;
1103
1104 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
1105 packages using plugdev in their /lib/udev/rules.d/ files should be
1106 changed to use this tag (either directly or indirectly via
1107 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
1108 to detect this?&lt;/p&gt;
1109
1110 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
1111 It is unclear to me if the uaccess tag is an internal implementation
1112 detail like the udev-acl tag used by
1113 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
1114 indirect method is the preferred way. Michael
1115 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
1116 documentation from the systemd project&lt;/a&gt; and I hope it will make
1117 this clearer. For now I use the generic classes when they exist and
1118 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
1119 directly if no such class exist.&lt;/p&gt;
1120
1121 &lt;p&gt;To learn more about the isenkram system, please check out
1122 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
1123 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
1124
1125 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
1126 please join us on our IRC channel
1127 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
1128 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
1129 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
1130 list is not yet created, but we are working on it. :)&lt;/p&gt;
1131
1132 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1133 activities, please send Bitcoin donations to my address
1134 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1135 </description>
1136 </item>
1137
1138 <item>
1139 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
1140 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
1141 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</guid>
1142 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
1143 <description>&lt;p&gt;In April we
1144 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html&quot;&gt;started
1145 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
1146 how to set up and administrate a Debian system. Today I am happy to
1147 report that the first draft is now publicly available. You can find
1148 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
1149 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
1150 eight chapters have a first draft translation, and we are working on
1151 proofreading the content. If you want to help out, please start
1152 contributing using
1153 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
1154 hosted weblate project page&lt;/a&gt;, and get in touch using
1155 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
1156 translators mailing list&lt;/a&gt;. Please also check out
1157 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
1158 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
1159 and update weblate if you find errors.&lt;/p&gt;
1160
1161 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
1162 electronic form.&lt;/p&gt;
1163 </description>
1164 </item>
1165
1166 <item>
1167 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
1168 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
1169 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
1170 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
1171 <description>&lt;p&gt;This summer, I read a great article
1172 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
1173 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
1174 how to profile multi-threaded programs. It presented a system for
1175 profiling software by running experiences in the running program,
1176 testing how run time performance is affected by &quot;speeding up&quot; parts of
1177 the code to various degrees compared to a normal run. It does this by
1178 slowing down parallel threads while the &quot;faster up&quot; code is running
1179 and measure how this affect processing time. The processing time is
1180 measured using probes inserted into the code, either using progress
1181 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1182 can also measure unmodified code by measuring complete the program
1183 runtime and running the program several times instead.&lt;/p&gt;
1184
1185 &lt;p&gt;The project and presentation was so inspiring that I would like to
1186 get the system into Debian. I
1187 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
1188 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
1189 system ready for Debian by sending patches. The build process need to
1190 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
1191 to include the JavaScript web page used to visualize the collected
1192 profiling information included in the source package.
1193 But I expect that should work out fairly soon.&lt;/p&gt;
1194
1195 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
1196 on a binary with debug symbols available, start the program like this:
1197
1198 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1199 coz run --- program-to-run
1200 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1201
1202 &lt;p&gt;This will create a text file profile.coz with the instrumentation
1203 information. To show what part of the code affect the performance
1204 most, use a web browser and either point it to
1205 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
1206 or use the copy from git (in the gh-pages branch). Check out this web
1207 site to have a look at several example profiling runs and get an idea what the end result from the profile runs look like. To make the
1208 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
1209 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1210 code, rebuild and run the profiler. This allow coz to do more
1211 targeted experiments.&lt;/p&gt;
1212
1213 &lt;p&gt;A video published by ACM
1214 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
1215 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
1216 from the 25th Symposium on Operating Systems Principles available
1217 titled
1218 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
1219 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
1220
1221 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
1222 for Coz is available from github. It will only build with clang
1223 because it uses a
1224 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
1225 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
1226 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
1227 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
1228
1229 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
1230 of software in Debian. I would very much like some help with the
1231 packaging effort, as I lack the in depth knowledge on how to package
1232 C++ libraries.&lt;/p&gt;
1233 </description>
1234 </item>
1235
1236 <item>
1237 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
1238 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
1239 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
1240 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
1241 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1242 to be a slight challenge. Here is the recipe if I ever need to do it
1243 again. It all started by me wanting to try the recipe to set up
1244 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
1245 hardened Android installation&lt;/a&gt; from the Tor project blog on a
1246 device I had access to. It is a old mobile phone with a broken
1247 microphone The initial idea had been to just
1248 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
1249 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
1250 until a few days ago.&lt;/p&gt;
1251
1252 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
1253 loader (press volume down and power at the same time), (2) select
1254 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
1255 machine, (4) request the device identifier token by running &#39;fastboot
1256 oem get_identifier_token&#39;, (5) request the device unlocking key using
1257 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
1258 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
1259
1260 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
1261 or newer, and the device I was working on had 2.00.0027. This
1262 apparently can be easily fixed by downloading a Windows program and
1263 running it on your Windows machine, if you accept the terms Microsoft
1264 require you to accept to use Windows - which I do not. So I had to
1265 come up with a different approach. I got a lot of help from AndyCap
1266 on #nuug, and would not have been able to get this working without
1267 him.&lt;/p&gt;
1268
1269 &lt;p&gt;First I needed to extract the hboot firmware from
1270 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
1271 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
1272 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
1273 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
1274 recognise the file format, but unruu worked and extracted rom.zip,
1275 containing the new hboot firmware and a text file describing which
1276 devices it would work for.&lt;/p&gt;
1277
1278 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
1279 followed some instructions
1280 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
1281 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
1282 machine with Debian testing:&lt;/p&gt;
1283
1284 &lt;p&gt;&lt;pre&gt;
1285 adb reboot-bootloader
1286 fastboot oem rebootRUU
1287 fastboot flash zip rom.zip
1288 fastboot flash zip rom.zip
1289 fastboot reboot
1290 &lt;/pre&gt;&lt;/p&gt;
1291
1292 &lt;p&gt;The flash command apparently need to be done twice to take effect,
1293 as the first is just preparations and the second one do the flashing.
1294 The adb command is just to get to the boot loader menu, so turning the
1295 device on while holding volume down and the power button should work
1296 too.&lt;/p&gt;
1297
1298 &lt;p&gt;With the new hboot version in place I could start following the
1299 instructions on the HTC developer web site. I got the device token
1300 like this:&lt;/p&gt;
1301
1302 &lt;p&gt;&lt;pre&gt;
1303 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
1304 &lt;/pre&gt;
1305
1306 &lt;p&gt;And once I got the unlock code via email, I could use it like
1307 this:&lt;/p&gt;
1308
1309 &lt;p&gt;&lt;pre&gt;
1310 fastboot flash unlocktoken Unlock_code.bin
1311 &lt;/pre&gt;&lt;/p&gt;
1312
1313 &lt;p&gt;And with that final step in place, the phone was unlocked and I
1314 could start stuffing the software of my own choosing into the device.
1315 So far I only inserted a replacement recovery image to wipe the phone
1316 before I start. We will see what happen next. Perhaps I should
1317 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
1318 </description>
1319 </item>
1320
1321 <item>
1322 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
1323 <link>http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</link>
1324 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</guid>
1325 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
1326 <description>&lt;p&gt;For a while now, I have wanted to test
1327 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
1328 said to provide end to end encrypted communication and several of my
1329 friends and family are already using it. As I by choice do not own a
1330 mobile phone, this proved to be harder than expected. And I wanted to
1331 have the source of the client and know that it was the code used on my
1332 machine. But yesterday I managed to get it working. I used the
1333 Github source, compared it to the source in
1334 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
1335 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
1336 patches to use the production Signal servers, started the app and
1337 asked for the hidden &quot;register without a smart phone&quot; form. Here is
1338 the recipe how I did it.&lt;/p&gt;
1339
1340 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
1341
1342 &lt;pre&gt;
1343 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1344 &lt;/pre&gt;
1345
1346 &lt;p&gt;Next, I patched the source to use the production servers, to be
1347 able to talk to other Signal users:&lt;/p&gt;
1348
1349 &lt;pre&gt;
1350 cat &amp;lt;&amp;lt;EOF | patch -p0
1351 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
1352 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
1353 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
1354 @@ -47,8 +47,8 @@
1355 });
1356 });
1357
1358 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
1359 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
1360 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
1361 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
1362 var messageReceiver;
1363 window.getSocketStatus = function() {
1364 if (messageReceiver) {
1365 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
1366 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
1367 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
1368 @@ -1,6 +1,6 @@
1369 ;(function() {
1370 &#39;use strict&#39;;
1371 - var BUILD_EXPIRATION = 0;
1372 + var BUILD_EXPIRATION = 1474492690000;
1373
1374 window.extension = window.extension || {};
1375
1376 EOF
1377 &lt;/pre&gt;
1378
1379 &lt;p&gt;The first part is changing the servers, and the second is updating
1380 an expiration timestamp. This timestamp need to be updated regularly.
1381 It is set 90 days in the future by the build process (Gruntfile.js).
1382 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
1383
1384 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
1385 script to launch Signal in Chromium.&lt;/p&gt;
1386
1387 &lt;pre&gt;
1388 #!/bin/sh
1389 cd $(dirname $0)
1390 mkdir -p userdata
1391 exec chromium \
1392 --proxy-server=&quot;socks://localhost:9050&quot; \
1393 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1394 &lt;/pre&gt;
1395
1396 &lt;p&gt; The script start the app and configure Chromium to use the Tor
1397 SOCKS5 proxy to make sure those controlling the Signal servers (today
1398 Amazon and Whisper Systems) as well as those listening on the lines
1399 will have a harder time location my laptop based on the Signal
1400 connections if they use source IP address.&lt;/p&gt;
1401
1402 &lt;p&gt;When the script starts, one need to follow the instructions under
1403 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
1404 repository. I right clicked on the Signal window to get up the
1405 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
1406 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
1407 registration form. Then I entered by land line phone number and
1408 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
1409 repeated the verification code three times. After entering the number
1410 into the verification code field in the form, I could start using
1411 Signal from my laptop.
1412
1413 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
1414 whom and thus who know who to those controlling the central server,
1415 but such leakage is hard to avoid with a centrally controlled server
1416 setup. It is something to keep in mind when using Signal - the
1417 content of your chats are harder to intercept, but the meta data
1418 exposing your contact network is available to people you do not know.
1419 So better than many options, but not great. And sadly the usage is
1420 connected to my land line, thus allowing those controlling the server
1421 to associate it to my home and person. I would prefer it if only
1422 those I knew could tell who I was on Signal. There are options
1423 avoiding such information leakage, but most of my friends are not
1424 using them, so I am stuck with Signal for now.&lt;/p&gt;
1425
1426 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
1427 on this topic in
1428 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html&quot;&gt;Experience
1429 and updated recipe for using the Signal app without a mobile
1430 phone&lt;/a&gt;.&lt;/p&gt;
1431 </description>
1432 </item>
1433
1434 <item>
1435 <title>The new &quot;best&quot; multimedia player in Debian?</title>
1436 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
1437 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
1438 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
1439 <description>&lt;p&gt;When I set out a few weeks ago to figure out
1440 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
1441 multimedia player in Debian claimed to support most file formats /
1442 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
1443 the various players claimed support for. The range was from 55 to 130
1444 MIME types. I suspect most media formats are supported by all
1445 players, but this is not really reflected in the MimeTypes values in
1446 their desktop files. There are probably also some bogus MIME types
1447 listed, but it is hard to identify which one this is.&lt;/p&gt;
1448
1449 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
1450 the players suggesting to add more MIME types to their desktop files,
1451 and decided to spend some time myself improving the situation for my
1452 favorite media player VLC. The fixes for VLC entered Debian unstable
1453 yesterday. The complete list of MIME types can be seen on the
1454 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
1455 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
1456
1457 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
1458 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1459 kmplayer. I am sure some of the other players desktop files support
1460 several of the formats currently listed as working only with vlc,
1461 toten and parole.&lt;/p&gt;
1462
1463 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
1464 supported by all the tested multimedia players in Debian in their
1465 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1466 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1467 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1468 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1469 it sad that video/ogg and video/webm is not supported by all the media
1470 players in Debian. As far as I can tell, all of them can handle both
1471 formats.&lt;/p&gt;
1472 </description>
1473 </item>
1474
1475 <item>
1476 <title>A program should be able to open its own files on Linux</title>
1477 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
1478 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
1479 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
1480 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
1481 decided to test its presentation tool when making the slides for a
1482 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1483 wrote the first draft of the slides, saved the result and went to bed
1484 the day before I would give the talk. The next day I took a plane to
1485 the location where the meeting should take place, and on the plane I
1486 started up koffice again to polish the talk a bit, only to discover
1487 that kpresenter refused to load its own data file. I cursed a bit and
1488 started making the slides again from memory, to have something to
1489 present when I arrived. I tested that the saved files could be
1490 loaded, and the day seemed to be rescued. I continued to polish the
1491 slides until I suddenly discovered that the saved file could no longer
1492 be loaded into kpresenter. In the end I had to rewrite the slides
1493 three times, condensing the content until the talk became shorter and
1494 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
1495 kpresenter wrote inline images in a way itself could not understand.
1496 Eventually that bug was fixed and kpresenter ended up being a great
1497 program to make slides. The point I&#39;m trying to make is that we
1498 expect a program to be able to load its own data files, and it is
1499 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
1500
1501 &lt;p&gt;Did you ever experience a program failing to load its own data
1502 files from the desktop file browser? It is not a uncommon problem. A
1503 while back I discovered that the screencast recorder
1504 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1505 browser would refuse to open. No video player claimed to understand
1506 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
1507 returning the application/ogg MIME type, which no video player I had
1508 installed listed as a MIME type they would understand. I asked for
1509 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
1510 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
1511 several video players to add video/ogg to their desktop files, to give
1512 the file browser an idea what to do about Ogg Theora files. After a
1513 while, the desktop file browsers in Debian started to handle the
1514 output from gtk-recordmydesktop properly.&lt;/p&gt;
1515
1516 &lt;p&gt;But history repeats itself. A few days ago I tested the music
1517 system Rosegarden again, and I discovered that the KDE and xfce file
1518 browsers did not know what to do with the Rosegarden project files
1519 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
1520 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
1521 included in the next upload. To increase the chance of me remembering
1522 how to fix the problem next time some program fail to load its files
1523 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
1524
1525 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
1526 There are two sources for the MIME type of a given file. The output from
1527 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
1528 shared MIME type registry (under /usr/share/mime/). The file MIME
1529 type is mapped to programs supporting the MIME type, and this
1530 information is collected from
1531 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
1532 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
1533 one desktop file claiming support for the MIME type of the file, it is
1534 activated when asking to open a given file. If there are more, one
1535 can normally select which one to use by right-clicking on the file and
1536 selecting the wanted one using &#39;Open with&#39; or similar. In general
1537 this work well. But it depend on each program picking a good MIME
1538 type (preferably
1539 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
1540 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
1541 registry recognizing the file and the desktop file to list the MIME
1542 type in its list of supported MIME types.&lt;/p&gt;
1543
1544 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
1545 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
1546 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
1547
1548 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1549 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
1550 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
1551 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
1552 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
1553 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
1554 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
1555 &amp;lt;/mime-type&amp;gt;
1556 &amp;lt;/mime-info&amp;gt;
1557 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1558
1559 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
1560 (it is a gzipped XML file). Note, it is much better to use an
1561 official MIME type registered with IANA than it is to make up ones own
1562 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
1563
1564 &lt;p&gt;The desktop file of the rosegarden program failed to list
1565 audio/x-rosegarden in its list of supported MIME types, causing the
1566 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
1567
1568 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1569 % grep Mime /usr/share/applications/rosegarden.desktop
1570 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1571 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1572 %
1573 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1574
1575 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
1576 MimeType= line.&lt;/p&gt;
1577
1578 &lt;p&gt;If you run into a file which fail to open the correct program when
1579 selected from the file browser, please check out the output from
1580 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
1581 MIME type is registered somewhere under /usr/share/mime/ and check
1582 that some desktop file under /usr/share/applications/ is claiming
1583 support for this MIME type. If not, please report a bug to have it
1584 fixed. :)&lt;/p&gt;
1585 </description>
1586 </item>
1587
1588 <item>
1589 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
1590 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
1591 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
1592 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
1593 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
1594 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
1595 related packages. The idea is to have a database of mappings between
1596 hardware and packages, and pop up a dialog suggesting for the user to
1597 install the packages to use a given hardware dongle. Some use cases
1598 are when you insert a Yubikey, it proposes to install the software
1599 needed to control it; when you insert a braille reader list it
1600 proposes to install the packages needed to send text to the reader;
1601 and when you insert a ColorHug screen calibrator it suggests to
1602 install the driver for it. The system work well, and even have a few
1603 command line tools to install firmware packages and packages for the
1604 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
1605
1606 &lt;p&gt;The system was initially written using aptdaemon, because I found
1607 good documentation and example code on how to use it. But aptdaemon
1608 is going away and is generally being replaced by
1609 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
1610 so Isenkram needed a rewrite. And today, thanks to the great patch
1611 from my college Sunil Mohan Adapa in the FreedomBox project, the
1612 rewrite finally took place. I&#39;ve just uploaded a new version of
1613 Isenkram into Debian Unstable with the patch included, and the default
1614 for the background daemon is now to use PackageKit. To check it out,
1615 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
1616 and see if it is recognised.&lt;/p&gt;
1617
1618 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
1619 the machine it is running on, you can check out the isenkram-lookup
1620 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
1621
1622 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1623 % isenkram-lookup
1624 bluez
1625 cheese
1626 fprintd
1627 fprintd-demo
1628 gkrellm-thinkbat
1629 hdapsd
1630 libpam-fprintd
1631 pidgin-blinklight
1632 thinkfan
1633 tleds
1634 tp-smapi-dkms
1635 tp-smapi-source
1636 tpb
1637 %p
1638 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1639
1640 &lt;p&gt;The hardware mappings come from several places. The preferred way
1641 is for packages to announce their hardware support using
1642 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
1643 cross distribution appstream system&lt;/a&gt;.
1644 See
1645 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
1646 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
1647 </description>
1648 </item>
1649
1650 <item>
1651 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
1652 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
1653 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
1654 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
1655 <description>&lt;p&gt;Yesterday I updated the
1656 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
1657 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
1658 enterprising users. There were some nice user and visible changes.
1659 First of all, both desktop menu entries now work. A design flaw in
1660 one of the script made the history graph fail to show up (its PNG was
1661 dumped in ~/.xsession-errors) if no controlling TTY was available.
1662 The script worked when called from the command line, but not when
1663 called from the desktop menu. I changed this to look for a DISPLAY
1664 variable or a TTY before deciding where to draw the graph, and now the
1665 graph window pop up as expected.&lt;/p&gt;
1666
1667 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
1668 graphs (the one showing the last few hours). New is also the user of
1669 colours showing charging in blue and discharge in red. The percentages
1670 of this graph is relative to last full charge, not battery design
1671 capacity.&lt;/p&gt;
1672
1673 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-05-23-battery-stats-rate.png&quot;/&gt;&lt;/p&gt;
1674
1675 &lt;p&gt;The other graph show the entire history of the collected battery
1676 statistics, comparing it to the design capacity of the battery to
1677 visualise how the battery life time get shorter over time. The red
1678 line in this graph is what the previous graph considers 100 percent:
1679
1680 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-05-23-battery-stats-history.png&quot;/&gt;&lt;/p&gt;
1681
1682 &lt;p&gt;In this graph you can see that I only charge the battery to 80
1683 percent of last full capacity, and how the capacity of the battery is
1684 shrinking. :(&lt;/p&gt;
1685
1686 &lt;p&gt;The last new feature is in the collector, which now will handle
1687 more hardware models. On some hardware, Linux power supply
1688 information is stored in /sys/class/power_supply/ACAD/, while the
1689 collector previously only looked in /sys/class/power_supply/AC/. Now
1690 both are checked to figure if there is power connected to the
1691 machine.&lt;/p&gt;
1692
1693 &lt;p&gt;If you are interested in how your laptop battery is doing, please
1694 check out the
1695 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
1696 in Debian unstable, or rebuild it on Jessie to get it working on
1697 Debian stable. :) The upstream source is available from &lt;a
1698 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1699 Patches are very welcome.&lt;/p&gt;
1700
1701 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1702 activities, please send Bitcoin donations to my address
1703 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1704 </description>
1705 </item>
1706
1707 <item>
1708 <title>Debian now with ZFS on Linux included</title>
1709 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
1710 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
1711 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
1712 <description>&lt;p&gt;Today, after many years of hard work from many people,
1713 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
1714 Debian. The package status can be seen on
1715 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
1716 for zfs-linux&lt;/a&gt;. and
1717 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
1718 team status page&lt;/a&gt;. If you want to help out, please join us.
1719 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
1720 source code&lt;/a&gt; is available via git on Alioth. It would also be
1721 great if you could help out with
1722 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
1723 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
1724 </description>
1725 </item>
1726
1727 <item>
1728 <title>What is the best multimedia player in Debian?</title>
1729 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
1730 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
1731 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
1732 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
1733 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
1734
1735 &lt;p&gt;A few years ago, I had a look at the media support for Browser
1736 plugins in Debian, to get an idea which plugins to include in Debian
1737 Edu. I created a script to extract the set of supported MIME types
1738 for each plugin, and used this to find out which multimedia browser
1739 plugin supported most file formats / media types.
1740 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
1741 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
1742 not been updated for a while. But browser plugins are less relevant
1743 these days, so I thought it was time to look at standalone
1744 players.&lt;/p&gt;
1745
1746 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
1747 player when I wanted to play videos from the Norwegian National
1748 Broadcasting Company, and decided to investigate why. The cause is a
1749 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
1750 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
1751 of MIME types announced in the desktop file and the browser plugin,
1752 only to discover that there is quite a large difference between the
1753 two for VLC. This discovery made me dig up the script I used to
1754 compare browser plugins, and adjust it to compare desktop files
1755 instead, to try to figure out which multimedia player in Debian
1756 support most file formats.&lt;/p&gt;
1757
1758 &lt;p&gt;The result can be seen on the Debian Wiki, as
1759 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
1760 table listing all MIME types supported by one of the packages included
1761 in the table&lt;/a&gt;, with the package supporting most MIME types being
1762 listed first in the table.&lt;/p&gt;
1763
1764 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
1765 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1766 kmplayer. Time for the other players to update their announced MIME
1767 support?&lt;/p&gt;
1768 </description>
1769 </item>
1770
1771 <item>
1772 <title>The Pyra - handheld computer with Debian preinstalled</title>
1773 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
1774 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
1775 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
1776 <description>A friend of mine made me aware of
1777 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
1778 handheld computer which will be delivered with Debian preinstalled. I
1779 would love to get one of those for my birthday. :)&lt;/p&gt;
1780
1781 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1782 plugs and many others connectors, and include a full keyboard and a 5&quot;
1783 LCD touch screen. The 6000mAh battery is claimed to provide a whole
1784 day of battery life time, but I have not seen any independent tests
1785 confirming this. The vendor is still collecting preorders, and the
1786 last I heard last night was that 22 more orders were needed before
1787 production started.&lt;/p&gt;
1788
1789 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
1790 Debian. Please let me know if you know of any others. Is it the
1791 first computer being sold with Debian preinstalled?&lt;/p&gt;
1792 </description>
1793 </item>
1794
1795 <item>
1796 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
1797 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
1798 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
1799 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
1800 <description>&lt;p&gt;During this weekends
1801 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
1802 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
1803 to make sure there are good books about Debian available in Norwegian
1804 Bokmål, and got in touch with the people behind the
1805 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
1806 project&lt;/a&gt; to get started. If you want to help out, please start
1807 contributing using
1808 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
1809 hosted weblate project page&lt;/a&gt;, and get in touch using
1810 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
1811 translators mailing list&lt;/a&gt;. Please also check out
1812 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
1813 contributors&lt;/a&gt;.&lt;/p&gt;
1814
1815 &lt;p&gt;The book is already available on paper in English, French and
1816 Japanese, and our goal is to get it available on paper in Norwegian
1817 Bokmål too. In addition to the paper edition, there are also EPUB and
1818 Mobi versions available. And there are incomplete translations
1819 available for many more languages.&lt;/p&gt;
1820 </description>
1821 </item>
1822
1823 <item>
1824 <title>One in two hundred Debian users using ZFS on Linux?</title>
1825 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
1826 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
1827 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
1828 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
1829 packages in Debian, and was quite surprised with what I found. I use
1830 ZFS myself at home, but did not really expect many others to do so.
1831 But I might be wrong.&lt;/p&gt;
1832
1833 &lt;p&gt;According to
1834 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
1835 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
1836 0.53% of the population, with the package installed. As far as I know
1837 the only use of the spl-linux package is as a support library for ZFS
1838 on Linux, so I use it here as proxy for measuring the number of ZFS
1839 installation on Linux in Debian. In the kFreeBSD variant of Debian
1840 the ZFS feature is already available, and there
1841 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
1842 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
1843 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
1844
1845 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
1846 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
1847 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
1848 cleared, the package is still not in Debian. The package is again in
1849 the NEW queue. Several uploads have been rejected so far because the
1850 debian/copyright file was incomplete or wrong, but there is no reason
1851 to give up. The current status can be seen on
1852 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
1853 team status page&lt;/a&gt;, and
1854 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
1855 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
1856
1857 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
1858 my home server can function in the future using only official Debian
1859 packages, and the current blocker is to get the debian/copyright file
1860 accepted by the FTP masters in Debian, I decided a while back to try
1861 to help out the team. This was the background for my blog post about
1862 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
1863 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
1864 used the techniques I explored there to try to find any errors in the
1865 copyright file. It is not very easy to check every one of the around
1866 2000 files in the source package, but I hope we this time got it
1867 right. If you want to help out, check out the git source and try to
1868 find missing entries in the debian/copyright file.&lt;/p&gt;
1869 </description>
1870 </item>
1871
1872 <item>
1873 <title>Full battery stats collector is now available in Debian</title>
1874 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
1875 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
1876 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
1877 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
1878 extended collector that will collect the complete battery history for
1879 later processing and graphing. The original collector store the
1880 battery level as percentage of last full level, while the new
1881 collector also record battery vendor, model, serial number, design
1882 full level, last full level and current battery level. This make it
1883 possible to predict the lifetime of the battery as well as visualise
1884 the energy flow when the battery is charging or discharging.&lt;/p&gt;
1885
1886 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
1887 in the version 0.5.1 package in unstable. Get the new battery level graph
1888 and lifetime prediction by running:
1889
1890 &lt;p&gt;&lt;pre&gt;
1891 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1892 &lt;/pre&gt;&lt;/p&gt;
1893
1894 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
1895
1896 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
1897 entry yet):&lt;/p&gt;
1898
1899 &lt;p&gt;&lt;pre&gt;
1900 /usr/share/battery-stats/battery-stats-graph-flow
1901 &lt;/pre&gt;&lt;/p&gt;
1902
1903 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
1904 when there are few data points. The graphs look a bit better with a
1905 few years of data.&lt;/p&gt;
1906
1907 &lt;p&gt;A while back one important feature I use in the battery stats
1908 collector broke in Debian. The scripts in
1909 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
1910 suspect it happened when Jessie started using systemd, but I do not
1911 know. The issue is reported as
1912 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
1913 pm-utils. I managed to work around it by adding an udev rule to call
1914 the collector script every time the power connector is connected and
1915 disconnected. With this fix in place it was finally time to make a
1916 new release of the package, and get it into Debian.&lt;/p&gt;
1917
1918 &lt;p&gt;If you are interested in how your laptop battery is doing, please
1919 check out the
1920 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
1921 in Debian unstable, or rebuild it on Jessie to get it working on
1922 Debian stable. :) The upstream source is available from
1923 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1924 As always, patches are very welcome.&lt;/p&gt;
1925 </description>
1926 </item>
1927
1928 <item>
1929 <title>Making battery measurements a little easier in Debian</title>
1930 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
1931 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
1932 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
1933 <description>&lt;p&gt;Back in September, I blogged about
1934 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
1935 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
1936 how it showed the decay and death of this battery (now replaced). I
1937 created a simple deb package to handle the collection and graphing,
1938 but did not want to upload it to Debian as there were already
1939 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
1940 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
1941 a point of uploading a competing package when battery-stats could be
1942 fixed instead. I reported a few bugs about its non-function, and
1943 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
1944
1945 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
1946 hands. The end result is that I am now the new upstream developer of
1947 battery stats (&lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;available from github&lt;/a&gt;) and part of the team maintaining
1948 battery-stats in Debian, and the package in Debian unstable is finally
1949 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
1950 information provided by the Linux kernel. If you install the
1951 battery-stats package from unstable now, you will be able to get a
1952 graph of the current battery fill level, to get some idea about the
1953 status of the battery. The source package build and work just fine in
1954 Debian testing and stable (and probably oldstable too, but I have not
1955 tested). The default graph you get for that system look like this:&lt;/p&gt;
1956
1957 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-03-15-battery-stats-graph-example.png&quot; width=&quot;70%&quot; align=&quot;center&quot;&gt;&lt;/p&gt;
1958
1959 &lt;p&gt;My plans for the future is to merge my old scripts into the
1960 battery-stats package, as my old scripts collected a lot more details
1961 about the battery. The scripts are merged into the upstream
1962 battery-stats git repository already, but I am not convinced they work
1963 yet, as I changed a lot of paths along the way. Will have to test a
1964 bit more before I make a new release.&lt;/p&gt;
1965
1966 &lt;p&gt;I will also consider changing the file format slightly, as I
1967 suspect the way I combine several values into one field might make it
1968 impossible to know the type of the value when using it for processing
1969 and graphing.&lt;/p&gt;
1970
1971 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
1972 battery, check out the battery-stats package in
1973 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
1974 on
1975 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
1976 I would love some help to improve the system further.&lt;/p&gt;
1977 </description>
1978 </item>
1979
1980 <item>
1981 <title>Creating, updating and checking debian/copyright semi-automatically</title>
1982 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
1983 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
1984 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
1985 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
1986 details. And one of the details is the content of the
1987 debian/copyright file, which should list all relevant licenses used by
1988 the code in the package in question, preferably in
1989 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
1990 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
1991
1992 &lt;p&gt;For large packages with lots of contributors it is hard to write
1993 and update this file manually, and if you get some detail wrong, the
1994 package is normally rejected by the ftpmasters. So getting it right
1995 the first time around get the package into Debian faster, and save
1996 both you and the ftpmasters some work.. Today, while trying to figure
1997 out what was wrong with
1998 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
1999 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
2000 figuring out the options for doing this job automatically, or at least
2001 semi-automatically.&lt;/p&gt;
2002
2003 &lt;p&gt;Lucikly, there are at least two tools available for generating the
2004 file based on the code in the source package,
2005 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
2006 and &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/cme&quot;&gt;cme&lt;/a&gt;&lt;/tt&gt;. I&#39;m
2007 not sure which one of them came first, but both seem to be able to
2008 create a sensible draft file. As far as I can tell, none of them can
2009 be trusted to get the result just right, so the content need to be
2010 polished a bit before the file is OK to upload. I found the debmake
2011 option in
2012 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
2013 blog posts from 2014&lt;/a&gt;.
2014
2015 &lt;p&gt;To generate using debmake, use the -cc option:
2016
2017 &lt;p&gt;&lt;pre&gt;
2018 debmake -cc &gt; debian/copyright
2019 &lt;/pre&gt;&lt;/p&gt;
2020
2021 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
2022 this might not be the best option.&lt;/p&gt;
2023
2024 &lt;p&gt;The cme option is based on a config parsing library, and I found
2025 this approach in
2026 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
2027 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
2028 dpkg-copyright&#39; option:
2029
2030 &lt;p&gt;&lt;pre&gt;
2031 cme update dpkg-copyright
2032 &lt;/pre&gt;&lt;/p&gt;
2033
2034 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
2035 handle UTF-8 names better than debmake.&lt;/p&gt;
2036
2037 &lt;p&gt;When the copyright file is created, I would also like some help to
2038 check if the file is correct. For this I found two good options,
2039 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
2040 to focus on license types and file matching, and is able to detect
2041 ineffective blocks in the copyright file. The latter reports missing
2042 copyright holders and years, but was confused by inconsistent license
2043 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
2044 fix all issues reported by them before uploading. But I do not know
2045 if the tools and the ftpmasters agree on what is important to fix in a
2046 copyright file, so the package might still be rejected.&lt;/p&gt;
2047
2048 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
2049 will read through the source and try to find all copyright statements.
2050 It is not comparing the result to the content of debian/copyright, but
2051 can be useful when verifying the content of the copyright file.&lt;/p&gt;
2052
2053 &lt;p&gt;Are you aware of better tools in Debian to create and update
2054 debian/copyright file. Please let me know, or blog about it on
2055 planet.debian.org.&lt;/p&gt;
2056
2057 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2058 activities, please send Bitcoin donations to my address
2059 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2060
2061 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
2062 on how to use licensecheck and cdbs to create a draft copyright file
2063
2064 &lt;p&gt;&lt;pre&gt;
2065 licensecheck --copyright -r `find * -type f` | \
2066 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
2067 &lt;/pre&gt;&lt;/p&gt;
2068
2069 &lt;p&gt;He mentioned that he normally check the generated file into the
2070 version control system to make it easier to discover license and
2071 copyright changes in the upstream source. I will try to do the same
2072 with my packages in the future.&lt;/p&gt;
2073
2074 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
2075 against using -quiet for new users, so I removed it from the proposed
2076 command line.&lt;/p&gt;
2077 </description>
2078 </item>
2079
2080 <item>
2081 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
2082 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
2083 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
2084 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
2085 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
2086 is taking shape in Debian, and one provided feature is a very
2087 convenient way to tell you which package to install to make a given
2088 firmware file available when the kernel is looking for it. This can
2089 be done using apt-file too, but that is for someone else to blog
2090 about. :)&lt;/p&gt;
2091
2092 &lt;p&gt;Here is a small recipe to find the package with a given firmware
2093 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
2094 picked from the set of firmware announced using appstream in Debian
2095 unstable. In general you would be looking for the firmware requested
2096 by the kernel during kernel module loading. To find the package
2097 providing the example file, do like this:&lt;/p&gt;
2098
2099 &lt;blockquote&gt;&lt;pre&gt;
2100 % apt install appstream
2101 [...]
2102 % apt update
2103 [...]
2104 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
2105 awk &#39;/Package:/ {print $2}&#39;
2106 firmware-qlogic
2107 %
2108 &lt;/pre&gt;&lt;/blockquote&gt;
2109
2110 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
2111 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
2112 a way appstream can use.&lt;/p&gt;
2113
2114 &lt;p&gt;This same approach can be used to find any package supporting a
2115 given MIME type. This is very useful when you get a file you do not
2116 know how to handle. First find the mime type using &lt;tt&gt;file
2117 --mime-type&lt;/tt&gt;, and next look up the package providing support for
2118 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2119 and you can find all packages handling this type like this:&lt;/p&gt;
2120
2121 &lt;blockquote&gt;&lt;pre&gt;
2122 % apt install appstream
2123 [...]
2124 % apt update
2125 [...]
2126 % appstreamcli what-provides mimetype image/svg+xml | \
2127 awk &#39;/Package:/ {print $2}&#39;
2128 bkchem
2129 phototonic
2130 inkscape
2131 shutter
2132 tetzle
2133 geeqie
2134 xia
2135 pinta
2136 gthumb
2137 karbon
2138 comix
2139 mirage
2140 viewnior
2141 postr
2142 ristretto
2143 kolourpaint4
2144 eog
2145 eom
2146 gimagereader
2147 midori
2148 %
2149 &lt;/pre&gt;&lt;/blockquote&gt;
2150
2151 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
2152 packages providing appstream metadata.&lt;/p&gt;
2153 </description>
2154 </item>
2155
2156 <item>
2157 <title>Creepy, visualise geotagged social media information - nice free software</title>
2158 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
2159 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
2160 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
2161 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
2162 with the computerised radio beacon known as a mobile phone their
2163 position is tracked by the phone company and often stored for a long
2164 time (like every time a SMS is received or sent). And if their
2165 computerised radio beacon is capable of running programs (often called
2166 mobile apps) downloaded from the Internet, these programs are often
2167 also capable of tracking their location (if the app requested access
2168 during installation). And when these programs send out information to
2169 central collection points, the location is often included, unless
2170 extra care is taken to not send the location. The provided
2171 information is used by several entities, for good and bad (what is
2172 good and bad, depend on your point of view). What is certain, is that
2173 the private sphere and the right to free movement is challenged and
2174 perhaps even eradicated for those announcing their location this way,
2175 when they share their whereabouts with private and public
2176 entities.&lt;/p&gt;
2177
2178 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-01-24-nice-creepy-desktop-window.png&quot;&gt;&lt;/p&gt;
2179
2180 &lt;p&gt;The phone company logs provide a register of locations to check out
2181 when one want to figure out what the tracked person was doing. It is
2182 unavailable for most of us, but provided to selected government
2183 officials, company staff, those illegally buying information from
2184 unfaithful servants and crackers stealing the information. But the
2185 public information can be collected and analysed, and a free software
2186 tool to do so is called
2187 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
2188 discovered it when I read
2189 &lt;a href=&quot;http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-7787884.html&quot;&gt;an
2190 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
2191 November 2014, and decided to check if it was available in Debian.
2192 The python program was in Debian, but
2193 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
2194 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
2195 uploaded a new version which did not work quite right, but did not
2196 have time to fix it then. This Christmas I decided to finally try to
2197 get Creepy operational in Debian. Now a fixed version is available in
2198 Debian unstable and testing, and almost all Debian specific patches
2199 are now included
2200 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
2201
2202 &lt;p&gt;The Creepy program visualises geolocation information fetched from
2203 Twitter, Instagram, Flickr and Google+, and allow one to get a
2204 complete picture of every social media message posted recently in a
2205 given area, or track the movement of a given individual across all
2206 these services. Earlier it was possible to use the search API of at
2207 least some of these services without identifying oneself, but these
2208 days it is impossible. This mean that to use Creepy, you need to
2209 configure it to log in as yourself on these services, and provide
2210 information to them about your search interests. This should be taken
2211 into account when using Creepy, as it will also share information
2212 about yourself with the services.&lt;/p&gt;
2213
2214 &lt;p&gt;The picture above show the twitter messages sent from (or at least
2215 geotagged with a position from) the city centre of Oslo, the capital
2216 of Norway. One useful way to use Creepy is to first look at
2217 information tagged with an area of interest, and next look at all the
2218 information provided by one or more individuals who was in the area.
2219 I tested it by checking out which celebrity provide their location in
2220 twitter messages by checkout out who sent twitter messages near a
2221 Norwegian TV station, and next could track their position over time,
2222 making it possible to locate their home and work place, among other
2223 things. A similar technique have been
2224 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
2225 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
2226 tool to discover lying governments, and a useful tool to help people
2227 understand the value of the private information they provide to the
2228 public.&lt;/p&gt;
2229
2230 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
2231 it depend on several python modules currently missing in Jessie (at
2232 least python-instagram, python-flickrapi and
2233 python-requests-toolbelt).&lt;/p&gt;
2234
2235 &lt;p&gt;(I have uploaded
2236 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
2237 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
2238 Creepy program in Debian.)&lt;/p&gt;
2239 </description>
2240 </item>
2241
2242 <item>
2243 <title>Always download Debian packages using Tor - the simple recipe</title>
2244 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
2245 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
2246 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
2247 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
2248 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
2249 that those listening on the Internet lines would have good reason to
2250 believe a computer have a given security hole&lt;/a&gt; if it download a
2251 security fix from a Debian mirror. This is a good reason to always
2252 use encrypted connections to the Debian mirror, to make sure those
2253 listening do not know which IP address to attack. In August, Richard
2254 Hartmann observed that encryption was not enough, when it was possible
2255 to interfere download size to security patches or the fact that
2256 download took place shortly after a security fix was released, and
2257 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
2258 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
2259 was not the first to propose this, as the
2260 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/apt-transport-tor&quot;&gt;apt-transport-tor&lt;/a&gt;&lt;/tt&gt;
2261 package by Tim Retout already existed to make it easy to convince apt
2262 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
2263 aware of that package when I read the blog post from Richard.&lt;/p&gt;
2264
2265 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
2266 sysadmins, and he set up a Tor hidden service on one of the central
2267 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2268 it possible to download packages directly between two tor nodes,
2269 making sure the network traffic always were encrypted.&lt;/p&gt;
2270
2271 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
2272 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
2273 urls with tor+http and tor+https, and using the hidden service instead
2274 of the official Debian mirror site. I recommend installing
2275 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
2276 done in /etc/.&lt;/p&gt;
2277
2278 &lt;blockquote&gt;&lt;pre&gt;
2279 apt install apt-transport-tor
2280 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
2281 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
2282 &lt;/pre&gt;&lt;/blockquote&gt;
2283
2284 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
2285 the sed commands for these too. The sed command is assuming your are
2286 using the ftp.debian.org Debian mirror. Adjust the command (or just
2287 edit the file manually) to match your mirror.&lt;/p&gt;
2288
2289 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
2290 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
2291 system, and do not work with these tor+http URLs. For
2292 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
2293 which need a recent apt version currently only in unstable. So if you
2294 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
2295
2296 &lt;p&gt;Another advantage from this change is that your machine will start
2297 using Tor regularly and at fairly random intervals (every time you
2298 update the package lists or upgrade or install a new package), thus
2299 masking other Tor traffic done from the same machine. Using Tor will
2300 become normal for the machine in question.&lt;/p&gt;
2301
2302 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
2303 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
2304 enabled. It would be great if it was the default on any Debian
2305 system.&lt;/p&gt;
2306 </description>
2307 </item>
2308
2309 <item>
2310 <title>OpenALPR, find car license plates in video streams - nice free software</title>
2311 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
2312 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
2313 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
2314 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
2315 call the car license plate numbers in those days. I would write the
2316 numbers down in my little book and compare notes with the other kids
2317 to see how many region codes we had seen and if we had seen some
2318 exotic or special region codes and numbers. It was a fun game to pass
2319 time, as we kids have plenty of it.&lt;/p&gt;
2320
2321 &lt;p&gt;A few days I came across
2322 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
2323 project&lt;/a&gt;, a free software project to automatically discover and
2324 report license plates in images and video streams, and provide the
2325 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
2326 such system for a while now, because I believe it is a bad idea that the
2327 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
2328 number plate recognition&lt;/a&gt; tool only is available in the hands of
2329 the powerful, and want it to be available also for the powerless to
2330 even the score when it comes to surveillance and sousveillance. I
2331 discovered the developer
2332 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
2333 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
2334 help him get it into shape to get the package uploaded into the Debian
2335 archive.&lt;/p&gt;
2336
2337 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
2338 it into Debian, where it currently
2339 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
2340 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
2341
2342 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
2343 for the common folks, ie those not running a large government
2344 surveillance system? Well, I plan to put it in a computer on my bike
2345 and in my car, tracking the cars nearby and allowing me to be notified
2346 when number plates on my watch list are discovered. Another use case
2347 was suggested by a friend of mine, who wanted to set it up at his home
2348 to open the car port automatically when it discovered the plate on his
2349 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2350 capable of placing his license plate number of a piece of cardboard to
2351 open his car port, men replied that it was always unlocked anyway. I
2352 guess for such use case it make sense. I am sure there are other use
2353 cases too, for those with imagination and a vision.&lt;/p&gt;
2354
2355 &lt;p&gt;If you want to build your own version of the Debian package, check
2356 out the upstream git source and symlink ./distros/debian to ./debian/
2357 before running &quot;debuild&quot; to build the source. Or wait a bit until the
2358 package show up in unstable.&lt;/p&gt;
2359 </description>
2360 </item>
2361
2362 <item>
2363 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
2364 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
2365 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
2366 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
2367 <description>&lt;p&gt;Around three years ago, I created
2368 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
2369 system&lt;/a&gt; to get a more practical solution in Debian for handing
2370 hardware related packages. A GUI system in the isenkram package will
2371 present a pop-up dialog when some hardware dongle supported by
2372 relevant packages in Debian is inserted into the machine. The same
2373 lookup mechanism to detect packages is available as command line
2374 tools in the isenkram-cli package. In addition to mapping hardware,
2375 it will also map kernel firmware files to packages and make it easy to
2376 install needed firmware packages automatically. The key for this
2377 system to work is a good way to map hardware to packages, in other
2378 words, allow packages to announce what hardware they will work
2379 with.&lt;/p&gt;
2380
2381 &lt;p&gt;I started by providing data files in the isenkram source, and
2382 adding code to download the latest version of these data files at run
2383 time, to ensure every user had the most up to date mapping available.
2384 I also added support for storing the mapping in the Packages file in
2385 the apt repositories, but did not push this approach because while I
2386 was trying to figure out how to best store hardware/package mappings,
2387 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
2388 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
2389 add the hardware mapping into that data set to be able to use
2390 appstream as a data source, and this was accepted at least for the
2391 Debian version of appstream.&lt;/p&gt;
2392
2393 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
2394 and today I uploaded a new version 0.20 of isenkram adding support for
2395 appstream as a data source for mapping hardware to packages. The only
2396 package so far using appstream to announce its hardware support is my
2397 pymissile package. I got help from Matthias Klumpp with figuring out
2398 how do add the required
2399 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
2400 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
2401 this content:&lt;/p&gt;
2402
2403 &lt;blockquote&gt;&lt;pre&gt;
2404 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
2405 &amp;lt;component&amp;gt;
2406 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
2407 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
2408 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
2409 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
2410 &amp;lt;description&amp;gt;
2411 &amp;lt;p&amp;gt;
2412 Pymissile provides a curses interface to control an original
2413 Marks and Spencer / Striker USB Missile Launcher, as well as a
2414 motion control script to allow a webcamera to control the
2415 launcher.
2416 &amp;lt;/p&amp;gt;
2417 &amp;lt;/description&amp;gt;
2418 &amp;lt;provides&amp;gt;
2419 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
2420 &amp;lt;/provides&amp;gt;
2421 &amp;lt;/component&amp;gt;
2422 &lt;/pre&gt;&lt;/blockquote&gt;
2423
2424 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
2425 which is a glob style match rule for hardware specific strings
2426 (modalias strings) provided by the Linux kernel. In this case, it
2427 will map to all USB devices with vendor code 1130 and product code
2428 0202.&lt;/p&gt;
2429
2430 &lt;p&gt;Note, it is important that the license of all the metadata files
2431 are compatible to have permissions to aggregate them into archive wide
2432 appstream files. Matthias suggested to use MIT or BSD licenses for
2433 these files. A challenge is figuring out a good id for the data, as
2434 it is supposed to be globally unique and shared across distributions
2435 (in other words, best to coordinate with upstream what to use). But
2436 it can be changed later or, so we went with the package name as
2437 upstream for this project is dormant.&lt;/p&gt;
2438
2439 &lt;p&gt;To get the metadata file installed in the correct location for the
2440 mirror update scripts to pick it up and include its content the
2441 appstream data source, the file must be installed in the binary
2442 package under /usr/share/appdata/. I did this by adding the following
2443 line to debian/pymissile.install:&lt;/p&gt;
2444
2445 &lt;blockquote&gt;&lt;pre&gt;
2446 debian/pymissile.metainfo.xml usr/share/appdata
2447 &lt;/pre&gt;&lt;/blockquote&gt;
2448
2449 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
2450 all packages useful on the current computer automatically, and the GUI
2451 pop-up handler will propose to install the package not already
2452 installed if a hardware dongle is inserted into the machine in
2453 question.&lt;/p&gt;
2454
2455 &lt;p&gt;Details of the modalias field in appstream is available from the
2456 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
2457
2458 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
2459 try running this command on the command line:&lt;/p&gt;
2460
2461 &lt;blockquote&gt;&lt;pre&gt;
2462 cat $(find /sys/devices/|grep modalias)
2463 &lt;/pre&gt;&lt;/blockquote&gt;
2464
2465 &lt;p&gt;To learn more about the isenkram system, please check out
2466 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
2467 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
2468 </description>
2469 </item>
2470
2471 <item>
2472 <title>The GNU General Public License is not magic pixie dust</title>
2473 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
2474 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
2475 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
2476 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
2477 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
2478 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
2479 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
2480 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
2481
2482 &lt;blockquote&gt;
2483
2484 &lt;p&gt;&lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;&lt;img src=&quot;https://sfconservancy.org/img/supporter-badge.png&quot; width=&quot;194&quot; height=&quot;90&quot; alt=&quot;Become a Software Freedom Conservancy Supporter!&quot; align=&quot;right&quot; border=&quot;0&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
2485
2486 &lt;blockquote&gt;
2487 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
2488
2489 The first step is to choose a
2490 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
2491 code.&lt;br/&gt;
2492
2493 The next step is, when someone fails to follow that copyleft license,
2494 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
2495
2496 and its a simple fact of our modern society that such type of
2497 work&lt;br/&gt;
2498
2499 is incredibly expensive to do and incredibly difficult to do.
2500 &lt;/blockquote&gt;
2501
2502 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
2503 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
2504 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
2505 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
2506
2507 &lt;p&gt;As the Debian Website
2508 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
2509 &lt;a href=&quot;https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=1.24&amp;amp;r2=1.25&quot;&gt;to&lt;/a&gt;
2510 imply, public domain and permissively licensed software can lead to
2511 the production of more proprietary software as people discover useful
2512 software, extend it and or incorporate it into their hardware or
2513 software products. Copyleft licenses such as the GNU GPL were created
2514 to close off this avenue to the production of proprietary software but
2515 such licenses are not enough. With the ongoing adoption of Free
2516 Software by individuals and groups, inevitably the community&#39;s
2517 expectations of license compliance are violated, usually out of
2518 ignorance of the way Free Software works, but not always. As Karen
2519 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
2520 Freedom&quot;&gt;FaiF&lt;/a&gt;
2521 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
2522 copyleft is nothing if no-one is willing and able to stand up in court
2523 to protect it. The reality of today&#39;s world is that legal
2524 representation is expensive, difficult and time consuming. With
2525 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
2526 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
2527 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
2528 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
2529 of the Linux project, Debian and other groups against GPL violations.
2530 In March the SFC supported a
2531 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
2532 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
2533 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
2534 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
2535 kernel. Since then two of their sponsors pulled corporate funding and
2536 conferences
2537 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
2538 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
2539 less on corporate funding and more on the broad community of
2540 individuals who support Free Software and copyleft. So the SFC has
2541 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
2542 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
2543 a community of folks who stand up for copyleft and the GPL by
2544 supporting their work on promoting and supporting copyleft and Free
2545 Software.&lt;/p&gt;
2546
2547 &lt;p&gt;If you support Free Software,
2548 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
2549 what the SFC do, agree with their
2550 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
2551 principles&lt;/a&gt;, are happy about their
2552 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
2553 work on a project that is an SFC
2554 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
2555 just want to stand up for copyleft, please join
2556 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
2557 Allan Webber&lt;/a&gt;,
2558 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
2559 Smith&lt;/a&gt;,
2560 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
2561 Bacon&lt;/a&gt;, myself and
2562 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
2563 becoming a
2564 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
2565 next week your donation will be
2566 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
2567 by an anonymous donor. Please also consider asking your employer to
2568 match your donation or become a sponsor of SFC. Don&#39;t forget to
2569 spread the word about your support for SFC via email, your blog and or
2570 social media accounts.&lt;/p&gt;
2571
2572 &lt;/blockquote&gt;
2573
2574 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
2575 of Software Freedom Conservancy myself. Perhaps you should be a
2576 supporter too?&lt;/p&gt;
2577 </description>
2578 </item>
2579
2580 <item>
2581 <title>PGP key transition statement for key EE4E02F9</title>
2582 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
2583 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
2584 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
2585 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
2586 set it up properly. I wanted to generate it offline and have it
2587 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
2588 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
2589 time to sit down with an offline machine almost took forever. But
2590 finally I&#39;ve been able to complete the process, and have now moved
2591 from my old GPG key to a new GPG key. See
2592 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
2593 full transition statement, signed with both my old and new key&lt;/a&gt; for
2594 the details. This is my new key:&lt;/p&gt;
2595
2596 &lt;pre&gt;
2597 pub 3936R/&lt;a href=&quot;http://pgp.cs.uu.nl/stats/111D6B29EE4E02F9.html&quot;&gt;111D6B29EE4E02F9&lt;/a&gt; 2015-11-03 [expires: 2019-11-14]
2598 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
2599 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
2600 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
2601 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
2602 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
2603 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
2604 &lt;/pre&gt;
2605
2606 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
2607 my old key.&lt;/p&gt;
2608
2609 &lt;p&gt;If you signed my old key
2610 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
2611 I&#39;d very much appreciate a signature on my new key, details and
2612 instructions in the transition statement. I m happy to reciprocate if
2613 you have a similarly signed transition statement to present.&lt;/p&gt;
2614 </description>
2615 </item>
2616
2617 <item>
2618 <title>The life and death of a laptop battery</title>
2619 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
2620 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
2621 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
2622 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
2623 But this do not last. The last few laptops gave me a feeling that
2624 within a year, the life time is just a fraction of what it used to be,
2625 and it slowly become painful to use the laptop without power connected
2626 all the time. Because of this, when I got a new Thinkpad X230 laptop
2627 about two years ago, I decided to monitor its battery state to have
2628 more hard facts when the battery started to fail.&lt;/p&gt;
2629
2630 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
2631
2632 &lt;p&gt;First I tried to find a sensible Debian package to record the
2633 battery status, assuming that this must be a problem already handled
2634 by someone else. I found
2635 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
2636 which collects statistics from the battery, but it was completely
2637 broken. I sent a few suggestions to the maintainer, but decided to
2638 write my own collector as a shell script while I waited for feedback
2639 from him. Via
2640 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
2641 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
2642 discovered
2643 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
2644 available in Debian.&lt;/p&gt;
2645
2646 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
2647 battery stats ever since. Now my
2648 /var/log/hjemmenett-battery-status.log file contain around 115,000
2649 measurements, from the time the battery was working great until now,
2650 when it is unable to charge above 7% of original capacity. My
2651 collector shell script is quite simple and look like this:&lt;/p&gt;
2652
2653 &lt;pre&gt;
2654 #!/bin/sh
2655 # Inspired by
2656 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
2657 # See also
2658 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
2659 logfile=/var/log/hjemmenett-battery-status.log
2660
2661 files=&quot;manufacturer model_name technology serial_number \
2662 energy_full energy_full_design energy_now cycle_count status&quot;
2663
2664 if [ ! -e &quot;$logfile&quot; ] ; then
2665 (
2666 printf &quot;timestamp,&quot;
2667 for f in $files; do
2668 printf &quot;%s,&quot; $f
2669 done
2670 echo
2671 ) &gt; &quot;$logfile&quot;
2672 fi
2673
2674 log_battery() {
2675 # Print complete message in one echo call, to avoid race condition
2676 # when several log processes run in parallel.
2677 msg=$(printf &quot;%s,&quot; $(date +%s); \
2678 for f in $files; do \
2679 printf &quot;%s,&quot; $(cat $f); \
2680 done)
2681 echo &quot;$msg&quot;
2682 }
2683
2684 cd /sys/class/power_supply
2685
2686 for bat in BAT*; do
2687 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
2688 done
2689 &lt;/pre&gt;
2690
2691 &lt;p&gt;The script is called when the power management system detect a
2692 change in the power status (power plug in or out), and when going into
2693 and out of hibernation and suspend. In addition, it collect a value
2694 every 10 minutes. This make it possible for me know when the battery
2695 is discharging, charging and how the maximum charge change over time.
2696 The code for the Debian package
2697 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
2698 available on github&lt;/a&gt;.&lt;/p&gt;
2699
2700 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
2701
2702 &lt;pre&gt;
2703 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2704 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
2705 [...]
2706 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
2707 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
2708 &lt;/pre&gt;
2709
2710 &lt;p&gt;I wrote a small script to create a graph of the charge development
2711 over time. This graph depicted above show the slow death of my laptop
2712 battery.&lt;/p&gt;
2713
2714 &lt;p&gt;But why is this happening? Why are my laptop batteries always
2715 dying in a year or two, while the batteries of space probes and
2716 satellites keep working year after year. If we are to believe
2717 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
2718 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
2719 chance, and the fix is to not charge the Lithium-ion batteries to 100%
2720 all the time, but to stay below 90% of full charge most of the time.
2721 I&#39;ve been told that the Tesla electric cars
2722 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
2723 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
2724 100% when preparing for a longer trip (not that I would want a car
2725 like Tesla where rights to privacy is abandoned, but that is another
2726 story), which I guess is the option we should have for laptops on
2727 Linux too.&lt;/p&gt;
2728
2729 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
2730 stop charging at 80%, unless requested to charge to 100% once in
2731 preparation for a longer trip? I found
2732 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
2733 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2734 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
2735 load).&lt;/p&gt;
2736
2737 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
2738 at the start. I also wonder why the &quot;full capacity&quot; increases some
2739 times, and if it is possible to repeat the process to get the battery
2740 back to design capacity. And I wonder if the discharge and charge
2741 speed change over time, or if this stay the same. I did not yet try
2742 to write a tool to calculate the derivative values of the battery
2743 level, but suspect some interesting insights might be learned from
2744 those.&lt;/p&gt;
2745
2746 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
2747 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2748 packages instead of the tp-smapi-dkms package I had tried to use
2749 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
2750 and stop. I&#39;ve done so now, but expect my existing battery is toast
2751 and need to be replaced. The proposal is unfortunately Thinkpad
2752 specific.&lt;/p&gt;
2753 </description>
2754 </item>
2755
2756 <item>
2757 <title>New laptop - some more clues and ideas based on feedback</title>
2758 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
2759 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
2760 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
2761 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
2762 need for a new laptop, and provided very useful feedback. I wish to
2763 thank every one of these. Several pointed me to the possibility of
2764 fixing my X230, and I am already in the process of getting Lenovo to
2765 do so thanks to the on site, next day support contract covering the
2766 machine. But the battery is almost useless (I expect to replace it
2767 with a non-official battery) and I do not expect the machine to live
2768 for many more years, so it is time to plan its replacement. If I did
2769 not have a support contract, it was suggested to find replacement parts
2770 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
2771 might present a language barrier as I do not understand French.&lt;/p&gt;
2772
2773 &lt;p&gt;One tip I got was to use the
2774 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
2775 compare laptop models. It seem to have more models available than
2776 prisjakt.no. Another tip I got from someone I know have similar
2777 keyboard preferences was that the HP EliteBook 840 keyboard is not
2778 very good, and this matches my experience with earlier EliteBook
2779 keyboards I tested. Because of this, I will not consider it any further.
2780
2781 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
2782 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2783 (which is missing from the X240), and is working fairly well with
2784 Debian Sid/Unstable according to
2785 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
2786 got on the keyboard quality are not consistent. Some say the keyboard
2787 is good, others say it is ok, while others say it is not very good.
2788 Those with experience from X41 and and X60 agree that the X250
2789 keyboard is not as good as those trusty old laptops, and suggest I
2790 keep and fix my X230 instead of upgrading, or get a used X230 to
2791 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
2792 activity and battery status, which is very convenient on my X230. I&#39;m
2793 also told that the CPU fan is running very often, making it a bit
2794 noisy. In any case, the X250 do not work out of the box with Debian
2795 Stable/Jessie, one of my requirements.&lt;/p&gt;
2796
2797 &lt;p&gt;I have also gotten a few vendor proposals, one was
2798 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
2799 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
2800 The latter look very attractive to me.&lt;/p&gt;
2801
2802 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
2803 as I keep looking for a replacement.&lt;/p&gt;
2804
2805 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
2806 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
2807 different
2808 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
2809 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
2810 </description>
2811 </item>
2812
2813 <item>
2814 <title>Time to find a new laptop, as the old one is broken after only two years</title>
2815 <link>http://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</link>
2816 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</guid>
2817 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
2818 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
2819 replacement soon. The left 5 cm of the screen on my Thinkpad X230
2820 started flickering yesterday, and I suspect the cause is a broken
2821 cable, as changing the angle of the screen some times get rid of the
2822 flickering.&lt;/p&gt;
2823
2824 &lt;p&gt;My requirements have not really changed since I bought it, and is
2825 still as
2826 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
2827 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
2828 good help from
2829 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
2830 where I could select at least a few of the requirements (mouse pin,
2831 wifi, weight) and go through the rest manually. Three button mouse
2832 and a good keyboard is not available as an option, and all the three
2833 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
2834 G2) lack three mouse buttons). It is also unclear to me how good the
2835 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2836 the keyboard, even if the quality and robustness in the X series have
2837 deteriorated since X41.&lt;/p&gt;
2838
2839 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
2840 seem sensible to me? Are there better services around to search the
2841 set of available laptops for features? Please send me an email if you
2842 have suggestions.&lt;/p&gt;
2843
2844 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
2845 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
2846 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
2847 </description>
2848 </item>
2849
2850 <item>
2851 <title>How to stay with sysvinit in Debian Jessie</title>
2852 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
2853 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
2854 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
2855 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
2856 sysvinit as its boot system by default. But how can one keep using
2857 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2858 courtesy of
2859 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
2860 Schubert&lt;/a&gt; and
2861 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
2862 McVittie&lt;/a&gt;.
2863
2864 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
2865 keep sysvinit as your boot system, create a file
2866 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
2867 you upgrade:&lt;/p&gt;
2868
2869 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2870 Package: systemd-sysv
2871 Pin: release o=Debian
2872 Pin-Priority: -1
2873 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2874
2875 &lt;p&gt;This file content will tell apt and aptitude to not consider
2876 installing systemd-sysv as part of any installation and upgrade
2877 solution when resolving dependencies, and thus tell it to avoid
2878 systemd as a default boot system. The end result should be that the
2879 upgraded system keep using sysvinit.&lt;/p&gt;
2880
2881 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
2882 get sysvinit installed by default (debootstrap used by
2883 debian-installer have no option for this), but one can tell the
2884 installer to switch to sysvinit before the first boot. Either by
2885 using a kernel argument to the installer, or by adding a line to the
2886 preseed file used. First, the kernel command line argument:
2887
2888 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2889 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
2890 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2891
2892 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
2893
2894 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2895 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2896 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
2897
2898 &lt;p&gt;One can of course also do this after the first boot by installing
2899 the sysvinit-core package.&lt;/p&gt;
2900
2901 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
2902 sysvinit boot sequence in Debian have several hardware specific bugs
2903 on Linux caused by the fact that it is unpredictable when hardware
2904 devices show up during boot. But on the other hand, the new default
2905 boot system still have a few rough edges I hope will be fixed before
2906 Jessie is released.&lt;/p&gt;
2907
2908 &lt;p&gt;Update 2014-11-26: Inspired by
2909 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
2910 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
2911 line.&lt;/p&gt;
2912 </description>
2913 </item>
2914
2915 <item>
2916 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
2917 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
2918 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
2919 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
2920 <description>&lt;p&gt;The right to communicate with your friends and family in private,
2921 without anyone snooping, is a right every citicen have in a liberal
2922 democracy. But this right is under serious attack these days.&lt;/p&gt;
2923
2924 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
2925 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2926 the whisleblower Snowden) more expensive for Internet email,
2927 is to deliver all email using SMTP via Tor. Such SMTP option would be
2928 a nice addition to the FreedomBox project if we could send email
2929 between FreedomBox machines without leaking metadata about the emails
2930 to the people peeking on the wire. I
2931 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
2932 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
2933 lot of useful feedback and suggestions. It also became obvious to me
2934 that this was not a novel idea, as the same idea was tested and
2935 documented by Johannes Berg as early as 2006, and both
2936 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
2937 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
2938 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
2939
2940 &lt;p&gt;To implement such system one need to set up a Tor hidden service
2941 providing the SMTP protocol on port 25, and use email addresses
2942 looking like username@hidden-service-name.onion. With such addresses
2943 the connections to port 25 on hidden-service-name.onion using Tor will
2944 go to the correct SMTP server. To do this, one need to configure the
2945 Tor daemon to provide the hidden service and the mail server to accept
2946 emails for this .onion domain. To learn more about Exim configuration
2947 in Debian and test the design provided by Johannes Berg in his FAQ, I
2948 set out yesterday to create a Debian package for making it trivial to
2949 set up such SMTP over Tor service based on Debian. Getting it to work
2950 were fairly easy, and
2951 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
2952 source code for the Debian package&lt;/a&gt; is available from github. I
2953 plan to move it into Debian if further testing prove this to be a
2954 useful approach.&lt;/p&gt;
2955
2956 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
2957 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
2958 get rid of exim4). Install tor, clone the git repository mentioned
2959 above, build the deb and install it on the machine. Next, run
2960 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
2961 the instructions to get the service up and running. Restart tor and
2962 exim when it is done, and test mail delivery using swaks like
2963 this:&lt;/p&gt;
2964
2965 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2966 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2967 --to fbx@dutlqrrmjhtfa3vp.onion
2968 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2969
2970 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
2971 address with your own address to test your server. :)&lt;/p&gt;
2972
2973 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
2974 easier and more automatic. Especially the tor setup need more work.
2975 Also, the package include a tor-smtp tool written in C, but its task
2976 should probably be rewritten in some script language to make the deb
2977 architecture independent. It would probably also make the code easier
2978 to review. The tor-smtp tool currently need to listen on a socket for
2979 exim to talk to it and is started using xinetd. It would be better if
2980 no daemon and no socket is needed. I suspect it is possible to get
2981 exim to run a command line tool for delivery instead of talking to a
2982 socket, and hope to figure out how in a future version of this
2983 system.&lt;/p&gt;
2984
2985 &lt;p&gt;Until I wipe my test machine, I can be reached using the
2986 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
2987 SMTorP. :)&lt;/p&gt;
2988 </description>
2989 </item>
2990
2991 <item>
2992 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
2993 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
2994 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
2995 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
2996 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
2997 alioth.debian.org, you know the web interface is fairly slow to
2998 operate. First you visit one web page, enter the moderation password
2999 and get a new page shown with a list of all the messages to moderate
3000 and various options for each email address. This take a while for
3001 every list you moderate, and you need to do it regularly to do a good
3002 job as a list moderator. But there is a quick alternative,
3003 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
3004 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
3005 to moderate in a fraction of a second. Here is a test run on two
3006 lists I recently took over:&lt;/p&gt;
3007
3008 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3009 % time listadmin xiph
3010 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3011 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3012
3013 real 0m1.709s
3014 user 0m0.232s
3015 sys 0m0.012s
3016 %
3017 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3018
3019 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
3020 there are no message in the moderation queue. Every morning I
3021 currently moderate 68 mailman lists, and it normally take around two
3022 minutes. When I took over the two pkg-xiph lists above a few days
3023 ago, there were 400 emails waiting in the moderator queue. It took me
3024 less than 15 minutes to process them all using the listadmin
3025 program.&lt;/p&gt;
3026
3027 &lt;p&gt;If you install
3028 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
3029 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
3030 with content like this, the moderation task is a breeze:&lt;/p&gt;
3031
3032 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3033 username username@example.org
3034 spamlevel 23
3035 default discard
3036 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
3037
3038 password secret
3039 adminurl https://{domain}/mailman/admindb/{list}
3040 mailman-list@lists.example.com
3041
3042 password hidden
3043 other-list@otherserver.example.org
3044 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3045
3046 &lt;p&gt;There are other options to set as well. Check the manual page to
3047 learn the details.&lt;/p&gt;
3048
3049 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
3050 the SSL certificate is self signed or not properly signed by a
3051 generally accepted signing authority, you can set a environment
3052 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
3053
3054 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3055 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
3056 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3057
3058 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
3059 can provide an argument to the listadmin script like I do in the
3060 initial screen dump (the xiph argument). Using an argument, only
3061 lists matching the argument string will be processed. This make it
3062 quick to accept messages if you notice the moderation request in your
3063 email.&lt;/p&gt;
3064
3065 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
3066 mailing lists, as I simply do not have time to spend on that if the
3067 process was any slower. The listadmin program have saved me hours of
3068 time I could spend elsewhere over the years. It truly is nice free
3069 software.&lt;/p&gt;
3070
3071 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3072 activities, please send Bitcoin donations to my address
3073 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3074
3075 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
3076 configuration example. Also, I&#39;ve been told that the
3077 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
3078 sure why.&lt;/p&gt;
3079 </description>
3080 </item>
3081
3082 <item>
3083 <title>Debian Jessie, PXE and automatic firmware installation</title>
3084 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
3085 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
3086 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
3087 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
3088 problem that the WiFi card require some firmware to work properly.
3089 And it has been a pain to fix this using preseeding in Debian.
3090 Normally something more is needed. But thanks to
3091 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
3092 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
3093 to do this using simple preseeding.&lt;/p&gt;
3094
3095 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
3096 firmware for the hardware found in the machine (actually, requested by
3097 the kernel modules for the hardware). (It can also install user space
3098 programs supporting the hardware detected, but that is not the focus
3099 of this story.)&lt;/p&gt;
3100
3101 &lt;p&gt;To get this working in the default installation, two preeseding
3102 values are needed. First, the isenkram-cli package must be installed
3103 into the target chroot (aka the hard drive) before tasksel is executed
3104 in the pkgsel step of the debian-installer system. This is done by
3105 preseeding the base-installer/includes debconf value to include the
3106 isenkram-cli package. The package name is next passed to debootstrap
3107 for installation. With the isenkram-cli package in place, tasksel
3108 will automatically use the isenkram tasks to detect hardware specific
3109 packages for the machine being installed and install them, because
3110 isenkram-cli contain tasksel tasks.&lt;/p&gt;
3111
3112 &lt;p&gt;Second, one need to enable the non-free APT repository, because
3113 most firmware unfortunately is non-free. This is done by preseeding
3114 the apt-mirror-setup step. This is unfortunate, but for a lot of
3115 hardware it is the only option in Debian.&lt;/p&gt;
3116
3117 &lt;p&gt;The end result is two lines needed in your preseeding file to get
3118 firmware installed automatically by the installer:&lt;/p&gt;
3119
3120 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3121 base-installer base-installer/includes string isenkram-cli
3122 apt-mirror-setup apt-setup/non-free boolean true
3123 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3124
3125 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
3126 both firmware and user space packages when using this method. It also
3127 do not work well, so use version 0.15 or later. Installing both
3128 firmware and user space packages might give you a bit more than you
3129 want, so I decided to split the tasksel task in two, one for firmware
3130 and one for user space programs. The firmware task is enabled by
3131 default, while the one for user space programs is not. This split is
3132 implemented in the package currently in unstable.&lt;/p&gt;
3133
3134 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
3135 this recipe work for you. :)&lt;/p&gt;
3136
3137 &lt;p&gt;So, I bet you are wondering, how can this work. First and
3138 foremost, it work because tasksel is modular, and driven by whatever
3139 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3140 isenkram-cli package place two files for tasksel to find. First there
3141 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
3142
3143 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3144 Task: isenkram-packages
3145 Section: hardware
3146 Description: Hardware specific packages (autodetected by isenkram)
3147 Based on the detected hardware various hardware specific packages are
3148 proposed.
3149 Test-new-install: show show
3150 Relevance: 8
3151 Packages: for-current-hardware
3152
3153 Task: isenkram-firmware
3154 Section: hardware
3155 Description: Hardware specific firmware packages (autodetected by isenkram)
3156 Based on the detected hardware various hardware specific firmware
3157 packages are proposed.
3158 Test-new-install: mark show
3159 Relevance: 8
3160 Packages: for-current-hardware-firmware
3161 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3162
3163 &lt;p&gt;The key parts are Test-new-install which indicate how the task
3164 should be handled and the Packages line referencing to a script in
3165 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3166 list of packages to install. The for-current-hardware-firmware script
3167 look like this to list relevant firmware for the machine:
3168
3169 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3170 #!/bin/sh
3171 #
3172 PATH=/usr/sbin:$PATH
3173 export PATH
3174 isenkram-autoinstall-firmware -l
3175 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3176
3177 &lt;p&gt;With those two pieces in place, the firmware is installed by
3178 tasksel during the normal d-i run. :)&lt;/p&gt;
3179
3180 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
3181 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
3182 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
3183 install.&lt;/p&gt;
3184
3185 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
3186 pilots in testing this feature, as isenkram is used there now to
3187 install firmware, replacing the earlier scripts.&lt;/p&gt;
3188 </description>
3189 </item>
3190
3191 <item>
3192 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
3193 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
3194 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
3195 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
3196 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
3197 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3198 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
3199 on a screen normally showing the bread types and prizes:&lt;/p&gt;
3200
3201 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2014-10-04-ubuntu-ica-storo-crop.jpeg&quot;&gt;&lt;/p&gt;
3202
3203 &lt;p&gt;If it had booted as it was supposed to, I would never had known
3204 about this hidden Linux installation. It is interesting what
3205 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
3206 </description>
3207 </item>
3208
3209 <item>
3210 <title>New lsdvd release version 0.17 is ready</title>
3211 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
3212 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
3213 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
3214 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
3215 got a new set of developers a few weeks ago, after the original
3216 developer decided to step down and pass the project to fresh blood.
3217 This project is now maintained by Petter Reinholdtsen and Steve
3218 Dibb.&lt;/p&gt;
3219
3220 &lt;p&gt;I just wrapped up
3221 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
3222 new lsdvd release&lt;/a&gt;, available in git or from
3223 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
3224 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
3225 0.17.&lt;/p&gt;
3226
3227 &lt;ul&gt;
3228
3229 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
3230 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
3231 non-existant, to work around additional copy protection&lt;/li&gt;
3232 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
3233 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
3234 &lt;li&gt;Fix include orders&lt;/li&gt;
3235 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
3236 &lt;li&gt;Fix the chapter count&lt;/li&gt;
3237 &lt;li&gt;Make sure the array size and the array limit used when initialising
3238 the palette size is the same.&lt;/li&gt;
3239 &lt;li&gt;Fix array printing.&lt;/li&gt;
3240 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
3241 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
3242 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
3243 with more GCC compiler warnings.&lt;/li&gt;
3244
3245 &lt;/ul&gt;
3246
3247 &lt;p&gt;This change bring together patches for lsdvd in use in various
3248 Linux and Unix distributions, as well as patches submitted to the
3249 project the last nine years. Please check it out. :)&lt;/p&gt;
3250 </description>
3251 </item>
3252
3253 <item>
3254 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
3255 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
3256 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
3257 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
3258 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
3259 project&lt;/a&gt; provide a Linux solution for schools, including a
3260 powerful desktop with education software, a central server providing
3261 web pages, user database, user home directories, central login and PXE
3262 boot of both clients without disk and the installation to install Debian
3263 Edu on machines with disk (and a few other services perhaps to small
3264 to mention here). We in the Debian Edu team are currently working on
3265 the Jessie based version, trying to get everything in shape before the
3266 freeze, to avoid having to maintain our own package repository in the
3267 future. The
3268 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
3269 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
3270 work left. Some fatal problems block testing, breaking the installer,
3271 but it is possible to work around these to get anyway. Here is a
3272 recipe on how to get the installation limping along.&lt;/p&gt;
3273
3274 &lt;p&gt;First, download the test ISO via
3275 &lt;a href=&quot;ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso&quot;&gt;ftp&lt;/a&gt;,
3276 &lt;a href=&quot;http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso&quot;&gt;http&lt;/a&gt;
3277 or rsync (use
3278 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
3279 The ISO build was broken on Tuesday, so we do not get a new ISO every
3280 12 hours or so, but thankfully the ISO we already got we are able to
3281 install with some tweaking.&lt;/p&gt;
3282
3283 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
3284 (use Alt-Ctrl-F2), run&lt;/p&gt;
3285
3286 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3287 nano /usr/bin/edu-eatmydata-install
3288 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3289
3290 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
3291 optimization. Return to the installation, select the profile you want
3292 and continue. Without this change, exim4-config will fail to install
3293 due to a known bug in eatmydata.&lt;/p&gt;
3294
3295 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
3296 this do not work, figure out what your correct value would be. All my
3297 test machines need /dev/sda, so I have no advice if it do not fit
3298 your need.&lt;/p&gt;
3299
3300 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
3301 root after the initial boot from hard drive, and install the
3302 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3303 or mate. If you want several desktop options, install more than one
3304 metapackage. Once this is done, reboot and you should have a working
3305 graphical login screen. This workaround should no longer be needed
3306 once the education-tasks package version 1.801 enter testing in two
3307 days.&lt;/p&gt;
3308
3309 &lt;p&gt;I believe the ISO build will start working on two days when the new
3310 tasksel package enter testing and Steve McIntyre get a chance to
3311 update the debian-cd git repository. The eatmydata, grub and desktop
3312 issues are already fixed in unstable and testing, and should show up
3313 on the ISO as soon as the ISO build start working again. Well the
3314 eatmydata optimization is really just disabled. The proper fix
3315 require an upload by the eatmydata maintainer applying the patch
3316 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
3317 The rest have proper fixes in unstable.&lt;/p&gt;
3318
3319 &lt;p&gt;I hope this get you going with the installation testing, as we are
3320 quickly running out of time trying to get our Jessie based
3321 installation ready before the distribution freeze in a month.&lt;/p&gt;
3322 </description>
3323 </item>
3324
3325 <item>
3326 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
3327 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
3328 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
3329 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
3330 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
3331 to handle my fairly large DVD collection. It is a nice command line
3332 tool to get details about a DVD, like title, tracks, track length,
3333 etc, in XML, Perl or human readable format. But lsdvd have not seen
3334 any new development since 2006 and had a few irritating bugs affecting
3335 its use with some DVDs. Upstream seemed to be dead, and in January I
3336 sent a small probe asking for a version control repository for the
3337 project, without any reply. But I use it regularly and would like to
3338 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
3339 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
3340 the project admin, and after getting a reply from him explaining that
3341 he was no longer interested in the project, I asked if I could take
3342 over. And yesterday, I became project admin.&lt;/p&gt;
3343
3344 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
3345 maintainer interested in joining forces to maintain the upstream
3346 project, and I hope we can get a new release out fairly quickly,
3347 collecting the patches spread around on the internet into on place.
3348 I&#39;ve added the relevant Debian patches to the freshly created git
3349 repository, and expect the Gentoo patches to make it too. If you got
3350 a DVD collection and care about command line tools, check out
3351 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
3352 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
3353 list&lt;/a&gt;. :)&lt;/p&gt;
3354 </description>
3355 </item>
3356
3357 <item>
3358 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
3359 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
3360 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
3361 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
3362 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
3363 a lot quicker. When we install more than 2000 packages in
3364 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
3365 tasksel in the installer, unpacking the binary packages take forever.
3366 A part of the slow I/O issue was discussed in
3367 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
3368 much file system sync-ing done by dpkg, which is the package
3369 responsible for unpacking the binary packages. Other parts (like code
3370 executed by postinst scripts) might also sync to disk during
3371 installation. All this sync-ing to disk do not really make sense to
3372 me. If the machine crash half-way through, I start over, I do not try
3373 to salvage the half installed system. So the failure sync-ing is
3374 supposed to protect against, hardware or system crash, is not really
3375 relevant while the installer is running.&lt;/p&gt;
3376
3377 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
3378 system sync()-ing in a fairly non-intrusive way, without the need to
3379 change the code in several packages. The idea is not new, but I have
3380 not heard anyone propose the approach using dpkg-divert before. It
3381 depend on the small and clever package
3382 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
3383 uses LD_PRELOAD to replace the system functions for syncing data to
3384 disk with functions doing nothing, thus allowing programs to live
3385 dangerous while speeding up disk I/O significantly. Instead of
3386 modifying the implementation of dpkg, apt and tasksel (which are the
3387 packages responsible for selecting, fetching and installing packages),
3388 it occurred to me that we could just divert the programs away, replace
3389 them with a simple shell wrapper calling
3390 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
3391 Two days ago I decided to test the idea, and wrapped up a simple
3392 implementation for the Debian Edu udeb.&lt;/p&gt;
3393
3394 &lt;p&gt;The effect was stunning. In my first test it reduced the running
3395 time of the pkgsel step (installing tasks) from 64 to less than 44
3396 minutes (20 minutes shaved off the installation) on an old Dell
3397 Latitude D505 machine. I am not quite sure what the optimised time
3398 would have been, as I messed up the testing a bit, causing the debconf
3399 priority to get low enough for two questions to pop up during
3400 installation. As soon as I saw the questions I moved the installation
3401 along, but do not know how long the question were holding up the
3402 installation. I did some more measurements using Debian Edu Jessie,
3403 and got these results. The time measured is the time stamp in
3404 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
3405 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
3406 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3407 timing thus do not depend on how quickly the user handle the tasksel
3408 dialog.&lt;/p&gt;
3409
3410 &lt;p&gt;&lt;table&gt;
3411
3412 &lt;tr&gt;
3413 &lt;th&gt;Machine/setup&lt;/th&gt;
3414 &lt;th&gt;Original tasksel&lt;/th&gt;
3415 &lt;th&gt;Optimised tasksel&lt;/th&gt;
3416 &lt;th&gt;Reduction&lt;/th&gt;
3417 &lt;/tr&gt;
3418
3419 &lt;tr&gt;
3420 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
3421 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
3422 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
3423 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
3424 &lt;/tr&gt;
3425
3426 &lt;tr&gt;
3427 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
3428 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
3429 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
3430 &lt;td&gt;23 min 40%&lt;/td&gt;
3431 &lt;/tr&gt;
3432
3433 &lt;tr&gt;
3434 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
3435 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
3436 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
3437 &lt;td&gt;11 min 50%&lt;/td&gt;
3438 &lt;/tr&gt;
3439
3440 &lt;tr&gt;
3441 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
3442 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
3443 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
3444 &lt;td&gt;2 min 33%&lt;/td&gt;
3445 &lt;/tr&gt;
3446
3447 &lt;tr&gt;
3448 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
3449 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
3450 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
3451 &lt;td&gt;4 min 21%&lt;/td&gt;
3452 &lt;/tr&gt;
3453
3454 &lt;/table&gt;&lt;/p&gt;
3455
3456 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
3457 time is spent downloading packages. The connection to the Internet
3458 was 100Mbit/s during testing, so downloading should not be a
3459 significant factor in the measurement. Download typically took a few
3460 seconds to a few minutes, depending on the amount of packages being
3461 installed.&lt;/p&gt;
3462
3463 &lt;p&gt;The speedup is implemented by using two hooks in
3464 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
3465 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
3466 finish-install.d hook to remove the divert at the end of the
3467 installation. I picked the pre-pkgsel.d hook instead of the
3468 post-base-installer.d hook because I test using an ISO without the
3469 eatmydata package included, and the post-base-installer.d hook in
3470 Debian Edu can only operate on packages included in the ISO. The
3471 negative effect of this is that I am unable to activate this
3472 optimization for the kernel installation step in d-i. If the code is
3473 moved to the post-base-installer.d hook, the speedup would be larger
3474 for the entire installation.&lt;/p&gt;
3475
3476 &lt;p&gt;I&#39;ve implemented this in the
3477 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
3478 git repository, and plan to provide the optimization as part of the
3479 Debian Edu installation. If you want to test this yourself, you can
3480 create two files in the installer (or in an udeb). One shell script
3481 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
3482
3483 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3484 #!/bin/sh
3485 set -e
3486 . /usr/share/debconf/confmodule
3487 info() {
3488 logger -t my-pkgsel &quot;info: $*&quot;
3489 }
3490 error() {
3491 logger -t my-pkgsel &quot;error: $*&quot;
3492 }
3493 override_install() {
3494 apt-install eatmydata || true
3495 if [ -x /target/usr/bin/eatmydata ] ; then
3496 for bin in dpkg apt-get aptitude tasksel ; do
3497 file=/usr/bin/$bin
3498 # Test that the file exist and have not been diverted already.
3499 if [ -f /target$file ] ; then
3500 info &quot;diverting $file using eatmydata&quot;
3501 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
3502 &gt; /target$file.edu
3503 chmod 755 /target$file.edu
3504 in-target dpkg-divert --package debian-edu-config \
3505 --rename --quiet --add $file
3506 ln -sf ./$bin.edu /target$file
3507 else
3508 error &quot;unable to divert $file, as it is missing.&quot;
3509 fi
3510 done
3511 else
3512 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
3513 fi
3514 }
3515
3516 override_install
3517 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3518
3519 &lt;p&gt;To clean up, another shell script should go into
3520 /usr/lib/finish-install.d/ with code like this:
3521
3522 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3523 #! /bin/sh -e
3524 . /usr/share/debconf/confmodule
3525 error() {
3526 logger -t my-finish-install &quot;error: $@&quot;
3527 }
3528 remove_install_override() {
3529 for bin in dpkg apt-get aptitude tasksel ; do
3530 file=/usr/bin/$bin
3531 if [ -x /target$file.edu ] ; then
3532 rm /target$file
3533 in-target dpkg-divert --package debian-edu-config \
3534 --rename --quiet --remove $file
3535 rm /target$file.edu
3536 else
3537 error &quot;Missing divert for $file.&quot;
3538 fi
3539 done
3540 sync # Flush file buffers before continuing
3541 }
3542
3543 remove_install_override
3544 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3545
3546 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
3547 edu-eatmydata-install and call it from the pre-pkgsel.d and
3548 finish-install.d scripts.&lt;/p&gt;
3549
3550 &lt;p&gt;By now you might ask if this change should get into the normal
3551 Debian installer too? I suspect it should, but am not sure the
3552 current debian-installer coordinators find it useful enough. It also
3553 depend on the side effects of the change. I&#39;m not aware of any, but I
3554 guess we will see if the change is safe after some more testing.
3555 Perhaps there is some package in Debian depending on sync() and
3556 fsync() having effect? Perhaps it should go into its own udeb, to
3557 allow those of us wanting to enable it to do so without affecting
3558 everyone.&lt;/p&gt;
3559
3560 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
3561 will break installation of all programs using gnutls because of
3562 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
3563 eatmydata package in Debian will solve it.&lt;/p&gt;
3564
3565 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
3566 the optimization work again. And I have discovered that the
3567 dpkg-divert trick is not really needed and implemented a slightly
3568 simpler approach as part of the debian-edu-install package. See
3569 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
3570
3571 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
3572 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
3573 triggering on i386 made it into testing, and broke this installation
3574 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
3575 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
3576 </description>
3577 </item>
3578
3579 <item>
3580 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
3581 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
3582 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
3583 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
3584 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
3585 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
3586 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
3587 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
3588 learn that there is a large set of publicly available key servers to
3589 use when looking for peoples public key. So far I have used
3590 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3591 were misbehaving, but those days are ended. The servers I have used
3592 up until yesterday have been slow and some times unavailable. I hope
3593 those problems are gone now.&lt;/p&gt;
3594
3595 &lt;p&gt;Behind the round robin DNS entry of the
3596 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
3597 there is a pool of more than 100 keyservers which are checked every
3598 day to ensure they are well connected and up to date. It must be
3599 better than what I have used so far. :)&lt;/p&gt;
3600
3601 &lt;p&gt;Yesterdays speaker told me that the service is the default
3602 keyserver provided by the default configuration in GnuPG, but this do
3603 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
3604
3605 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
3606 line:&lt;/p&gt;
3607
3608 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3609 keyserver pool.sks-keyservers.net
3610 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3611
3612 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
3613 entries in DNS. Just for fun, I did just that at work, so now every
3614 user of GnuPG at the University of Oslo should find a OpenGPG
3615 keyserver automatically should their need it:&lt;/p&gt;
3616
3617 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3618 % host -t srv _pgpkey-http._tcp.uio.no
3619 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
3620 %
3621 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3622
3623 &lt;p&gt;Now if only
3624 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
3625 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
3626 very happy. It can look up a given key or search for a user ID, but I
3627 normally do not want that, but to find a trust path from my key to
3628 another key. Given a user ID or key ID, I would like to find (and
3629 download) the keys representing a signature path from my key to the
3630 key in question, to be able to get a trust path between the two keys.
3631 This is as far as I can tell not possible today. Perhaps something
3632 for a future version of the protocol?&lt;/p&gt;
3633 </description>
3634 </item>
3635
3636 <item>
3637 <title>From English wiki to translated PDF and epub via Docbook</title>
3638 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
3639 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
3640 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
3641 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
3642 project&lt;/a&gt; provide an instruction manual for teachers, system
3643 administrators and other users that contain useful tips for setting up
3644 and maintaining a Debian Edu installation. This text is about how the
3645 text processing of this manual is handled in the project.&lt;/p&gt;
3646
3647 &lt;p&gt;One goal of the project is to provide information in the native
3648 language of its users, and for this we need to handle translations.
3649 But we also want to make sure each language contain the same
3650 information, so for this we need a good way to keep the translations
3651 in sync. And we want it to be easy for our users to improve the
3652 documentation, avoiding the need to learn special formats or tools to
3653 contribute, and the obvious way to do this is to make it possible to
3654 edit the documentation using a web browser. We also want it to be
3655 easy for translators to keep the translation up to date, and give them
3656 help in figuring out what need to be translated. Here is the list of
3657 tools and the process we have found trying to reach all these
3658 goals.&lt;/p&gt;
3659
3660 &lt;p&gt;We maintain the authoritative source of our manual in the
3661 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
3662 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
3663 front page with references to the different chapters, several pages
3664 for each chapter, and finally one &quot;collection page&quot; gluing all the
3665 chapters together into one large web page (aka
3666 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
3667 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
3668 processing and translations. Thanks to the fact that the
3669 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
3670 wiki.debian.org support exporting pages in
3671 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
3672 the list of pages to export using the raw version of the AllInOne
3673 page, loop over each of them to generate a Docbook XML version of the
3674 manual. This process also download images and transform image
3675 references to use the locally downloaded images. The generated
3676 Docbook XML files are slightly broken, so some post-processing is done
3677 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
3678 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3679 a handfull of images. The XML file can now be used to generate PDF, HTML
3680 and epub versions of the English manual. This is the basic step of
3681 our process, making PDF (using dblatex), HTML (using xsltproc) and
3682 epub (using dbtoepub) version from Docbook XML, and the resulting files
3683 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
3684
3685 &lt;p&gt;But English documentation is not enough for us. We want translated
3686 documentation too, and we want to make it easy for translators to
3687 track the English original. For this we use the
3688 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
3689 which allow us to transform the English Docbook XML file into a
3690 translation file (a .pot file), usable with the normal gettext based
3691 translation tools used by those translating free software. The pot
3692 file is used to create and maintain translation files (several .po
3693 files), which the translations update with the native language
3694 translations of all titles, paragraphs and blocks of text in the
3695 original. The next step is combining the original English Docbook XML
3696 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3697 create a translated Docbook XML file (in this case
3698 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3699 translated, if the translation is not complete) Docbook XML file can
3700 then be used like the original to create a PDF, HTML and epub version
3701 of the documentation.&lt;/p&gt;
3702
3703 &lt;p&gt;The translators use different tools to edit the .po files. We
3704 recommend using
3705 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
3706 while some use emacs and vi, others can use web based editors like
3707 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
3708 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
3709 is where the .po file end up, in our git repository. Updated
3710 translations can either be committed directly to git, or submitted as
3711 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
3712 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
3713
3714 &lt;p&gt;One challenge is images, which both might need to be translated (if
3715 they show translated user applications), and are needed in different
3716 formats when creating PDF and HTML versions (epub is a HTML version in
3717 this regard). For this we transform the original PNG images to the
3718 needed density and format during build, and have a way to provide
3719 translated images by storing translated versions in
3720 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3721 package maintainers know more.&lt;/p&gt;
3722
3723 &lt;p&gt;If you wonder what the result look like, we provide
3724 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
3725 of the documentation packages on the web&lt;/a&gt;. See for example the
3726 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
3727 PDF version&lt;/a&gt; or the
3728 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
3729 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
3730 but perhaps it will be done in the future.&lt;/p&gt;
3731
3732 &lt;p&gt;To learn more, check out
3733 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
3734 debian-edu-doc package&lt;/a&gt;,
3735 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
3736 manual on the wiki&lt;/a&gt; and
3737 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
3738 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
3739 </description>
3740 </item>
3741
3742 <item>
3743 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
3744 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
3745 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
3746 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
3747 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
3748 related packages relevant for the computer installed automatically.
3749 So I implemented one, using
3750 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
3751 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
3752 run tasksel as user root. You should be presented with a new option,
3753 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
3754 select it, tasksel will install the packages isenkram claim is fit for
3755 the current hardware, hot pluggable or not.&lt;p&gt;
3756
3757 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
3758 description, and the other is the script used to extract the list of
3759 packages to install. The first part is in
3760 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
3761 this:&lt;/p&gt;
3762
3763 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3764 Task: isenkram
3765 Section: hardware
3766 Description: Hardware specific packages (autodetected by isenkram)
3767 Based on the detected hardware various hardware specific packages are
3768 proposed.
3769 Test-new-install: mark show
3770 Relevance: 8
3771 Packages: for-current-hardware
3772 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3773
3774 &lt;p&gt;The second part is in
3775 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
3776 this:&lt;/p&gt;
3777
3778 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3779 #!/bin/sh
3780 #
3781 (
3782 isenkram-lookup
3783 isenkram-autoinstall-firmware -l
3784 ) | sort -u
3785 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3786
3787 &lt;p&gt;All in all, a very short and simple implementation making it
3788 trivial to install the hardware dependent package we all may want to
3789 have installed on our machines. I&#39;ve not been able to find a way to
3790 get tasksel to tell you exactly which packages it plan to install
3791 before doing the installation. So if you are curious or careful,
3792 check the output from the isenkram-* command line tools first.&lt;/p&gt;
3793
3794 &lt;p&gt;The information about which packages are handling which hardware is
3795 fetched either from the isenkram package itself in
3796 /usr/share/isenkram/, from git.debian.org or from the APT package
3797 database (using the Modaliases header). The APT package database
3798 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3799 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
3800 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
3801 the python-apt code (bug
3802 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
3803 workaround I was able to get rid of the file descriptor leak and
3804 reduce the memory leak from ~30 MiB per hardware detection down to
3805 around 2 MiB per hardware detection. It should make the desktop
3806 daemon a lot more useful. The fix is in version 0.7 uploaded to
3807 unstable today.&lt;/p&gt;
3808
3809 &lt;p&gt;I believe the current way of mapping hardware to packages in
3810 Isenkram is is a good draft, but in the future I expect isenkram to
3811 use the AppStream data source for this. A proposal for getting proper
3812 AppStream support into Debian is floating around as
3813 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
3814 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
3815 project&lt;/a&gt; will take place this summer to improve the situation. I
3816 look forward to seeing the result, and welcome patches for isenkram to
3817 start using the information when it is ready.&lt;/p&gt;
3818
3819 &lt;p&gt;If you want your package to map to some specific hardware, either
3820 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
3821 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
3822 package&lt;/a&gt; or submit a bug report with the details to the isenkram
3823 package. See also
3824 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
3825 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
3826 the information will be migrated to AppStream eventually, but for the
3827 moment I got no better place to store it.&lt;/p&gt;
3828 </description>
3829 </item>
3830
3831 <item>
3832 <title>FreedomBox milestone - all packages now in Debian Sid</title>
3833 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
3834 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
3835 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
3836 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
3837 project&lt;/a&gt; is working on providing the software and hardware to make
3838 it easy for non-technical people to host their data and communication
3839 at home, and being able to communicate with their friends and family
3840 encrypted and away from prying eyes. It is still going strong, and
3841 today a major mile stone was reached.&lt;/p&gt;
3842
3843 &lt;p&gt;Today, the last of the packages currently used by the project to
3844 created the system images were accepted into Debian Unstable. It was
3845 the freedombox-setup package, which is used to configure the images
3846 during build and on the first boot. Now all one need to get going is
3847 the build code from the freedom-maker git repository and packages from
3848 Debian. And once the freedombox-setup package enter testing, we can
3849 build everything directly from Debian. :)&lt;/p&gt;
3850
3851 &lt;p&gt;Some key packages used by Freedombox are
3852 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
3853 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
3854 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
3855 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
3856 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
3857 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
3858 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
3859 are plans to integrate more packages into the setup. User
3860 documentation is maintained on the Debian wiki. Please
3861 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
3862 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
3863
3864 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
3865 setup, run this on a Debian machine using a user with sudo rights to
3866 become root:&lt;/p&gt;
3867
3868 &lt;p&gt;&lt;pre&gt;
3869 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3870 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3871 u-boot-tools
3872 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3873 freedom-maker
3874 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3875 &lt;/pre&gt;&lt;/p&gt;
3876
3877 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
3878 devices. See the README in the freedom-maker git repo for more
3879 details on the build. If you do not want all three images, trim the
3880 make line. Note that the virtualbox-image target is not really
3881 virtualbox specific. It create a x86 image usable in kvm, qemu,
3882 vmware and any other x86 virtual machine environment. You might need
3883 the version of vmdebootstrap in Jessie to get the build working, as it
3884 include fixes for a race condition with kpartx.&lt;/p&gt;
3885
3886 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
3887 method, boot a Debian Wheezy ISO and use this boot argument to load
3888 the preseed values:&lt;/p&gt;
3889
3890 &lt;p&gt;&lt;pre&gt;
3891 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;
3892 &lt;/pre&gt;&lt;/p&gt;
3893
3894 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
3895 it still work.&lt;/p&gt;
3896
3897 &lt;p&gt;If you wonder how to help, one task you could look at is using
3898 systemd as the boot system. It will become the default for Linux in
3899 Jessie, so we need to make sure it is usable on the Freedombox. I did
3900 a simple test a few weeks ago, and noticed dnsmasq failed to start
3901 during boot when using systemd. I suspect there are other problems
3902 too. :) To detect problems, there is a test suite included, which can
3903 be run from the plinth web interface.&lt;/p&gt;
3904
3905 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
3906 us get the new release published. :) Please join us on
3907 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
3908 irc.debian.org)&lt;/a&gt; and
3909 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3910 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3911 </description>
3912 </item>
3913
3914 <item>
3915 <title>S3QL, a locally mounted cloud file system - nice free software</title>
3916 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
3917 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
3918 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
3919 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
3920 solution for use at home. My requirements are simple, it must be
3921 cheap and locally encrypted (in other words, I keep the encryption
3922 keys, the storage provider do not have access to my private files).
3923 One idea me and my friends had many years ago, before the cloud
3924 storage providers showed up, was to use Google mail as storage,
3925 writing a Linux block device storing blocks as emails in the mail
3926 service provided by Google, and thus get heaps of free space. On top
3927 of this one can add encryption, RAID and volume management to have
3928 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3929 I never found time to implement such system. But the last few weeks I
3930 have looked at a system called
3931 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
3932 mounted network backed file system with the features I need.&lt;/p&gt;
3933
3934 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
3935 handling several different storage providers, any with Amazon S3,
3936 Google Drive or OpenStack API. There are heaps of such storage
3937 providers. S3QL can also use a local directory as storage, which
3938 combined with sshfs allow for file storage on any ssh server. S3QL
3939 include support for encryption, compression, de-duplication, snapshots
3940 and immutable file systems, allowing me to mount the remote storage as
3941 a local mount point, look at and use the files as if they were local,
3942 while the content is stored in the cloud as well. This allow me to
3943 have a backup that should survive fire. The file system can not be
3944 shared between several machines at the same time, as only one can
3945 mount it at the time, but any machine with the encryption key and
3946 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
3947
3948 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
3949 package is included already. So to get started, run &lt;tt&gt;apt-get
3950 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
3951 Greenqloud, after reading their nice recipe on
3952 &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
3953 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
3954 in Iceland more than those in USA when it come to keeping my personal
3955 data safe and private, and thus would rather spend money on a company
3956 in Iceland. Another nice recipe is available from the article
3957 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
3958 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
3959 Admin magazine. When the provider is picked, figure out how to get
3960 the API key needed to connect to the storage API. With Greencloud,
3961 the key did not show up until I had added payment details to my
3962 account.&lt;/p&gt;
3963
3964 &lt;p&gt;Armed with the API access details, it is time to create the file
3965 system. First, create a new bucket in the cloud. This bucket is the
3966 file system storage area. I picked a bucket name reflecting the
3967 machine that was going to store data there, but any name will do.
3968 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
3969 the API login and password, and a locally created password. Store it
3970 all in ~root/.s3ql/authinfo2 like this:
3971
3972 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3973 [s3c]
3974 storage-url: s3c://s.greenqloud.com:443/bucket-name
3975 backend-login: API-login
3976 backend-password: API-password
3977 fs-passphrase: local-password
3978 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3979
3980 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
3981 but any sensible way to create a fairly random password should do it.
3982 Armed with these details, it is now time to run mkfs, entering the API
3983 details and password to create it:&lt;/p&gt;
3984
3985 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3986 # mkdir -m 700 /var/lib/s3ql-cache
3987 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3988 --ssl s3c://s.greenqloud.com:443/bucket-name
3989 Enter backend login:
3990 Enter backend password:
3991 Before using S3QL, make sure to read the user&#39;s guide, especially
3992 the &#39;Important Rules to Avoid Loosing Data&#39; section.
3993 Enter encryption password:
3994 Confirm encryption password:
3995 Generating random encryption key...
3996 Creating metadata tables...
3997 Dumping metadata...
3998 ..objects..
3999 ..blocks..
4000 ..inodes..
4001 ..inode_blocks..
4002 ..symlink_targets..
4003 ..names..
4004 ..contents..
4005 ..ext_attributes..
4006 Compressing and uploading metadata...
4007 Wrote 0.00 MB of compressed metadata.
4008 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4009
4010 &lt;p&gt;The next step is mounting the file system to make the storage available.
4011
4012 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4013 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4014 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
4015 Using 4 upload threads.
4016 Downloading and decompressing metadata...
4017 Reading metadata...
4018 ..objects..
4019 ..blocks..
4020 ..inodes..
4021 ..inode_blocks..
4022 ..symlink_targets..
4023 ..names..
4024 ..contents..
4025 ..ext_attributes..
4026 Mounting filesystem...
4027 # df -h /s3ql
4028 Filesystem Size Used Avail Use% Mounted on
4029 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
4030 #
4031 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4032
4033 &lt;p&gt;The file system is now ready for use. I use rsync to store my
4034 backups in it, and as the metadata used by rsync is downloaded at
4035 mount time, no network traffic (and storage cost) is triggered by
4036 running rsync. To unmount, one should not use the normal umount
4037 command, as this will not flush the cache to the cloud storage, but
4038 instead running the umount.s3ql command like this:
4039
4040 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4041 # umount.s3ql /s3ql
4042 #
4043 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4044
4045 &lt;p&gt;There is a fsck command available to check the file system and
4046 correct any problems detected. This can be used if the local server
4047 crashes while the file system is mounted, to reset the &quot;already
4048 mounted&quot; flag. This is what it look like when processing a working
4049 file system:&lt;/p&gt;
4050
4051 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4052 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
4053 Using cached metadata.
4054 File system seems clean, checking anyway.
4055 Checking DB integrity...
4056 Creating temporary extra indices...
4057 Checking lost+found...
4058 Checking cached objects...
4059 Checking names (refcounts)...
4060 Checking contents (names)...
4061 Checking contents (inodes)...
4062 Checking contents (parent inodes)...
4063 Checking objects (reference counts)...
4064 Checking objects (backend)...
4065 ..processed 5000 objects so far..
4066 ..processed 10000 objects so far..
4067 ..processed 15000 objects so far..
4068 Checking objects (sizes)...
4069 Checking blocks (referenced objects)...
4070 Checking blocks (refcounts)...
4071 Checking inode-block mapping (blocks)...
4072 Checking inode-block mapping (inodes)...
4073 Checking inodes (refcounts)...
4074 Checking inodes (sizes)...
4075 Checking extended attributes (names)...
4076 Checking extended attributes (inodes)...
4077 Checking symlinks (inodes)...
4078 Checking directory reachability...
4079 Checking unix conventions...
4080 Checking referential integrity...
4081 Dropping temporary indices...
4082 Backing up old metadata...
4083 Dumping metadata...
4084 ..objects..
4085 ..blocks..
4086 ..inodes..
4087 ..inode_blocks..
4088 ..symlink_targets..
4089 ..names..
4090 ..contents..
4091 ..ext_attributes..
4092 Compressing and uploading metadata...
4093 Wrote 0.89 MB of compressed metadata.
4094 #
4095 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4096
4097 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
4098 quick, about the same speed as local file access. Uploading large
4099 amount of data is to me limited by the bandwidth out of and into my
4100 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
4101 which is very close to my upload speed, and downloading the same
4102 Debian installation ISO gave me 610 kiB/s, close to my download speed.
4103 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
4104 network, not the file system code. I do not know what a good cache
4105 size would be, but suspect that the cache should e larger than your
4106 working set.&lt;/p&gt;
4107
4108 &lt;p&gt;I mentioned that only one machine can mount the file system at the
4109 time. If another machine try, it is told that the file system is
4110 busy:&lt;/p&gt;
4111
4112 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4113 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4114 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
4115 Using 8 upload threads.
4116 Backend reports that fs is still mounted elsewhere, aborting.
4117 #
4118 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4119
4120 &lt;p&gt;The file content is uploaded when the cache is full, while the
4121 metadata is uploaded once every 24 hour by default. To ensure the
4122 file system content is flushed to the cloud, one can either umount the
4123 file system, or ask S3QL to flush the cache and metadata using
4124 s3qlctrl:
4125
4126 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4127 # s3qlctrl upload-meta /s3ql
4128 # s3qlctrl flushcache /s3ql
4129 #
4130 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4131
4132 &lt;p&gt;If you are curious about how much space your data uses in the
4133 cloud, and how much compression and deduplication cut down on the
4134 storage usage, you can use s3qlstat on the mounted file system to get
4135 a report:&lt;/p&gt;
4136
4137 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4138 # s3qlstat /s3ql
4139 Directory entries: 9141
4140 Inodes: 9143
4141 Data blocks: 8851
4142 Total data size: 22049.38 MB
4143 After de-duplication: 21955.46 MB (99.57% of total)
4144 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
4145 Database size: 2.39 MB (uncompressed)
4146 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4147 #
4148 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4149
4150 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
4151 storage. I did not try to locate them all, but am aware of at least
4152 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
4153 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
4154 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
4155 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
4156 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
4157 accept payment in Bitcoin. Pick one that suit your need. Some of
4158 them provide several GiB of free storage, but the prize models are
4159 quite different and you will have to figure out what suits you
4160 best.&lt;/p&gt;
4161
4162 &lt;p&gt;While researching this blog post, I had a look at research papers
4163 and posters discussing the S3QL file system. There are several, which
4164 told me that the file system is getting a critical check by the
4165 science community and increased my confidence in using it. One nice
4166 poster is titled
4167 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
4168 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4169 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
4170 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4171 and Pamela Smith. Please have a look.&lt;/p&gt;
4172
4173 &lt;p&gt;Given my problems with different file systems earlier, I decided to
4174 check out the mounted S3QL file system to see if it would be usable as
4175 a home directory (in other word, that it provided POSIX semantics when
4176 it come to locking and umask handling etc). Running
4177 &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
4178 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
4179 no error was found. So the file system can be used for home
4180 directories, if one chooses to do so.&lt;/p&gt;
4181
4182 &lt;p&gt;If you do not want a locally file system, and want something that
4183 work without the Linux fuse file system, I would like to mention the
4184 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
4185 provide locally encrypted backup using a command line client. It have
4186 a nicer access control system, where one can split out read and write
4187 access, allowing some systems to write to the backup and others to
4188 only read from it.&lt;/p&gt;
4189
4190 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4191 activities, please send Bitcoin donations to my address
4192 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4193 </description>
4194 </item>
4195
4196 <item>
4197 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
4198 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
4199 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
4200 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
4201 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
4202 project&lt;/a&gt; is working on providing the software and hardware for
4203 making it easy for non-technical people to host their data and
4204 communication at home, and being able to communicate with their
4205 friends and family encrypted and away from prying eyes. It has been
4206 going on for a while, and is slowly progressing towards a new test
4207 release (0.2).&lt;/p&gt;
4208
4209 &lt;p&gt;And what day could be better than the Pi day to announce that the
4210 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
4211 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4212 system), and can also be installed using a Debian installer preseed
4213 file. The Debian based Freedombox is now based on Debian Jessie,
4214 where most of the needed packages used are already present. Only one,
4215 the freedombox-setup package, is missing. To try to build your own
4216 boot image to test the current status, fetch the freedom-maker scripts
4217 and build using
4218 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
4219 with a user with sudo access to become root:
4220
4221 &lt;pre&gt;
4222 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4223 freedom-maker
4224 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4225 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4226 u-boot-tools
4227 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4228 &lt;/pre&gt;
4229
4230 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
4231 devices. See the README for more details on the build. If you do not
4232 want all three images, trim the make line. But note that thanks to &lt;a
4233 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
4234 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
4235 kpartx call.&lt;/p&gt;
4236
4237 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
4238 method, boot a Debian Wheezy ISO and use this boot argument to load
4239 the preseed values:&lt;/p&gt;
4240
4241 &lt;pre&gt;
4242 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;
4243 &lt;/pre&gt;
4244
4245 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
4246 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
4247 currently hang while setting up APT sources. Killing the
4248 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
4249 installation will get the installation going. This affect all
4250 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
4251
4252 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
4253 us get the new release published. :) Please join us on
4254 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
4255 irc.debian.org)&lt;/a&gt; and
4256 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4257 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4258 </description>
4259 </item>
4260
4261 <item>
4262 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
4263 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
4264 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
4265 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
4266 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
4267 innetgr tools, because I needed them in
4268 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
4269 ng-utils, and it has served me well. I placed the project under the
4270 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
4271 repository. But many years ago, the CVS repository was dropped (lost,
4272 not migrated to new hardware, not sure), and the project have lacked a
4273 proper home since then.&lt;/p&gt;
4274
4275 &lt;p&gt;Last summer, I had a look at the package and made a new release
4276 fixing a irritating crash bug, but was unable to store the changes in
4277 a proper source control system. I applied for a project on
4278 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
4279 to follow up on it. Until today. :)&lt;/p&gt;
4280
4281 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
4282 now have a new home, and a git repository with the highlight of the
4283 history of the project. I published all release tarballs and imported
4284 them into the git repository. As the project is really stable and not
4285 expected to gain new features any time soon, I decided to make a new
4286 release and call it 1.0. Visit the new project home on
4287 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
4288 if you want to check it out. The new version is also uploaded into
4289 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
4290 </description>
4291 </item>
4292
4293 <item>
4294 <title>Testing sysvinit from experimental in Debian Hurd</title>
4295 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
4296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
4297 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
4298 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
4299 their changes into sysvinit, to allow them to use the normal sysvinit
4300 boot system instead of their old one. This follow up on the
4301 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
4302 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
4303 get Debian on Hurd working more like Debian on Linux. To get started,
4304 I downloaded a prebuilt hard disk image from
4305 &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;,
4306 and started it using virt-manager.&lt;/p&gt;
4307
4308 &lt;p&gt;The first think I had to do after logging in (root without any
4309 password) was to get the network operational. I followed
4310 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
4311 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
4312 commands as root to get the machine to accept a IP address from the
4313 kvm internal DHCP server:&lt;/p&gt;
4314
4315 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4316 settrans -fgap /dev/netdde /hurd/netdde
4317 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
4318 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
4319 dhclient /dev/eth0
4320 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4321
4322 &lt;p&gt;After this, the machine had internet connectivity, and I could
4323 upgrade it and install the sysvinit packages from experimental and
4324 enable it as the default boot system in Hurd.&lt;/p&gt;
4325
4326 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
4327 running on the machine it for ssh login to work a password need to be
4328 set. Also, note that a bug somewhere in openssh on Hurd block
4329 compression from working. Remember to turn that off on the client
4330 side.&lt;/p&gt;
4331
4332 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
4333 stuff:&lt;/p&gt;
4334
4335 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4336 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
4337 deb http://http.debian.net/debian/ experimental main
4338 EOF
4339 apt-get update
4340 apt-get dist-upgrade
4341 apt-get install -t experimental initscripts sysv-rc sysvinit \
4342 sysvinit-core sysvinit-utils
4343 update-alternatives --config runsystem
4344 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4345
4346 &lt;p&gt;To reboot after switching boot system, you have to use
4347 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
4348 yet a sysvinit process able to receive the signals from the normal
4349 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
4350 upgrading every package and rebooting, the network come up with DHCP
4351 after boot as it should, and the settrans/pkill hack mentioned at the
4352 start is no longer needed. But for some strange reason, there are no
4353 longer any login prompt in the virtual console, so I logged in using
4354 ssh instead.
4355
4356 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
4357 fail some times. No idea what the cause is, but hope the Hurd porters
4358 figure it out. At least Justus said on IRC (#debian-hurd on
4359 irc.debian.org) that they are aware of the problem. A way to reduce
4360 the impact is to upgrade to the Hurd packages built by Justus by
4361 adding this repository to the machine:&lt;/p&gt;
4362
4363 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4364 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
4365 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4366 EOF
4367 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4368
4369 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
4370 http://ftp.debian-ports.org/debian, because some of the packages in
4371 unstable do not yet include the required patches that are lingering in
4372 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
4373
4374 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4375 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
4376 i emacs - GNU Emacs editor (metapackage)
4377 i gdb - GNU Debugger
4378 i hurd-recommended - Miscellaneous translators
4379 i isc-dhcp-client - ISC DHCP client
4380 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4381 i libc-bin - Embedded GNU C Library: Binaries
4382 i libc-dev-bin - Embedded GNU C Library: Development binaries
4383 i libc0.3 - Embedded GNU C Library: Shared libraries
4384 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4385 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4386 i multiarch-support - Transitional package to ensure multiarch compatibilit
4387 i A x11-common - X Window System (X.Org) infrastructure
4388 i xorg - X.Org X Window System
4389 i A xserver-xorg - X.Org X server
4390 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4391 #
4392 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4393
4394 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
4395 X.org did not work out of the box and I never took the time to follow
4396 the porters instructions to fix it. This time I was interested in the
4397 command line stuff.&lt;p&gt;
4398 </description>
4399 </item>
4400
4401 <item>
4402 <title>New chrpath release 0.16</title>
4403 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
4404 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
4405 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
4406 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
4407 find problems in C, C++ and Java code using static source code
4408 analysis. It can detect a lot of different problems, and is very
4409 useful to find memory and locking bugs in the error handling part of
4410 the source. The company behind it provide
4411 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
4412 a community service&lt;/a&gt;, and many hundred free software projects are
4413 already checked. A few days ago I decided to have a closer look at
4414 the Coverity system, and discovered that the
4415 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
4416 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
4417 projects I am involved with was already registered. But these are
4418 fairly big, and I would also like to have a small and easy project to
4419 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
4420 checking of the chrpath project&lt;/a&gt;. It was
4421 added to the checker and discovered seven potential defects. Six of
4422 these were real, mostly resource &quot;leak&quot; when the program detected an
4423 error. Nothing serious, as the resources would be released a fraction
4424 of a second later when the program exited because of the error, but it
4425 is nice to do it right in case the source of the program some time in
4426 the future end up in a library. Having fixed all defects and added
4427 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
4428 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
4429 publish a new release. These are the release notes:&lt;/p&gt;
4430
4431 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
4432
4433 &lt;ul&gt;
4434
4435 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
4436 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
4437 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
4438
4439 &lt;/ul&gt;
4440
4441 &lt;p&gt;You can
4442 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
4443 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
4444 project if something is wrong with the new release. The test suite
4445 did not discover any old errors, so if you find a new one, please also
4446 include a test suite check.&lt;/p&gt;
4447 </description>
4448 </item>
4449
4450 <item>
4451 <title>New chrpath release 0.15</title>
4452 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
4453 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
4454 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
4455 <description>&lt;p&gt;After many years break from the package and a vain hope that
4456 development would be continued by someone else, I finally pulled my
4457 acts together this morning and wrapped up a new release of chrpath,
4458 the command line tool to modify the rpath and runpath of already
4459 compiled ELF programs. The update was triggered by the persistence of
4460 Isha Vishnoi at IBM, which needed a new config.guess file to get
4461 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
4462 is working on. I checked the
4463 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
4464 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
4465 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
4466 packages for interesting patches (failed to find the source from
4467 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4468 These are the release notes:&lt;/p&gt;
4469
4470 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
4471
4472 &lt;ul&gt;
4473
4474 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
4475 with newer architectures. Thanks to isha vishnoi for the heads
4476 up.&lt;/li&gt;
4477
4478 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
4479
4480 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4481 Matthias Klose.&lt;/li&gt;
4482
4483 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
4484 Petr Machata found in Fedora.&lt;/li&gt;
4485
4486 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
4487 .dynamic is a NULL terminated string. Based on patch found in
4488 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
4489
4490 &lt;/ul&gt;
4491
4492 &lt;p&gt;You can
4493 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
4494 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
4495 project if something is wrong with the new release. The test suite
4496 did not discover any old errors, so if you find a new one, please also
4497 include a testsuite check.&lt;/p&gt;
4498 </description>
4499 </item>
4500
4501 <item>
4502 <title>Debian init.d boot script example for rsyslog</title>
4503 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
4504 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
4505 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
4506 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
4507 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
4508 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
4509 init.d scripts at all. Here is an example init.d script, ie a rewrite
4510 of /etc/init.d/rsyslog:&lt;/p&gt;
4511
4512 &lt;p&gt;&lt;pre&gt;
4513 #!/lib/init/init-d-script
4514 ### BEGIN INIT INFO
4515 # Provides: rsyslog
4516 # Required-Start: $remote_fs $time
4517 # Required-Stop: umountnfs $time
4518 # X-Stop-After: sendsigs
4519 # Default-Start: 2 3 4 5
4520 # Default-Stop: 0 1 6
4521 # Short-Description: enhanced syslogd
4522 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4523 # It is quite compatible to stock sysklogd and can be
4524 # used as a drop-in replacement.
4525 ### END INIT INFO
4526 DESC=&quot;enhanced syslogd&quot;
4527 DAEMON=/usr/sbin/rsyslogd
4528 &lt;/pre&gt;&lt;/p&gt;
4529
4530 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
4531 script was 137 lines, and the above is just 15 lines, most of it meta
4532 info/comments.&lt;/p&gt;
4533
4534 &lt;p&gt;How to do this, you ask? Well, one create a new script
4535 /lib/init/init-d-script looking something like this:
4536
4537 &lt;p&gt;&lt;pre&gt;
4538 #!/bin/sh
4539
4540 # Define LSB log_* functions.
4541 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
4542 # and status_of_proc is working.
4543 . /lib/lsb/init-functions
4544
4545 #
4546 # Function that starts the daemon/service
4547
4548 #
4549 do_start()
4550 {
4551 # Return
4552 # 0 if daemon has been started
4553 # 1 if daemon was already running
4554 # 2 if daemon could not be started
4555 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
4556 || return 1
4557 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4558 $DAEMON_ARGS \
4559 || return 2
4560 # Add code here, if necessary, that waits for the process to be ready
4561 # to handle requests from services started subsequently which depend
4562 # on this one. As a last resort, sleep for some time.
4563 }
4564
4565 #
4566 # Function that stops the daemon/service
4567 #
4568 do_stop()
4569 {
4570 # Return
4571 # 0 if daemon has been stopped
4572 # 1 if daemon was already stopped
4573 # 2 if daemon could not be stopped
4574 # other if a failure occurred
4575 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
4576 RETVAL=&quot;$?&quot;
4577 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
4578 # Wait for children to finish too if this is a daemon that forks
4579 # and if the daemon is only ever run from this initscript.
4580 # If the above conditions are not satisfied then add some other code
4581 # that waits for the process to drop all resources that could be
4582 # needed by services started subsequently. A last resort is to
4583 # sleep for some time.
4584 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
4585 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
4586 # Many daemons don&#39;t delete their pidfiles when they exit.
4587 rm -f $PIDFILE
4588 return &quot;$RETVAL&quot;
4589 }
4590
4591 #
4592 # Function that sends a SIGHUP to the daemon/service
4593 #
4594 do_reload() {
4595 #
4596 # If the daemon can reload its configuration without
4597 # restarting (for example, when it is sent a SIGHUP),
4598 # then implement that here.
4599 #
4600 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
4601 return 0
4602 }
4603
4604 SCRIPTNAME=$1
4605 scriptbasename=&quot;$(basename $1)&quot;
4606 echo &quot;SN: $scriptbasename&quot;
4607 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
4608 script=&quot;$1&quot;
4609 shift
4610 . $script
4611 else
4612 exit 0
4613 fi
4614
4615 NAME=$(basename $DAEMON)
4616 PIDFILE=/var/run/$NAME.pid
4617
4618 # Exit if the package is not installed
4619 #[ -x &quot;$DAEMON&quot; ] || exit 0
4620
4621 # Read configuration variable file if it is present
4622 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
4623
4624 # Load the VERBOSE setting and other rcS variables
4625 . /lib/init/vars.sh
4626
4627 case &quot;$1&quot; in
4628 start)
4629 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
4630 do_start
4631 case &quot;$?&quot; in
4632 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
4633 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
4634 esac
4635 ;;
4636 stop)
4637 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
4638 do_stop
4639 case &quot;$?&quot; in
4640 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
4641 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
4642 esac
4643 ;;
4644 status)
4645 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
4646 ;;
4647 #reload|force-reload)
4648 #
4649 # If do_reload() is not implemented then leave this commented out
4650 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
4651 #
4652 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
4653 #do_reload
4654 #log_end_msg $?
4655 #;;
4656 restart|force-reload)
4657 #
4658 # If the &quot;reload&quot; option is implemented then remove the
4659 # &#39;force-reload&#39; alias
4660 #
4661 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
4662 do_stop
4663 case &quot;$?&quot; in
4664 0|1)
4665 do_start
4666 case &quot;$?&quot; in
4667 0) log_end_msg 0 ;;
4668 1) log_end_msg 1 ;; # Old process is still running
4669 *) log_end_msg 1 ;; # Failed to start
4670 esac
4671 ;;
4672 *)
4673 # Failed to stop
4674 log_end_msg 1
4675 ;;
4676 esac
4677 ;;
4678 *)
4679 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
4680 exit 3
4681 ;;
4682 esac
4683
4684 :
4685 &lt;/pre&gt;&lt;/p&gt;
4686
4687 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
4688 lot. I did not really polish the approach, so it might not always
4689 work out of the box, but you get the idea. I did not try very hard to
4690 optimize it nor make it more robust either.&lt;/p&gt;
4691
4692 &lt;p&gt;A better argument for switching init system in Debian than reducing
4693 the size of init scripts (which is a good thing to do anyway), is to
4694 get boot system that is able to handle the kernel events sensibly and
4695 robustly, and do not depend on the boot to run sequentially. The boot
4696 and the kernel have not behaved sequentially in years.&lt;/p&gt;
4697 </description>
4698 </item>
4699
4700 <item>
4701 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
4702 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
4703 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
4704 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
4705 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
4706 remote display access is the preferred solution with oVirt and RedHat
4707 Enterprise Virtualization, and I was sad to discover the other day
4708 that the browser plugin needed to use these systems seamlessly was
4709 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
4710 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
4711 2013-04-01, so I decided to wrap up a package based on the great work
4712 from Cajus Pollmeier and put it in a collab-maint maintained git
4713 repository to get a package I could use. I would very much like
4714 others to help me maintain the package (or just take over, I do not
4715 mind), but as no-one had volunteered so far, I just uploaded it to
4716 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
4717
4718 &lt;p&gt;The source is now available from
4719 &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;
4720 </description>
4721 </item>
4722
4723 <item>
4724 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
4725 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
4726 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
4727 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
4728 <description>&lt;p&gt;The
4729 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
4730 program is a a very nice system to create virtual machine images. It
4731 create a image file, add a partition table, mount it and run
4732 debootstrap in the mounted directory to create a Debian system on a
4733 stick. Yesterday, I decided to try to teach it how to make images for
4734 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
4735 of a plan to simplify the build system for
4736 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
4737 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
4738 the virtualbox images, but its current build system made multistrap
4739 based system for Dreamplug images, and it is lacking support for
4740 Raspberry Pi.&lt;/p&gt;
4741
4742 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
4743 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4744 code and adjusted it to be able to build armel images on my amd64
4745 Debian laptop. I ended up giving vmdebootstrap five new options,
4746 allowing me to replicate the image creation process I use to make
4747 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
4748 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
4749 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
4750 call debootstrap with --foreign and to copy the handler into the
4751 generated chroot before running the second stage. This allow
4752 vmdebootstrap to create armel images on an amd64 host. Next I added
4753 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
4754 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
4755 given file system type, allowing me to create an image with a vfat
4756 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
4757 variant&lt;/tt&gt; option to allow me to create smaller images without the
4758 Debian base system packages installed. Finally, I added an option
4759 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
4760 as a boot loader. It is not needed on the Raspberry Pi and probably
4761 most other non-x86 architectures. The changes were accepted by the
4762 upstream author of vmdebootstrap yesterday and today, and is now
4763 available from
4764 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
4765 upstream project page&lt;/a&gt;.&lt;/p&gt;
4766
4767 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
4768 create a small script (the customize script) to add the non-free
4769 binary blob needed to boot the Raspberry Pi and the APT source
4770 list:&lt;/p&gt;
4771
4772 &lt;p&gt;&lt;pre&gt;
4773 #!/bin/sh
4774 set -e # Exit on first error
4775 rootdir=&quot;$1&quot;
4776 cd &quot;$rootdir&quot;
4777 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
4778 deb http://http.debian.net/debian/ jessie main contrib non-free
4779 EOF
4780 # Install non-free binary blob needed to boot Raspberry Pi. This
4781 # install a kernel somewhere too.
4782 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4783 -O $rootdir/usr/bin/rpi-update
4784 chmod a+x $rootdir/usr/bin/rpi-update
4785 mkdir -p $rootdir/lib/modules
4786 touch $rootdir/boot/start.elf
4787 chroot $rootdir rpi-update
4788 &lt;/pre&gt;&lt;/p&gt;
4789
4790 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
4791 to build the image:&lt;/p&gt;
4792
4793 &lt;pre&gt;
4794 sudo ./vmdebootstrap \
4795 --variant minbase \
4796 --arch armel \
4797 --distribution jessie \
4798 --mirror http://http.debian.net/debian \
4799 --image test.img \
4800 --size 600M \
4801 --bootsize 64M \
4802 --boottype vfat \
4803 --log-level debug \
4804 --verbose \
4805 --no-kernel \
4806 --no-extlinux \
4807 --root-password raspberry \
4808 --hostname raspberrypi \
4809 --foreign /usr/bin/qemu-arm-static \
4810 --customize `pwd`/customize \
4811 --package netbase \
4812 --package git-core \
4813 --package binutils \
4814 --package ca-certificates \
4815 --package wget \
4816 --package kmod
4817 &lt;/pre&gt;&lt;/p&gt;
4818
4819 &lt;p&gt;The list of packages being installed are the ones needed by
4820 rpi-update to make the image bootable on the Raspberry Pi, with the
4821 exception of netbase, which is needed by debootstrap to find
4822 /etc/hosts with the minbase variant. I really wish there was a way to
4823 set up an Raspberry Pi using only packages in the Debian archive, but
4824 that is not possible as far as I know, because it boots from the GPU
4825 using a non-free binary blob.&lt;/p&gt;
4826
4827 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
4828 probably a few others installed. I have not checked the complete
4829 build dependency list.&lt;/p&gt;
4830
4831 &lt;p&gt;The resulting image will not use the hardware floating point unit
4832 on the Raspberry PI, because the armel architecture in Debian is not
4833 optimized for that use. So the images created will be a bit slower
4834 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
4835 </description>
4836 </item>
4837
4838 <item>
4839 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
4840 <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>
4841 <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>
4842 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
4843 <description>&lt;p&gt;The last few days I came across a few good causes that should get
4844 wider attention. I recommend signing and donating to each one of
4845 these. :)&lt;/p&gt;
4846
4847 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
4848 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
4849 Women program which is a Google Summer of Code like initiative to get
4850 more women involved in free software. One debian sponsor has offered
4851 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
4852 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
4853 hope you will to. :)&lt;/p&gt;
4854
4855 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
4856 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
4857 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
4858 take place these days, and their need to fund the work. I&#39;ve already
4859 donated. Are you next?&lt;/p&gt;
4860
4861 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
4862 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4863 statement under the heading
4864 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
4865 Access&lt;/a&gt; for those of us asking for more focus on open access in the
4866 Norwegian government. So far 499 signatures. I hope you will sign it
4867 too.&lt;/p&gt;
4868 </description>
4869 </item>
4870
4871 <item>
4872 <title>Videos about the Freedombox project - for inspiration and learning</title>
4873 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
4874 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
4875 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
4876 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
4877 project&lt;/a&gt; have been going on for a while, and have presented the
4878 vision, ideas and solution several places. Here is a little
4879 collection of videos of talks and presentation of the project.&lt;/p&gt;
4880
4881 &lt;ul&gt;
4882
4883 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
4884 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
4885
4886 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
4887 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
4888
4889 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
4890 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4891 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
4892 (Youtube)&lt;/li&gt;
4893
4894 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
4895 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
4896
4897 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
4898 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
4899
4900 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
4901 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4902 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
4903
4904 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
4905 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
4906 (Youtube)&lt;/li&gt;
4907
4908 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
4909 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
4910
4911 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
4912 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
4913
4914 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
4915 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4916 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
4917
4918 &lt;/ul&gt;
4919
4920 &lt;p&gt;A larger list is available from
4921 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
4922 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
4923
4924 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
4925 Jessie is coming along quite well, and soon both Owncloud and using
4926 Tor should be available for testers of the Freedombox solution. :) In
4927 a few weeks I hope everything needed to test it is included in Debian.
4928 The withsqlite package is already in Debian, and the plinth package is
4929 pending in NEW. The third and vital part of that puzzle is the
4930 metapackage/setup framework, which is still pending an upload. Join
4931 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
4932 (#freedombox on irc.debian.org)&lt;/a&gt; and
4933 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4934 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4935 </description>
4936 </item>
4937
4938 <item>
4939 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
4940 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
4941 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
4942 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
4943 <description>&lt;p&gt;I was introduced to the
4944 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
4945 in 2010, when Eben Moglen presented his vision about serving the need
4946 of non-technical people to keep their personal information private and
4947 within the legal protection of their own homes. The idea is to give
4948 people back the power over their network and machines, and return
4949 Internet back to its intended peer-to-peer architecture. Instead of
4950 depending on a central service, the Freedombox will give everyone
4951 control over their own basic infrastructure.&lt;/p&gt;
4952
4953 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
4954 taken priority. But this summers nasty news about the misuse of trust
4955 and privilege exercised by the &quot;western&quot; intelligence gathering
4956 communities increased my eagerness to contribute to a point where I
4957 actually started working on the project a while back.&lt;/p&gt;
4958
4959 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
4960 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
4961 create a simple and cheap Debian based appliance that anyone can hook
4962 up in their home and get access to secure and private services and
4963 communication. The initial deployment platform have been the
4964 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
4965 which is a piece of hardware I do not own. So to be able to test what
4966 the current Freedombox setup look like, I had to come up with a way to install
4967 it on some hardware I do have access to. I have rewritten the
4968 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
4969 image build framework to use .deb packages instead of only copying
4970 setup into the boot images, and thanks to this rewrite I am able to
4971 set up any machine supported by Debian Wheezy as a Freedombox, using
4972 the previously mentioned deb (and a few support debs for packages
4973 missing in Debian).&lt;/p&gt;
4974
4975 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
4976 scripts
4977 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
4978 and a administrative web interface
4979 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
4980 withsqlite), as well as a privacy enhancing proxy based on
4981 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
4982 (freedombox-privoxy). There is also a web/javascript based XMPP
4983 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
4984 trying (unsuccessfully so far) to talk to the XMPP server
4985 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
4986 web interface is pluggable, and the goal is to use it to enable OpenID
4987 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4988 this is really working yet, see
4989 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
4990 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
4991 on github at the moment. The HTTP proxy is operational out of the
4992 box, and the admin web interface can be used to add/remove plinth
4993 users. I&#39;ve not been able to do anything else with it so far, but
4994 know there are several branches spread around github and other places
4995 with lots of half baked features.&lt;/p&gt;
4996
4997 &lt;p&gt;Anyway, if you want to have a look at the current state, the
4998 following recipes should work to give you a test machine to poke
4999 at.&lt;/p&gt;
5000
5001 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
5002
5003 &lt;ol&gt;
5004
5005 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
5006 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
5007 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
5008 to the Debian installer:&lt;p&gt;
5009 &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;
5010
5011 &lt;li&gt;Answer the few language/region/password questions and pick disk to
5012 install on.&lt;/li&gt;
5013
5014 &lt;li&gt;When the installation is finished and the machine have rebooted a
5015 few times, your Freedombox is ready for testing.&lt;/li&gt;
5016
5017 &lt;/ol&gt;
5018
5019 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
5020
5021 &lt;ol&gt;
5022
5023 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
5024 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
5025 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
5026 &lt;pre&gt;
5027 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
5028 &lt;/pre&gt;&lt;/li&gt;
5029 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
5030 &lt;pre&gt;
5031 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5032 apt-key add -
5033 apt-get update
5034 apt-get install freedombox-setup
5035 /usr/lib/freedombox/setup
5036 &lt;/pre&gt;&lt;/li&gt;
5037 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
5038
5039 &lt;/ol&gt;
5040
5041 &lt;p&gt;You can test it on other architectures too, but because the
5042 freedombox-privoxy package is binary, it will only work as intended on
5043 the architectures where I have had time to build the binary and put it
5044 in my APT repository. But do not let this stop you. It is only a
5045 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
5046
5047 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
5048 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
5049 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
5050 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
5051
5052 &lt;p&gt;Please let me know if this works for you, or if you have any
5053 problems. We gather on the IRC channel
5054 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
5055 irc.debian.org and the
5056 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
5057 mailing list&lt;/a&gt;.&lt;/p&gt;
5058
5059 &lt;p&gt;Once you get your freedombox operational, you can visit
5060 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
5061 welcome screen (dead end - do not be surprised if you are unable to
5062 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
5063 to look at the rest of plinth. The default user is &#39;admin&#39; and the
5064 default password is &#39;secret&#39;.&lt;/p&gt;
5065 </description>
5066 </item>
5067
5068 <item>
5069 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
5070 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
5071 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
5072 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
5073 <description>&lt;p&gt;Earlier, I reported about
5074 &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
5075 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
5076 told by IBM that the original disk should be thrown away. And as
5077 there no longer was a problem if I bricked the firmware, I decided
5078 today to try to install Intel firmware to replace the Lenovo firmware
5079 currently on the disk.&lt;/p&gt;
5080
5081 &lt;p&gt;I searched the Intel site for firmware, and found
5082 &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;
5083 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5084 according to the site should contain the latest firmware for SSD
5085 disks. I inserted the broken disk in one of my spare laptops and
5086 booted the ISO from a USB stick. The disk was recognized, but the
5087 program claimed the newest firmware already were installed and refused
5088 to insert any Intel firmware. So no change, and the disk is still
5089 unable to handle write load. :( I guess the only way to get them
5090 working would be if Lenovo releases new firmware. No idea how likely
5091 that is. Anyway, just blogging about this test for completeness. I
5092 got a working Samsung disk, and see no point in spending more time on
5093 the broken disks.&lt;/p&gt;
5094 </description>
5095 </item>
5096
5097 <item>
5098 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
5099 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
5100 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
5101 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
5102 <description>&lt;p&gt;Today I switched to
5103 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
5104 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
5105 my new Thinkpad X230, which was delivered with an
5106 &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
5107 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
5108 sustained writes. My hardware supplier have been very forthcoming in
5109 trying to find a solution, and after first trying with another
5110 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
5111 disk instead to fix it once and for all. The Samsung disk survived
5112 the installation of Debian with encrypted disks (filling the disk with
5113 random data during installation killed the first two), and I thus
5114 decided to trust it with my data. I have installed it as a Debian Edu
5115 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5116 server at home using Kerberos and LDAP, and will use it as my work
5117 station from now on.&lt;/p&gt;
5118
5119 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
5120 Debian Wheezy default installation need to be tuned a bit to increase
5121 performance and increase life time of the disk. The Linux kernel and
5122 user space applications do not yet adjust automatically to such
5123 environment. To make it easier for my self, I created a draft Debian
5124 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
5125 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
5126 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
5127 is set up to adjust the setup of the machine by just installing the
5128 package. If there is any non-SSD disk in the machine, the package
5129 will refuse to install, as I did not try to write any logic to sort
5130 file systems in SSD and non-SSD file systems.&lt;/p&gt;
5131
5132 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
5133 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5134 where I set up the machine with one large encrypted partition (in
5135 addition to /boot), put LVM on top of this and set up partitions on
5136 top of this again. See the README file in the package source for the
5137 references I used to pick the settings. At the moment these
5138 parameters are tuned:&lt;/p&gt;
5139
5140 &lt;ul&gt;
5141
5142 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
5143 (adding discard to /etc/crypttab)&lt;/li&gt;
5144
5145 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
5146 this case a cryptsetup partition) by changing issue_discards from
5147 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
5148
5149 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
5150 systems.&lt;/li&gt;
5151
5152 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
5153 /etc/fstab.&lt;/li&gt;
5154
5155 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
5156
5157 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
5158 cron.daily).&lt;/li&gt;
5159
5160 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
5161 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
5162
5163 &lt;/ul&gt;
5164
5165 &lt;p&gt;During installation, I cancelled the part where the installer fill
5166 the disk with random data, as this would kill the SSD performance for
5167 little gain. My goal with the encrypted file system is to ensure
5168 those stealing my laptop end up with a brick and not a working
5169 computer. I have no hope in keeping the really resourceful people
5170 from getting the data on the disk (see
5171 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
5172 Thus I concluded that adding the discard option to crypttab is the
5173 right thing to do.&lt;/p&gt;
5174
5175 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
5176 it for SSD, but others recommended deadline and a benchmark I found
5177 indicated that deadline might be better for interactive use.&lt;/p&gt;
5178
5179 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
5180 and ext4, but read that it would give a performance hit ever time a
5181 file is removed, and thought it best to that that slowdown once a day
5182 instead of during my work.&lt;/p&gt;
5183
5184 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5185 this is already done by Debian Edu.&lt;/p&gt;
5186
5187 &lt;p&gt;I have not yet started on the user space tuning. I expect
5188 iceweasel need some tuning, and perhaps other applications too, but
5189 have not yet had time to investigate those parts.&lt;/p&gt;
5190
5191 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
5192 there.&lt;/p&gt;
5193
5194 &lt;p&gt;As for the answer to the question in the title of this blog post,
5195 as far as I know, the only solution I know about is to replace the
5196 disk. It might be possible to flash it with Intel firmware instead of
5197 the Lenovo firmware. But I have not tried and did not want to do so
5198 without approval from Lenovo as I wanted to keep the warranty on the
5199 disk until a solution was found and they wanted the broken disks
5200 back.&lt;/p&gt;
5201 </description>
5202 </item>
5203
5204 <item>
5205 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
5206 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
5207 <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>
5208 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
5209 <description>&lt;p&gt;A few days ago, I wrote about
5210 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
5211 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
5212 was dying during installation because it is unable to cope with
5213 sustained write. My supplier is in contact with
5214 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
5215 replacement disk to try to fix the problem. They decided to send an
5216 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
5217
5218 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
5219 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5220 same firmware version as the original. This time my hope raised
5221 slightly as the installation progressed, as the original disk used to
5222 die after 4-7% of the disk was written to, while this time it kept
5223 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
5224 died again and I was back on square one. I still do not have a new
5225 laptop with a disk I can trust. I can not live with a disk that might
5226 lock up when I download a new
5227 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
5228 other large files. I look forward to hearing from my supplier with
5229 the next proposal from Lenovo.&lt;/p&gt;
5230
5231 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
5232 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5233 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
5234 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
5235 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
5236 P/N 45N8295, P0C38732.&lt;/p&gt;
5237
5238 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
5239 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
5240 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
5241 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
5242 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
5243 P/N 45N8295, P0C38732.&lt;/p&gt;
5244
5245 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
5246 SA, date and WNPP values. Mentioning all the details here in case
5247 someone is able to use the information to find a way to identify the
5248 failing disk among working ones (if any such working disk actually
5249 exist).&lt;/p&gt;
5250 </description>
5251 </item>
5252
5253 <item>
5254 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
5255 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
5256 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
5257 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
5258 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
5259 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5260 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
5261 member assosiation NUUG&lt;/a&gt; and
5262 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
5263 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
5264 Bitraf&lt;/a&gt;.&lt;/p&gt;
5265
5266 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
5267 welcome, and there is no fee to participate. There is on the other
5268 hand limited space, and only room for 30 people. Please put your name
5269 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
5270 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
5271 </description>
5272 </item>
5273
5274 <item>
5275 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
5276 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
5277 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
5278 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
5279 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
5280 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
5281 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
5282 time to spend on it, and it took a while to find a model I believe
5283 will do the job, but two days ago the replacement finally arrived. I
5284 ended up picking a
5285 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
5286 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5287 a roaming workstation, and it seemed to work flawlessly. But my
5288 second installation with encrypted disk was not as successful. More
5289 on that below.&lt;/p&gt;
5290
5291 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
5292 important requirements (robust and with a good keyboard) are never
5293 listed in the feature list. But I did get good help from the search
5294 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
5295 allowed me to limit the list of interesting laptops based on my other
5296 requirements. A bit surprising that SSD disk are not disks according
5297 to that search interface, so I had to drop specifying the number of
5298 disks from my search parameters. I also asked around among friends to
5299 get their impression on keyboards and robustness.&lt;/p&gt;
5300
5301 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
5302 X41. I am not quite convinced about the keyboard, as it is
5303 significantly wider than my old keyboard, and I have to stretch my
5304 hand a lot more to reach the edges. But the key response is fairly
5305 good and the individual key shape is fairly easy to handle, so I hope
5306 I will get used to it. My old X40 was starting to fail, and I really
5307 needed a new laptop now. :)&lt;/p&gt;
5308
5309 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
5310 visit to the BIOS during boot it disable it.&lt;/p&gt;
5311
5312 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
5313 lock up during load. And this happen when installing Debian Wheezy
5314 with encrypted disk, while the disk is being filled with random data.
5315 I also tested to install Ubuntu Raring, and it happen there too if I
5316 reenable the code to fill the disk with random data (it is disabled by
5317 default in Ubuntu). And the bug with is already known. It was
5318 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
5319 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
5320 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5321 kernel developers as
5322 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
5323 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
5324 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5325 Lenovo forums, both for
5326 &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
5327 2012-11-10&lt;/a&gt; and for
5328 &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
5329 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
5330 reports state that the disk lock up during use if many writes are done
5331 on the disk, so it is much no use to work around the installation
5332 problem and end up with a computer that can lock up at any moment.
5333 There is even a
5334 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
5335 available&lt;/a&gt; that will lock up the hard drive after running a few
5336 minutes by writing to a file.&lt;/p&gt;
5337
5338 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
5339 contacting PCHELP Norway (request 01D1FDP) which handle support
5340 requests for Lenovo, his first suggestion was to upgrade the disk
5341 firmware. Unfortunately there is no newer firmware available from
5342 Lenovo, as my disk already have the most recent one (version LF1i). I
5343 hope to hear more from him today and hope the problem can be
5344 fixed. :)&lt;/p&gt;
5345 </description>
5346 </item>
5347
5348 <item>
5349 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
5350 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
5351 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
5352 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
5353 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
5354 trusty old Thinkpad X41. Unfortunately I did not have much time to
5355 spend on it, but today the replacement finally arrived. I ended up
5356 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
5357 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
5358 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5359 this, it is installing what I hope will be a more final installation,
5360 with a encrypted hard drive to ensure any dope head stealing it end up
5361 with an expencive door stop.&lt;/p&gt;
5362
5363 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
5364 important requirements (robust and with a good keyboard) are never
5365 listed in the feature list. But I did get good help from the search
5366 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
5367 allowed me to limit the list of interesting laptops based on my other
5368 requirements. A bit surprising that SSD disk are not disks, so I had
5369 to drop number of disks from my search parameters.&lt;/p&gt;
5370
5371 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
5372 wider than my old keyboard, and I have to stretch my hand a lot more
5373 to reach the edges. But the key response is fairly good and the
5374 individual key shape is fairly easy to handle, so I hope I will get
5375 used to it. My old X40 was starting to fail, and I really needed a
5376 new laptop now. :)&lt;/p&gt;
5377
5378 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
5379 </description>
5380 </item>
5381
5382 <item>
5383 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
5384 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
5385 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
5386 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
5387 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
5388 perfectly capable of, and I have to do it manually to get things
5389 working. One such task is to find out what firmware packages are
5390 needed to get the hardware on my computer working. Most often this
5391 affect the wifi card, but some times it even affect the RAID
5392 controller or the ethernet card. Today I pushed version 0.4 of the
5393 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
5394 including a new script isenkram-autoinstall-firmware handling the
5395 process of asking all the loaded kernel modules what firmware files
5396 they want, find debian packages providing these files and install the
5397 debian packages. Here is a test run on my laptop:&lt;/p&gt;
5398
5399 &lt;p&gt;&lt;pre&gt;
5400 # isenkram-autoinstall-firmware
5401 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5402 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5403 info: locating packages with the requested firmware files
5404 info: Updating APT sources after adding non-free APT source
5405 info: trying to install firmware-ipw2x00
5406 firmware-ipw2x00
5407 firmware-ipw2x00
5408 Preconfiguring packages ...
5409 Selecting previously deselected package firmware-ipw2x00.
5410 (Reading database ... 259727 files and directories currently installed.)
5411 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5412 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
5413 #
5414 &lt;/pre&gt;&lt;/p&gt;
5415
5416 &lt;p&gt;When all the requested firmware is present, a simple message is
5417 printed instead:&lt;/p&gt;
5418
5419 &lt;p&gt;&lt;pre&gt;
5420 # isenkram-autoinstall-firmware
5421 info: did not find any firmware files requested by loaded kernel modules. exiting
5422 #
5423 &lt;/pre&gt;&lt;/p&gt;
5424
5425 &lt;p&gt;It could use some polish, but it is already working well and saving
5426 me some time when setting up new machines. :)&lt;/p&gt;
5427
5428 &lt;p&gt;So, how does it work? It look at the set of currently loaded
5429 kernel modules, and look up each one of them using modinfo, to find
5430 the firmware files listed in the module meta-information. Next, it
5431 download the Contents file from a nearby APT mirror, and search for
5432 the firmware files in this file to locate the package with the
5433 requested firmware file. If the package is in the non-free section, a
5434 non-free APT source is added and the package is installed using
5435 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
5436 machine.&lt;/p&gt;
5437
5438 &lt;p&gt;I hope someone find time to implement a more polished version of
5439 this script as part of the hw-detect debian-installer module, to
5440 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
5441 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
5442 firmware during a PXE install when the packages already are available
5443 from the nearby Debian mirror.&lt;/p&gt;
5444 </description>
5445 </item>
5446
5447 <item>
5448 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
5449 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
5450 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
5451 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
5452 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5453 the screen just turn black when Linux boot, either during installation
5454 or on first boot from the hard disk. I&#39;ve seen it once in a while the
5455 last few years, but only recently understood the cause. I&#39;ve seen it
5456 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5457 The reason seem to be in the wiring of some laptops. The system to
5458 control the screen background light is inverted, so when Linux try to
5459 turn the brightness fully on, it end up turning it off instead. I do
5460 not know which Linux drivers are affected, but this post is about the
5461 i915 driver used by the
5462 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
5463 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
5464
5465 &lt;p&gt;The problem can be worked around two ways. Either by adding
5466 i915.invert_brightness=1 as a kernel option, or by adding a file in
5467 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
5468 option when it load the i915 kernel module. On Debian and Ubuntu, it
5469 can be done by running these commands as root:&lt;/p&gt;
5470
5471 &lt;pre&gt;
5472 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
5473 update-initramfs -u -k all
5474 &lt;/pre&gt;
5475
5476 &lt;p&gt;Since March 2012 there is
5477 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
5478 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
5479 hardware have this problem, and get the driver to invert the
5480 brightness setting automatically. To use it, one need to add a row in
5481 &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
5482 intel_quirks array&lt;/a&gt; in the driver source
5483 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
5484 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
5485 number (vendor number 8086 is assumed) and subdevice vendor and device
5486 number.&lt;/p&gt;
5487
5488 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
5489 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
5490
5491 &lt;p&gt;&lt;pre&gt;
5492 00:02.0 VGA compatible controller [0300]: Intel Corporation \
5493 3rd Gen Core processor Graphics Controller [8086:0156] \
5494 (rev 09) (prog-if 00 [VGA controller])
5495 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
5496 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5497 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5498 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
5499 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
5500 Latency: 0
5501 Interrupt: pin A routed to IRQ 42
5502 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
5503 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
5504 Region 4: I/O ports at 4000 [size=64]
5505 Expansion ROM at &lt;unassigned&gt; [disabled]
5506 Capabilities: &lt;access denied&gt;
5507 Kernel driver in use: i915
5508 &lt;/pre&gt;&lt;/p&gt;
5509
5510 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
5511
5512 &lt;p&gt;&lt;pre&gt;
5513 struct intel_quirk intel_quirks[] = {
5514 ...
5515 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5516 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
5517 ...
5518 }
5519 &lt;/pre&gt;&lt;/p&gt;
5520
5521 &lt;p&gt;According to the kernel module instructions (as seen using
5522 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
5523 invert_brightness flag should be sent to the
5524 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
5525 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
5526 developers. But my email about the laptop sent 2013-06-03 have not
5527 yet shown up in
5528 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
5529 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
5530 emails from non-subscribers. Because of this, I sent my patch also to
5531 the Debian bug tracking system instead as
5532 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
5533 sure the patch is not lost.&lt;/p&gt;
5534
5535 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
5536 with this problem working properly with Linux. If you use Gnome, your
5537 worries should be over at this point. But if you use KDE, there is
5538 something in KDE ignoring the invert_brightness setting and turning on
5539 the screen during login. I&#39;ve reported it to Debian as
5540 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
5541 have no idea yet how to figure out exactly what subsystem is doing
5542 this. Perhaps you can help? Perhaps you know what the Gnome
5543 developers did to handle this, and this can give a clue to the KDE
5544 developers? Or you know where in KDE the screen brightness is changed
5545 during login? If so, please update the BTS report (or get in touch if
5546 you do not know how to update BTS).&lt;/p&gt;
5547
5548 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
5549 acpi_backlight=vendor, to disable ACPI backlight support completely,
5550 as the ACPI information on the machine is trash and it is better to
5551 leave it to the intel video driver to control the screen
5552 backlight.&lt;/p&gt;
5553 </description>
5554 </item>
5555
5556 <item>
5557 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
5558 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
5559 <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>
5560 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
5561 <description>&lt;p&gt;Two days ago, I asked
5562 &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
5563 I could install Linux on a Packard Bell EasyNote LV computer
5564 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
5565 with the obstacles put in the way of Linux users on a laptop with UEFI
5566 and Windows 8.&lt;/p&gt;
5567
5568 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
5569 secure booting or fast boot. I suspect fast boot was the problem,
5570 causing the firmware to boot directly from HD without considering any
5571 key presses and alternative devices, but do not know UEFI settings
5572 enough to tell.&lt;/p&gt;
5573
5574 &lt;p&gt;There is no way to install Linux on the machine in question without
5575 opening the box and disconnecting the hard drive! This is as far as I
5576 can tell, the only way to get access to the firmware setup menu
5577 without accepting the Windows 8 license agreement. I am told (and
5578 found description on how to) that it is possible to configure the
5579 firmware setup once booted into Windows 8. But as I believe the terms
5580 of that agreement are completely unacceptable, accepting the license
5581 was never an alternative. I do not enter agreements I do not intend
5582 to follow.&lt;/p&gt;
5583
5584 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
5585 waste many hours on this, but luckily there was a way to get it to
5586 work. But I would not recommend it to anyone planning to run Linux on
5587 it, and I have become sceptical to Windows 8 certified laptops. Is
5588 this the way Linux will be forced out of the market place, by making
5589 it close to impossible for &quot;normal&quot; users to install Linux without
5590 accepting the Microsoft Windows license terms? Or at least not
5591 without risking to loose the warranty?&lt;/p&gt;
5592
5593 &lt;p&gt;I&#39;ve updated the
5594 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
5595 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
5596 do not have to struggle as much as I did to get Linux into the
5597 machine.&lt;/p&gt;
5598
5599 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5600 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
5601 </description>
5602 </item>
5603
5604 <item>
5605 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
5606 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
5607 <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>
5608 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
5609 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
5610 new laptops for my parents and a few others. I bought Packard Bell
5611 Easynote LV to run Kubuntu on and use as their home computer. But I
5612 am completely unable to figure out how to install Linux on it. The
5613 computer is preinstalled with Windows 8, and I suspect it uses UEFI
5614 instead of a BIOS to boot.&lt;/p&gt;
5615
5616 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
5617 to get it to boot the Linux installer from my USB stick. I have yet
5618 to try the DVD install, and still hope it will work. when I turn on
5619 the computer, there is no information on what buttons to press to get
5620 the normal boot menu. I expect to get some boot menu to select PXE or
5621 USB stick booting. When booting, it first ask for the language to
5622 use, then for some regional settings, and finally if I will accept the
5623 Windows 8 terms of use. As these terms are completely unacceptable to
5624 me, I have no other choice but to turn off the computer and try again
5625 to get it to boot the Linux installer.&lt;/p&gt;
5626
5627 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
5628 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
5629 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
5630 installed on this machine, please get in touch or update that wiki
5631 page. If I can&#39;t find a way to install Linux, I will have to return
5632 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
5633
5634 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
5635 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
5636 on new Laptops?&lt;/p&gt;
5637 </description>
5638 </item>
5639
5640 <item>
5641 <title>How to transform a Debian based system to a Debian Edu installation</title>
5642 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
5643 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
5644 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
5645 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
5646 an operating system based on Debian intended for use in schools. It
5647 contain a turn-key solution for the computer network provided to
5648 pupils in the primary schools. It provide both the central server,
5649 network boot servers and desktop environments with heaps of
5650 educational software. The project was founded almost 12 years ago,
5651 2001-07-02. If you want to support the project, which is in need for
5652 cash to fund developer gatherings and other project related activity,
5653 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
5654 donate some money&lt;/a&gt;.
5655
5656 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
5657 lists and elsewhere, is the question on how to transform a Debian or
5658 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
5659 hard, and last week I wrote a script to replicate the steps done by
5660 the Debian Edu installer.&lt;/p&gt;
5661
5662 &lt;p&gt;The script,
5663 &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;
5664 in the debian-edu-config package, will go through these six steps and
5665 transform an existing Debian Wheezy or Ubuntu (untested) installation
5666 into a Debian Edu Workstation:&lt;/p&gt;
5667
5668 &lt;ol&gt;
5669
5670 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
5671 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
5672 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
5673 our configuration.&lt;/li&gt;
5674 &lt;li&gt;Preseed debconf database with profile setup in
5675 /etc/debian-edu/config, and run tasksel to install packages
5676 according to the profile specified in the config above,
5677 overriding some of the Debian automation machinery.&lt;/li&gt;
5678 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
5679 that could not be done using preseeding.&lt;/li&gt;
5680 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
5681
5682 &lt;/ol&gt;
5683
5684 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
5685 replicated like this. Disk partitioning and LVM setup, for example.
5686 So this script just assume there is enough disk space to install all
5687 the needed packages.&lt;/p&gt;
5688
5689 &lt;p&gt;The script was created to help a Debian Edu student working on
5690 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
5691 Debian Edu client, and using it he can take the existing
5692 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
5693 transform it into a fully functioning Debian Edu Workstation (or
5694 Roaming Workstation, or whatever :).&lt;/p&gt;
5695
5696 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
5697 If a LXDE based Roaming workstation is wanted instead, modify the
5698 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
5699
5700 &lt;p&gt;&lt;pre&gt;
5701 PROFILE=&quot;Roaming-Workstation&quot;
5702 DESKTOP=&quot;lxde&quot;
5703 &lt;/pre&gt;&lt;/p&gt;
5704
5705 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
5706 the cloud, by starting with a virtual Debian installation at some
5707 virtual hosting service and setting up all the services on first
5708 boot.&lt;/p&gt;
5709 </description>
5710 </item>
5711
5712 <item>
5713 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
5714 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
5715 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
5716 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
5717 <description>&lt;P&gt;In January,
5718 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
5719 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
5720 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
5721 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
5722 marvellous construction system from Denmark. We also created
5723 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
5724 a place to take notes and write down our plans and hopes. And several
5725 people showed up to help. I was very happy to see the effect of my
5726 call. Since the small start, we have a debtags tag
5727 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
5728 tag for LEGO related packages, and now count 10 packages related to
5729 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
5730
5731 &lt;p&gt;&lt;table&gt;
5732 &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;
5733 &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;
5734 &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;
5735 &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;
5736 &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;
5737 &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;
5738 &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;
5739 &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;
5740 &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;
5741 &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;
5742 &lt;/table&gt;&lt;/p&gt;
5743
5744 &lt;p&gt;Some of these are available in Wheezy, and all but one are
5745 currently available in Jessie/testing. leocad is so far only
5746 available in experimental.&lt;/p&gt;
5747
5748 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
5749 adding the rest of the great free software tools available on Linux
5750 for LEGO designers.&lt;/p&gt;
5751 </description>
5752 </item>
5753
5754 <item>
5755 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
5756 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
5757 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
5758 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
5759 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
5760 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
5761 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
5762 Debian release, and I expect to move my machines at home over to it fairly
5763 soon.&lt;/p&gt;
5764
5765 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
5766 in particular make me very happy to see included. The
5767 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
5768 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
5769 included for the first time. Alongside similar programs like
5770 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
5771 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
5772 it allow for visual programming where syntax errors can not happen,
5773 and a friendly programming environment for learning to control the
5774 computer. Scratch will also be included in the next release of Debian
5775 Edu.&lt;/a&gt;
5776
5777 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
5778 Edu/Skolelinux release too. The
5779 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
5780 alpha release&lt;/a&gt; went out last week, and the next should soon
5781 follow.&lt;p&gt;
5782 </description>
5783 </item>
5784
5785 <item>
5786 <title>Isenkram 0.2 finally in the Debian archive</title>
5787 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
5788 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
5789 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
5790 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
5791 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
5792 for many months. I uploaded it to the Debian experimental suite
5793 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
5794
5795 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
5796 install to work with a pluggable hardware device. The suggestion pop
5797 up when the device is plugged in. For example if a Lego Mindstorm NXT
5798 is inserted, it will suggest to install the program needed to program
5799 the NXT controller. Give it a go, and report bugs and suggestions to
5800 BTS. :)&lt;/p&gt;
5801 </description>
5802 </item>
5803
5804 <item>
5805 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
5806 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
5807 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
5808 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
5809 <description>&lt;p&gt;My
5810 &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
5811 bitcoin related blog post&lt;/a&gt; mentioned that the new
5812 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
5813 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5814 2013-01-19, and have been available in unstable since then. It was
5815 automatically copied to Ubuntu, and is available in their Raring
5816 version too.&lt;/p&gt;
5817
5818 &lt;p&gt;But there is a strange problem with the build that block this new
5819 version from being available on the i386 and kfreebsd-i386
5820 architectures. For some strange reason, the autobuilders in Debian
5821 for these architectures fail to run the test suite on these
5822 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
5823 We are so far unable to reproduce it when building it manually, and
5824 no-one have been able to propose a fix. If you got an idea what is
5825 failing, please let us know via the BTS.&lt;/p&gt;
5826
5827 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
5828 I often run low on disk space, is the fact that the client will exit
5829 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
5830 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
5831 it. :)&lt;/p&gt;
5832
5833 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
5834 activities, please send Bitcoin donations to my address
5835 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5836 </description>
5837 </item>
5838
5839 <item>
5840 <title>Welcome to the world, Isenkram!</title>
5841 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
5842 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
5843 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
5844 <description>&lt;p&gt;Yesterday, I
5845 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
5846 for testers&lt;/a&gt; for my prototype for making Debian better at handling
5847 pluggable hardware devices, which I
5848 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
5849 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
5850 up, and caused me to really want to to open up the development to more
5851 people. But before I did this, I want to come up with a sensible name
5852 for this project. Today I finally decided on a new name, and I have
5853 renamed the project from hw-support-handler to this new name. In the
5854 process, I moved the source to git and made it available as a
5855 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
5856 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
5857 To fetch and build the latest version of the source, use&lt;/p&gt;
5858
5859 &lt;pre&gt;
5860 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5861 cd isenkram &amp;&amp; git-buildpackage -us -uc
5862 &lt;/pre&gt;
5863
5864 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
5865 want to hack on the source or improve the package, please go ahead.
5866 But please talk to me first on IRC or via email before you do major
5867 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
5868
5869 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
5870 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5871 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
5872 the German word eisenkram, for those that are familiar with that
5873 word.&lt;/p&gt;
5874
5875 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
5876 instructions, to avoid confusing people with an error from the signing
5877 process.&lt;/p&gt;
5878
5879 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
5880 clone argument to avoid the need for authentication.&lt;/p&gt;
5881 </description>
5882 </item>
5883
5884 <item>
5885 <title>First prototype ready making hardware easier to use in Debian</title>
5886 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
5887 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
5888 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
5889 <description>&lt;p&gt;Early this month I set out to try to
5890 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
5891 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
5892 prototype is working, and it is ready for a larger audience. To test
5893 it, fetch the
5894 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
5895 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
5896 package. You might have to log out and in again activate the
5897 autostart script.&lt;/p&gt;
5898
5899 &lt;p&gt;The design is simple:&lt;/p&gt;
5900
5901 &lt;ul&gt;
5902
5903 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
5904 hw-support-handlerd to start when the user log in.&lt;/li&gt;
5905
5906 &lt;li&gt;This program listen for kernel events about new hardware (directly
5907 from the kernel like udev does), not using HAL dbus events as I
5908 initially did.&lt;/li&gt;
5909
5910 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
5911 the APT database, a database
5912 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
5913 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
5914
5915 &lt;li&gt;If a package is mapped to the hardware in question, the package
5916 isn&#39;t installed yet and this is the first time the hardware was
5917 plugged in, show a desktop notification suggesting to install the
5918 package or packages.&lt;/li&gt;
5919
5920 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
5921 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
5922
5923 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
5924 package while showing progress information in a window.&lt;/li&gt;
5925
5926 &lt;/ul&gt;
5927
5928 &lt;p&gt;I still need to come up with a better name for the system. Here
5929 are some screen shots showing the prototype in action. First the
5930 notification, then the password request, and finally the request to
5931 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
5932
5933 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
5934 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
5935 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
5936 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
5937 &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;
5938
5939 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
5940 is already useful. The database of hardware to package mappings also
5941 need more work. It is currently compatible with the Ubuntu way of
5942 storing such information in the package control file, but could be
5943 changed to use other formats instead or in addition to the current
5944 method. I&#39;ve dropped the use of discover for this mapping, as the
5945 modalias approach is more flexible and easier to use on Linux as long
5946 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
5947
5948 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
5949 here is the command required to check out and build the source: Use
5950 &#39;&lt;tt&gt;svn checkout
5951 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5952 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
5953 devscripts package.&lt;/p&gt;
5954
5955 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
5956 renamed to Isenkram and the source moved from the Debian Edu
5957 subversion repository to a Debian collab-maint git repository. See
5958 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
5959 instructions&lt;/a&gt; for details.&lt;/p&gt;
5960 </description>
5961 </item>
5962
5963 <item>
5964 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
5965 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
5966 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
5967 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
5968 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
5969 suddenly in bed. With a quiet whimper, it went completely quiet and
5970 black. The power button was no longer able to turn it on. It was a
5971 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5972 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5973 Compaq I had before that. Now I need to find a replacement. To keep
5974 going during Christmas, I moved the one year old SSD disk to my old
5975 X40 where it fitted (only one I had left that could use it), but it is
5976 not a durable solution.
5977
5978 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
5979 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
5980
5981 &lt;ul&gt;
5982
5983 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
5984 than A4).&lt;/li&gt;
5985 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
5986 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
5987 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
5988 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
5989 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
5990 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
5991 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
5992 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
5993 size).&lt;/li&gt;
5994 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
5995 X.org packages.&lt;/li&gt;
5996 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
5997 the time).
5998
5999 &lt;/ul&gt;
6000
6001 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
6002 list. The reason is simply that the specifications on laptops the
6003 last 10-15 years have been sufficient for my needs, and I have to look
6004 at other features to choose my laptop. But are there still made as
6005 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6006 robust, and Thinkpads seem to be heading in the wrong direction since
6007 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
6008 still be useful.&lt;/p&gt;
6009
6010 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
6011 external keyboard? I&#39;ll have to check the
6012 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
6013 well-supported laptops, or perhaps just buy one preinstalled from one
6014 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
6015 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
6016 </description>
6017 </item>
6018
6019 <item>
6020 <title>How to find a browser plugin supporting a given MIME type</title>
6021 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
6022 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
6023 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
6024 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
6025 install to get support for a given MIME type. Thanks to
6026 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
6027 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
6028 Unfortunately, not very many packages provide the needed meta
6029 information, Anyway, here is a small script to look up all browser
6030 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
6031
6032 &lt;pre&gt;
6033 #!/usr/bin/python
6034 import sys
6035 import apt
6036 def pkgs_handling_mimetype(mimetype):
6037 cache = apt.Cache()
6038 cache.open(None)
6039 thepkgs = []
6040 for pkg in cache:
6041 version = pkg.candidate
6042 if version is None:
6043 version = pkg.installed
6044 if version is None:
6045 continue
6046 record = version.record
6047 if not record.has_key(&#39;Npp-MimeType&#39;):
6048 continue
6049 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
6050 for t in mime_types:
6051 t = t.rstrip().strip()
6052 if t == mimetype:
6053 thepkgs.append(pkg.name)
6054 return thepkgs
6055 mimetype = &quot;audio/ogg&quot;
6056 if 1 &lt; len(sys.argv):
6057 mimetype = sys.argv[1]
6058 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
6059 for pkg in pkgs_handling_mimetype(mimetype):
6060 print &quot; %s&quot; %pkg
6061 &lt;/pre&gt;
6062
6063 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
6064
6065 &lt;pre&gt;
6066 % ./apt-find-browserplug-for-mimetype
6067 Browser plugin packages supporting audio/ogg:
6068 gecko-mediaplayer
6069 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6070 Browser plugin packages supporting application/x-shockwave-flash:
6071 browser-plugin-gnash
6072 %
6073 &lt;/pre&gt;
6074
6075 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
6076 itself to query for plugins and propose to install the needed
6077 packages. It would be great if Debian supported such feature too. Is
6078 anyone working on adding it?&lt;/p&gt;
6079
6080 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
6081 request for icweasel support for this feature is
6082 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
6083 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
6084 of manpower and wish for a different design is the reason thus feature
6085 is not yet in iceweasel from Debian.&lt;/p&gt;
6086 </description>
6087 </item>
6088
6089 <item>
6090 <title>What is the most supported MIME type in Debian?</title>
6091 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
6092 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
6093 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
6094 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
6095 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
6096 proposal to make it possible for a Desktop application to propose to
6097 the user some package to install to gain support for a given MIME
6098 type, font, library etc. that is currently missing. With such
6099 mechanism in place, it would be possible for the desktop to
6100 automatically propose and install leocad if some LDraw file is
6101 downloaded by the browser.&lt;/p&gt;
6102
6103 &lt;p&gt;To get some idea about the current content of the archive, I decided
6104 to write a simple program to extract all .desktop files from the
6105 Debian archive and look up the claimed MIME support there. The result
6106 can be found on the
6107 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
6108 site&lt;/a&gt;. Using the collected information, it become possible to
6109 answer the question in the title. Here are the 20 most supported MIME
6110 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6111 The complete list is available from the link above.&lt;/p&gt;
6112
6113 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
6114
6115 &lt;pre&gt;
6116 count MIME type
6117 ----- -----------------------
6118 32 text/plain
6119 30 audio/mpeg
6120 29 image/png
6121 28 image/jpeg
6122 27 application/ogg
6123 26 audio/x-mp3
6124 25 image/tiff
6125 25 image/gif
6126 22 image/bmp
6127 22 audio/x-wav
6128 20 audio/x-flac
6129 19 audio/x-mpegurl
6130 18 video/x-ms-asf
6131 18 audio/x-musepack
6132 18 audio/x-mpeg
6133 18 application/x-ogg
6134 17 video/mpeg
6135 17 audio/x-scpls
6136 17 audio/ogg
6137 16 video/x-ms-wmv
6138 &lt;/pre&gt;
6139
6140 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
6141
6142 &lt;pre&gt;
6143 count MIME type
6144 ----- -----------------------
6145 33 text/plain
6146 32 image/png
6147 32 image/jpeg
6148 29 audio/mpeg
6149 27 image/gif
6150 26 image/tiff
6151 26 application/ogg
6152 25 audio/x-mp3
6153 22 image/bmp
6154 21 audio/x-wav
6155 19 audio/x-mpegurl
6156 19 audio/x-mpeg
6157 18 video/mpeg
6158 18 audio/x-scpls
6159 18 audio/x-flac
6160 18 application/x-ogg
6161 17 video/x-ms-asf
6162 17 text/html
6163 17 audio/x-musepack
6164 16 image/x-xbitmap
6165 &lt;/pre&gt;
6166
6167 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
6168
6169 &lt;pre&gt;
6170 count MIME type
6171 ----- -----------------------
6172 31 text/plain
6173 31 image/png
6174 31 image/jpeg
6175 29 audio/mpeg
6176 28 application/ogg
6177 27 image/gif
6178 26 image/tiff
6179 26 audio/x-mp3
6180 23 audio/x-wav
6181 22 image/bmp
6182 21 audio/x-flac
6183 20 audio/x-mpegurl
6184 19 audio/x-mpeg
6185 18 video/x-ms-asf
6186 18 video/mpeg
6187 18 audio/x-scpls
6188 18 application/x-ogg
6189 17 audio/x-musepack
6190 16 video/x-ms-wmv
6191 16 video/x-msvideo
6192 &lt;/pre&gt;
6193
6194 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
6195 information mentioned in DEP-11. I have not yet had time to look at
6196 it, but hope the PackageKit people in Debian are on top of these
6197 issues.&lt;/p&gt;
6198
6199 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
6200 discovering a typo in my script.&lt;/p&gt;
6201 </description>
6202 </item>
6203
6204 <item>
6205 <title>Using modalias info to find packages handling my hardware</title>
6206 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
6207 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
6208 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
6209 <description>&lt;p&gt;Yesterday, I wrote about the
6210 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
6211 values provided by the Linux kernel&lt;/a&gt; following my hope for
6212 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
6213 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
6214 modalias values attached to package names can be used to map packages
6215 to hardware. This allow the system to look up and suggest relevant
6216 packages when I plug in some new hardware into my machine, and replace
6217 discover and discover-data as the database used to map hardware to
6218 packages.&lt;/p&gt;
6219
6220 &lt;p&gt;I create a modaliases file with entries like the following,
6221 containing package name, kernel module name (if relevant, otherwise
6222 the package name) and globs matching the relevant hardware
6223 modalias.&lt;/p&gt;
6224
6225 &lt;p&gt;&lt;blockquote&gt;
6226 Package: package-name
6227 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
6228 &lt;/blockquote&gt;&lt;/p&gt;
6229
6230 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
6231 for a given modalias value using this file.&lt;/p&gt;
6232
6233 &lt;p&gt;An entry like this would suggest the video and picture application
6234 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
6235
6236 &lt;p&gt;&lt;blockquote&gt;
6237 Package: cheese
6238 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
6239 &lt;/blockquote&gt;&lt;/p&gt;
6240
6241 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
6242 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
6243
6244 &lt;p&gt;&lt;blockquote&gt;
6245 Package: pcmciautils
6246 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6247 &lt;/blockquote&gt;&lt;/p&gt;
6248
6249 &lt;p&gt;An entry like this would suggest the package colorhug-client when
6250 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
6251
6252 &lt;p&gt;&lt;blockquote&gt;
6253 Package: colorhug-client
6254 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
6255 &lt;/blockquote&gt;&lt;/p&gt;
6256
6257 &lt;p&gt;I believe the format is compatible with the format of the Packages
6258 file in the Debian archive. Ubuntu already uses their Packages file
6259 to store their mappings from packages to hardware.&lt;/p&gt;
6260
6261 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
6262 announce the hardware it support in a way my prototype understand.
6263 This allow those publishing packages in an APT source outside the
6264 Debian archive as well as those backporting packages to make sure the
6265 hardware mapping are included in the package meta information. I&#39;ve
6266 tested such header in the pymissile package, and its modalias mapping
6267 is working as it should with my prototype. It even made it to Ubuntu
6268 Raring.&lt;/p&gt;
6269
6270 &lt;p&gt;To test if it was possible to look up supported hardware using only
6271 the shell tools available in the Debian installer, I wrote a shell
6272 implementation of the lookup code. The idea is to create files for
6273 each modalias and let the shell do the matching. Please check out and
6274 try the
6275 &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;
6276 shell script. It run without any extra dependencies and fetch the
6277 hardware mappings from the Debian archive and the subversion
6278 repository where I currently work on my prototype.&lt;/p&gt;
6279
6280 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
6281 install yubikey-personalization:&lt;/p&gt;
6282
6283 &lt;p&gt;&lt;blockquote&gt;
6284 % ./hw-support-lookup
6285 &lt;br&gt;yubikey-personalization
6286 &lt;br&gt;%
6287 &lt;/blockquote&gt;&lt;/p&gt;
6288
6289 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6290 propose to install the pcmciautils package:&lt;/p&gt;
6291
6292 &lt;p&gt;&lt;blockquote&gt;
6293 % ./hw-support-lookup
6294 &lt;br&gt;pcmciautils
6295 &lt;br&gt;%
6296 &lt;/blockquote&gt;&lt;/p&gt;
6297
6298 &lt;p&gt;If you know of any hardware-package mapping that should be added to
6299 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
6300 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
6301
6302 &lt;p&gt;It could be possible to generate several of the mappings between
6303 packages and hardware. One source would be to look at packages with
6304 kernel modules, ie packages with *.ko files in /lib/modules/, and
6305 extract their modalias information. Another would be to look at
6306 packages with udev rules, ie packages with files in
6307 /lib/udev/rules.d/, and extract their vendor/model information to
6308 generate a modalias matching rule. I have not tested any of these to
6309 see if it work.&lt;/p&gt;
6310
6311 &lt;p&gt;If you want to help implementing a system to let us propose what
6312 packages to install when new hardware is plugged into a Debian
6313 machine, please send me an email or talk to me on
6314 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
6315 </description>
6316 </item>
6317
6318 <item>
6319 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
6320 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
6321 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
6322 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
6323 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
6324 information, to find the packages that support a given piece of
6325 hardware, I refreshed my memory regarding modalias values, and decided
6326 to document the details. Here are my findings so far, also available
6327 in
6328 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
6329 Debian Edu subversion repository&lt;/a&gt;:
6330
6331 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
6332
6333 &lt;p&gt;This document try to explain what the different types of modalias
6334 values stands for. It is in part based on information from
6335 &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;,
6336 &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;,
6337 &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
6338 &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;.
6339
6340 &lt;p&gt;The modalias entries for a given Linux machine can be found using
6341 this shell script:&lt;/p&gt;
6342
6343 &lt;pre&gt;
6344 find /sys -name modalias -print0 | xargs -0 cat | sort -u
6345 &lt;/pre&gt;
6346
6347 &lt;p&gt;The supported modalias globs for a given kernel module can be found
6348 using modinfo:&lt;/p&gt;
6349
6350 &lt;pre&gt;
6351 % /sbin/modinfo psmouse | grep alias:
6352 alias: serio:ty05pr*id*ex*
6353 alias: serio:ty01pr*id*ex*
6354 %
6355 &lt;/pre&gt;
6356
6357 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
6358
6359 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
6360 Bridge memory controller:&lt;/p&gt;
6361
6362 &lt;p&gt;&lt;blockquote&gt;
6363 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6364 &lt;/blockquote&gt;&lt;/p&gt;
6365
6366 &lt;p&gt;This represent these values:&lt;/p&gt;
6367
6368 &lt;pre&gt;
6369 v 00008086 (vendor)
6370 d 00002770 (device)
6371 sv 00001028 (subvendor)
6372 sd 000001AD (subdevice)
6373 bc 06 (bus class)
6374 sc 00 (bus subclass)
6375 i 00 (interface)
6376 &lt;/pre&gt;
6377
6378 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
6379 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
6380 0600. The 0600 class is a host bridge. Other useful bus values are
6381 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
6382
6383 &lt;p&gt;Not sure how to figure out the interface value, nor what it
6384 means.&lt;/p&gt;
6385
6386 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
6387
6388 &lt;p&gt;Some typical USB entries can look like this. This is an internal
6389 USB hub in a laptop:&lt;/p&gt;
6390
6391 &lt;p&gt;&lt;blockquote&gt;
6392 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6393 &lt;/blockquote&gt;&lt;/p&gt;
6394
6395 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
6396
6397 &lt;pre&gt;
6398 v 1D6B (device vendor)
6399 p 0001 (device product)
6400 d 0206 (bcddevice)
6401 dc 09 (device class)
6402 dsc 00 (device subclass)
6403 dp 00 (device protocol)
6404 ic 09 (interface class)
6405 isc 00 (interface subclass)
6406 ip 00 (interface protocol)
6407 &lt;/pre&gt;
6408
6409 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
6410 class is in the interface class section. For a simple USB web camera,
6411 these alias entries show up:&lt;/p&gt;
6412
6413 &lt;p&gt;&lt;blockquote&gt;
6414 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6415 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6416 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6417 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6418 &lt;/blockquote&gt;&lt;/p&gt;
6419
6420 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
6421 camera), 0101 is audio control device and 0102 is audio streaming (aka
6422 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
6423
6424 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
6425
6426 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
6427 receiver in a Thinkpad X40:&lt;/p&gt;
6428
6429 &lt;p&gt;&lt;blockquote&gt;
6430 acpi:IBM0071:PNP0511:
6431 &lt;/blockquote&gt;&lt;/p&gt;
6432
6433 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
6434
6435 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
6436
6437 &lt;p&gt;The DMI table contain lots of information about the computer case
6438 and model. This is an entry for a IBM Thinkpad X40, fetched from
6439 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
6440
6441 &lt;p&gt;&lt;blockquote&gt;
6442 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6443 &lt;/blockquote&gt;&lt;/p&gt;
6444
6445 &lt;p&gt;The values present are&lt;/p&gt;
6446
6447 &lt;pre&gt;
6448 bvn IBM (BIOS vendor)
6449 bvr 1UETB6WW(1.66) (BIOS version)
6450 bd 06/15/2005 (BIOS date)
6451 svn IBM (system vendor)
6452 pn 2371H4G (product name)
6453 pvr ThinkPadX40 (product version)
6454 rvn IBM (board vendor)
6455 rn 2371H4G (board name)
6456 rvr NotAvailable (board version)
6457 cvn IBM (chassis vendor)
6458 ct 10 (chassis type)
6459 cvr NotAvailable (chassis version)
6460 &lt;/pre&gt;
6461
6462 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
6463 found in the dmidecode source:&lt;/p&gt;
6464
6465 &lt;pre&gt;
6466 3 Desktop
6467 4 Low Profile Desktop
6468 5 Pizza Box
6469 6 Mini Tower
6470 7 Tower
6471 8 Portable
6472 9 Laptop
6473 10 Notebook
6474 11 Hand Held
6475 12 Docking Station
6476 13 All In One
6477 14 Sub Notebook
6478 15 Space-saving
6479 16 Lunch Box
6480 17 Main Server Chassis
6481 18 Expansion Chassis
6482 19 Sub Chassis
6483 20 Bus Expansion Chassis
6484 21 Peripheral Chassis
6485 22 RAID Chassis
6486 23 Rack Mount Chassis
6487 24 Sealed-case PC
6488 25 Multi-system
6489 26 CompactPCI
6490 27 AdvancedTCA
6491 28 Blade
6492 29 Blade Enclosing
6493 &lt;/pre&gt;
6494
6495 &lt;p&gt;The chassis type values are not always accurately set in the DMI
6496 table. For example my home server is a tower, but the DMI modalias
6497 claim it is a desktop.&lt;/p&gt;
6498
6499 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
6500
6501 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
6502 test machine:&lt;/p&gt;
6503
6504 &lt;p&gt;&lt;blockquote&gt;
6505 serio:ty01pr00id00ex00
6506 &lt;/blockquote&gt;&lt;/p&gt;
6507
6508 &lt;p&gt;The values present are&lt;/p&gt;
6509
6510 &lt;pre&gt;
6511 ty 01 (type)
6512 pr 00 (prototype)
6513 id 00 (id)
6514 ex 00 (extra)
6515 &lt;/pre&gt;
6516
6517 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
6518 the valid values are.&lt;/p&gt;
6519
6520 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
6521
6522 &lt;p&gt;There are heaps of other modalias subtypes according to
6523 file2alias.c. There is the rest of the list from that source: amba,
6524 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6525 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6526 vmbus, x86cpu and zorro. I did not spend time documenting all of
6527 these, as they do not seem relevant for my intended use with mapping
6528 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
6529
6530 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
6531
6532 &lt;p&gt;To check which kernel modules provide support for a given modalias,
6533 one can use the following shell script:&lt;/p&gt;
6534
6535 &lt;pre&gt;
6536 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
6537 echo &quot;$id&quot; ; \
6538 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
6539 done
6540 &lt;/pre&gt;
6541
6542 &lt;p&gt;The output can look like this (only the first few entries as the
6543 list is very long on my test machine):&lt;/p&gt;
6544
6545 &lt;pre&gt;
6546 acpi:ACPI0003:
6547 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
6548 acpi:device:
6549 FATAL: Module acpi:device: not found.
6550 acpi:IBM0068:
6551 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
6552 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
6553 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
6554 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6555 acpi:IBM0071:PNP0511:
6556 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
6557 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
6558 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
6559 [...]
6560 &lt;/pre&gt;
6561
6562 &lt;p&gt;If you want to help implementing a system to let us propose what
6563 packages to install when new hardware is plugged into a Debian
6564 machine, please send me an email or talk to me on
6565 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
6566
6567 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
6568 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
6569 in /sys/ with space in them.&lt;/p&gt;
6570 </description>
6571 </item>
6572
6573 <item>
6574 <title>Moved the pymissile Debian packaging to collab-maint</title>
6575 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
6576 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
6577 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
6578 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
6579 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6580 Launcher and updated the Debian package
6581 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
6582 sure udev will fix the device permissions when it is plugged in. I
6583 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
6584 hopefully make the package be proposed by jockey in Ubuntu when a user
6585 plug in his rocket launcher. In the process I moved the source to a
6586 git repository under collab-maint, to make it easier for any DD to
6587 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
6588 is not very active, but the software still work for me even after five
6589 years of relative silence. The new git repository is not listed in
6590 the uploaded package yet, because I want to test the other changes a
6591 bit more before I upload the new version. If you want to check out
6592 the new version with a .desktop file included, visit the
6593 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
6594 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
6595 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
6596 </description>
6597 </item>
6598
6599 <item>
6600 <title>Lets make hardware dongles easier to use in Debian</title>
6601 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
6602 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
6603 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
6604 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
6605 general, is that there is a great package management system with the
6606 ability to automatically install software packages by downloading them
6607 from the distribution mirrors, but no way to get it to automatically
6608 install the packages I need to use the hardware I plug into my
6609 machine. Even if the package to use it is easily available from the
6610 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6611 suggest to automatically install the python-nxt, nbc and t2n packages
6612 I need to talk to it. When I plug in a Yubikey, it could propose the
6613 yubikey-personalization package. The information required to do this
6614 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
6615
6616 &lt;p&gt;Some years ago, I proposed to
6617 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
6618 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
6619 simple:
6620
6621 &lt;ul&gt;
6622
6623 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
6624 starting when a user log in.&lt;/li&gt;
6625
6626 &lt;li&gt;Set this program up to listen for kernel events emitted when new
6627 hardware is inserted into the computer.&lt;/li&gt;
6628
6629 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
6630 database mapping to packages, and take note of any non-installed
6631 packages.&lt;/li&gt;
6632
6633 &lt;li&gt;Show a message to the user proposing to install the discovered
6634 package, and make it easy to install it.&lt;/li&gt;
6635
6636 &lt;/ul&gt;
6637
6638 &lt;p&gt;I am not sure what the best way to implement this is, but my
6639 initial idea was to use dbus events to discover new hardware, the
6640 discover database to find packages and
6641 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
6642 packages.&lt;/p&gt;
6643
6644 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
6645 draft package is now checked into
6646 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
6647 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
6648 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
6649 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6650 the relevant packages in Debian, and uploaded a new version
6651 2.2013.01.09 to unstable. I also discovered that the current
6652 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
6653 package in Debian no longer discovered any USB devices, because
6654 /proc/bus/usb/devices is no longer present. I ported it to use
6655 libusb as a fall back option to get it working. The fixed package
6656 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
6657 because of the freeze).&lt;/p&gt;
6658
6659 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
6660 desktop notification to show up (only once, the first time it is
6661 inserted):&lt;/p&gt;
6662
6663 &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;
6664
6665 &lt;p&gt;For this prototype to be really useful, some way to automatically
6666 install the proposed packages by pressing the &quot;Please install
6667 program(s)&quot; button should to be implemented.&lt;/p&gt;
6668
6669 &lt;p&gt;If this idea seem useful to you, and you want to help make it
6670 happen, please help me update the discover-data database with mappings
6671 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
6672 list the package you would like to have installed when a given
6673 hardware device is inserted into your computer, and report bugs using
6674 reportbug if it isn&#39;t. Or, if you know of a better way to provide
6675 such mapping, please let me know.&lt;/p&gt;
6676
6677 &lt;p&gt;This prototype need more work, and there are several questions that
6678 should be considered before it is ready for production use. Is dbus
6679 the correct way to detect new hardware? At the moment I look for HAL
6680 dbus events on the system bus, because that is the events I could see
6681 on my Debian Squeeze KDE desktop. Are there better events to use?
6682 How should the user be notified? Is the desktop notification
6683 mechanism the best option, or should the background daemon raise a
6684 popup instead? How should packages be installed? When should they
6685 not be installed?&lt;/p&gt;
6686
6687 &lt;p&gt;If you want to help getting such feature implemented in Debian,
6688 please send me an email. :)&lt;/p&gt;
6689 </description>
6690 </item>
6691
6692 <item>
6693 <title>New IRC channel for LEGO designers using Debian</title>
6694 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
6695 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
6696 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
6697 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
6698 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
6699 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
6700 discovered I had to build all the tools myself because none were
6701 already in Debian Squeeze. If Debian support for LEGO is something
6702 you care about, please join me on the IRC channel
6703 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
6704 irc.debian.org). There is a lot that could be done to improve the
6705 Debian support for LEGO designers. For example both CAD software
6706 and Mindstorm compilers are missing. :)&lt;/p&gt;
6707
6708 &lt;p&gt;Update 2012-01-03: A
6709 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
6710 including links to Lego related packages is now available.&lt;/p&gt;
6711 </description>
6712 </item>
6713
6714 <item>
6715 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
6716 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
6717 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
6718 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
6719 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
6720 year! I hope next year will prove to be a good year.&lt;/p&gt;
6721
6722 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
6723 decentralised &quot;currency&quot; that allow people to transfer bitcoins
6724 between each other with minimal overhead, is a very interesting
6725 experiment. And as I wrote a few days ago, the bitcoin situation in
6726 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
6727 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
6728 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
6729 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
6730 for one of the ftpmasters to approve the new bitcoin-qt package
6731 name.&lt;/p&gt;
6732
6733 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
6734 team in Debian, you can easily test the package in Debian Squeeze
6735 using the following steps to get a set of working packages:&lt;/p&gt;
6736
6737 &lt;blockquote&gt;&lt;pre&gt;
6738 git clone git://git.debian.org/git/collab-maint/bitcoin
6739 cd bitcoin
6740 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6741 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6742 &lt;/pre&gt;&lt;/blockquote&gt;
6743
6744 &lt;p&gt;You might have to install some build dependencies as well. The
6745 list of commands should give you two packages, bitcoind and
6746 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6747 client will download the complete set of bitcoin &quot;blocks&quot;, which need
6748 around 5.6 GiB of data on my machine at the moment. Make sure your
6749 ~/.bitcoin/ directory have lots of spare room if you want to download
6750 all the blocks. The client will warn if the disk is getting full, so
6751 there is not really a problem if you got too little room, but you will
6752 not be able to get all the features out of the client.&lt;/p&gt;
6753
6754 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
6755 activities, please send Bitcoin donations to my address
6756 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6757 </description>
6758 </item>
6759
6760 <item>
6761 <title>A word on bitcoin support in Debian</title>
6762 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
6763 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
6764 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
6765 <description>&lt;p&gt;It has been a while since I wrote about
6766 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
6767 peer-to-peer based crypto-currency, and the reason is simply that I
6768 have been busy elsewhere. But two days ago, I started looking at the
6769 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
6770 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
6771 is now maintained by a
6772 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
6773 people&lt;/a&gt;, and the grunt work had already been done by this team. We
6774 owe a huge thank you to all these team members. :)
6775 But I was sad to discover that the bitcoin client is missing in
6776 Wheezy. It is only available in Sid (and an outdated client from
6777 backports). The client had several RC bugs registered in BTS blocking
6778 it from entering testing. To try to help the team and improve the
6779 situation, I spent some time providing patches and triaging the bug
6780 reports. I also had a look at the bitcoin package available from Matt
6781 Corallo in a
6782 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
6783 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
6784 Debian package.&lt;/p&gt;
6785
6786 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
6787 IRC, I pushed several patches into the collab-maint git repository to
6788 improve the package. It now contains fixes for the RC issues (not from
6789 me, but fixed by Scott Howard), build rules for a Qt GUI client
6790 package, konqueror support for the bitcoin: URI and bash completion
6791 setup. As I work on Debian Squeeze, I also created
6792 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
6793 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
6794 it and try to integrate it into the git repository before uploading a
6795 new version to unstable.
6796
6797 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
6798 centralized control currently exercised in the monetary system. I
6799 find it completely unacceptable that the USA government is collecting
6800 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6801 that the major credit card companies can block legal money
6802 transactions to Wikileaks. But for bitcoin to succeed, more people
6803 need to use bitcoins, and more people need to accept bitcoins when
6804 they sell products and services. Improving the bitcoin support in
6805 Debian is a small step in the right direction, but not enough.
6806 Unfortunately the user experience when browsing the web and wanting to
6807 pay with bitcoin is still not very good. The bitcoin: URI is a step
6808 in the right direction, but need to work in most or every browser in
6809 use. Also the bitcoin-qt client is too heavy to fire up to do a
6810 quick transaction. I believe there are other clients available, but
6811 have not tested them.&lt;/p&gt;
6812
6813 &lt;p&gt;My
6814 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
6815 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
6816 I received 20.15 BTC so far on the address I provided in my blog two
6817 years ago, as can be
6818 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
6819 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
6820 donation. The blockexplorer service demonstrates quite well that
6821 bitcoin is not quite anonymous and untracked. :) I wonder if the
6822 number of users have gone up since then. If you use bitcoin and want
6823 to show your support of my activity, please send Bitcoin donations to
6824 the same address as last time,
6825 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6826 </description>
6827 </item>
6828
6829 <item>
6830 <title>Git repository for song book for Computer Scientists</title>
6831 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
6832 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
6833 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
6834 <description>&lt;p&gt;As I
6835 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
6836 this summer&lt;/a&gt;, I have created a Computer Science song book a few
6837 years ago, and today I finally found time to create a public
6838 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
6839 repository for the project&lt;/a&gt;.&lt;/p&gt;
6840
6841 &lt;p&gt;If you want to help out, please clone the source and submit patches
6842 to the HTML version. To generate the PDF and PostScript version,
6843 please use prince XML, or let me know about a useful free software
6844 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
6845
6846 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
6847 PostScript formats at
6848 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
6849 Science Songbook&lt;/a&gt;.&lt;/p&gt;
6850 </description>
6851 </item>
6852
6853 <item>
6854 <title>Gratulerer med 19-årsdagen, Debian!</title>
6855 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
6856 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
6857 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
6858 <description>&lt;p&gt;I dag fyller
6859 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
6860 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
6861 si gratulerer med dagen, Debian!&lt;/p&gt;
6862 </description>
6863 </item>
6864
6865 <item>
6866 <title>Song book for Computer Scientists</title>
6867 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
6868 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
6869 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
6870 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
6871 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
6872 collecting computer related songs for use at parties. The original
6873 version was written in LaTeX, but a few years ago I got help from
6874 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6875 while keeping the ability to create a nice book in PDF format. I have
6876 not had time to maintain the book for a while now, and guess I should
6877 put it up on some public version control repository where others can
6878 help me extend and update the book. If anyone is volunteering to help
6879 me with this, send me an email. Also let me know if there are songs
6880 missing in my book.&lt;/p&gt;
6881
6882 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
6883 me today that I really should let all my readers share the joys of
6884 singing out load about programming, computers and computer networks.
6885 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
6886 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
6887 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
6888 Computer Science Songbook&lt;/a&gt;.
6889 </description>
6890 </item>
6891
6892 <item>
6893 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
6894 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
6895 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
6896 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
6897 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
6898 around 1000 at the moment. To be able to get help from the vendors
6899 when something go wrong, we want to keep the firmware on the servers
6900 up to date. If the firmware isn&#39;t the latest and greatest, the
6901 vendors typically refuse to start debugging any problems until the
6902 firmware is upgraded. So before every reboot, we want to upgrade the
6903 firmware, and we would really like everyone handling servers at the
6904 university to do this themselves when they plan to reboot a machine.
6905 For that to happen we at the unix server admin group need to provide
6906 the tools to do so.&lt;/p&gt;
6907
6908 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
6909 fetch and install the latest firmware for the servers we got. Most of
6910 our hardware are from Dell and HP, so I have focused on these servers
6911 so far. This blog post is about the Dell part.&lt;/P&gt;
6912
6913 &lt;p&gt;On the Dell FTP site I was lucky enough to find
6914 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
6915 with firmware information for all 11th generation servers, listing
6916 which firmware should be used on a given model and where on the FTP
6917 site I can find it. Using a simple perl XML parser I can then
6918 download the shell scripts Dell provides to do firmware upgrades from
6919 within Linux and reboot when all the firmware is primed and ready to
6920 be activated on the first reboot.&lt;/p&gt;
6921
6922 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
6923 Are there anyone working on similar tools for firmware upgrading all
6924 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
6925
6926 &lt;p&gt;&lt;pre&gt;
6927 #!/usr/bin/perl
6928 use strict;
6929 use warnings;
6930 use File::Temp qw(tempdir);
6931 BEGIN {
6932 # Install needed RHEL packages if missing
6933 my %rhelmodules = (
6934 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
6935 );
6936 for my $module (keys %rhelmodules) {
6937 eval &quot;use $module;&quot;;
6938 if ($@) {
6939 my $pkg = $rhelmodules{$module};
6940 system(&quot;yum install -y $pkg&quot;);
6941 eval &quot;use $module;&quot;;
6942 }
6943 }
6944 }
6945 my $errorsto = &#39;pere@hungry.com&#39;;
6946
6947 upgrade_dell();
6948
6949 exit 0;
6950
6951 sub run_firmware_script {
6952 my ($opts, $script) = @_;
6953 unless ($script) {
6954 print STDERR &quot;fail: missing script name\n&quot;;
6955 exit 1
6956 }
6957 print STDERR &quot;Running $script\n\n&quot;;
6958
6959 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
6960 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
6961 } else {
6962 print STDERR &quot;fail: firmware script returned error\n&quot;;
6963 }
6964 }
6965
6966 sub run_firmware_scripts {
6967 my ($opts, @dirs) = @_;
6968 # Run firmware packages
6969 for my $dir (@dirs) {
6970 print STDERR &quot;info: Running scripts in $dir\n&quot;;
6971 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
6972 while (my $s = readdir $dh) {
6973 next if $s =~ m/^\.\.?/;
6974 run_firmware_script($opts, &quot;$dir/$s&quot;);
6975 }
6976 closedir $dh;
6977 }
6978 }
6979
6980 sub download {
6981 my $url = shift;
6982 print STDERR &quot;info: Downloading $url\n&quot;;
6983 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
6984 }
6985
6986 sub upgrade_dell {
6987 my @dirs;
6988 my $product = `dmidecode -s system-product-name`;
6989 chomp $product;
6990
6991 if ($product =~ m/PowerEdge/) {
6992
6993 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6994 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
6995
6996 my $tmpdir = tempdir(
6997 CLEANUP =&gt; 1
6998 );
6999 chdir($tmpdir);
7000 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
7001 system(&#39;gunzip Catalog.xml.gz&#39;);
7002 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
7003 # -q is quiet, disabling interactivity and reducing console output
7004 my $fwopts = &quot;-q&quot;;
7005 if (@paths) {
7006 for my $url (@paths) {
7007 fetch_dell_fw($url);
7008 }
7009 run_firmware_scripts($fwopts, $tmpdir);
7010 } else {
7011 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
7012 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
7013 }
7014 chdir(&#39;/&#39;);
7015 } else {
7016 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
7017 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
7018 }
7019 }
7020
7021 sub fetch_dell_fw {
7022 my $path = shift;
7023 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
7024 download($url);
7025 }
7026
7027 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7028 # firmware packages to download from Dell. Only work for Linux
7029 # machines and 11th generation Dell servers.
7030 sub fetch_dell_fw_list {
7031 my $filename = shift;
7032
7033 my $product = `dmidecode -s system-product-name`;
7034 chomp $product;
7035 my ($mybrand, $mymodel) = split(/\s+/, $product);
7036
7037 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
7038
7039 my $xml = XMLin($filename);
7040 my @paths;
7041 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
7042 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
7043 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
7044 my $oscode;
7045 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
7046 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
7047 } else {
7048 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
7049 }
7050 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
7051 {
7052 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
7053 }
7054 }
7055 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
7056 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
7057
7058 # Drop application packages, only firmware and BIOS
7059 next if &#39;APAC&#39; eq $componenttype;
7060
7061 my $cpath = $component-&gt;{path};
7062 for my $path (@paths) {
7063 if ($cpath =~ m%/$path$%) {
7064 push(@paths, $cpath);
7065 }
7066 }
7067 }
7068 return @paths;
7069 }
7070 &lt;/pre&gt;
7071
7072 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
7073 it could work on other platforms with some tweaking. Anyone know a
7074 index like Catalog.xml is available from HP for HP servers? At the
7075 moment I maintain a similar list manually and it is quickly getting
7076 outdated.&lt;/p&gt;
7077 </description>
7078 </item>
7079
7080 <item>
7081 <title>How is booting into runlevel 1 different from single user boots?</title>
7082 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
7083 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
7084 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
7085 <description>&lt;p&gt;Wouter Verhelst have some
7086 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
7087 comments and opinions&lt;/a&gt; on my blog post on
7088 &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
7089 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
7090 &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
7091 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
7092 small piece of his comment now, and though it best to address the
7093 misunderstanding he bring forward:&lt;/p&gt;
7094
7095 &lt;p&gt;&lt;blockquote&gt;
7096 Currently, a system admin has four options: [...] boot to a
7097 single-user system (by adding &#39;single&#39; to the kernel command line;
7098 this runs rcS and rc1 scripts)
7099 &lt;/blockquote&gt;&lt;/p&gt;
7100
7101 &lt;p&gt;This make me believe Wouter believe booting into single user mode
7102 and booting into runlevel 1 is the same. I am not surprised he
7103 believe this, because it would make sense and is a quite sensible
7104 thing to believe. But because the boot in Debian is slightly broken,
7105 runlevel 1 do not work properly and it isn&#39;t the same as single user
7106 mode. I&#39;ll try to explain what is actually happing, but it is a bit
7107 hard to explain.&lt;/p&gt;
7108
7109 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
7110 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
7111 executed in single user mode is sulogin. Single user mode is a boot
7112 state &quot;between&quot; the runlevels, and when booting into single user mode,
7113 only the scripts in /etc/rcS.d/ are executed before the init process
7114 enters the single user state. When switching to runlevel 1, the state
7115 is in fact not ending in runlevel 1, but it passes through runlevel 1
7116 and end up in the single user mode (see /etc/rc1.d/S03single, which
7117 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
7118 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
7119 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7120 mode).&lt;/p&gt;
7121
7122 &lt;p&gt;This summary might make it clearer. When booting for the first
7123 time into single user mode, the following commands are executed:
7124 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
7125 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
7126 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
7127 trying to continue after visiting single user mode. Not all services
7128 are started again as they should, causing the machine to end up in an
7129 unpredicatble state. This is why Debian admins recommend rebooting
7130 after visiting single user mode.&lt;/p&gt;
7131
7132 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
7133 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
7134 to runlevel 1, the services started from /etc/rcS.d/ are not properly
7135 stopped when passing through the scripts in /etc/rc1.d/, and not
7136 started again when switching away from runlevel 1 to the runlevels
7137 2-5. I believe the problem is best fixed by moving all the scripts
7138 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
7139 functioning single user mode during boot.&lt;/p&gt;
7140
7141 &lt;p&gt;I have spent several years investigating the Debian boot system,
7142 and discovered this problem a few years ago. I suspect it originates
7143 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
7144 </description>
7145 </item>
7146
7147 <item>
7148 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
7149 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
7150 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
7151 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
7152 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
7153 are started from /etc/rcS.d/. In fact, there is a bite more of them
7154 than make sense, and this causes a few problems. What kind of
7155 problems, you might ask. There are at least two problems. The first
7156 is that it is not possible to recover a machine after switching to
7157 runlevel 1. One need to actually reboot to get the machine back to
7158 the expected state. The other is that single user boot will sometimes
7159 run into problems because some of the subsystems are activated before
7160 the root login is presented, causing problems when trying to recover a
7161 machine from a problem in that subsystem. A minor additional point is
7162 that moving more scripts out of rcS.d/ and into the other rc#.d/
7163 directories will increase the amount of scripts that can run in
7164 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
7165
7166 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
7167 scripts that _have_ to execute before the root login prompt is
7168 presented during a single user boot should go there. Everything else
7169 should go into the numeric runlevels. This means things like
7170 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7171 the numeric runlevels. Today in Debian, there are around 115 init.d
7172 scripts that are started from rcS.d/, and most of them should be moved
7173 out. Do your package have one of them? Please help us make single
7174 user and runlevel 1 better by moving it.&lt;/p&gt;
7175
7176 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
7177 etc. should still be started from rcS.d/, but there is for example no
7178 need to have the network enabled before the single user login prompt
7179 is presented.&lt;/p&gt;
7180
7181 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
7182 Debian systems working while scripts migrate and during upgrades, the
7183 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7184 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7185 and the next ones can only be moved when their dependencies have been
7186 moved first. This migration must be done sequentially while we ensure
7187 that the package system upgrade packages in the right order to keep
7188 the system state correct. This will require some coordination when it
7189 comes to network related packages, but most of the packages with
7190 scripts that should migrate do not have anything in rcS.d/ depending
7191 on them. Some packages have already been updated, like the sudo
7192 package, while others are still left to do. I wish I had time to work
7193 on this myself, but real live constrains make it unlikely that I will
7194 find time to push this forward.&lt;/p&gt;
7195 </description>
7196 </item>
7197
7198 <item>
7199 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
7200 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
7201 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
7202 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
7203 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
7204 mentioned the issues I believe should be improved in Debian for its
7205 desktop to be useful for more people. The use case for this is my
7206 parents, which are currently running Kubuntu which solve the
7207 issues.&lt;/p&gt;
7208
7209 &lt;p&gt;I suspect these four missing features are not very hard to
7210 implement. After all, they are present in Ubuntu, so if we wanted to
7211 do this in Debian we would have a source.&lt;/p&gt;
7212
7213 &lt;ol&gt;
7214
7215 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
7216 are new packages available for upgrades, a icon in the KDE status bar
7217 indicate this, and clicking on it will activate the simple upgrade
7218 tool to handle it. I have no problem guiding both of my parents
7219 through the process over the phone. If a kernel reboot is required,
7220 this too is indicated by the status bars and the upgrade tool. Last
7221 time I checked, nothing with the same features was working in KDE in
7222 Debian.&lt;/li&gt;
7223
7224 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
7225 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
7226 currently have a handler for, it will ask the user if the system
7227 should search for a package that would add support for this MIME type,
7228 and if the user say yes, the APT sources will be searched for packages
7229 advertising the MIME type in their control file (visible in the
7230 Packages file in the APT archive). If one or more packages are found,
7231 it is a simple click of the mouse to add support for the missing mime
7232 type. If the package require the user to accept some non-free
7233 license, this is explained to the user. The entire process make it
7234 more clear to the user why something do not work in the browser, and
7235 make the chances higher for the user to blame the web page authors and
7236 not the browser for any missing features.&lt;/li&gt;
7237
7238 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
7239 handlers.&lt;/strong&gt; When the media players encounter a format or codec
7240 it is not supporting, a dialog pop up asking the user if the system
7241 should search for a package that would add support for it. This
7242 happen with things like MP3, Windows Media or H.264. The selection
7243 and installation procedure is very similar to the Firefox browser
7244 plugin handling. This is as far as I know implemented using a
7245 gstreamer hook. The end result is that the user easily get access to
7246 the codecs that are present from the APT archives available, while
7247 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
7248
7249 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
7250 displaying a text/plain file in my Debian browser, it will propose to
7251 start emacs to show it. If I remember correctly, when doing the same
7252 in Kunbutu it show the file as a text file in the browser. At least I
7253 know Opera will show text files within the browser. I much prefer the
7254 latter behaviour.&lt;/li&gt;
7255
7256 &lt;/ol&gt;
7257
7258 &lt;p&gt;There are other nice features as well, like the simplified suite
7259 upgrader, but given that I am the one mostly doing the dist-upgrade,
7260 it do not matter much.&lt;/p&gt;
7261
7262 &lt;p&gt;I really hope we could get these features in place for the next
7263 Debian release. It would require the coordinated effort of several
7264 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
7265 </description>
7266 </item>
7267
7268 <item>
7269 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
7270 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
7271 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
7272 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
7273 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
7274 site is build on Debian/Squeeze, and this platform was chosen because
7275 I am most familiar with Debian (being a Debian Developer for around 10
7276 years) because it is the latest stable Debian release which should get
7277 security support for a few years.&lt;/p&gt;
7278
7279 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
7280 that are missing in Debian at the moment. It would be great if these
7281 modules were added to the Debian archive, allowing anyone to set up
7282 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
7283 in their own country using only Debian packages. The list of modules
7284 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
7285 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
7286 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7287 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7288 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7289 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7290 easier in the future.&lt;/p&gt;
7291
7292 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
7293 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
7294 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
7295 with the responsibility of tracking security problems, which I really
7296 do not have time for.&lt;/p&gt;
7297 </description>
7298 </item>
7299
7300 <item>
7301 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
7302 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
7303 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
7304 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
7305 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
7306 posts have been in Norwegian the last few weeks, so here is a short
7307 update in English.&lt;/p&gt;
7308
7309 &lt;p&gt;The kids still keep me too busy to get much free software work
7310 done, but I did manage to organise a project to get a Norwegian port
7311 of the British service
7312 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
7313 and it has been running for a month now. The entire project has been
7314 organised by me and two others. Around Christmas we gathered sponsors
7315 to fund the development work. In January I drafted a contract with
7316 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
7317 and in February the development took place. Most of it involved
7318 converting the source to use GPS coordinates instead of British
7319 easting/northing, and the resulting code should be a lot easier to get
7320 running in any country by now. The Norwegian
7321 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
7322 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
7323 source and the source for administrative borders in Norway, and
7324 support for this had to be added/fixed.&lt;/p&gt;
7325
7326 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
7327 polishing the system before we announced it March 7th. The system is
7328 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
7329 problem reports in a few weeks. Soon we hope to announce the Android
7330 and iPhone versions making it even easier to report problems with the
7331 public infrastructure.&lt;/p&gt;
7332
7333 &lt;p&gt;Perhaps something to consider for those of you in countries without
7334 such service?&lt;/p&gt;
7335 </description>
7336 </item>
7337
7338 <item>
7339 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
7340 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
7341 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
7342 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
7343 <description>&lt;p&gt;The last few days I have looked at ways to track open security
7344 issues here at my work with the University of Oslo. My idea is that
7345 it should be possible to use the information about security issues
7346 available on the Internet, and check our locally
7347 maintained/distributed software against this information. It should
7348 allow us to verify that no known security issues are forgotten. The
7349 CVE database listing vulnerabilities seem like a great central point,
7350 and by using the package lists from Debian mapped to CVEs provided by
7351 the testing security team, I believed it should be possible to figure
7352 out which security holes were present in our free software
7353 collection.&lt;/p&gt;
7354
7355 &lt;p&gt;After reading up on the topic, it became obvious that the first
7356 building block is to be able to name software packages in a unique and
7357 consistent way across data sources. I considered several ways to do
7358 this, for example coming up with my own naming scheme like using URLs
7359 to project home pages or URLs to the Freshmeat entries, or using some
7360 existing naming scheme. And it seem like I am not the first one to
7361 come across this problem, as MITRE already proposed and implemented a
7362 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
7363 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
7364 software, hardware and other platform components. The CPE ids are
7365 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
7366 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
7367 issues for any CPE name. With this in place, all I need to do is to
7368 locate the CPE id for the software packages we use at the university.
7369 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
7370 NVD entry if a CVE for the package exist).&lt;/p&gt;
7371
7372 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
7373 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
7374 check out, one could look up
7375 &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
7376 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
7377 The most recent one is
7378 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
7379 and at the bottom of the NVD page for this vulnerability the complete
7380 list of affected versions is provided.&lt;/p&gt;
7381
7382 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
7383 for offline processing of issues. Using this dump, I&#39;ve written a
7384 small script taking a list of CPEs as input and list all CVEs
7385 affecting the packages represented by these CPEs. One give it CPEs
7386 with version numbers as specified above and get a list of open
7387 security issues out.&lt;/p&gt;
7388
7389 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
7390 information need to be high. For that to happen, I believe as many as
7391 possible need to use and contribute to the NVD database. I notice
7392 RHEL is providing
7393 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
7394 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
7395 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
7396
7397 &lt;p&gt;To get an idea about the quality for free software, I spent some
7398 time making it possible to compare the CVE database from Debian with
7399 the CVE database in NVD. The result look fairly good, but there are
7400 some inconsistencies in NVD (same software package having several
7401 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7402 Debian believe are affected by a CVE). Hope to find time to improve
7403 the quality of NVD, but that require being able to get in touch with
7404 someone maintaining it. So far my three emails with questions and
7405 corrections have not seen any reply, but I hope contact can be
7406 established soon.&lt;/p&gt;
7407
7408 &lt;p&gt;An interesting application for CPEs is cross platform package
7409 mapping. It would be useful to know which packages in for example
7410 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7411 this would be trivial if all linux distributions provided CPE entries
7412 for their packages.&lt;/p&gt;
7413 </description>
7414 </item>
7415
7416 <item>
7417 <title>Which module is loaded for a given PCI and USB device?</title>
7418 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
7419 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
7420 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
7421 <description>&lt;p&gt;In the
7422 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
7423 package in Debian, there is a script to report useful information
7424 about the running hardware for use when people report missing
7425 information. One part of this script that I find very useful when
7426 debugging hardware problems, is the part mapping loaded kernel module
7427 to the PCI device it claims. It allow me to quickly see if the kernel
7428 module I expect is driving the hardware I am struggling with. To see
7429 the output, make sure discover-data is installed and run
7430 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
7431 one of my machines like this:&lt;/p&gt;
7432
7433 &lt;pre&gt;
7434 loaded modules:
7435 10de:03eb i2c_nforce2
7436 10de:03f1 ohci_hcd
7437 10de:03f2 ehci_hcd
7438 10de:03f0 snd_hda_intel
7439 10de:03ec pata_amd
7440 10de:03f6 sata_nv
7441 1022:1103 k8temp
7442 109e:036e bttv
7443 109e:0878 snd_bt87x
7444 11ab:4364 sky2
7445 &lt;/pre&gt;
7446
7447 &lt;p&gt;The code in question look like this, slightly modified for
7448 readability and to drop the output to file descriptor 3:&lt;/p&gt;
7449
7450 &lt;pre&gt;
7451 if [ -d /sys/bus/pci/devices/ ] ; then
7452 echo loaded pci modules:
7453 (
7454 cd /sys/bus/pci/devices/
7455 for address in * ; do
7456 if [ -d &quot;$address/driver/module&quot; ] ; then
7457 module=`cd $address/driver/module ; pwd -P | xargs basename`
7458 if grep -q &quot;^$module &quot; /proc/modules ; then
7459 address=$(echo $address |sed s/0000://)
7460 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
7461 echo &quot;$id $module&quot;
7462 fi
7463 fi
7464 done
7465 )
7466 echo
7467 fi
7468 &lt;/pre&gt;
7469
7470 &lt;p&gt;Similar code could be used to extract USB device module
7471 mappings:&lt;/p&gt;
7472
7473 &lt;pre&gt;
7474 if [ -d /sys/bus/usb/devices/ ] ; then
7475 echo loaded usb modules:
7476 (
7477 cd /sys/bus/usb/devices/
7478 for address in * ; do
7479 if [ -d &quot;$address/driver/module&quot; ] ; then
7480 module=`cd $address/driver/module ; pwd -P | xargs basename`
7481 if grep -q &quot;^$module &quot; /proc/modules ; then
7482 address=$(echo $address |sed s/0000://)
7483 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
7484 if [ &quot;$id&quot; ] ; then
7485 echo &quot;$id $module&quot;
7486 fi
7487 fi
7488 fi
7489 done
7490 )
7491 echo
7492 fi
7493 &lt;/pre&gt;
7494
7495 &lt;p&gt;This might perhaps be something to include in other tools as
7496 well.&lt;/p&gt;
7497 </description>
7498 </item>
7499
7500 <item>
7501 <title>How to test if a laptop is working with Linux</title>
7502 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
7503 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
7504 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
7505 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
7506 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
7507 batch of computers will work with Linux. Every year for the last few
7508 years the university have organised shared bid of a few thousand
7509 computers, and this year HP won the bid. Two different desktops and
7510 five different laptops are on the list this year. We in the UNIX
7511 group want to know which one of these computers work well with RHEL
7512 and Ubuntu, the two Linux distributions we currently handle at the
7513 university.&lt;/p&gt;
7514
7515 &lt;p&gt;My test method is simple, and I share it here to get feedback and
7516 perhaps inspire others to test hardware as well. To test, I PXE
7517 install the OS version of choice, and log in as my normal user and run
7518 a few applications and plug in selected pieces of hardware. When
7519 something fail, I make a note about this in the test matrix and move
7520 on. If I have some spare time I try to report the bug to the OS
7521 vendor, but as I only have the machines for a short time, I rarely
7522 have the time to do this for all the problems I find.&lt;/p&gt;
7523
7524 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
7525 I perform on a new model.&lt;/p&gt;
7526
7527 &lt;ul&gt;
7528
7529 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
7530 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7531 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
7532
7533 &lt;li&gt;Is X.org working? If the graphical login screen show up after
7534 installation, X.org is working.&lt;/li&gt;
7535
7536 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
7537 package mesa-utils on Ubuntu) and writing down the frames per second
7538 reported by the program.&lt;/li&gt;
7539
7540 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
7541 logging in, and if I can hear this the test is successful. If there
7542 are several audio exits on the machine, I try them all and check if
7543 the Gnome/KDE audio mixer can control where to send the sound. I
7544 normally test this by playing
7545 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
7546 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
7547
7548 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
7549 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
7550
7551 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
7552 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
7553
7554 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
7555 picture from the v4l device show up.&lt;/li&gt;
7556
7557 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7558 any bluetooth devices are discovered. In my office, I normally see a
7559 few.&lt;/li&gt;
7560
7561 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
7562 memory modules lying around, and stick them in and see if Gnome/KDE
7563 notice this.&lt;/li&gt;
7564
7565 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
7566 special button work, and if the laptop continue to work after
7567 resume.&lt;/li&gt;
7568
7569 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
7570 adjusting background light, switching on/off external video output,
7571 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7572 laptop to laptop, so I just write down which are working and which are
7573 not.&lt;/li&gt;
7574
7575 &lt;li&gt;Some laptops have smart card readers, finger print readers,
7576 acceleration sensors etc. I rarely test these, as I do not know how
7577 to quickly test if they are working or not, so I only document their
7578 existence.&lt;/li&gt;
7579
7580 &lt;/ul&gt;
7581
7582 &lt;p&gt;By now I suspect you are really curious what the test results are
7583 for the HP machines I am testing. I&#39;m not done yet, so I will report
7584 the test results later. For now I can report that HP 8100 Elite work
7585 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
7586 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
7587 can see, I have most machines left to test. One interesting
7588 observation is that Ubuntu Lucid has almost twice the frame rate than
7589 RHEL6 with glxgears. No idea why.&lt;/p&gt;
7590 </description>
7591 </item>
7592
7593 <item>
7594 <title>Some thoughts on BitCoins</title>
7595 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
7596 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
7597 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
7598 <description>&lt;p&gt;As I continue to explore
7599 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
7600 what properties the system have, and how it will be affected by laws
7601 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
7602
7603 &lt;p&gt;One interesting thing to note is that since the transactions are
7604 verified using a peer to peer network, all details about a transaction
7605 is known to everyone. This means that if a BitCoin address has been
7606 published like I did with mine in my initial post about BitCoin, it is
7607 possible for everyone to see how many BitCoins have been transfered to
7608 that address. There is even a web service to look at the details for
7609 all transactions. There I can see that my address
7610 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
7611 have received 16.06 Bitcoin, the
7612 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
7613 address of Simon Phipps have received 181.97 BitCoin and the address
7614 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
7615 of EFF have received 2447.38 BitCoins so far. Thank you to each and
7616 every one of you that donated bitcoins to support my activity. The
7617 fact that anyone can see how much money was transfered to a given
7618 address make it more obvious why the BitCoin community recommend to
7619 generate and hand out a new address for each transaction. I&#39;m told
7620 there is no way to track which addresses belong to a given person or
7621 organisation without the person or organisation revealing it
7622 themselves, as Simon, EFF and I have done.&lt;/p&gt;
7623
7624 &lt;p&gt;In Norway, and in most other countries, there are laws and
7625 regulations limiting how much money one can transfer across the border
7626 without declaring it. There are money laundering, tax and accounting
7627 laws and regulations I would expect to apply to the use of BitCoin.
7628 If the Skolelinux foundation
7629 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
7630 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
7631 normal bank transfers like EFF is doing, how should this be accounted?
7632 Given that it is impossible to know if money can cross the border or
7633 not, should everything or nothing be declared? What exchange rate
7634 should be used when calculating taxes? Would receivers have to pay
7635 income tax if the foundation were to pay Skolelinux contributors in
7636 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
7637
7638 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
7639 accepted by a lot of users. It must be possible to get easy access to
7640 the currency (as a wage or using currency exchanges), and it must be
7641 easy to spend it. At the moment BitCoin seem fairly easy to get
7642 access to, but there are very few places to spend it. I am not really
7643 a regular user of any of the vendor types currently accepting BitCoin,
7644 so I wonder when my kind of shop would start accepting BitCoins. I
7645 would like to buy electronics, travels and subway tickets, not herbs
7646 and books. :) The currency is young, and this will improve over time
7647 if it become popular, but I suspect regular banks will start to lobby
7648 to get BitCoin declared illegal if it become popular. I&#39;m sure they
7649 will claim it is helping fund terrorism and money laundering (which
7650 probably would be true, as is any currency in existence), but I
7651 believe the problems should be solved elsewhere and not by blaming
7652 currencies.&lt;/p&gt;
7653
7654 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
7655 CPU intensive process that depend on a bit of luck as well (as one is
7656 competing against all the other miners currently spending CPU cycles
7657 to see which one get the next lump of cash). The &quot;winner&quot; get 50
7658 BitCoin when this happen. Yesterday I came across the obvious way to
7659 join forces to increase ones changes of getting at least some coins,
7660 by coordinating the work on mining BitCoins across several machines
7661 and people, and sharing the result if one is lucky and get the 50
7662 BitCoins. Check out
7663 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
7664 if this sounds interesting. I have not had time to try to set up a
7665 machine to participate there yet, but have seen that running on ones
7666 own for a few days have not yield any BitCoins througth mining
7667 yet.&lt;/p&gt;
7668
7669 &lt;p&gt;Update 2010-12-15: Found an &lt;a
7670 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
7671 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
7672 it was interesting to read. The arguments presented seem to be
7673 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
7674 </description>
7675 </item>
7676
7677 <item>
7678 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
7679 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
7680 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
7681 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
7682 <description>&lt;p&gt;With this weeks lawless
7683 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
7684 attacks&lt;/a&gt; on Wikileak and
7685 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
7686 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
7687 not be trusted to handle money transactions.
7688 A blog post from
7689 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
7690 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
7691 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
7692 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
7693 some help from my friend to get it all running, and he even handed me
7694 some bitcoins to get started. I even donated a few bitcoins to Simon
7695 for helping me remember BitCoin.&lt;/p&gt;
7696
7697 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
7698 crypto-currency, decentralised and handled using peer-to-peer
7699 networks. It allows anonymous transactions and prohibits central
7700 control over the transactions, making it impossible for governments
7701 and companies alike to block donations and other transactions. The
7702 source is free software, and while the key dependency wxWidgets 2.9
7703 for the graphical user interface is missing in Debian, the command
7704 line client builds just fine. Hopefully Jonas
7705 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
7706 Debian&lt;/a&gt; soon.&lt;/p&gt;
7707
7708 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
7709 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
7710 bitcoins&lt;/a&gt; when selling services and goods, and there are even
7711 currency &quot;stock&quot; markets where the exchange rate is decided. There
7712 are not many users so far, but the concept seems promising. If you
7713 want to get started and lack a friend with any bitcoins to spare,
7714 you can even get
7715 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
7716 bitcoin at the time of writing). Use
7717 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
7718 on the current exchange rates.&lt;/p&gt;
7719
7720 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
7721 machines. If you want to support my activity, please send Bitcoin
7722 donations to the address
7723 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
7724 </description>
7725 </item>
7726
7727 <item>
7728 <title>Why isn&#39;t Debian Edu using VLC?</title>
7729 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
7730 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
7731 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
7732 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
7733 presented, and the winner among the multimedia player were VLC.
7734 Personally, I like VLC, and it is my player of choice when I first try
7735 to play a video file or stream. Only if VLC fail will I drag out
7736 gmplayer to see if it can do better. The reason is mostly the failure
7737 model and trust. When VLC fail, it normally pop up a error message
7738 reporting the problem. When mplayer fail, it normally segfault or
7739 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
7740
7741 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
7742 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
7743 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
7744 plugin to play web videos seamlessly, and the VLC browser plugin is
7745 not very good. For example, it lack in-line control buttons, so there
7746 is no way for the user to pause the video. Also, when I
7747 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
7748 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
7749 failed on several video pages where mplayer based plugins worked. If
7750 the browser plugin for VLC was as good as the gecko-mediaplayer
7751 package (which uses mplayer), we would switch.&lt;/P&gt;
7752
7753 &lt;p&gt;While VLC is a good player, its user interface is slightly
7754 annoying. The most annoying feature is its inconsistent use of
7755 keyboard shortcuts. When the player is in full screen mode, its
7756 shortcuts are different from when it is playing the video in a window.
7757 For example, space only work as pause when in full screen mode. I
7758 wish it had consisten shortcuts and that space also would work when in
7759 window mode. Another nice shortcut in gmplayer is [enter] to restart
7760 the current video. It is very nice when playing short videos from the
7761 web and want to restart it when new people arrive to have a look at
7762 what is going on.&lt;/p&gt;
7763 </description>
7764 </item>
7765
7766 <item>
7767 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
7768 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
7769 <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>
7770 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
7771 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
7772 upgrade testing of the
7773 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
7774 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
7775 This seem like a very good idea, so I adjusted by test scripts and
7776 can now present the updated result from today:&lt;/p&gt;
7777
7778 &lt;p&gt;This is for Gnome:&lt;/p&gt;
7779
7780 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7781
7782 &lt;blockquote&gt;&lt;p&gt;
7783 apache2.2-bin
7784 aptdaemon
7785 baobab
7786 binfmt-support
7787 browser-plugin-gnash
7788 cheese-common
7789 cli-common
7790 cups-pk-helper
7791 dmz-cursor-theme
7792 empathy
7793 empathy-common
7794 freedesktop-sound-theme
7795 freeglut3
7796 gconf-defaults-service
7797 gdm-themes
7798 gedit-plugins
7799 geoclue
7800 geoclue-hostip
7801 geoclue-localnet
7802 geoclue-manual
7803 geoclue-yahoo
7804 gnash
7805 gnash-common
7806 gnome
7807 gnome-backgrounds
7808 gnome-cards-data
7809 gnome-codec-install
7810 gnome-core
7811 gnome-desktop-environment
7812 gnome-disk-utility
7813 gnome-screenshot
7814 gnome-search-tool
7815 gnome-session-canberra
7816 gnome-system-log
7817 gnome-themes-extras
7818 gnome-themes-more
7819 gnome-user-share
7820 gstreamer0.10-fluendo-mp3
7821 gstreamer0.10-tools
7822 gtk2-engines
7823 gtk2-engines-pixbuf
7824 gtk2-engines-smooth
7825 hamster-applet
7826 libapache2-mod-dnssd
7827 libapr1
7828 libaprutil1
7829 libaprutil1-dbd-sqlite3
7830 libaprutil1-ldap
7831 libart2.0-cil
7832 libboost-date-time1.42.0
7833 libboost-python1.42.0
7834 libboost-thread1.42.0
7835 libchamplain-0.4-0
7836 libchamplain-gtk-0.4-0
7837 libcheese-gtk18
7838 libclutter-gtk-0.10-0
7839 libcryptui0
7840 libdiscid0
7841 libelf1
7842 libepc-1.0-2
7843 libepc-common
7844 libepc-ui-1.0-2
7845 libfreerdp-plugins-standard
7846 libfreerdp0
7847 libgconf2.0-cil
7848 libgdata-common
7849 libgdata7
7850 libgdu-gtk0
7851 libgee2
7852 libgeoclue0
7853 libgexiv2-0
7854 libgif4
7855 libglade2.0-cil
7856 libglib2.0-cil
7857 libgmime2.4-cil
7858 libgnome-vfs2.0-cil
7859 libgnome2.24-cil
7860 libgnomepanel2.24-cil
7861 libgpod-common
7862 libgpod4
7863 libgtk2.0-cil
7864 libgtkglext1
7865 libgtksourceview2.0-common
7866 libmono-addins-gui0.2-cil
7867 libmono-addins0.2-cil
7868 libmono-cairo2.0-cil
7869 libmono-corlib2.0-cil
7870 libmono-i18n-west2.0-cil
7871 libmono-posix2.0-cil
7872 libmono-security2.0-cil
7873 libmono-sharpzip2.84-cil
7874 libmono-system2.0-cil
7875 libmtp8
7876 libmusicbrainz3-6
7877 libndesk-dbus-glib1.0-cil
7878 libndesk-dbus1.0-cil
7879 libopal3.6.8
7880 libpolkit-gtk-1-0
7881 libpt2.6.7
7882 libpython2.6
7883 librpm1
7884 librpmio1
7885 libsdl1.2debian
7886 libsrtp0
7887 libssh-4
7888 libtelepathy-farsight0
7889 libtelepathy-glib0
7890 libtidy-0.99-0
7891 media-player-info
7892 mesa-utils
7893 mono-2.0-gac
7894 mono-gac
7895 mono-runtime
7896 nautilus-sendto
7897 nautilus-sendto-empathy
7898 p7zip-full
7899 pkg-config
7900 python-aptdaemon
7901 python-aptdaemon-gtk
7902 python-axiom
7903 python-beautifulsoup
7904 python-bugbuddy
7905 python-clientform
7906 python-coherence
7907 python-configobj
7908 python-crypto
7909 python-cupshelpers
7910 python-elementtree
7911 python-epsilon
7912 python-evolution
7913 python-feedparser
7914 python-gdata
7915 python-gdbm
7916 python-gst0.10
7917 python-gtkglext1
7918 python-gtksourceview2
7919 python-httplib2
7920 python-louie
7921 python-mako
7922 python-markupsafe
7923 python-mechanize
7924 python-nevow
7925 python-notify
7926 python-opengl
7927 python-openssl
7928 python-pam
7929 python-pkg-resources
7930 python-pyasn1
7931 python-pysqlite2
7932 python-rdflib
7933 python-serial
7934 python-tagpy
7935 python-twisted-bin
7936 python-twisted-conch
7937 python-twisted-core
7938 python-twisted-web
7939 python-utidylib
7940 python-webkit
7941 python-xdg
7942 python-zope.interface
7943 remmina
7944 remmina-plugin-data
7945 remmina-plugin-rdp
7946 remmina-plugin-vnc
7947 rhythmbox-plugin-cdrecorder
7948 rhythmbox-plugins
7949 rpm-common
7950 rpm2cpio
7951 seahorse-plugins
7952 shotwell
7953 software-center
7954 system-config-printer-udev
7955 telepathy-gabble
7956 telepathy-mission-control-5
7957 telepathy-salut
7958 tomboy
7959 totem
7960 totem-coherence
7961 totem-mozilla
7962 totem-plugins
7963 transmission-common
7964 xdg-user-dirs
7965 xdg-user-dirs-gtk
7966 xserver-xephyr
7967 &lt;/p&gt;&lt;/blockquote&gt;
7968
7969 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7970
7971 &lt;blockquote&gt;&lt;p&gt;
7972 cheese
7973 ekiga
7974 eog
7975 epiphany-extensions
7976 evolution-exchange
7977 fast-user-switch-applet
7978 file-roller
7979 gcalctool
7980 gconf-editor
7981 gdm
7982 gedit
7983 gedit-common
7984 gnome-games
7985 gnome-games-data
7986 gnome-nettool
7987 gnome-system-tools
7988 gnome-themes
7989 gnuchess
7990 gucharmap
7991 guile-1.8-libs
7992 libavahi-ui0
7993 libdmx1
7994 libgalago3
7995 libgtk-vnc-1.0-0
7996 libgtksourceview2.0-0
7997 liblircclient0
7998 libsdl1.2debian-alsa
7999 libspeexdsp1
8000 libsvga1
8001 rhythmbox
8002 seahorse
8003 sound-juicer
8004 system-config-printer
8005 totem-common
8006 transmission-gtk
8007 vinagre
8008 vino
8009 &lt;/p&gt;&lt;/blockquote&gt;
8010
8011 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8012
8013 &lt;blockquote&gt;&lt;p&gt;
8014 gstreamer0.10-gnomevfs
8015 &lt;/p&gt;&lt;/blockquote&gt;
8016
8017 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8018
8019 &lt;blockquote&gt;&lt;p&gt;
8020 [nothing]
8021 &lt;/p&gt;&lt;/blockquote&gt;
8022
8023 &lt;p&gt;This is for KDE:&lt;/p&gt;
8024
8025 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8026
8027 &lt;blockquote&gt;&lt;p&gt;
8028 ksmserver
8029 &lt;/p&gt;&lt;/blockquote&gt;
8030
8031 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8032
8033 &lt;blockquote&gt;&lt;p&gt;
8034 kwin
8035 network-manager-kde
8036 &lt;/p&gt;&lt;/blockquote&gt;
8037
8038 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8039
8040 &lt;blockquote&gt;&lt;p&gt;
8041 arts
8042 dolphin
8043 freespacenotifier
8044 google-gadgets-gst
8045 google-gadgets-xul
8046 kappfinder
8047 kcalc
8048 kcharselect
8049 kde-core
8050 kde-plasma-desktop
8051 kde-standard
8052 kde-window-manager
8053 kdeartwork
8054 kdeartwork-emoticons
8055 kdeartwork-style
8056 kdeartwork-theme-icon
8057 kdebase
8058 kdebase-apps
8059 kdebase-workspace
8060 kdebase-workspace-bin
8061 kdebase-workspace-data
8062 kdeeject
8063 kdelibs
8064 kdeplasma-addons
8065 kdeutils
8066 kdewallpapers
8067 kdf
8068 kfloppy
8069 kgpg
8070 khelpcenter4
8071 kinfocenter
8072 konq-plugins-l10n
8073 konqueror-nsplugins
8074 kscreensaver
8075 kscreensaver-xsavers
8076 ktimer
8077 kwrite
8078 libgle3
8079 libkde4-ruby1.8
8080 libkonq5
8081 libkonq5-templates
8082 libnetpbm10
8083 libplasma-ruby
8084 libplasma-ruby1.8
8085 libqt4-ruby1.8
8086 marble-data
8087 marble-plugins
8088 netpbm
8089 nuvola-icon-theme
8090 plasma-dataengines-workspace
8091 plasma-desktop
8092 plasma-desktopthemes-artwork
8093 plasma-runners-addons
8094 plasma-scriptengine-googlegadgets
8095 plasma-scriptengine-python
8096 plasma-scriptengine-qedje
8097 plasma-scriptengine-ruby
8098 plasma-scriptengine-webkit
8099 plasma-scriptengines
8100 plasma-wallpapers-addons
8101 plasma-widget-folderview
8102 plasma-widget-networkmanagement
8103 ruby
8104 sweeper
8105 update-notifier-kde
8106 xscreensaver-data-extra
8107 xscreensaver-gl
8108 xscreensaver-gl-extra
8109 xscreensaver-screensaver-bsod
8110 &lt;/p&gt;&lt;/blockquote&gt;
8111
8112 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8113
8114 &lt;blockquote&gt;&lt;p&gt;
8115 ark
8116 google-gadgets-common
8117 google-gadgets-qt
8118 htdig
8119 kate
8120 kdebase-bin
8121 kdebase-data
8122 kdepasswd
8123 kfind
8124 klipper
8125 konq-plugins
8126 konqueror
8127 ksysguard
8128 ksysguardd
8129 libarchive1
8130 libcln6
8131 libeet1
8132 libeina-svn-06
8133 libggadget-1.0-0b
8134 libggadget-qt-1.0-0b
8135 libgps19
8136 libkdecorations4
8137 libkephal4
8138 libkonq4
8139 libkonqsidebarplugin4a
8140 libkscreensaver5
8141 libksgrd4
8142 libksignalplotter4
8143 libkunitconversion4
8144 libkwineffects1a
8145 libmarblewidget4
8146 libntrack-qt4-1
8147 libntrack0
8148 libplasma-geolocation-interface4
8149 libplasmaclock4a
8150 libplasmagenericshell4
8151 libprocesscore4a
8152 libprocessui4a
8153 libqalculate5
8154 libqedje0a
8155 libqtruby4shared2
8156 libqzion0a
8157 libruby1.8
8158 libscim8c2a
8159 libsmokekdecore4-3
8160 libsmokekdeui4-3
8161 libsmokekfile3
8162 libsmokekhtml3
8163 libsmokekio3
8164 libsmokeknewstuff2-3
8165 libsmokeknewstuff3-3
8166 libsmokekparts3
8167 libsmokektexteditor3
8168 libsmokekutils3
8169 libsmokenepomuk3
8170 libsmokephonon3
8171 libsmokeplasma3
8172 libsmokeqtcore4-3
8173 libsmokeqtdbus4-3
8174 libsmokeqtgui4-3
8175 libsmokeqtnetwork4-3
8176 libsmokeqtopengl4-3
8177 libsmokeqtscript4-3
8178 libsmokeqtsql4-3
8179 libsmokeqtsvg4-3
8180 libsmokeqttest4-3
8181 libsmokeqtuitools4-3
8182 libsmokeqtwebkit4-3
8183 libsmokeqtxml4-3
8184 libsmokesolid3
8185 libsmokesoprano3
8186 libtaskmanager4a
8187 libtidy-0.99-0
8188 libweather-ion4a
8189 libxklavier16
8190 libxxf86misc1
8191 okteta
8192 oxygencursors
8193 plasma-dataengines-addons
8194 plasma-scriptengine-superkaramba
8195 plasma-widget-lancelot
8196 plasma-widgets-addons
8197 plasma-widgets-workspace
8198 polkit-kde-1
8199 ruby1.8
8200 systemsettings
8201 update-notifier-common
8202 &lt;/p&gt;&lt;/blockquote&gt;
8203
8204 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
8205 aptitude a bit more similar, but there are still quite a lott of
8206 differences. I have no idea what packages should be installed after
8207 the upgrade, but hope those that do can have a look.&lt;/p&gt;
8208 </description>
8209 </item>
8210
8211 <item>
8212 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
8213 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
8214 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
8215 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
8216 <description>&lt;p&gt;Most of the computers in use by the
8217 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
8218 are virtual machines. And they have been Xen machines running on a
8219 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
8220 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
8221 bit harder that it could have been, because we set up the Xen virtual
8222 machines to get the virtual partitions from LVM, which as far as I
8223 know is not supported by KVM. So to migrate, we had to convert
8224 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
8225
8226 &lt;p&gt;I found
8227 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
8228 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
8229 migration. It uses qemu-img from the qemu package to make the disk
8230 image, parted to partition it, losetup and kpartx to present the disk
8231 image partions as devices, and dd to copy the data. I NFS mounted the
8232 new servers storage area on the old server to do the migration.&lt;/p&gt;
8233
8234 &lt;pre&gt;
8235 #!/bin/sh
8236
8237 # Based on
8238 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8239
8240 set -e
8241 set -x
8242
8243 if [ -z &quot;$1&quot; ] ; then
8244 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
8245 exit 1
8246 else
8247 host=&quot;$1&quot;
8248 fi
8249
8250 if [ ! -e /dev/vg_data/$host-disk ] ; then
8251 echo &quot;error: unable to find LVM volume for $host&quot;
8252 exit 1
8253 fi
8254
8255 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8256 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
8257 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
8258 totalsize=$(( ( $disksize + $swapsize ) ))
8259
8260 img=$host.img
8261 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
8262 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8263
8264 parted $img mklabel msdos
8265 parted $img mkpart primary linux-swap 0 $disksize
8266 parted $img mkpart primary ext2 $disksize $totalsize
8267 parted $img set 1 boot on
8268
8269 modprobe dm-mod
8270 losetup /dev/loop0 $img
8271 kpartx -a /dev/loop0
8272
8273 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
8274 fsck.ext3 -f /dev/mapper/loop0p1 || true
8275 mkswap /dev/mapper/loop0p2
8276
8277 kpartx -d /dev/loop0
8278 losetup -d /dev/loop0
8279 &lt;/pre&gt;
8280
8281 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
8282 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
8283
8284 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
8285 the new disk image attached, installed grub-pc and linux-image-686 and
8286 set up grub to boot from the disk image. After this, the KVM machines
8287 seem to work just fine.&lt;/p&gt;
8288 </description>
8289 </item>
8290
8291 <item>
8292 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
8293 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
8294 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
8295 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
8296 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
8297 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
8298 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
8299 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
8300
8301 &lt;p&gt;I still do not know what a correct migration should look like, so I
8302 report any differences between apt and aptitude and hope someone else
8303 can see if anything should be changed.&lt;/p&gt;
8304
8305 &lt;p&gt;This is for Gnome:&lt;/p&gt;
8306
8307 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8308
8309 &lt;blockquote&gt;&lt;p&gt;
8310 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8311 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
8312 dmz-cursor-theme empathy empathy-common finger
8313 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8314 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8315 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8316 gnome-cards-data gnome-codec-install gnome-core
8317 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8318 gnome-search-tool gnome-session-canberra gnome-spell
8319 gnome-system-log gnome-themes-extras gnome-themes-more
8320 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8321 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8322 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8323 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8324 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
8325 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
8326 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
8327 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
8328 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
8329 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8330 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
8331 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8332 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8333 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8334 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8335 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8336 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8337 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8338 libmono-security2.0-cil libmono-sharpzip2.84-cil
8339 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
8340 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
8341 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
8342 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
8343 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
8344 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
8345 libxalan2-java libxerces2-java media-player-info mesa-utils
8346 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
8347 nautilus-sendto-empathy openoffice.org-writer2latex
8348 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
8349 python-aptdaemon python-aptdaemon-gtk python-axiom
8350 python-beautifulsoup python-bugbuddy python-clientform
8351 python-coherence python-configobj python-crypto python-cupshelpers
8352 python-cupsutils python-eggtrayicon python-elementtree
8353 python-epsilon python-evolution python-feedparser python-gdata
8354 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8355 python-gtksourceview2 python-httplib2 python-louie python-mako
8356 python-markupsafe python-mechanize python-nevow python-notify
8357 python-opengl python-openssl python-pam python-pkg-resources
8358 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8359 python-tagpy python-twisted-bin python-twisted-conch
8360 python-twisted-core python-twisted-web python-utidylib python-webkit
8361 python-xdg python-zope.interface remmina remmina-plugin-data
8362 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8363 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8364 software-center svgalibg1 system-config-printer-udev
8365 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
8366 totem totem-coherence totem-mozilla totem-plugins
8367 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8368 zip
8369 &lt;/p&gt;&lt;/blockquote&gt;
8370
8371 Installed using apt-get, removed with aptitude
8372
8373 &lt;blockquote&gt;&lt;p&gt;
8374 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8375 epiphany-extensions epiphany-gecko evolution-exchange
8376 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8377 gedit-common gnome-app-install gnome-games gnome-games-data
8378 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8379 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8380 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8381 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
8382 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
8383 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
8384 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
8385 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
8386 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
8387 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
8388 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
8389 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
8390 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8391 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8392 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8393 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8394 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
8395 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
8396 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
8397 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
8398 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
8399 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8400 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8401 sound-juicer swfdec-gnome system-config-printer totem-common
8402 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8403 &lt;/p&gt;&lt;/blockquote&gt;
8404
8405 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8406
8407 &lt;blockquote&gt;&lt;p&gt;
8408 gstreamer0.10-gnomevfs
8409 &lt;/p&gt;&lt;/blockquote&gt;
8410
8411 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8412
8413 &lt;blockquote&gt;&lt;p&gt;
8414 [nothing]
8415 &lt;/p&gt;&lt;/blockquote&gt;
8416
8417 &lt;p&gt;This is for KDE:&lt;/p&gt;
8418
8419 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8420
8421 &lt;blockquote&gt;&lt;p&gt;
8422 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
8423 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8424 ghostscript-x git gnome-audio gnugo granatier gs-common
8425 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8426 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8427 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8428 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8429 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8430 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8431 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8432 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8433 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8434 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8435 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8436 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
8437 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8438 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8439 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8440 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8441 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8442 libkrossui4 libmailtools-perl libmime-tools-perl
8443 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8444 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8445 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8446 lirc luatex marble networkstatus noatun-plugins
8447 openoffice.org-writer2latex palapeli palapeli-data parley
8448 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8449 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8450 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8451 ttf-sazanami-gothic
8452 &lt;/p&gt;&lt;/blockquote&gt;
8453
8454 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8455
8456 &lt;blockquote&gt;&lt;p&gt;
8457 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8458 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8459 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8460 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8461 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8462 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8463 kitchensync kiten kjumpingcube klatin klettres klickety klines
8464 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8465 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8466 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8467 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8468 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8469 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8470 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8471 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8472 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8473 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
8474 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
8475 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8476 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
8477 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
8478 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8479 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8480 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8481 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8482 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8483 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8484 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
8485 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
8486 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8487 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8488 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8489 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8490 &lt;/p&gt;&lt;/blockquote&gt;
8491
8492 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8493
8494 &lt;blockquote&gt;&lt;p&gt;
8495 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8496 kdeartwork kdebase kdebase-apps kdebase-workspace
8497 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8498 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8499 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8500 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8501 xscreensaver-screensaver-bsod
8502 &lt;/p&gt;&lt;/blockquote&gt;
8503
8504 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8505
8506 &lt;blockquote&gt;&lt;p&gt;
8507 kdebase-bin konq-plugins konqueror
8508 &lt;/p&gt;&lt;/blockquote&gt;
8509 </description>
8510 </item>
8511
8512 <item>
8513 <title>Gnash buildbot slave and Debian kfreebsd</title>
8514 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
8515 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
8516 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
8517 <description>&lt;p&gt;Answering
8518 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
8519 call from the Gnash project&lt;/a&gt; for
8520 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
8521 current source, I have set up a virtual KVM machine on the Debian
8522 Edu/Skolelinux virtualization host to test the git source on
8523 Debian/Squeeze. I hope this can help the developers in getting new
8524 releases out more often.&lt;/p&gt;
8525
8526 &lt;p&gt;As the developers want less main-stream build platforms tested to,
8527 I have considered setting up a &lt;a
8528 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
8529 machine as well. I have also considered using the kfreebsd
8530 architecture in Debian as a file server in NUUG to get access to the 5
8531 TB zfs volume we currently use to store DV video. Because of this, I
8532 finally got around to do a test installation of Debian/Squeeze with
8533 kfreebsd. Installation went fairly smooth, thought I noticed some
8534 visual glitches in the cdebconf dialogs (black cursor left on the
8535 screen at random locations). Have not gotten very far with the
8536 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8537 fatal problem. Have to spend some more time on it to see if it is
8538 useful as a file server for NUUG. Will try to find time to set up a
8539 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
8540 </description>
8541 </item>
8542
8543 <item>
8544 <title>Debian in 3D</title>
8545 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
8546 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
8547 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
8548 <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;
8549
8550 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
8551 3D linked in from
8552 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
8553 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
8554 </description>
8555 </item>
8556
8557 <item>
8558 <title>Software updates 2010-10-24</title>
8559 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
8560 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
8561 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
8562 <description>&lt;p&gt;Some updates.&lt;/p&gt;
8563
8564 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
8565 raise money for the project is going well. The lower limit of 10
8566 signers was reached in 24 hours, and so far 13 people have signed it.
8567 More signers and more funding is most welcome, and I am really curious
8568 how far we can get before the time limit of December 24 is reached.
8569 :)&lt;/p&gt;
8570
8571 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
8572 about what appear to be a great code coverage tool capable of
8573 generating code coverage stats without any changes to the source code.
8574 It is called
8575 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
8576 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
8577 It is missing in Debian, but the git source built just fine in Squeeze
8578 after I installed libelf-dev, libdwarf-dev, pkg-config and
8579 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8580 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
8581
8582 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
8583 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
8584 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
8585 alpha test release of the Squeeze based Debian Edu /
8586 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
8587 release. Give it a try if you need a complete linux solution for your
8588 school, including central infrastructure server, workstations, thin
8589 client servers and diskless workstations. A nice touch added
8590 yesterday is RDP support on the thin client servers, for windows
8591 clients to get a Linux desktop on request.&lt;/p&gt;
8592 </description>
8593 </item>
8594
8595 <item>
8596 <title>Some notes on Flash in Debian and Debian Edu</title>
8597 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
8598 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
8599 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
8600 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
8601 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
8602 second most popular used package that is missing in Debian. The sixth
8603 most popular is flashplayer-mozilla. This is a clear indication that
8604 working flash is important for Debian users. Around 10 percent of the
8605 users submitting data to popcon.debian.org have this package
8606 installed.&lt;/p&gt;
8607
8608 &lt;p&gt;In the report written by Lars Risan in August 2008
8609&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
8610 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8611 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
8612 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
8613 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
8614 web sites require Flash to work, and lacking working Flash support in
8615 the web browser and the problems with installing it was perceived as a
8616 good reason to stay with Windows.&lt;/p&gt;
8617
8618 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
8619 said to be the retarded cousin that did not really understand
8620 everything you told him but could work fairly well. This was a
8621 comment regarding the problems Linux have with proprietary formats and
8622 non-standard web pages, and is sad because it exposes a fairly common
8623 understanding of whose fault it is if web pages that only work in for
8624 example Internet Explorer 6 fail to work on Firefox, and funny because
8625 it explain very well how annoying it is for users when Linux
8626 distributions do not work with the documents they receive or the web
8627 pages they want to visit.&lt;/p&gt;
8628
8629 &lt;p&gt;This is part of the reason why I believe it is important for Debian
8630 and Debian Edu to have a well working Flash implementation in the
8631 distribution, to get at least popular sites as Youtube and Google
8632 Video to working out of the box. For Squeeze, Debian have the chance
8633 to include the latest version of Gnash that will make this happen, as
8634 the new release 0.8.8 was published a few weeks ago and is resting in
8635 unstable. The new version work with more sites that version 0.8.7.
8636 The Gnash maintainers have asked for a freeze exception, but the
8637 release team have not had time to reply to it yet. I hope they agree
8638 with me that Flash is important for the Debian desktop users, and thus
8639 accept the new package into Squeeze.&lt;/p&gt;
8640 </description>
8641 </item>
8642
8643 <item>
8644 <title>Circular package dependencies harms apt recovery</title>
8645 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
8646 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
8647 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
8648 <description>&lt;p&gt;I discovered this while doing
8649 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
8650 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
8651 in Debian still got circular dependencies, and it is often claimed
8652 that apt and aptitude should be able to handle this just fine, but
8653 some times these dependency loops causes apt to fail.&lt;/p&gt;
8654
8655 &lt;p&gt;An example is from todays
8656 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
8657 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
8658 causes perl-modules to fail to upgrade. The cause is simple. If a
8659 package fail to unpack, then only part of packages with the circular
8660 dependency might end up being unpacked when unpacking aborts, and the
8661 ones already unpacked will fail to configure in the recovery phase
8662 because its dependencies are unavailable.&lt;/p&gt;
8663
8664 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
8665
8666 &lt;blockquote&gt;&lt;pre&gt;
8667 dpkg: dependency problems prevent configuration of perl-modules:
8668 perl-modules depends on perl (&gt;= 5.10.1-1); however:
8669 Version of perl on system is 5.10.0-19lenny2.
8670 dpkg: error processing perl-modules (--configure):
8671 dependency problems - leaving unconfigured
8672 &lt;/pre&gt;&lt;/blockquote&gt;
8673
8674 &lt;p&gt;The perl/perl-modules circular dependency is already
8675 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
8676 hopefully be solved as soon as possible, but it is not the only one,
8677 and each one of these loops in the dependency tree can cause similar
8678 failures. Of course, they only occur when there are bugs in other
8679 packages causing the unpacking to fail, but it is rather nasty when
8680 the failure of one package causes the problem to become worse because
8681 of dependency loops.&lt;/p&gt;
8682
8683 &lt;p&gt;Thanks to
8684 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
8685 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
8686 dependencies
8687 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
8688 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
8689
8690 &lt;p&gt;Todays testing also exposed a bug in
8691 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
8692 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
8693 apt-get and aptitude, the latter possibly caused by some circular
8694 dependency. Reported both to BTS to try to get someone to look at
8695 it.&lt;/p&gt;
8696 </description>
8697 </item>
8698
8699 <item>
8700 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
8701 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
8702 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
8703 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
8704 <description>&lt;p&gt;This is a
8705 &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;
8706 on my
8707 &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
8708 work&lt;/a&gt; on
8709 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
8710 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
8711
8712 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
8713 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8714 and dhcp3-server-ldap in Debian use the LDAP server. The two
8715 implementations are quite different in how they use LDAP.&lt;/p&gt;
8716
8717 To get this information, I started slapd with debugging enabled and
8718 dumped the debug output to a file to get the LDAP searches performed
8719 on a Debian Edu main-server. Here is a summary.
8720
8721 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
8722
8723 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
8724 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
8725 the web.
8726
8727 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
8728 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
8729 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
8730 reverse entries are in two different subtrees in LDAP with a structure
8731 based on the DNS names, as in tjener.intern and
8732 2.2.0.10.in-addr.arpa.&lt;/p&gt;
8733
8734 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
8735 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
8736 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
8737 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
8738 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
8739 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
8740 forward entries, it is looking for attributes named dnsttl, arecord,
8741 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8742 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8743 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8744 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8745 spfrecord and modifytimestamp. For reverse entries it is looking for
8746 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8747 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8748 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8749 ldapsearch commands could look like this:&lt;/p&gt;
8750
8751 &lt;blockquote&gt;&lt;pre&gt;
8752 ldapsearch -h ldap \
8753 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8754 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
8755 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8756 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8757 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8758 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8759
8760 ldapsearch -h ldap \
8761 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8762 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
8763 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8764 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8765 srvrecord naptrrecord modifytimestamp
8766 &lt;/pre&gt;&lt;/blockquote&gt;
8767
8768 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
8769 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8770 example LDAP objects used there. In addition to these objects, the
8771 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8772 also exist.&lt;/p&gt;
8773
8774 &lt;blockquote&gt;&lt;pre&gt;
8775 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8776 objectclass: top
8777 objectclass: dnsdomain
8778 objectclass: domainrelatedobject
8779 dc: tjener
8780 arecord: 10.0.2.2
8781 associateddomain: tjener.intern
8782
8783 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8784 objectclass: top
8785 objectclass: dnsdomain2
8786 objectclass: domainrelatedobject
8787 dc: 2
8788 ptrrecord: tjener.intern
8789 associateddomain: 2.2.0.10.in-addr.arpa
8790 &lt;/pre&gt;&lt;/blockquote&gt;
8791
8792 &lt;p&gt;In strict mode, the server behaves differently. When looking for
8793 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
8794 same base as in the tree mode for a object with filter
8795 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
8796 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8797 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8798 naptrrecord and modifytimestamp. For reverse entires it also do a
8799 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
8800 and the requested attributes are associateddomain, dnsttl and
8801 modifytimestamp. In short, in strict mode the objects with ptrrecord
8802 go away, and the arecord attribute in the forward object is used
8803 instead.&lt;/p&gt;
8804
8805 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
8806 like this:&lt;/p&gt;
8807
8808 &lt;blockquote&gt;&lt;pre&gt;
8809 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8810 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
8811 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8812 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8813 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8814 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8815
8816 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8817 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
8818 &lt;/pre&gt;&lt;/blockquote&gt;
8819
8820 &lt;p&gt;In addition to the forward and reverse searches , there is also a
8821 search for SOA records, which behave similar to the forward and
8822 reverse lookups.&lt;/p&gt;
8823
8824 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
8825 specify any objectclass names, and instead look for the attributes it
8826 need to generate a DNS reply. This make it able to work with any
8827 objectclass that provide the needed attributes.&lt;/p&gt;
8828
8829 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
8830 dnsdomain2 schemas. The latter is used for reverse entries like
8831 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
8832
8833 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
8834 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8835 attributes) and domainrelatedobject (for associatedDomain). The use
8836 of structural object classes make it impossible to combine these
8837 classes with the object classes used by DHCP.&lt;/p&gt;
8838
8839 &lt;p&gt;There are other schemas that could be used too, for example the
8840 dnszone structural object class used by Gosa and bind-sdb for the DNS
8841 attributes combined with the domainrelatedobject object class, but in
8842 this case some unused attributes would have to be included as well
8843 (zonename and relativedomainname).&lt;/p&gt;
8844
8845 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
8846 mode and not use any of the existing objectclasses (dnsdomain,
8847 dnsdomain2 and dnszone) when one want to combine the DNS information
8848 with DHCP information, and instead create a auxiliary object class
8849 defined something like this (using the attributes defined for
8850 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
8851
8852 &lt;blockquote&gt;&lt;pre&gt;
8853 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
8854 SUP top
8855 AUXILIARY
8856 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8857 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8858 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8859 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8860 A6Record $ DNAMERecord
8861 ))
8862 &lt;/pre&gt;&lt;/blockquote&gt;
8863
8864 &lt;p&gt;This will allow any object to become a DNS entry when combined with
8865 the domainrelatedobject object class, and allow any entity to include
8866 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
8867 developers asking for their view on this schema and if they are
8868 interested in providing such schema with PowerDNS, and I hope my
8869 message will be accepted into their mailing list soon.&lt;/p&gt;
8870
8871 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
8872
8873 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
8874 the object attributes, and then uses the attributes it want. This
8875 make it harder to figure out exactly what attributes are used, but
8876 thanks to the working example in Debian Edu I can at least get an idea
8877 what is needed without having to read the source code.&lt;/p&gt;
8878
8879 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
8880 search filter to use to locate the correct dhcpServer entity is
8881 stored. These are the relevant entries from
8882 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
8883
8884 &lt;blockquote&gt;&lt;pre&gt;
8885 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
8886 ldap-dhcp-server-cn &quot;dhcp&quot;;
8887 &lt;/pre&gt;&lt;/blockquote&gt;
8888
8889 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
8890 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
8891 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
8892 search result is this entry:&lt;/p&gt;
8893
8894 &lt;blockquote&gt;&lt;pre&gt;
8895 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8896 cn: dhcp
8897 objectClass: top
8898 objectClass: dhcpServer
8899 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8900 &lt;/pre&gt;&lt;/blockquote&gt;
8901
8902 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
8903 subtree with DHCP configuration. The DHCP configuration subtree base
8904 is located using a base scope search with base &quot;cn=DHCP
8905 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
8906 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
8907 The search result is this entry:&lt;/p&gt;
8908
8909 &lt;blockquote&gt;&lt;pre&gt;
8910 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8911 cn: DHCP Config
8912 objectClass: top
8913 objectClass: dhcpService
8914 objectClass: dhcpOptions
8915 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8916 dhcpStatements: ddns-update-style none
8917 dhcpStatements: authoritative
8918 dhcpOption: smtp-server code 69 = array of ip-address
8919 dhcpOption: www-server code 72 = array of ip-address
8920 dhcpOption: wpad-url code 252 = text
8921 &lt;/pre&gt;&lt;/blockquote&gt;
8922
8923 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
8924 all the DHCP configuration is loaded, it is ready to receive requests.
8925 The subtree in Debian Edu contain objects with object classes
8926 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8927 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8928 and information about netmasks, dynamic range etc. Leaving out the
8929 details here because it is not relevant for the focus of my
8930 investigation, which is to see if it is possible to merge dns and dhcp
8931 related computer objects.&lt;/p&gt;
8932
8933 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
8934 of the client (00:00:00:00:00:00 in this example), using a subtree
8935 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
8936 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8937 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
8938 like:&lt;/p&gt;
8939
8940 &lt;blockquote&gt;&lt;pre&gt;
8941 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8942 cn: hostname
8943 objectClass: top
8944 objectClass: dhcpHost
8945 dhcpHWAddress: ethernet 00:00:00:00:00:00
8946 dhcpStatements: fixed-address hostname
8947 &lt;/pre&gt;&lt;/blockquote&gt;
8948
8949 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
8950 The object classes need to have fixed names, and the configuration
8951 need to be stored in a fairly specific LDAP structure. On the
8952 positive side, the invidiual dhcpHost entires can be anywhere without
8953 the DN pointed to by the dhcpServer entries. The latter should make
8954 it possible to group all host entries in a subtree next to the
8955 configuration entries, and this subtree can also be shared with the
8956 DNS server if the schema proposed above is combined with the dhcpHost
8957 structural object class.
8958
8959 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
8960
8961 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
8962 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
8963 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
8964 allowing DNS objects to be stored anywhere under the base cn specified
8965 in the configuration.&lt;/p&gt;
8966
8967 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
8968 regarding which LDAP schemas to use and which LDAP structure to use.
8969 I guess one could implement ones own schema, as long as the
8970 objectclasses and attributes have the names used, but this do not
8971 really help when the DHCP subtree need to have a fairly fixed
8972 structure.&lt;/p&gt;
8973
8974 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
8975 this might work for Debian Edu:&lt;/p&gt;
8976
8977 &lt;blockquote&gt;&lt;pre&gt;
8978 ou=services
8979 cn=machine-info (dhcpService) - dhcpServiceDN points here
8980 cn=dhcp (dhcpServer)
8981 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8982 cn=10.0.2.0 (dhcpSubnet)
8983 cn=group1 (dhcpGroup/dhcpOptions)
8984 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8985 cn=192.168.0.0 (dhcpSubnet)
8986 cn=group1 (dhcpGroup/dhcpOptions)
8987 ou=machines - PowerDNS base points here
8988 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8989 &lt;/pre&gt;&lt;/blockquote&gt;
8990
8991 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
8992 entries to be in the dhcpGroup subtrees, the entries can be stored
8993 there instead of a common machines subtree, and the PowerDNS base
8994 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
8995
8996 &lt;p&gt;The combined object under the machines subtree would look something
8997 like this:&lt;/p&gt;
8998
8999 &lt;blockquote&gt;&lt;pre&gt;
9000 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9001 dc: hostname
9002 objectClass: top
9003 objectClass: dhcpHost
9004 objectclass: domainrelatedobject
9005 objectclass: dnsDomainAux
9006 associateddomain: hostname.intern
9007 arecord: 10.11.12.13
9008 dhcpHWAddress: ethernet 00:00:00:00:00:00
9009 dhcpStatements: fixed-address hostname.intern
9010 &lt;/pre&gt;&lt;/blockquote&gt;
9011
9012 &lt;/p&gt;One could even add the LTSP configuration associated with a given
9013 machine, as long as the required attributes are available in a
9014 auxiliary object class.&lt;/p&gt;
9015 </description>
9016 </item>
9017
9018 <item>
9019 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
9020 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
9021 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
9022 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
9023 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
9024 DHCP services in Debian Edu to use the same LDAP objects for a given
9025 computer, to avoid the possibility of having a inconsistent state for
9026 a computer in LDAP (as in DHCP but no DNS entry or the other way
9027 around) and make it easier to add computers to LDAP.&lt;/p&gt;
9028
9029 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
9030 information finally found a solution that seem to work.&lt;/p&gt;
9031
9032 &lt;p&gt;The old setup required three LDAP objects for a given computer.
9033 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9034 we switch powerdns to use its strict LDAP method (ldap-method=strict
9035 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9036 merged into one while making it impossible to transfer the reverse map
9037 to a slave DNS server.&lt;/p&gt;
9038
9039 &lt;p&gt;If we also replace the object class used to get the DNS related
9040 attributes to one allowing these attributes to be combined with the
9041 dhcphost object class, we can merge the DNS and DHCP entries into one.
9042 I&#39;ve written such object class in the dnsdomainaux.schema file (need
9043 proper OIDs, but that is a minor issue), and tested the setup. It
9044 seem to work.&lt;/p&gt;
9045
9046 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
9047 for both DNS and DHCP, and even the LTSP configuration I suggested in
9048 an earlier email. The combined LDAP object will look something like
9049 this:&lt;/p&gt;
9050
9051 &lt;blockquote&gt;&lt;pre&gt;
9052 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9053 cn: hostname
9054 objectClass: dhcphost
9055 objectclass: domainrelatedobject
9056 objectclass: dnsdomainaux
9057 associateddomain: hostname.intern
9058 arecord: 10.11.12.13
9059 dhcphwaddress: ethernet 00:00:00:00:00:00
9060 dhcpstatements: fixed-address hostname
9061 ldapconfigsound: Y
9062 &lt;/pre&gt;&lt;/blockquote&gt;
9063
9064 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
9065 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9066 before asking DNS to resolve the fixed-adddress. LTSP will use
9067 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
9068
9069 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
9070 dhcphost in a different location, to allow us to put the objects
9071 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
9072 that. If I can&#39;t figure out a way to do that, we can still get rid of
9073 the hosts subtree and move all its content into the DHCP Config tree
9074 (which probably should be renamed to be more related to the new
9075 content. I suspect cn=dnsdhcp,ou=services or something like that
9076 might be a good place to put it.&lt;/p&gt;
9077
9078 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
9079 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9080 </description>
9081 </item>
9082
9083 <item>
9084 <title>Idea for storing LTSP configuration in LDAP</title>
9085 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
9086 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
9087 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
9088 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
9089 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9090 clients, and that this can be used to fetch configuration from LDAP if
9091 Debian Edu choose to store configuration there.&lt;/p&gt;
9092
9093 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
9094 to get configuration from LDAP. The idea is to look up the MAC
9095 address of the client in LDAP, and look for attributes on the form
9096 ltspconfigsetting=value, and use this to export SETTING=value to the
9097 LTSP clients.&lt;/p&gt;
9098
9099 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
9100 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
9101 allowing us to store all information about a computer in one place.&lt;/p&gt;
9102
9103 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
9104 this approach. A real LDAP schema for the ltspClientAux objectclass
9105 need to be written. Comments, suggestions, etc?&lt;/p&gt;
9106
9107 &lt;blockquote&gt;&lt;pre&gt;
9108 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9109 #
9110 # Fetch LTSP client settings from LDAP based on MAC address
9111 #
9112 # Uses ethernet address as stored in the dhcpHost objectclass using
9113 # the dhcpHWAddress attribute or ethernet address stored in the
9114 # ieee802Device objectclass with the macAddress attribute.
9115 #
9116 # This module is written to be schema agnostic, and only depend on the
9117 # existence of attribute names.
9118 #
9119 # The LTSP configuration variables are saved directly using a
9120 # ltspConfig prefix and uppercasing the rest of the attribute name.
9121 # To set the SERVER variable, set the ltspConfigServer attribute.
9122 #
9123 # Some LDAP schema should be created with all the relevant
9124 # configuration settings. Something like this should work:
9125 #
9126 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
9127 # SUP top
9128 # AUXILIARY
9129 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9130
9131 LDAPSERVER=$(debian-edu-ldapserver)
9132 if [ &quot;$LDAPSERVER&quot; ] ; then
9133 LDAPBASE=$(debian-edu-ldapserver -b)
9134 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
9135 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
9136 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
9137 grep &#39;^ltspConfig&#39; | while read attr value ; do
9138 # Remove prefix and convert to upper case
9139 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
9140 # bass value on to clients
9141 eval &quot;$attr=$value; export $attr&quot;
9142 done
9143 done
9144 fi
9145 &lt;/pre&gt;&lt;/blockquote&gt;
9146
9147 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
9148 the while block might end up in a subshell causing the variables set
9149 there to not show up in ltsp-config, but if that is the case I am sure
9150 the code can be restructured to make sure the variables are passed on.
9151 I expect that can be solved with some testing. :)&lt;/p&gt;
9152
9153 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
9154 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9155
9156 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
9157 configuration in LDAP that was created around year 2000 by
9158 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
9159 Xperience, Inc., 2000&lt;/a&gt;. I found its
9160 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
9161 personal home page over at redhat.com.&lt;/p&gt;
9162 </description>
9163 </item>
9164
9165 <item>
9166 <title>jXplorer, a very nice LDAP GUI</title>
9167 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
9168 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
9169 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
9170 <description>&lt;p&gt;Since
9171 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
9172 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
9173 LDAP GUI that is even better than luma. The java application
9174 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
9175 moving LDAP objects and subtrees using drag-and-drop, and can
9176 authenticate using Kerberos. I have only tested the Kerberos
9177 authentication, but do not have a LDAP setup allowing me to rewrite
9178 LDAP with my test user yet. It is
9179 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
9180 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
9181 have with it is how it handle errors. If something go wrong, its
9182 non-intuitive behaviour require me to go through some query work list
9183 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
9184 </description>
9185 </item>
9186
9187 <item>
9188 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
9189 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
9190 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
9191 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
9192 <description>&lt;p&gt;Here is a short update on my &lt;a
9193 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
9194 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
9195 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
9196 not reporting the status for KDE, because the upgrade crashes when
9197 aptitude try because of missing conflicts
9198 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
9199 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
9200
9201 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
9202 complete list of the installed packages. Based on this I see these
9203 differences when I did a test run today. As usual, I do not really
9204 know what the correct set of packages would be, but thought it best to
9205 publish the difference.&lt;/p&gt;
9206
9207 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9208
9209 &lt;blockquote&gt;&lt;p&gt;
9210 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
9211 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
9212 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9213 libgtksourceview-common libpt-1.10.10-plugins-alsa
9214 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9215 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9216 python-4suite-xml python-eggtrayicon python-gtkhtml2
9217 python-gtkmozembed svgalibg1 xserver-xephyr zip
9218 &lt;/p&gt;&lt;/blockquote&gt;
9219
9220 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9221
9222 &lt;blockquote&gt;&lt;p&gt;
9223 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9224 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9225 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
9226 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
9227 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
9228 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
9229 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
9230 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
9231 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
9232 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
9233 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
9234 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
9235 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9236 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
9237 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9238 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
9239 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
9240 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9241 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9242 mysql-common swfdec-gnome totem-gstreamer wodim
9243 &lt;/p&gt;&lt;/blockquote&gt;
9244
9245 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9246
9247 &lt;blockquote&gt;&lt;p&gt;
9248 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9249 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9250 xserver-xorg-input-all xserver-xorg-input-evdev
9251 xserver-xorg-input-kbd xserver-xorg-input-mouse
9252 xserver-xorg-input-synaptics xserver-xorg-video-all
9253 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9254 xserver-xorg-video-chips xserver-xorg-video-cirrus
9255 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9256 xserver-xorg-video-glint xserver-xorg-video-i128
9257 xserver-xorg-video-i740 xserver-xorg-video-mach64
9258 xserver-xorg-video-mga xserver-xorg-video-neomagic
9259 xserver-xorg-video-nouveau xserver-xorg-video-nv
9260 xserver-xorg-video-r128 xserver-xorg-video-radeon
9261 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9262 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9263 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9264 xserver-xorg-video-sis xserver-xorg-video-sisusb
9265 xserver-xorg-video-tdfx xserver-xorg-video-tga
9266 xserver-xorg-video-trident xserver-xorg-video-tseng
9267 xserver-xorg-video-vesa xserver-xorg-video-vmware
9268 xserver-xorg-video-voodoo
9269 &lt;/p&gt;&lt;/blockquote&gt;
9270
9271 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9272
9273 &lt;blockquote&gt;&lt;p&gt;
9274 deskbar-applet xserver-xorg xserver-xorg-core
9275 xserver-xorg-input-wacom xserver-xorg-video-intel
9276 xserver-xorg-video-openchrome
9277 &lt;/p&gt;&lt;/blockquote&gt;
9278
9279 &lt;p&gt;I was told on IRC that the xorg-xserver package was
9280 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
9281 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
9282 No idea when it hits Squeeze, but when it does I hope it will reduce
9283 the difference somewhat.
9284 </description>
9285 </item>
9286
9287 <item>
9288 <title>LUMA, a very nice LDAP GUI</title>
9289 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
9290 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
9291 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
9292 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
9293 directory in Debian Edu, and in the process I started to miss a GUI
9294 tool to browse the LDAP tree. The only one I was able to find in
9295 Debian/Squeeze and Lenny is
9296 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
9297 be a great tool to get a overview of the current LDAP directory
9298 populated by default in Skolelinux. Thanks to it, I have been able to
9299 find empty and obsolete subtrees, misplaced objects and duplicate
9300 objects. It will be installed by default in Debian/Squeeze. If you
9301 are working with LDAP, give it a go. :)&lt;/p&gt;
9302
9303 &lt;p&gt;I did notice one problem with it I have not had time to report to
9304 the BTS yet. There is no .desktop file in the package, so the tool do
9305 not show up in the Gnome and KDE menus, but only deep down in in the
9306 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9307 released.&lt;/p&gt;
9308
9309 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
9310 like to move objects and remove subtrees directly in the GUI, but have
9311 not found a way to do that with LUMA yet. So in the mean time, I use
9312 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
9313
9314 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
9315 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9316
9317 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
9318 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
9319 useful GUI alternative. It seem like a good tool, but is unmaintained
9320 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9321 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
9322 </description>
9323 </item>
9324
9325 <item>
9326 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
9327 <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>
9328 <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>
9329 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
9330 <description>&lt;p&gt;A while back, I
9331 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
9332 about the fact&lt;/a&gt; that it is not possible with the provided schemas
9333 for storing DNS and DHCP information in LDAP to combine the two sets
9334 of information into one LDAP object representing a computer.&lt;/p&gt;
9335
9336 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
9337 the dhcpHost object class auxiliary, to allow it to be combined with
9338 the dNSDomain object class, and thus forming one object for one
9339 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
9340
9341 &lt;p&gt;If I understand this correctly, it is not safe to do this change
9342 without also changing the assigned number for the object class, and I
9343 do not know enough about LDAP schema design to do that properly for
9344 Debian Edu.&lt;/p&gt;
9345
9346 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
9347 the
9348 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
9349 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
9350 available today from IETF.&lt;/p&gt;
9351
9352 &lt;pre&gt;
9353 --- dhcp.schema (revision 65192)
9354 +++ dhcp.schema (working copy)
9355 @@ -376,7 +376,7 @@
9356 objectclass ( 2.16.840.1.113719.1.203.6.6
9357 NAME &#39;dhcpHost&#39;
9358 DESC &#39;This represents information about a particular client&#39;
9359 - SUP top
9360 + SUP top AUXILIARY
9361 MUST cn
9362 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9363 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
9364 &lt;/pre&gt;
9365
9366 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
9367 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9368 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
9369
9370 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
9371 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9372 </description>
9373 </item>
9374
9375 <item>
9376 <title>Calling tasksel like the installer, while still getting useful output</title>
9377 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
9378 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
9379 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
9380 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
9381 installs packages during the normal debian-installer run. Until now,
9382 I have ended up letting tasksel do the work, with the annoying problem
9383 of not getting any feedback at all when something fails (like a
9384 conffile question from dpkg or a download that fails), using code like
9385 this:
9386
9387 &lt;blockquote&gt;&lt;pre&gt;
9388 export DEBIAN_FRONTEND=noninteractive
9389 tasksel --new-install
9390 &lt;/pre&gt;&lt;/blockquote&gt;
9391
9392 This would invoke tasksel, let its automatic task selection pick the
9393 tasks to install, and continue to install the requested tasks without
9394 any output what so ever.
9395
9396 Recently I revisited this problem while working on the automatic
9397 package upgrade testing, because tasksel would some times hang without
9398 any useful feedback, and I want to see what is going on when it
9399 happen. Then it occured to me, I can parse the output from tasksel
9400 when asked to run in test mode, and use that aptitude command line
9401 printed by tasksel then to simulate the tasksel run. I ended up using
9402 code like this:
9403
9404 &lt;blockquote&gt;&lt;pre&gt;
9405 export DEBIAN_FRONTEND=noninteractive
9406 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
9407 $cmd
9408 &lt;/pre&gt;&lt;/blockquote&gt;
9409
9410 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
9411 --without-recommends -o APT::Install-Recommends=no -y install
9412 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9413 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
9414 laptop task and all packages with priority standard , required and
9415 important, just like tasksel would have done it during
9416 installation.&lt;/p&gt;
9417
9418 &lt;p&gt;A better approach is probably to extend tasksel to be able to
9419 install packages without using debconf-apt-progress, for use cases
9420 like this.&lt;/p&gt;
9421 </description>
9422 </item>
9423
9424 <item>
9425 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
9426 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
9427 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
9428 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
9429 <description>&lt;p&gt;My
9430 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
9431 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
9432 finally made the upgrade logs available from
9433 &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;.
9434 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9435 apt and aptitude, and found their differences interesting. This time
9436 I will only focus on their removal plans.&lt;/p&gt;
9437
9438 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
9439 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
9440 surprising part is that it want to remove xorg and all
9441 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9442 sure why. When asking aptitude to do the same, it want to remove 129
9443 packages, but most of them are library packages I suspect are no
9444 longer needed. Both of them want to remove bluetooth packages, which
9445 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
9446
9447 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
9448 which seem like a bad idea and xorg the same way as with Gnome. Asking
9449 aptitude for the same, it wants to remove 192 packages, none which are
9450 too surprising.&lt;/p&gt;
9451
9452 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
9453 and avoided, and perhaps others as well. Here are the complete list
9454 of planned removals. The complete logs is available from the URL
9455 above. Note if you want to repeat these tests, that the upgrade test
9456 for kde+apt-get hung in the tasksel setup because of dpkg asking
9457 conffile questions. No idea why. I worked around it by using
9458 &#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
9459 continue.&lt;/p&gt;
9460
9461 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
9462 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
9463 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9464 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
9465 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9466 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9467 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9468 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9469 xserver-xorg-input-kbd xserver-xorg-input-mouse
9470 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9471 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9472 xserver-xorg-video-ati xserver-xorg-video-chips
9473 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9474 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9475 xserver-xorg-video-glint xserver-xorg-video-i128
9476 xserver-xorg-video-i740 xserver-xorg-video-imstt
9477 xserver-xorg-video-intel xserver-xorg-video-mach64
9478 xserver-xorg-video-mga xserver-xorg-video-neomagic
9479 xserver-xorg-video-nsc xserver-xorg-video-nv
9480 xserver-xorg-video-openchrome xserver-xorg-video-r128
9481 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9482 xserver-xorg-video-rendition xserver-xorg-video-s3
9483 xserver-xorg-video-s3virge xserver-xorg-video-savage
9484 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9485 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9486 xserver-xorg-video-tga xserver-xorg-video-trident
9487 xserver-xorg-video-tseng xserver-xorg-video-v4l
9488 xserver-xorg-video-vesa xserver-xorg-video-vga
9489 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
9490 xulrunner-1.9-gnome-support&lt;/p&gt;
9491
9492 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
9493
9494 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
9495 djvulibre-desktop finger gnome-app-install gnome-mount
9496 gnome-network-admin gnome-spell gnome-vfs-obexftp
9497 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9498 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9499 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9500 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
9501 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
9502 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
9503 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
9504 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
9505 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
9506 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
9507 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
9508 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
9509 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9510 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
9511 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
9512 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
9513 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
9514 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
9515 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9516 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9517 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9518 openoffice.org-writer2latex openssl-blacklist p7zip
9519 python-4suite-xml python-eggtrayicon python-gnome2-desktop
9520 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9521 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9522 swfdec-mozilla totem-gstreamer update-manager wodim
9523 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9524 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9525 zip&lt;/p&gt;
9526
9527 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
9528
9529 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9530 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9531 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9532 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9533 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9534 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9535 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9536 xserver-xorg-input-kbd xserver-xorg-input-mouse
9537 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9538 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9539 xserver-xorg-video-ati xserver-xorg-video-chips
9540 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9541 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9542 xserver-xorg-video-glint xserver-xorg-video-i128
9543 xserver-xorg-video-i740 xserver-xorg-video-imstt
9544 xserver-xorg-video-intel xserver-xorg-video-mach64
9545 xserver-xorg-video-mga xserver-xorg-video-neomagic
9546 xserver-xorg-video-nsc xserver-xorg-video-nv
9547 xserver-xorg-video-openchrome xserver-xorg-video-r128
9548 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9549 xserver-xorg-video-rendition xserver-xorg-video-s3
9550 xserver-xorg-video-s3virge xserver-xorg-video-savage
9551 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9552 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9553 xserver-xorg-video-tga xserver-xorg-video-trident
9554 xserver-xorg-video-tseng xserver-xorg-video-v4l
9555 xserver-xorg-video-vesa xserver-xorg-video-vga
9556 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
9557
9558 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
9559 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
9560 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9561 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9562 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9563 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9564 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9565 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9566 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9567 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9568 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9569 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9570 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9571 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9572 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9573 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9574 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9575 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9576 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9577 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
9578 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9579 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9580 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
9581 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9582 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9583 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9584 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9585 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9586 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
9587 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
9588 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9589 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9590 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9591 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9592 texlive-common texlive-doc-base texlive-fonts-recommended
9593 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9594 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9595 xulrunner-1.9&lt;/p&gt;
9596
9597 </description>
9598 </item>
9599
9600 <item>
9601 <title>Automatic upgrade testing from Lenny to Squeeze</title>
9602 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
9603 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
9604 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
9605 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
9606 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9607 have been discovered and reported in the process
9608 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
9609 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
9610 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
9611 kdebase-workspace-data), and to get a more regular testing going on, I
9612 am working on a script to automate the test.&lt;/p&gt;
9613
9614 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
9615 Gnome or KDE desktop installation inside the chroot before upgrading
9616 it. To ensure no services are started in the chroot, a policy-rc.d
9617 script is inserted. To make sure tasksel believe it is to install a
9618 desktop on a laptop, the tasksel tests are replaced in the chroot
9619 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
9620
9621 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9622 currently always fail because udev refuses to upgrade with the kernel
9623 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9624 is created. The bug report
9625 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
9626 this problem do not trigger in a chroot, but I touch the file anyway
9627 to make sure the upgrade go well. Testing on virtual and real
9628 hardware have failed me because of udev so far, and creating this file
9629 do the trick in such settings anyway. This is a
9630 &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
9631 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
9632 maintainer because he lack the resources to rewrite udev to keep
9633 working with old kernels or something like that. I really wish the
9634 udev upstream would keep udev backwards compatible, to avoid such
9635 upgrade problem, but given that they fail to do so, I guess
9636 documenting the way out of this mess is the best option we got for
9637 Debian Squeeze.&lt;/p&gt;
9638
9639 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
9640 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
9641 trick:&lt;/p&gt;
9642
9643 &lt;blockquote&gt;&lt;pre&gt;
9644 #!/bin/sh
9645 set -ex
9646
9647 if [ &quot;$1&quot; ] ; then
9648 desktop=$1
9649 else
9650 desktop=gnome
9651 fi
9652
9653 from=lenny
9654 to=squeeze
9655
9656 exec &amp;lt; /dev/null
9657 unset LANG
9658 mirror=http://ftp.skolelinux.org/debian
9659 tmpdir=chroot-$from-upgrade-$to-$desktop
9660 fuser -mv .
9661 debootstrap $from $tmpdir $mirror
9662 chroot $tmpdir aptitude update
9663 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
9664 #!/bin/sh
9665 exit 101
9666 EOF
9667 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9668 exit_cleanup() {
9669 umount $tmpdir/proc
9670 }
9671 mount -t proc proc $tmpdir/proc
9672 # Make sure proc is unmounted also on failure
9673 trap exit_cleanup EXIT INT
9674
9675 chroot $tmpdir aptitude -y install debconf-utils
9676
9677 # Make sure tasksel autoselection trigger. It need the test scripts
9678 # to return the correct answers.
9679 echo tasksel tasksel/desktop multiselect $desktop | \
9680 chroot $tmpdir debconf-set-selections
9681
9682 # Include the desktop and laptop task
9683 for test in desktop laptop ; do
9684 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
9685 #!/bin/sh
9686 exit 2
9687 EOF
9688 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9689 done
9690
9691 DEBIAN_FRONTEND=noninteractive
9692 DEBIAN_PRIORITY=critical
9693 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9694 chroot $tmpdir tasksel --new-install
9695
9696 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
9697 chroot $tmpdir aptitude update
9698 touch $tmpdir/etc/udev/kernel-upgrade
9699 chroot $tmpdir aptitude -y dist-upgrade
9700 fuser -mv
9701 &lt;/pre&gt;&lt;/blockquote&gt;
9702
9703 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
9704 with aptitude, but I have not had time to look at how they behave
9705 differently so far. I hope to get a cron job running to do the test
9706 regularly and post the result on the web. The Gnome upgrade currently
9707 work, while the KDE upgrade fail because of the bug in
9708 kdebase-workspace-data&lt;/p&gt;
9709
9710 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
9711 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
9712 post, so I will refrain from trying. I can report that for Gnome,
9713 aptitude report 760 packages upgraded, 448 newly installed, 129 to
9714 remove and 1 not upgraded and 1024MB need to be downloaded while for
9715 KDE the same numbers are 702 packages upgraded, 507 newly installed,
9716 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
9717
9718 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
9719 is able to migrate to dependency based boot sequencing and parallel
9720 booting without a hitch. Was unsure if there were still bugs with
9721 packages failing to clean up their obsolete init.d script during
9722 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9723 packages.&lt;/p&gt;
9724 </description>
9725 </item>
9726
9727 <item>
9728 <title>Upstart or sysvinit - as init.d scripts see it</title>
9729 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
9730 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
9731 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
9732 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
9733 scripts to migrate (some of) their operations to upstart job while
9734 keeping the init.d for hurd and kfreebsd. The packages with such
9735 needs will need a way to get their init.d scripts to behave
9736 differently when used with sysvinit and with upstart. Because of
9737 this, I had a look at the environment variables set when a init.d
9738 script is running under upstart, and when it is not.&lt;/p&gt;
9739
9740 &lt;p&gt;With upstart, I notice these environment variables are set when a
9741 script is started from rcS.d/ (ignoring some irrelevant ones like
9742 COLUMNS):&lt;/p&gt;
9743
9744 &lt;blockquote&gt;&lt;pre&gt;
9745 DEFAULT_RUNLEVEL=2
9746 previous=N
9747 PREVLEVEL=
9748 RUNLEVEL=
9749 runlevel=S
9750 UPSTART_EVENTS=startup
9751 UPSTART_INSTANCE=
9752 UPSTART_JOB=rc-sysinit
9753 &lt;/pre&gt;&lt;/blockquote&gt;
9754
9755 &lt;p&gt;With sysvinit, these environment variables are set for the same
9756 script.&lt;/p&gt;
9757
9758 &lt;blockquote&gt;&lt;pre&gt;
9759 INIT_VERSION=sysvinit-2.88
9760 previous=N
9761 PREVLEVEL=N
9762 RUNLEVEL=S
9763 runlevel=S
9764 &lt;/pre&gt;&lt;/blockquote&gt;
9765
9766 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
9767 sysvinit are not set by upstart. Not sure if it is intentional or not
9768 to not be compatible with sysvinit in this regard.&lt;/p&gt;
9769
9770 &lt;p&gt;For scripts needing to behave differently when upstart is used,
9771 looking for the UPSTART_JOB environment variable seem to be a good
9772 choice.&lt;/p&gt;
9773 </description>
9774 </item>
9775
9776 <item>
9777 <title>A manual for standards wars...</title>
9778 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
9779 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
9780 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
9781 <description>&lt;p&gt;Via the
9782 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
9783 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
9784 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
9785 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
9786 following the standards wars of today.&lt;/p&gt;
9787 </description>
9788 </item>
9789
9790 <item>
9791 <title>Sitesummary tip: Listing computer hardware models used at site</title>
9792 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
9793 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
9794 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
9795 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
9796 to get a list of the machine types in use thanks to the DMI
9797 information extracted from each machine. The script to do so is
9798 included in the sitesummary package, and here is example output from
9799 the Skolelinux build servers:&lt;/p&gt;
9800
9801 &lt;blockquote&gt;&lt;pre&gt;
9802 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9803 vendor count
9804 Dell Computer Corporation 1
9805 PowerEdge 1750 1
9806 IBM 1
9807 eserver xSeries 345 -[8670M1X]- 1
9808 Intel 2
9809 [no-dmi-info] 3
9810 maintainer:~#
9811 &lt;/pre&gt;&lt;/blockquote&gt;
9812
9813 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
9814 provided in each machine. Here there are Intel machines without model
9815 information listed with Intel as vendor and no model, and virtual Xen
9816 machines listed as [no-dmi-info]. One can add -l as a command line
9817 option to list the individual machines.&lt;/p&gt;
9818
9819 &lt;p&gt;A larger list is
9820 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
9821 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
9822 provide the basic sitesummary report publicly. In their report there
9823 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
9824 their machines, and as sitesummary is available in both distributions,
9825 it is trivial to get all of them to report to the same central
9826 collector.&lt;/p&gt;
9827 </description>
9828 </item>
9829
9830 <item>
9831 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
9832 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
9833 <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>
9834 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
9835 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
9836 start at boot when an NVidia video card is used is handled. The
9837 problem seem to be that the nvidia X.org driver uses a long time to
9838 initialize, and this duration is longer than kdm is configured to
9839 wait.&lt;/p&gt;
9840
9841 &lt;p&gt;I came across two bugs related to this issue,
9842 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
9843 against initscripts and passed on to nvidia-glx when it became obvious
9844 that the nvidia drivers were involved, and
9845 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
9846 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
9847
9848 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
9849 problem nvidia video card owners experience and make sure the Debian
9850 distribution work out of the box for these users. The nvidia driver
9851 maintainers expect kdm to be set up to wait longer, while kdm expect
9852 the nvidia driver maintainers to fix the driver to start faster, and
9853 while they wait for each other I guess the users end up switching to a
9854 distribution that work for them. I have no idea what the solution is,
9855 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
9856
9857 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
9858 </description>
9859 </item>
9860
9861 <item>
9862 <title>Parallellized boot seem to hold up well in Debian/testing</title>
9863 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
9864 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
9865 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
9866 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
9867 The feature seem to hold up pretty well, but three fairly serious
9868 issues are known and should be solved:
9869
9870 &lt;p&gt;&lt;ul&gt;
9871
9872 &lt;li&gt;The wicd package seen to
9873 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
9874 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
9875 parallel booting is enabled. No idea why, but the wicd maintainer
9876 seem to be on the case.&lt;/li&gt;
9877
9878 &lt;li&gt;The nvidia X driver seem to
9879 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
9880 triggered more easily when parallel booting is in effect. The
9881 maintainer is on the case.&lt;/li&gt;
9882
9883 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
9884 sequencing (the shutdown is broken) when old file-rc users
9885 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
9886 sysv-rc. One way to solve it would be for file-rc to create
9887 /etc/init.d/.legacy-bootordering, and another is to try to make
9888 sysv-rc more robust. Will investigate some more and probably upload a
9889 workaround in sysv-rc to help those trying to move from file-rc to
9890 sysv-rc get a working shutdown.&lt;/li&gt;
9891
9892 &lt;/ul&gt;&lt;/p&gt;
9893
9894 &lt;p&gt;All in all not many surprising issues, and all of them seem
9895 solvable before Squeeze is released. In addition to these there are
9896 some packages with bugs in their dependencies and run level settings,
9897 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
9898
9899 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9900 the BTS, please usertag the report to get it to show up at
9901 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9902 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9903
9904 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
9905 </description>
9906 </item>
9907
9908 <item>
9909 <title>More flexible firmware handling in debian-installer</title>
9910 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
9911 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
9912 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
9913 <description>&lt;p&gt;After a long break from debian-installer development, I finally
9914 found time today to return to the project. Having to spend less time
9915 working dependency based boot in debian, as it is almost complete now,
9916 definitely helped freeing some time.&lt;/p&gt;
9917
9918 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
9919 include some firmware packages on the Debian Edu CDs, those needed to
9920 get disk and network controllers working. Without having these
9921 firmware packages available during installation, it is impossible to
9922 install Debian Edu on the given machine, and because our target group
9923 are non-technical people, asking them to provide firmware packages on
9924 an external medium is a support pain. Initially, I expected it to be
9925 enough to include the firmware packages on the CD to get
9926 debian-installer to find and use them. This proved to be wrong.
9927 Next, I hoped it was enough to symlink the relevant firmware packages
9928 to some useful location on the CD (tried /cdrom/ and
9929 /cdrom/firmware/). This also proved to not work, and at this point I
9930 found time to look at the debian-installer code to figure out what was
9931 going to work.&lt;/p&gt;
9932
9933 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
9934 look revealed that it would only look for firmware packages outside
9935 the installation media, so the CD was never checked for firmware
9936 packages. It would only check USB sticks, floppies and other
9937 &quot;external&quot; media devices. Today I changed it to also look in the
9938 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9939 solve the problem I ran into with Debian edu. I also changed it to
9940 look in /firmware/, to make sure the installer also find firmware
9941 provided in the initrd when booting the installer via PXE, to allow us
9942 to provide the same feature in the PXE setup included in Debian
9943 Edu.&lt;/p&gt;
9944
9945 &lt;p&gt;To make sure firmware deb packages with a license questions are not
9946 activated without asking if the license is accepted, I extended
9947 hw-detect to look for preinst scripts in the firmware packages, and
9948 run these before activating the firmware during installation. The
9949 license question is asked using debconf in the preinst, so this should
9950 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
9951
9952 &lt;p&gt;If you want to discuss the details of these features, please
9953 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
9954 </description>
9955 </item>
9956
9957 <item>
9958 <title>Parallellized boot is now the default in Debian/unstable</title>
9959 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
9960 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
9961 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
9962 <description>&lt;p&gt;Since this evening, parallel booting is the default in
9963 Debian/unstable for machines using dependency based boot sequencing.
9964 Apparently the testing of concurrent booting has been wider than
9965 expected, if I am to believe the
9966 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
9967 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
9968 with the feature this weekend, to give us some time to detect any
9969 remaining problems before Squeeze is frozen. If serious problems are
9970 detected, it is simple to change the default back to sequential boot.
9971 The upload of the new sysvinit package also activate a new upstream
9972 version.&lt;/p&gt;
9973
9974 More information about
9975 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
9976 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
9977 currently possible to disable parallel booting when one run into
9978 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
9979
9980 &lt;blockquote&gt;&lt;pre&gt;
9981 CONCURRENCY=none
9982 &lt;/pre&gt;&lt;/blockquote&gt;
9983
9984 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
9985 the BTS, please usertag the report to get it to show up at
9986 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
9987 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
9988 </description>
9989 </item>
9990
9991 <item>
9992 <title>Sitesummary tip: Listing MAC address of all clients</title>
9993 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
9994 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
9995 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
9996 <description>&lt;p&gt;In the recent Debian Edu versions, the
9997 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
9998 system&lt;/a&gt; is used to keep track of the machines in the school
9999 network. Each machine will automatically report its status to the
10000 central server after boot and once per night. The network setup is
10001 also reported, and using this information it is possible to get the
10002 MAC address of all network interfaces in the machines. This is useful
10003 to update the DHCP configuration.&lt;/p&gt;
10004
10005 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
10006 ist all MAC addresses of all machines reporting to sitesummary. Run
10007 this on the collector host:&lt;/p&gt;
10008
10009 &lt;blockquote&gt;&lt;pre&gt;
10010 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
10011 &lt;/pre&gt;&lt;/blockquote&gt;
10012
10013 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
10014 line per machine and with space between the MAC addresses.&lt;/p&gt;
10015
10016 &lt;p&gt;To allow system administrators easier job at adding static DHCP
10017 addresses for hosts, it would be possible to extend this to fetch
10018 machine information from sitesummary and update the DHCP and DNS
10019 tables in LDAP using this information. Such tool is unfortunately not
10020 written yet.&lt;/p&gt;
10021 </description>
10022 </item>
10023
10024 <item>
10025 <title>systemd, an interesting alternative to upstart</title>
10026 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
10027 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
10028 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
10029 <description>&lt;p&gt;The last few days a new boot system called
10030 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
10031 has been
10032 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
10033
10034 to the free software world. I have not yet had time to play around
10035 with it, but it seem to be a very interesting alternative to
10036 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
10037 a good alternative for Debian when we are able to switch to an event
10038 based boot system. Tollef is
10039 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
10040 systemd into Debian, and I look forward to seeing how well it work. I
10041 like the fact that systemd handles init.d scripts with dependency
10042 information natively, allowing them to run in parallel where upstart
10043 at the moment do not.&lt;/p&gt;
10044
10045 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
10046 platform support. It only work on recent Linux kernels, and also need
10047 some new kernel features enabled to function properly. This means
10048 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10049 system. Not sure how that will be handled if systemd proves to be the
10050 way forward.&lt;/p&gt;
10051
10052 &lt;p&gt;In the mean time, based on the
10053 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
10054 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
10055 decided to enable full parallel booting as the default in Debian as
10056 soon as possible (probably this weekend or early next week), to see if
10057 there are any remaining serious bugs in the init.d dependencies. A
10058 new version of the sysvinit package implementing this change is
10059 already in experimental. If all go well, Squeeze will be released
10060 with parallel booting enabled by default.&lt;/p&gt;
10061 </description>
10062 </item>
10063
10064 <item>
10065 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
10066 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
10067 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
10068 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
10069 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
10070 complete, so complete that it is actually possible to run all the
10071 init.d scripts in parallell based on these dependencies. If you want
10072 to test your Squeeze system, make sure
10073 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
10074 based boot sequencing&lt;/a&gt; is enabled, and add this line to
10075 /etc/default/rcS:&lt;/p&gt;
10076
10077 &lt;blockquote&gt;&lt;pre&gt;
10078 CONCURRENCY=makefile
10079 &lt;/pre&gt;&lt;/blockquote&gt;
10080
10081 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
10082 scripts in parallel using the dependency information stored in
10083 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10084 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10085 to try to start the kdm and gdm scripts as early as possible, and will
10086 start the facilities required by kdm or gdm as early as possible to
10087 make this happen.&lt;/p&gt;
10088
10089 &lt;p&gt;Give it a try, and see if you like the result. If some services
10090 fail to start properly, it is most likely because they have incomplete
10091 init.d script dependencies in their startup script (or some of their
10092 dependent scripts have incomplete dependencies). Report bugs and get
10093 the package maintainers to fix it. :)&lt;/p&gt;
10094
10095 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
10096 manage to get the init.d script dependencies complete and correct. I
10097 expect we will get there in Squeeze+1, if we get manage to test and
10098 fix the remaining issues.&lt;/p&gt;
10099
10100 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10101 the BTS, please usertag the report to get it to show up at
10102 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10103 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10104 </description>
10105 </item>
10106
10107 <item>
10108 <title>Debian has switched to dependency based boot sequencing</title>
10109 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
10110 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
10111 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
10112 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
10113 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
10114 have been migrated to using dependency based boot sequencing. This
10115 conclude work me and others have been doing for the last three days.
10116 It feels great to see this finally part of the default Debian
10117 installation. Now we just need to weed out the last few problems that
10118 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
10119
10120 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
10121 fixing the more fundamental problem of handing the event based
10122 non-predictable kernel in the early boot.&lt;/p&gt;
10123 </description>
10124 </item>
10125
10126 <item>
10127 <title>Taking over sysvinit development</title>
10128 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
10129 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
10130 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
10131 <description>&lt;p&gt;After several years of frustration with the lack of activity from
10132 the existing sysvinit upstream developer, I decided a few weeks ago to
10133 take over the package and become the new upstream. The number of
10134 patches to track for the Debian package was becoming a burden, and the
10135 lack of synchronization between the distribution made it hard to keep
10136 the package up to date.&lt;/p&gt;
10137
10138 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10139 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
10140 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
10141 and Fedora), based on the patches currently in use in these
10142 distributions. We Debian maintainers plan to move to this tarball as
10143 the new upstream as soon as we find time to do the merge. Since the
10144 new tarball was created, we agreed with Werner at SuSe to make a new
10145 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
10146 development there. The project is registered and currently waiting
10147 for approval by the Savannah administrators, and as soon as it is
10148 approved, we will import the old versions from svn and continue
10149 working on the future release.&lt;/p&gt;
10150
10151 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
10152 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
10153 </description>
10154 </item>
10155
10156 <item>
10157 <title>Debian boots quicker and quicker</title>
10158 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
10159 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
10160 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
10161 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
10162 people involved in the boot system on Debian and Ubuntu, to see if we
10163 could find more ways to speed up the boot system. This was an Ubuntu
10164 funded
10165 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
10166 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
10167 of boot systems, and ways to handle the increasing number of boot
10168 issues introduced by the Linux kernel becoming more and more
10169 asynchronous and event base. The Ubuntu approach using udev and
10170 upstart might be a good way forward. Time will show.&lt;/p&gt;
10171
10172 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
10173 process in Debian. All of these should be applied to get a quick
10174 boot:&lt;/p&gt;
10175
10176 &lt;ul&gt;
10177
10178 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
10179
10180 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
10181 clock is in UTC.&lt;/li&gt;
10182
10183 &lt;li&gt;Install and activate the insserv package to enable
10184 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
10185 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
10186
10187 &lt;/ul&gt;
10188
10189 These points are based on the Google summer of code work done by
10190 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
10191 Villegas&lt;/a&gt;.
10192
10193 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
10194 unstable yesterday. When we tested it, we were able to cut 6 seconds
10195 from the boot sequence. It depend on very correct dependency
10196 declaration in all init.d scripts, so I expect us to find edge cases
10197 where the dependences in some scripts are slightly wrong when we start
10198 using this.&lt;/p&gt;
10199
10200 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10201 introduced by Raphael Geissert today, one that could affect the
10202 startup speed as well. Instead of starting some scripts concurrently
10203 from rcS.d/ and another set of scripts from rc2.d/, it would be
10204 possible to run a of them in the same process. A quick way to test
10205 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
10206 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
10207 </description>
10208 </item>
10209
10210 <item>
10211 <title>BSAs påstander om piratkopiering møter motstand</title>
10212 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
10213 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
10214 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
10215 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
10216 programvareselskapene som Microsoft og Apple, publisert en rapport der
10217 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10218 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10219 dager siden kom
10220 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
10221 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
10222 dagene. Et spesielt interessant kommentar fra Sverige,
10223 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
10224 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
10225
10226 &lt;blockquote&gt;
10227 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
10228 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10229 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
10230 exakta&quot;, säger BSAs Sverigechef John Hugosson.
10231 &lt;/blockquote&gt;
10232
10233 &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
10234 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
10235 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
10236 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
10237 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
10238
10239 &lt;p&gt;Fant lenkene via &lt;a
10240 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
10241 på Slashdot&lt;/a&gt;.&lt;/p&gt;
10242 </description>
10243 </item>
10244
10245 <item>
10246 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
10247 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
10248 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
10249 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
10250 <description>&lt;p&gt;Kom over
10251 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
10252 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10253 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10254 jobber til daglig. En rask opptelling forteller meg at vi har 490
10255 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
10256 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
10257 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
10258 </description>
10259 </item>
10260
10261 <item>
10262 <title>Kryptert harddisk - naturligvis</title>
10263 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
10264 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
10265 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
10266 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
10267 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
10268 når en tar tap av arbeidstid, fortrolige dokumenter,
10269 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10270 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10271 til at jeg har kryptert harddisken på både kontormaskinen og min
10272 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10273 komme på avveie, den første informasjon relatert til jobben min ved
10274 Universitetet i Oslo, og den andre relatert til blant annet
10275 foreningsarbeide. Kryptering av diskene gjør at det er lite
10276 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10277 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10278 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10279 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10280 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10281 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10282 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10283 det er gjort slik jeg gjør det er minimale, og gevinstene er
10284 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10285 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
10286
10287 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10288 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10289 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10290 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10291 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10292 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10293 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10294 betydelige.&lt;/p&gt;
10295 </description>
10296 </item>
10297
10298 <item>
10299 <title>Two projects that have improved the quality of free software a lot</title>
10300 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
10301 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
10302 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
10303 <description>&lt;p&gt;There are two software projects that have had huge influence on the
10304 quality of free software, and I wanted to mention both in case someone
10305 do not yet know them.&lt;/p&gt;
10306
10307 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
10308 tool to detect and expose errors in the memory handling of programs.
10309 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
10310 and it will report any problems on stdout. It is even better if the
10311 program include debug information. With debug information, it is able
10312 to report the source file name and line number where the problem
10313 occurs. It can report things like &#39;reading past memory block in file
10314 X line N, the memory block was allocated in file Y, line M&#39;, and
10315 &#39;using uninitialised value in control logic&#39;. This tool has made it
10316 trivial to investigate reproducible crash bugs in programs, and have
10317 reduced the number of this kind of bugs in free software a lot.
10318
10319 &lt;p&gt;The second one is
10320 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
10321 a source code checker. It is able to process the source of a program
10322 and find problems in the logic without running the program. It
10323 started out as the Stanford Checker and became well known when it was
10324 used to find bugs in the Linux kernel. It is now a commercial tool
10325 and the company behind it is running
10326 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
10327 free software community, where a lot of free software projects get
10328 their source checked for free. Several thousand defects have been
10329 found and fixed so far. It can find errors like &#39;lock L taken in file
10330 X line N is never released if exiting in line M&#39;, or &#39;the code in file
10331 Y lines O to P can never be executed&#39;. The projects included in the
10332 community service project have managed to get rid of a lot of
10333 reliability problems thanks to Coverity.&lt;/p&gt;
10334
10335 &lt;p&gt;I believe tools like this, that are able to automatically find
10336 errors in the source, are vital to improve the quality of software and
10337 make sure we can get rid of the crashing and failing software we are
10338 surrounded by today.&lt;/p&gt;
10339 </description>
10340 </item>
10341
10342 <item>
10343 <title>No patch is not better than a useless patch</title>
10344 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
10345 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
10346 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
10347 <description>&lt;p&gt;Julien Blache
10348 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
10349 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
10350 patch allow one to discuss a concrete and proposed solution, and also
10351 prove that the issue at hand is important enough for someone to spent
10352 time on fixing it. No patch do not provide any of these positive
10353 properties.&lt;/p&gt;
10354 </description>
10355 </item>
10356
10357 <item>
10358 <title>Standardize on protocols and formats, not vendors and applications</title>
10359 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
10360 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
10361 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
10362 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
10363 very good one to form a long lived computer infrastructure. It is the
10364 simple one, lost by many in todays computer industry: Standardize on
10365 open network protocols and open exchange/storage formats, not applications.
10366 Applications come and go, while protocols and files tend to stay, and
10367 thus one want to make it easy to change application and vendor, while
10368 avoiding conversion costs and locking users to a specific platform or
10369 application.&lt;/p&gt;
10370
10371 &lt;p&gt;This approach make it possible to replace the client applications
10372 independently of the server applications. One can even allow users to
10373 use several different applications as long as they handle the selected
10374 protocol and format. In the normal case, only one client application
10375 is recommended and users only get help if they choose to use this
10376 application, but those that want to deviate from the easy path are not
10377 blocked from doing so.&lt;/p&gt;
10378
10379 &lt;p&gt;It also allow us to replace the server side without forcing the
10380 users to replace their applications, and thus allow us to select the
10381 best server implementation at any moment, when scale and resouce
10382 requirements change.&lt;/p&gt;
10383
10384 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
10385 open formats, but I would never recommend standardizing on a single
10386 application that do not use open network protocol or open formats.&lt;/p&gt;
10387 </description>
10388 </item>
10389
10390 <item>
10391 <title>Returning from Skolelinux developer gathering</title>
10392 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
10393 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
10394 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
10395 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
10396 Edu/Skolelinux development gathering. I got a bit done tuning the
10397 desktop, and looked into the dynamic service location protocol
10398 implementation avahi. It look like it could be useful for us. Almost
10399 30 people participated, and I believe it was a great environment to
10400 get to know the Skolelinux system. Walter Bender, involved in the
10401 development of the Sugar educational platform, presented his stuff and
10402 also helped me improve my OLPC installation. He also showed me that
10403 his Turtle Art application can be used in standalone mode, and we
10404 agreed that I would help getting it packaged for Debian. As a
10405 standalone application it would be great for Debian Edu. We also
10406 tried to get the video conferencing working with two OLPCs, but that
10407 proved to be too hard for us. The application seem to need more work
10408 before it is ready for me. I look forward to getting home and relax
10409 now. :)&lt;/p&gt;
10410 </description>
10411 </item>
10412
10413 <item>
10414 <title>Time for new LDAP schemas replacing RFC 2307?</title>
10415 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
10416 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
10417 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
10418 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
10419 optimal. There is RFC 2307 documenting one way to store NIS maps in
10420 LDAP, and a modified version of this normally called RFC 2307bis, with
10421 some modifications to be compatible with Active Directory. The RFC
10422 specification handle the content of a lot of system databases, but do
10423 not handle DNS zones and DHCP configuration.&lt;/p&gt;
10424
10425 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
10426 we would like to store information about users, SMB clients/hosts,
10427 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10428 and LTSP configuration in LDAP. These objects have a lot in common,
10429 but with the current LDAP schemas it is not possible to have one
10430 object per entity. For example, one need to have at least three LDAP
10431 objects for a given computer, one with the SMB related stuff, one with
10432 DNS information and another with DHCP information. The schemas
10433 provided for DNS and DHCP are impossible to combine into one LDAP
10434 object. In addition, it is impossible to implement quick queries for
10435 netgroup membership, because of the way NIS triples are implemented.
10436 It just do not scale. I believe it is time for a few RFC
10437 specifications to cleam up this mess.&lt;/p&gt;
10438
10439 &lt;p&gt;I would like to have one LDAP object representing each computer in
10440 the network, and this object can then keep the SMB (ie host key), DHCP
10441 (mac address/name) and DNS (name/IP address) settings in one place.
10442 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
10443
10444 &lt;p&gt;I would also like to have a quick way to map from a user or
10445 computer and to the net group this user or computer is a member.&lt;/p&gt;
10446
10447 &lt;p&gt;Active Directory have done a better job than unix heads like myself
10448 in this regard, and the unix side need to catch up. Time to start a
10449 new IETF work group?&lt;/p&gt;
10450 </description>
10451 </item>
10452
10453 <item>
10454 <title>Endelig er Debian Lenny gitt ut</title>
10455 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
10456 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
10457 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
10458 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
10459 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
10460 Et langt steg videre for Debian-prosjektet, og en rekke nye
10461 programpakker blir nå tilgjengelig for de av oss som bruker den
10462 stabile utgaven av Debian. Neste steg er nå å få
10463 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
10464 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
10465 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10466 slippes løs på skolene. Takk til alle debian-utviklerne som har
10467 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10468 bootsekvens tilgjengelig i stabil utgave, vha pakken
10469 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
10470 </description>
10471 </item>
10472
10473 <item>
10474 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
10475 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
10476 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
10477 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
10478 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
10479 Oslo. Most of Saturday was used for the general assemly for the
10480 member organization, but the rest of the weekend I used to tune the
10481 LTSP installation. LTSP now work out of the box on the 10-network.
10482 Acer Aspire One proved to be a very nice thin client, with both
10483 screen, mouse and keybard in a small box. Was working on getting the
10484 diskless workstation setup configured out of the box, but did not
10485 finish it before the weekend was up.&lt;/p&gt;
10486
10487 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
10488 the Brazilian group, so that will have to wait for the next
10489 development gathering. Would love to have the Debian Edu installer
10490 automatically detect and configure a multiseat setup when it find one
10491 of these cards.&lt;/p&gt;
10492 </description>
10493 </item>
10494
10495 <item>
10496 <title>The sorry state of multimedia browser plugins in Debian</title>
10497 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
10498 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
10499 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
10500 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
10501 plugins available in Debian Lenny, to see which one we should use by
10502 default in Debian Edu. We need an embedded video playing plugin with
10503 control buttons to pause or stop the video, and capable of streaming
10504 all the multimedia content available on the web. The test results and
10505 notes are available on
10506 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
10507 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
10508 fill this need. My personal video player favorite, VLC, has a really
10509 bad plugin which fail on a lot of the test pages. A lot of the MIME
10510 types I would expect to work with any free software player (like
10511 video/ogg), just do not work. And simple formats like the
10512 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
10513 totem and vlc plugins. I hope the situation will improve soon. No
10514 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
10515
10516 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
10517 be the only one fitting our needs. :/&lt;/p&gt;
10518 </description>
10519 </item>
10520
10521 </channel>
10522 </rss>