]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
a6b7840306e66c234f34bea4ee9bcc440fcc125e
[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>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
11 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
13 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
14 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
15 mobile cell towers. And this radio chatter is available for anyone
16 with a radio receiver capable of receiving them. Details about the
17 mobile phones with very good accuracy is of course collected by the
18 phone companies, but this is not the topic of this blog post. The
19 mobile phone radio chatter make it possible to figure out when a cell
20 phone is nearby, as it include the SIM card ID (IMSI). By paying
21 attention over time, one can see when a phone arrive and when it leave
22 an area. I believe it would be nice to make this information more
23 available to the general public, to make more people aware of how
24 their phones are announcing their whereabouts to anyone that care to
25 listen.&lt;/p&gt;
26
27 &lt;p&gt;I am very happy to report that we managed to get something
28 visualizing this information up and running for
29 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
30 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
31 library. The solution is based on the
32 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
33 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
34 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
35 Sone from the Computer Science department of the University of
36 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
37 IMSIs) as dots in a web browser graph, with lines to the dot
38 representing mobile base station it is talking to. It was working in
39 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
40
41 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
42 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
43 connected and visualize the visible cell phone towers using an
44 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
45 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
46 grgsm_livemon_headless processes from
47 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
48 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
49
50 &lt;p&gt;The frequencies to listen to, are identified using a slightly
51 patched scan-and-livemon (to set the --args values for each receiver),
52 and the Hopglass data is generated using the
53 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
54 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
55 more than four SDRs working. There is also a geographical map trying
56 to show the location of the base stations, but I believe their
57 coordinates are hardcoded to some random location in Germany, I
58 believe. The code should be replaced with code to look up location in
59 a text file, a sqlite database or one of the online databases
60 mentioned in
61 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
62 issue for the topic&lt;/a&gt;.
63
64 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
65 </description>
66 </item>
67
68 <item>
69 <title>Easier recipe to observe the cell phones around you</title>
70 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
71 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
72 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
73 <description>&lt;p&gt;A little more than a month ago I wrote
74 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html&quot;&gt;how
75 to observe the SIM card ID (aka IMSI number) of mobile phones talking
76 to nearby mobile phone base stations using Debian GNU/Linux and a
77 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
78 the location of people and equipment (like cars and trains) with an
79 accuracy of a few kilometer. Since then we have worked to make the
80 procedure even simpler, and it is now possible to do this without any
81 manual frequency tuning and without building your own packages.&lt;/p&gt;
82
83 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
84 package is now included in Debian testing and unstable, and the
85 IMSI-catcher code no longer require root access to fetch and decode
86 the GSM data collected using gr-gsm.&lt;/p&gt;
87
88 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
89 clone of two python scripts:&lt;/p&gt;
90
91 &lt;ol&gt;
92
93 &lt;li&gt;Start with a Debian machine running the Buster version (aka
94 testing).&lt;/li&gt;
95
96 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
97 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
98
99 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
100 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
101
102 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
103
104 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
105 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
106 stations and start listening for GSM packages on one of them.&lt;/li&gt;
107
108 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
109 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
110
111 &lt;/ol&gt;
112
113 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
114 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
115 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
116 work with RTL 8232 and other similar USB radio receivers you can get
117 very cheaply
118 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
119 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
120 and only use HackRF for fetching GSM data.&lt;/p&gt;
121
122 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
123 frequencies at the time, so if you are going to track and count every
124 cell phone around you, you need to listen to all the frequencies used.
125 To listen to several frequencies, use the --numrecv argument to
126 scan-and-livemon to use several receivers. Further, I am not sure if
127 phones using 3G or 4G will show as talking GSM to base stations, so
128 this approach might not see all phones around you. I typically see
129 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
130
131 &lt;p&gt;I&#39;ve tried to run the scanner on a
132 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
133 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
134 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
135 stdout, I am told there it is caused by a buffer overflow between the
136 radio and GNU Radio, caused by the program being unable to read the
137 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
138 where you started scan-and-livemon, you need a give the process more
139 CPU power. Perhaps someone are able to optimize the code to a point
140 where it become possible to set up RPi3 based GSM sniffers? I tried
141 using Raspbian instead of Debian, but there seem to be something wrong
142 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
143 </description>
144 </item>
145
146 <item>
147 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
148 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
149 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
150 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
151 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
152 web based ICT news magazine digi.no on
153 &lt;a href=&quot;https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-60-kroner-na-kan-mobiler-kartlegges-av-alle/398588&quot;&gt;how
154 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
155 DVB-T software defined radios. The article refered to instructions
156 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
157 Keld Norman on Youtube on how to make a simple $7 IMSI Catcher&lt;/a&gt;, and I decided to test them out.&lt;/p&gt;
158
159 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
160 bypass apt), use pip to install pybombs (to bypass both apt and pip),
161 and the ask pybombs to fetch and build everything you need from
162 scratch. I wanted to see if I could do the same on the most recent
163 Debian packages, but this did not work because pybombs tried to build
164 stuff that no longer build with the most recent openssl library or
165 some other version skew problem. While trying to get this recipe
166 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
167 and the only piece of software dependency missing in Debian was the
168 gr-gsm package. I also found out that the lead upstream developer of
169 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
170 Debian packages provided in an Ubuntu PPA repository. All I needed to
171 do was to dget the Debian source package and built it.&lt;/p&gt;
172
173 &lt;p&gt;The IMSI collector is a python script listening for packages on the
174 loopback network device and printing to the terminal some specific GSM
175 packages with IMSI numbers in them. The code is fairly short and easy
176 to understand. The reason this work is because gr-gsm include a tool
177 to read GSM data from a software defined radio like a DVB-T USB stick
178 and other software defined radios, decode them and inject them into a
179 network device on your Linux machine (using the loopback device by
180 default). This proved to work just fine, and I&#39;ve been testing the
181 collector for a few days now.&lt;/p&gt;
182
183 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
184
185 &lt;ol&gt;
186
187 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
188
189 &lt;li&gt;build and install the gr-gsm package available from
190 &lt;a href=&quot;http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/&quot;&gt;http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/&lt;/a&gt;,&lt;/li&gt;
191
192 &lt;li&gt;clone the git repostory from &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher&quot;&gt;https://github.com/Oros42/IMSI-catcher&lt;/a&gt;,&lt;/li&gt;
193
194 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
195 where it was started is filled with a stream of text (meaning you
196 found a GSM station).&lt;/li&gt;
197
198 &lt;li&gt;go into the IMSI-catcher directory and run &#39;sudo python simple_IMSI-catcher.py&#39; to extract the IMSI numbers.&lt;/li&gt;
199
200 &lt;/ol&gt;
201
202 &lt;p&gt;To make it even easier in the future to get this sniffer up and
203 running, I decided to package
204 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
205 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
206 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
207 Luckily the gnuradio maintainer has promised to help me, as I do not
208 know much about gnuradio stuff yet.&lt;/p&gt;
209
210 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
211 commercial tools like
212 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
213 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
214 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
215 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
216 more people realise how their whereabouts when carrying a cell phone
217 is easily tracked. Seeing the data flow on the screen, realizing that
218 I live close to a police station and knowing that the police is also
219 wearing cell phones, I wonder how hard it would be for criminals to
220 track the position of the police officers to discover when there are
221 police near by, or for foreign military forces to track the location
222 of the Norwegian military forces, or for anyone to track the location
223 of government officials...&lt;/p&gt;
224
225 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
226 script mentioned above is only a fraction of the data broadcasted on
227 the GSM network. It will only collect one frequency at the time,
228 while a typical phone will be using several frequencies, and not all
229 phones will be using the frequencies tracked by the grgsm_livemod
230 program. Also, there is a lot of radio chatter being ignored by the
231 simple_IMSI-catcher script, which would be collected by extending the
232 parser code. I wonder if gr-gsm can be set up to listen to more than
233 one frequency?&lt;/p&gt;
234 </description>
235 </item>
236
237 <item>
238 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
239 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
240 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
241 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
242 <description>&lt;p align=&quot;center&quot;&gt;&lt;img align=&quot;center&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-07-25-debian-handbook-nb-testprint.png&quot;/&gt;&lt;/p&gt;
243
244 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
245 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
246 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
247 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
248 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
249 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
250 price. The book is also available for download in electronic form as
251 PDF, EPUB and Mobipocket, as can be
252 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
253 as a web page&lt;/a&gt;.&lt;/p&gt;
254
255 &lt;p&gt;This is the second book I publish (the first was the book
256 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
257 in
258 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
259 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
260 and
261 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
262 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
263 project. I hope
264 &quot;&lt;a href=&quot;http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-23262290.html&quot;&gt;Håndbok
265 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
266 </description>
267 </item>
268
269 <item>
270 <title>Når nynorskoversettelsen svikter til eksamen...</title>
271 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
272 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
273 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
274 <description>&lt;p&gt;&lt;a href=&quot;http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-622459b.html&quot;&gt;Aftenposten
275 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
276 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
277 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
278 på om den fri oversetterløsningen
279 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
280 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
281
282 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
283
284 &lt;blockquote&gt;
285 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
286 rolle og muligheter til å håndtere internasjonale utfordringer, som
287 for eksempel flykningekrisen.&lt;/p&gt;
288
289 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
290 på temaet:&lt;/p&gt;
291 &lt;ol&gt;
292 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
293 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
294 &lt;/ol&gt;
295
296 &lt;/blockquote&gt;
297
298 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
299
300 &lt;blockquote&gt;
301 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
302 andre aktørar og høve til å handtera internasjonale utfordringar, som
303 til dømes *flykningekrisen.&lt;/p&gt;
304
305 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
306 temaet:&lt;/p&gt;
307
308 &lt;ol&gt;
309 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
310 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
311 &lt;/ol&gt;
312
313 &lt;/blockquote&gt;
314
315 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
316 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
317 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
318 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
319 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
320 det er kanskje flisespikking. Det understreker vel bare at det alltid
321 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
322 </description>
323 </item>
324
325 <item>
326 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
327 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
328 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
329 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
330 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
331 computers at the time, I often needed a way to detect if the machine
332 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
333 file or directory affected by the hang, the process (and possibly the
334 shell) will hang too. So you want to be able to detect this without
335 risking the detection process getting stuck too. It has not been
336 obvious how to do this. When the hang has lasted a while, it is
337 possible to find messages like these in dmesg:&lt;/p&gt;
338
339 &lt;p&gt;&lt;blockquote&gt;
340 nfs: server nfsserver not responding, still trying
341 &lt;br&gt;nfs: server nfsserver OK
342 &lt;/blockquote&gt;&lt;/p&gt;
343
344 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
345 be sure looking in dmesg is going to work. If there are lots of other
346 messages in dmesg the lines might have rotated out of site before they
347 are noticed.&lt;/p&gt;
348
349 &lt;p&gt;While reading through the nfs client implementation in linux kernel
350 code, I came across some statistics that seem to give a way to detect
351 it. The om_timeouts sunrpc value in the kernel will increase every
352 time the above log entry is inserted into dmesg. And after digging a
353 bit further, I discovered that this value show up in
354 /proc/self/mountstats on Linux.&lt;/p&gt;
355
356 &lt;p&gt;The mountstats content seem to be shared between files using the
357 same file system context, so it is enough to check one of the
358 mountstats files to get the state of the mount point for the machine.
359 I assume this will not show lazy umounted NFS points, nor NFS mount
360 points in a different process context (ie with a different filesystem
361 view), but that does not worry me.&lt;/p&gt;
362
363 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
364
365 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
366 [...]
367 device /dev/mapper/Debian-var mounted on /var with fstype ext3
368 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
369 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
370 age: 7863311
371 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
372 sec: flavor=1,pseudoflavor=1
373 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
374 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
375 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
376 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
377 per-op statistics
378 NULL: 0 0 0 0 0 0 0 0
379 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
380 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
381 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
382 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
383 READLINK: 125 125 0 20472 18620 0 1112 1118
384 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
385 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
386 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
387 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
388 SYMLINK: 903 903 0 233428 245488 6 5865 5917
389 MKNOD: 80 80 0 20148 21760 0 299 304
390 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
391 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
392 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
393 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
394 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
395 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
396 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
397 FSINFO: 2 2 0 232 328 0 1 1
398 PATHCONF: 1 1 0 116 140 0 0 0
399 COMMIT: 0 0 0 0 0 0 0 0
400
401 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
402 [...]
403 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
404
405 &lt;p&gt;The key number to look at is the third number in the per-op list.
406 It is the number of NFS timeouts experiences per file system
407 operation. Here 22 write timeouts and 5 access timeouts. If these
408 numbers are increasing, I believe the machine is experiencing NFS
409 hang. Unfortunately the timeout value do not start to increase right
410 away. The NFS operations need to time out first, and this can take a
411 while. The exact timeout value depend on the setup. For example the
412 defaults for TCP and UDP mount points are quite different, and the
413 timeout value is affected by the soft, hard, timeo and retrans NFS
414 mount options.&lt;/p&gt;
415
416 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
417 Enterprise Linux for getting the timeout count is to peek in /proc/.
418 But according to
419 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
420 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
421 command can be used to get these timeout values. But this do not work
422 on Linux, as far as I can tell. I
423 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
424 but have not seen any replies yet.&lt;/p&gt;
425
426 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
427 experiencing NFS hangs? Is there a way to detect which processes are
428 affected? Is there a way to get the NFS mount going quickly once the
429 network problem causing the NFS hang has been cleared? I would very
430 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
431 </description>
432 </item>
433
434 <item>
435 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
436 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
437 <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>
438 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
439 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
440 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
441 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
442 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
443 we are working on the proof reading to ensure consistent language and
444 use of correct computer science terms. The plan is to make the book
445 available on paper, as well as in electronic form. For that to
446 happen, the proof reading must be completed and all the figures need
447 to be translated. If you want to help out, get in touch.&lt;/p&gt;
448
449 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
450
451 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
452 pages) of the book created every morning is available for
453 proofreading. If you find any errors, please
454 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
455 Weblate and correct the error&lt;/a&gt;. The
456 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
457 of the translation including figures&lt;/a&gt; is a useful source for those
458 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
459 </description>
460 </item>
461
462 <item>
463 <title>Unlimited randomness with the ChaosKey?</title>
464 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
465 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
466 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
467 <description>&lt;p&gt;A few days ago I ordered a small batch of
468 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
469 USB dongle for generating entropy created by Bdale Garbee and Keith
470 Packard. Yesterday it arrived, and I am very happy to report that it
471 work great! According to its designers, to get it to work out of the
472 box, you need the Linux kernel version 4.1 or later. I tested on a
473 Debian Stretch machine (kernel version 4.9), and there it worked just
474 fine, increasing the available entropy very quickly. I wrote a small
475 test oneliner to test. It first print the current entropy level,
476 drain /dev/random, and then print the entropy level for five seconds.
477 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
478
479 &lt;blockquote&gt;&lt;pre&gt;
480 % cat /proc/sys/kernel/random/entropy_avail; \
481 dd bs=1M if=/dev/random of=/dev/null count=1; \
482 for n in $(seq 1 5); do \
483 cat /proc/sys/kernel/random/entropy_avail; \
484 sleep 1; \
485 done
486 300
487 0+1 oppføringer inn
488 0+1 oppføringer ut
489 28 byte kopiert, 0,000264565 s, 106 kB/s
490 4
491 8
492 12
493 17
494 21
495 %
496 &lt;/pre&gt;&lt;/blockquote&gt;
497
498 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
499 application requiring random bits (like a HTTPS enabled web server)
500 will halt and wait for more entrpy. And here is the situation with
501 the ChaosKey inserted:&lt;/p&gt;
502
503 &lt;blockquote&gt;&lt;pre&gt;
504 % cat /proc/sys/kernel/random/entropy_avail; \
505 dd bs=1M if=/dev/random of=/dev/null count=1; \
506 for n in $(seq 1 5); do \
507 cat /proc/sys/kernel/random/entropy_avail; \
508 sleep 1; \
509 done
510 1079
511 0+1 oppføringer inn
512 0+1 oppføringer ut
513 104 byte kopiert, 0,000487647 s, 213 kB/s
514 433
515 1028
516 1031
517 1035
518 1038
519 %
520 &lt;/pre&gt;&lt;/blockquote&gt;
521
522 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
523 someone want to buy one here in Norway. :)&lt;/p&gt;
524
525 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
526 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
527 recording illuminating&lt;/a&gt;. It explains exactly what the source of
528 randomness is, if you are unable to spot it from the schema drawing
529 available from the ChaosKey web site linked at the start of this blog
530 post.&lt;/p&gt;
531 </description>
532 </item>
533
534 <item>
535 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
536 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
537 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
538 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
539 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
540 web servers, and who own the network equipment it is flowing through?
541 It is possible to get a glimpse of this from using traceroute, but it
542 is hard to find all the details. Many years ago, I wrote a system to
543 map the Norwegian Internet (trying to figure out if our plans for a
544 network game service would get low enough latency, and who we needed
545 to talk to about setting up game servers close to the users. Back
546 then I used traceroute output from many locations (I asked my friends
547 to run a script and send me their traceroute output) to create the
548 graph and the map. The output from traceroute typically look like
549 this:
550
551 &lt;p&gt;&lt;pre&gt;
552 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
553 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
554 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
555 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
556 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
557 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
558 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
559 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
560 8 * * *
561 9 * * *
562 [...]
563 &lt;/pre&gt;&lt;/p&gt;
564
565 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
566 network equipment involved in getting the data traffic from me to the
567 www.stortinget.no server, and how long it took in milliseconds for a
568 package to reach the equipment and return to me. Three packages are
569 sent, and some times the packages do not follow the same path. This
570 is shown for hop 5, where three different IP addresses replied to the
571 traceroute request.&lt;/p&gt;
572
573 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
574 implementations I use are traceroute (using ICMP packages) mtr (can do
575 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
576 traceroute and a lot of other capabilities). All of them are easily
577 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
578
579 &lt;p&gt;This time around, I wanted to know the geographic location of
580 different route points, to visualize how visiting a web page spread
581 information about the visit to a lot of servers around the globe. The
582 background is that a web site today often will ask the browser to get
583 from many servers the parts (for example HTML, JSON, fonts,
584 JavaScript, CSS, video) required to display the content. This will
585 leak information about the visit to those controlling these servers
586 and anyone able to peek at the data traffic passing by (like your ISP,
587 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
588
589 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
590 www.stortinget.no. It is read daily by all members of parliament and
591 their staff, as well as political journalists, activits and many other
592 citizens of Norway. A visit to the www.stortinget.no web site will
593 ask your browser to contact 8 other servers: ajax.googleapis.com,
594 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
595 stats.g.doubleclick.net, www.google-analytics.com,
596 www.googletagmanager.com and www.netigate.se. I extracted this by
597 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
598 Stortinget web page and tell me all the URLs PhantomJS downloaded to
599 render the page (in HAR format using
600 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
601 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
602 to do this). My goal is to visualize network traces to all IP
603 addresses behind these DNS names, do show where visitors personal
604 information is spread when visiting the page.&lt;/p&gt;
605
606 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
607 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;
608
609 &lt;p&gt;When I had a look around for options, I could not find any good
610 free software tools to do this, and decided I needed my own traceroute
611 wrapper outputting KML based on locations looked up using GeoIP. KML
612 is easy to work with and easy to generate, and understood by several
613 of the GIS tools I have available. I got good help from by NUUG
614 colleague Anders Einar with this, and the result can be seen in
615 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
616 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
617 free GeoIP databases I could find (and the for-pay databases my
618 friends had access to) is not up to the task. The IP addresses of
619 central Internet infrastructure would typically be placed near the
620 controlling companies main office, and not where the router is really
621 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
622 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
623
624 &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
625 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;
626
627 &lt;p&gt;I also had a look at the visual traceroute graph created by
628 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
629 showing IP network ownership (aka AS owner) for the IP address in
630 question.
631 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
632 graph display a lot of useful information about the traceroute in SVG
633 format&lt;/a&gt;, and give a good indication on who control the network
634 equipment involved, but it do not include geolocation. This graph
635 make it possible to see the information is made available at least for
636 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
637 3 Communications and NetDNA.&lt;/p&gt;
638
639 &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
640 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;
641
642 &lt;p&gt;In the process, I came across the
643 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
644 Salim Gasmi. Its methology of combining guesses based on DNS names,
645 various location databases and finally use latecy times to rule out
646 candidate locations seemed to do a very good job of guessing correct
647 geolocation. But it could only do one trace at the time, did not have
648 a sensor in Norway and did not make the geolocations easily available
649 for postprocessing. So I contacted the developer and asked if he
650 would be willing to share the code (he refused until he had time to
651 clean it up), but he was interested in providing the geolocations in a
652 machine readable format, and willing to set up a sensor in Norway. So
653 since yesterday, it is possible to run traces from Norway in this
654 service thanks to a sensor node set up by
655 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
656 trace in KML format for further processing.&lt;/p&gt;
657
658 &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
659 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;
660
661 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
662 Denmark, Germany, Holland and Ireland. Plenty of places where the
663 Snowden confirmations verified the traffic is read by various actors
664 without your best interest as their top priority.&lt;/p&gt;
665
666 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
667 over all the hosts behind the urls imported by www.stortinget.no and
668 ask for the KML file from GeoTraceroute, and create a combined KML
669 file with all the traces (unfortunately only one of the IP addresses
670 behind the DNS name is traced this time. To get them all, one would
671 have to request traces using IP number instead of DNS names from
672 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
673
674 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
675 the IP traffic moves and who control the boxes involved in moving it.
676 And every time the link crosses for example the Swedish border, we can
677 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
678 Britain and NSA in USA and cables around the globe. (Hm, what should
679 we tell them? :) Keep that in mind if you ever send anything
680 unencrypted over the Internet.&lt;/p&gt;
681
682 &lt;p&gt;PS: KML files are drawn using
683 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
684 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
685 Marble. There are heaps of other options too.&lt;/p&gt;
686
687 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
688 activities, please send Bitcoin donations to my address
689 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
690 </description>
691 </item>
692
693 <item>
694 <title>Appstream just learned how to map hardware to packages too!</title>
695 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
696 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
697 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
698 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
699 readers probably know, I have been working on the
700 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
701 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
702 it easier for users to figure out what to install to get a given piece
703 of hardware to work in Debian, and a key part of this system is a way
704 to map hardware to packages. Isenkram have its own mapping database,
705 and also uses data provided by each package using the AppStream
706 metadata format. And today,
707 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
708 Debian learned to look up hardware the same way Isenkram is doing it,
709 ie using fnmatch():&lt;/p&gt;
710
711 &lt;p&gt;&lt;pre&gt;
712 % appstreamcli what-provides modalias \
713 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
714 Identifier: pymissile [generic]
715 Name: pymissile
716 Summary: Control original Striker USB Missile Launcher
717 Package: pymissile
718 % appstreamcli what-provides modalias usb:v0694p0002d0000
719 Identifier: libnxt [generic]
720 Name: libnxt
721 Summary: utility library for talking to the LEGO Mindstorms NXT brick
722 Package: libnxt
723 ---
724 Identifier: t2n [generic]
725 Name: t2n
726 Summary: Simple command-line tool for Lego NXT
727 Package: t2n
728 ---
729 Identifier: python-nxt [generic]
730 Name: python-nxt
731 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
732 Package: python-nxt
733 ---
734 Identifier: nbc [generic]
735 Name: nbc
736 Summary: C compiler for LEGO Mindstorms NXT bricks
737 Package: nbc
738 %
739 &lt;/pre&gt;&lt;/p&gt;
740
741 &lt;p&gt;A similar query can be done using the combined AppStream and
742 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
743
744 &lt;p&gt;&lt;pre&gt;
745 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
746 pymissile
747 % isenkram-lookup usb:v0694p0002d0000
748 libnxt
749 nbc
750 python-nxt
751 t2n
752 %
753 &lt;/pre&gt;&lt;/p&gt;
754
755 &lt;p&gt;You can find modalias values relevant for your machine using
756 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
757
758 &lt;p&gt;If you want to make this system a success and help Debian users
759 make the most of the hardware they have, please
760 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
761 AppStream metadata for your package following the guidelines&lt;/a&gt;
762 documented in the wiki. So far only 11 packages provide such
763 information, among the several hundred hardware specific packages in
764 Debian. The Isenkram database on the other hand contain 101 packages,
765 mostly related to USB dongles. Most of the packages with hardware
766 mapping in AppStream are LEGO Mindstorms related, because I have, as
767 part of my involvement in
768 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
769 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
770 complete set of packages in Debian for that particular hardware. The
771 team also got a nice Christmas present today. The
772 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
773 package&lt;/a&gt; made it into Debian. With this package in place, it is
774 now possible to use the LEGO Mindstorms NXT unit with only free
775 software, as the nxt-firmware package contain the source and firmware
776 binaries for the NXT brick.&lt;/p&gt;
777
778 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
779 activities, please send Bitcoin donations to my address
780 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
781 </description>
782 </item>
783
784 <item>
785 <title>Isenkram updated with a lot more hardware-package mappings</title>
786 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
787 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
788 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
789 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
790 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
791 and install packages to get your hardware dongles to work, is still
792 going strong. It is a system to look up the hardware present on or
793 connected to the current system, and map the hardware to Debian
794 packages. It can either be done using the tools in isenkram-cli or
795 using the user space daemon in the isenkram package. The latter will
796 notify you, when inserting new hardware, about what packages to
797 install to get the dongle working. It will even provide a button to
798 click on to ask packagekit to install the packages.&lt;/p&gt;
799
800 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
801
802 &lt;p&gt;&lt;pre&gt;
803 % isenkram-lookup
804 bluez
805 cheese
806 ethtool
807 fprintd
808 fprintd-demo
809 gkrellm-thinkbat
810 hdapsd
811 libpam-fprintd
812 pidgin-blinklight
813 thinkfan
814 tlp
815 tp-smapi-dkms
816 tp-smapi-source
817 tpb
818 %
819 &lt;/pre&gt;&lt;/p&gt;
820
821 &lt;p&gt;It can also list the firware package providing firmware requested
822 by the load kernel modules, which in my case is an empty list because
823 I have all the firmware my machine need:
824
825 &lt;p&gt;&lt;pre&gt;
826 % /usr/sbin/isenkram-autoinstall-firmware -l
827 info: did not find any firmware files requested by loaded kernel modules. exiting
828 %
829 &lt;/pre&gt;&lt;/p&gt;
830
831 &lt;p&gt;The last few days I had a look at several of the around 250
832 packages in Debian with udev rules. These seem like good candidates
833 to install when a given hardware dongle is inserted, and I found
834 several that should be proposed by isenkram. I have not had time to
835 check all of them, but am happy to report that now there are 97
836 packages packages mapped to hardware by Isenkram. 11 of these
837 packages provide hardware mapping using AppStream, while the rest are
838 listed in the modaliases file provided in isenkram.&lt;/p&gt;
839
840 &lt;p&gt;These are the packages with hardware mappings at the moment. The
841 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
842 support using AppStream, for everyone to use:&lt;/p&gt;
843
844 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
845 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
846 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
847 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
848 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
849 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
850 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
851 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
852 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
853 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
854 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
855 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
856 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
857 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
858 pcscd, pidgin-blinklight, printer-driver-splix,
859 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
860 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
861 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
862 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
863 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
864 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
865 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
866 xserver-xorg-video-vmware, yubikey-personalization and
867 zd1211-firmware&lt;/p&gt;
868
869 &lt;p&gt;If you know of other packages, please let me know with a wishlist
870 bug report against the isenkram-cli package, and ask the package
871 maintainer to
872 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
873 metadata according to the guidelines&lt;/a&gt; to provide the information
874 for everyone. In time, I hope to get rid of the isenkram specific
875 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
876
877 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
878 much hardware, and suggest that the package with with any ethernet
879 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
880 the details. I hope the maintainer find time to address it soon. In
881 the mean time I provide an override in isenkram.&lt;/p&gt;
882 </description>
883 </item>
884
885 <item>
886 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
887 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
888 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
889 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
890 <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;
891
892 &lt;p&gt;In my early years, I played
893 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
894 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
895 space, and reached the &#39;elite&#39; fighting status before I moved on. The
896 original Elite game was available on Commodore 64 and the IBM PC
897 edition I played had a 64 KB executable. I am still impressed today
898 that the authors managed to squeeze both a 3D engine and details about
899 more than 2000 planet systems across 7 galaxies into a binary so
900 small.&lt;/p&gt;
901
902 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
903 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
904 really have time to test it properly until a few days ago. It was
905 great to discover that my old knowledge about trading routes were
906 still valid. But my fighting and flying abilities were gone, so I had
907 to retrain to be able to dock on a space station. And I am still not
908 able to make much resistance when I am attacked by pirates, so I
909 bougth and mounted the most powerful laser in the rear to be able to
910 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
911
912 &lt;p&gt;When playing Elite in the late eighties, I had to discover
913 everything on my own, and I had long lists of prices seen on different
914 planets to be able to decide where to trade what. This time I had the
915 advantages of the
916 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
917 where information about each planet is easily available with common
918 price ranges and suggested trading routes. This improved my ability
919 to earn money and I have been able to earn enough to buy a lot of
920 useful equipent in a few days. I believe I originally played for
921 months before I could get a docking computer, while now I could get it
922 after less then a week.&lt;/p&gt;
923
924 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
925 space, you should try out Oolite. It is available for Linux, MacOSX
926 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
927
928 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
929 activities, please send Bitcoin donations to my address
930 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
931 </description>
932 </item>
933
934 <item>
935 <title>Quicker Debian installations using eatmydata</title>
936 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
937 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
938 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
939 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
940 installation system, observing how using
941 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
942 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
943 speedup around 20-40 percent for Debian Edu, where we install around
944 1000 packages from within the installer. The eatmydata package
945 provide a way to disable/delay file system flushing. This is a bit
946 risky in the general case, as files that should be stored on disk will
947 stay only in memory a bit longer than expected, causing problems if a
948 machine crashes at an inconvenient time. But for an installation, if
949 the machine crashes during installation the process is normally
950 restarted, and avoiding disk operations as much as possible to speed
951 up the process make perfect sense.
952
953 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
954 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
955 but did not have time to push it any further. But a few months ago I
956 picked it up again and worked with the libeatmydata package maintainer
957 Mattia Rizzolo to make it easier for everyone to get this installation
958 speedup in Debian. Thanks to our cooperation There is now an
959 eatmydata-udeb package in Debian testing and unstable, and simply
960 enabling/installing it in debian-installer (d-i) is enough to get the
961 quicker installations. It can be enabled using preseeding. The
962 following untested kernel argument should do the trick:&lt;/p&gt;
963
964 &lt;blockquote&gt;&lt;pre&gt;
965 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
966 &lt;/pre&gt;&lt;/blockquote&gt;
967
968 &lt;p&gt;This should ask d-i to install the package inside the d-i
969 environment early in the installation sequence. Having it installed
970 in d-i in turn will make sure the relevant scripts are called just
971 after debootstrap filled /target/ with the freshly installed Debian
972 system to configure apt to run dpkg with eatmydata. This is enough to
973 speed up the installation process. There is a proposal to
974 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
975 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
976 tested its impact.&lt;/p&gt;
977
978 </description>
979 </item>
980
981 <item>
982 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
983 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
984 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
985 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
986 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
987 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
988 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
989 elever over det ganske land skal levere inn hvert år. Det mange ikke
990 vet er at selv om de kommersielle alternativene
991 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
992 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
993 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
994 utmerket fri programvarealternativ som kan. Oversetterverktøyet
995 Apertium har støtte for en rekke språkkombinasjoner, og takket være
996 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
997 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
998 nynorsk, og få den automatoversatt til det andre skriftspråket.
999 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1000 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1001 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1002 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1003 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
1004 teksten din i webskjemaet der.
1005
1006 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
1007 teknologien kan du enten installere pakken
1008 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
1009 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1010 api.apertium.org. Se
1011 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
1012 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1013 denne teksten som ble skrevet på bokmål over maskinoversatt til
1014 nynorsk.&lt;/p&gt;
1015
1016 &lt;hr/&gt;
1017
1018 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1019 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1020 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1021 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1022 veit er at sjølv om dei kommersielle alternativa
1023 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
1024 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
1025 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1026 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1027 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1028 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1029 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1030 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1031 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1032 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1033 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1034 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1035 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
1036 teksta di i *webskjemaet der.
1037
1038 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
1039 teknologien kan du anten installera pakken
1040 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
1041 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1042 *api.*apertium.org. Sjå
1043 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
1044 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1045 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1046 nynorsk.&lt;/p&gt;
1047 </description>
1048 </item>
1049
1050 <item>
1051 <title>Coz profiler for multi-threaded software is now in Debian</title>
1052 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
1053 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
1054 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
1055 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
1056 profiler able to run benchmarking experiments on the instrumented
1057 multi-threaded program, finally
1058 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
1059 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
1060 months since
1061 &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
1062 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
1063 it suitable for Debian. There are still issues with clang
1064 compatibility, inline assembly only working x86 and minimized
1065 JavaScript libraries.&lt;/p&gt;
1066
1067 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
1068
1069 &lt;p&gt;&lt;blockquote&gt;
1070 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
1071 &lt;/blockquote&gt;&lt;/p&gt;
1072
1073 &lt;p&gt;This will produce a profile.coz file in the current working
1074 directory with the profiling information. This is then given to a
1075 JavaScript application provided in the package and available from
1076 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
1077 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
1078
1079 &lt;p&gt;&lt;blockquote&gt;
1080 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
1081 &lt;/blockquote&gt;&lt;/p&gt;
1082
1083 &lt;p&gt;See the project home page and the
1084 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
1085 ;login: article on Coz&lt;/a&gt; for more information on how it is
1086 working.&lt;/p&gt;
1087 </description>
1088 </item>
1089
1090 <item>
1091 <title>My own self balancing Lego Segway</title>
1092 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
1093 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
1094 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
1095 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
1096 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
1097 present. It had been on my wishlist for a while, because I wanted to
1098 build a Segway like balancing lego robot. I had already built
1099 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
1100 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
1101 NXT kit as the balance sensor, but it was not working very well. It
1102 could balance for a while, but was very sensitive to the light
1103 condition in the room and the reflective properties of the surface and
1104 would fall over after a short while. I wanted something more robust,
1105 and had
1106 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
1107 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
1108 wishlist for some years before it suddenly showed up as a gift from my
1109 loved ones. :)&lt;/p&gt;
1110
1111 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
1112 since then. But that changed some days ago, when I was searching for
1113 lego segway information and came across a recipe from HiTechnic for
1114 building
1115 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
1116 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
1117 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
1118 code&lt;/a&gt; was included, so it was just a question of putting it all
1119 together. And thanks to the great work of many Debian developers, the
1120 compiler needed to build the source for the NXT is already included in
1121 Debian, so I was read to go in less than an hour. The resulting robot
1122 do not look very impressive in its simplicity:&lt;/p&gt;
1123
1124 &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;
1125
1126 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
1127 design from HiTechnic, I had to comment out the last task
1128 (taskControl). I simply placed /* and */ around it get the program
1129 working without that sensor present. Now it balances just fine until
1130 the battery status run low:&lt;/p&gt;
1131
1132 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
1133 &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;
1134 &lt;/video&gt;&lt;/p&gt;
1135
1136 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
1137 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
1138
1139 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
1140 they need to work with LEGO in Debian and all our derivative
1141 distributions like Ubuntu, check out
1142 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
1143 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
1144 RCX and NXT controller (no EV3), and would like to make sure the
1145 Debian tools needed to program the systems I own work as they
1146 should.&lt;/p&gt;
1147 </description>
1148 </item>
1149
1150 <item>
1151 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
1152 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
1153 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
1154 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
1155 <description>&lt;p&gt;In July
1156 &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
1157 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
1158 the ability to receive SMS messages (aka without a cell phone). It is
1159 time to share some experiences and provide an updated setup.&lt;/p&gt;
1160
1161 &lt;p&gt;The Signal app have worked fine for several months now, and I use
1162 it regularly to chat with my loved ones. I had a major snag at the
1163 end of my summer vacation, when the the app completely forgot my
1164 setup, identity and keys. The reason behind this major mess was
1165 running out of disk space. To avoid that ever happening again I have
1166 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
1167 roll back to an earlier version if the files are wiped by mistake. I
1168 had to use it once after introducing the git backup. When rolling
1169 back to an earlier version, one need to use the &#39;reset session&#39; option
1170 in Signal to get going, and notify the people you talk with about the
1171 problem. I assume there is some sequence number tracking in the
1172 protocol to detect rollback attacks. The git repository is rather big
1173 (674 MiB so far), but I have not tried to figure out if some of the
1174 content can be added to a .gitignore file due to lack of spare
1175 time.&lt;/p&gt;
1176
1177 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
1178 make it impossible to send messages using Signal. I could still
1179 receive them, but had to patch the code with a new timestamp to send.
1180 I believe the timeout is added by the developers to force people to
1181 upgrade to the latest version of the app, even when there is no
1182 protocol changes, to reduce the version skew among the user base and
1183 thus try to keep the number of support requests down.&lt;/p&gt;
1184
1185 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
1186 making the old patch fail to apply cleanly. Below is an updated
1187 patch, including the shell wrapper I use to start Signal. The
1188 original version required a new user to locate the JavaScript console
1189 and call a function from there. I got help from a friend with more
1190 JavaScript knowledge than me to modify the code to provide a GUI
1191 button instead. This mean that to get started you just need to run
1192 the wrapper and click the &#39;Register without mobile phone&#39; to get going
1193 now. I&#39;ve also modified the timeout code to always set it to 90 days
1194 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
1195
1196 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
1197
1198 &lt;ol&gt;
1199
1200 &lt;li&gt;First, install required packages to get the source code and the
1201 browser you need. Signal only work with Chrome/Chromium, as far as I
1202 know, so you need to install it.
1203
1204 &lt;pre&gt;
1205 apt install git tor chromium
1206 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1207 &lt;/pre&gt;&lt;/li&gt;
1208
1209 &lt;li&gt;Modify the source code using command listed in the the patch
1210 block below.&lt;/li&gt;
1211
1212 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
1213 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
1214
1215 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
1216 number you can receive calls to the next minute, receive the
1217 verification code and enter it into the form field and press
1218 &#39;Register&#39;. Note, the phone number you use will be user Signal
1219 username, ie the way others can find you on Signal.&lt;/li&gt;
1220
1221 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
1222 not show up in the contact list until you restart Signal, and there is
1223 no way to assign names to Contacts. There is also no way to create or
1224 update chat groups. I suspect this is because the web app do not have
1225 a associated contact database.&lt;/li&gt;
1226
1227 &lt;/ol&gt;
1228
1229 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
1230 main author moxie0 reject federation and accept dependencies to major
1231 corporations like Google (part of the code is fetched from Google) and
1232 Amazon (the central coordination point is owned by Amazon). See for
1233 example
1234 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
1235 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
1236 view on these issues. But the network effect is strong in this case,
1237 and several of the people I want to communicate with already use
1238 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
1239 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
1240 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
1241 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
1242 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
1243 working on Debian Stable.&lt;/p&gt;
1244
1245 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
1246 working. It switch to the production servers, disable to timeout,
1247 make registration easier and add the shell wrapper:&lt;/p&gt;
1248
1249 &lt;pre&gt;
1250 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
1251 diff --git a/js/background.js b/js/background.js
1252 index 24b4c1d..579345f 100644
1253 --- a/js/background.js
1254 +++ b/js/background.js
1255 @@ -33,9 +33,9 @@
1256 });
1257 });
1258
1259 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
1260 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
1261 var SERVER_PORTS = [80, 4433, 8443];
1262 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
1263 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
1264 var messageReceiver;
1265 window.getSocketStatus = function() {
1266 if (messageReceiver) {
1267 diff --git a/js/expire.js b/js/expire.js
1268 index 639aeae..beb91c3 100644
1269 --- a/js/expire.js
1270 +++ b/js/expire.js
1271 @@ -1,6 +1,6 @@
1272 ;(function() {
1273 &#39;use strict&#39;;
1274 - var BUILD_EXPIRATION = 0;
1275 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
1276
1277 window.extension = window.extension || {};
1278
1279 diff --git a/js/views/install_view.js b/js/views/install_view.js
1280 index 7816f4f..1d6233b 100644
1281 --- a/js/views/install_view.js
1282 +++ b/js/views/install_view.js
1283 @@ -38,7 +38,8 @@
1284 return {
1285 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
1286 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
1287 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
1288 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
1289 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
1290 };
1291 },
1292 clearQR: function() {
1293 diff --git a/options.html b/options.html
1294 index dc0f28e..8d709f6 100644
1295 --- a/options.html
1296 +++ b/options.html
1297 @@ -14,7 +14,10 @@
1298 &amp;lt;div class=&#39;nav&#39;&gt;
1299 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
1300 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
1301 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
1302 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
1303 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
1304 +
1305 + &amp;lt;/div&gt;
1306 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
1307 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
1308 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
1309 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
1310 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
1311 @@ -0,0 +1,12 @@
1312 +#!/bin/sh
1313 +set -e
1314 +cd $(dirname $0)
1315 +mkdir -p userdata
1316 +userdata=&quot;`pwd`/userdata&quot;
1317 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
1318 + (cd $userdata &amp;&amp; git init)
1319 +fi
1320 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
1321 +exec chromium \
1322 + --proxy-server=&quot;socks://localhost:9050&quot; \
1323 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1324 EOF
1325 chmod a+rx run-signal-app
1326 &lt;/pre&gt;
1327
1328 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1329 activities, please send Bitcoin donations to my address
1330 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1331 </description>
1332 </item>
1333
1334 <item>
1335 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
1336 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
1337 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
1338 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
1339 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
1340 system&lt;/a&gt; provide a practical and easy way to figure out which
1341 packages support the hardware in a given machine. The command line
1342 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
1343 convenient way to list and install packages relevant for the current
1344 hardware during system installation, both user space packages and
1345 firmware packages. The GUI background daemon on the other hand provide
1346 a pop-up proposing to install packages when a new dongle is inserted
1347 while using the computer. For example, if you plug in a smart card
1348 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
1349 that package isn&#39;t already installed, and if you plug in a USB video
1350 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
1351 cheese is currently missing. This already work just fine.&lt;/p&gt;
1352
1353 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
1354 package names. When I started no such database existed in Debian, so
1355 I made my own data set and included it with the isenkram package and
1356 made isenkram fetch the latest version of this database from git using
1357 http. This way the isenkram users would get updated package proposals
1358 as soon as I learned more about hardware related packages.&lt;/p&gt;
1359
1360 &lt;p&gt;The hardware is identified using modalias strings. The modalias
1361 design is from the Linux kernel where most hardware descriptors are
1362 made available as a strings that can be matched using filename style
1363 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1364 identifiers.&lt;/p&gt;
1365
1366 &lt;p&gt;The downside to the Isenkram specific database is that there is no
1367 information about relevant distribution / Debian version, making
1368 isenkram propose obsolete packages too. But along came AppStream, a
1369 cross distribution mechanism to store and collect metadata about
1370 software packages. When I heard about the proposal, I contacted the
1371 people involved and suggested to add a hardware matching rule using
1372 modalias strings in the specification, to be able to use AppStream for
1373 mapping hardware to packages. This idea was accepted and AppStream is
1374 now a great way for a package to announce the hardware it support in a
1375 distribution neutral way. I wrote
1376 &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
1377 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
1378 December. If you have a hardware related package in Debian, please
1379 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
1380
1381 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
1382 RCX or NXT unit, announce this support using AppStream. The effect is
1383 that when you insert such LEGO robot controller into your Debian
1384 machine, Isenkram will propose to install the packages needed to get
1385 it working. The intention is that this should allow the local user to
1386 start programming his robot controller right away without having to
1387 guess what packages to use or which permissions to fix.&lt;/p&gt;
1388
1389 &lt;p&gt;But when I sat down with my son the other day to program our NXT
1390 unit using his Debian Stretch computer, I discovered something
1391 annoying. The local console user (ie my son) did not get access to
1392 the USB device for programming the unit. This used to work, but no
1393 longer in Jessie and Stretch. After some investigation and asking
1394 around on #debian-devel, I discovered that this was because udev had
1395 changed the mechanism used to grant access to local devices. The
1396 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
1397 no longer applied, because LDAP users no longer was added to the
1398 plugdev group during login. Michael Biebl told me that this method
1399 was obsolete and the new method used ACLs instead. This was good
1400 news, as the plugdev mechanism is a mess when using a remote user
1401 directory like LDAP. Using ACLs would make sure a user lost device
1402 access when she logged out, even if the user left behind a background
1403 process which would retain the plugdev membership with the ConsoleKit
1404 setup. Armed with this knowledge I moved on to fix the access problem
1405 for the LEGO Mindstorms related packages.&lt;/p&gt;
1406
1407 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
1408 applied directly for a device, or is applied in
1409 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
1410 LEGO Mindstorms udev rules did not have a class, I decided to add the
1411 tag directly in the udev rules files included in the packages. Here
1412 is one example. For the nqc C compiler for the RCX, the
1413 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
1414
1415 &lt;p&gt;&lt;pre&gt;
1416 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
1417 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
1418 &lt;/pre&gt;&lt;/p&gt;
1419
1420 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
1421 packages using plugdev in their /lib/udev/rules.d/ files should be
1422 changed to use this tag (either directly or indirectly via
1423 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
1424 to detect this?&lt;/p&gt;
1425
1426 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
1427 It is unclear to me if the uaccess tag is an internal implementation
1428 detail like the udev-acl tag used by
1429 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
1430 indirect method is the preferred way. Michael
1431 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
1432 documentation from the systemd project&lt;/a&gt; and I hope it will make
1433 this clearer. For now I use the generic classes when they exist and
1434 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
1435 directly if no such class exist.&lt;/p&gt;
1436
1437 &lt;p&gt;To learn more about the isenkram system, please check out
1438 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
1439 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
1440
1441 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
1442 please join us on our IRC channel
1443 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
1444 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
1445 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
1446 list is not yet created, but we are working on it. :)&lt;/p&gt;
1447
1448 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1449 activities, please send Bitcoin donations to my address
1450 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1451 </description>
1452 </item>
1453
1454 <item>
1455 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
1456 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
1457 <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>
1458 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
1459 <description>&lt;p&gt;In April we
1460 &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
1461 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
1462 how to set up and administrate a Debian system. Today I am happy to
1463 report that the first draft is now publicly available. You can find
1464 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
1465 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
1466 eight chapters have a first draft translation, and we are working on
1467 proofreading the content. If you want to help out, please start
1468 contributing using
1469 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
1470 hosted weblate project page&lt;/a&gt;, and get in touch using
1471 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
1472 translators mailing list&lt;/a&gt;. Please also check out
1473 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
1474 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
1475 and update weblate if you find errors.&lt;/p&gt;
1476
1477 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
1478 electronic form.&lt;/p&gt;
1479 </description>
1480 </item>
1481
1482 <item>
1483 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
1484 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
1485 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
1486 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
1487 <description>&lt;p&gt;This summer, I read a great article
1488 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
1489 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
1490 how to profile multi-threaded programs. It presented a system for
1491 profiling software by running experiences in the running program,
1492 testing how run time performance is affected by &quot;speeding up&quot; parts of
1493 the code to various degrees compared to a normal run. It does this by
1494 slowing down parallel threads while the &quot;faster up&quot; code is running
1495 and measure how this affect processing time. The processing time is
1496 measured using probes inserted into the code, either using progress
1497 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1498 can also measure unmodified code by measuring complete the program
1499 runtime and running the program several times instead.&lt;/p&gt;
1500
1501 &lt;p&gt;The project and presentation was so inspiring that I would like to
1502 get the system into Debian. I
1503 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
1504 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
1505 system ready for Debian by sending patches. The build process need to
1506 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
1507 to include the JavaScript web page used to visualize the collected
1508 profiling information included in the source package.
1509 But I expect that should work out fairly soon.&lt;/p&gt;
1510
1511 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
1512 on a binary with debug symbols available, start the program like this:
1513
1514 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1515 coz run --- program-to-run
1516 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1517
1518 &lt;p&gt;This will create a text file profile.coz with the instrumentation
1519 information. To show what part of the code affect the performance
1520 most, use a web browser and either point it to
1521 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
1522 or use the copy from git (in the gh-pages branch). Check out this web
1523 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
1524 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
1525 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1526 code, rebuild and run the profiler. This allow coz to do more
1527 targeted experiments.&lt;/p&gt;
1528
1529 &lt;p&gt;A video published by ACM
1530 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
1531 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
1532 from the 25th Symposium on Operating Systems Principles available
1533 titled
1534 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
1535 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
1536
1537 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
1538 for Coz is available from github. It will only build with clang
1539 because it uses a
1540 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
1541 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
1542 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
1543 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
1544
1545 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
1546 of software in Debian. I would very much like some help with the
1547 packaging effort, as I lack the in depth knowledge on how to package
1548 C++ libraries.&lt;/p&gt;
1549 </description>
1550 </item>
1551
1552 <item>
1553 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
1554 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
1555 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
1556 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
1557 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1558 to be a slight challenge. Here is the recipe if I ever need to do it
1559 again. It all started by me wanting to try the recipe to set up
1560 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
1561 hardened Android installation&lt;/a&gt; from the Tor project blog on a
1562 device I had access to. It is a old mobile phone with a broken
1563 microphone The initial idea had been to just
1564 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
1565 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
1566 until a few days ago.&lt;/p&gt;
1567
1568 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
1569 loader (press volume down and power at the same time), (2) select
1570 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
1571 machine, (4) request the device identifier token by running &#39;fastboot
1572 oem get_identifier_token&#39;, (5) request the device unlocking key using
1573 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
1574 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
1575
1576 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
1577 or newer, and the device I was working on had 2.00.0027. This
1578 apparently can be easily fixed by downloading a Windows program and
1579 running it on your Windows machine, if you accept the terms Microsoft
1580 require you to accept to use Windows - which I do not. So I had to
1581 come up with a different approach. I got a lot of help from AndyCap
1582 on #nuug, and would not have been able to get this working without
1583 him.&lt;/p&gt;
1584
1585 &lt;p&gt;First I needed to extract the hboot firmware from
1586 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
1587 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
1588 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
1589 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
1590 recognise the file format, but unruu worked and extracted rom.zip,
1591 containing the new hboot firmware and a text file describing which
1592 devices it would work for.&lt;/p&gt;
1593
1594 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
1595 followed some instructions
1596 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
1597 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
1598 machine with Debian testing:&lt;/p&gt;
1599
1600 &lt;p&gt;&lt;pre&gt;
1601 adb reboot-bootloader
1602 fastboot oem rebootRUU
1603 fastboot flash zip rom.zip
1604 fastboot flash zip rom.zip
1605 fastboot reboot
1606 &lt;/pre&gt;&lt;/p&gt;
1607
1608 &lt;p&gt;The flash command apparently need to be done twice to take effect,
1609 as the first is just preparations and the second one do the flashing.
1610 The adb command is just to get to the boot loader menu, so turning the
1611 device on while holding volume down and the power button should work
1612 too.&lt;/p&gt;
1613
1614 &lt;p&gt;With the new hboot version in place I could start following the
1615 instructions on the HTC developer web site. I got the device token
1616 like this:&lt;/p&gt;
1617
1618 &lt;p&gt;&lt;pre&gt;
1619 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
1620 &lt;/pre&gt;
1621
1622 &lt;p&gt;And once I got the unlock code via email, I could use it like
1623 this:&lt;/p&gt;
1624
1625 &lt;p&gt;&lt;pre&gt;
1626 fastboot flash unlocktoken Unlock_code.bin
1627 &lt;/pre&gt;&lt;/p&gt;
1628
1629 &lt;p&gt;And with that final step in place, the phone was unlocked and I
1630 could start stuffing the software of my own choosing into the device.
1631 So far I only inserted a replacement recovery image to wipe the phone
1632 before I start. We will see what happen next. Perhaps I should
1633 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
1634 </description>
1635 </item>
1636
1637 <item>
1638 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
1639 <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>
1640 <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>
1641 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
1642 <description>&lt;p&gt;For a while now, I have wanted to test
1643 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
1644 said to provide end to end encrypted communication and several of my
1645 friends and family are already using it. As I by choice do not own a
1646 mobile phone, this proved to be harder than expected. And I wanted to
1647 have the source of the client and know that it was the code used on my
1648 machine. But yesterday I managed to get it working. I used the
1649 Github source, compared it to the source in
1650 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
1651 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
1652 patches to use the production Signal servers, started the app and
1653 asked for the hidden &quot;register without a smart phone&quot; form. Here is
1654 the recipe how I did it.&lt;/p&gt;
1655
1656 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
1657
1658 &lt;pre&gt;
1659 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1660 &lt;/pre&gt;
1661
1662 &lt;p&gt;Next, I patched the source to use the production servers, to be
1663 able to talk to other Signal users:&lt;/p&gt;
1664
1665 &lt;pre&gt;
1666 cat &amp;lt;&amp;lt;EOF | patch -p0
1667 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
1668 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
1669 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
1670 @@ -47,8 +47,8 @@
1671 });
1672 });
1673
1674 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
1675 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
1676 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
1677 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
1678 var messageReceiver;
1679 window.getSocketStatus = function() {
1680 if (messageReceiver) {
1681 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
1682 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
1683 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
1684 @@ -1,6 +1,6 @@
1685 ;(function() {
1686 &#39;use strict&#39;;
1687 - var BUILD_EXPIRATION = 0;
1688 + var BUILD_EXPIRATION = 1474492690000;
1689
1690 window.extension = window.extension || {};
1691
1692 EOF
1693 &lt;/pre&gt;
1694
1695 &lt;p&gt;The first part is changing the servers, and the second is updating
1696 an expiration timestamp. This timestamp need to be updated regularly.
1697 It is set 90 days in the future by the build process (Gruntfile.js).
1698 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
1699
1700 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
1701 script to launch Signal in Chromium.&lt;/p&gt;
1702
1703 &lt;pre&gt;
1704 #!/bin/sh
1705 cd $(dirname $0)
1706 mkdir -p userdata
1707 exec chromium \
1708 --proxy-server=&quot;socks://localhost:9050&quot; \
1709 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1710 &lt;/pre&gt;
1711
1712 &lt;p&gt; The script start the app and configure Chromium to use the Tor
1713 SOCKS5 proxy to make sure those controlling the Signal servers (today
1714 Amazon and Whisper Systems) as well as those listening on the lines
1715 will have a harder time location my laptop based on the Signal
1716 connections if they use source IP address.&lt;/p&gt;
1717
1718 &lt;p&gt;When the script starts, one need to follow the instructions under
1719 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
1720 repository. I right clicked on the Signal window to get up the
1721 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
1722 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
1723 registration form. Then I entered by land line phone number and
1724 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
1725 repeated the verification code three times. After entering the number
1726 into the verification code field in the form, I could start using
1727 Signal from my laptop.
1728
1729 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
1730 whom and thus who know who to those controlling the central server,
1731 but such leakage is hard to avoid with a centrally controlled server
1732 setup. It is something to keep in mind when using Signal - the
1733 content of your chats are harder to intercept, but the meta data
1734 exposing your contact network is available to people you do not know.
1735 So better than many options, but not great. And sadly the usage is
1736 connected to my land line, thus allowing those controlling the server
1737 to associate it to my home and person. I would prefer it if only
1738 those I knew could tell who I was on Signal. There are options
1739 avoiding such information leakage, but most of my friends are not
1740 using them, so I am stuck with Signal for now.&lt;/p&gt;
1741
1742 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
1743 on this topic in
1744 &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
1745 and updated recipe for using the Signal app without a mobile
1746 phone&lt;/a&gt;.&lt;/p&gt;
1747 </description>
1748 </item>
1749
1750 <item>
1751 <title>The new &quot;best&quot; multimedia player in Debian?</title>
1752 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
1753 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
1754 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
1755 <description>&lt;p&gt;When I set out a few weeks ago to figure out
1756 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
1757 multimedia player in Debian claimed to support most file formats /
1758 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
1759 the various players claimed support for. The range was from 55 to 130
1760 MIME types. I suspect most media formats are supported by all
1761 players, but this is not really reflected in the MimeTypes values in
1762 their desktop files. There are probably also some bogus MIME types
1763 listed, but it is hard to identify which one this is.&lt;/p&gt;
1764
1765 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
1766 the players suggesting to add more MIME types to their desktop files,
1767 and decided to spend some time myself improving the situation for my
1768 favorite media player VLC. The fixes for VLC entered Debian unstable
1769 yesterday. The complete list of MIME types can be seen on the
1770 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
1771 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
1772
1773 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
1774 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1775 kmplayer. I am sure some of the other players desktop files support
1776 several of the formats currently listed as working only with vlc,
1777 toten and parole.&lt;/p&gt;
1778
1779 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
1780 supported by all the tested multimedia players in Debian in their
1781 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1782 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1783 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1784 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1785 it sad that video/ogg and video/webm is not supported by all the media
1786 players in Debian. As far as I can tell, all of them can handle both
1787 formats.&lt;/p&gt;
1788 </description>
1789 </item>
1790
1791 <item>
1792 <title>A program should be able to open its own files on Linux</title>
1793 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
1794 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
1795 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
1796 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
1797 decided to test its presentation tool when making the slides for a
1798 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1799 wrote the first draft of the slides, saved the result and went to bed
1800 the day before I would give the talk. The next day I took a plane to
1801 the location where the meeting should take place, and on the plane I
1802 started up koffice again to polish the talk a bit, only to discover
1803 that kpresenter refused to load its own data file. I cursed a bit and
1804 started making the slides again from memory, to have something to
1805 present when I arrived. I tested that the saved files could be
1806 loaded, and the day seemed to be rescued. I continued to polish the
1807 slides until I suddenly discovered that the saved file could no longer
1808 be loaded into kpresenter. In the end I had to rewrite the slides
1809 three times, condensing the content until the talk became shorter and
1810 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
1811 kpresenter wrote inline images in a way itself could not understand.
1812 Eventually that bug was fixed and kpresenter ended up being a great
1813 program to make slides. The point I&#39;m trying to make is that we
1814 expect a program to be able to load its own data files, and it is
1815 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
1816
1817 &lt;p&gt;Did you ever experience a program failing to load its own data
1818 files from the desktop file browser? It is not a uncommon problem. A
1819 while back I discovered that the screencast recorder
1820 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1821 browser would refuse to open. No video player claimed to understand
1822 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
1823 returning the application/ogg MIME type, which no video player I had
1824 installed listed as a MIME type they would understand. I asked for
1825 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
1826 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
1827 several video players to add video/ogg to their desktop files, to give
1828 the file browser an idea what to do about Ogg Theora files. After a
1829 while, the desktop file browsers in Debian started to handle the
1830 output from gtk-recordmydesktop properly.&lt;/p&gt;
1831
1832 &lt;p&gt;But history repeats itself. A few days ago I tested the music
1833 system Rosegarden again, and I discovered that the KDE and xfce file
1834 browsers did not know what to do with the Rosegarden project files
1835 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
1836 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
1837 included in the next upload. To increase the chance of me remembering
1838 how to fix the problem next time some program fail to load its files
1839 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
1840
1841 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
1842 There are two sources for the MIME type of a given file. The output from
1843 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
1844 shared MIME type registry (under /usr/share/mime/). The file MIME
1845 type is mapped to programs supporting the MIME type, and this
1846 information is collected from
1847 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
1848 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
1849 one desktop file claiming support for the MIME type of the file, it is
1850 activated when asking to open a given file. If there are more, one
1851 can normally select which one to use by right-clicking on the file and
1852 selecting the wanted one using &#39;Open with&#39; or similar. In general
1853 this work well. But it depend on each program picking a good MIME
1854 type (preferably
1855 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
1856 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
1857 registry recognizing the file and the desktop file to list the MIME
1858 type in its list of supported MIME types.&lt;/p&gt;
1859
1860 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
1861 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
1862 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
1863
1864 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1865 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
1866 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
1867 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
1868 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
1869 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
1870 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
1871 &amp;lt;/mime-type&amp;gt;
1872 &amp;lt;/mime-info&amp;gt;
1873 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1874
1875 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
1876 (it is a gzipped XML file). Note, it is much better to use an
1877 official MIME type registered with IANA than it is to make up ones own
1878 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
1879
1880 &lt;p&gt;The desktop file of the rosegarden program failed to list
1881 audio/x-rosegarden in its list of supported MIME types, causing the
1882 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
1883
1884 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1885 % grep Mime /usr/share/applications/rosegarden.desktop
1886 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1887 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1888 %
1889 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1890
1891 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
1892 MimeType= line.&lt;/p&gt;
1893
1894 &lt;p&gt;If you run into a file which fail to open the correct program when
1895 selected from the file browser, please check out the output from
1896 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
1897 MIME type is registered somewhere under /usr/share/mime/ and check
1898 that some desktop file under /usr/share/applications/ is claiming
1899 support for this MIME type. If not, please report a bug to have it
1900 fixed. :)&lt;/p&gt;
1901 </description>
1902 </item>
1903
1904 <item>
1905 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
1906 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
1907 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
1908 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
1909 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
1910 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
1911 related packages. The idea is to have a database of mappings between
1912 hardware and packages, and pop up a dialog suggesting for the user to
1913 install the packages to use a given hardware dongle. Some use cases
1914 are when you insert a Yubikey, it proposes to install the software
1915 needed to control it; when you insert a braille reader list it
1916 proposes to install the packages needed to send text to the reader;
1917 and when you insert a ColorHug screen calibrator it suggests to
1918 install the driver for it. The system work well, and even have a few
1919 command line tools to install firmware packages and packages for the
1920 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
1921
1922 &lt;p&gt;The system was initially written using aptdaemon, because I found
1923 good documentation and example code on how to use it. But aptdaemon
1924 is going away and is generally being replaced by
1925 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
1926 so Isenkram needed a rewrite. And today, thanks to the great patch
1927 from my college Sunil Mohan Adapa in the FreedomBox project, the
1928 rewrite finally took place. I&#39;ve just uploaded a new version of
1929 Isenkram into Debian Unstable with the patch included, and the default
1930 for the background daemon is now to use PackageKit. To check it out,
1931 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
1932 and see if it is recognised.&lt;/p&gt;
1933
1934 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
1935 the machine it is running on, you can check out the isenkram-lookup
1936 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
1937
1938 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1939 % isenkram-lookup
1940 bluez
1941 cheese
1942 fprintd
1943 fprintd-demo
1944 gkrellm-thinkbat
1945 hdapsd
1946 libpam-fprintd
1947 pidgin-blinklight
1948 thinkfan
1949 tleds
1950 tp-smapi-dkms
1951 tp-smapi-source
1952 tpb
1953 %p
1954 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1955
1956 &lt;p&gt;The hardware mappings come from several places. The preferred way
1957 is for packages to announce their hardware support using
1958 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
1959 cross distribution appstream system&lt;/a&gt;.
1960 See
1961 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
1962 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
1963 </description>
1964 </item>
1965
1966 <item>
1967 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
1968 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
1969 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
1970 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
1971 <description>&lt;p&gt;Yesterday I updated the
1972 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
1973 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
1974 enterprising users. There were some nice user and visible changes.
1975 First of all, both desktop menu entries now work. A design flaw in
1976 one of the script made the history graph fail to show up (its PNG was
1977 dumped in ~/.xsession-errors) if no controlling TTY was available.
1978 The script worked when called from the command line, but not when
1979 called from the desktop menu. I changed this to look for a DISPLAY
1980 variable or a TTY before deciding where to draw the graph, and now the
1981 graph window pop up as expected.&lt;/p&gt;
1982
1983 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
1984 graphs (the one showing the last few hours). New is also the user of
1985 colours showing charging in blue and discharge in red. The percentages
1986 of this graph is relative to last full charge, not battery design
1987 capacity.&lt;/p&gt;
1988
1989 &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;
1990
1991 &lt;p&gt;The other graph show the entire history of the collected battery
1992 statistics, comparing it to the design capacity of the battery to
1993 visualise how the battery life time get shorter over time. The red
1994 line in this graph is what the previous graph considers 100 percent:
1995
1996 &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;
1997
1998 &lt;p&gt;In this graph you can see that I only charge the battery to 80
1999 percent of last full capacity, and how the capacity of the battery is
2000 shrinking. :(&lt;/p&gt;
2001
2002 &lt;p&gt;The last new feature is in the collector, which now will handle
2003 more hardware models. On some hardware, Linux power supply
2004 information is stored in /sys/class/power_supply/ACAD/, while the
2005 collector previously only looked in /sys/class/power_supply/AC/. Now
2006 both are checked to figure if there is power connected to the
2007 machine.&lt;/p&gt;
2008
2009 &lt;p&gt;If you are interested in how your laptop battery is doing, please
2010 check out the
2011 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
2012 in Debian unstable, or rebuild it on Jessie to get it working on
2013 Debian stable. :) The upstream source is available from &lt;a
2014 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2015 Patches are very welcome.&lt;/p&gt;
2016
2017 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2018 activities, please send Bitcoin donations to my address
2019 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2020 </description>
2021 </item>
2022
2023 <item>
2024 <title>Debian now with ZFS on Linux included</title>
2025 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
2026 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
2027 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
2028 <description>&lt;p&gt;Today, after many years of hard work from many people,
2029 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
2030 Debian. The package status can be seen on
2031 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
2032 for zfs-linux&lt;/a&gt;. and
2033 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
2034 team status page&lt;/a&gt;. If you want to help out, please join us.
2035 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
2036 source code&lt;/a&gt; is available via git on Alioth. It would also be
2037 great if you could help out with
2038 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
2039 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
2040 </description>
2041 </item>
2042
2043 <item>
2044 <title>What is the best multimedia player in Debian?</title>
2045 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
2046 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
2047 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
2048 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
2049 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
2050
2051 &lt;p&gt;A few years ago, I had a look at the media support for Browser
2052 plugins in Debian, to get an idea which plugins to include in Debian
2053 Edu. I created a script to extract the set of supported MIME types
2054 for each plugin, and used this to find out which multimedia browser
2055 plugin supported most file formats / media types.
2056 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
2057 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
2058 not been updated for a while. But browser plugins are less relevant
2059 these days, so I thought it was time to look at standalone
2060 players.&lt;/p&gt;
2061
2062 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
2063 player when I wanted to play videos from the Norwegian National
2064 Broadcasting Company, and decided to investigate why. The cause is a
2065 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
2066 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
2067 of MIME types announced in the desktop file and the browser plugin,
2068 only to discover that there is quite a large difference between the
2069 two for VLC. This discovery made me dig up the script I used to
2070 compare browser plugins, and adjust it to compare desktop files
2071 instead, to try to figure out which multimedia player in Debian
2072 support most file formats.&lt;/p&gt;
2073
2074 &lt;p&gt;The result can be seen on the Debian Wiki, as
2075 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
2076 table listing all MIME types supported by one of the packages included
2077 in the table&lt;/a&gt;, with the package supporting most MIME types being
2078 listed first in the table.&lt;/p&gt;
2079
2080 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
2081 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2082 kmplayer. Time for the other players to update their announced MIME
2083 support?&lt;/p&gt;
2084 </description>
2085 </item>
2086
2087 <item>
2088 <title>The Pyra - handheld computer with Debian preinstalled</title>
2089 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
2090 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
2091 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
2092 <description>A friend of mine made me aware of
2093 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
2094 handheld computer which will be delivered with Debian preinstalled. I
2095 would love to get one of those for my birthday. :)&lt;/p&gt;
2096
2097 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2098 plugs and many others connectors, and include a full keyboard and a 5&quot;
2099 LCD touch screen. The 6000mAh battery is claimed to provide a whole
2100 day of battery life time, but I have not seen any independent tests
2101 confirming this. The vendor is still collecting preorders, and the
2102 last I heard last night was that 22 more orders were needed before
2103 production started.&lt;/p&gt;
2104
2105 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
2106 Debian. Please let me know if you know of any others. Is it the
2107 first computer being sold with Debian preinstalled?&lt;/p&gt;
2108 </description>
2109 </item>
2110
2111 <item>
2112 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
2113 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
2114 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
2115 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
2116 <description>&lt;p&gt;During this weekends
2117 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
2118 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
2119 to make sure there are good books about Debian available in Norwegian
2120 Bokmål, and got in touch with the people behind the
2121 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
2122 project&lt;/a&gt; to get started. If you want to help out, please start
2123 contributing using
2124 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
2125 hosted weblate project page&lt;/a&gt;, and get in touch using
2126 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
2127 translators mailing list&lt;/a&gt;. Please also check out
2128 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
2129 contributors&lt;/a&gt;.&lt;/p&gt;
2130
2131 &lt;p&gt;The book is already available on paper in English, French and
2132 Japanese, and our goal is to get it available on paper in Norwegian
2133 Bokmål too. In addition to the paper edition, there are also EPUB and
2134 Mobi versions available. And there are incomplete translations
2135 available for many more languages.&lt;/p&gt;
2136 </description>
2137 </item>
2138
2139 <item>
2140 <title>One in two hundred Debian users using ZFS on Linux?</title>
2141 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
2142 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
2143 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
2144 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
2145 packages in Debian, and was quite surprised with what I found. I use
2146 ZFS myself at home, but did not really expect many others to do so.
2147 But I might be wrong.&lt;/p&gt;
2148
2149 &lt;p&gt;According to
2150 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
2151 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
2152 0.53% of the population, with the package installed. As far as I know
2153 the only use of the spl-linux package is as a support library for ZFS
2154 on Linux, so I use it here as proxy for measuring the number of ZFS
2155 installation on Linux in Debian. In the kFreeBSD variant of Debian
2156 the ZFS feature is already available, and there
2157 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
2158 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
2159 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
2160
2161 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
2162 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
2163 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
2164 cleared, the package is still not in Debian. The package is again in
2165 the NEW queue. Several uploads have been rejected so far because the
2166 debian/copyright file was incomplete or wrong, but there is no reason
2167 to give up. The current status can be seen on
2168 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
2169 team status page&lt;/a&gt;, and
2170 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
2171 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
2172
2173 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
2174 my home server can function in the future using only official Debian
2175 packages, and the current blocker is to get the debian/copyright file
2176 accepted by the FTP masters in Debian, I decided a while back to try
2177 to help out the team. This was the background for my blog post about
2178 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
2179 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
2180 used the techniques I explored there to try to find any errors in the
2181 copyright file. It is not very easy to check every one of the around
2182 2000 files in the source package, but I hope we this time got it
2183 right. If you want to help out, check out the git source and try to
2184 find missing entries in the debian/copyright file.&lt;/p&gt;
2185 </description>
2186 </item>
2187
2188 <item>
2189 <title>Full battery stats collector is now available in Debian</title>
2190 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
2191 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
2192 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
2193 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
2194 extended collector that will collect the complete battery history for
2195 later processing and graphing. The original collector store the
2196 battery level as percentage of last full level, while the new
2197 collector also record battery vendor, model, serial number, design
2198 full level, last full level and current battery level. This make it
2199 possible to predict the lifetime of the battery as well as visualise
2200 the energy flow when the battery is charging or discharging.&lt;/p&gt;
2201
2202 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
2203 in the version 0.5.1 package in unstable. Get the new battery level graph
2204 and lifetime prediction by running:
2205
2206 &lt;p&gt;&lt;pre&gt;
2207 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2208 &lt;/pre&gt;&lt;/p&gt;
2209
2210 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
2211
2212 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
2213 entry yet):&lt;/p&gt;
2214
2215 &lt;p&gt;&lt;pre&gt;
2216 /usr/share/battery-stats/battery-stats-graph-flow
2217 &lt;/pre&gt;&lt;/p&gt;
2218
2219 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
2220 when there are few data points. The graphs look a bit better with a
2221 few years of data.&lt;/p&gt;
2222
2223 &lt;p&gt;A while back one important feature I use in the battery stats
2224 collector broke in Debian. The scripts in
2225 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
2226 suspect it happened when Jessie started using systemd, but I do not
2227 know. The issue is reported as
2228 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
2229 pm-utils. I managed to work around it by adding an udev rule to call
2230 the collector script every time the power connector is connected and
2231 disconnected. With this fix in place it was finally time to make a
2232 new release of the package, and get it into Debian.&lt;/p&gt;
2233
2234 &lt;p&gt;If you are interested in how your laptop battery is doing, please
2235 check out the
2236 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
2237 in Debian unstable, or rebuild it on Jessie to get it working on
2238 Debian stable. :) The upstream source is available from
2239 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2240 As always, patches are very welcome.&lt;/p&gt;
2241 </description>
2242 </item>
2243
2244 <item>
2245 <title>Making battery measurements a little easier in Debian</title>
2246 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
2247 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
2248 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
2249 <description>&lt;p&gt;Back in September, I blogged about
2250 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
2251 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
2252 how it showed the decay and death of this battery (now replaced). I
2253 created a simple deb package to handle the collection and graphing,
2254 but did not want to upload it to Debian as there were already
2255 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
2256 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
2257 a point of uploading a competing package when battery-stats could be
2258 fixed instead. I reported a few bugs about its non-function, and
2259 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
2260
2261 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
2262 hands. The end result is that I am now the new upstream developer of
2263 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
2264 battery-stats in Debian, and the package in Debian unstable is finally
2265 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
2266 information provided by the Linux kernel. If you install the
2267 battery-stats package from unstable now, you will be able to get a
2268 graph of the current battery fill level, to get some idea about the
2269 status of the battery. The source package build and work just fine in
2270 Debian testing and stable (and probably oldstable too, but I have not
2271 tested). The default graph you get for that system look like this:&lt;/p&gt;
2272
2273 &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;
2274
2275 &lt;p&gt;My plans for the future is to merge my old scripts into the
2276 battery-stats package, as my old scripts collected a lot more details
2277 about the battery. The scripts are merged into the upstream
2278 battery-stats git repository already, but I am not convinced they work
2279 yet, as I changed a lot of paths along the way. Will have to test a
2280 bit more before I make a new release.&lt;/p&gt;
2281
2282 &lt;p&gt;I will also consider changing the file format slightly, as I
2283 suspect the way I combine several values into one field might make it
2284 impossible to know the type of the value when using it for processing
2285 and graphing.&lt;/p&gt;
2286
2287 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
2288 battery, check out the battery-stats package in
2289 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
2290 on
2291 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2292 I would love some help to improve the system further.&lt;/p&gt;
2293 </description>
2294 </item>
2295
2296 <item>
2297 <title>Creating, updating and checking debian/copyright semi-automatically</title>
2298 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
2299 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
2300 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
2301 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
2302 details. And one of the details is the content of the
2303 debian/copyright file, which should list all relevant licenses used by
2304 the code in the package in question, preferably in
2305 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
2306 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
2307
2308 &lt;p&gt;For large packages with lots of contributors it is hard to write
2309 and update this file manually, and if you get some detail wrong, the
2310 package is normally rejected by the ftpmasters. So getting it right
2311 the first time around get the package into Debian faster, and save
2312 both you and the ftpmasters some work.. Today, while trying to figure
2313 out what was wrong with
2314 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
2315 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
2316 figuring out the options for doing this job automatically, or at least
2317 semi-automatically.&lt;/p&gt;
2318
2319 &lt;p&gt;Lucikly, there are at least two tools available for generating the
2320 file based on the code in the source package,
2321 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
2322 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
2323 not sure which one of them came first, but both seem to be able to
2324 create a sensible draft file. As far as I can tell, none of them can
2325 be trusted to get the result just right, so the content need to be
2326 polished a bit before the file is OK to upload. I found the debmake
2327 option in
2328 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
2329 blog posts from 2014&lt;/a&gt;.
2330
2331 &lt;p&gt;To generate using debmake, use the -cc option:
2332
2333 &lt;p&gt;&lt;pre&gt;
2334 debmake -cc &gt; debian/copyright
2335 &lt;/pre&gt;&lt;/p&gt;
2336
2337 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
2338 this might not be the best option.&lt;/p&gt;
2339
2340 &lt;p&gt;The cme option is based on a config parsing library, and I found
2341 this approach in
2342 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
2343 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
2344 dpkg-copyright&#39; option:
2345
2346 &lt;p&gt;&lt;pre&gt;
2347 cme update dpkg-copyright
2348 &lt;/pre&gt;&lt;/p&gt;
2349
2350 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
2351 handle UTF-8 names better than debmake.&lt;/p&gt;
2352
2353 &lt;p&gt;When the copyright file is created, I would also like some help to
2354 check if the file is correct. For this I found two good options,
2355 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
2356 to focus on license types and file matching, and is able to detect
2357 ineffective blocks in the copyright file. The latter reports missing
2358 copyright holders and years, but was confused by inconsistent license
2359 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
2360 fix all issues reported by them before uploading. But I do not know
2361 if the tools and the ftpmasters agree on what is important to fix in a
2362 copyright file, so the package might still be rejected.&lt;/p&gt;
2363
2364 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
2365 will read through the source and try to find all copyright statements.
2366 It is not comparing the result to the content of debian/copyright, but
2367 can be useful when verifying the content of the copyright file.&lt;/p&gt;
2368
2369 &lt;p&gt;Are you aware of better tools in Debian to create and update
2370 debian/copyright file. Please let me know, or blog about it on
2371 planet.debian.org.&lt;/p&gt;
2372
2373 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2374 activities, please send Bitcoin donations to my address
2375 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2376
2377 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
2378 on how to use licensecheck and cdbs to create a draft copyright file
2379
2380 &lt;p&gt;&lt;pre&gt;
2381 licensecheck --copyright -r `find * -type f` | \
2382 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
2383 &lt;/pre&gt;&lt;/p&gt;
2384
2385 &lt;p&gt;He mentioned that he normally check the generated file into the
2386 version control system to make it easier to discover license and
2387 copyright changes in the upstream source. I will try to do the same
2388 with my packages in the future.&lt;/p&gt;
2389
2390 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
2391 against using -quiet for new users, so I removed it from the proposed
2392 command line.&lt;/p&gt;
2393 </description>
2394 </item>
2395
2396 <item>
2397 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
2398 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
2399 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
2400 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
2401 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
2402 is taking shape in Debian, and one provided feature is a very
2403 convenient way to tell you which package to install to make a given
2404 firmware file available when the kernel is looking for it. This can
2405 be done using apt-file too, but that is for someone else to blog
2406 about. :)&lt;/p&gt;
2407
2408 &lt;p&gt;Here is a small recipe to find the package with a given firmware
2409 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
2410 picked from the set of firmware announced using appstream in Debian
2411 unstable. In general you would be looking for the firmware requested
2412 by the kernel during kernel module loading. To find the package
2413 providing the example file, do like this:&lt;/p&gt;
2414
2415 &lt;blockquote&gt;&lt;pre&gt;
2416 % apt install appstream
2417 [...]
2418 % apt update
2419 [...]
2420 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
2421 awk &#39;/Package:/ {print $2}&#39;
2422 firmware-qlogic
2423 %
2424 &lt;/pre&gt;&lt;/blockquote&gt;
2425
2426 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
2427 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
2428 a way appstream can use.&lt;/p&gt;
2429
2430 &lt;p&gt;This same approach can be used to find any package supporting a
2431 given MIME type. This is very useful when you get a file you do not
2432 know how to handle. First find the mime type using &lt;tt&gt;file
2433 --mime-type&lt;/tt&gt;, and next look up the package providing support for
2434 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2435 and you can find all packages handling this type like this:&lt;/p&gt;
2436
2437 &lt;blockquote&gt;&lt;pre&gt;
2438 % apt install appstream
2439 [...]
2440 % apt update
2441 [...]
2442 % appstreamcli what-provides mimetype image/svg+xml | \
2443 awk &#39;/Package:/ {print $2}&#39;
2444 bkchem
2445 phototonic
2446 inkscape
2447 shutter
2448 tetzle
2449 geeqie
2450 xia
2451 pinta
2452 gthumb
2453 karbon
2454 comix
2455 mirage
2456 viewnior
2457 postr
2458 ristretto
2459 kolourpaint4
2460 eog
2461 eom
2462 gimagereader
2463 midori
2464 %
2465 &lt;/pre&gt;&lt;/blockquote&gt;
2466
2467 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
2468 packages providing appstream metadata.&lt;/p&gt;
2469 </description>
2470 </item>
2471
2472 <item>
2473 <title>Creepy, visualise geotagged social media information - nice free software</title>
2474 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
2475 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
2476 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
2477 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
2478 with the computerised radio beacon known as a mobile phone their
2479 position is tracked by the phone company and often stored for a long
2480 time (like every time a SMS is received or sent). And if their
2481 computerised radio beacon is capable of running programs (often called
2482 mobile apps) downloaded from the Internet, these programs are often
2483 also capable of tracking their location (if the app requested access
2484 during installation). And when these programs send out information to
2485 central collection points, the location is often included, unless
2486 extra care is taken to not send the location. The provided
2487 information is used by several entities, for good and bad (what is
2488 good and bad, depend on your point of view). What is certain, is that
2489 the private sphere and the right to free movement is challenged and
2490 perhaps even eradicated for those announcing their location this way,
2491 when they share their whereabouts with private and public
2492 entities.&lt;/p&gt;
2493
2494 &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;
2495
2496 &lt;p&gt;The phone company logs provide a register of locations to check out
2497 when one want to figure out what the tracked person was doing. It is
2498 unavailable for most of us, but provided to selected government
2499 officials, company staff, those illegally buying information from
2500 unfaithful servants and crackers stealing the information. But the
2501 public information can be collected and analysed, and a free software
2502 tool to do so is called
2503 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
2504 discovered it when I read
2505 &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
2506 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
2507 November 2014, and decided to check if it was available in Debian.
2508 The python program was in Debian, but
2509 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
2510 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
2511 uploaded a new version which did not work quite right, but did not
2512 have time to fix it then. This Christmas I decided to finally try to
2513 get Creepy operational in Debian. Now a fixed version is available in
2514 Debian unstable and testing, and almost all Debian specific patches
2515 are now included
2516 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
2517
2518 &lt;p&gt;The Creepy program visualises geolocation information fetched from
2519 Twitter, Instagram, Flickr and Google+, and allow one to get a
2520 complete picture of every social media message posted recently in a
2521 given area, or track the movement of a given individual across all
2522 these services. Earlier it was possible to use the search API of at
2523 least some of these services without identifying oneself, but these
2524 days it is impossible. This mean that to use Creepy, you need to
2525 configure it to log in as yourself on these services, and provide
2526 information to them about your search interests. This should be taken
2527 into account when using Creepy, as it will also share information
2528 about yourself with the services.&lt;/p&gt;
2529
2530 &lt;p&gt;The picture above show the twitter messages sent from (or at least
2531 geotagged with a position from) the city centre of Oslo, the capital
2532 of Norway. One useful way to use Creepy is to first look at
2533 information tagged with an area of interest, and next look at all the
2534 information provided by one or more individuals who was in the area.
2535 I tested it by checking out which celebrity provide their location in
2536 twitter messages by checkout out who sent twitter messages near a
2537 Norwegian TV station, and next could track their position over time,
2538 making it possible to locate their home and work place, among other
2539 things. A similar technique have been
2540 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
2541 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
2542 tool to discover lying governments, and a useful tool to help people
2543 understand the value of the private information they provide to the
2544 public.&lt;/p&gt;
2545
2546 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
2547 it depend on several python modules currently missing in Jessie (at
2548 least python-instagram, python-flickrapi and
2549 python-requests-toolbelt).&lt;/p&gt;
2550
2551 &lt;p&gt;(I have uploaded
2552 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
2553 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
2554 Creepy program in Debian.)&lt;/p&gt;
2555 </description>
2556 </item>
2557
2558 <item>
2559 <title>Always download Debian packages using Tor - the simple recipe</title>
2560 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
2561 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
2562 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
2563 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
2564 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
2565 that those listening on the Internet lines would have good reason to
2566 believe a computer have a given security hole&lt;/a&gt; if it download a
2567 security fix from a Debian mirror. This is a good reason to always
2568 use encrypted connections to the Debian mirror, to make sure those
2569 listening do not know which IP address to attack. In August, Richard
2570 Hartmann observed that encryption was not enough, when it was possible
2571 to interfere download size to security patches or the fact that
2572 download took place shortly after a security fix was released, and
2573 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
2574 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
2575 was not the first to propose this, as the
2576 &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;
2577 package by Tim Retout already existed to make it easy to convince apt
2578 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
2579 aware of that package when I read the blog post from Richard.&lt;/p&gt;
2580
2581 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
2582 sysadmins, and he set up a Tor hidden service on one of the central
2583 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2584 it possible to download packages directly between two tor nodes,
2585 making sure the network traffic always were encrypted.&lt;/p&gt;
2586
2587 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
2588 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
2589 urls with tor+http and tor+https, and using the hidden service instead
2590 of the official Debian mirror site. I recommend installing
2591 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
2592 done in /etc/.&lt;/p&gt;
2593
2594 &lt;blockquote&gt;&lt;pre&gt;
2595 apt install apt-transport-tor
2596 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
2597 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
2598 &lt;/pre&gt;&lt;/blockquote&gt;
2599
2600 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
2601 the sed commands for these too. The sed command is assuming your are
2602 using the ftp.debian.org Debian mirror. Adjust the command (or just
2603 edit the file manually) to match your mirror.&lt;/p&gt;
2604
2605 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
2606 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
2607 system, and do not work with these tor+http URLs. For
2608 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
2609 which need a recent apt version currently only in unstable. So if you
2610 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
2611
2612 &lt;p&gt;Another advantage from this change is that your machine will start
2613 using Tor regularly and at fairly random intervals (every time you
2614 update the package lists or upgrade or install a new package), thus
2615 masking other Tor traffic done from the same machine. Using Tor will
2616 become normal for the machine in question.&lt;/p&gt;
2617
2618 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
2619 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
2620 enabled. It would be great if it was the default on any Debian
2621 system.&lt;/p&gt;
2622 </description>
2623 </item>
2624
2625 <item>
2626 <title>OpenALPR, find car license plates in video streams - nice free software</title>
2627 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
2628 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
2629 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
2630 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
2631 call the car license plate numbers in those days. I would write the
2632 numbers down in my little book and compare notes with the other kids
2633 to see how many region codes we had seen and if we had seen some
2634 exotic or special region codes and numbers. It was a fun game to pass
2635 time, as we kids have plenty of it.&lt;/p&gt;
2636
2637 &lt;p&gt;A few days I came across
2638 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
2639 project&lt;/a&gt;, a free software project to automatically discover and
2640 report license plates in images and video streams, and provide the
2641 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
2642 such system for a while now, because I believe it is a bad idea that the
2643 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
2644 number plate recognition&lt;/a&gt; tool only is available in the hands of
2645 the powerful, and want it to be available also for the powerless to
2646 even the score when it comes to surveillance and sousveillance. I
2647 discovered the developer
2648 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
2649 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
2650 help him get it into shape to get the package uploaded into the Debian
2651 archive.&lt;/p&gt;
2652
2653 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
2654 it into Debian, where it currently
2655 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
2656 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
2657
2658 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
2659 for the common folks, ie those not running a large government
2660 surveillance system? Well, I plan to put it in a computer on my bike
2661 and in my car, tracking the cars nearby and allowing me to be notified
2662 when number plates on my watch list are discovered. Another use case
2663 was suggested by a friend of mine, who wanted to set it up at his home
2664 to open the car port automatically when it discovered the plate on his
2665 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2666 capable of placing his license plate number of a piece of cardboard to
2667 open his car port, men replied that it was always unlocked anyway. I
2668 guess for such use case it make sense. I am sure there are other use
2669 cases too, for those with imagination and a vision.&lt;/p&gt;
2670
2671 &lt;p&gt;If you want to build your own version of the Debian package, check
2672 out the upstream git source and symlink ./distros/debian to ./debian/
2673 before running &quot;debuild&quot; to build the source. Or wait a bit until the
2674 package show up in unstable.&lt;/p&gt;
2675 </description>
2676 </item>
2677
2678 <item>
2679 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
2680 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
2681 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
2682 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
2683 <description>&lt;p&gt;Around three years ago, I created
2684 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
2685 system&lt;/a&gt; to get a more practical solution in Debian for handing
2686 hardware related packages. A GUI system in the isenkram package will
2687 present a pop-up dialog when some hardware dongle supported by
2688 relevant packages in Debian is inserted into the machine. The same
2689 lookup mechanism to detect packages is available as command line
2690 tools in the isenkram-cli package. In addition to mapping hardware,
2691 it will also map kernel firmware files to packages and make it easy to
2692 install needed firmware packages automatically. The key for this
2693 system to work is a good way to map hardware to packages, in other
2694 words, allow packages to announce what hardware they will work
2695 with.&lt;/p&gt;
2696
2697 &lt;p&gt;I started by providing data files in the isenkram source, and
2698 adding code to download the latest version of these data files at run
2699 time, to ensure every user had the most up to date mapping available.
2700 I also added support for storing the mapping in the Packages file in
2701 the apt repositories, but did not push this approach because while I
2702 was trying to figure out how to best store hardware/package mappings,
2703 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
2704 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
2705 add the hardware mapping into that data set to be able to use
2706 appstream as a data source, and this was accepted at least for the
2707 Debian version of appstream.&lt;/p&gt;
2708
2709 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
2710 and today I uploaded a new version 0.20 of isenkram adding support for
2711 appstream as a data source for mapping hardware to packages. The only
2712 package so far using appstream to announce its hardware support is my
2713 pymissile package. I got help from Matthias Klumpp with figuring out
2714 how do add the required
2715 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
2716 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
2717 this content:&lt;/p&gt;
2718
2719 &lt;blockquote&gt;&lt;pre&gt;
2720 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
2721 &amp;lt;component&amp;gt;
2722 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
2723 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
2724 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
2725 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
2726 &amp;lt;description&amp;gt;
2727 &amp;lt;p&amp;gt;
2728 Pymissile provides a curses interface to control an original
2729 Marks and Spencer / Striker USB Missile Launcher, as well as a
2730 motion control script to allow a webcamera to control the
2731 launcher.
2732 &amp;lt;/p&amp;gt;
2733 &amp;lt;/description&amp;gt;
2734 &amp;lt;provides&amp;gt;
2735 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
2736 &amp;lt;/provides&amp;gt;
2737 &amp;lt;/component&amp;gt;
2738 &lt;/pre&gt;&lt;/blockquote&gt;
2739
2740 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
2741 which is a glob style match rule for hardware specific strings
2742 (modalias strings) provided by the Linux kernel. In this case, it
2743 will map to all USB devices with vendor code 1130 and product code
2744 0202.&lt;/p&gt;
2745
2746 &lt;p&gt;Note, it is important that the license of all the metadata files
2747 are compatible to have permissions to aggregate them into archive wide
2748 appstream files. Matthias suggested to use MIT or BSD licenses for
2749 these files. A challenge is figuring out a good id for the data, as
2750 it is supposed to be globally unique and shared across distributions
2751 (in other words, best to coordinate with upstream what to use). But
2752 it can be changed later or, so we went with the package name as
2753 upstream for this project is dormant.&lt;/p&gt;
2754
2755 &lt;p&gt;To get the metadata file installed in the correct location for the
2756 mirror update scripts to pick it up and include its content the
2757 appstream data source, the file must be installed in the binary
2758 package under /usr/share/appdata/. I did this by adding the following
2759 line to debian/pymissile.install:&lt;/p&gt;
2760
2761 &lt;blockquote&gt;&lt;pre&gt;
2762 debian/pymissile.metainfo.xml usr/share/appdata
2763 &lt;/pre&gt;&lt;/blockquote&gt;
2764
2765 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
2766 all packages useful on the current computer automatically, and the GUI
2767 pop-up handler will propose to install the package not already
2768 installed if a hardware dongle is inserted into the machine in
2769 question.&lt;/p&gt;
2770
2771 &lt;p&gt;Details of the modalias field in appstream is available from the
2772 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
2773
2774 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
2775 try running this command on the command line:&lt;/p&gt;
2776
2777 &lt;blockquote&gt;&lt;pre&gt;
2778 cat $(find /sys/devices/|grep modalias)
2779 &lt;/pre&gt;&lt;/blockquote&gt;
2780
2781 &lt;p&gt;To learn more about the isenkram system, please check out
2782 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
2783 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
2784 </description>
2785 </item>
2786
2787 <item>
2788 <title>The GNU General Public License is not magic pixie dust</title>
2789 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
2790 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
2791 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
2792 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
2793 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
2794 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
2795 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
2796 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
2797
2798 &lt;blockquote&gt;
2799
2800 &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;
2801
2802 &lt;blockquote&gt;
2803 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
2804
2805 The first step is to choose a
2806 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
2807 code.&lt;br/&gt;
2808
2809 The next step is, when someone fails to follow that copyleft license,
2810 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
2811
2812 and its a simple fact of our modern society that such type of
2813 work&lt;br/&gt;
2814
2815 is incredibly expensive to do and incredibly difficult to do.
2816 &lt;/blockquote&gt;
2817
2818 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
2819 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
2820 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
2821 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
2822
2823 &lt;p&gt;As the Debian Website
2824 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
2825 &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;
2826 imply, public domain and permissively licensed software can lead to
2827 the production of more proprietary software as people discover useful
2828 software, extend it and or incorporate it into their hardware or
2829 software products. Copyleft licenses such as the GNU GPL were created
2830 to close off this avenue to the production of proprietary software but
2831 such licenses are not enough. With the ongoing adoption of Free
2832 Software by individuals and groups, inevitably the community&#39;s
2833 expectations of license compliance are violated, usually out of
2834 ignorance of the way Free Software works, but not always. As Karen
2835 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
2836 Freedom&quot;&gt;FaiF&lt;/a&gt;
2837 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
2838 copyleft is nothing if no-one is willing and able to stand up in court
2839 to protect it. The reality of today&#39;s world is that legal
2840 representation is expensive, difficult and time consuming. With
2841 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
2842 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
2843 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
2844 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
2845 of the Linux project, Debian and other groups against GPL violations.
2846 In March the SFC supported a
2847 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
2848 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
2849 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
2850 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
2851 kernel. Since then two of their sponsors pulled corporate funding and
2852 conferences
2853 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
2854 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
2855 less on corporate funding and more on the broad community of
2856 individuals who support Free Software and copyleft. So the SFC has
2857 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
2858 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
2859 a community of folks who stand up for copyleft and the GPL by
2860 supporting their work on promoting and supporting copyleft and Free
2861 Software.&lt;/p&gt;
2862
2863 &lt;p&gt;If you support Free Software,
2864 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
2865 what the SFC do, agree with their
2866 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
2867 principles&lt;/a&gt;, are happy about their
2868 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
2869 work on a project that is an SFC
2870 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
2871 just want to stand up for copyleft, please join
2872 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
2873 Allan Webber&lt;/a&gt;,
2874 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
2875 Smith&lt;/a&gt;,
2876 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
2877 Bacon&lt;/a&gt;, myself and
2878 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
2879 becoming a
2880 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
2881 next week your donation will be
2882 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
2883 by an anonymous donor. Please also consider asking your employer to
2884 match your donation or become a sponsor of SFC. Don&#39;t forget to
2885 spread the word about your support for SFC via email, your blog and or
2886 social media accounts.&lt;/p&gt;
2887
2888 &lt;/blockquote&gt;
2889
2890 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
2891 of Software Freedom Conservancy myself. Perhaps you should be a
2892 supporter too?&lt;/p&gt;
2893 </description>
2894 </item>
2895
2896 <item>
2897 <title>PGP key transition statement for key EE4E02F9</title>
2898 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
2899 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
2900 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
2901 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
2902 set it up properly. I wanted to generate it offline and have it
2903 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
2904 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
2905 time to sit down with an offline machine almost took forever. But
2906 finally I&#39;ve been able to complete the process, and have now moved
2907 from my old GPG key to a new GPG key. See
2908 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
2909 full transition statement, signed with both my old and new key&lt;/a&gt; for
2910 the details. This is my new key:&lt;/p&gt;
2911
2912 &lt;pre&gt;
2913 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]
2914 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
2915 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
2916 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
2917 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
2918 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
2919 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
2920 &lt;/pre&gt;
2921
2922 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
2923 my old key.&lt;/p&gt;
2924
2925 &lt;p&gt;If you signed my old key
2926 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
2927 I&#39;d very much appreciate a signature on my new key, details and
2928 instructions in the transition statement. I m happy to reciprocate if
2929 you have a similarly signed transition statement to present.&lt;/p&gt;
2930 </description>
2931 </item>
2932
2933 <item>
2934 <title>The life and death of a laptop battery</title>
2935 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
2936 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
2937 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
2938 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
2939 But this do not last. The last few laptops gave me a feeling that
2940 within a year, the life time is just a fraction of what it used to be,
2941 and it slowly become painful to use the laptop without power connected
2942 all the time. Because of this, when I got a new Thinkpad X230 laptop
2943 about two years ago, I decided to monitor its battery state to have
2944 more hard facts when the battery started to fail.&lt;/p&gt;
2945
2946 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
2947
2948 &lt;p&gt;First I tried to find a sensible Debian package to record the
2949 battery status, assuming that this must be a problem already handled
2950 by someone else. I found
2951 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
2952 which collects statistics from the battery, but it was completely
2953 broken. I sent a few suggestions to the maintainer, but decided to
2954 write my own collector as a shell script while I waited for feedback
2955 from him. Via
2956 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
2957 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
2958 discovered
2959 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
2960 available in Debian.&lt;/p&gt;
2961
2962 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
2963 battery stats ever since. Now my
2964 /var/log/hjemmenett-battery-status.log file contain around 115,000
2965 measurements, from the time the battery was working great until now,
2966 when it is unable to charge above 7% of original capacity. My
2967 collector shell script is quite simple and look like this:&lt;/p&gt;
2968
2969 &lt;pre&gt;
2970 #!/bin/sh
2971 # Inspired by
2972 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
2973 # See also
2974 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
2975 logfile=/var/log/hjemmenett-battery-status.log
2976
2977 files=&quot;manufacturer model_name technology serial_number \
2978 energy_full energy_full_design energy_now cycle_count status&quot;
2979
2980 if [ ! -e &quot;$logfile&quot; ] ; then
2981 (
2982 printf &quot;timestamp,&quot;
2983 for f in $files; do
2984 printf &quot;%s,&quot; $f
2985 done
2986 echo
2987 ) &gt; &quot;$logfile&quot;
2988 fi
2989
2990 log_battery() {
2991 # Print complete message in one echo call, to avoid race condition
2992 # when several log processes run in parallel.
2993 msg=$(printf &quot;%s,&quot; $(date +%s); \
2994 for f in $files; do \
2995 printf &quot;%s,&quot; $(cat $f); \
2996 done)
2997 echo &quot;$msg&quot;
2998 }
2999
3000 cd /sys/class/power_supply
3001
3002 for bat in BAT*; do
3003 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
3004 done
3005 &lt;/pre&gt;
3006
3007 &lt;p&gt;The script is called when the power management system detect a
3008 change in the power status (power plug in or out), and when going into
3009 and out of hibernation and suspend. In addition, it collect a value
3010 every 10 minutes. This make it possible for me know when the battery
3011 is discharging, charging and how the maximum charge change over time.
3012 The code for the Debian package
3013 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
3014 available on github&lt;/a&gt;.&lt;/p&gt;
3015
3016 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
3017
3018 &lt;pre&gt;
3019 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3020 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
3021 [...]
3022 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3023 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3024 &lt;/pre&gt;
3025
3026 &lt;p&gt;I wrote a small script to create a graph of the charge development
3027 over time. This graph depicted above show the slow death of my laptop
3028 battery.&lt;/p&gt;
3029
3030 &lt;p&gt;But why is this happening? Why are my laptop batteries always
3031 dying in a year or two, while the batteries of space probes and
3032 satellites keep working year after year. If we are to believe
3033 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
3034 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
3035 chance, and the fix is to not charge the Lithium-ion batteries to 100%
3036 all the time, but to stay below 90% of full charge most of the time.
3037 I&#39;ve been told that the Tesla electric cars
3038 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
3039 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
3040 100% when preparing for a longer trip (not that I would want a car
3041 like Tesla where rights to privacy is abandoned, but that is another
3042 story), which I guess is the option we should have for laptops on
3043 Linux too.&lt;/p&gt;
3044
3045 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
3046 stop charging at 80%, unless requested to charge to 100% once in
3047 preparation for a longer trip? I found
3048 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
3049 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3050 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
3051 load).&lt;/p&gt;
3052
3053 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
3054 at the start. I also wonder why the &quot;full capacity&quot; increases some
3055 times, and if it is possible to repeat the process to get the battery
3056 back to design capacity. And I wonder if the discharge and charge
3057 speed change over time, or if this stay the same. I did not yet try
3058 to write a tool to calculate the derivative values of the battery
3059 level, but suspect some interesting insights might be learned from
3060 those.&lt;/p&gt;
3061
3062 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
3063 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3064 packages instead of the tp-smapi-dkms package I had tried to use
3065 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
3066 and stop. I&#39;ve done so now, but expect my existing battery is toast
3067 and need to be replaced. The proposal is unfortunately Thinkpad
3068 specific.&lt;/p&gt;
3069 </description>
3070 </item>
3071
3072 <item>
3073 <title>New laptop - some more clues and ideas based on feedback</title>
3074 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
3075 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
3076 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
3077 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
3078 need for a new laptop, and provided very useful feedback. I wish to
3079 thank every one of these. Several pointed me to the possibility of
3080 fixing my X230, and I am already in the process of getting Lenovo to
3081 do so thanks to the on site, next day support contract covering the
3082 machine. But the battery is almost useless (I expect to replace it
3083 with a non-official battery) and I do not expect the machine to live
3084 for many more years, so it is time to plan its replacement. If I did
3085 not have a support contract, it was suggested to find replacement parts
3086 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
3087 might present a language barrier as I do not understand French.&lt;/p&gt;
3088
3089 &lt;p&gt;One tip I got was to use the
3090 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
3091 compare laptop models. It seem to have more models available than
3092 prisjakt.no. Another tip I got from someone I know have similar
3093 keyboard preferences was that the HP EliteBook 840 keyboard is not
3094 very good, and this matches my experience with earlier EliteBook
3095 keyboards I tested. Because of this, I will not consider it any further.
3096
3097 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
3098 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3099 (which is missing from the X240), and is working fairly well with
3100 Debian Sid/Unstable according to
3101 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
3102 got on the keyboard quality are not consistent. Some say the keyboard
3103 is good, others say it is ok, while others say it is not very good.
3104 Those with experience from X41 and and X60 agree that the X250
3105 keyboard is not as good as those trusty old laptops, and suggest I
3106 keep and fix my X230 instead of upgrading, or get a used X230 to
3107 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
3108 activity and battery status, which is very convenient on my X230. I&#39;m
3109 also told that the CPU fan is running very often, making it a bit
3110 noisy. In any case, the X250 do not work out of the box with Debian
3111 Stable/Jessie, one of my requirements.&lt;/p&gt;
3112
3113 &lt;p&gt;I have also gotten a few vendor proposals, one was
3114 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
3115 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
3116 The latter look very attractive to me.&lt;/p&gt;
3117
3118 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
3119 as I keep looking for a replacement.&lt;/p&gt;
3120
3121 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
3122 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
3123 different
3124 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
3125 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
3126 </description>
3127 </item>
3128
3129 <item>
3130 <title>Time to find a new laptop, as the old one is broken after only two years</title>
3131 <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>
3132 <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>
3133 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
3134 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
3135 replacement soon. The left 5 cm of the screen on my Thinkpad X230
3136 started flickering yesterday, and I suspect the cause is a broken
3137 cable, as changing the angle of the screen some times get rid of the
3138 flickering.&lt;/p&gt;
3139
3140 &lt;p&gt;My requirements have not really changed since I bought it, and is
3141 still as
3142 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
3143 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
3144 good help from
3145 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
3146 where I could select at least a few of the requirements (mouse pin,
3147 wifi, weight) and go through the rest manually. Three button mouse
3148 and a good keyboard is not available as an option, and all the three
3149 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
3150 G2) lack three mouse buttons). It is also unclear to me how good the
3151 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3152 the keyboard, even if the quality and robustness in the X series have
3153 deteriorated since X41.&lt;/p&gt;
3154
3155 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
3156 seem sensible to me? Are there better services around to search the
3157 set of available laptops for features? Please send me an email if you
3158 have suggestions.&lt;/p&gt;
3159
3160 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
3161 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
3162 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
3163 </description>
3164 </item>
3165
3166 <item>
3167 <title>How to stay with sysvinit in Debian Jessie</title>
3168 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
3169 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
3170 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
3171 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
3172 sysvinit as its boot system by default. But how can one keep using
3173 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3174 courtesy of
3175 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
3176 Schubert&lt;/a&gt; and
3177 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
3178 McVittie&lt;/a&gt;.
3179
3180 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
3181 keep sysvinit as your boot system, create a file
3182 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
3183 you upgrade:&lt;/p&gt;
3184
3185 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3186 Package: systemd-sysv
3187 Pin: release o=Debian
3188 Pin-Priority: -1
3189 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3190
3191 &lt;p&gt;This file content will tell apt and aptitude to not consider
3192 installing systemd-sysv as part of any installation and upgrade
3193 solution when resolving dependencies, and thus tell it to avoid
3194 systemd as a default boot system. The end result should be that the
3195 upgraded system keep using sysvinit.&lt;/p&gt;
3196
3197 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
3198 get sysvinit installed by default (debootstrap used by
3199 debian-installer have no option for this), but one can tell the
3200 installer to switch to sysvinit before the first boot. Either by
3201 using a kernel argument to the installer, or by adding a line to the
3202 preseed file used. First, the kernel command line argument:
3203
3204 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3205 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
3206 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3207
3208 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
3209
3210 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3211 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3212 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3213
3214 &lt;p&gt;One can of course also do this after the first boot by installing
3215 the sysvinit-core package.&lt;/p&gt;
3216
3217 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
3218 sysvinit boot sequence in Debian have several hardware specific bugs
3219 on Linux caused by the fact that it is unpredictable when hardware
3220 devices show up during boot. But on the other hand, the new default
3221 boot system still have a few rough edges I hope will be fixed before
3222 Jessie is released.&lt;/p&gt;
3223
3224 &lt;p&gt;Update 2014-11-26: Inspired by
3225 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
3226 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
3227 line.&lt;/p&gt;
3228 </description>
3229 </item>
3230
3231 <item>
3232 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
3233 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
3234 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
3235 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
3236 <description>&lt;p&gt;The right to communicate with your friends and family in private,
3237 without anyone snooping, is a right every citicen have in a liberal
3238 democracy. But this right is under serious attack these days.&lt;/p&gt;
3239
3240 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
3241 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3242 the whisleblower Snowden) more expensive for Internet email,
3243 is to deliver all email using SMTP via Tor. Such SMTP option would be
3244 a nice addition to the FreedomBox project if we could send email
3245 between FreedomBox machines without leaking metadata about the emails
3246 to the people peeking on the wire. I
3247 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
3248 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
3249 lot of useful feedback and suggestions. It also became obvious to me
3250 that this was not a novel idea, as the same idea was tested and
3251 documented by Johannes Berg as early as 2006, and both
3252 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
3253 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
3254 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
3255
3256 &lt;p&gt;To implement such system one need to set up a Tor hidden service
3257 providing the SMTP protocol on port 25, and use email addresses
3258 looking like username@hidden-service-name.onion. With such addresses
3259 the connections to port 25 on hidden-service-name.onion using Tor will
3260 go to the correct SMTP server. To do this, one need to configure the
3261 Tor daemon to provide the hidden service and the mail server to accept
3262 emails for this .onion domain. To learn more about Exim configuration
3263 in Debian and test the design provided by Johannes Berg in his FAQ, I
3264 set out yesterday to create a Debian package for making it trivial to
3265 set up such SMTP over Tor service based on Debian. Getting it to work
3266 were fairly easy, and
3267 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
3268 source code for the Debian package&lt;/a&gt; is available from github. I
3269 plan to move it into Debian if further testing prove this to be a
3270 useful approach.&lt;/p&gt;
3271
3272 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
3273 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
3274 get rid of exim4). Install tor, clone the git repository mentioned
3275 above, build the deb and install it on the machine. Next, run
3276 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
3277 the instructions to get the service up and running. Restart tor and
3278 exim when it is done, and test mail delivery using swaks like
3279 this:&lt;/p&gt;
3280
3281 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3282 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3283 --to fbx@dutlqrrmjhtfa3vp.onion
3284 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3285
3286 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
3287 address with your own address to test your server. :)&lt;/p&gt;
3288
3289 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
3290 easier and more automatic. Especially the tor setup need more work.
3291 Also, the package include a tor-smtp tool written in C, but its task
3292 should probably be rewritten in some script language to make the deb
3293 architecture independent. It would probably also make the code easier
3294 to review. The tor-smtp tool currently need to listen on a socket for
3295 exim to talk to it and is started using xinetd. It would be better if
3296 no daemon and no socket is needed. I suspect it is possible to get
3297 exim to run a command line tool for delivery instead of talking to a
3298 socket, and hope to figure out how in a future version of this
3299 system.&lt;/p&gt;
3300
3301 &lt;p&gt;Until I wipe my test machine, I can be reached using the
3302 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
3303 SMTorP. :)&lt;/p&gt;
3304 </description>
3305 </item>
3306
3307 <item>
3308 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
3309 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
3310 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
3311 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
3312 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
3313 alioth.debian.org, you know the web interface is fairly slow to
3314 operate. First you visit one web page, enter the moderation password
3315 and get a new page shown with a list of all the messages to moderate
3316 and various options for each email address. This take a while for
3317 every list you moderate, and you need to do it regularly to do a good
3318 job as a list moderator. But there is a quick alternative,
3319 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
3320 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
3321 to moderate in a fraction of a second. Here is a test run on two
3322 lists I recently took over:&lt;/p&gt;
3323
3324 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3325 % time listadmin xiph
3326 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3327 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3328
3329 real 0m1.709s
3330 user 0m0.232s
3331 sys 0m0.012s
3332 %
3333 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3334
3335 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
3336 there are no message in the moderation queue. Every morning I
3337 currently moderate 68 mailman lists, and it normally take around two
3338 minutes. When I took over the two pkg-xiph lists above a few days
3339 ago, there were 400 emails waiting in the moderator queue. It took me
3340 less than 15 minutes to process them all using the listadmin
3341 program.&lt;/p&gt;
3342
3343 &lt;p&gt;If you install
3344 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
3345 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
3346 with content like this, the moderation task is a breeze:&lt;/p&gt;
3347
3348 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3349 username username@example.org
3350 spamlevel 23
3351 default discard
3352 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
3353
3354 password secret
3355 adminurl https://{domain}/mailman/admindb/{list}
3356 mailman-list@lists.example.com
3357
3358 password hidden
3359 other-list@otherserver.example.org
3360 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3361
3362 &lt;p&gt;There are other options to set as well. Check the manual page to
3363 learn the details.&lt;/p&gt;
3364
3365 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
3366 the SSL certificate is self signed or not properly signed by a
3367 generally accepted signing authority, you can set a environment
3368 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
3369
3370 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3371 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
3372 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3373
3374 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
3375 can provide an argument to the listadmin script like I do in the
3376 initial screen dump (the xiph argument). Using an argument, only
3377 lists matching the argument string will be processed. This make it
3378 quick to accept messages if you notice the moderation request in your
3379 email.&lt;/p&gt;
3380
3381 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
3382 mailing lists, as I simply do not have time to spend on that if the
3383 process was any slower. The listadmin program have saved me hours of
3384 time I could spend elsewhere over the years. It truly is nice free
3385 software.&lt;/p&gt;
3386
3387 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3388 activities, please send Bitcoin donations to my address
3389 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3390
3391 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
3392 configuration example. Also, I&#39;ve been told that the
3393 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
3394 sure why.&lt;/p&gt;
3395 </description>
3396 </item>
3397
3398 <item>
3399 <title>Debian Jessie, PXE and automatic firmware installation</title>
3400 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
3401 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
3402 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
3403 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
3404 problem that the WiFi card require some firmware to work properly.
3405 And it has been a pain to fix this using preseeding in Debian.
3406 Normally something more is needed. But thanks to
3407 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
3408 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
3409 to do this using simple preseeding.&lt;/p&gt;
3410
3411 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
3412 firmware for the hardware found in the machine (actually, requested by
3413 the kernel modules for the hardware). (It can also install user space
3414 programs supporting the hardware detected, but that is not the focus
3415 of this story.)&lt;/p&gt;
3416
3417 &lt;p&gt;To get this working in the default installation, two preeseding
3418 values are needed. First, the isenkram-cli package must be installed
3419 into the target chroot (aka the hard drive) before tasksel is executed
3420 in the pkgsel step of the debian-installer system. This is done by
3421 preseeding the base-installer/includes debconf value to include the
3422 isenkram-cli package. The package name is next passed to debootstrap
3423 for installation. With the isenkram-cli package in place, tasksel
3424 will automatically use the isenkram tasks to detect hardware specific
3425 packages for the machine being installed and install them, because
3426 isenkram-cli contain tasksel tasks.&lt;/p&gt;
3427
3428 &lt;p&gt;Second, one need to enable the non-free APT repository, because
3429 most firmware unfortunately is non-free. This is done by preseeding
3430 the apt-mirror-setup step. This is unfortunate, but for a lot of
3431 hardware it is the only option in Debian.&lt;/p&gt;
3432
3433 &lt;p&gt;The end result is two lines needed in your preseeding file to get
3434 firmware installed automatically by the installer:&lt;/p&gt;
3435
3436 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3437 base-installer base-installer/includes string isenkram-cli
3438 apt-mirror-setup apt-setup/non-free boolean true
3439 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3440
3441 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
3442 both firmware and user space packages when using this method. It also
3443 do not work well, so use version 0.15 or later. Installing both
3444 firmware and user space packages might give you a bit more than you
3445 want, so I decided to split the tasksel task in two, one for firmware
3446 and one for user space programs. The firmware task is enabled by
3447 default, while the one for user space programs is not. This split is
3448 implemented in the package currently in unstable.&lt;/p&gt;
3449
3450 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
3451 this recipe work for you. :)&lt;/p&gt;
3452
3453 &lt;p&gt;So, I bet you are wondering, how can this work. First and
3454 foremost, it work because tasksel is modular, and driven by whatever
3455 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3456 isenkram-cli package place two files for tasksel to find. First there
3457 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
3458
3459 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3460 Task: isenkram-packages
3461 Section: hardware
3462 Description: Hardware specific packages (autodetected by isenkram)
3463 Based on the detected hardware various hardware specific packages are
3464 proposed.
3465 Test-new-install: show show
3466 Relevance: 8
3467 Packages: for-current-hardware
3468
3469 Task: isenkram-firmware
3470 Section: hardware
3471 Description: Hardware specific firmware packages (autodetected by isenkram)
3472 Based on the detected hardware various hardware specific firmware
3473 packages are proposed.
3474 Test-new-install: mark show
3475 Relevance: 8
3476 Packages: for-current-hardware-firmware
3477 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3478
3479 &lt;p&gt;The key parts are Test-new-install which indicate how the task
3480 should be handled and the Packages line referencing to a script in
3481 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3482 list of packages to install. The for-current-hardware-firmware script
3483 look like this to list relevant firmware for the machine:
3484
3485 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3486 #!/bin/sh
3487 #
3488 PATH=/usr/sbin:$PATH
3489 export PATH
3490 isenkram-autoinstall-firmware -l
3491 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3492
3493 &lt;p&gt;With those two pieces in place, the firmware is installed by
3494 tasksel during the normal d-i run. :)&lt;/p&gt;
3495
3496 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
3497 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
3498 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
3499 install.&lt;/p&gt;
3500
3501 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
3502 pilots in testing this feature, as isenkram is used there now to
3503 install firmware, replacing the earlier scripts.&lt;/p&gt;
3504 </description>
3505 </item>
3506
3507 <item>
3508 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
3509 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
3510 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
3511 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
3512 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
3513 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3514 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
3515 on a screen normally showing the bread types and prizes:&lt;/p&gt;
3516
3517 &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;
3518
3519 &lt;p&gt;If it had booted as it was supposed to, I would never had known
3520 about this hidden Linux installation. It is interesting what
3521 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
3522 </description>
3523 </item>
3524
3525 <item>
3526 <title>New lsdvd release version 0.17 is ready</title>
3527 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
3528 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
3529 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
3530 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
3531 got a new set of developers a few weeks ago, after the original
3532 developer decided to step down and pass the project to fresh blood.
3533 This project is now maintained by Petter Reinholdtsen and Steve
3534 Dibb.&lt;/p&gt;
3535
3536 &lt;p&gt;I just wrapped up
3537 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
3538 new lsdvd release&lt;/a&gt;, available in git or from
3539 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
3540 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
3541 0.17.&lt;/p&gt;
3542
3543 &lt;ul&gt;
3544
3545 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
3546 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
3547 non-existant, to work around additional copy protection&lt;/li&gt;
3548 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
3549 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
3550 &lt;li&gt;Fix include orders&lt;/li&gt;
3551 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
3552 &lt;li&gt;Fix the chapter count&lt;/li&gt;
3553 &lt;li&gt;Make sure the array size and the array limit used when initialising
3554 the palette size is the same.&lt;/li&gt;
3555 &lt;li&gt;Fix array printing.&lt;/li&gt;
3556 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
3557 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
3558 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
3559 with more GCC compiler warnings.&lt;/li&gt;
3560
3561 &lt;/ul&gt;
3562
3563 &lt;p&gt;This change bring together patches for lsdvd in use in various
3564 Linux and Unix distributions, as well as patches submitted to the
3565 project the last nine years. Please check it out. :)&lt;/p&gt;
3566 </description>
3567 </item>
3568
3569 <item>
3570 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
3571 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
3572 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
3573 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
3574 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
3575 project&lt;/a&gt; provide a Linux solution for schools, including a
3576 powerful desktop with education software, a central server providing
3577 web pages, user database, user home directories, central login and PXE
3578 boot of both clients without disk and the installation to install Debian
3579 Edu on machines with disk (and a few other services perhaps to small
3580 to mention here). We in the Debian Edu team are currently working on
3581 the Jessie based version, trying to get everything in shape before the
3582 freeze, to avoid having to maintain our own package repository in the
3583 future. The
3584 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
3585 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
3586 work left. Some fatal problems block testing, breaking the installer,
3587 but it is possible to work around these to get anyway. Here is a
3588 recipe on how to get the installation limping along.&lt;/p&gt;
3589
3590 &lt;p&gt;First, download the test ISO via
3591 &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;,
3592 &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;
3593 or rsync (use
3594 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
3595 The ISO build was broken on Tuesday, so we do not get a new ISO every
3596 12 hours or so, but thankfully the ISO we already got we are able to
3597 install with some tweaking.&lt;/p&gt;
3598
3599 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
3600 (use Alt-Ctrl-F2), run&lt;/p&gt;
3601
3602 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3603 nano /usr/bin/edu-eatmydata-install
3604 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3605
3606 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
3607 optimization. Return to the installation, select the profile you want
3608 and continue. Without this change, exim4-config will fail to install
3609 due to a known bug in eatmydata.&lt;/p&gt;
3610
3611 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
3612 this do not work, figure out what your correct value would be. All my
3613 test machines need /dev/sda, so I have no advice if it do not fit
3614 your need.&lt;/p&gt;
3615
3616 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
3617 root after the initial boot from hard drive, and install the
3618 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3619 or mate. If you want several desktop options, install more than one
3620 metapackage. Once this is done, reboot and you should have a working
3621 graphical login screen. This workaround should no longer be needed
3622 once the education-tasks package version 1.801 enter testing in two
3623 days.&lt;/p&gt;
3624
3625 &lt;p&gt;I believe the ISO build will start working on two days when the new
3626 tasksel package enter testing and Steve McIntyre get a chance to
3627 update the debian-cd git repository. The eatmydata, grub and desktop
3628 issues are already fixed in unstable and testing, and should show up
3629 on the ISO as soon as the ISO build start working again. Well the
3630 eatmydata optimization is really just disabled. The proper fix
3631 require an upload by the eatmydata maintainer applying the patch
3632 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
3633 The rest have proper fixes in unstable.&lt;/p&gt;
3634
3635 &lt;p&gt;I hope this get you going with the installation testing, as we are
3636 quickly running out of time trying to get our Jessie based
3637 installation ready before the distribution freeze in a month.&lt;/p&gt;
3638 </description>
3639 </item>
3640
3641 <item>
3642 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
3643 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
3644 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
3645 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
3646 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
3647 to handle my fairly large DVD collection. It is a nice command line
3648 tool to get details about a DVD, like title, tracks, track length,
3649 etc, in XML, Perl or human readable format. But lsdvd have not seen
3650 any new development since 2006 and had a few irritating bugs affecting
3651 its use with some DVDs. Upstream seemed to be dead, and in January I
3652 sent a small probe asking for a version control repository for the
3653 project, without any reply. But I use it regularly and would like to
3654 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
3655 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
3656 the project admin, and after getting a reply from him explaining that
3657 he was no longer interested in the project, I asked if I could take
3658 over. And yesterday, I became project admin.&lt;/p&gt;
3659
3660 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
3661 maintainer interested in joining forces to maintain the upstream
3662 project, and I hope we can get a new release out fairly quickly,
3663 collecting the patches spread around on the internet into on place.
3664 I&#39;ve added the relevant Debian patches to the freshly created git
3665 repository, and expect the Gentoo patches to make it too. If you got
3666 a DVD collection and care about command line tools, check out
3667 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
3668 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
3669 list&lt;/a&gt;. :)&lt;/p&gt;
3670 </description>
3671 </item>
3672
3673 <item>
3674 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
3675 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
3676 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
3677 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
3678 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
3679 a lot quicker. When we install more than 2000 packages in
3680 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
3681 tasksel in the installer, unpacking the binary packages take forever.
3682 A part of the slow I/O issue was discussed in
3683 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
3684 much file system sync-ing done by dpkg, which is the package
3685 responsible for unpacking the binary packages. Other parts (like code
3686 executed by postinst scripts) might also sync to disk during
3687 installation. All this sync-ing to disk do not really make sense to
3688 me. If the machine crash half-way through, I start over, I do not try
3689 to salvage the half installed system. So the failure sync-ing is
3690 supposed to protect against, hardware or system crash, is not really
3691 relevant while the installer is running.&lt;/p&gt;
3692
3693 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
3694 system sync()-ing in a fairly non-intrusive way, without the need to
3695 change the code in several packages. The idea is not new, but I have
3696 not heard anyone propose the approach using dpkg-divert before. It
3697 depend on the small and clever package
3698 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
3699 uses LD_PRELOAD to replace the system functions for syncing data to
3700 disk with functions doing nothing, thus allowing programs to live
3701 dangerous while speeding up disk I/O significantly. Instead of
3702 modifying the implementation of dpkg, apt and tasksel (which are the
3703 packages responsible for selecting, fetching and installing packages),
3704 it occurred to me that we could just divert the programs away, replace
3705 them with a simple shell wrapper calling
3706 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
3707 Two days ago I decided to test the idea, and wrapped up a simple
3708 implementation for the Debian Edu udeb.&lt;/p&gt;
3709
3710 &lt;p&gt;The effect was stunning. In my first test it reduced the running
3711 time of the pkgsel step (installing tasks) from 64 to less than 44
3712 minutes (20 minutes shaved off the installation) on an old Dell
3713 Latitude D505 machine. I am not quite sure what the optimised time
3714 would have been, as I messed up the testing a bit, causing the debconf
3715 priority to get low enough for two questions to pop up during
3716 installation. As soon as I saw the questions I moved the installation
3717 along, but do not know how long the question were holding up the
3718 installation. I did some more measurements using Debian Edu Jessie,
3719 and got these results. The time measured is the time stamp in
3720 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
3721 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
3722 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3723 timing thus do not depend on how quickly the user handle the tasksel
3724 dialog.&lt;/p&gt;
3725
3726 &lt;p&gt;&lt;table&gt;
3727
3728 &lt;tr&gt;
3729 &lt;th&gt;Machine/setup&lt;/th&gt;
3730 &lt;th&gt;Original tasksel&lt;/th&gt;
3731 &lt;th&gt;Optimised tasksel&lt;/th&gt;
3732 &lt;th&gt;Reduction&lt;/th&gt;
3733 &lt;/tr&gt;
3734
3735 &lt;tr&gt;
3736 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
3737 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
3738 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
3739 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
3740 &lt;/tr&gt;
3741
3742 &lt;tr&gt;
3743 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
3744 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
3745 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
3746 &lt;td&gt;23 min 40%&lt;/td&gt;
3747 &lt;/tr&gt;
3748
3749 &lt;tr&gt;
3750 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
3751 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
3752 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
3753 &lt;td&gt;11 min 50%&lt;/td&gt;
3754 &lt;/tr&gt;
3755
3756 &lt;tr&gt;
3757 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
3758 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
3759 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
3760 &lt;td&gt;2 min 33%&lt;/td&gt;
3761 &lt;/tr&gt;
3762
3763 &lt;tr&gt;
3764 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
3765 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
3766 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
3767 &lt;td&gt;4 min 21%&lt;/td&gt;
3768 &lt;/tr&gt;
3769
3770 &lt;/table&gt;&lt;/p&gt;
3771
3772 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
3773 time is spent downloading packages. The connection to the Internet
3774 was 100Mbit/s during testing, so downloading should not be a
3775 significant factor in the measurement. Download typically took a few
3776 seconds to a few minutes, depending on the amount of packages being
3777 installed.&lt;/p&gt;
3778
3779 &lt;p&gt;The speedup is implemented by using two hooks in
3780 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
3781 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
3782 finish-install.d hook to remove the divert at the end of the
3783 installation. I picked the pre-pkgsel.d hook instead of the
3784 post-base-installer.d hook because I test using an ISO without the
3785 eatmydata package included, and the post-base-installer.d hook in
3786 Debian Edu can only operate on packages included in the ISO. The
3787 negative effect of this is that I am unable to activate this
3788 optimization for the kernel installation step in d-i. If the code is
3789 moved to the post-base-installer.d hook, the speedup would be larger
3790 for the entire installation.&lt;/p&gt;
3791
3792 &lt;p&gt;I&#39;ve implemented this in the
3793 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
3794 git repository, and plan to provide the optimization as part of the
3795 Debian Edu installation. If you want to test this yourself, you can
3796 create two files in the installer (or in an udeb). One shell script
3797 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
3798
3799 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3800 #!/bin/sh
3801 set -e
3802 . /usr/share/debconf/confmodule
3803 info() {
3804 logger -t my-pkgsel &quot;info: $*&quot;
3805 }
3806 error() {
3807 logger -t my-pkgsel &quot;error: $*&quot;
3808 }
3809 override_install() {
3810 apt-install eatmydata || true
3811 if [ -x /target/usr/bin/eatmydata ] ; then
3812 for bin in dpkg apt-get aptitude tasksel ; do
3813 file=/usr/bin/$bin
3814 # Test that the file exist and have not been diverted already.
3815 if [ -f /target$file ] ; then
3816 info &quot;diverting $file using eatmydata&quot;
3817 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
3818 &gt; /target$file.edu
3819 chmod 755 /target$file.edu
3820 in-target dpkg-divert --package debian-edu-config \
3821 --rename --quiet --add $file
3822 ln -sf ./$bin.edu /target$file
3823 else
3824 error &quot;unable to divert $file, as it is missing.&quot;
3825 fi
3826 done
3827 else
3828 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
3829 fi
3830 }
3831
3832 override_install
3833 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3834
3835 &lt;p&gt;To clean up, another shell script should go into
3836 /usr/lib/finish-install.d/ with code like this:
3837
3838 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3839 #! /bin/sh -e
3840 . /usr/share/debconf/confmodule
3841 error() {
3842 logger -t my-finish-install &quot;error: $@&quot;
3843 }
3844 remove_install_override() {
3845 for bin in dpkg apt-get aptitude tasksel ; do
3846 file=/usr/bin/$bin
3847 if [ -x /target$file.edu ] ; then
3848 rm /target$file
3849 in-target dpkg-divert --package debian-edu-config \
3850 --rename --quiet --remove $file
3851 rm /target$file.edu
3852 else
3853 error &quot;Missing divert for $file.&quot;
3854 fi
3855 done
3856 sync # Flush file buffers before continuing
3857 }
3858
3859 remove_install_override
3860 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3861
3862 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
3863 edu-eatmydata-install and call it from the pre-pkgsel.d and
3864 finish-install.d scripts.&lt;/p&gt;
3865
3866 &lt;p&gt;By now you might ask if this change should get into the normal
3867 Debian installer too? I suspect it should, but am not sure the
3868 current debian-installer coordinators find it useful enough. It also
3869 depend on the side effects of the change. I&#39;m not aware of any, but I
3870 guess we will see if the change is safe after some more testing.
3871 Perhaps there is some package in Debian depending on sync() and
3872 fsync() having effect? Perhaps it should go into its own udeb, to
3873 allow those of us wanting to enable it to do so without affecting
3874 everyone.&lt;/p&gt;
3875
3876 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
3877 will break installation of all programs using gnutls because of
3878 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
3879 eatmydata package in Debian will solve it.&lt;/p&gt;
3880
3881 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
3882 the optimization work again. And I have discovered that the
3883 dpkg-divert trick is not really needed and implemented a slightly
3884 simpler approach as part of the debian-edu-install package. See
3885 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
3886
3887 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
3888 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
3889 triggering on i386 made it into testing, and broke this installation
3890 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
3891 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
3892 </description>
3893 </item>
3894
3895 <item>
3896 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
3897 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
3898 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
3899 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
3900 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
3901 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
3902 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
3903 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
3904 learn that there is a large set of publicly available key servers to
3905 use when looking for peoples public key. So far I have used
3906 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3907 were misbehaving, but those days are ended. The servers I have used
3908 up until yesterday have been slow and some times unavailable. I hope
3909 those problems are gone now.&lt;/p&gt;
3910
3911 &lt;p&gt;Behind the round robin DNS entry of the
3912 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
3913 there is a pool of more than 100 keyservers which are checked every
3914 day to ensure they are well connected and up to date. It must be
3915 better than what I have used so far. :)&lt;/p&gt;
3916
3917 &lt;p&gt;Yesterdays speaker told me that the service is the default
3918 keyserver provided by the default configuration in GnuPG, but this do
3919 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
3920
3921 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
3922 line:&lt;/p&gt;
3923
3924 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3925 keyserver pool.sks-keyservers.net
3926 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3927
3928 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
3929 entries in DNS. Just for fun, I did just that at work, so now every
3930 user of GnuPG at the University of Oslo should find a OpenGPG
3931 keyserver automatically should their need it:&lt;/p&gt;
3932
3933 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3934 % host -t srv _pgpkey-http._tcp.uio.no
3935 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
3936 %
3937 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3938
3939 &lt;p&gt;Now if only
3940 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
3941 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
3942 very happy. It can look up a given key or search for a user ID, but I
3943 normally do not want that, but to find a trust path from my key to
3944 another key. Given a user ID or key ID, I would like to find (and
3945 download) the keys representing a signature path from my key to the
3946 key in question, to be able to get a trust path between the two keys.
3947 This is as far as I can tell not possible today. Perhaps something
3948 for a future version of the protocol?&lt;/p&gt;
3949 </description>
3950 </item>
3951
3952 <item>
3953 <title>From English wiki to translated PDF and epub via Docbook</title>
3954 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
3955 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
3956 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
3957 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
3958 project&lt;/a&gt; provide an instruction manual for teachers, system
3959 administrators and other users that contain useful tips for setting up
3960 and maintaining a Debian Edu installation. This text is about how the
3961 text processing of this manual is handled in the project.&lt;/p&gt;
3962
3963 &lt;p&gt;One goal of the project is to provide information in the native
3964 language of its users, and for this we need to handle translations.
3965 But we also want to make sure each language contain the same
3966 information, so for this we need a good way to keep the translations
3967 in sync. And we want it to be easy for our users to improve the
3968 documentation, avoiding the need to learn special formats or tools to
3969 contribute, and the obvious way to do this is to make it possible to
3970 edit the documentation using a web browser. We also want it to be
3971 easy for translators to keep the translation up to date, and give them
3972 help in figuring out what need to be translated. Here is the list of
3973 tools and the process we have found trying to reach all these
3974 goals.&lt;/p&gt;
3975
3976 &lt;p&gt;We maintain the authoritative source of our manual in the
3977 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
3978 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
3979 front page with references to the different chapters, several pages
3980 for each chapter, and finally one &quot;collection page&quot; gluing all the
3981 chapters together into one large web page (aka
3982 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
3983 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
3984 processing and translations. Thanks to the fact that the
3985 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
3986 wiki.debian.org support exporting pages in
3987 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
3988 the list of pages to export using the raw version of the AllInOne
3989 page, loop over each of them to generate a Docbook XML version of the
3990 manual. This process also download images and transform image
3991 references to use the locally downloaded images. The generated
3992 Docbook XML files are slightly broken, so some post-processing is done
3993 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
3994 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3995 a handfull of images. The XML file can now be used to generate PDF, HTML
3996 and epub versions of the English manual. This is the basic step of
3997 our process, making PDF (using dblatex), HTML (using xsltproc) and
3998 epub (using dbtoepub) version from Docbook XML, and the resulting files
3999 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
4000
4001 &lt;p&gt;But English documentation is not enough for us. We want translated
4002 documentation too, and we want to make it easy for translators to
4003 track the English original. For this we use the
4004 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
4005 which allow us to transform the English Docbook XML file into a
4006 translation file (a .pot file), usable with the normal gettext based
4007 translation tools used by those translating free software. The pot
4008 file is used to create and maintain translation files (several .po
4009 files), which the translations update with the native language
4010 translations of all titles, paragraphs and blocks of text in the
4011 original. The next step is combining the original English Docbook XML
4012 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4013 create a translated Docbook XML file (in this case
4014 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4015 translated, if the translation is not complete) Docbook XML file can
4016 then be used like the original to create a PDF, HTML and epub version
4017 of the documentation.&lt;/p&gt;
4018
4019 &lt;p&gt;The translators use different tools to edit the .po files. We
4020 recommend using
4021 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
4022 while some use emacs and vi, others can use web based editors like
4023 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
4024 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
4025 is where the .po file end up, in our git repository. Updated
4026 translations can either be committed directly to git, or submitted as
4027 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
4028 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
4029
4030 &lt;p&gt;One challenge is images, which both might need to be translated (if
4031 they show translated user applications), and are needed in different
4032 formats when creating PDF and HTML versions (epub is a HTML version in
4033 this regard). For this we transform the original PNG images to the
4034 needed density and format during build, and have a way to provide
4035 translated images by storing translated versions in
4036 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4037 package maintainers know more.&lt;/p&gt;
4038
4039 &lt;p&gt;If you wonder what the result look like, we provide
4040 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
4041 of the documentation packages on the web&lt;/a&gt;. See for example the
4042 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
4043 PDF version&lt;/a&gt; or the
4044 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
4045 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
4046 but perhaps it will be done in the future.&lt;/p&gt;
4047
4048 &lt;p&gt;To learn more, check out
4049 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
4050 debian-edu-doc package&lt;/a&gt;,
4051 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
4052 manual on the wiki&lt;/a&gt; and
4053 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
4054 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
4055 </description>
4056 </item>
4057
4058 <item>
4059 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
4060 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
4061 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
4062 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
4063 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
4064 related packages relevant for the computer installed automatically.
4065 So I implemented one, using
4066 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
4067 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
4068 run tasksel as user root. You should be presented with a new option,
4069 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
4070 select it, tasksel will install the packages isenkram claim is fit for
4071 the current hardware, hot pluggable or not.&lt;p&gt;
4072
4073 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
4074 description, and the other is the script used to extract the list of
4075 packages to install. The first part is in
4076 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
4077 this:&lt;/p&gt;
4078
4079 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4080 Task: isenkram
4081 Section: hardware
4082 Description: Hardware specific packages (autodetected by isenkram)
4083 Based on the detected hardware various hardware specific packages are
4084 proposed.
4085 Test-new-install: mark show
4086 Relevance: 8
4087 Packages: for-current-hardware
4088 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4089
4090 &lt;p&gt;The second part is in
4091 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
4092 this:&lt;/p&gt;
4093
4094 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4095 #!/bin/sh
4096 #
4097 (
4098 isenkram-lookup
4099 isenkram-autoinstall-firmware -l
4100 ) | sort -u
4101 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4102
4103 &lt;p&gt;All in all, a very short and simple implementation making it
4104 trivial to install the hardware dependent package we all may want to
4105 have installed on our machines. I&#39;ve not been able to find a way to
4106 get tasksel to tell you exactly which packages it plan to install
4107 before doing the installation. So if you are curious or careful,
4108 check the output from the isenkram-* command line tools first.&lt;/p&gt;
4109
4110 &lt;p&gt;The information about which packages are handling which hardware is
4111 fetched either from the isenkram package itself in
4112 /usr/share/isenkram/, from git.debian.org or from the APT package
4113 database (using the Modaliases header). The APT package database
4114 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4115 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
4116 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
4117 the python-apt code (bug
4118 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
4119 workaround I was able to get rid of the file descriptor leak and
4120 reduce the memory leak from ~30 MiB per hardware detection down to
4121 around 2 MiB per hardware detection. It should make the desktop
4122 daemon a lot more useful. The fix is in version 0.7 uploaded to
4123 unstable today.&lt;/p&gt;
4124
4125 &lt;p&gt;I believe the current way of mapping hardware to packages in
4126 Isenkram is is a good draft, but in the future I expect isenkram to
4127 use the AppStream data source for this. A proposal for getting proper
4128 AppStream support into Debian is floating around as
4129 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
4130 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
4131 project&lt;/a&gt; will take place this summer to improve the situation. I
4132 look forward to seeing the result, and welcome patches for isenkram to
4133 start using the information when it is ready.&lt;/p&gt;
4134
4135 &lt;p&gt;If you want your package to map to some specific hardware, either
4136 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
4137 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
4138 package&lt;/a&gt; or submit a bug report with the details to the isenkram
4139 package. See also
4140 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
4141 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
4142 the information will be migrated to AppStream eventually, but for the
4143 moment I got no better place to store it.&lt;/p&gt;
4144 </description>
4145 </item>
4146
4147 <item>
4148 <title>FreedomBox milestone - all packages now in Debian Sid</title>
4149 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
4150 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
4151 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
4152 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
4153 project&lt;/a&gt; is working on providing the software and hardware to make
4154 it easy for non-technical people to host their data and communication
4155 at home, and being able to communicate with their friends and family
4156 encrypted and away from prying eyes. It is still going strong, and
4157 today a major mile stone was reached.&lt;/p&gt;
4158
4159 &lt;p&gt;Today, the last of the packages currently used by the project to
4160 created the system images were accepted into Debian Unstable. It was
4161 the freedombox-setup package, which is used to configure the images
4162 during build and on the first boot. Now all one need to get going is
4163 the build code from the freedom-maker git repository and packages from
4164 Debian. And once the freedombox-setup package enter testing, we can
4165 build everything directly from Debian. :)&lt;/p&gt;
4166
4167 &lt;p&gt;Some key packages used by Freedombox are
4168 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
4169 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
4170 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
4171 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
4172 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
4173 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
4174 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
4175 are plans to integrate more packages into the setup. User
4176 documentation is maintained on the Debian wiki. Please
4177 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
4178 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
4179
4180 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
4181 setup, run this on a Debian machine using a user with sudo rights to
4182 become root:&lt;/p&gt;
4183
4184 &lt;p&gt;&lt;pre&gt;
4185 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4186 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4187 u-boot-tools
4188 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4189 freedom-maker
4190 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4191 &lt;/pre&gt;&lt;/p&gt;
4192
4193 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
4194 devices. See the README in the freedom-maker git repo for more
4195 details on the build. If you do not want all three images, trim the
4196 make line. Note that the virtualbox-image target is not really
4197 virtualbox specific. It create a x86 image usable in kvm, qemu,
4198 vmware and any other x86 virtual machine environment. You might need
4199 the version of vmdebootstrap in Jessie to get the build working, as it
4200 include fixes for a race condition with kpartx.&lt;/p&gt;
4201
4202 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
4203 method, boot a Debian Wheezy ISO and use this boot argument to load
4204 the preseed values:&lt;/p&gt;
4205
4206 &lt;p&gt;&lt;pre&gt;
4207 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;
4208 &lt;/pre&gt;&lt;/p&gt;
4209
4210 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
4211 it still work.&lt;/p&gt;
4212
4213 &lt;p&gt;If you wonder how to help, one task you could look at is using
4214 systemd as the boot system. It will become the default for Linux in
4215 Jessie, so we need to make sure it is usable on the Freedombox. I did
4216 a simple test a few weeks ago, and noticed dnsmasq failed to start
4217 during boot when using systemd. I suspect there are other problems
4218 too. :) To detect problems, there is a test suite included, which can
4219 be run from the plinth web interface.&lt;/p&gt;
4220
4221 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
4222 us get the new release published. :) Please join us on
4223 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
4224 irc.debian.org)&lt;/a&gt; and
4225 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4226 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4227 </description>
4228 </item>
4229
4230 <item>
4231 <title>S3QL, a locally mounted cloud file system - nice free software</title>
4232 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
4233 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
4234 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
4235 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
4236 solution for use at home. My requirements are simple, it must be
4237 cheap and locally encrypted (in other words, I keep the encryption
4238 keys, the storage provider do not have access to my private files).
4239 One idea me and my friends had many years ago, before the cloud
4240 storage providers showed up, was to use Google mail as storage,
4241 writing a Linux block device storing blocks as emails in the mail
4242 service provided by Google, and thus get heaps of free space. On top
4243 of this one can add encryption, RAID and volume management to have
4244 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4245 I never found time to implement such system. But the last few weeks I
4246 have looked at a system called
4247 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
4248 mounted network backed file system with the features I need.&lt;/p&gt;
4249
4250 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
4251 handling several different storage providers, any with Amazon S3,
4252 Google Drive or OpenStack API. There are heaps of such storage
4253 providers. S3QL can also use a local directory as storage, which
4254 combined with sshfs allow for file storage on any ssh server. S3QL
4255 include support for encryption, compression, de-duplication, snapshots
4256 and immutable file systems, allowing me to mount the remote storage as
4257 a local mount point, look at and use the files as if they were local,
4258 while the content is stored in the cloud as well. This allow me to
4259 have a backup that should survive fire. The file system can not be
4260 shared between several machines at the same time, as only one can
4261 mount it at the time, but any machine with the encryption key and
4262 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
4263
4264 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
4265 package is included already. So to get started, run &lt;tt&gt;apt-get
4266 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
4267 Greenqloud, after reading their nice recipe on
4268 &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
4269 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
4270 in Iceland more than those in USA when it come to keeping my personal
4271 data safe and private, and thus would rather spend money on a company
4272 in Iceland. Another nice recipe is available from the article
4273 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
4274 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
4275 Admin magazine. When the provider is picked, figure out how to get
4276 the API key needed to connect to the storage API. With Greencloud,
4277 the key did not show up until I had added payment details to my
4278 account.&lt;/p&gt;
4279
4280 &lt;p&gt;Armed with the API access details, it is time to create the file
4281 system. First, create a new bucket in the cloud. This bucket is the
4282 file system storage area. I picked a bucket name reflecting the
4283 machine that was going to store data there, but any name will do.
4284 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
4285 the API login and password, and a locally created password. Store it
4286 all in ~root/.s3ql/authinfo2 like this:
4287
4288 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4289 [s3c]
4290 storage-url: s3c://s.greenqloud.com:443/bucket-name
4291 backend-login: API-login
4292 backend-password: API-password
4293 fs-passphrase: local-password
4294 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4295
4296 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
4297 but any sensible way to create a fairly random password should do it.
4298 Armed with these details, it is now time to run mkfs, entering the API
4299 details and password to create it:&lt;/p&gt;
4300
4301 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4302 # mkdir -m 700 /var/lib/s3ql-cache
4303 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4304 --ssl s3c://s.greenqloud.com:443/bucket-name
4305 Enter backend login:
4306 Enter backend password:
4307 Before using S3QL, make sure to read the user&#39;s guide, especially
4308 the &#39;Important Rules to Avoid Loosing Data&#39; section.
4309 Enter encryption password:
4310 Confirm encryption password:
4311 Generating random encryption key...
4312 Creating metadata tables...
4313 Dumping metadata...
4314 ..objects..
4315 ..blocks..
4316 ..inodes..
4317 ..inode_blocks..
4318 ..symlink_targets..
4319 ..names..
4320 ..contents..
4321 ..ext_attributes..
4322 Compressing and uploading metadata...
4323 Wrote 0.00 MB of compressed metadata.
4324 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4325
4326 &lt;p&gt;The next step is mounting the file system to make the storage available.
4327
4328 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4329 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4330 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
4331 Using 4 upload threads.
4332 Downloading and decompressing metadata...
4333 Reading metadata...
4334 ..objects..
4335 ..blocks..
4336 ..inodes..
4337 ..inode_blocks..
4338 ..symlink_targets..
4339 ..names..
4340 ..contents..
4341 ..ext_attributes..
4342 Mounting filesystem...
4343 # df -h /s3ql
4344 Filesystem Size Used Avail Use% Mounted on
4345 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
4346 #
4347 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4348
4349 &lt;p&gt;The file system is now ready for use. I use rsync to store my
4350 backups in it, and as the metadata used by rsync is downloaded at
4351 mount time, no network traffic (and storage cost) is triggered by
4352 running rsync. To unmount, one should not use the normal umount
4353 command, as this will not flush the cache to the cloud storage, but
4354 instead running the umount.s3ql command like this:
4355
4356 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4357 # umount.s3ql /s3ql
4358 #
4359 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4360
4361 &lt;p&gt;There is a fsck command available to check the file system and
4362 correct any problems detected. This can be used if the local server
4363 crashes while the file system is mounted, to reset the &quot;already
4364 mounted&quot; flag. This is what it look like when processing a working
4365 file system:&lt;/p&gt;
4366
4367 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4368 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
4369 Using cached metadata.
4370 File system seems clean, checking anyway.
4371 Checking DB integrity...
4372 Creating temporary extra indices...
4373 Checking lost+found...
4374 Checking cached objects...
4375 Checking names (refcounts)...
4376 Checking contents (names)...
4377 Checking contents (inodes)...
4378 Checking contents (parent inodes)...
4379 Checking objects (reference counts)...
4380 Checking objects (backend)...
4381 ..processed 5000 objects so far..
4382 ..processed 10000 objects so far..
4383 ..processed 15000 objects so far..
4384 Checking objects (sizes)...
4385 Checking blocks (referenced objects)...
4386 Checking blocks (refcounts)...
4387 Checking inode-block mapping (blocks)...
4388 Checking inode-block mapping (inodes)...
4389 Checking inodes (refcounts)...
4390 Checking inodes (sizes)...
4391 Checking extended attributes (names)...
4392 Checking extended attributes (inodes)...
4393 Checking symlinks (inodes)...
4394 Checking directory reachability...
4395 Checking unix conventions...
4396 Checking referential integrity...
4397 Dropping temporary indices...
4398 Backing up old metadata...
4399 Dumping metadata...
4400 ..objects..
4401 ..blocks..
4402 ..inodes..
4403 ..inode_blocks..
4404 ..symlink_targets..
4405 ..names..
4406 ..contents..
4407 ..ext_attributes..
4408 Compressing and uploading metadata...
4409 Wrote 0.89 MB of compressed metadata.
4410 #
4411 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4412
4413 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
4414 quick, about the same speed as local file access. Uploading large
4415 amount of data is to me limited by the bandwidth out of and into my
4416 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
4417 which is very close to my upload speed, and downloading the same
4418 Debian installation ISO gave me 610 kiB/s, close to my download speed.
4419 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
4420 network, not the file system code. I do not know what a good cache
4421 size would be, but suspect that the cache should e larger than your
4422 working set.&lt;/p&gt;
4423
4424 &lt;p&gt;I mentioned that only one machine can mount the file system at the
4425 time. If another machine try, it is told that the file system is
4426 busy:&lt;/p&gt;
4427
4428 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4429 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4430 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
4431 Using 8 upload threads.
4432 Backend reports that fs is still mounted elsewhere, aborting.
4433 #
4434 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4435
4436 &lt;p&gt;The file content is uploaded when the cache is full, while the
4437 metadata is uploaded once every 24 hour by default. To ensure the
4438 file system content is flushed to the cloud, one can either umount the
4439 file system, or ask S3QL to flush the cache and metadata using
4440 s3qlctrl:
4441
4442 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4443 # s3qlctrl upload-meta /s3ql
4444 # s3qlctrl flushcache /s3ql
4445 #
4446 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4447
4448 &lt;p&gt;If you are curious about how much space your data uses in the
4449 cloud, and how much compression and deduplication cut down on the
4450 storage usage, you can use s3qlstat on the mounted file system to get
4451 a report:&lt;/p&gt;
4452
4453 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4454 # s3qlstat /s3ql
4455 Directory entries: 9141
4456 Inodes: 9143
4457 Data blocks: 8851
4458 Total data size: 22049.38 MB
4459 After de-duplication: 21955.46 MB (99.57% of total)
4460 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
4461 Database size: 2.39 MB (uncompressed)
4462 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4463 #
4464 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4465
4466 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
4467 storage. I did not try to locate them all, but am aware of at least
4468 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
4469 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
4470 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
4471 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
4472 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
4473 accept payment in Bitcoin. Pick one that suit your need. Some of
4474 them provide several GiB of free storage, but the prize models are
4475 quite different and you will have to figure out what suits you
4476 best.&lt;/p&gt;
4477
4478 &lt;p&gt;While researching this blog post, I had a look at research papers
4479 and posters discussing the S3QL file system. There are several, which
4480 told me that the file system is getting a critical check by the
4481 science community and increased my confidence in using it. One nice
4482 poster is titled
4483 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
4484 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4485 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
4486 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4487 and Pamela Smith. Please have a look.&lt;/p&gt;
4488
4489 &lt;p&gt;Given my problems with different file systems earlier, I decided to
4490 check out the mounted S3QL file system to see if it would be usable as
4491 a home directory (in other word, that it provided POSIX semantics when
4492 it come to locking and umask handling etc). Running
4493 &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
4494 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
4495 no error was found. So the file system can be used for home
4496 directories, if one chooses to do so.&lt;/p&gt;
4497
4498 &lt;p&gt;If you do not want a locally file system, and want something that
4499 work without the Linux fuse file system, I would like to mention the
4500 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
4501 provide locally encrypted backup using a command line client. It have
4502 a nicer access control system, where one can split out read and write
4503 access, allowing some systems to write to the backup and others to
4504 only read from it.&lt;/p&gt;
4505
4506 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4507 activities, please send Bitcoin donations to my address
4508 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4509 </description>
4510 </item>
4511
4512 <item>
4513 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
4514 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
4515 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
4516 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
4517 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
4518 project&lt;/a&gt; is working on providing the software and hardware for
4519 making it easy for non-technical people to host their data and
4520 communication at home, and being able to communicate with their
4521 friends and family encrypted and away from prying eyes. It has been
4522 going on for a while, and is slowly progressing towards a new test
4523 release (0.2).&lt;/p&gt;
4524
4525 &lt;p&gt;And what day could be better than the Pi day to announce that the
4526 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
4527 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4528 system), and can also be installed using a Debian installer preseed
4529 file. The Debian based Freedombox is now based on Debian Jessie,
4530 where most of the needed packages used are already present. Only one,
4531 the freedombox-setup package, is missing. To try to build your own
4532 boot image to test the current status, fetch the freedom-maker scripts
4533 and build using
4534 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
4535 with a user with sudo access to become root:
4536
4537 &lt;pre&gt;
4538 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4539 freedom-maker
4540 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4541 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4542 u-boot-tools
4543 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4544 &lt;/pre&gt;
4545
4546 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
4547 devices. See the README for more details on the build. If you do not
4548 want all three images, trim the make line. But note that thanks to &lt;a
4549 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
4550 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
4551 kpartx call.&lt;/p&gt;
4552
4553 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
4554 method, boot a Debian Wheezy ISO and use this boot argument to load
4555 the preseed values:&lt;/p&gt;
4556
4557 &lt;pre&gt;
4558 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;
4559 &lt;/pre&gt;
4560
4561 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
4562 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
4563 currently hang while setting up APT sources. Killing the
4564 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
4565 installation will get the installation going. This affect all
4566 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
4567
4568 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
4569 us get the new release published. :) Please join us on
4570 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
4571 irc.debian.org)&lt;/a&gt; and
4572 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4573 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4574 </description>
4575 </item>
4576
4577 <item>
4578 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
4579 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
4580 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
4581 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
4582 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
4583 innetgr tools, because I needed them in
4584 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
4585 ng-utils, and it has served me well. I placed the project under the
4586 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
4587 repository. But many years ago, the CVS repository was dropped (lost,
4588 not migrated to new hardware, not sure), and the project have lacked a
4589 proper home since then.&lt;/p&gt;
4590
4591 &lt;p&gt;Last summer, I had a look at the package and made a new release
4592 fixing a irritating crash bug, but was unable to store the changes in
4593 a proper source control system. I applied for a project on
4594 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
4595 to follow up on it. Until today. :)&lt;/p&gt;
4596
4597 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
4598 now have a new home, and a git repository with the highlight of the
4599 history of the project. I published all release tarballs and imported
4600 them into the git repository. As the project is really stable and not
4601 expected to gain new features any time soon, I decided to make a new
4602 release and call it 1.0. Visit the new project home on
4603 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
4604 if you want to check it out. The new version is also uploaded into
4605 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
4606 </description>
4607 </item>
4608
4609 <item>
4610 <title>Testing sysvinit from experimental in Debian Hurd</title>
4611 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
4612 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
4613 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
4614 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
4615 their changes into sysvinit, to allow them to use the normal sysvinit
4616 boot system instead of their old one. This follow up on the
4617 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
4618 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
4619 get Debian on Hurd working more like Debian on Linux. To get started,
4620 I downloaded a prebuilt hard disk image from
4621 &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;,
4622 and started it using virt-manager.&lt;/p&gt;
4623
4624 &lt;p&gt;The first think I had to do after logging in (root without any
4625 password) was to get the network operational. I followed
4626 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
4627 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
4628 commands as root to get the machine to accept a IP address from the
4629 kvm internal DHCP server:&lt;/p&gt;
4630
4631 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4632 settrans -fgap /dev/netdde /hurd/netdde
4633 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
4634 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
4635 dhclient /dev/eth0
4636 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4637
4638 &lt;p&gt;After this, the machine had internet connectivity, and I could
4639 upgrade it and install the sysvinit packages from experimental and
4640 enable it as the default boot system in Hurd.&lt;/p&gt;
4641
4642 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
4643 running on the machine it for ssh login to work a password need to be
4644 set. Also, note that a bug somewhere in openssh on Hurd block
4645 compression from working. Remember to turn that off on the client
4646 side.&lt;/p&gt;
4647
4648 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
4649 stuff:&lt;/p&gt;
4650
4651 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4652 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
4653 deb http://http.debian.net/debian/ experimental main
4654 EOF
4655 apt-get update
4656 apt-get dist-upgrade
4657 apt-get install -t experimental initscripts sysv-rc sysvinit \
4658 sysvinit-core sysvinit-utils
4659 update-alternatives --config runsystem
4660 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4661
4662 &lt;p&gt;To reboot after switching boot system, you have to use
4663 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
4664 yet a sysvinit process able to receive the signals from the normal
4665 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
4666 upgrading every package and rebooting, the network come up with DHCP
4667 after boot as it should, and the settrans/pkill hack mentioned at the
4668 start is no longer needed. But for some strange reason, there are no
4669 longer any login prompt in the virtual console, so I logged in using
4670 ssh instead.
4671
4672 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
4673 fail some times. No idea what the cause is, but hope the Hurd porters
4674 figure it out. At least Justus said on IRC (#debian-hurd on
4675 irc.debian.org) that they are aware of the problem. A way to reduce
4676 the impact is to upgrade to the Hurd packages built by Justus by
4677 adding this repository to the machine:&lt;/p&gt;
4678
4679 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4680 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
4681 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4682 EOF
4683 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4684
4685 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
4686 http://ftp.debian-ports.org/debian, because some of the packages in
4687 unstable do not yet include the required patches that are lingering in
4688 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
4689
4690 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4691 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
4692 i emacs - GNU Emacs editor (metapackage)
4693 i gdb - GNU Debugger
4694 i hurd-recommended - Miscellaneous translators
4695 i isc-dhcp-client - ISC DHCP client
4696 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4697 i libc-bin - Embedded GNU C Library: Binaries
4698 i libc-dev-bin - Embedded GNU C Library: Development binaries
4699 i libc0.3 - Embedded GNU C Library: Shared libraries
4700 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4701 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4702 i multiarch-support - Transitional package to ensure multiarch compatibilit
4703 i A x11-common - X Window System (X.Org) infrastructure
4704 i xorg - X.Org X Window System
4705 i A xserver-xorg - X.Org X server
4706 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4707 #
4708 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4709
4710 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
4711 X.org did not work out of the box and I never took the time to follow
4712 the porters instructions to fix it. This time I was interested in the
4713 command line stuff.&lt;p&gt;
4714 </description>
4715 </item>
4716
4717 <item>
4718 <title>New chrpath release 0.16</title>
4719 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
4720 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
4721 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
4722 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
4723 find problems in C, C++ and Java code using static source code
4724 analysis. It can detect a lot of different problems, and is very
4725 useful to find memory and locking bugs in the error handling part of
4726 the source. The company behind it provide
4727 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
4728 a community service&lt;/a&gt;, and many hundred free software projects are
4729 already checked. A few days ago I decided to have a closer look at
4730 the Coverity system, and discovered that the
4731 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
4732 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
4733 projects I am involved with was already registered. But these are
4734 fairly big, and I would also like to have a small and easy project to
4735 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
4736 checking of the chrpath project&lt;/a&gt;. It was
4737 added to the checker and discovered seven potential defects. Six of
4738 these were real, mostly resource &quot;leak&quot; when the program detected an
4739 error. Nothing serious, as the resources would be released a fraction
4740 of a second later when the program exited because of the error, but it
4741 is nice to do it right in case the source of the program some time in
4742 the future end up in a library. Having fixed all defects and added
4743 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
4744 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
4745 publish a new release. These are the release notes:&lt;/p&gt;
4746
4747 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
4748
4749 &lt;ul&gt;
4750
4751 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
4752 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
4753 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
4754
4755 &lt;/ul&gt;
4756
4757 &lt;p&gt;You can
4758 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
4759 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
4760 project if something is wrong with the new release. The test suite
4761 did not discover any old errors, so if you find a new one, please also
4762 include a test suite check.&lt;/p&gt;
4763 </description>
4764 </item>
4765
4766 <item>
4767 <title>New chrpath release 0.15</title>
4768 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
4769 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
4770 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
4771 <description>&lt;p&gt;After many years break from the package and a vain hope that
4772 development would be continued by someone else, I finally pulled my
4773 acts together this morning and wrapped up a new release of chrpath,
4774 the command line tool to modify the rpath and runpath of already
4775 compiled ELF programs. The update was triggered by the persistence of
4776 Isha Vishnoi at IBM, which needed a new config.guess file to get
4777 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
4778 is working on. I checked the
4779 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
4780 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
4781 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
4782 packages for interesting patches (failed to find the source from
4783 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4784 These are the release notes:&lt;/p&gt;
4785
4786 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
4787
4788 &lt;ul&gt;
4789
4790 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
4791 with newer architectures. Thanks to isha vishnoi for the heads
4792 up.&lt;/li&gt;
4793
4794 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
4795
4796 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4797 Matthias Klose.&lt;/li&gt;
4798
4799 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
4800 Petr Machata found in Fedora.&lt;/li&gt;
4801
4802 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
4803 .dynamic is a NULL terminated string. Based on patch found in
4804 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
4805
4806 &lt;/ul&gt;
4807
4808 &lt;p&gt;You can
4809 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
4810 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
4811 project if something is wrong with the new release. The test suite
4812 did not discover any old errors, so if you find a new one, please also
4813 include a testsuite check.&lt;/p&gt;
4814 </description>
4815 </item>
4816
4817 <item>
4818 <title>Debian init.d boot script example for rsyslog</title>
4819 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
4820 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
4821 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
4822 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
4823 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
4824 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
4825 init.d scripts at all. Here is an example init.d script, ie a rewrite
4826 of /etc/init.d/rsyslog:&lt;/p&gt;
4827
4828 &lt;p&gt;&lt;pre&gt;
4829 #!/lib/init/init-d-script
4830 ### BEGIN INIT INFO
4831 # Provides: rsyslog
4832 # Required-Start: $remote_fs $time
4833 # Required-Stop: umountnfs $time
4834 # X-Stop-After: sendsigs
4835 # Default-Start: 2 3 4 5
4836 # Default-Stop: 0 1 6
4837 # Short-Description: enhanced syslogd
4838 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4839 # It is quite compatible to stock sysklogd and can be
4840 # used as a drop-in replacement.
4841 ### END INIT INFO
4842 DESC=&quot;enhanced syslogd&quot;
4843 DAEMON=/usr/sbin/rsyslogd
4844 &lt;/pre&gt;&lt;/p&gt;
4845
4846 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
4847 script was 137 lines, and the above is just 15 lines, most of it meta
4848 info/comments.&lt;/p&gt;
4849
4850 &lt;p&gt;How to do this, you ask? Well, one create a new script
4851 /lib/init/init-d-script looking something like this:
4852
4853 &lt;p&gt;&lt;pre&gt;
4854 #!/bin/sh
4855
4856 # Define LSB log_* functions.
4857 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
4858 # and status_of_proc is working.
4859 . /lib/lsb/init-functions
4860
4861 #
4862 # Function that starts the daemon/service
4863
4864 #
4865 do_start()
4866 {
4867 # Return
4868 # 0 if daemon has been started
4869 # 1 if daemon was already running
4870 # 2 if daemon could not be started
4871 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
4872 || return 1
4873 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4874 $DAEMON_ARGS \
4875 || return 2
4876 # Add code here, if necessary, that waits for the process to be ready
4877 # to handle requests from services started subsequently which depend
4878 # on this one. As a last resort, sleep for some time.
4879 }
4880
4881 #
4882 # Function that stops the daemon/service
4883 #
4884 do_stop()
4885 {
4886 # Return
4887 # 0 if daemon has been stopped
4888 # 1 if daemon was already stopped
4889 # 2 if daemon could not be stopped
4890 # other if a failure occurred
4891 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
4892 RETVAL=&quot;$?&quot;
4893 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
4894 # Wait for children to finish too if this is a daemon that forks
4895 # and if the daemon is only ever run from this initscript.
4896 # If the above conditions are not satisfied then add some other code
4897 # that waits for the process to drop all resources that could be
4898 # needed by services started subsequently. A last resort is to
4899 # sleep for some time.
4900 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
4901 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
4902 # Many daemons don&#39;t delete their pidfiles when they exit.
4903 rm -f $PIDFILE
4904 return &quot;$RETVAL&quot;
4905 }
4906
4907 #
4908 # Function that sends a SIGHUP to the daemon/service
4909 #
4910 do_reload() {
4911 #
4912 # If the daemon can reload its configuration without
4913 # restarting (for example, when it is sent a SIGHUP),
4914 # then implement that here.
4915 #
4916 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
4917 return 0
4918 }
4919
4920 SCRIPTNAME=$1
4921 scriptbasename=&quot;$(basename $1)&quot;
4922 echo &quot;SN: $scriptbasename&quot;
4923 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
4924 script=&quot;$1&quot;
4925 shift
4926 . $script
4927 else
4928 exit 0
4929 fi
4930
4931 NAME=$(basename $DAEMON)
4932 PIDFILE=/var/run/$NAME.pid
4933
4934 # Exit if the package is not installed
4935 #[ -x &quot;$DAEMON&quot; ] || exit 0
4936
4937 # Read configuration variable file if it is present
4938 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
4939
4940 # Load the VERBOSE setting and other rcS variables
4941 . /lib/init/vars.sh
4942
4943 case &quot;$1&quot; in
4944 start)
4945 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
4946 do_start
4947 case &quot;$?&quot; in
4948 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
4949 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
4950 esac
4951 ;;
4952 stop)
4953 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
4954 do_stop
4955 case &quot;$?&quot; in
4956 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
4957 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
4958 esac
4959 ;;
4960 status)
4961 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
4962 ;;
4963 #reload|force-reload)
4964 #
4965 # If do_reload() is not implemented then leave this commented out
4966 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
4967 #
4968 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
4969 #do_reload
4970 #log_end_msg $?
4971 #;;
4972 restart|force-reload)
4973 #
4974 # If the &quot;reload&quot; option is implemented then remove the
4975 # &#39;force-reload&#39; alias
4976 #
4977 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
4978 do_stop
4979 case &quot;$?&quot; in
4980 0|1)
4981 do_start
4982 case &quot;$?&quot; in
4983 0) log_end_msg 0 ;;
4984 1) log_end_msg 1 ;; # Old process is still running
4985 *) log_end_msg 1 ;; # Failed to start
4986 esac
4987 ;;
4988 *)
4989 # Failed to stop
4990 log_end_msg 1
4991 ;;
4992 esac
4993 ;;
4994 *)
4995 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
4996 exit 3
4997 ;;
4998 esac
4999
5000 :
5001 &lt;/pre&gt;&lt;/p&gt;
5002
5003 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
5004 lot. I did not really polish the approach, so it might not always
5005 work out of the box, but you get the idea. I did not try very hard to
5006 optimize it nor make it more robust either.&lt;/p&gt;
5007
5008 &lt;p&gt;A better argument for switching init system in Debian than reducing
5009 the size of init scripts (which is a good thing to do anyway), is to
5010 get boot system that is able to handle the kernel events sensibly and
5011 robustly, and do not depend on the boot to run sequentially. The boot
5012 and the kernel have not behaved sequentially in years.&lt;/p&gt;
5013 </description>
5014 </item>
5015
5016 <item>
5017 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
5018 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
5019 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
5020 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
5021 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
5022 remote display access is the preferred solution with oVirt and RedHat
5023 Enterprise Virtualization, and I was sad to discover the other day
5024 that the browser plugin needed to use these systems seamlessly was
5025 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
5026 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
5027 2013-04-01, so I decided to wrap up a package based on the great work
5028 from Cajus Pollmeier and put it in a collab-maint maintained git
5029 repository to get a package I could use. I would very much like
5030 others to help me maintain the package (or just take over, I do not
5031 mind), but as no-one had volunteered so far, I just uploaded it to
5032 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
5033
5034 &lt;p&gt;The source is now available from
5035 &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;
5036 </description>
5037 </item>
5038
5039 <item>
5040 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
5041 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
5042 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
5043 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
5044 <description>&lt;p&gt;The
5045 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
5046 program is a a very nice system to create virtual machine images. It
5047 create a image file, add a partition table, mount it and run
5048 debootstrap in the mounted directory to create a Debian system on a
5049 stick. Yesterday, I decided to try to teach it how to make images for
5050 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
5051 of a plan to simplify the build system for
5052 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
5053 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
5054 the virtualbox images, but its current build system made multistrap
5055 based system for Dreamplug images, and it is lacking support for
5056 Raspberry Pi.&lt;/p&gt;
5057
5058 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
5059 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5060 code and adjusted it to be able to build armel images on my amd64
5061 Debian laptop. I ended up giving vmdebootstrap five new options,
5062 allowing me to replicate the image creation process I use to make
5063 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
5064 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
5065 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
5066 call debootstrap with --foreign and to copy the handler into the
5067 generated chroot before running the second stage. This allow
5068 vmdebootstrap to create armel images on an amd64 host. Next I added
5069 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
5070 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
5071 given file system type, allowing me to create an image with a vfat
5072 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
5073 variant&lt;/tt&gt; option to allow me to create smaller images without the
5074 Debian base system packages installed. Finally, I added an option
5075 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
5076 as a boot loader. It is not needed on the Raspberry Pi and probably
5077 most other non-x86 architectures. The changes were accepted by the
5078 upstream author of vmdebootstrap yesterday and today, and is now
5079 available from
5080 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
5081 upstream project page&lt;/a&gt;.&lt;/p&gt;
5082
5083 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
5084 create a small script (the customize script) to add the non-free
5085 binary blob needed to boot the Raspberry Pi and the APT source
5086 list:&lt;/p&gt;
5087
5088 &lt;p&gt;&lt;pre&gt;
5089 #!/bin/sh
5090 set -e # Exit on first error
5091 rootdir=&quot;$1&quot;
5092 cd &quot;$rootdir&quot;
5093 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
5094 deb http://http.debian.net/debian/ jessie main contrib non-free
5095 EOF
5096 # Install non-free binary blob needed to boot Raspberry Pi. This
5097 # install a kernel somewhere too.
5098 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5099 -O $rootdir/usr/bin/rpi-update
5100 chmod a+x $rootdir/usr/bin/rpi-update
5101 mkdir -p $rootdir/lib/modules
5102 touch $rootdir/boot/start.elf
5103 chroot $rootdir rpi-update
5104 &lt;/pre&gt;&lt;/p&gt;
5105
5106 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
5107 to build the image:&lt;/p&gt;
5108
5109 &lt;pre&gt;
5110 sudo ./vmdebootstrap \
5111 --variant minbase \
5112 --arch armel \
5113 --distribution jessie \
5114 --mirror http://http.debian.net/debian \
5115 --image test.img \
5116 --size 600M \
5117 --bootsize 64M \
5118 --boottype vfat \
5119 --log-level debug \
5120 --verbose \
5121 --no-kernel \
5122 --no-extlinux \
5123 --root-password raspberry \
5124 --hostname raspberrypi \
5125 --foreign /usr/bin/qemu-arm-static \
5126 --customize `pwd`/customize \
5127 --package netbase \
5128 --package git-core \
5129 --package binutils \
5130 --package ca-certificates \
5131 --package wget \
5132 --package kmod
5133 &lt;/pre&gt;&lt;/p&gt;
5134
5135 &lt;p&gt;The list of packages being installed are the ones needed by
5136 rpi-update to make the image bootable on the Raspberry Pi, with the
5137 exception of netbase, which is needed by debootstrap to find
5138 /etc/hosts with the minbase variant. I really wish there was a way to
5139 set up an Raspberry Pi using only packages in the Debian archive, but
5140 that is not possible as far as I know, because it boots from the GPU
5141 using a non-free binary blob.&lt;/p&gt;
5142
5143 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
5144 probably a few others installed. I have not checked the complete
5145 build dependency list.&lt;/p&gt;
5146
5147 &lt;p&gt;The resulting image will not use the hardware floating point unit
5148 on the Raspberry PI, because the armel architecture in Debian is not
5149 optimized for that use. So the images created will be a bit slower
5150 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
5151 </description>
5152 </item>
5153
5154 <item>
5155 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
5156 <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>
5157 <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>
5158 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
5159 <description>&lt;p&gt;The last few days I came across a few good causes that should get
5160 wider attention. I recommend signing and donating to each one of
5161 these. :)&lt;/p&gt;
5162
5163 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
5164 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
5165 Women program which is a Google Summer of Code like initiative to get
5166 more women involved in free software. One debian sponsor has offered
5167 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
5168 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
5169 hope you will to. :)&lt;/p&gt;
5170
5171 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
5172 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
5173 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
5174 take place these days, and their need to fund the work. I&#39;ve already
5175 donated. Are you next?&lt;/p&gt;
5176
5177 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
5178 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5179 statement under the heading
5180 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
5181 Access&lt;/a&gt; for those of us asking for more focus on open access in the
5182 Norwegian government. So far 499 signatures. I hope you will sign it
5183 too.&lt;/p&gt;
5184 </description>
5185 </item>
5186
5187 <item>
5188 <title>Videos about the Freedombox project - for inspiration and learning</title>
5189 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
5190 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
5191 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
5192 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
5193 project&lt;/a&gt; have been going on for a while, and have presented the
5194 vision, ideas and solution several places. Here is a little
5195 collection of videos of talks and presentation of the project.&lt;/p&gt;
5196
5197 &lt;ul&gt;
5198
5199 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
5200 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
5201
5202 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
5203 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
5204
5205 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
5206 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5207 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
5208 (Youtube)&lt;/li&gt;
5209
5210 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
5211 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
5212
5213 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
5214 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
5215
5216 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
5217 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5218 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
5219
5220 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
5221 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
5222 (Youtube)&lt;/li&gt;
5223
5224 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
5225 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
5226
5227 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
5228 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
5229
5230 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
5231 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5232 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
5233
5234 &lt;/ul&gt;
5235
5236 &lt;p&gt;A larger list is available from
5237 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
5238 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
5239
5240 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
5241 Jessie is coming along quite well, and soon both Owncloud and using
5242 Tor should be available for testers of the Freedombox solution. :) In
5243 a few weeks I hope everything needed to test it is included in Debian.
5244 The withsqlite package is already in Debian, and the plinth package is
5245 pending in NEW. The third and vital part of that puzzle is the
5246 metapackage/setup framework, which is still pending an upload. Join
5247 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
5248 (#freedombox on irc.debian.org)&lt;/a&gt; and
5249 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5250 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5251 </description>
5252 </item>
5253
5254 <item>
5255 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
5256 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
5257 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
5258 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
5259 <description>&lt;p&gt;I was introduced to the
5260 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
5261 in 2010, when Eben Moglen presented his vision about serving the need
5262 of non-technical people to keep their personal information private and
5263 within the legal protection of their own homes. The idea is to give
5264 people back the power over their network and machines, and return
5265 Internet back to its intended peer-to-peer architecture. Instead of
5266 depending on a central service, the Freedombox will give everyone
5267 control over their own basic infrastructure.&lt;/p&gt;
5268
5269 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
5270 taken priority. But this summers nasty news about the misuse of trust
5271 and privilege exercised by the &quot;western&quot; intelligence gathering
5272 communities increased my eagerness to contribute to a point where I
5273 actually started working on the project a while back.&lt;/p&gt;
5274
5275 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
5276 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
5277 create a simple and cheap Debian based appliance that anyone can hook
5278 up in their home and get access to secure and private services and
5279 communication. The initial deployment platform have been the
5280 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
5281 which is a piece of hardware I do not own. So to be able to test what
5282 the current Freedombox setup look like, I had to come up with a way to install
5283 it on some hardware I do have access to. I have rewritten the
5284 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
5285 image build framework to use .deb packages instead of only copying
5286 setup into the boot images, and thanks to this rewrite I am able to
5287 set up any machine supported by Debian Wheezy as a Freedombox, using
5288 the previously mentioned deb (and a few support debs for packages
5289 missing in Debian).&lt;/p&gt;
5290
5291 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
5292 scripts
5293 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
5294 and a administrative web interface
5295 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
5296 withsqlite), as well as a privacy enhancing proxy based on
5297 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
5298 (freedombox-privoxy). There is also a web/javascript based XMPP
5299 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
5300 trying (unsuccessfully so far) to talk to the XMPP server
5301 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
5302 web interface is pluggable, and the goal is to use it to enable OpenID
5303 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5304 this is really working yet, see
5305 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
5306 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
5307 on github at the moment. The HTTP proxy is operational out of the
5308 box, and the admin web interface can be used to add/remove plinth
5309 users. I&#39;ve not been able to do anything else with it so far, but
5310 know there are several branches spread around github and other places
5311 with lots of half baked features.&lt;/p&gt;
5312
5313 &lt;p&gt;Anyway, if you want to have a look at the current state, the
5314 following recipes should work to give you a test machine to poke
5315 at.&lt;/p&gt;
5316
5317 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
5318
5319 &lt;ol&gt;
5320
5321 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
5322 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
5323 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
5324 to the Debian installer:&lt;p&gt;
5325 &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;
5326
5327 &lt;li&gt;Answer the few language/region/password questions and pick disk to
5328 install on.&lt;/li&gt;
5329
5330 &lt;li&gt;When the installation is finished and the machine have rebooted a
5331 few times, your Freedombox is ready for testing.&lt;/li&gt;
5332
5333 &lt;/ol&gt;
5334
5335 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
5336
5337 &lt;ol&gt;
5338
5339 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
5340 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
5341 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
5342 &lt;pre&gt;
5343 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
5344 &lt;/pre&gt;&lt;/li&gt;
5345 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
5346 &lt;pre&gt;
5347 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5348 apt-key add -
5349 apt-get update
5350 apt-get install freedombox-setup
5351 /usr/lib/freedombox/setup
5352 &lt;/pre&gt;&lt;/li&gt;
5353 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
5354
5355 &lt;/ol&gt;
5356
5357 &lt;p&gt;You can test it on other architectures too, but because the
5358 freedombox-privoxy package is binary, it will only work as intended on
5359 the architectures where I have had time to build the binary and put it
5360 in my APT repository. But do not let this stop you. It is only a
5361 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
5362
5363 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
5364 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
5365 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
5366 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
5367
5368 &lt;p&gt;Please let me know if this works for you, or if you have any
5369 problems. We gather on the IRC channel
5370 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
5371 irc.debian.org and the
5372 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
5373 mailing list&lt;/a&gt;.&lt;/p&gt;
5374
5375 &lt;p&gt;Once you get your freedombox operational, you can visit
5376 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
5377 welcome screen (dead end - do not be surprised if you are unable to
5378 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
5379 to look at the rest of plinth. The default user is &#39;admin&#39; and the
5380 default password is &#39;secret&#39;.&lt;/p&gt;
5381 </description>
5382 </item>
5383
5384 <item>
5385 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
5386 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
5387 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
5388 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
5389 <description>&lt;p&gt;Earlier, I reported about
5390 &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
5391 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
5392 told by IBM that the original disk should be thrown away. And as
5393 there no longer was a problem if I bricked the firmware, I decided
5394 today to try to install Intel firmware to replace the Lenovo firmware
5395 currently on the disk.&lt;/p&gt;
5396
5397 &lt;p&gt;I searched the Intel site for firmware, and found
5398 &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;
5399 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5400 according to the site should contain the latest firmware for SSD
5401 disks. I inserted the broken disk in one of my spare laptops and
5402 booted the ISO from a USB stick. The disk was recognized, but the
5403 program claimed the newest firmware already were installed and refused
5404 to insert any Intel firmware. So no change, and the disk is still
5405 unable to handle write load. :( I guess the only way to get them
5406 working would be if Lenovo releases new firmware. No idea how likely
5407 that is. Anyway, just blogging about this test for completeness. I
5408 got a working Samsung disk, and see no point in spending more time on
5409 the broken disks.&lt;/p&gt;
5410 </description>
5411 </item>
5412
5413 <item>
5414 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
5415 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
5416 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
5417 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
5418 <description>&lt;p&gt;Today I switched to
5419 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
5420 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
5421 my new Thinkpad X230, which was delivered with an
5422 &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
5423 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
5424 sustained writes. My hardware supplier have been very forthcoming in
5425 trying to find a solution, and after first trying with another
5426 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
5427 disk instead to fix it once and for all. The Samsung disk survived
5428 the installation of Debian with encrypted disks (filling the disk with
5429 random data during installation killed the first two), and I thus
5430 decided to trust it with my data. I have installed it as a Debian Edu
5431 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5432 server at home using Kerberos and LDAP, and will use it as my work
5433 station from now on.&lt;/p&gt;
5434
5435 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
5436 Debian Wheezy default installation need to be tuned a bit to increase
5437 performance and increase life time of the disk. The Linux kernel and
5438 user space applications do not yet adjust automatically to such
5439 environment. To make it easier for my self, I created a draft Debian
5440 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
5441 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
5442 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
5443 is set up to adjust the setup of the machine by just installing the
5444 package. If there is any non-SSD disk in the machine, the package
5445 will refuse to install, as I did not try to write any logic to sort
5446 file systems in SSD and non-SSD file systems.&lt;/p&gt;
5447
5448 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
5449 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5450 where I set up the machine with one large encrypted partition (in
5451 addition to /boot), put LVM on top of this and set up partitions on
5452 top of this again. See the README file in the package source for the
5453 references I used to pick the settings. At the moment these
5454 parameters are tuned:&lt;/p&gt;
5455
5456 &lt;ul&gt;
5457
5458 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
5459 (adding discard to /etc/crypttab)&lt;/li&gt;
5460
5461 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
5462 this case a cryptsetup partition) by changing issue_discards from
5463 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
5464
5465 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
5466 systems.&lt;/li&gt;
5467
5468 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
5469 /etc/fstab.&lt;/li&gt;
5470
5471 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
5472
5473 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
5474 cron.daily).&lt;/li&gt;
5475
5476 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
5477 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
5478
5479 &lt;/ul&gt;
5480
5481 &lt;p&gt;During installation, I cancelled the part where the installer fill
5482 the disk with random data, as this would kill the SSD performance for
5483 little gain. My goal with the encrypted file system is to ensure
5484 those stealing my laptop end up with a brick and not a working
5485 computer. I have no hope in keeping the really resourceful people
5486 from getting the data on the disk (see
5487 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
5488 Thus I concluded that adding the discard option to crypttab is the
5489 right thing to do.&lt;/p&gt;
5490
5491 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
5492 it for SSD, but others recommended deadline and a benchmark I found
5493 indicated that deadline might be better for interactive use.&lt;/p&gt;
5494
5495 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
5496 and ext4, but read that it would give a performance hit ever time a
5497 file is removed, and thought it best to that that slowdown once a day
5498 instead of during my work.&lt;/p&gt;
5499
5500 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5501 this is already done by Debian Edu.&lt;/p&gt;
5502
5503 &lt;p&gt;I have not yet started on the user space tuning. I expect
5504 iceweasel need some tuning, and perhaps other applications too, but
5505 have not yet had time to investigate those parts.&lt;/p&gt;
5506
5507 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
5508 there.&lt;/p&gt;
5509
5510 &lt;p&gt;As for the answer to the question in the title of this blog post,
5511 as far as I know, the only solution I know about is to replace the
5512 disk. It might be possible to flash it with Intel firmware instead of
5513 the Lenovo firmware. But I have not tried and did not want to do so
5514 without approval from Lenovo as I wanted to keep the warranty on the
5515 disk until a solution was found and they wanted the broken disks
5516 back.&lt;/p&gt;
5517 </description>
5518 </item>
5519
5520 <item>
5521 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
5522 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
5523 <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>
5524 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
5525 <description>&lt;p&gt;A few days ago, I wrote about
5526 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
5527 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
5528 was dying during installation because it is unable to cope with
5529 sustained write. My supplier is in contact with
5530 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
5531 replacement disk to try to fix the problem. They decided to send an
5532 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
5533
5534 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
5535 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5536 same firmware version as the original. This time my hope raised
5537 slightly as the installation progressed, as the original disk used to
5538 die after 4-7% of the disk was written to, while this time it kept
5539 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
5540 died again and I was back on square one. I still do not have a new
5541 laptop with a disk I can trust. I can not live with a disk that might
5542 lock up when I download a new
5543 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
5544 other large files. I look forward to hearing from my supplier with
5545 the next proposal from Lenovo.&lt;/p&gt;
5546
5547 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
5548 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5549 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
5550 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
5551 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
5552 P/N 45N8295, P0C38732.&lt;/p&gt;
5553
5554 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
5555 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
5556 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
5557 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
5558 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
5559 P/N 45N8295, P0C38732.&lt;/p&gt;
5560
5561 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
5562 SA, date and WNPP values. Mentioning all the details here in case
5563 someone is able to use the information to find a way to identify the
5564 failing disk among working ones (if any such working disk actually
5565 exist).&lt;/p&gt;
5566 </description>
5567 </item>
5568
5569 <item>
5570 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
5571 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
5572 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
5573 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
5574 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
5575 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5576 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
5577 member assosiation NUUG&lt;/a&gt; and
5578 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
5579 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
5580 Bitraf&lt;/a&gt;.&lt;/p&gt;
5581
5582 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
5583 welcome, and there is no fee to participate. There is on the other
5584 hand limited space, and only room for 30 people. Please put your name
5585 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
5586 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
5587 </description>
5588 </item>
5589
5590 <item>
5591 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
5592 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
5593 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
5594 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
5595 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
5596 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
5597 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
5598 time to spend on it, and it took a while to find a model I believe
5599 will do the job, but two days ago the replacement finally arrived. I
5600 ended up picking a
5601 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
5602 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5603 a roaming workstation, and it seemed to work flawlessly. But my
5604 second installation with encrypted disk was not as successful. More
5605 on that below.&lt;/p&gt;
5606
5607 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
5608 important requirements (robust and with a good keyboard) are never
5609 listed in the feature list. But I did get good help from the search
5610 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
5611 allowed me to limit the list of interesting laptops based on my other
5612 requirements. A bit surprising that SSD disk are not disks according
5613 to that search interface, so I had to drop specifying the number of
5614 disks from my search parameters. I also asked around among friends to
5615 get their impression on keyboards and robustness.&lt;/p&gt;
5616
5617 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
5618 X41. I am not quite convinced about the keyboard, as it is
5619 significantly wider than my old keyboard, and I have to stretch my
5620 hand a lot more to reach the edges. But the key response is fairly
5621 good and the individual key shape is fairly easy to handle, so I hope
5622 I will get used to it. My old X40 was starting to fail, and I really
5623 needed a new laptop now. :)&lt;/p&gt;
5624
5625 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
5626 visit to the BIOS during boot it disable it.&lt;/p&gt;
5627
5628 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
5629 lock up during load. And this happen when installing Debian Wheezy
5630 with encrypted disk, while the disk is being filled with random data.
5631 I also tested to install Ubuntu Raring, and it happen there too if I
5632 reenable the code to fill the disk with random data (it is disabled by
5633 default in Ubuntu). And the bug with is already known. It was
5634 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
5635 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
5636 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5637 kernel developers as
5638 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
5639 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
5640 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5641 Lenovo forums, both for
5642 &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
5643 2012-11-10&lt;/a&gt; and for
5644 &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
5645 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
5646 reports state that the disk lock up during use if many writes are done
5647 on the disk, so it is much no use to work around the installation
5648 problem and end up with a computer that can lock up at any moment.
5649 There is even a
5650 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
5651 available&lt;/a&gt; that will lock up the hard drive after running a few
5652 minutes by writing to a file.&lt;/p&gt;
5653
5654 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
5655 contacting PCHELP Norway (request 01D1FDP) which handle support
5656 requests for Lenovo, his first suggestion was to upgrade the disk
5657 firmware. Unfortunately there is no newer firmware available from
5658 Lenovo, as my disk already have the most recent one (version LF1i). I
5659 hope to hear more from him today and hope the problem can be
5660 fixed. :)&lt;/p&gt;
5661 </description>
5662 </item>
5663
5664 <item>
5665 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
5666 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
5667 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
5668 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
5669 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
5670 trusty old Thinkpad X41. Unfortunately I did not have much time to
5671 spend on it, but today the replacement finally arrived. I ended up
5672 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
5673 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
5674 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5675 this, it is installing what I hope will be a more final installation,
5676 with a encrypted hard drive to ensure any dope head stealing it end up
5677 with an expencive door stop.&lt;/p&gt;
5678
5679 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
5680 important requirements (robust and with a good keyboard) are never
5681 listed in the feature list. But I did get good help from the search
5682 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
5683 allowed me to limit the list of interesting laptops based on my other
5684 requirements. A bit surprising that SSD disk are not disks, so I had
5685 to drop number of disks from my search parameters.&lt;/p&gt;
5686
5687 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
5688 wider than my old keyboard, and I have to stretch my hand a lot more
5689 to reach the edges. But the key response is fairly good and the
5690 individual key shape is fairly easy to handle, so I hope I will get
5691 used to it. My old X40 was starting to fail, and I really needed a
5692 new laptop now. :)&lt;/p&gt;
5693
5694 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
5695 </description>
5696 </item>
5697
5698 <item>
5699 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
5700 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
5701 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
5702 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
5703 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
5704 perfectly capable of, and I have to do it manually to get things
5705 working. One such task is to find out what firmware packages are
5706 needed to get the hardware on my computer working. Most often this
5707 affect the wifi card, but some times it even affect the RAID
5708 controller or the ethernet card. Today I pushed version 0.4 of the
5709 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
5710 including a new script isenkram-autoinstall-firmware handling the
5711 process of asking all the loaded kernel modules what firmware files
5712 they want, find debian packages providing these files and install the
5713 debian packages. Here is a test run on my laptop:&lt;/p&gt;
5714
5715 &lt;p&gt;&lt;pre&gt;
5716 # isenkram-autoinstall-firmware
5717 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5718 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5719 info: locating packages with the requested firmware files
5720 info: Updating APT sources after adding non-free APT source
5721 info: trying to install firmware-ipw2x00
5722 firmware-ipw2x00
5723 firmware-ipw2x00
5724 Preconfiguring packages ...
5725 Selecting previously deselected package firmware-ipw2x00.
5726 (Reading database ... 259727 files and directories currently installed.)
5727 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5728 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
5729 #
5730 &lt;/pre&gt;&lt;/p&gt;
5731
5732 &lt;p&gt;When all the requested firmware is present, a simple message is
5733 printed instead:&lt;/p&gt;
5734
5735 &lt;p&gt;&lt;pre&gt;
5736 # isenkram-autoinstall-firmware
5737 info: did not find any firmware files requested by loaded kernel modules. exiting
5738 #
5739 &lt;/pre&gt;&lt;/p&gt;
5740
5741 &lt;p&gt;It could use some polish, but it is already working well and saving
5742 me some time when setting up new machines. :)&lt;/p&gt;
5743
5744 &lt;p&gt;So, how does it work? It look at the set of currently loaded
5745 kernel modules, and look up each one of them using modinfo, to find
5746 the firmware files listed in the module meta-information. Next, it
5747 download the Contents file from a nearby APT mirror, and search for
5748 the firmware files in this file to locate the package with the
5749 requested firmware file. If the package is in the non-free section, a
5750 non-free APT source is added and the package is installed using
5751 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
5752 machine.&lt;/p&gt;
5753
5754 &lt;p&gt;I hope someone find time to implement a more polished version of
5755 this script as part of the hw-detect debian-installer module, to
5756 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
5757 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
5758 firmware during a PXE install when the packages already are available
5759 from the nearby Debian mirror.&lt;/p&gt;
5760 </description>
5761 </item>
5762
5763 <item>
5764 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
5765 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
5766 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
5767 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
5768 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5769 the screen just turn black when Linux boot, either during installation
5770 or on first boot from the hard disk. I&#39;ve seen it once in a while the
5771 last few years, but only recently understood the cause. I&#39;ve seen it
5772 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5773 The reason seem to be in the wiring of some laptops. The system to
5774 control the screen background light is inverted, so when Linux try to
5775 turn the brightness fully on, it end up turning it off instead. I do
5776 not know which Linux drivers are affected, but this post is about the
5777 i915 driver used by the
5778 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
5779 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
5780
5781 &lt;p&gt;The problem can be worked around two ways. Either by adding
5782 i915.invert_brightness=1 as a kernel option, or by adding a file in
5783 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
5784 option when it load the i915 kernel module. On Debian and Ubuntu, it
5785 can be done by running these commands as root:&lt;/p&gt;
5786
5787 &lt;pre&gt;
5788 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
5789 update-initramfs -u -k all
5790 &lt;/pre&gt;
5791
5792 &lt;p&gt;Since March 2012 there is
5793 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
5794 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
5795 hardware have this problem, and get the driver to invert the
5796 brightness setting automatically. To use it, one need to add a row in
5797 &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
5798 intel_quirks array&lt;/a&gt; in the driver source
5799 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
5800 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
5801 number (vendor number 8086 is assumed) and subdevice vendor and device
5802 number.&lt;/p&gt;
5803
5804 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
5805 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
5806
5807 &lt;p&gt;&lt;pre&gt;
5808 00:02.0 VGA compatible controller [0300]: Intel Corporation \
5809 3rd Gen Core processor Graphics Controller [8086:0156] \
5810 (rev 09) (prog-if 00 [VGA controller])
5811 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
5812 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5813 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5814 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
5815 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
5816 Latency: 0
5817 Interrupt: pin A routed to IRQ 42
5818 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
5819 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
5820 Region 4: I/O ports at 4000 [size=64]
5821 Expansion ROM at &lt;unassigned&gt; [disabled]
5822 Capabilities: &lt;access denied&gt;
5823 Kernel driver in use: i915
5824 &lt;/pre&gt;&lt;/p&gt;
5825
5826 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
5827
5828 &lt;p&gt;&lt;pre&gt;
5829 struct intel_quirk intel_quirks[] = {
5830 ...
5831 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5832 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
5833 ...
5834 }
5835 &lt;/pre&gt;&lt;/p&gt;
5836
5837 &lt;p&gt;According to the kernel module instructions (as seen using
5838 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
5839 invert_brightness flag should be sent to the
5840 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
5841 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
5842 developers. But my email about the laptop sent 2013-06-03 have not
5843 yet shown up in
5844 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
5845 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
5846 emails from non-subscribers. Because of this, I sent my patch also to
5847 the Debian bug tracking system instead as
5848 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
5849 sure the patch is not lost.&lt;/p&gt;
5850
5851 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
5852 with this problem working properly with Linux. If you use Gnome, your
5853 worries should be over at this point. But if you use KDE, there is
5854 something in KDE ignoring the invert_brightness setting and turning on
5855 the screen during login. I&#39;ve reported it to Debian as
5856 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
5857 have no idea yet how to figure out exactly what subsystem is doing
5858 this. Perhaps you can help? Perhaps you know what the Gnome
5859 developers did to handle this, and this can give a clue to the KDE
5860 developers? Or you know where in KDE the screen brightness is changed
5861 during login? If so, please update the BTS report (or get in touch if
5862 you do not know how to update BTS).&lt;/p&gt;
5863
5864 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
5865 acpi_backlight=vendor, to disable ACPI backlight support completely,
5866 as the ACPI information on the machine is trash and it is better to
5867 leave it to the intel video driver to control the screen
5868 backlight.&lt;/p&gt;
5869 </description>
5870 </item>
5871
5872 <item>
5873 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
5874 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
5875 <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>
5876 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
5877 <description>&lt;p&gt;Two days ago, I asked
5878 &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
5879 I could install Linux on a Packard Bell EasyNote LV computer
5880 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
5881 with the obstacles put in the way of Linux users on a laptop with UEFI
5882 and Windows 8.&lt;/p&gt;
5883
5884 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
5885 secure booting or fast boot. I suspect fast boot was the problem,
5886 causing the firmware to boot directly from HD without considering any
5887 key presses and alternative devices, but do not know UEFI settings
5888 enough to tell.&lt;/p&gt;
5889
5890 &lt;p&gt;There is no way to install Linux on the machine in question without
5891 opening the box and disconnecting the hard drive! This is as far as I
5892 can tell, the only way to get access to the firmware setup menu
5893 without accepting the Windows 8 license agreement. I am told (and
5894 found description on how to) that it is possible to configure the
5895 firmware setup once booted into Windows 8. But as I believe the terms
5896 of that agreement are completely unacceptable, accepting the license
5897 was never an alternative. I do not enter agreements I do not intend
5898 to follow.&lt;/p&gt;
5899
5900 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
5901 waste many hours on this, but luckily there was a way to get it to
5902 work. But I would not recommend it to anyone planning to run Linux on
5903 it, and I have become sceptical to Windows 8 certified laptops. Is
5904 this the way Linux will be forced out of the market place, by making
5905 it close to impossible for &quot;normal&quot; users to install Linux without
5906 accepting the Microsoft Windows license terms? Or at least not
5907 without risking to loose the warranty?&lt;/p&gt;
5908
5909 &lt;p&gt;I&#39;ve updated the
5910 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
5911 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
5912 do not have to struggle as much as I did to get Linux into the
5913 machine.&lt;/p&gt;
5914
5915 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5916 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
5917 </description>
5918 </item>
5919
5920 <item>
5921 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
5922 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
5923 <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>
5924 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
5925 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
5926 new laptops for my parents and a few others. I bought Packard Bell
5927 Easynote LV to run Kubuntu on and use as their home computer. But I
5928 am completely unable to figure out how to install Linux on it. The
5929 computer is preinstalled with Windows 8, and I suspect it uses UEFI
5930 instead of a BIOS to boot.&lt;/p&gt;
5931
5932 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
5933 to get it to boot the Linux installer from my USB stick. I have yet
5934 to try the DVD install, and still hope it will work. when I turn on
5935 the computer, there is no information on what buttons to press to get
5936 the normal boot menu. I expect to get some boot menu to select PXE or
5937 USB stick booting. When booting, it first ask for the language to
5938 use, then for some regional settings, and finally if I will accept the
5939 Windows 8 terms of use. As these terms are completely unacceptable to
5940 me, I have no other choice but to turn off the computer and try again
5941 to get it to boot the Linux installer.&lt;/p&gt;
5942
5943 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
5944 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
5945 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
5946 installed on this machine, please get in touch or update that wiki
5947 page. If I can&#39;t find a way to install Linux, I will have to return
5948 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
5949
5950 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
5951 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
5952 on new Laptops?&lt;/p&gt;
5953 </description>
5954 </item>
5955
5956 <item>
5957 <title>How to transform a Debian based system to a Debian Edu installation</title>
5958 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
5959 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
5960 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
5961 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
5962 an operating system based on Debian intended for use in schools. It
5963 contain a turn-key solution for the computer network provided to
5964 pupils in the primary schools. It provide both the central server,
5965 network boot servers and desktop environments with heaps of
5966 educational software. The project was founded almost 12 years ago,
5967 2001-07-02. If you want to support the project, which is in need for
5968 cash to fund developer gatherings and other project related activity,
5969 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
5970 donate some money&lt;/a&gt;.
5971
5972 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
5973 lists and elsewhere, is the question on how to transform a Debian or
5974 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
5975 hard, and last week I wrote a script to replicate the steps done by
5976 the Debian Edu installer.&lt;/p&gt;
5977
5978 &lt;p&gt;The script,
5979 &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;
5980 in the debian-edu-config package, will go through these six steps and
5981 transform an existing Debian Wheezy or Ubuntu (untested) installation
5982 into a Debian Edu Workstation:&lt;/p&gt;
5983
5984 &lt;ol&gt;
5985
5986 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
5987 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
5988 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
5989 our configuration.&lt;/li&gt;
5990 &lt;li&gt;Preseed debconf database with profile setup in
5991 /etc/debian-edu/config, and run tasksel to install packages
5992 according to the profile specified in the config above,
5993 overriding some of the Debian automation machinery.&lt;/li&gt;
5994 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
5995 that could not be done using preseeding.&lt;/li&gt;
5996 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
5997
5998 &lt;/ol&gt;
5999
6000 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
6001 replicated like this. Disk partitioning and LVM setup, for example.
6002 So this script just assume there is enough disk space to install all
6003 the needed packages.&lt;/p&gt;
6004
6005 &lt;p&gt;The script was created to help a Debian Edu student working on
6006 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
6007 Debian Edu client, and using it he can take the existing
6008 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
6009 transform it into a fully functioning Debian Edu Workstation (or
6010 Roaming Workstation, or whatever :).&lt;/p&gt;
6011
6012 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
6013 If a LXDE based Roaming workstation is wanted instead, modify the
6014 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
6015
6016 &lt;p&gt;&lt;pre&gt;
6017 PROFILE=&quot;Roaming-Workstation&quot;
6018 DESKTOP=&quot;lxde&quot;
6019 &lt;/pre&gt;&lt;/p&gt;
6020
6021 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
6022 the cloud, by starting with a virtual Debian installation at some
6023 virtual hosting service and setting up all the services on first
6024 boot.&lt;/p&gt;
6025 </description>
6026 </item>
6027
6028 <item>
6029 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
6030 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
6031 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
6032 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
6033 <description>&lt;P&gt;In January,
6034 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
6035 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
6036 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
6037 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
6038 marvellous construction system from Denmark. We also created
6039 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
6040 a place to take notes and write down our plans and hopes. And several
6041 people showed up to help. I was very happy to see the effect of my
6042 call. Since the small start, we have a debtags tag
6043 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
6044 tag for LEGO related packages, and now count 10 packages related to
6045 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
6046
6047 &lt;p&gt;&lt;table&gt;
6048 &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;
6049 &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;
6050 &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;
6051 &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;
6052 &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;
6053 &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;
6054 &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;
6055 &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;
6056 &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;
6057 &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;
6058 &lt;/table&gt;&lt;/p&gt;
6059
6060 &lt;p&gt;Some of these are available in Wheezy, and all but one are
6061 currently available in Jessie/testing. leocad is so far only
6062 available in experimental.&lt;/p&gt;
6063
6064 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
6065 adding the rest of the great free software tools available on Linux
6066 for LEGO designers.&lt;/p&gt;
6067 </description>
6068 </item>
6069
6070 <item>
6071 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
6072 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
6073 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
6074 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
6075 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
6076 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
6077 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
6078 Debian release, and I expect to move my machines at home over to it fairly
6079 soon.&lt;/p&gt;
6080
6081 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
6082 in particular make me very happy to see included. The
6083 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
6084 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
6085 included for the first time. Alongside similar programs like
6086 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
6087 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
6088 it allow for visual programming where syntax errors can not happen,
6089 and a friendly programming environment for learning to control the
6090 computer. Scratch will also be included in the next release of Debian
6091 Edu.&lt;/a&gt;
6092
6093 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
6094 Edu/Skolelinux release too. The
6095 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
6096 alpha release&lt;/a&gt; went out last week, and the next should soon
6097 follow.&lt;p&gt;
6098 </description>
6099 </item>
6100
6101 <item>
6102 <title>Isenkram 0.2 finally in the Debian archive</title>
6103 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
6104 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
6105 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
6106 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
6107 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
6108 for many months. I uploaded it to the Debian experimental suite
6109 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
6110
6111 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
6112 install to work with a pluggable hardware device. The suggestion pop
6113 up when the device is plugged in. For example if a Lego Mindstorm NXT
6114 is inserted, it will suggest to install the program needed to program
6115 the NXT controller. Give it a go, and report bugs and suggestions to
6116 BTS. :)&lt;/p&gt;
6117 </description>
6118 </item>
6119
6120 <item>
6121 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
6122 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
6123 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
6124 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
6125 <description>&lt;p&gt;My
6126 &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
6127 bitcoin related blog post&lt;/a&gt; mentioned that the new
6128 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
6129 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6130 2013-01-19, and have been available in unstable since then. It was
6131 automatically copied to Ubuntu, and is available in their Raring
6132 version too.&lt;/p&gt;
6133
6134 &lt;p&gt;But there is a strange problem with the build that block this new
6135 version from being available on the i386 and kfreebsd-i386
6136 architectures. For some strange reason, the autobuilders in Debian
6137 for these architectures fail to run the test suite on these
6138 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
6139 We are so far unable to reproduce it when building it manually, and
6140 no-one have been able to propose a fix. If you got an idea what is
6141 failing, please let us know via the BTS.&lt;/p&gt;
6142
6143 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
6144 I often run low on disk space, is the fact that the client will exit
6145 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
6146 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
6147 it. :)&lt;/p&gt;
6148
6149 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
6150 activities, please send Bitcoin donations to my address
6151 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6152 </description>
6153 </item>
6154
6155 <item>
6156 <title>Welcome to the world, Isenkram!</title>
6157 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
6158 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
6159 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
6160 <description>&lt;p&gt;Yesterday, I
6161 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
6162 for testers&lt;/a&gt; for my prototype for making Debian better at handling
6163 pluggable hardware devices, which I
6164 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
6165 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
6166 up, and caused me to really want to to open up the development to more
6167 people. But before I did this, I want to come up with a sensible name
6168 for this project. Today I finally decided on a new name, and I have
6169 renamed the project from hw-support-handler to this new name. In the
6170 process, I moved the source to git and made it available as a
6171 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
6172 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
6173 To fetch and build the latest version of the source, use&lt;/p&gt;
6174
6175 &lt;pre&gt;
6176 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6177 cd isenkram &amp;&amp; git-buildpackage -us -uc
6178 &lt;/pre&gt;
6179
6180 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
6181 want to hack on the source or improve the package, please go ahead.
6182 But please talk to me first on IRC or via email before you do major
6183 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
6184
6185 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
6186 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6187 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
6188 the German word eisenkram, for those that are familiar with that
6189 word.&lt;/p&gt;
6190
6191 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
6192 instructions, to avoid confusing people with an error from the signing
6193 process.&lt;/p&gt;
6194
6195 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
6196 clone argument to avoid the need for authentication.&lt;/p&gt;
6197 </description>
6198 </item>
6199
6200 <item>
6201 <title>First prototype ready making hardware easier to use in Debian</title>
6202 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
6203 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
6204 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
6205 <description>&lt;p&gt;Early this month I set out to try to
6206 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
6207 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
6208 prototype is working, and it is ready for a larger audience. To test
6209 it, fetch the
6210 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
6211 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
6212 package. You might have to log out and in again activate the
6213 autostart script.&lt;/p&gt;
6214
6215 &lt;p&gt;The design is simple:&lt;/p&gt;
6216
6217 &lt;ul&gt;
6218
6219 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
6220 hw-support-handlerd to start when the user log in.&lt;/li&gt;
6221
6222 &lt;li&gt;This program listen for kernel events about new hardware (directly
6223 from the kernel like udev does), not using HAL dbus events as I
6224 initially did.&lt;/li&gt;
6225
6226 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
6227 the APT database, a database
6228 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
6229 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
6230
6231 &lt;li&gt;If a package is mapped to the hardware in question, the package
6232 isn&#39;t installed yet and this is the first time the hardware was
6233 plugged in, show a desktop notification suggesting to install the
6234 package or packages.&lt;/li&gt;
6235
6236 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
6237 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
6238
6239 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
6240 package while showing progress information in a window.&lt;/li&gt;
6241
6242 &lt;/ul&gt;
6243
6244 &lt;p&gt;I still need to come up with a better name for the system. Here
6245 are some screen shots showing the prototype in action. First the
6246 notification, then the password request, and finally the request to
6247 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
6248
6249 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
6250 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
6251 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
6252 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
6253 &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;
6254
6255 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
6256 is already useful. The database of hardware to package mappings also
6257 need more work. It is currently compatible with the Ubuntu way of
6258 storing such information in the package control file, but could be
6259 changed to use other formats instead or in addition to the current
6260 method. I&#39;ve dropped the use of discover for this mapping, as the
6261 modalias approach is more flexible and easier to use on Linux as long
6262 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
6263
6264 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
6265 here is the command required to check out and build the source: Use
6266 &#39;&lt;tt&gt;svn checkout
6267 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6268 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
6269 devscripts package.&lt;/p&gt;
6270
6271 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
6272 renamed to Isenkram and the source moved from the Debian Edu
6273 subversion repository to a Debian collab-maint git repository. See
6274 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
6275 instructions&lt;/a&gt; for details.&lt;/p&gt;
6276 </description>
6277 </item>
6278
6279 <item>
6280 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
6281 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
6282 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
6283 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
6284 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
6285 suddenly in bed. With a quiet whimper, it went completely quiet and
6286 black. The power button was no longer able to turn it on. It was a
6287 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6288 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6289 Compaq I had before that. Now I need to find a replacement. To keep
6290 going during Christmas, I moved the one year old SSD disk to my old
6291 X40 where it fitted (only one I had left that could use it), but it is
6292 not a durable solution.
6293
6294 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
6295 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
6296
6297 &lt;ul&gt;
6298
6299 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
6300 than A4).&lt;/li&gt;
6301 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
6302 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
6303 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
6304 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
6305 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
6306 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
6307 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
6308 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
6309 size).&lt;/li&gt;
6310 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
6311 X.org packages.&lt;/li&gt;
6312 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
6313 the time).
6314
6315 &lt;/ul&gt;
6316
6317 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
6318 list. The reason is simply that the specifications on laptops the
6319 last 10-15 years have been sufficient for my needs, and I have to look
6320 at other features to choose my laptop. But are there still made as
6321 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6322 robust, and Thinkpads seem to be heading in the wrong direction since
6323 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
6324 still be useful.&lt;/p&gt;
6325
6326 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
6327 external keyboard? I&#39;ll have to check the
6328 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
6329 well-supported laptops, or perhaps just buy one preinstalled from one
6330 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
6331 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
6332 </description>
6333 </item>
6334
6335 <item>
6336 <title>How to find a browser plugin supporting a given MIME type</title>
6337 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
6338 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
6339 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
6340 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
6341 install to get support for a given MIME type. Thanks to
6342 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
6343 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
6344 Unfortunately, not very many packages provide the needed meta
6345 information, Anyway, here is a small script to look up all browser
6346 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
6347
6348 &lt;pre&gt;
6349 #!/usr/bin/python
6350 import sys
6351 import apt
6352 def pkgs_handling_mimetype(mimetype):
6353 cache = apt.Cache()
6354 cache.open(None)
6355 thepkgs = []
6356 for pkg in cache:
6357 version = pkg.candidate
6358 if version is None:
6359 version = pkg.installed
6360 if version is None:
6361 continue
6362 record = version.record
6363 if not record.has_key(&#39;Npp-MimeType&#39;):
6364 continue
6365 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
6366 for t in mime_types:
6367 t = t.rstrip().strip()
6368 if t == mimetype:
6369 thepkgs.append(pkg.name)
6370 return thepkgs
6371 mimetype = &quot;audio/ogg&quot;
6372 if 1 &lt; len(sys.argv):
6373 mimetype = sys.argv[1]
6374 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
6375 for pkg in pkgs_handling_mimetype(mimetype):
6376 print &quot; %s&quot; %pkg
6377 &lt;/pre&gt;
6378
6379 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
6380
6381 &lt;pre&gt;
6382 % ./apt-find-browserplug-for-mimetype
6383 Browser plugin packages supporting audio/ogg:
6384 gecko-mediaplayer
6385 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6386 Browser plugin packages supporting application/x-shockwave-flash:
6387 browser-plugin-gnash
6388 %
6389 &lt;/pre&gt;
6390
6391 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
6392 itself to query for plugins and propose to install the needed
6393 packages. It would be great if Debian supported such feature too. Is
6394 anyone working on adding it?&lt;/p&gt;
6395
6396 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
6397 request for icweasel support for this feature is
6398 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
6399 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
6400 of manpower and wish for a different design is the reason thus feature
6401 is not yet in iceweasel from Debian.&lt;/p&gt;
6402 </description>
6403 </item>
6404
6405 <item>
6406 <title>What is the most supported MIME type in Debian?</title>
6407 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
6408 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
6409 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
6410 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
6411 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
6412 proposal to make it possible for a Desktop application to propose to
6413 the user some package to install to gain support for a given MIME
6414 type, font, library etc. that is currently missing. With such
6415 mechanism in place, it would be possible for the desktop to
6416 automatically propose and install leocad if some LDraw file is
6417 downloaded by the browser.&lt;/p&gt;
6418
6419 &lt;p&gt;To get some idea about the current content of the archive, I decided
6420 to write a simple program to extract all .desktop files from the
6421 Debian archive and look up the claimed MIME support there. The result
6422 can be found on the
6423 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
6424 site&lt;/a&gt;. Using the collected information, it become possible to
6425 answer the question in the title. Here are the 20 most supported MIME
6426 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6427 The complete list is available from the link above.&lt;/p&gt;
6428
6429 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
6430
6431 &lt;pre&gt;
6432 count MIME type
6433 ----- -----------------------
6434 32 text/plain
6435 30 audio/mpeg
6436 29 image/png
6437 28 image/jpeg
6438 27 application/ogg
6439 26 audio/x-mp3
6440 25 image/tiff
6441 25 image/gif
6442 22 image/bmp
6443 22 audio/x-wav
6444 20 audio/x-flac
6445 19 audio/x-mpegurl
6446 18 video/x-ms-asf
6447 18 audio/x-musepack
6448 18 audio/x-mpeg
6449 18 application/x-ogg
6450 17 video/mpeg
6451 17 audio/x-scpls
6452 17 audio/ogg
6453 16 video/x-ms-wmv
6454 &lt;/pre&gt;
6455
6456 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
6457
6458 &lt;pre&gt;
6459 count MIME type
6460 ----- -----------------------
6461 33 text/plain
6462 32 image/png
6463 32 image/jpeg
6464 29 audio/mpeg
6465 27 image/gif
6466 26 image/tiff
6467 26 application/ogg
6468 25 audio/x-mp3
6469 22 image/bmp
6470 21 audio/x-wav
6471 19 audio/x-mpegurl
6472 19 audio/x-mpeg
6473 18 video/mpeg
6474 18 audio/x-scpls
6475 18 audio/x-flac
6476 18 application/x-ogg
6477 17 video/x-ms-asf
6478 17 text/html
6479 17 audio/x-musepack
6480 16 image/x-xbitmap
6481 &lt;/pre&gt;
6482
6483 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
6484
6485 &lt;pre&gt;
6486 count MIME type
6487 ----- -----------------------
6488 31 text/plain
6489 31 image/png
6490 31 image/jpeg
6491 29 audio/mpeg
6492 28 application/ogg
6493 27 image/gif
6494 26 image/tiff
6495 26 audio/x-mp3
6496 23 audio/x-wav
6497 22 image/bmp
6498 21 audio/x-flac
6499 20 audio/x-mpegurl
6500 19 audio/x-mpeg
6501 18 video/x-ms-asf
6502 18 video/mpeg
6503 18 audio/x-scpls
6504 18 application/x-ogg
6505 17 audio/x-musepack
6506 16 video/x-ms-wmv
6507 16 video/x-msvideo
6508 &lt;/pre&gt;
6509
6510 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
6511 information mentioned in DEP-11. I have not yet had time to look at
6512 it, but hope the PackageKit people in Debian are on top of these
6513 issues.&lt;/p&gt;
6514
6515 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
6516 discovering a typo in my script.&lt;/p&gt;
6517 </description>
6518 </item>
6519
6520 <item>
6521 <title>Using modalias info to find packages handling my hardware</title>
6522 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
6523 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
6524 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
6525 <description>&lt;p&gt;Yesterday, I wrote about the
6526 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
6527 values provided by the Linux kernel&lt;/a&gt; following my hope for
6528 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
6529 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
6530 modalias values attached to package names can be used to map packages
6531 to hardware. This allow the system to look up and suggest relevant
6532 packages when I plug in some new hardware into my machine, and replace
6533 discover and discover-data as the database used to map hardware to
6534 packages.&lt;/p&gt;
6535
6536 &lt;p&gt;I create a modaliases file with entries like the following,
6537 containing package name, kernel module name (if relevant, otherwise
6538 the package name) and globs matching the relevant hardware
6539 modalias.&lt;/p&gt;
6540
6541 &lt;p&gt;&lt;blockquote&gt;
6542 Package: package-name
6543 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
6544 &lt;/blockquote&gt;&lt;/p&gt;
6545
6546 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
6547 for a given modalias value using this file.&lt;/p&gt;
6548
6549 &lt;p&gt;An entry like this would suggest the video and picture application
6550 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
6551
6552 &lt;p&gt;&lt;blockquote&gt;
6553 Package: cheese
6554 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
6555 &lt;/blockquote&gt;&lt;/p&gt;
6556
6557 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
6558 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
6559
6560 &lt;p&gt;&lt;blockquote&gt;
6561 Package: pcmciautils
6562 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6563 &lt;/blockquote&gt;&lt;/p&gt;
6564
6565 &lt;p&gt;An entry like this would suggest the package colorhug-client when
6566 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
6567
6568 &lt;p&gt;&lt;blockquote&gt;
6569 Package: colorhug-client
6570 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
6571 &lt;/blockquote&gt;&lt;/p&gt;
6572
6573 &lt;p&gt;I believe the format is compatible with the format of the Packages
6574 file in the Debian archive. Ubuntu already uses their Packages file
6575 to store their mappings from packages to hardware.&lt;/p&gt;
6576
6577 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
6578 announce the hardware it support in a way my prototype understand.
6579 This allow those publishing packages in an APT source outside the
6580 Debian archive as well as those backporting packages to make sure the
6581 hardware mapping are included in the package meta information. I&#39;ve
6582 tested such header in the pymissile package, and its modalias mapping
6583 is working as it should with my prototype. It even made it to Ubuntu
6584 Raring.&lt;/p&gt;
6585
6586 &lt;p&gt;To test if it was possible to look up supported hardware using only
6587 the shell tools available in the Debian installer, I wrote a shell
6588 implementation of the lookup code. The idea is to create files for
6589 each modalias and let the shell do the matching. Please check out and
6590 try the
6591 &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;
6592 shell script. It run without any extra dependencies and fetch the
6593 hardware mappings from the Debian archive and the subversion
6594 repository where I currently work on my prototype.&lt;/p&gt;
6595
6596 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
6597 install yubikey-personalization:&lt;/p&gt;
6598
6599 &lt;p&gt;&lt;blockquote&gt;
6600 % ./hw-support-lookup
6601 &lt;br&gt;yubikey-personalization
6602 &lt;br&gt;%
6603 &lt;/blockquote&gt;&lt;/p&gt;
6604
6605 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6606 propose to install the pcmciautils package:&lt;/p&gt;
6607
6608 &lt;p&gt;&lt;blockquote&gt;
6609 % ./hw-support-lookup
6610 &lt;br&gt;pcmciautils
6611 &lt;br&gt;%
6612 &lt;/blockquote&gt;&lt;/p&gt;
6613
6614 &lt;p&gt;If you know of any hardware-package mapping that should be added to
6615 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
6616 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
6617
6618 &lt;p&gt;It could be possible to generate several of the mappings between
6619 packages and hardware. One source would be to look at packages with
6620 kernel modules, ie packages with *.ko files in /lib/modules/, and
6621 extract their modalias information. Another would be to look at
6622 packages with udev rules, ie packages with files in
6623 /lib/udev/rules.d/, and extract their vendor/model information to
6624 generate a modalias matching rule. I have not tested any of these to
6625 see if it work.&lt;/p&gt;
6626
6627 &lt;p&gt;If you want to help implementing a system to let us propose what
6628 packages to install when new hardware is plugged into a Debian
6629 machine, please send me an email or talk to me on
6630 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
6631 </description>
6632 </item>
6633
6634 <item>
6635 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
6636 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
6637 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
6638 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
6639 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
6640 information, to find the packages that support a given piece of
6641 hardware, I refreshed my memory regarding modalias values, and decided
6642 to document the details. Here are my findings so far, also available
6643 in
6644 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
6645 Debian Edu subversion repository&lt;/a&gt;:
6646
6647 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
6648
6649 &lt;p&gt;This document try to explain what the different types of modalias
6650 values stands for. It is in part based on information from
6651 &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;,
6652 &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;,
6653 &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
6654 &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;.
6655
6656 &lt;p&gt;The modalias entries for a given Linux machine can be found using
6657 this shell script:&lt;/p&gt;
6658
6659 &lt;pre&gt;
6660 find /sys -name modalias -print0 | xargs -0 cat | sort -u
6661 &lt;/pre&gt;
6662
6663 &lt;p&gt;The supported modalias globs for a given kernel module can be found
6664 using modinfo:&lt;/p&gt;
6665
6666 &lt;pre&gt;
6667 % /sbin/modinfo psmouse | grep alias:
6668 alias: serio:ty05pr*id*ex*
6669 alias: serio:ty01pr*id*ex*
6670 %
6671 &lt;/pre&gt;
6672
6673 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
6674
6675 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
6676 Bridge memory controller:&lt;/p&gt;
6677
6678 &lt;p&gt;&lt;blockquote&gt;
6679 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6680 &lt;/blockquote&gt;&lt;/p&gt;
6681
6682 &lt;p&gt;This represent these values:&lt;/p&gt;
6683
6684 &lt;pre&gt;
6685 v 00008086 (vendor)
6686 d 00002770 (device)
6687 sv 00001028 (subvendor)
6688 sd 000001AD (subdevice)
6689 bc 06 (bus class)
6690 sc 00 (bus subclass)
6691 i 00 (interface)
6692 &lt;/pre&gt;
6693
6694 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
6695 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
6696 0600. The 0600 class is a host bridge. Other useful bus values are
6697 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
6698
6699 &lt;p&gt;Not sure how to figure out the interface value, nor what it
6700 means.&lt;/p&gt;
6701
6702 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
6703
6704 &lt;p&gt;Some typical USB entries can look like this. This is an internal
6705 USB hub in a laptop:&lt;/p&gt;
6706
6707 &lt;p&gt;&lt;blockquote&gt;
6708 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6709 &lt;/blockquote&gt;&lt;/p&gt;
6710
6711 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
6712
6713 &lt;pre&gt;
6714 v 1D6B (device vendor)
6715 p 0001 (device product)
6716 d 0206 (bcddevice)
6717 dc 09 (device class)
6718 dsc 00 (device subclass)
6719 dp 00 (device protocol)
6720 ic 09 (interface class)
6721 isc 00 (interface subclass)
6722 ip 00 (interface protocol)
6723 &lt;/pre&gt;
6724
6725 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
6726 class is in the interface class section. For a simple USB web camera,
6727 these alias entries show up:&lt;/p&gt;
6728
6729 &lt;p&gt;&lt;blockquote&gt;
6730 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6731 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6732 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6733 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6734 &lt;/blockquote&gt;&lt;/p&gt;
6735
6736 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
6737 camera), 0101 is audio control device and 0102 is audio streaming (aka
6738 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
6739
6740 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
6741
6742 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
6743 receiver in a Thinkpad X40:&lt;/p&gt;
6744
6745 &lt;p&gt;&lt;blockquote&gt;
6746 acpi:IBM0071:PNP0511:
6747 &lt;/blockquote&gt;&lt;/p&gt;
6748
6749 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
6750
6751 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
6752
6753 &lt;p&gt;The DMI table contain lots of information about the computer case
6754 and model. This is an entry for a IBM Thinkpad X40, fetched from
6755 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
6756
6757 &lt;p&gt;&lt;blockquote&gt;
6758 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6759 &lt;/blockquote&gt;&lt;/p&gt;
6760
6761 &lt;p&gt;The values present are&lt;/p&gt;
6762
6763 &lt;pre&gt;
6764 bvn IBM (BIOS vendor)
6765 bvr 1UETB6WW(1.66) (BIOS version)
6766 bd 06/15/2005 (BIOS date)
6767 svn IBM (system vendor)
6768 pn 2371H4G (product name)
6769 pvr ThinkPadX40 (product version)
6770 rvn IBM (board vendor)
6771 rn 2371H4G (board name)
6772 rvr NotAvailable (board version)
6773 cvn IBM (chassis vendor)
6774 ct 10 (chassis type)
6775 cvr NotAvailable (chassis version)
6776 &lt;/pre&gt;
6777
6778 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
6779 found in the dmidecode source:&lt;/p&gt;
6780
6781 &lt;pre&gt;
6782 3 Desktop
6783 4 Low Profile Desktop
6784 5 Pizza Box
6785 6 Mini Tower
6786 7 Tower
6787 8 Portable
6788 9 Laptop
6789 10 Notebook
6790 11 Hand Held
6791 12 Docking Station
6792 13 All In One
6793 14 Sub Notebook
6794 15 Space-saving
6795 16 Lunch Box
6796 17 Main Server Chassis
6797 18 Expansion Chassis
6798 19 Sub Chassis
6799 20 Bus Expansion Chassis
6800 21 Peripheral Chassis
6801 22 RAID Chassis
6802 23 Rack Mount Chassis
6803 24 Sealed-case PC
6804 25 Multi-system
6805 26 CompactPCI
6806 27 AdvancedTCA
6807 28 Blade
6808 29 Blade Enclosing
6809 &lt;/pre&gt;
6810
6811 &lt;p&gt;The chassis type values are not always accurately set in the DMI
6812 table. For example my home server is a tower, but the DMI modalias
6813 claim it is a desktop.&lt;/p&gt;
6814
6815 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
6816
6817 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
6818 test machine:&lt;/p&gt;
6819
6820 &lt;p&gt;&lt;blockquote&gt;
6821 serio:ty01pr00id00ex00
6822 &lt;/blockquote&gt;&lt;/p&gt;
6823
6824 &lt;p&gt;The values present are&lt;/p&gt;
6825
6826 &lt;pre&gt;
6827 ty 01 (type)
6828 pr 00 (prototype)
6829 id 00 (id)
6830 ex 00 (extra)
6831 &lt;/pre&gt;
6832
6833 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
6834 the valid values are.&lt;/p&gt;
6835
6836 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
6837
6838 &lt;p&gt;There are heaps of other modalias subtypes according to
6839 file2alias.c. There is the rest of the list from that source: amba,
6840 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6841 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6842 vmbus, x86cpu and zorro. I did not spend time documenting all of
6843 these, as they do not seem relevant for my intended use with mapping
6844 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
6845
6846 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
6847
6848 &lt;p&gt;To check which kernel modules provide support for a given modalias,
6849 one can use the following shell script:&lt;/p&gt;
6850
6851 &lt;pre&gt;
6852 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
6853 echo &quot;$id&quot; ; \
6854 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
6855 done
6856 &lt;/pre&gt;
6857
6858 &lt;p&gt;The output can look like this (only the first few entries as the
6859 list is very long on my test machine):&lt;/p&gt;
6860
6861 &lt;pre&gt;
6862 acpi:ACPI0003:
6863 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
6864 acpi:device:
6865 FATAL: Module acpi:device: not found.
6866 acpi:IBM0068:
6867 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
6868 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
6869 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
6870 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6871 acpi:IBM0071:PNP0511:
6872 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
6873 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
6874 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
6875 [...]
6876 &lt;/pre&gt;
6877
6878 &lt;p&gt;If you want to help implementing a system to let us propose what
6879 packages to install when new hardware is plugged into a Debian
6880 machine, please send me an email or talk to me on
6881 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
6882
6883 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
6884 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
6885 in /sys/ with space in them.&lt;/p&gt;
6886 </description>
6887 </item>
6888
6889 <item>
6890 <title>Moved the pymissile Debian packaging to collab-maint</title>
6891 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
6892 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
6893 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
6894 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
6895 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6896 Launcher and updated the Debian package
6897 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
6898 sure udev will fix the device permissions when it is plugged in. I
6899 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
6900 hopefully make the package be proposed by jockey in Ubuntu when a user
6901 plug in his rocket launcher. In the process I moved the source to a
6902 git repository under collab-maint, to make it easier for any DD to
6903 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
6904 is not very active, but the software still work for me even after five
6905 years of relative silence. The new git repository is not listed in
6906 the uploaded package yet, because I want to test the other changes a
6907 bit more before I upload the new version. If you want to check out
6908 the new version with a .desktop file included, visit the
6909 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
6910 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
6911 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
6912 </description>
6913 </item>
6914
6915 <item>
6916 <title>Lets make hardware dongles easier to use in Debian</title>
6917 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
6918 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
6919 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
6920 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
6921 general, is that there is a great package management system with the
6922 ability to automatically install software packages by downloading them
6923 from the distribution mirrors, but no way to get it to automatically
6924 install the packages I need to use the hardware I plug into my
6925 machine. Even if the package to use it is easily available from the
6926 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6927 suggest to automatically install the python-nxt, nbc and t2n packages
6928 I need to talk to it. When I plug in a Yubikey, it could propose the
6929 yubikey-personalization package. The information required to do this
6930 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
6931
6932 &lt;p&gt;Some years ago, I proposed to
6933 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
6934 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
6935 simple:
6936
6937 &lt;ul&gt;
6938
6939 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
6940 starting when a user log in.&lt;/li&gt;
6941
6942 &lt;li&gt;Set this program up to listen for kernel events emitted when new
6943 hardware is inserted into the computer.&lt;/li&gt;
6944
6945 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
6946 database mapping to packages, and take note of any non-installed
6947 packages.&lt;/li&gt;
6948
6949 &lt;li&gt;Show a message to the user proposing to install the discovered
6950 package, and make it easy to install it.&lt;/li&gt;
6951
6952 &lt;/ul&gt;
6953
6954 &lt;p&gt;I am not sure what the best way to implement this is, but my
6955 initial idea was to use dbus events to discover new hardware, the
6956 discover database to find packages and
6957 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
6958 packages.&lt;/p&gt;
6959
6960 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
6961 draft package is now checked into
6962 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
6963 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
6964 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
6965 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6966 the relevant packages in Debian, and uploaded a new version
6967 2.2013.01.09 to unstable. I also discovered that the current
6968 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
6969 package in Debian no longer discovered any USB devices, because
6970 /proc/bus/usb/devices is no longer present. I ported it to use
6971 libusb as a fall back option to get it working. The fixed package
6972 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
6973 because of the freeze).&lt;/p&gt;
6974
6975 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
6976 desktop notification to show up (only once, the first time it is
6977 inserted):&lt;/p&gt;
6978
6979 &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;
6980
6981 &lt;p&gt;For this prototype to be really useful, some way to automatically
6982 install the proposed packages by pressing the &quot;Please install
6983 program(s)&quot; button should to be implemented.&lt;/p&gt;
6984
6985 &lt;p&gt;If this idea seem useful to you, and you want to help make it
6986 happen, please help me update the discover-data database with mappings
6987 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
6988 list the package you would like to have installed when a given
6989 hardware device is inserted into your computer, and report bugs using
6990 reportbug if it isn&#39;t. Or, if you know of a better way to provide
6991 such mapping, please let me know.&lt;/p&gt;
6992
6993 &lt;p&gt;This prototype need more work, and there are several questions that
6994 should be considered before it is ready for production use. Is dbus
6995 the correct way to detect new hardware? At the moment I look for HAL
6996 dbus events on the system bus, because that is the events I could see
6997 on my Debian Squeeze KDE desktop. Are there better events to use?
6998 How should the user be notified? Is the desktop notification
6999 mechanism the best option, or should the background daemon raise a
7000 popup instead? How should packages be installed? When should they
7001 not be installed?&lt;/p&gt;
7002
7003 &lt;p&gt;If you want to help getting such feature implemented in Debian,
7004 please send me an email. :)&lt;/p&gt;
7005 </description>
7006 </item>
7007
7008 <item>
7009 <title>New IRC channel for LEGO designers using Debian</title>
7010 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
7011 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
7012 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
7013 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
7014 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
7015 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
7016 discovered I had to build all the tools myself because none were
7017 already in Debian Squeeze. If Debian support for LEGO is something
7018 you care about, please join me on the IRC channel
7019 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
7020 irc.debian.org). There is a lot that could be done to improve the
7021 Debian support for LEGO designers. For example both CAD software
7022 and Mindstorm compilers are missing. :)&lt;/p&gt;
7023
7024 &lt;p&gt;Update 2012-01-03: A
7025 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
7026 including links to Lego related packages is now available.&lt;/p&gt;
7027 </description>
7028 </item>
7029
7030 <item>
7031 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
7032 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
7033 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
7034 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
7035 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
7036 year! I hope next year will prove to be a good year.&lt;/p&gt;
7037
7038 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
7039 decentralised &quot;currency&quot; that allow people to transfer bitcoins
7040 between each other with minimal overhead, is a very interesting
7041 experiment. And as I wrote a few days ago, the bitcoin situation in
7042 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
7043 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
7044 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
7045 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
7046 for one of the ftpmasters to approve the new bitcoin-qt package
7047 name.&lt;/p&gt;
7048
7049 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
7050 team in Debian, you can easily test the package in Debian Squeeze
7051 using the following steps to get a set of working packages:&lt;/p&gt;
7052
7053 &lt;blockquote&gt;&lt;pre&gt;
7054 git clone git://git.debian.org/git/collab-maint/bitcoin
7055 cd bitcoin
7056 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7057 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7058 &lt;/pre&gt;&lt;/blockquote&gt;
7059
7060 &lt;p&gt;You might have to install some build dependencies as well. The
7061 list of commands should give you two packages, bitcoind and
7062 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7063 client will download the complete set of bitcoin &quot;blocks&quot;, which need
7064 around 5.6 GiB of data on my machine at the moment. Make sure your
7065 ~/.bitcoin/ directory have lots of spare room if you want to download
7066 all the blocks. The client will warn if the disk is getting full, so
7067 there is not really a problem if you got too little room, but you will
7068 not be able to get all the features out of the client.&lt;/p&gt;
7069
7070 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
7071 activities, please send Bitcoin donations to my address
7072 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7073 </description>
7074 </item>
7075
7076 <item>
7077 <title>A word on bitcoin support in Debian</title>
7078 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
7079 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
7080 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
7081 <description>&lt;p&gt;It has been a while since I wrote about
7082 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
7083 peer-to-peer based crypto-currency, and the reason is simply that I
7084 have been busy elsewhere. But two days ago, I started looking at the
7085 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
7086 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
7087 is now maintained by a
7088 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
7089 people&lt;/a&gt;, and the grunt work had already been done by this team. We
7090 owe a huge thank you to all these team members. :)
7091 But I was sad to discover that the bitcoin client is missing in
7092 Wheezy. It is only available in Sid (and an outdated client from
7093 backports). The client had several RC bugs registered in BTS blocking
7094 it from entering testing. To try to help the team and improve the
7095 situation, I spent some time providing patches and triaging the bug
7096 reports. I also had a look at the bitcoin package available from Matt
7097 Corallo in a
7098 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
7099 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
7100 Debian package.&lt;/p&gt;
7101
7102 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
7103 IRC, I pushed several patches into the collab-maint git repository to
7104 improve the package. It now contains fixes for the RC issues (not from
7105 me, but fixed by Scott Howard), build rules for a Qt GUI client
7106 package, konqueror support for the bitcoin: URI and bash completion
7107 setup. As I work on Debian Squeeze, I also created
7108 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
7109 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
7110 it and try to integrate it into the git repository before uploading a
7111 new version to unstable.
7112
7113 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
7114 centralized control currently exercised in the monetary system. I
7115 find it completely unacceptable that the USA government is collecting
7116 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7117 that the major credit card companies can block legal money
7118 transactions to Wikileaks. But for bitcoin to succeed, more people
7119 need to use bitcoins, and more people need to accept bitcoins when
7120 they sell products and services. Improving the bitcoin support in
7121 Debian is a small step in the right direction, but not enough.
7122 Unfortunately the user experience when browsing the web and wanting to
7123 pay with bitcoin is still not very good. The bitcoin: URI is a step
7124 in the right direction, but need to work in most or every browser in
7125 use. Also the bitcoin-qt client is too heavy to fire up to do a
7126 quick transaction. I believe there are other clients available, but
7127 have not tested them.&lt;/p&gt;
7128
7129 &lt;p&gt;My
7130 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
7131 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
7132 I received 20.15 BTC so far on the address I provided in my blog two
7133 years ago, as can be
7134 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
7135 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
7136 donation. The blockexplorer service demonstrates quite well that
7137 bitcoin is not quite anonymous and untracked. :) I wonder if the
7138 number of users have gone up since then. If you use bitcoin and want
7139 to show your support of my activity, please send Bitcoin donations to
7140 the same address as last time,
7141 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7142 </description>
7143 </item>
7144
7145 <item>
7146 <title>Git repository for song book for Computer Scientists</title>
7147 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
7148 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
7149 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
7150 <description>&lt;p&gt;As I
7151 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
7152 this summer&lt;/a&gt;, I have created a Computer Science song book a few
7153 years ago, and today I finally found time to create a public
7154 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
7155 repository for the project&lt;/a&gt;.&lt;/p&gt;
7156
7157 &lt;p&gt;If you want to help out, please clone the source and submit patches
7158 to the HTML version. To generate the PDF and PostScript version,
7159 please use prince XML, or let me know about a useful free software
7160 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
7161
7162 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
7163 PostScript formats at
7164 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
7165 Science Songbook&lt;/a&gt;.&lt;/p&gt;
7166 </description>
7167 </item>
7168
7169 <item>
7170 <title>Gratulerer med 19-årsdagen, Debian!</title>
7171 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
7172 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
7173 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
7174 <description>&lt;p&gt;I dag fyller
7175 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
7176 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
7177 si gratulerer med dagen, Debian!&lt;/p&gt;
7178 </description>
7179 </item>
7180
7181 <item>
7182 <title>Song book for Computer Scientists</title>
7183 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
7184 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
7185 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
7186 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
7187 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
7188 collecting computer related songs for use at parties. The original
7189 version was written in LaTeX, but a few years ago I got help from
7190 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7191 while keeping the ability to create a nice book in PDF format. I have
7192 not had time to maintain the book for a while now, and guess I should
7193 put it up on some public version control repository where others can
7194 help me extend and update the book. If anyone is volunteering to help
7195 me with this, send me an email. Also let me know if there are songs
7196 missing in my book.&lt;/p&gt;
7197
7198 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
7199 me today that I really should let all my readers share the joys of
7200 singing out load about programming, computers and computer networks.
7201 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
7202 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
7203 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
7204 Computer Science Songbook&lt;/a&gt;.
7205 </description>
7206 </item>
7207
7208 <item>
7209 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
7210 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
7211 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
7212 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
7213 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
7214 around 1000 at the moment. To be able to get help from the vendors
7215 when something go wrong, we want to keep the firmware on the servers
7216 up to date. If the firmware isn&#39;t the latest and greatest, the
7217 vendors typically refuse to start debugging any problems until the
7218 firmware is upgraded. So before every reboot, we want to upgrade the
7219 firmware, and we would really like everyone handling servers at the
7220 university to do this themselves when they plan to reboot a machine.
7221 For that to happen we at the unix server admin group need to provide
7222 the tools to do so.&lt;/p&gt;
7223
7224 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
7225 fetch and install the latest firmware for the servers we got. Most of
7226 our hardware are from Dell and HP, so I have focused on these servers
7227 so far. This blog post is about the Dell part.&lt;/P&gt;
7228
7229 &lt;p&gt;On the Dell FTP site I was lucky enough to find
7230 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
7231 with firmware information for all 11th generation servers, listing
7232 which firmware should be used on a given model and where on the FTP
7233 site I can find it. Using a simple perl XML parser I can then
7234 download the shell scripts Dell provides to do firmware upgrades from
7235 within Linux and reboot when all the firmware is primed and ready to
7236 be activated on the first reboot.&lt;/p&gt;
7237
7238 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
7239 Are there anyone working on similar tools for firmware upgrading all
7240 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
7241
7242 &lt;p&gt;&lt;pre&gt;
7243 #!/usr/bin/perl
7244 use strict;
7245 use warnings;
7246 use File::Temp qw(tempdir);
7247 BEGIN {
7248 # Install needed RHEL packages if missing
7249 my %rhelmodules = (
7250 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
7251 );
7252 for my $module (keys %rhelmodules) {
7253 eval &quot;use $module;&quot;;
7254 if ($@) {
7255 my $pkg = $rhelmodules{$module};
7256 system(&quot;yum install -y $pkg&quot;);
7257 eval &quot;use $module;&quot;;
7258 }
7259 }
7260 }
7261 my $errorsto = &#39;pere@hungry.com&#39;;
7262
7263 upgrade_dell();
7264
7265 exit 0;
7266
7267 sub run_firmware_script {
7268 my ($opts, $script) = @_;
7269 unless ($script) {
7270 print STDERR &quot;fail: missing script name\n&quot;;
7271 exit 1
7272 }
7273 print STDERR &quot;Running $script\n\n&quot;;
7274
7275 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
7276 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
7277 } else {
7278 print STDERR &quot;fail: firmware script returned error\n&quot;;
7279 }
7280 }
7281
7282 sub run_firmware_scripts {
7283 my ($opts, @dirs) = @_;
7284 # Run firmware packages
7285 for my $dir (@dirs) {
7286 print STDERR &quot;info: Running scripts in $dir\n&quot;;
7287 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
7288 while (my $s = readdir $dh) {
7289 next if $s =~ m/^\.\.?/;
7290 run_firmware_script($opts, &quot;$dir/$s&quot;);
7291 }
7292 closedir $dh;
7293 }
7294 }
7295
7296 sub download {
7297 my $url = shift;
7298 print STDERR &quot;info: Downloading $url\n&quot;;
7299 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
7300 }
7301
7302 sub upgrade_dell {
7303 my @dirs;
7304 my $product = `dmidecode -s system-product-name`;
7305 chomp $product;
7306
7307 if ($product =~ m/PowerEdge/) {
7308
7309 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7310 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
7311
7312 my $tmpdir = tempdir(
7313 CLEANUP =&gt; 1
7314 );
7315 chdir($tmpdir);
7316 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
7317 system(&#39;gunzip Catalog.xml.gz&#39;);
7318 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
7319 # -q is quiet, disabling interactivity and reducing console output
7320 my $fwopts = &quot;-q&quot;;
7321 if (@paths) {
7322 for my $url (@paths) {
7323 fetch_dell_fw($url);
7324 }
7325 run_firmware_scripts($fwopts, $tmpdir);
7326 } else {
7327 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
7328 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
7329 }
7330 chdir(&#39;/&#39;);
7331 } else {
7332 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
7333 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
7334 }
7335 }
7336
7337 sub fetch_dell_fw {
7338 my $path = shift;
7339 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
7340 download($url);
7341 }
7342
7343 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7344 # firmware packages to download from Dell. Only work for Linux
7345 # machines and 11th generation Dell servers.
7346 sub fetch_dell_fw_list {
7347 my $filename = shift;
7348
7349 my $product = `dmidecode -s system-product-name`;
7350 chomp $product;
7351 my ($mybrand, $mymodel) = split(/\s+/, $product);
7352
7353 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
7354
7355 my $xml = XMLin($filename);
7356 my @paths;
7357 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
7358 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
7359 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
7360 my $oscode;
7361 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
7362 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
7363 } else {
7364 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
7365 }
7366 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
7367 {
7368 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
7369 }
7370 }
7371 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
7372 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
7373
7374 # Drop application packages, only firmware and BIOS
7375 next if &#39;APAC&#39; eq $componenttype;
7376
7377 my $cpath = $component-&gt;{path};
7378 for my $path (@paths) {
7379 if ($cpath =~ m%/$path$%) {
7380 push(@paths, $cpath);
7381 }
7382 }
7383 }
7384 return @paths;
7385 }
7386 &lt;/pre&gt;
7387
7388 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
7389 it could work on other platforms with some tweaking. Anyone know a
7390 index like Catalog.xml is available from HP for HP servers? At the
7391 moment I maintain a similar list manually and it is quickly getting
7392 outdated.&lt;/p&gt;
7393 </description>
7394 </item>
7395
7396 <item>
7397 <title>How is booting into runlevel 1 different from single user boots?</title>
7398 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
7399 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
7400 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
7401 <description>&lt;p&gt;Wouter Verhelst have some
7402 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
7403 comments and opinions&lt;/a&gt; on my blog post on
7404 &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
7405 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
7406 &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
7407 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
7408 small piece of his comment now, and though it best to address the
7409 misunderstanding he bring forward:&lt;/p&gt;
7410
7411 &lt;p&gt;&lt;blockquote&gt;
7412 Currently, a system admin has four options: [...] boot to a
7413 single-user system (by adding &#39;single&#39; to the kernel command line;
7414 this runs rcS and rc1 scripts)
7415 &lt;/blockquote&gt;&lt;/p&gt;
7416
7417 &lt;p&gt;This make me believe Wouter believe booting into single user mode
7418 and booting into runlevel 1 is the same. I am not surprised he
7419 believe this, because it would make sense and is a quite sensible
7420 thing to believe. But because the boot in Debian is slightly broken,
7421 runlevel 1 do not work properly and it isn&#39;t the same as single user
7422 mode. I&#39;ll try to explain what is actually happing, but it is a bit
7423 hard to explain.&lt;/p&gt;
7424
7425 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
7426 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
7427 executed in single user mode is sulogin. Single user mode is a boot
7428 state &quot;between&quot; the runlevels, and when booting into single user mode,
7429 only the scripts in /etc/rcS.d/ are executed before the init process
7430 enters the single user state. When switching to runlevel 1, the state
7431 is in fact not ending in runlevel 1, but it passes through runlevel 1
7432 and end up in the single user mode (see /etc/rc1.d/S03single, which
7433 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
7434 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
7435 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7436 mode).&lt;/p&gt;
7437
7438 &lt;p&gt;This summary might make it clearer. When booting for the first
7439 time into single user mode, the following commands are executed:
7440 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
7441 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
7442 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
7443 trying to continue after visiting single user mode. Not all services
7444 are started again as they should, causing the machine to end up in an
7445 unpredicatble state. This is why Debian admins recommend rebooting
7446 after visiting single user mode.&lt;/p&gt;
7447
7448 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
7449 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
7450 to runlevel 1, the services started from /etc/rcS.d/ are not properly
7451 stopped when passing through the scripts in /etc/rc1.d/, and not
7452 started again when switching away from runlevel 1 to the runlevels
7453 2-5. I believe the problem is best fixed by moving all the scripts
7454 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
7455 functioning single user mode during boot.&lt;/p&gt;
7456
7457 &lt;p&gt;I have spent several years investigating the Debian boot system,
7458 and discovered this problem a few years ago. I suspect it originates
7459 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
7460 </description>
7461 </item>
7462
7463 <item>
7464 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
7465 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
7466 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
7467 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
7468 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
7469 are started from /etc/rcS.d/. In fact, there is a bite more of them
7470 than make sense, and this causes a few problems. What kind of
7471 problems, you might ask. There are at least two problems. The first
7472 is that it is not possible to recover a machine after switching to
7473 runlevel 1. One need to actually reboot to get the machine back to
7474 the expected state. The other is that single user boot will sometimes
7475 run into problems because some of the subsystems are activated before
7476 the root login is presented, causing problems when trying to recover a
7477 machine from a problem in that subsystem. A minor additional point is
7478 that moving more scripts out of rcS.d/ and into the other rc#.d/
7479 directories will increase the amount of scripts that can run in
7480 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
7481
7482 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
7483 scripts that _have_ to execute before the root login prompt is
7484 presented during a single user boot should go there. Everything else
7485 should go into the numeric runlevels. This means things like
7486 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7487 the numeric runlevels. Today in Debian, there are around 115 init.d
7488 scripts that are started from rcS.d/, and most of them should be moved
7489 out. Do your package have one of them? Please help us make single
7490 user and runlevel 1 better by moving it.&lt;/p&gt;
7491
7492 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
7493 etc. should still be started from rcS.d/, but there is for example no
7494 need to have the network enabled before the single user login prompt
7495 is presented.&lt;/p&gt;
7496
7497 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
7498 Debian systems working while scripts migrate and during upgrades, the
7499 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7500 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7501 and the next ones can only be moved when their dependencies have been
7502 moved first. This migration must be done sequentially while we ensure
7503 that the package system upgrade packages in the right order to keep
7504 the system state correct. This will require some coordination when it
7505 comes to network related packages, but most of the packages with
7506 scripts that should migrate do not have anything in rcS.d/ depending
7507 on them. Some packages have already been updated, like the sudo
7508 package, while others are still left to do. I wish I had time to work
7509 on this myself, but real live constrains make it unlikely that I will
7510 find time to push this forward.&lt;/p&gt;
7511 </description>
7512 </item>
7513
7514 <item>
7515 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
7516 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
7517 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
7518 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
7519 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
7520 mentioned the issues I believe should be improved in Debian for its
7521 desktop to be useful for more people. The use case for this is my
7522 parents, which are currently running Kubuntu which solve the
7523 issues.&lt;/p&gt;
7524
7525 &lt;p&gt;I suspect these four missing features are not very hard to
7526 implement. After all, they are present in Ubuntu, so if we wanted to
7527 do this in Debian we would have a source.&lt;/p&gt;
7528
7529 &lt;ol&gt;
7530
7531 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
7532 are new packages available for upgrades, a icon in the KDE status bar
7533 indicate this, and clicking on it will activate the simple upgrade
7534 tool to handle it. I have no problem guiding both of my parents
7535 through the process over the phone. If a kernel reboot is required,
7536 this too is indicated by the status bars and the upgrade tool. Last
7537 time I checked, nothing with the same features was working in KDE in
7538 Debian.&lt;/li&gt;
7539
7540 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
7541 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
7542 currently have a handler for, it will ask the user if the system
7543 should search for a package that would add support for this MIME type,
7544 and if the user say yes, the APT sources will be searched for packages
7545 advertising the MIME type in their control file (visible in the
7546 Packages file in the APT archive). If one or more packages are found,
7547 it is a simple click of the mouse to add support for the missing mime
7548 type. If the package require the user to accept some non-free
7549 license, this is explained to the user. The entire process make it
7550 more clear to the user why something do not work in the browser, and
7551 make the chances higher for the user to blame the web page authors and
7552 not the browser for any missing features.&lt;/li&gt;
7553
7554 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
7555 handlers.&lt;/strong&gt; When the media players encounter a format or codec
7556 it is not supporting, a dialog pop up asking the user if the system
7557 should search for a package that would add support for it. This
7558 happen with things like MP3, Windows Media or H.264. The selection
7559 and installation procedure is very similar to the Firefox browser
7560 plugin handling. This is as far as I know implemented using a
7561 gstreamer hook. The end result is that the user easily get access to
7562 the codecs that are present from the APT archives available, while
7563 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
7564
7565 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
7566 displaying a text/plain file in my Debian browser, it will propose to
7567 start emacs to show it. If I remember correctly, when doing the same
7568 in Kunbutu it show the file as a text file in the browser. At least I
7569 know Opera will show text files within the browser. I much prefer the
7570 latter behaviour.&lt;/li&gt;
7571
7572 &lt;/ol&gt;
7573
7574 &lt;p&gt;There are other nice features as well, like the simplified suite
7575 upgrader, but given that I am the one mostly doing the dist-upgrade,
7576 it do not matter much.&lt;/p&gt;
7577
7578 &lt;p&gt;I really hope we could get these features in place for the next
7579 Debian release. It would require the coordinated effort of several
7580 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
7581 </description>
7582 </item>
7583
7584 <item>
7585 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
7586 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
7587 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
7588 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
7589 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
7590 site is build on Debian/Squeeze, and this platform was chosen because
7591 I am most familiar with Debian (being a Debian Developer for around 10
7592 years) because it is the latest stable Debian release which should get
7593 security support for a few years.&lt;/p&gt;
7594
7595 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
7596 that are missing in Debian at the moment. It would be great if these
7597 modules were added to the Debian archive, allowing anyone to set up
7598 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
7599 in their own country using only Debian packages. The list of modules
7600 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
7601 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
7602 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7603 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7604 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7605 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7606 easier in the future.&lt;/p&gt;
7607
7608 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
7609 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
7610 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
7611 with the responsibility of tracking security problems, which I really
7612 do not have time for.&lt;/p&gt;
7613 </description>
7614 </item>
7615
7616 <item>
7617 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
7618 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
7619 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
7620 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
7621 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
7622 posts have been in Norwegian the last few weeks, so here is a short
7623 update in English.&lt;/p&gt;
7624
7625 &lt;p&gt;The kids still keep me too busy to get much free software work
7626 done, but I did manage to organise a project to get a Norwegian port
7627 of the British service
7628 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
7629 and it has been running for a month now. The entire project has been
7630 organised by me and two others. Around Christmas we gathered sponsors
7631 to fund the development work. In January I drafted a contract with
7632 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
7633 and in February the development took place. Most of it involved
7634 converting the source to use GPS coordinates instead of British
7635 easting/northing, and the resulting code should be a lot easier to get
7636 running in any country by now. The Norwegian
7637 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
7638 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
7639 source and the source for administrative borders in Norway, and
7640 support for this had to be added/fixed.&lt;/p&gt;
7641
7642 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
7643 polishing the system before we announced it March 7th. The system is
7644 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
7645 problem reports in a few weeks. Soon we hope to announce the Android
7646 and iPhone versions making it even easier to report problems with the
7647 public infrastructure.&lt;/p&gt;
7648
7649 &lt;p&gt;Perhaps something to consider for those of you in countries without
7650 such service?&lt;/p&gt;
7651 </description>
7652 </item>
7653
7654 <item>
7655 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
7656 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
7657 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
7658 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
7659 <description>&lt;p&gt;The last few days I have looked at ways to track open security
7660 issues here at my work with the University of Oslo. My idea is that
7661 it should be possible to use the information about security issues
7662 available on the Internet, and check our locally
7663 maintained/distributed software against this information. It should
7664 allow us to verify that no known security issues are forgotten. The
7665 CVE database listing vulnerabilities seem like a great central point,
7666 and by using the package lists from Debian mapped to CVEs provided by
7667 the testing security team, I believed it should be possible to figure
7668 out which security holes were present in our free software
7669 collection.&lt;/p&gt;
7670
7671 &lt;p&gt;After reading up on the topic, it became obvious that the first
7672 building block is to be able to name software packages in a unique and
7673 consistent way across data sources. I considered several ways to do
7674 this, for example coming up with my own naming scheme like using URLs
7675 to project home pages or URLs to the Freshmeat entries, or using some
7676 existing naming scheme. And it seem like I am not the first one to
7677 come across this problem, as MITRE already proposed and implemented a
7678 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
7679 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
7680 software, hardware and other platform components. The CPE ids are
7681 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
7682 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
7683 issues for any CPE name. With this in place, all I need to do is to
7684 locate the CPE id for the software packages we use at the university.
7685 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
7686 NVD entry if a CVE for the package exist).&lt;/p&gt;
7687
7688 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
7689 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
7690 check out, one could look up
7691 &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
7692 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
7693 The most recent one is
7694 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
7695 and at the bottom of the NVD page for this vulnerability the complete
7696 list of affected versions is provided.&lt;/p&gt;
7697
7698 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
7699 for offline processing of issues. Using this dump, I&#39;ve written a
7700 small script taking a list of CPEs as input and list all CVEs
7701 affecting the packages represented by these CPEs. One give it CPEs
7702 with version numbers as specified above and get a list of open
7703 security issues out.&lt;/p&gt;
7704
7705 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
7706 information need to be high. For that to happen, I believe as many as
7707 possible need to use and contribute to the NVD database. I notice
7708 RHEL is providing
7709 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
7710 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
7711 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
7712
7713 &lt;p&gt;To get an idea about the quality for free software, I spent some
7714 time making it possible to compare the CVE database from Debian with
7715 the CVE database in NVD. The result look fairly good, but there are
7716 some inconsistencies in NVD (same software package having several
7717 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7718 Debian believe are affected by a CVE). Hope to find time to improve
7719 the quality of NVD, but that require being able to get in touch with
7720 someone maintaining it. So far my three emails with questions and
7721 corrections have not seen any reply, but I hope contact can be
7722 established soon.&lt;/p&gt;
7723
7724 &lt;p&gt;An interesting application for CPEs is cross platform package
7725 mapping. It would be useful to know which packages in for example
7726 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7727 this would be trivial if all linux distributions provided CPE entries
7728 for their packages.&lt;/p&gt;
7729 </description>
7730 </item>
7731
7732 <item>
7733 <title>Which module is loaded for a given PCI and USB device?</title>
7734 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
7735 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
7736 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
7737 <description>&lt;p&gt;In the
7738 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
7739 package in Debian, there is a script to report useful information
7740 about the running hardware for use when people report missing
7741 information. One part of this script that I find very useful when
7742 debugging hardware problems, is the part mapping loaded kernel module
7743 to the PCI device it claims. It allow me to quickly see if the kernel
7744 module I expect is driving the hardware I am struggling with. To see
7745 the output, make sure discover-data is installed and run
7746 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
7747 one of my machines like this:&lt;/p&gt;
7748
7749 &lt;pre&gt;
7750 loaded modules:
7751 10de:03eb i2c_nforce2
7752 10de:03f1 ohci_hcd
7753 10de:03f2 ehci_hcd
7754 10de:03f0 snd_hda_intel
7755 10de:03ec pata_amd
7756 10de:03f6 sata_nv
7757 1022:1103 k8temp
7758 109e:036e bttv
7759 109e:0878 snd_bt87x
7760 11ab:4364 sky2
7761 &lt;/pre&gt;
7762
7763 &lt;p&gt;The code in question look like this, slightly modified for
7764 readability and to drop the output to file descriptor 3:&lt;/p&gt;
7765
7766 &lt;pre&gt;
7767 if [ -d /sys/bus/pci/devices/ ] ; then
7768 echo loaded pci modules:
7769 (
7770 cd /sys/bus/pci/devices/
7771 for address in * ; do
7772 if [ -d &quot;$address/driver/module&quot; ] ; then
7773 module=`cd $address/driver/module ; pwd -P | xargs basename`
7774 if grep -q &quot;^$module &quot; /proc/modules ; then
7775 address=$(echo $address |sed s/0000://)
7776 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
7777 echo &quot;$id $module&quot;
7778 fi
7779 fi
7780 done
7781 )
7782 echo
7783 fi
7784 &lt;/pre&gt;
7785
7786 &lt;p&gt;Similar code could be used to extract USB device module
7787 mappings:&lt;/p&gt;
7788
7789 &lt;pre&gt;
7790 if [ -d /sys/bus/usb/devices/ ] ; then
7791 echo loaded usb modules:
7792 (
7793 cd /sys/bus/usb/devices/
7794 for address in * ; do
7795 if [ -d &quot;$address/driver/module&quot; ] ; then
7796 module=`cd $address/driver/module ; pwd -P | xargs basename`
7797 if grep -q &quot;^$module &quot; /proc/modules ; then
7798 address=$(echo $address |sed s/0000://)
7799 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
7800 if [ &quot;$id&quot; ] ; then
7801 echo &quot;$id $module&quot;
7802 fi
7803 fi
7804 fi
7805 done
7806 )
7807 echo
7808 fi
7809 &lt;/pre&gt;
7810
7811 &lt;p&gt;This might perhaps be something to include in other tools as
7812 well.&lt;/p&gt;
7813 </description>
7814 </item>
7815
7816 <item>
7817 <title>How to test if a laptop is working with Linux</title>
7818 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
7819 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
7820 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
7821 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
7822 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
7823 batch of computers will work with Linux. Every year for the last few
7824 years the university have organised shared bid of a few thousand
7825 computers, and this year HP won the bid. Two different desktops and
7826 five different laptops are on the list this year. We in the UNIX
7827 group want to know which one of these computers work well with RHEL
7828 and Ubuntu, the two Linux distributions we currently handle at the
7829 university.&lt;/p&gt;
7830
7831 &lt;p&gt;My test method is simple, and I share it here to get feedback and
7832 perhaps inspire others to test hardware as well. To test, I PXE
7833 install the OS version of choice, and log in as my normal user and run
7834 a few applications and plug in selected pieces of hardware. When
7835 something fail, I make a note about this in the test matrix and move
7836 on. If I have some spare time I try to report the bug to the OS
7837 vendor, but as I only have the machines for a short time, I rarely
7838 have the time to do this for all the problems I find.&lt;/p&gt;
7839
7840 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
7841 I perform on a new model.&lt;/p&gt;
7842
7843 &lt;ul&gt;
7844
7845 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
7846 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7847 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
7848
7849 &lt;li&gt;Is X.org working? If the graphical login screen show up after
7850 installation, X.org is working.&lt;/li&gt;
7851
7852 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
7853 package mesa-utils on Ubuntu) and writing down the frames per second
7854 reported by the program.&lt;/li&gt;
7855
7856 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
7857 logging in, and if I can hear this the test is successful. If there
7858 are several audio exits on the machine, I try them all and check if
7859 the Gnome/KDE audio mixer can control where to send the sound. I
7860 normally test this by playing
7861 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
7862 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
7863
7864 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
7865 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
7866
7867 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
7868 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
7869
7870 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
7871 picture from the v4l device show up.&lt;/li&gt;
7872
7873 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7874 any bluetooth devices are discovered. In my office, I normally see a
7875 few.&lt;/li&gt;
7876
7877 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
7878 memory modules lying around, and stick them in and see if Gnome/KDE
7879 notice this.&lt;/li&gt;
7880
7881 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
7882 special button work, and if the laptop continue to work after
7883 resume.&lt;/li&gt;
7884
7885 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
7886 adjusting background light, switching on/off external video output,
7887 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7888 laptop to laptop, so I just write down which are working and which are
7889 not.&lt;/li&gt;
7890
7891 &lt;li&gt;Some laptops have smart card readers, finger print readers,
7892 acceleration sensors etc. I rarely test these, as I do not know how
7893 to quickly test if they are working or not, so I only document their
7894 existence.&lt;/li&gt;
7895
7896 &lt;/ul&gt;
7897
7898 &lt;p&gt;By now I suspect you are really curious what the test results are
7899 for the HP machines I am testing. I&#39;m not done yet, so I will report
7900 the test results later. For now I can report that HP 8100 Elite work
7901 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
7902 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
7903 can see, I have most machines left to test. One interesting
7904 observation is that Ubuntu Lucid has almost twice the frame rate than
7905 RHEL6 with glxgears. No idea why.&lt;/p&gt;
7906 </description>
7907 </item>
7908
7909 <item>
7910 <title>Some thoughts on BitCoins</title>
7911 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
7912 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
7913 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
7914 <description>&lt;p&gt;As I continue to explore
7915 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
7916 what properties the system have, and how it will be affected by laws
7917 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
7918
7919 &lt;p&gt;One interesting thing to note is that since the transactions are
7920 verified using a peer to peer network, all details about a transaction
7921 is known to everyone. This means that if a BitCoin address has been
7922 published like I did with mine in my initial post about BitCoin, it is
7923 possible for everyone to see how many BitCoins have been transfered to
7924 that address. There is even a web service to look at the details for
7925 all transactions. There I can see that my address
7926 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
7927 have received 16.06 Bitcoin, the
7928 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
7929 address of Simon Phipps have received 181.97 BitCoin and the address
7930 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
7931 of EFF have received 2447.38 BitCoins so far. Thank you to each and
7932 every one of you that donated bitcoins to support my activity. The
7933 fact that anyone can see how much money was transfered to a given
7934 address make it more obvious why the BitCoin community recommend to
7935 generate and hand out a new address for each transaction. I&#39;m told
7936 there is no way to track which addresses belong to a given person or
7937 organisation without the person or organisation revealing it
7938 themselves, as Simon, EFF and I have done.&lt;/p&gt;
7939
7940 &lt;p&gt;In Norway, and in most other countries, there are laws and
7941 regulations limiting how much money one can transfer across the border
7942 without declaring it. There are money laundering, tax and accounting
7943 laws and regulations I would expect to apply to the use of BitCoin.
7944 If the Skolelinux foundation
7945 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
7946 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
7947 normal bank transfers like EFF is doing, how should this be accounted?
7948 Given that it is impossible to know if money can cross the border or
7949 not, should everything or nothing be declared? What exchange rate
7950 should be used when calculating taxes? Would receivers have to pay
7951 income tax if the foundation were to pay Skolelinux contributors in
7952 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
7953
7954 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
7955 accepted by a lot of users. It must be possible to get easy access to
7956 the currency (as a wage or using currency exchanges), and it must be
7957 easy to spend it. At the moment BitCoin seem fairly easy to get
7958 access to, but there are very few places to spend it. I am not really
7959 a regular user of any of the vendor types currently accepting BitCoin,
7960 so I wonder when my kind of shop would start accepting BitCoins. I
7961 would like to buy electronics, travels and subway tickets, not herbs
7962 and books. :) The currency is young, and this will improve over time
7963 if it become popular, but I suspect regular banks will start to lobby
7964 to get BitCoin declared illegal if it become popular. I&#39;m sure they
7965 will claim it is helping fund terrorism and money laundering (which
7966 probably would be true, as is any currency in existence), but I
7967 believe the problems should be solved elsewhere and not by blaming
7968 currencies.&lt;/p&gt;
7969
7970 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
7971 CPU intensive process that depend on a bit of luck as well (as one is
7972 competing against all the other miners currently spending CPU cycles
7973 to see which one get the next lump of cash). The &quot;winner&quot; get 50
7974 BitCoin when this happen. Yesterday I came across the obvious way to
7975 join forces to increase ones changes of getting at least some coins,
7976 by coordinating the work on mining BitCoins across several machines
7977 and people, and sharing the result if one is lucky and get the 50
7978 BitCoins. Check out
7979 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
7980 if this sounds interesting. I have not had time to try to set up a
7981 machine to participate there yet, but have seen that running on ones
7982 own for a few days have not yield any BitCoins througth mining
7983 yet.&lt;/p&gt;
7984
7985 &lt;p&gt;Update 2010-12-15: Found an &lt;a
7986 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
7987 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
7988 it was interesting to read. The arguments presented seem to be
7989 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
7990 </description>
7991 </item>
7992
7993 <item>
7994 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
7995 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
7996 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
7997 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
7998 <description>&lt;p&gt;With this weeks lawless
7999 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
8000 attacks&lt;/a&gt; on Wikileak and
8001 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
8002 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
8003 not be trusted to handle money transactions.
8004 A blog post from
8005 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
8006 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
8007 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
8008 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
8009 some help from my friend to get it all running, and he even handed me
8010 some bitcoins to get started. I even donated a few bitcoins to Simon
8011 for helping me remember BitCoin.&lt;/p&gt;
8012
8013 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
8014 crypto-currency, decentralised and handled using peer-to-peer
8015 networks. It allows anonymous transactions and prohibits central
8016 control over the transactions, making it impossible for governments
8017 and companies alike to block donations and other transactions. The
8018 source is free software, and while the key dependency wxWidgets 2.9
8019 for the graphical user interface is missing in Debian, the command
8020 line client builds just fine. Hopefully Jonas
8021 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
8022 Debian&lt;/a&gt; soon.&lt;/p&gt;
8023
8024 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
8025 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
8026 bitcoins&lt;/a&gt; when selling services and goods, and there are even
8027 currency &quot;stock&quot; markets where the exchange rate is decided. There
8028 are not many users so far, but the concept seems promising. If you
8029 want to get started and lack a friend with any bitcoins to spare,
8030 you can even get
8031 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
8032 bitcoin at the time of writing). Use
8033 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
8034 on the current exchange rates.&lt;/p&gt;
8035
8036 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
8037 machines. If you want to support my activity, please send Bitcoin
8038 donations to the address
8039 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
8040 </description>
8041 </item>
8042
8043 <item>
8044 <title>Why isn&#39;t Debian Edu using VLC?</title>
8045 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
8046 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
8047 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
8048 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
8049 presented, and the winner among the multimedia player were VLC.
8050 Personally, I like VLC, and it is my player of choice when I first try
8051 to play a video file or stream. Only if VLC fail will I drag out
8052 gmplayer to see if it can do better. The reason is mostly the failure
8053 model and trust. When VLC fail, it normally pop up a error message
8054 reporting the problem. When mplayer fail, it normally segfault or
8055 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
8056
8057 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
8058 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
8059 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
8060 plugin to play web videos seamlessly, and the VLC browser plugin is
8061 not very good. For example, it lack in-line control buttons, so there
8062 is no way for the user to pause the video. Also, when I
8063 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
8064 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
8065 failed on several video pages where mplayer based plugins worked. If
8066 the browser plugin for VLC was as good as the gecko-mediaplayer
8067 package (which uses mplayer), we would switch.&lt;/P&gt;
8068
8069 &lt;p&gt;While VLC is a good player, its user interface is slightly
8070 annoying. The most annoying feature is its inconsistent use of
8071 keyboard shortcuts. When the player is in full screen mode, its
8072 shortcuts are different from when it is playing the video in a window.
8073 For example, space only work as pause when in full screen mode. I
8074 wish it had consisten shortcuts and that space also would work when in
8075 window mode. Another nice shortcut in gmplayer is [enter] to restart
8076 the current video. It is very nice when playing short videos from the
8077 web and want to restart it when new people arrive to have a look at
8078 what is going on.&lt;/p&gt;
8079 </description>
8080 </item>
8081
8082 <item>
8083 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
8084 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
8085 <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>
8086 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
8087 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
8088 upgrade testing of the
8089 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
8090 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
8091 This seem like a very good idea, so I adjusted by test scripts and
8092 can now present the updated result from today:&lt;/p&gt;
8093
8094 &lt;p&gt;This is for Gnome:&lt;/p&gt;
8095
8096 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8097
8098 &lt;blockquote&gt;&lt;p&gt;
8099 apache2.2-bin
8100 aptdaemon
8101 baobab
8102 binfmt-support
8103 browser-plugin-gnash
8104 cheese-common
8105 cli-common
8106 cups-pk-helper
8107 dmz-cursor-theme
8108 empathy
8109 empathy-common
8110 freedesktop-sound-theme
8111 freeglut3
8112 gconf-defaults-service
8113 gdm-themes
8114 gedit-plugins
8115 geoclue
8116 geoclue-hostip
8117 geoclue-localnet
8118 geoclue-manual
8119 geoclue-yahoo
8120 gnash
8121 gnash-common
8122 gnome
8123 gnome-backgrounds
8124 gnome-cards-data
8125 gnome-codec-install
8126 gnome-core
8127 gnome-desktop-environment
8128 gnome-disk-utility
8129 gnome-screenshot
8130 gnome-search-tool
8131 gnome-session-canberra
8132 gnome-system-log
8133 gnome-themes-extras
8134 gnome-themes-more
8135 gnome-user-share
8136 gstreamer0.10-fluendo-mp3
8137 gstreamer0.10-tools
8138 gtk2-engines
8139 gtk2-engines-pixbuf
8140 gtk2-engines-smooth
8141 hamster-applet
8142 libapache2-mod-dnssd
8143 libapr1
8144 libaprutil1
8145 libaprutil1-dbd-sqlite3
8146 libaprutil1-ldap
8147 libart2.0-cil
8148 libboost-date-time1.42.0
8149 libboost-python1.42.0
8150 libboost-thread1.42.0
8151 libchamplain-0.4-0
8152 libchamplain-gtk-0.4-0
8153 libcheese-gtk18
8154 libclutter-gtk-0.10-0
8155 libcryptui0
8156 libdiscid0
8157 libelf1
8158 libepc-1.0-2
8159 libepc-common
8160 libepc-ui-1.0-2
8161 libfreerdp-plugins-standard
8162 libfreerdp0
8163 libgconf2.0-cil
8164 libgdata-common
8165 libgdata7
8166 libgdu-gtk0
8167 libgee2
8168 libgeoclue0
8169 libgexiv2-0
8170 libgif4
8171 libglade2.0-cil
8172 libglib2.0-cil
8173 libgmime2.4-cil
8174 libgnome-vfs2.0-cil
8175 libgnome2.24-cil
8176 libgnomepanel2.24-cil
8177 libgpod-common
8178 libgpod4
8179 libgtk2.0-cil
8180 libgtkglext1
8181 libgtksourceview2.0-common
8182 libmono-addins-gui0.2-cil
8183 libmono-addins0.2-cil
8184 libmono-cairo2.0-cil
8185 libmono-corlib2.0-cil
8186 libmono-i18n-west2.0-cil
8187 libmono-posix2.0-cil
8188 libmono-security2.0-cil
8189 libmono-sharpzip2.84-cil
8190 libmono-system2.0-cil
8191 libmtp8
8192 libmusicbrainz3-6
8193 libndesk-dbus-glib1.0-cil
8194 libndesk-dbus1.0-cil
8195 libopal3.6.8
8196 libpolkit-gtk-1-0
8197 libpt2.6.7
8198 libpython2.6
8199 librpm1
8200 librpmio1
8201 libsdl1.2debian
8202 libsrtp0
8203 libssh-4
8204 libtelepathy-farsight0
8205 libtelepathy-glib0
8206 libtidy-0.99-0
8207 media-player-info
8208 mesa-utils
8209 mono-2.0-gac
8210 mono-gac
8211 mono-runtime
8212 nautilus-sendto
8213 nautilus-sendto-empathy
8214 p7zip-full
8215 pkg-config
8216 python-aptdaemon
8217 python-aptdaemon-gtk
8218 python-axiom
8219 python-beautifulsoup
8220 python-bugbuddy
8221 python-clientform
8222 python-coherence
8223 python-configobj
8224 python-crypto
8225 python-cupshelpers
8226 python-elementtree
8227 python-epsilon
8228 python-evolution
8229 python-feedparser
8230 python-gdata
8231 python-gdbm
8232 python-gst0.10
8233 python-gtkglext1
8234 python-gtksourceview2
8235 python-httplib2
8236 python-louie
8237 python-mako
8238 python-markupsafe
8239 python-mechanize
8240 python-nevow
8241 python-notify
8242 python-opengl
8243 python-openssl
8244 python-pam
8245 python-pkg-resources
8246 python-pyasn1
8247 python-pysqlite2
8248 python-rdflib
8249 python-serial
8250 python-tagpy
8251 python-twisted-bin
8252 python-twisted-conch
8253 python-twisted-core
8254 python-twisted-web
8255 python-utidylib
8256 python-webkit
8257 python-xdg
8258 python-zope.interface
8259 remmina
8260 remmina-plugin-data
8261 remmina-plugin-rdp
8262 remmina-plugin-vnc
8263 rhythmbox-plugin-cdrecorder
8264 rhythmbox-plugins
8265 rpm-common
8266 rpm2cpio
8267 seahorse-plugins
8268 shotwell
8269 software-center
8270 system-config-printer-udev
8271 telepathy-gabble
8272 telepathy-mission-control-5
8273 telepathy-salut
8274 tomboy
8275 totem
8276 totem-coherence
8277 totem-mozilla
8278 totem-plugins
8279 transmission-common
8280 xdg-user-dirs
8281 xdg-user-dirs-gtk
8282 xserver-xephyr
8283 &lt;/p&gt;&lt;/blockquote&gt;
8284
8285 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8286
8287 &lt;blockquote&gt;&lt;p&gt;
8288 cheese
8289 ekiga
8290 eog
8291 epiphany-extensions
8292 evolution-exchange
8293 fast-user-switch-applet
8294 file-roller
8295 gcalctool
8296 gconf-editor
8297 gdm
8298 gedit
8299 gedit-common
8300 gnome-games
8301 gnome-games-data
8302 gnome-nettool
8303 gnome-system-tools
8304 gnome-themes
8305 gnuchess
8306 gucharmap
8307 guile-1.8-libs
8308 libavahi-ui0
8309 libdmx1
8310 libgalago3
8311 libgtk-vnc-1.0-0
8312 libgtksourceview2.0-0
8313 liblircclient0
8314 libsdl1.2debian-alsa
8315 libspeexdsp1
8316 libsvga1
8317 rhythmbox
8318 seahorse
8319 sound-juicer
8320 system-config-printer
8321 totem-common
8322 transmission-gtk
8323 vinagre
8324 vino
8325 &lt;/p&gt;&lt;/blockquote&gt;
8326
8327 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8328
8329 &lt;blockquote&gt;&lt;p&gt;
8330 gstreamer0.10-gnomevfs
8331 &lt;/p&gt;&lt;/blockquote&gt;
8332
8333 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8334
8335 &lt;blockquote&gt;&lt;p&gt;
8336 [nothing]
8337 &lt;/p&gt;&lt;/blockquote&gt;
8338
8339 &lt;p&gt;This is for KDE:&lt;/p&gt;
8340
8341 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8342
8343 &lt;blockquote&gt;&lt;p&gt;
8344 ksmserver
8345 &lt;/p&gt;&lt;/blockquote&gt;
8346
8347 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8348
8349 &lt;blockquote&gt;&lt;p&gt;
8350 kwin
8351 network-manager-kde
8352 &lt;/p&gt;&lt;/blockquote&gt;
8353
8354 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8355
8356 &lt;blockquote&gt;&lt;p&gt;
8357 arts
8358 dolphin
8359 freespacenotifier
8360 google-gadgets-gst
8361 google-gadgets-xul
8362 kappfinder
8363 kcalc
8364 kcharselect
8365 kde-core
8366 kde-plasma-desktop
8367 kde-standard
8368 kde-window-manager
8369 kdeartwork
8370 kdeartwork-emoticons
8371 kdeartwork-style
8372 kdeartwork-theme-icon
8373 kdebase
8374 kdebase-apps
8375 kdebase-workspace
8376 kdebase-workspace-bin
8377 kdebase-workspace-data
8378 kdeeject
8379 kdelibs
8380 kdeplasma-addons
8381 kdeutils
8382 kdewallpapers
8383 kdf
8384 kfloppy
8385 kgpg
8386 khelpcenter4
8387 kinfocenter
8388 konq-plugins-l10n
8389 konqueror-nsplugins
8390 kscreensaver
8391 kscreensaver-xsavers
8392 ktimer
8393 kwrite
8394 libgle3
8395 libkde4-ruby1.8
8396 libkonq5
8397 libkonq5-templates
8398 libnetpbm10
8399 libplasma-ruby
8400 libplasma-ruby1.8
8401 libqt4-ruby1.8
8402 marble-data
8403 marble-plugins
8404 netpbm
8405 nuvola-icon-theme
8406 plasma-dataengines-workspace
8407 plasma-desktop
8408 plasma-desktopthemes-artwork
8409 plasma-runners-addons
8410 plasma-scriptengine-googlegadgets
8411 plasma-scriptengine-python
8412 plasma-scriptengine-qedje
8413 plasma-scriptengine-ruby
8414 plasma-scriptengine-webkit
8415 plasma-scriptengines
8416 plasma-wallpapers-addons
8417 plasma-widget-folderview
8418 plasma-widget-networkmanagement
8419 ruby
8420 sweeper
8421 update-notifier-kde
8422 xscreensaver-data-extra
8423 xscreensaver-gl
8424 xscreensaver-gl-extra
8425 xscreensaver-screensaver-bsod
8426 &lt;/p&gt;&lt;/blockquote&gt;
8427
8428 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8429
8430 &lt;blockquote&gt;&lt;p&gt;
8431 ark
8432 google-gadgets-common
8433 google-gadgets-qt
8434 htdig
8435 kate
8436 kdebase-bin
8437 kdebase-data
8438 kdepasswd
8439 kfind
8440 klipper
8441 konq-plugins
8442 konqueror
8443 ksysguard
8444 ksysguardd
8445 libarchive1
8446 libcln6
8447 libeet1
8448 libeina-svn-06
8449 libggadget-1.0-0b
8450 libggadget-qt-1.0-0b
8451 libgps19
8452 libkdecorations4
8453 libkephal4
8454 libkonq4
8455 libkonqsidebarplugin4a
8456 libkscreensaver5
8457 libksgrd4
8458 libksignalplotter4
8459 libkunitconversion4
8460 libkwineffects1a
8461 libmarblewidget4
8462 libntrack-qt4-1
8463 libntrack0
8464 libplasma-geolocation-interface4
8465 libplasmaclock4a
8466 libplasmagenericshell4
8467 libprocesscore4a
8468 libprocessui4a
8469 libqalculate5
8470 libqedje0a
8471 libqtruby4shared2
8472 libqzion0a
8473 libruby1.8
8474 libscim8c2a
8475 libsmokekdecore4-3
8476 libsmokekdeui4-3
8477 libsmokekfile3
8478 libsmokekhtml3
8479 libsmokekio3
8480 libsmokeknewstuff2-3
8481 libsmokeknewstuff3-3
8482 libsmokekparts3
8483 libsmokektexteditor3
8484 libsmokekutils3
8485 libsmokenepomuk3
8486 libsmokephonon3
8487 libsmokeplasma3
8488 libsmokeqtcore4-3
8489 libsmokeqtdbus4-3
8490 libsmokeqtgui4-3
8491 libsmokeqtnetwork4-3
8492 libsmokeqtopengl4-3
8493 libsmokeqtscript4-3
8494 libsmokeqtsql4-3
8495 libsmokeqtsvg4-3
8496 libsmokeqttest4-3
8497 libsmokeqtuitools4-3
8498 libsmokeqtwebkit4-3
8499 libsmokeqtxml4-3
8500 libsmokesolid3
8501 libsmokesoprano3
8502 libtaskmanager4a
8503 libtidy-0.99-0
8504 libweather-ion4a
8505 libxklavier16
8506 libxxf86misc1
8507 okteta
8508 oxygencursors
8509 plasma-dataengines-addons
8510 plasma-scriptengine-superkaramba
8511 plasma-widget-lancelot
8512 plasma-widgets-addons
8513 plasma-widgets-workspace
8514 polkit-kde-1
8515 ruby1.8
8516 systemsettings
8517 update-notifier-common
8518 &lt;/p&gt;&lt;/blockquote&gt;
8519
8520 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
8521 aptitude a bit more similar, but there are still quite a lott of
8522 differences. I have no idea what packages should be installed after
8523 the upgrade, but hope those that do can have a look.&lt;/p&gt;
8524 </description>
8525 </item>
8526
8527 <item>
8528 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
8529 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
8530 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
8531 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
8532 <description>&lt;p&gt;Most of the computers in use by the
8533 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
8534 are virtual machines. And they have been Xen machines running on a
8535 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
8536 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
8537 bit harder that it could have been, because we set up the Xen virtual
8538 machines to get the virtual partitions from LVM, which as far as I
8539 know is not supported by KVM. So to migrate, we had to convert
8540 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
8541
8542 &lt;p&gt;I found
8543 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
8544 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
8545 migration. It uses qemu-img from the qemu package to make the disk
8546 image, parted to partition it, losetup and kpartx to present the disk
8547 image partions as devices, and dd to copy the data. I NFS mounted the
8548 new servers storage area on the old server to do the migration.&lt;/p&gt;
8549
8550 &lt;pre&gt;
8551 #!/bin/sh
8552
8553 # Based on
8554 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8555
8556 set -e
8557 set -x
8558
8559 if [ -z &quot;$1&quot; ] ; then
8560 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
8561 exit 1
8562 else
8563 host=&quot;$1&quot;
8564 fi
8565
8566 if [ ! -e /dev/vg_data/$host-disk ] ; then
8567 echo &quot;error: unable to find LVM volume for $host&quot;
8568 exit 1
8569 fi
8570
8571 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8572 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
8573 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
8574 totalsize=$(( ( $disksize + $swapsize ) ))
8575
8576 img=$host.img
8577 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
8578 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8579
8580 parted $img mklabel msdos
8581 parted $img mkpart primary linux-swap 0 $disksize
8582 parted $img mkpart primary ext2 $disksize $totalsize
8583 parted $img set 1 boot on
8584
8585 modprobe dm-mod
8586 losetup /dev/loop0 $img
8587 kpartx -a /dev/loop0
8588
8589 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
8590 fsck.ext3 -f /dev/mapper/loop0p1 || true
8591 mkswap /dev/mapper/loop0p2
8592
8593 kpartx -d /dev/loop0
8594 losetup -d /dev/loop0
8595 &lt;/pre&gt;
8596
8597 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
8598 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
8599
8600 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
8601 the new disk image attached, installed grub-pc and linux-image-686 and
8602 set up grub to boot from the disk image. After this, the KVM machines
8603 seem to work just fine.&lt;/p&gt;
8604 </description>
8605 </item>
8606
8607 <item>
8608 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
8609 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
8610 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
8611 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
8612 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
8613 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
8614 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
8615 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
8616
8617 &lt;p&gt;I still do not know what a correct migration should look like, so I
8618 report any differences between apt and aptitude and hope someone else
8619 can see if anything should be changed.&lt;/p&gt;
8620
8621 &lt;p&gt;This is for Gnome:&lt;/p&gt;
8622
8623 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8624
8625 &lt;blockquote&gt;&lt;p&gt;
8626 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8627 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
8628 dmz-cursor-theme empathy empathy-common finger
8629 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8630 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8631 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8632 gnome-cards-data gnome-codec-install gnome-core
8633 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8634 gnome-search-tool gnome-session-canberra gnome-spell
8635 gnome-system-log gnome-themes-extras gnome-themes-more
8636 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8637 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8638 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8639 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8640 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
8641 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
8642 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
8643 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
8644 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
8645 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8646 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
8647 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8648 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8649 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8650 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8651 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8652 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8653 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8654 libmono-security2.0-cil libmono-sharpzip2.84-cil
8655 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
8656 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
8657 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
8658 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
8659 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
8660 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
8661 libxalan2-java libxerces2-java media-player-info mesa-utils
8662 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
8663 nautilus-sendto-empathy openoffice.org-writer2latex
8664 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
8665 python-aptdaemon python-aptdaemon-gtk python-axiom
8666 python-beautifulsoup python-bugbuddy python-clientform
8667 python-coherence python-configobj python-crypto python-cupshelpers
8668 python-cupsutils python-eggtrayicon python-elementtree
8669 python-epsilon python-evolution python-feedparser python-gdata
8670 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8671 python-gtksourceview2 python-httplib2 python-louie python-mako
8672 python-markupsafe python-mechanize python-nevow python-notify
8673 python-opengl python-openssl python-pam python-pkg-resources
8674 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8675 python-tagpy python-twisted-bin python-twisted-conch
8676 python-twisted-core python-twisted-web python-utidylib python-webkit
8677 python-xdg python-zope.interface remmina remmina-plugin-data
8678 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8679 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8680 software-center svgalibg1 system-config-printer-udev
8681 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
8682 totem totem-coherence totem-mozilla totem-plugins
8683 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8684 zip
8685 &lt;/p&gt;&lt;/blockquote&gt;
8686
8687 Installed using apt-get, removed with aptitude
8688
8689 &lt;blockquote&gt;&lt;p&gt;
8690 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8691 epiphany-extensions epiphany-gecko evolution-exchange
8692 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8693 gedit-common gnome-app-install gnome-games gnome-games-data
8694 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8695 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8696 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8697 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
8698 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
8699 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
8700 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
8701 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
8702 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
8703 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
8704 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
8705 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
8706 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8707 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8708 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8709 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8710 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
8711 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
8712 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
8713 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
8714 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
8715 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8716 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8717 sound-juicer swfdec-gnome system-config-printer totem-common
8718 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8719 &lt;/p&gt;&lt;/blockquote&gt;
8720
8721 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8722
8723 &lt;blockquote&gt;&lt;p&gt;
8724 gstreamer0.10-gnomevfs
8725 &lt;/p&gt;&lt;/blockquote&gt;
8726
8727 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8728
8729 &lt;blockquote&gt;&lt;p&gt;
8730 [nothing]
8731 &lt;/p&gt;&lt;/blockquote&gt;
8732
8733 &lt;p&gt;This is for KDE:&lt;/p&gt;
8734
8735 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8736
8737 &lt;blockquote&gt;&lt;p&gt;
8738 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
8739 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8740 ghostscript-x git gnome-audio gnugo granatier gs-common
8741 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8742 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8743 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8744 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8745 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8746 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8747 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8748 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8749 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8750 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8751 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8752 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
8753 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8754 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8755 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8756 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8757 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8758 libkrossui4 libmailtools-perl libmime-tools-perl
8759 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8760 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8761 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8762 lirc luatex marble networkstatus noatun-plugins
8763 openoffice.org-writer2latex palapeli palapeli-data parley
8764 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8765 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8766 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8767 ttf-sazanami-gothic
8768 &lt;/p&gt;&lt;/blockquote&gt;
8769
8770 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8771
8772 &lt;blockquote&gt;&lt;p&gt;
8773 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8774 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8775 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8776 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8777 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8778 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8779 kitchensync kiten kjumpingcube klatin klettres klickety klines
8780 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8781 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8782 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8783 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8784 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8785 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8786 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8787 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8788 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8789 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
8790 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
8791 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8792 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
8793 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
8794 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8795 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8796 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8797 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8798 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8799 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8800 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
8801 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
8802 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8803 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8804 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8805 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8806 &lt;/p&gt;&lt;/blockquote&gt;
8807
8808 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8809
8810 &lt;blockquote&gt;&lt;p&gt;
8811 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8812 kdeartwork kdebase kdebase-apps kdebase-workspace
8813 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8814 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8815 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8816 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8817 xscreensaver-screensaver-bsod
8818 &lt;/p&gt;&lt;/blockquote&gt;
8819
8820 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8821
8822 &lt;blockquote&gt;&lt;p&gt;
8823 kdebase-bin konq-plugins konqueror
8824 &lt;/p&gt;&lt;/blockquote&gt;
8825 </description>
8826 </item>
8827
8828 <item>
8829 <title>Gnash buildbot slave and Debian kfreebsd</title>
8830 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
8831 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
8832 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
8833 <description>&lt;p&gt;Answering
8834 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
8835 call from the Gnash project&lt;/a&gt; for
8836 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
8837 current source, I have set up a virtual KVM machine on the Debian
8838 Edu/Skolelinux virtualization host to test the git source on
8839 Debian/Squeeze. I hope this can help the developers in getting new
8840 releases out more often.&lt;/p&gt;
8841
8842 &lt;p&gt;As the developers want less main-stream build platforms tested to,
8843 I have considered setting up a &lt;a
8844 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
8845 machine as well. I have also considered using the kfreebsd
8846 architecture in Debian as a file server in NUUG to get access to the 5
8847 TB zfs volume we currently use to store DV video. Because of this, I
8848 finally got around to do a test installation of Debian/Squeeze with
8849 kfreebsd. Installation went fairly smooth, thought I noticed some
8850 visual glitches in the cdebconf dialogs (black cursor left on the
8851 screen at random locations). Have not gotten very far with the
8852 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8853 fatal problem. Have to spend some more time on it to see if it is
8854 useful as a file server for NUUG. Will try to find time to set up a
8855 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
8856 </description>
8857 </item>
8858
8859 <item>
8860 <title>Debian in 3D</title>
8861 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
8862 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
8863 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
8864 <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;
8865
8866 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
8867 3D linked in from
8868 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
8869 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
8870 </description>
8871 </item>
8872
8873 <item>
8874 <title>Software updates 2010-10-24</title>
8875 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
8876 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
8877 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
8878 <description>&lt;p&gt;Some updates.&lt;/p&gt;
8879
8880 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
8881 raise money for the project is going well. The lower limit of 10
8882 signers was reached in 24 hours, and so far 13 people have signed it.
8883 More signers and more funding is most welcome, and I am really curious
8884 how far we can get before the time limit of December 24 is reached.
8885 :)&lt;/p&gt;
8886
8887 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
8888 about what appear to be a great code coverage tool capable of
8889 generating code coverage stats without any changes to the source code.
8890 It is called
8891 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
8892 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
8893 It is missing in Debian, but the git source built just fine in Squeeze
8894 after I installed libelf-dev, libdwarf-dev, pkg-config and
8895 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8896 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
8897
8898 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
8899 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
8900 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
8901 alpha test release of the Squeeze based Debian Edu /
8902 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
8903 release. Give it a try if you need a complete linux solution for your
8904 school, including central infrastructure server, workstations, thin
8905 client servers and diskless workstations. A nice touch added
8906 yesterday is RDP support on the thin client servers, for windows
8907 clients to get a Linux desktop on request.&lt;/p&gt;
8908 </description>
8909 </item>
8910
8911 <item>
8912 <title>Some notes on Flash in Debian and Debian Edu</title>
8913 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
8914 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
8915 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
8916 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
8917 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
8918 second most popular used package that is missing in Debian. The sixth
8919 most popular is flashplayer-mozilla. This is a clear indication that
8920 working flash is important for Debian users. Around 10 percent of the
8921 users submitting data to popcon.debian.org have this package
8922 installed.&lt;/p&gt;
8923
8924 &lt;p&gt;In the report written by Lars Risan in August 2008
8925&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
8926 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8927 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
8928 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
8929 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
8930 web sites require Flash to work, and lacking working Flash support in
8931 the web browser and the problems with installing it was perceived as a
8932 good reason to stay with Windows.&lt;/p&gt;
8933
8934 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
8935 said to be the retarded cousin that did not really understand
8936 everything you told him but could work fairly well. This was a
8937 comment regarding the problems Linux have with proprietary formats and
8938 non-standard web pages, and is sad because it exposes a fairly common
8939 understanding of whose fault it is if web pages that only work in for
8940 example Internet Explorer 6 fail to work on Firefox, and funny because
8941 it explain very well how annoying it is for users when Linux
8942 distributions do not work with the documents they receive or the web
8943 pages they want to visit.&lt;/p&gt;
8944
8945 &lt;p&gt;This is part of the reason why I believe it is important for Debian
8946 and Debian Edu to have a well working Flash implementation in the
8947 distribution, to get at least popular sites as Youtube and Google
8948 Video to working out of the box. For Squeeze, Debian have the chance
8949 to include the latest version of Gnash that will make this happen, as
8950 the new release 0.8.8 was published a few weeks ago and is resting in
8951 unstable. The new version work with more sites that version 0.8.7.
8952 The Gnash maintainers have asked for a freeze exception, but the
8953 release team have not had time to reply to it yet. I hope they agree
8954 with me that Flash is important for the Debian desktop users, and thus
8955 accept the new package into Squeeze.&lt;/p&gt;
8956 </description>
8957 </item>
8958
8959 <item>
8960 <title>Circular package dependencies harms apt recovery</title>
8961 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
8962 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
8963 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
8964 <description>&lt;p&gt;I discovered this while doing
8965 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
8966 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
8967 in Debian still got circular dependencies, and it is often claimed
8968 that apt and aptitude should be able to handle this just fine, but
8969 some times these dependency loops causes apt to fail.&lt;/p&gt;
8970
8971 &lt;p&gt;An example is from todays
8972 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
8973 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
8974 causes perl-modules to fail to upgrade. The cause is simple. If a
8975 package fail to unpack, then only part of packages with the circular
8976 dependency might end up being unpacked when unpacking aborts, and the
8977 ones already unpacked will fail to configure in the recovery phase
8978 because its dependencies are unavailable.&lt;/p&gt;
8979
8980 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
8981
8982 &lt;blockquote&gt;&lt;pre&gt;
8983 dpkg: dependency problems prevent configuration of perl-modules:
8984 perl-modules depends on perl (&gt;= 5.10.1-1); however:
8985 Version of perl on system is 5.10.0-19lenny2.
8986 dpkg: error processing perl-modules (--configure):
8987 dependency problems - leaving unconfigured
8988 &lt;/pre&gt;&lt;/blockquote&gt;
8989
8990 &lt;p&gt;The perl/perl-modules circular dependency is already
8991 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
8992 hopefully be solved as soon as possible, but it is not the only one,
8993 and each one of these loops in the dependency tree can cause similar
8994 failures. Of course, they only occur when there are bugs in other
8995 packages causing the unpacking to fail, but it is rather nasty when
8996 the failure of one package causes the problem to become worse because
8997 of dependency loops.&lt;/p&gt;
8998
8999 &lt;p&gt;Thanks to
9000 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
9001 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
9002 dependencies
9003 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
9004 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
9005
9006 &lt;p&gt;Todays testing also exposed a bug in
9007 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
9008 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
9009 apt-get and aptitude, the latter possibly caused by some circular
9010 dependency. Reported both to BTS to try to get someone to look at
9011 it.&lt;/p&gt;
9012 </description>
9013 </item>
9014
9015 <item>
9016 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
9017 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
9018 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
9019 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
9020 <description>&lt;p&gt;This is a
9021 &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;
9022 on my
9023 &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
9024 work&lt;/a&gt; on
9025 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
9026 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
9027
9028 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
9029 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9030 and dhcp3-server-ldap in Debian use the LDAP server. The two
9031 implementations are quite different in how they use LDAP.&lt;/p&gt;
9032
9033 To get this information, I started slapd with debugging enabled and
9034 dumped the debug output to a file to get the LDAP searches performed
9035 on a Debian Edu main-server. Here is a summary.
9036
9037 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
9038
9039 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
9040 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
9041 the web.
9042
9043 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
9044 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
9045 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
9046 reverse entries are in two different subtrees in LDAP with a structure
9047 based on the DNS names, as in tjener.intern and
9048 2.2.0.10.in-addr.arpa.&lt;/p&gt;
9049
9050 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
9051 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
9052 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
9053 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
9054 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
9055 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
9056 forward entries, it is looking for attributes named dnsttl, arecord,
9057 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9058 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9059 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9060 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9061 spfrecord and modifytimestamp. For reverse entries it is looking for
9062 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9063 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9064 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9065 ldapsearch commands could look like this:&lt;/p&gt;
9066
9067 &lt;blockquote&gt;&lt;pre&gt;
9068 ldapsearch -h ldap \
9069 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9070 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
9071 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9072 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9073 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9074 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9075
9076 ldapsearch -h ldap \
9077 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9078 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
9079 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9080 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9081 srvrecord naptrrecord modifytimestamp
9082 &lt;/pre&gt;&lt;/blockquote&gt;
9083
9084 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
9085 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9086 example LDAP objects used there. In addition to these objects, the
9087 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9088 also exist.&lt;/p&gt;
9089
9090 &lt;blockquote&gt;&lt;pre&gt;
9091 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9092 objectclass: top
9093 objectclass: dnsdomain
9094 objectclass: domainrelatedobject
9095 dc: tjener
9096 arecord: 10.0.2.2
9097 associateddomain: tjener.intern
9098
9099 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9100 objectclass: top
9101 objectclass: dnsdomain2
9102 objectclass: domainrelatedobject
9103 dc: 2
9104 ptrrecord: tjener.intern
9105 associateddomain: 2.2.0.10.in-addr.arpa
9106 &lt;/pre&gt;&lt;/blockquote&gt;
9107
9108 &lt;p&gt;In strict mode, the server behaves differently. When looking for
9109 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
9110 same base as in the tree mode for a object with filter
9111 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
9112 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9113 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9114 naptrrecord and modifytimestamp. For reverse entires it also do a
9115 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
9116 and the requested attributes are associateddomain, dnsttl and
9117 modifytimestamp. In short, in strict mode the objects with ptrrecord
9118 go away, and the arecord attribute in the forward object is used
9119 instead.&lt;/p&gt;
9120
9121 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
9122 like this:&lt;/p&gt;
9123
9124 &lt;blockquote&gt;&lt;pre&gt;
9125 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9126 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
9127 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9128 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9129 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9130 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9131
9132 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9133 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
9134 &lt;/pre&gt;&lt;/blockquote&gt;
9135
9136 &lt;p&gt;In addition to the forward and reverse searches , there is also a
9137 search for SOA records, which behave similar to the forward and
9138 reverse lookups.&lt;/p&gt;
9139
9140 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
9141 specify any objectclass names, and instead look for the attributes it
9142 need to generate a DNS reply. This make it able to work with any
9143 objectclass that provide the needed attributes.&lt;/p&gt;
9144
9145 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
9146 dnsdomain2 schemas. The latter is used for reverse entries like
9147 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
9148
9149 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
9150 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9151 attributes) and domainrelatedobject (for associatedDomain). The use
9152 of structural object classes make it impossible to combine these
9153 classes with the object classes used by DHCP.&lt;/p&gt;
9154
9155 &lt;p&gt;There are other schemas that could be used too, for example the
9156 dnszone structural object class used by Gosa and bind-sdb for the DNS
9157 attributes combined with the domainrelatedobject object class, but in
9158 this case some unused attributes would have to be included as well
9159 (zonename and relativedomainname).&lt;/p&gt;
9160
9161 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
9162 mode and not use any of the existing objectclasses (dnsdomain,
9163 dnsdomain2 and dnszone) when one want to combine the DNS information
9164 with DHCP information, and instead create a auxiliary object class
9165 defined something like this (using the attributes defined for
9166 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
9167
9168 &lt;blockquote&gt;&lt;pre&gt;
9169 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
9170 SUP top
9171 AUXILIARY
9172 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9173 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9174 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9175 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9176 A6Record $ DNAMERecord
9177 ))
9178 &lt;/pre&gt;&lt;/blockquote&gt;
9179
9180 &lt;p&gt;This will allow any object to become a DNS entry when combined with
9181 the domainrelatedobject object class, and allow any entity to include
9182 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
9183 developers asking for their view on this schema and if they are
9184 interested in providing such schema with PowerDNS, and I hope my
9185 message will be accepted into their mailing list soon.&lt;/p&gt;
9186
9187 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
9188
9189 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
9190 the object attributes, and then uses the attributes it want. This
9191 make it harder to figure out exactly what attributes are used, but
9192 thanks to the working example in Debian Edu I can at least get an idea
9193 what is needed without having to read the source code.&lt;/p&gt;
9194
9195 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
9196 search filter to use to locate the correct dhcpServer entity is
9197 stored. These are the relevant entries from
9198 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
9199
9200 &lt;blockquote&gt;&lt;pre&gt;
9201 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
9202 ldap-dhcp-server-cn &quot;dhcp&quot;;
9203 &lt;/pre&gt;&lt;/blockquote&gt;
9204
9205 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
9206 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
9207 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
9208 search result is this entry:&lt;/p&gt;
9209
9210 &lt;blockquote&gt;&lt;pre&gt;
9211 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9212 cn: dhcp
9213 objectClass: top
9214 objectClass: dhcpServer
9215 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9216 &lt;/pre&gt;&lt;/blockquote&gt;
9217
9218 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
9219 subtree with DHCP configuration. The DHCP configuration subtree base
9220 is located using a base scope search with base &quot;cn=DHCP
9221 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
9222 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
9223 The search result is this entry:&lt;/p&gt;
9224
9225 &lt;blockquote&gt;&lt;pre&gt;
9226 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9227 cn: DHCP Config
9228 objectClass: top
9229 objectClass: dhcpService
9230 objectClass: dhcpOptions
9231 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9232 dhcpStatements: ddns-update-style none
9233 dhcpStatements: authoritative
9234 dhcpOption: smtp-server code 69 = array of ip-address
9235 dhcpOption: www-server code 72 = array of ip-address
9236 dhcpOption: wpad-url code 252 = text
9237 &lt;/pre&gt;&lt;/blockquote&gt;
9238
9239 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
9240 all the DHCP configuration is loaded, it is ready to receive requests.
9241 The subtree in Debian Edu contain objects with object classes
9242 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9243 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9244 and information about netmasks, dynamic range etc. Leaving out the
9245 details here because it is not relevant for the focus of my
9246 investigation, which is to see if it is possible to merge dns and dhcp
9247 related computer objects.&lt;/p&gt;
9248
9249 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
9250 of the client (00:00:00:00:00:00 in this example), using a subtree
9251 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
9252 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9253 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
9254 like:&lt;/p&gt;
9255
9256 &lt;blockquote&gt;&lt;pre&gt;
9257 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9258 cn: hostname
9259 objectClass: top
9260 objectClass: dhcpHost
9261 dhcpHWAddress: ethernet 00:00:00:00:00:00
9262 dhcpStatements: fixed-address hostname
9263 &lt;/pre&gt;&lt;/blockquote&gt;
9264
9265 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
9266 The object classes need to have fixed names, and the configuration
9267 need to be stored in a fairly specific LDAP structure. On the
9268 positive side, the invidiual dhcpHost entires can be anywhere without
9269 the DN pointed to by the dhcpServer entries. The latter should make
9270 it possible to group all host entries in a subtree next to the
9271 configuration entries, and this subtree can also be shared with the
9272 DNS server if the schema proposed above is combined with the dhcpHost
9273 structural object class.
9274
9275 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
9276
9277 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
9278 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
9279 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
9280 allowing DNS objects to be stored anywhere under the base cn specified
9281 in the configuration.&lt;/p&gt;
9282
9283 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
9284 regarding which LDAP schemas to use and which LDAP structure to use.
9285 I guess one could implement ones own schema, as long as the
9286 objectclasses and attributes have the names used, but this do not
9287 really help when the DHCP subtree need to have a fairly fixed
9288 structure.&lt;/p&gt;
9289
9290 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
9291 this might work for Debian Edu:&lt;/p&gt;
9292
9293 &lt;blockquote&gt;&lt;pre&gt;
9294 ou=services
9295 cn=machine-info (dhcpService) - dhcpServiceDN points here
9296 cn=dhcp (dhcpServer)
9297 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9298 cn=10.0.2.0 (dhcpSubnet)
9299 cn=group1 (dhcpGroup/dhcpOptions)
9300 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9301 cn=192.168.0.0 (dhcpSubnet)
9302 cn=group1 (dhcpGroup/dhcpOptions)
9303 ou=machines - PowerDNS base points here
9304 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9305 &lt;/pre&gt;&lt;/blockquote&gt;
9306
9307 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
9308 entries to be in the dhcpGroup subtrees, the entries can be stored
9309 there instead of a common machines subtree, and the PowerDNS base
9310 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
9311
9312 &lt;p&gt;The combined object under the machines subtree would look something
9313 like this:&lt;/p&gt;
9314
9315 &lt;blockquote&gt;&lt;pre&gt;
9316 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9317 dc: hostname
9318 objectClass: top
9319 objectClass: dhcpHost
9320 objectclass: domainrelatedobject
9321 objectclass: dnsDomainAux
9322 associateddomain: hostname.intern
9323 arecord: 10.11.12.13
9324 dhcpHWAddress: ethernet 00:00:00:00:00:00
9325 dhcpStatements: fixed-address hostname.intern
9326 &lt;/pre&gt;&lt;/blockquote&gt;
9327
9328 &lt;/p&gt;One could even add the LTSP configuration associated with a given
9329 machine, as long as the required attributes are available in a
9330 auxiliary object class.&lt;/p&gt;
9331 </description>
9332 </item>
9333
9334 <item>
9335 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
9336 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
9337 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
9338 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
9339 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
9340 DHCP services in Debian Edu to use the same LDAP objects for a given
9341 computer, to avoid the possibility of having a inconsistent state for
9342 a computer in LDAP (as in DHCP but no DNS entry or the other way
9343 around) and make it easier to add computers to LDAP.&lt;/p&gt;
9344
9345 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
9346 information finally found a solution that seem to work.&lt;/p&gt;
9347
9348 &lt;p&gt;The old setup required three LDAP objects for a given computer.
9349 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9350 we switch powerdns to use its strict LDAP method (ldap-method=strict
9351 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9352 merged into one while making it impossible to transfer the reverse map
9353 to a slave DNS server.&lt;/p&gt;
9354
9355 &lt;p&gt;If we also replace the object class used to get the DNS related
9356 attributes to one allowing these attributes to be combined with the
9357 dhcphost object class, we can merge the DNS and DHCP entries into one.
9358 I&#39;ve written such object class in the dnsdomainaux.schema file (need
9359 proper OIDs, but that is a minor issue), and tested the setup. It
9360 seem to work.&lt;/p&gt;
9361
9362 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
9363 for both DNS and DHCP, and even the LTSP configuration I suggested in
9364 an earlier email. The combined LDAP object will look something like
9365 this:&lt;/p&gt;
9366
9367 &lt;blockquote&gt;&lt;pre&gt;
9368 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9369 cn: hostname
9370 objectClass: dhcphost
9371 objectclass: domainrelatedobject
9372 objectclass: dnsdomainaux
9373 associateddomain: hostname.intern
9374 arecord: 10.11.12.13
9375 dhcphwaddress: ethernet 00:00:00:00:00:00
9376 dhcpstatements: fixed-address hostname
9377 ldapconfigsound: Y
9378 &lt;/pre&gt;&lt;/blockquote&gt;
9379
9380 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
9381 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9382 before asking DNS to resolve the fixed-adddress. LTSP will use
9383 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
9384
9385 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
9386 dhcphost in a different location, to allow us to put the objects
9387 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
9388 that. If I can&#39;t figure out a way to do that, we can still get rid of
9389 the hosts subtree and move all its content into the DHCP Config tree
9390 (which probably should be renamed to be more related to the new
9391 content. I suspect cn=dnsdhcp,ou=services or something like that
9392 might be a good place to put it.&lt;/p&gt;
9393
9394 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
9395 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9396 </description>
9397 </item>
9398
9399 <item>
9400 <title>Idea for storing LTSP configuration in LDAP</title>
9401 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
9402 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
9403 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
9404 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
9405 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9406 clients, and that this can be used to fetch configuration from LDAP if
9407 Debian Edu choose to store configuration there.&lt;/p&gt;
9408
9409 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
9410 to get configuration from LDAP. The idea is to look up the MAC
9411 address of the client in LDAP, and look for attributes on the form
9412 ltspconfigsetting=value, and use this to export SETTING=value to the
9413 LTSP clients.&lt;/p&gt;
9414
9415 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
9416 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
9417 allowing us to store all information about a computer in one place.&lt;/p&gt;
9418
9419 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
9420 this approach. A real LDAP schema for the ltspClientAux objectclass
9421 need to be written. Comments, suggestions, etc?&lt;/p&gt;
9422
9423 &lt;blockquote&gt;&lt;pre&gt;
9424 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9425 #
9426 # Fetch LTSP client settings from LDAP based on MAC address
9427 #
9428 # Uses ethernet address as stored in the dhcpHost objectclass using
9429 # the dhcpHWAddress attribute or ethernet address stored in the
9430 # ieee802Device objectclass with the macAddress attribute.
9431 #
9432 # This module is written to be schema agnostic, and only depend on the
9433 # existence of attribute names.
9434 #
9435 # The LTSP configuration variables are saved directly using a
9436 # ltspConfig prefix and uppercasing the rest of the attribute name.
9437 # To set the SERVER variable, set the ltspConfigServer attribute.
9438 #
9439 # Some LDAP schema should be created with all the relevant
9440 # configuration settings. Something like this should work:
9441 #
9442 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
9443 # SUP top
9444 # AUXILIARY
9445 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9446
9447 LDAPSERVER=$(debian-edu-ldapserver)
9448 if [ &quot;$LDAPSERVER&quot; ] ; then
9449 LDAPBASE=$(debian-edu-ldapserver -b)
9450 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
9451 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
9452 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
9453 grep &#39;^ltspConfig&#39; | while read attr value ; do
9454 # Remove prefix and convert to upper case
9455 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
9456 # bass value on to clients
9457 eval &quot;$attr=$value; export $attr&quot;
9458 done
9459 done
9460 fi
9461 &lt;/pre&gt;&lt;/blockquote&gt;
9462
9463 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
9464 the while block might end up in a subshell causing the variables set
9465 there to not show up in ltsp-config, but if that is the case I am sure
9466 the code can be restructured to make sure the variables are passed on.
9467 I expect that can be solved with some testing. :)&lt;/p&gt;
9468
9469 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
9470 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9471
9472 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
9473 configuration in LDAP that was created around year 2000 by
9474 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
9475 Xperience, Inc., 2000&lt;/a&gt;. I found its
9476 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
9477 personal home page over at redhat.com.&lt;/p&gt;
9478 </description>
9479 </item>
9480
9481 <item>
9482 <title>jXplorer, a very nice LDAP GUI</title>
9483 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
9484 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
9485 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
9486 <description>&lt;p&gt;Since
9487 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
9488 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
9489 LDAP GUI that is even better than luma. The java application
9490 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
9491 moving LDAP objects and subtrees using drag-and-drop, and can
9492 authenticate using Kerberos. I have only tested the Kerberos
9493 authentication, but do not have a LDAP setup allowing me to rewrite
9494 LDAP with my test user yet. It is
9495 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
9496 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
9497 have with it is how it handle errors. If something go wrong, its
9498 non-intuitive behaviour require me to go through some query work list
9499 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
9500 </description>
9501 </item>
9502
9503 <item>
9504 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
9505 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
9506 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
9507 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
9508 <description>&lt;p&gt;Here is a short update on my &lt;a
9509 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
9510 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
9511 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
9512 not reporting the status for KDE, because the upgrade crashes when
9513 aptitude try because of missing conflicts
9514 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
9515 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
9516
9517 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
9518 complete list of the installed packages. Based on this I see these
9519 differences when I did a test run today. As usual, I do not really
9520 know what the correct set of packages would be, but thought it best to
9521 publish the difference.&lt;/p&gt;
9522
9523 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9524
9525 &lt;blockquote&gt;&lt;p&gt;
9526 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
9527 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
9528 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9529 libgtksourceview-common libpt-1.10.10-plugins-alsa
9530 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9531 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9532 python-4suite-xml python-eggtrayicon python-gtkhtml2
9533 python-gtkmozembed svgalibg1 xserver-xephyr zip
9534 &lt;/p&gt;&lt;/blockquote&gt;
9535
9536 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9537
9538 &lt;blockquote&gt;&lt;p&gt;
9539 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9540 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9541 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
9542 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
9543 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
9544 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
9545 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
9546 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
9547 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
9548 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
9549 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
9550 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
9551 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9552 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
9553 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9554 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
9555 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
9556 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9557 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9558 mysql-common swfdec-gnome totem-gstreamer wodim
9559 &lt;/p&gt;&lt;/blockquote&gt;
9560
9561 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9562
9563 &lt;blockquote&gt;&lt;p&gt;
9564 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9565 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9566 xserver-xorg-input-all xserver-xorg-input-evdev
9567 xserver-xorg-input-kbd xserver-xorg-input-mouse
9568 xserver-xorg-input-synaptics xserver-xorg-video-all
9569 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9570 xserver-xorg-video-chips xserver-xorg-video-cirrus
9571 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9572 xserver-xorg-video-glint xserver-xorg-video-i128
9573 xserver-xorg-video-i740 xserver-xorg-video-mach64
9574 xserver-xorg-video-mga xserver-xorg-video-neomagic
9575 xserver-xorg-video-nouveau xserver-xorg-video-nv
9576 xserver-xorg-video-r128 xserver-xorg-video-radeon
9577 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9578 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9579 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9580 xserver-xorg-video-sis xserver-xorg-video-sisusb
9581 xserver-xorg-video-tdfx xserver-xorg-video-tga
9582 xserver-xorg-video-trident xserver-xorg-video-tseng
9583 xserver-xorg-video-vesa xserver-xorg-video-vmware
9584 xserver-xorg-video-voodoo
9585 &lt;/p&gt;&lt;/blockquote&gt;
9586
9587 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9588
9589 &lt;blockquote&gt;&lt;p&gt;
9590 deskbar-applet xserver-xorg xserver-xorg-core
9591 xserver-xorg-input-wacom xserver-xorg-video-intel
9592 xserver-xorg-video-openchrome
9593 &lt;/p&gt;&lt;/blockquote&gt;
9594
9595 &lt;p&gt;I was told on IRC that the xorg-xserver package was
9596 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
9597 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
9598 No idea when it hits Squeeze, but when it does I hope it will reduce
9599 the difference somewhat.
9600 </description>
9601 </item>
9602
9603 <item>
9604 <title>LUMA, a very nice LDAP GUI</title>
9605 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
9606 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
9607 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
9608 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
9609 directory in Debian Edu, and in the process I started to miss a GUI
9610 tool to browse the LDAP tree. The only one I was able to find in
9611 Debian/Squeeze and Lenny is
9612 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
9613 be a great tool to get a overview of the current LDAP directory
9614 populated by default in Skolelinux. Thanks to it, I have been able to
9615 find empty and obsolete subtrees, misplaced objects and duplicate
9616 objects. It will be installed by default in Debian/Squeeze. If you
9617 are working with LDAP, give it a go. :)&lt;/p&gt;
9618
9619 &lt;p&gt;I did notice one problem with it I have not had time to report to
9620 the BTS yet. There is no .desktop file in the package, so the tool do
9621 not show up in the Gnome and KDE menus, but only deep down in in the
9622 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9623 released.&lt;/p&gt;
9624
9625 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
9626 like to move objects and remove subtrees directly in the GUI, but have
9627 not found a way to do that with LUMA yet. So in the mean time, I use
9628 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
9629
9630 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
9631 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9632
9633 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
9634 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
9635 useful GUI alternative. It seem like a good tool, but is unmaintained
9636 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9637 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
9638 </description>
9639 </item>
9640
9641 <item>
9642 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
9643 <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>
9644 <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>
9645 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
9646 <description>&lt;p&gt;A while back, I
9647 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
9648 about the fact&lt;/a&gt; that it is not possible with the provided schemas
9649 for storing DNS and DHCP information in LDAP to combine the two sets
9650 of information into one LDAP object representing a computer.&lt;/p&gt;
9651
9652 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
9653 the dhcpHost object class auxiliary, to allow it to be combined with
9654 the dNSDomain object class, and thus forming one object for one
9655 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
9656
9657 &lt;p&gt;If I understand this correctly, it is not safe to do this change
9658 without also changing the assigned number for the object class, and I
9659 do not know enough about LDAP schema design to do that properly for
9660 Debian Edu.&lt;/p&gt;
9661
9662 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
9663 the
9664 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
9665 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
9666 available today from IETF.&lt;/p&gt;
9667
9668 &lt;pre&gt;
9669 --- dhcp.schema (revision 65192)
9670 +++ dhcp.schema (working copy)
9671 @@ -376,7 +376,7 @@
9672 objectclass ( 2.16.840.1.113719.1.203.6.6
9673 NAME &#39;dhcpHost&#39;
9674 DESC &#39;This represents information about a particular client&#39;
9675 - SUP top
9676 + SUP top AUXILIARY
9677 MUST cn
9678 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9679 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
9680 &lt;/pre&gt;
9681
9682 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
9683 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9684 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
9685
9686 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
9687 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9688 </description>
9689 </item>
9690
9691 <item>
9692 <title>Calling tasksel like the installer, while still getting useful output</title>
9693 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
9694 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
9695 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
9696 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
9697 installs packages during the normal debian-installer run. Until now,
9698 I have ended up letting tasksel do the work, with the annoying problem
9699 of not getting any feedback at all when something fails (like a
9700 conffile question from dpkg or a download that fails), using code like
9701 this:
9702
9703 &lt;blockquote&gt;&lt;pre&gt;
9704 export DEBIAN_FRONTEND=noninteractive
9705 tasksel --new-install
9706 &lt;/pre&gt;&lt;/blockquote&gt;
9707
9708 This would invoke tasksel, let its automatic task selection pick the
9709 tasks to install, and continue to install the requested tasks without
9710 any output what so ever.
9711
9712 Recently I revisited this problem while working on the automatic
9713 package upgrade testing, because tasksel would some times hang without
9714 any useful feedback, and I want to see what is going on when it
9715 happen. Then it occured to me, I can parse the output from tasksel
9716 when asked to run in test mode, and use that aptitude command line
9717 printed by tasksel then to simulate the tasksel run. I ended up using
9718 code like this:
9719
9720 &lt;blockquote&gt;&lt;pre&gt;
9721 export DEBIAN_FRONTEND=noninteractive
9722 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
9723 $cmd
9724 &lt;/pre&gt;&lt;/blockquote&gt;
9725
9726 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
9727 --without-recommends -o APT::Install-Recommends=no -y install
9728 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9729 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
9730 laptop task and all packages with priority standard , required and
9731 important, just like tasksel would have done it during
9732 installation.&lt;/p&gt;
9733
9734 &lt;p&gt;A better approach is probably to extend tasksel to be able to
9735 install packages without using debconf-apt-progress, for use cases
9736 like this.&lt;/p&gt;
9737 </description>
9738 </item>
9739
9740 <item>
9741 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
9742 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
9743 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
9744 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
9745 <description>&lt;p&gt;My
9746 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
9747 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
9748 finally made the upgrade logs available from
9749 &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;.
9750 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9751 apt and aptitude, and found their differences interesting. This time
9752 I will only focus on their removal plans.&lt;/p&gt;
9753
9754 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
9755 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
9756 surprising part is that it want to remove xorg and all
9757 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9758 sure why. When asking aptitude to do the same, it want to remove 129
9759 packages, but most of them are library packages I suspect are no
9760 longer needed. Both of them want to remove bluetooth packages, which
9761 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
9762
9763 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
9764 which seem like a bad idea and xorg the same way as with Gnome. Asking
9765 aptitude for the same, it wants to remove 192 packages, none which are
9766 too surprising.&lt;/p&gt;
9767
9768 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
9769 and avoided, and perhaps others as well. Here are the complete list
9770 of planned removals. The complete logs is available from the URL
9771 above. Note if you want to repeat these tests, that the upgrade test
9772 for kde+apt-get hung in the tasksel setup because of dpkg asking
9773 conffile questions. No idea why. I worked around it by using
9774 &#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
9775 continue.&lt;/p&gt;
9776
9777 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
9778 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
9779 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9780 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
9781 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9782 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9783 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9784 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9785 xserver-xorg-input-kbd xserver-xorg-input-mouse
9786 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9787 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9788 xserver-xorg-video-ati xserver-xorg-video-chips
9789 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9790 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9791 xserver-xorg-video-glint xserver-xorg-video-i128
9792 xserver-xorg-video-i740 xserver-xorg-video-imstt
9793 xserver-xorg-video-intel xserver-xorg-video-mach64
9794 xserver-xorg-video-mga xserver-xorg-video-neomagic
9795 xserver-xorg-video-nsc xserver-xorg-video-nv
9796 xserver-xorg-video-openchrome xserver-xorg-video-r128
9797 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9798 xserver-xorg-video-rendition xserver-xorg-video-s3
9799 xserver-xorg-video-s3virge xserver-xorg-video-savage
9800 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9801 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9802 xserver-xorg-video-tga xserver-xorg-video-trident
9803 xserver-xorg-video-tseng xserver-xorg-video-v4l
9804 xserver-xorg-video-vesa xserver-xorg-video-vga
9805 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
9806 xulrunner-1.9-gnome-support&lt;/p&gt;
9807
9808 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
9809
9810 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
9811 djvulibre-desktop finger gnome-app-install gnome-mount
9812 gnome-network-admin gnome-spell gnome-vfs-obexftp
9813 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9814 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9815 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9816 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
9817 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
9818 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
9819 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
9820 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
9821 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
9822 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
9823 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
9824 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
9825 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9826 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
9827 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
9828 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
9829 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
9830 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
9831 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9832 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9833 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9834 openoffice.org-writer2latex openssl-blacklist p7zip
9835 python-4suite-xml python-eggtrayicon python-gnome2-desktop
9836 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9837 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9838 swfdec-mozilla totem-gstreamer update-manager wodim
9839 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9840 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9841 zip&lt;/p&gt;
9842
9843 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
9844
9845 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9846 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9847 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9848 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9849 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9850 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9851 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9852 xserver-xorg-input-kbd xserver-xorg-input-mouse
9853 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9854 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9855 xserver-xorg-video-ati xserver-xorg-video-chips
9856 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9857 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9858 xserver-xorg-video-glint xserver-xorg-video-i128
9859 xserver-xorg-video-i740 xserver-xorg-video-imstt
9860 xserver-xorg-video-intel xserver-xorg-video-mach64
9861 xserver-xorg-video-mga xserver-xorg-video-neomagic
9862 xserver-xorg-video-nsc xserver-xorg-video-nv
9863 xserver-xorg-video-openchrome xserver-xorg-video-r128
9864 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9865 xserver-xorg-video-rendition xserver-xorg-video-s3
9866 xserver-xorg-video-s3virge xserver-xorg-video-savage
9867 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9868 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9869 xserver-xorg-video-tga xserver-xorg-video-trident
9870 xserver-xorg-video-tseng xserver-xorg-video-v4l
9871 xserver-xorg-video-vesa xserver-xorg-video-vga
9872 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
9873
9874 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
9875 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
9876 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9877 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9878 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9879 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9880 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9881 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9882 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9883 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9884 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9885 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9886 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9887 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9888 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9889 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9890 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9891 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9892 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9893 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
9894 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9895 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9896 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
9897 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9898 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9899 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9900 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9901 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9902 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
9903 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
9904 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9905 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9906 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9907 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9908 texlive-common texlive-doc-base texlive-fonts-recommended
9909 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9910 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9911 xulrunner-1.9&lt;/p&gt;
9912
9913 </description>
9914 </item>
9915
9916 <item>
9917 <title>Automatic upgrade testing from Lenny to Squeeze</title>
9918 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
9919 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
9920 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
9921 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
9922 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9923 have been discovered and reported in the process
9924 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
9925 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
9926 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
9927 kdebase-workspace-data), and to get a more regular testing going on, I
9928 am working on a script to automate the test.&lt;/p&gt;
9929
9930 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
9931 Gnome or KDE desktop installation inside the chroot before upgrading
9932 it. To ensure no services are started in the chroot, a policy-rc.d
9933 script is inserted. To make sure tasksel believe it is to install a
9934 desktop on a laptop, the tasksel tests are replaced in the chroot
9935 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
9936
9937 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9938 currently always fail because udev refuses to upgrade with the kernel
9939 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9940 is created. The bug report
9941 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
9942 this problem do not trigger in a chroot, but I touch the file anyway
9943 to make sure the upgrade go well. Testing on virtual and real
9944 hardware have failed me because of udev so far, and creating this file
9945 do the trick in such settings anyway. This is a
9946 &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
9947 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
9948 maintainer because he lack the resources to rewrite udev to keep
9949 working with old kernels or something like that. I really wish the
9950 udev upstream would keep udev backwards compatible, to avoid such
9951 upgrade problem, but given that they fail to do so, I guess
9952 documenting the way out of this mess is the best option we got for
9953 Debian Squeeze.&lt;/p&gt;
9954
9955 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
9956 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
9957 trick:&lt;/p&gt;
9958
9959 &lt;blockquote&gt;&lt;pre&gt;
9960 #!/bin/sh
9961 set -ex
9962
9963 if [ &quot;$1&quot; ] ; then
9964 desktop=$1
9965 else
9966 desktop=gnome
9967 fi
9968
9969 from=lenny
9970 to=squeeze
9971
9972 exec &amp;lt; /dev/null
9973 unset LANG
9974 mirror=http://ftp.skolelinux.org/debian
9975 tmpdir=chroot-$from-upgrade-$to-$desktop
9976 fuser -mv .
9977 debootstrap $from $tmpdir $mirror
9978 chroot $tmpdir aptitude update
9979 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
9980 #!/bin/sh
9981 exit 101
9982 EOF
9983 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9984 exit_cleanup() {
9985 umount $tmpdir/proc
9986 }
9987 mount -t proc proc $tmpdir/proc
9988 # Make sure proc is unmounted also on failure
9989 trap exit_cleanup EXIT INT
9990
9991 chroot $tmpdir aptitude -y install debconf-utils
9992
9993 # Make sure tasksel autoselection trigger. It need the test scripts
9994 # to return the correct answers.
9995 echo tasksel tasksel/desktop multiselect $desktop | \
9996 chroot $tmpdir debconf-set-selections
9997
9998 # Include the desktop and laptop task
9999 for test in desktop laptop ; do
10000 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
10001 #!/bin/sh
10002 exit 2
10003 EOF
10004 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10005 done
10006
10007 DEBIAN_FRONTEND=noninteractive
10008 DEBIAN_PRIORITY=critical
10009 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10010 chroot $tmpdir tasksel --new-install
10011
10012 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
10013 chroot $tmpdir aptitude update
10014 touch $tmpdir/etc/udev/kernel-upgrade
10015 chroot $tmpdir aptitude -y dist-upgrade
10016 fuser -mv
10017 &lt;/pre&gt;&lt;/blockquote&gt;
10018
10019 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
10020 with aptitude, but I have not had time to look at how they behave
10021 differently so far. I hope to get a cron job running to do the test
10022 regularly and post the result on the web. The Gnome upgrade currently
10023 work, while the KDE upgrade fail because of the bug in
10024 kdebase-workspace-data&lt;/p&gt;
10025
10026 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
10027 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
10028 post, so I will refrain from trying. I can report that for Gnome,
10029 aptitude report 760 packages upgraded, 448 newly installed, 129 to
10030 remove and 1 not upgraded and 1024MB need to be downloaded while for
10031 KDE the same numbers are 702 packages upgraded, 507 newly installed,
10032 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
10033
10034 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
10035 is able to migrate to dependency based boot sequencing and parallel
10036 booting without a hitch. Was unsure if there were still bugs with
10037 packages failing to clean up their obsolete init.d script during
10038 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10039 packages.&lt;/p&gt;
10040 </description>
10041 </item>
10042
10043 <item>
10044 <title>Upstart or sysvinit - as init.d scripts see it</title>
10045 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
10046 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
10047 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
10048 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
10049 scripts to migrate (some of) their operations to upstart job while
10050 keeping the init.d for hurd and kfreebsd. The packages with such
10051 needs will need a way to get their init.d scripts to behave
10052 differently when used with sysvinit and with upstart. Because of
10053 this, I had a look at the environment variables set when a init.d
10054 script is running under upstart, and when it is not.&lt;/p&gt;
10055
10056 &lt;p&gt;With upstart, I notice these environment variables are set when a
10057 script is started from rcS.d/ (ignoring some irrelevant ones like
10058 COLUMNS):&lt;/p&gt;
10059
10060 &lt;blockquote&gt;&lt;pre&gt;
10061 DEFAULT_RUNLEVEL=2
10062 previous=N
10063 PREVLEVEL=
10064 RUNLEVEL=
10065 runlevel=S
10066 UPSTART_EVENTS=startup
10067 UPSTART_INSTANCE=
10068 UPSTART_JOB=rc-sysinit
10069 &lt;/pre&gt;&lt;/blockquote&gt;
10070
10071 &lt;p&gt;With sysvinit, these environment variables are set for the same
10072 script.&lt;/p&gt;
10073
10074 &lt;blockquote&gt;&lt;pre&gt;
10075 INIT_VERSION=sysvinit-2.88
10076 previous=N
10077 PREVLEVEL=N
10078 RUNLEVEL=S
10079 runlevel=S
10080 &lt;/pre&gt;&lt;/blockquote&gt;
10081
10082 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
10083 sysvinit are not set by upstart. Not sure if it is intentional or not
10084 to not be compatible with sysvinit in this regard.&lt;/p&gt;
10085
10086 &lt;p&gt;For scripts needing to behave differently when upstart is used,
10087 looking for the UPSTART_JOB environment variable seem to be a good
10088 choice.&lt;/p&gt;
10089 </description>
10090 </item>
10091
10092 <item>
10093 <title>A manual for standards wars...</title>
10094 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
10095 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
10096 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
10097 <description>&lt;p&gt;Via the
10098 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
10099 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
10100 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
10101 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
10102 following the standards wars of today.&lt;/p&gt;
10103 </description>
10104 </item>
10105
10106 <item>
10107 <title>Sitesummary tip: Listing computer hardware models used at site</title>
10108 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
10109 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
10110 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
10111 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
10112 to get a list of the machine types in use thanks to the DMI
10113 information extracted from each machine. The script to do so is
10114 included in the sitesummary package, and here is example output from
10115 the Skolelinux build servers:&lt;/p&gt;
10116
10117 &lt;blockquote&gt;&lt;pre&gt;
10118 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10119 vendor count
10120 Dell Computer Corporation 1
10121 PowerEdge 1750 1
10122 IBM 1
10123 eserver xSeries 345 -[8670M1X]- 1
10124 Intel 2
10125 [no-dmi-info] 3
10126 maintainer:~#
10127 &lt;/pre&gt;&lt;/blockquote&gt;
10128
10129 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
10130 provided in each machine. Here there are Intel machines without model
10131 information listed with Intel as vendor and no model, and virtual Xen
10132 machines listed as [no-dmi-info]. One can add -l as a command line
10133 option to list the individual machines.&lt;/p&gt;
10134
10135 &lt;p&gt;A larger list is
10136 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
10137 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
10138 provide the basic sitesummary report publicly. In their report there
10139 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
10140 their machines, and as sitesummary is available in both distributions,
10141 it is trivial to get all of them to report to the same central
10142 collector.&lt;/p&gt;
10143 </description>
10144 </item>
10145
10146 <item>
10147 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
10148 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
10149 <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>
10150 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
10151 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
10152 start at boot when an NVidia video card is used is handled. The
10153 problem seem to be that the nvidia X.org driver uses a long time to
10154 initialize, and this duration is longer than kdm is configured to
10155 wait.&lt;/p&gt;
10156
10157 &lt;p&gt;I came across two bugs related to this issue,
10158 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
10159 against initscripts and passed on to nvidia-glx when it became obvious
10160 that the nvidia drivers were involved, and
10161 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
10162 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
10163
10164 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
10165 problem nvidia video card owners experience and make sure the Debian
10166 distribution work out of the box for these users. The nvidia driver
10167 maintainers expect kdm to be set up to wait longer, while kdm expect
10168 the nvidia driver maintainers to fix the driver to start faster, and
10169 while they wait for each other I guess the users end up switching to a
10170 distribution that work for them. I have no idea what the solution is,
10171 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
10172
10173 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
10174 </description>
10175 </item>
10176
10177 <item>
10178 <title>Parallellized boot seem to hold up well in Debian/testing</title>
10179 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
10180 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
10181 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
10182 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
10183 The feature seem to hold up pretty well, but three fairly serious
10184 issues are known and should be solved:
10185
10186 &lt;p&gt;&lt;ul&gt;
10187
10188 &lt;li&gt;The wicd package seen to
10189 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
10190 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
10191 parallel booting is enabled. No idea why, but the wicd maintainer
10192 seem to be on the case.&lt;/li&gt;
10193
10194 &lt;li&gt;The nvidia X driver seem to
10195 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
10196 triggered more easily when parallel booting is in effect. The
10197 maintainer is on the case.&lt;/li&gt;
10198
10199 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
10200 sequencing (the shutdown is broken) when old file-rc users
10201 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
10202 sysv-rc. One way to solve it would be for file-rc to create
10203 /etc/init.d/.legacy-bootordering, and another is to try to make
10204 sysv-rc more robust. Will investigate some more and probably upload a
10205 workaround in sysv-rc to help those trying to move from file-rc to
10206 sysv-rc get a working shutdown.&lt;/li&gt;
10207
10208 &lt;/ul&gt;&lt;/p&gt;
10209
10210 &lt;p&gt;All in all not many surprising issues, and all of them seem
10211 solvable before Squeeze is released. In addition to these there are
10212 some packages with bugs in their dependencies and run level settings,
10213 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
10214
10215 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10216 the BTS, please usertag the report to get it to show up at
10217 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10218 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10219
10220 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
10221 </description>
10222 </item>
10223
10224 <item>
10225 <title>More flexible firmware handling in debian-installer</title>
10226 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
10227 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
10228 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
10229 <description>&lt;p&gt;After a long break from debian-installer development, I finally
10230 found time today to return to the project. Having to spend less time
10231 working dependency based boot in debian, as it is almost complete now,
10232 definitely helped freeing some time.&lt;/p&gt;
10233
10234 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
10235 include some firmware packages on the Debian Edu CDs, those needed to
10236 get disk and network controllers working. Without having these
10237 firmware packages available during installation, it is impossible to
10238 install Debian Edu on the given machine, and because our target group
10239 are non-technical people, asking them to provide firmware packages on
10240 an external medium is a support pain. Initially, I expected it to be
10241 enough to include the firmware packages on the CD to get
10242 debian-installer to find and use them. This proved to be wrong.
10243 Next, I hoped it was enough to symlink the relevant firmware packages
10244 to some useful location on the CD (tried /cdrom/ and
10245 /cdrom/firmware/). This also proved to not work, and at this point I
10246 found time to look at the debian-installer code to figure out what was
10247 going to work.&lt;/p&gt;
10248
10249 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
10250 look revealed that it would only look for firmware packages outside
10251 the installation media, so the CD was never checked for firmware
10252 packages. It would only check USB sticks, floppies and other
10253 &quot;external&quot; media devices. Today I changed it to also look in the
10254 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10255 solve the problem I ran into with Debian edu. I also changed it to
10256 look in /firmware/, to make sure the installer also find firmware
10257 provided in the initrd when booting the installer via PXE, to allow us
10258 to provide the same feature in the PXE setup included in Debian
10259 Edu.&lt;/p&gt;
10260
10261 &lt;p&gt;To make sure firmware deb packages with a license questions are not
10262 activated without asking if the license is accepted, I extended
10263 hw-detect to look for preinst scripts in the firmware packages, and
10264 run these before activating the firmware during installation. The
10265 license question is asked using debconf in the preinst, so this should
10266 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
10267
10268 &lt;p&gt;If you want to discuss the details of these features, please
10269 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
10270 </description>
10271 </item>
10272
10273 <item>
10274 <title>Parallellized boot is now the default in Debian/unstable</title>
10275 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
10276 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
10277 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
10278 <description>&lt;p&gt;Since this evening, parallel booting is the default in
10279 Debian/unstable for machines using dependency based boot sequencing.
10280 Apparently the testing of concurrent booting has been wider than
10281 expected, if I am to believe the
10282 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
10283 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
10284 with the feature this weekend, to give us some time to detect any
10285 remaining problems before Squeeze is frozen. If serious problems are
10286 detected, it is simple to change the default back to sequential boot.
10287 The upload of the new sysvinit package also activate a new upstream
10288 version.&lt;/p&gt;
10289
10290 More information about
10291 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
10292 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
10293 currently possible to disable parallel booting when one run into
10294 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
10295
10296 &lt;blockquote&gt;&lt;pre&gt;
10297 CONCURRENCY=none
10298 &lt;/pre&gt;&lt;/blockquote&gt;
10299
10300 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10301 the BTS, please usertag the report to get it to show up at
10302 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10303 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10304 </description>
10305 </item>
10306
10307 <item>
10308 <title>Sitesummary tip: Listing MAC address of all clients</title>
10309 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
10310 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
10311 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
10312 <description>&lt;p&gt;In the recent Debian Edu versions, the
10313 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
10314 system&lt;/a&gt; is used to keep track of the machines in the school
10315 network. Each machine will automatically report its status to the
10316 central server after boot and once per night. The network setup is
10317 also reported, and using this information it is possible to get the
10318 MAC address of all network interfaces in the machines. This is useful
10319 to update the DHCP configuration.&lt;/p&gt;
10320
10321 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
10322 ist all MAC addresses of all machines reporting to sitesummary. Run
10323 this on the collector host:&lt;/p&gt;
10324
10325 &lt;blockquote&gt;&lt;pre&gt;
10326 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
10327 &lt;/pre&gt;&lt;/blockquote&gt;
10328
10329 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
10330 line per machine and with space between the MAC addresses.&lt;/p&gt;
10331
10332 &lt;p&gt;To allow system administrators easier job at adding static DHCP
10333 addresses for hosts, it would be possible to extend this to fetch
10334 machine information from sitesummary and update the DHCP and DNS
10335 tables in LDAP using this information. Such tool is unfortunately not
10336 written yet.&lt;/p&gt;
10337 </description>
10338 </item>
10339
10340 <item>
10341 <title>systemd, an interesting alternative to upstart</title>
10342 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
10343 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
10344 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
10345 <description>&lt;p&gt;The last few days a new boot system called
10346 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
10347 has been
10348 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
10349
10350 to the free software world. I have not yet had time to play around
10351 with it, but it seem to be a very interesting alternative to
10352 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
10353 a good alternative for Debian when we are able to switch to an event
10354 based boot system. Tollef is
10355 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
10356 systemd into Debian, and I look forward to seeing how well it work. I
10357 like the fact that systemd handles init.d scripts with dependency
10358 information natively, allowing them to run in parallel where upstart
10359 at the moment do not.&lt;/p&gt;
10360
10361 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
10362 platform support. It only work on recent Linux kernels, and also need
10363 some new kernel features enabled to function properly. This means
10364 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10365 system. Not sure how that will be handled if systemd proves to be the
10366 way forward.&lt;/p&gt;
10367
10368 &lt;p&gt;In the mean time, based on the
10369 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
10370 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
10371 decided to enable full parallel booting as the default in Debian as
10372 soon as possible (probably this weekend or early next week), to see if
10373 there are any remaining serious bugs in the init.d dependencies. A
10374 new version of the sysvinit package implementing this change is
10375 already in experimental. If all go well, Squeeze will be released
10376 with parallel booting enabled by default.&lt;/p&gt;
10377 </description>
10378 </item>
10379
10380 <item>
10381 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
10382 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
10383 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
10384 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
10385 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
10386 complete, so complete that it is actually possible to run all the
10387 init.d scripts in parallell based on these dependencies. If you want
10388 to test your Squeeze system, make sure
10389 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
10390 based boot sequencing&lt;/a&gt; is enabled, and add this line to
10391 /etc/default/rcS:&lt;/p&gt;
10392
10393 &lt;blockquote&gt;&lt;pre&gt;
10394 CONCURRENCY=makefile
10395 &lt;/pre&gt;&lt;/blockquote&gt;
10396
10397 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
10398 scripts in parallel using the dependency information stored in
10399 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10400 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10401 to try to start the kdm and gdm scripts as early as possible, and will
10402 start the facilities required by kdm or gdm as early as possible to
10403 make this happen.&lt;/p&gt;
10404
10405 &lt;p&gt;Give it a try, and see if you like the result. If some services
10406 fail to start properly, it is most likely because they have incomplete
10407 init.d script dependencies in their startup script (or some of their
10408 dependent scripts have incomplete dependencies). Report bugs and get
10409 the package maintainers to fix it. :)&lt;/p&gt;
10410
10411 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
10412 manage to get the init.d script dependencies complete and correct. I
10413 expect we will get there in Squeeze+1, if we get manage to test and
10414 fix the remaining issues.&lt;/p&gt;
10415
10416 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10417 the BTS, please usertag the report to get it to show up at
10418 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10419 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10420 </description>
10421 </item>
10422
10423 <item>
10424 <title>Debian has switched to dependency based boot sequencing</title>
10425 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
10426 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
10427 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
10428 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
10429 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
10430 have been migrated to using dependency based boot sequencing. This
10431 conclude work me and others have been doing for the last three days.
10432 It feels great to see this finally part of the default Debian
10433 installation. Now we just need to weed out the last few problems that
10434 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
10435
10436 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
10437 fixing the more fundamental problem of handing the event based
10438 non-predictable kernel in the early boot.&lt;/p&gt;
10439 </description>
10440 </item>
10441
10442 <item>
10443 <title>Taking over sysvinit development</title>
10444 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
10445 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
10446 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
10447 <description>&lt;p&gt;After several years of frustration with the lack of activity from
10448 the existing sysvinit upstream developer, I decided a few weeks ago to
10449 take over the package and become the new upstream. The number of
10450 patches to track for the Debian package was becoming a burden, and the
10451 lack of synchronization between the distribution made it hard to keep
10452 the package up to date.&lt;/p&gt;
10453
10454 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10455 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
10456 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
10457 and Fedora), based on the patches currently in use in these
10458 distributions. We Debian maintainers plan to move to this tarball as
10459 the new upstream as soon as we find time to do the merge. Since the
10460 new tarball was created, we agreed with Werner at SuSe to make a new
10461 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
10462 development there. The project is registered and currently waiting
10463 for approval by the Savannah administrators, and as soon as it is
10464 approved, we will import the old versions from svn and continue
10465 working on the future release.&lt;/p&gt;
10466
10467 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
10468 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
10469 </description>
10470 </item>
10471
10472 <item>
10473 <title>Debian boots quicker and quicker</title>
10474 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
10475 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
10476 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
10477 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
10478 people involved in the boot system on Debian and Ubuntu, to see if we
10479 could find more ways to speed up the boot system. This was an Ubuntu
10480 funded
10481 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
10482 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
10483 of boot systems, and ways to handle the increasing number of boot
10484 issues introduced by the Linux kernel becoming more and more
10485 asynchronous and event base. The Ubuntu approach using udev and
10486 upstart might be a good way forward. Time will show.&lt;/p&gt;
10487
10488 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
10489 process in Debian. All of these should be applied to get a quick
10490 boot:&lt;/p&gt;
10491
10492 &lt;ul&gt;
10493
10494 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
10495
10496 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
10497 clock is in UTC.&lt;/li&gt;
10498
10499 &lt;li&gt;Install and activate the insserv package to enable
10500 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
10501 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
10502
10503 &lt;/ul&gt;
10504
10505 These points are based on the Google summer of code work done by
10506 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
10507 Villegas&lt;/a&gt;.
10508
10509 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
10510 unstable yesterday. When we tested it, we were able to cut 6 seconds
10511 from the boot sequence. It depend on very correct dependency
10512 declaration in all init.d scripts, so I expect us to find edge cases
10513 where the dependences in some scripts are slightly wrong when we start
10514 using this.&lt;/p&gt;
10515
10516 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10517 introduced by Raphael Geissert today, one that could affect the
10518 startup speed as well. Instead of starting some scripts concurrently
10519 from rcS.d/ and another set of scripts from rc2.d/, it would be
10520 possible to run a of them in the same process. A quick way to test
10521 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
10522 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
10523 </description>
10524 </item>
10525
10526 <item>
10527 <title>BSAs påstander om piratkopiering møter motstand</title>
10528 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
10529 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
10530 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
10531 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
10532 programvareselskapene som Microsoft og Apple, publisert en rapport der
10533 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10534 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10535 dager siden kom
10536 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
10537 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
10538 dagene. Et spesielt interessant kommentar fra Sverige,
10539 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
10540 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
10541
10542 &lt;blockquote&gt;
10543 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
10544 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10545 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
10546 exakta&quot;, säger BSAs Sverigechef John Hugosson.
10547 &lt;/blockquote&gt;
10548
10549 &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
10550 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
10551 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
10552 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
10553 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
10554
10555 &lt;p&gt;Fant lenkene via &lt;a
10556 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
10557 på Slashdot&lt;/a&gt;.&lt;/p&gt;
10558 </description>
10559 </item>
10560
10561 <item>
10562 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
10563 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
10564 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
10565 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
10566 <description>&lt;p&gt;Kom over
10567 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
10568 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10569 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10570 jobber til daglig. En rask opptelling forteller meg at vi har 490
10571 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
10572 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
10573 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
10574 </description>
10575 </item>
10576
10577 <item>
10578 <title>Kryptert harddisk - naturligvis</title>
10579 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
10580 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
10581 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
10582 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
10583 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
10584 når en tar tap av arbeidstid, fortrolige dokumenter,
10585 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10586 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10587 til at jeg har kryptert harddisken på både kontormaskinen og min
10588 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10589 komme på avveie, den første informasjon relatert til jobben min ved
10590 Universitetet i Oslo, og den andre relatert til blant annet
10591 foreningsarbeide. Kryptering av diskene gjør at det er lite
10592 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10593 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10594 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10595 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10596 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10597 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10598 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10599 det er gjort slik jeg gjør det er minimale, og gevinstene er
10600 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10601 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
10602
10603 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10604 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10605 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10606 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10607 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10608 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10609 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10610 betydelige.&lt;/p&gt;
10611 </description>
10612 </item>
10613
10614 <item>
10615 <title>Two projects that have improved the quality of free software a lot</title>
10616 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
10617 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
10618 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
10619 <description>&lt;p&gt;There are two software projects that have had huge influence on the
10620 quality of free software, and I wanted to mention both in case someone
10621 do not yet know them.&lt;/p&gt;
10622
10623 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
10624 tool to detect and expose errors in the memory handling of programs.
10625 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
10626 and it will report any problems on stdout. It is even better if the
10627 program include debug information. With debug information, it is able
10628 to report the source file name and line number where the problem
10629 occurs. It can report things like &#39;reading past memory block in file
10630 X line N, the memory block was allocated in file Y, line M&#39;, and
10631 &#39;using uninitialised value in control logic&#39;. This tool has made it
10632 trivial to investigate reproducible crash bugs in programs, and have
10633 reduced the number of this kind of bugs in free software a lot.
10634
10635 &lt;p&gt;The second one is
10636 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
10637 a source code checker. It is able to process the source of a program
10638 and find problems in the logic without running the program. It
10639 started out as the Stanford Checker and became well known when it was
10640 used to find bugs in the Linux kernel. It is now a commercial tool
10641 and the company behind it is running
10642 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
10643 free software community, where a lot of free software projects get
10644 their source checked for free. Several thousand defects have been
10645 found and fixed so far. It can find errors like &#39;lock L taken in file
10646 X line N is never released if exiting in line M&#39;, or &#39;the code in file
10647 Y lines O to P can never be executed&#39;. The projects included in the
10648 community service project have managed to get rid of a lot of
10649 reliability problems thanks to Coverity.&lt;/p&gt;
10650
10651 &lt;p&gt;I believe tools like this, that are able to automatically find
10652 errors in the source, are vital to improve the quality of software and
10653 make sure we can get rid of the crashing and failing software we are
10654 surrounded by today.&lt;/p&gt;
10655 </description>
10656 </item>
10657
10658 <item>
10659 <title>No patch is not better than a useless patch</title>
10660 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
10661 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
10662 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
10663 <description>&lt;p&gt;Julien Blache
10664 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
10665 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
10666 patch allow one to discuss a concrete and proposed solution, and also
10667 prove that the issue at hand is important enough for someone to spent
10668 time on fixing it. No patch do not provide any of these positive
10669 properties.&lt;/p&gt;
10670 </description>
10671 </item>
10672
10673 <item>
10674 <title>Standardize on protocols and formats, not vendors and applications</title>
10675 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
10676 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
10677 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
10678 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
10679 very good one to form a long lived computer infrastructure. It is the
10680 simple one, lost by many in todays computer industry: Standardize on
10681 open network protocols and open exchange/storage formats, not applications.
10682 Applications come and go, while protocols and files tend to stay, and
10683 thus one want to make it easy to change application and vendor, while
10684 avoiding conversion costs and locking users to a specific platform or
10685 application.&lt;/p&gt;
10686
10687 &lt;p&gt;This approach make it possible to replace the client applications
10688 independently of the server applications. One can even allow users to
10689 use several different applications as long as they handle the selected
10690 protocol and format. In the normal case, only one client application
10691 is recommended and users only get help if they choose to use this
10692 application, but those that want to deviate from the easy path are not
10693 blocked from doing so.&lt;/p&gt;
10694
10695 &lt;p&gt;It also allow us to replace the server side without forcing the
10696 users to replace their applications, and thus allow us to select the
10697 best server implementation at any moment, when scale and resouce
10698 requirements change.&lt;/p&gt;
10699
10700 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
10701 open formats, but I would never recommend standardizing on a single
10702 application that do not use open network protocol or open formats.&lt;/p&gt;
10703 </description>
10704 </item>
10705
10706 <item>
10707 <title>Returning from Skolelinux developer gathering</title>
10708 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
10709 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
10710 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
10711 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
10712 Edu/Skolelinux development gathering. I got a bit done tuning the
10713 desktop, and looked into the dynamic service location protocol
10714 implementation avahi. It look like it could be useful for us. Almost
10715 30 people participated, and I believe it was a great environment to
10716 get to know the Skolelinux system. Walter Bender, involved in the
10717 development of the Sugar educational platform, presented his stuff and
10718 also helped me improve my OLPC installation. He also showed me that
10719 his Turtle Art application can be used in standalone mode, and we
10720 agreed that I would help getting it packaged for Debian. As a
10721 standalone application it would be great for Debian Edu. We also
10722 tried to get the video conferencing working with two OLPCs, but that
10723 proved to be too hard for us. The application seem to need more work
10724 before it is ready for me. I look forward to getting home and relax
10725 now. :)&lt;/p&gt;
10726 </description>
10727 </item>
10728
10729 <item>
10730 <title>Time for new LDAP schemas replacing RFC 2307?</title>
10731 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
10732 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
10733 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
10734 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
10735 optimal. There is RFC 2307 documenting one way to store NIS maps in
10736 LDAP, and a modified version of this normally called RFC 2307bis, with
10737 some modifications to be compatible with Active Directory. The RFC
10738 specification handle the content of a lot of system databases, but do
10739 not handle DNS zones and DHCP configuration.&lt;/p&gt;
10740
10741 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
10742 we would like to store information about users, SMB clients/hosts,
10743 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10744 and LTSP configuration in LDAP. These objects have a lot in common,
10745 but with the current LDAP schemas it is not possible to have one
10746 object per entity. For example, one need to have at least three LDAP
10747 objects for a given computer, one with the SMB related stuff, one with
10748 DNS information and another with DHCP information. The schemas
10749 provided for DNS and DHCP are impossible to combine into one LDAP
10750 object. In addition, it is impossible to implement quick queries for
10751 netgroup membership, because of the way NIS triples are implemented.
10752 It just do not scale. I believe it is time for a few RFC
10753 specifications to cleam up this mess.&lt;/p&gt;
10754
10755 &lt;p&gt;I would like to have one LDAP object representing each computer in
10756 the network, and this object can then keep the SMB (ie host key), DHCP
10757 (mac address/name) and DNS (name/IP address) settings in one place.
10758 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
10759
10760 &lt;p&gt;I would also like to have a quick way to map from a user or
10761 computer and to the net group this user or computer is a member.&lt;/p&gt;
10762
10763 &lt;p&gt;Active Directory have done a better job than unix heads like myself
10764 in this regard, and the unix side need to catch up. Time to start a
10765 new IETF work group?&lt;/p&gt;
10766 </description>
10767 </item>
10768
10769 <item>
10770 <title>Endelig er Debian Lenny gitt ut</title>
10771 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
10772 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
10773 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
10774 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
10775 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
10776 Et langt steg videre for Debian-prosjektet, og en rekke nye
10777 programpakker blir nå tilgjengelig for de av oss som bruker den
10778 stabile utgaven av Debian. Neste steg er nå å få
10779 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
10780 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
10781 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10782 slippes løs på skolene. Takk til alle debian-utviklerne som har
10783 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10784 bootsekvens tilgjengelig i stabil utgave, vha pakken
10785 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
10786 </description>
10787 </item>
10788
10789 <item>
10790 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
10791 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
10792 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
10793 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
10794 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
10795 Oslo. Most of Saturday was used for the general assemly for the
10796 member organization, but the rest of the weekend I used to tune the
10797 LTSP installation. LTSP now work out of the box on the 10-network.
10798 Acer Aspire One proved to be a very nice thin client, with both
10799 screen, mouse and keybard in a small box. Was working on getting the
10800 diskless workstation setup configured out of the box, but did not
10801 finish it before the weekend was up.&lt;/p&gt;
10802
10803 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
10804 the Brazilian group, so that will have to wait for the next
10805 development gathering. Would love to have the Debian Edu installer
10806 automatically detect and configure a multiseat setup when it find one
10807 of these cards.&lt;/p&gt;
10808 </description>
10809 </item>
10810
10811 <item>
10812 <title>The sorry state of multimedia browser plugins in Debian</title>
10813 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
10814 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
10815 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
10816 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
10817 plugins available in Debian Lenny, to see which one we should use by
10818 default in Debian Edu. We need an embedded video playing plugin with
10819 control buttons to pause or stop the video, and capable of streaming
10820 all the multimedia content available on the web. The test results and
10821 notes are available on
10822 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
10823 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
10824 fill this need. My personal video player favorite, VLC, has a really
10825 bad plugin which fail on a lot of the test pages. A lot of the MIME
10826 types I would expect to work with any free software player (like
10827 video/ogg), just do not work. And simple formats like the
10828 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
10829 totem and vlc plugins. I hope the situation will improve soon. No
10830 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
10831
10832 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
10833 be the only one fitting our needs. :/&lt;/p&gt;
10834 </description>
10835 </item>
10836
10837 </channel>
10838 </rss>