]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
27e0e3130c42edad34824b65d5064bc20a439d85
[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>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
11 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
13 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
14 <description>&lt;p&gt;A new version of the
15 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
16 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
17 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
18 useful. It was uploaded the last few days, and the last update will
19 enter testing tomorrow. See the
20 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
21 notes&lt;/a&gt; for the list of bug fixes and new features.&lt;/p&gt; Version 3.2
22 was announced 6 days ago. We will try to get it into Debian as
23 well.&lt;/p&gt;
24
25 &lt;p&gt;More information related to 3D printing is available on the
26 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
27 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
28 in Debian.&lt;/p&gt;
29
30 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
31 activities, please send Bitcoin donations to my address
32 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
33 </description>
34 </item>
35
36 <item>
37 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
38 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
39 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
40 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
41 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
42 that the nice and user friendly 3D printer slicer software Cura just
43 entered Debian Unstable. It consist of five packages,
44 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
45 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
46 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
47 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
48 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
49 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
50 two, uranium and cura, entered Unstable yesterday. This should make
51 it easier for Debian users to print on at least the Ultimaker class of
52 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
53 make life easier for at least me. :)&lt;/p&gt;
54
55 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
56 happy to assist him in sponsoring the packages. With the introduction
57 of Cura, Debian is up to three 3D printer slicers at your service,
58 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
59 printer, give it a go. :)&lt;/p&gt;
60
61 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
62 team, flocking together on the
63 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
64 mailing list and the
65 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
66 IRC channel.&lt;/p&gt;
67
68 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
69 version 3.0.3 and then update the entire set of packages to version
70 3.1.0 which showed up the last few days.&lt;/p&gt;
71 </description>
72 </item>
73
74 <item>
75 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
76 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
77 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
78 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
79 <description>&lt;p&gt;At my nearby maker space,
80 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
81 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
82 on Windows and MacOS X than Linux, because the software involved had
83 to be manually compiled and set up on Linux while premade packages
84 worked out of the box on Windows and MacOS X. I found this annoying,
85 as the software involved,
86 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
87 and should be trivial to get up and running on Linux if someone took
88 the time to package it for the relevant distributions. I even found
89 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
90 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
91 never resulted in the software showing up in Debian. So a few days
92 ago I offered my help to try to improve the situation.&lt;/p&gt;
93
94 &lt;p&gt;Now I am very happy to see that all the packages required by a
95 working Cura in Debian are uploaded into Debian and waiting in the NEW
96 queue for the ftpmasters to have a look. You can track the progress
97 on
98 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
99 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
100
101 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
102 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
103 queue&lt;/a&gt; while we work up updating the packages to the latest
104 upstream version.&lt;/p&gt;
105
106 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
107 to use and was unable to configure correctly for Ultimaker 2+ in the
108 short time I spent on it, are already in Debian. If you are looking
109 for 3D printer &quot;slicers&quot; and want something already available in
110 Debian, check out
111 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
112 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
113 The latter is a fork of the former.&lt;/p&gt;
114
115 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
116 activities, please send Bitcoin donations to my address
117 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
118 </description>
119 </item>
120
121 <item>
122 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
123 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
124 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
125 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
126 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
127 mobile cell towers. And this radio chatter is available for anyone
128 with a radio receiver capable of receiving them. Details about the
129 mobile phones with very good accuracy is of course collected by the
130 phone companies, but this is not the topic of this blog post. The
131 mobile phone radio chatter make it possible to figure out when a cell
132 phone is nearby, as it include the SIM card ID (IMSI). By paying
133 attention over time, one can see when a phone arrive and when it leave
134 an area. I believe it would be nice to make this information more
135 available to the general public, to make more people aware of how
136 their phones are announcing their whereabouts to anyone that care to
137 listen.&lt;/p&gt;
138
139 &lt;p&gt;I am very happy to report that we managed to get something
140 visualizing this information up and running for
141 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
142 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
143 library. The solution is based on the
144 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
145 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
146 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
147 Sone from the Computer Science department of the University of
148 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
149 IMSIs) as dots in a web browser graph, with lines to the dot
150 representing mobile base station it is talking to. It was working in
151 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
152
153 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
154 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
155 connected and visualize the visible cell phone towers using an
156 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
157 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
158 grgsm_livemon_headless processes from
159 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
160 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
161
162 &lt;p&gt;The frequencies to listen to, are identified using a slightly
163 patched scan-and-livemon (to set the --args values for each receiver),
164 and the Hopglass data is generated using the
165 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
166 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
167 more than four SDRs working. There is also a geographical map trying
168 to show the location of the base stations, but I believe their
169 coordinates are hardcoded to some random location in Germany, I
170 believe. The code should be replaced with code to look up location in
171 a text file, a sqlite database or one of the online databases
172 mentioned in
173 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
174 issue for the topic&lt;/a&gt;.
175
176 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
177 </description>
178 </item>
179
180 <item>
181 <title>Easier recipe to observe the cell phones around you</title>
182 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
183 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
184 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
185 <description>&lt;p&gt;A little more than a month ago I wrote
186 &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
187 to observe the SIM card ID (aka IMSI number) of mobile phones talking
188 to nearby mobile phone base stations using Debian GNU/Linux and a
189 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
190 the location of people and equipment (like cars and trains) with an
191 accuracy of a few kilometer. Since then we have worked to make the
192 procedure even simpler, and it is now possible to do this without any
193 manual frequency tuning and without building your own packages.&lt;/p&gt;
194
195 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
196 package is now included in Debian testing and unstable, and the
197 IMSI-catcher code no longer require root access to fetch and decode
198 the GSM data collected using gr-gsm.&lt;/p&gt;
199
200 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
201 clone of two python scripts:&lt;/p&gt;
202
203 &lt;ol&gt;
204
205 &lt;li&gt;Start with a Debian machine running the Buster version (aka
206 testing).&lt;/li&gt;
207
208 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
209 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
210
211 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
212 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
213
214 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
215
216 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
217 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
218 stations and start listening for GSM packages on one of them.&lt;/li&gt;
219
220 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
221 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
222
223 &lt;/ol&gt;
224
225 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
226 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
227 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
228 work with RTL 8232 and other similar USB radio receivers you can get
229 very cheaply
230 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
231 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
232 and only use HackRF for fetching GSM data.&lt;/p&gt;
233
234 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
235 frequencies at the time, so if you are going to track and count every
236 cell phone around you, you need to listen to all the frequencies used.
237 To listen to several frequencies, use the --numrecv argument to
238 scan-and-livemon to use several receivers. Further, I am not sure if
239 phones using 3G or 4G will show as talking GSM to base stations, so
240 this approach might not see all phones around you. I typically see
241 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
242
243 &lt;p&gt;I&#39;ve tried to run the scanner on a
244 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
245 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
246 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
247 stdout, I am told there it is caused by a buffer overflow between the
248 radio and GNU Radio, caused by the program being unable to read the
249 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
250 where you started scan-and-livemon, you need a give the process more
251 CPU power. Perhaps someone are able to optimize the code to a point
252 where it become possible to set up RPi3 based GSM sniffers? I tried
253 using Raspbian instead of Debian, but there seem to be something wrong
254 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
255 </description>
256 </item>
257
258 <item>
259 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
260 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
261 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
262 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
263 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
264 web based ICT news magazine digi.no on
265 &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
266 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
267 DVB-T software defined radios. The article refered to instructions
268 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
269 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;
270
271 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
272 bypass apt), use pip to install pybombs (to bypass both apt and pip),
273 and the ask pybombs to fetch and build everything you need from
274 scratch. I wanted to see if I could do the same on the most recent
275 Debian packages, but this did not work because pybombs tried to build
276 stuff that no longer build with the most recent openssl library or
277 some other version skew problem. While trying to get this recipe
278 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
279 and the only piece of software dependency missing in Debian was the
280 gr-gsm package. I also found out that the lead upstream developer of
281 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
282 Debian packages provided in an Ubuntu PPA repository. All I needed to
283 do was to dget the Debian source package and built it.&lt;/p&gt;
284
285 &lt;p&gt;The IMSI collector is a python script listening for packages on the
286 loopback network device and printing to the terminal some specific GSM
287 packages with IMSI numbers in them. The code is fairly short and easy
288 to understand. The reason this work is because gr-gsm include a tool
289 to read GSM data from a software defined radio like a DVB-T USB stick
290 and other software defined radios, decode them and inject them into a
291 network device on your Linux machine (using the loopback device by
292 default). This proved to work just fine, and I&#39;ve been testing the
293 collector for a few days now.&lt;/p&gt;
294
295 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
296
297 &lt;ol&gt;
298
299 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
300
301 &lt;li&gt;build and install the gr-gsm package available from
302 &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;
303
304 &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;
305
306 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
307 where it was started is filled with a stream of text (meaning you
308 found a GSM station).&lt;/li&gt;
309
310 &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;
311
312 &lt;/ol&gt;
313
314 &lt;p&gt;To make it even easier in the future to get this sniffer up and
315 running, I decided to package
316 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
317 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
318 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
319 Luckily the gnuradio maintainer has promised to help me, as I do not
320 know much about gnuradio stuff yet.&lt;/p&gt;
321
322 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
323 commercial tools like
324 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
325 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
326 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
327 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
328 more people realise how their whereabouts when carrying a cell phone
329 is easily tracked. Seeing the data flow on the screen, realizing that
330 I live close to a police station and knowing that the police is also
331 wearing cell phones, I wonder how hard it would be for criminals to
332 track the position of the police officers to discover when there are
333 police near by, or for foreign military forces to track the location
334 of the Norwegian military forces, or for anyone to track the location
335 of government officials...&lt;/p&gt;
336
337 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
338 script mentioned above is only a fraction of the data broadcasted on
339 the GSM network. It will only collect one frequency at the time,
340 while a typical phone will be using several frequencies, and not all
341 phones will be using the frequencies tracked by the grgsm_livemod
342 program. Also, there is a lot of radio chatter being ignored by the
343 simple_IMSI-catcher script, which would be collected by extending the
344 parser code. I wonder if gr-gsm can be set up to listen to more than
345 one frequency?&lt;/p&gt;
346 </description>
347 </item>
348
349 <item>
350 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
351 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
352 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
353 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
354 <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;
355
356 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
357 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
358 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
359 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
360 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
361 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
362 price. The book is also available for download in electronic form as
363 PDF, EPUB and Mobipocket, as can be
364 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
365 as a web page&lt;/a&gt;.&lt;/p&gt;
366
367 &lt;p&gt;This is the second book I publish (the first was the book
368 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
369 in
370 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
371 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
372 and
373 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
374 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
375 project. I hope
376 &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
377 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
378 </description>
379 </item>
380
381 <item>
382 <title>Når nynorskoversettelsen svikter til eksamen...</title>
383 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
384 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
385 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
386 <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
387 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
388 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
389 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
390 på om den fri oversetterløsningen
391 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
392 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
393
394 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
395
396 &lt;blockquote&gt;
397 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
398 rolle og muligheter til å håndtere internasjonale utfordringer, som
399 for eksempel flykningekrisen.&lt;/p&gt;
400
401 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
402 på temaet:&lt;/p&gt;
403 &lt;ol&gt;
404 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
405 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
406 &lt;/ol&gt;
407
408 &lt;/blockquote&gt;
409
410 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
411
412 &lt;blockquote&gt;
413 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
414 andre aktørar og høve til å handtera internasjonale utfordringar, som
415 til dømes *flykningekrisen.&lt;/p&gt;
416
417 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
418 temaet:&lt;/p&gt;
419
420 &lt;ol&gt;
421 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
422 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
423 &lt;/ol&gt;
424
425 &lt;/blockquote&gt;
426
427 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
428 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
429 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
430 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
431 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
432 det er kanskje flisespikking. Det understreker vel bare at det alltid
433 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
434 </description>
435 </item>
436
437 <item>
438 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
439 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
440 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
441 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
442 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
443 computers at the time, I often needed a way to detect if the machine
444 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
445 file or directory affected by the hang, the process (and possibly the
446 shell) will hang too. So you want to be able to detect this without
447 risking the detection process getting stuck too. It has not been
448 obvious how to do this. When the hang has lasted a while, it is
449 possible to find messages like these in dmesg:&lt;/p&gt;
450
451 &lt;p&gt;&lt;blockquote&gt;
452 nfs: server nfsserver not responding, still trying
453 &lt;br&gt;nfs: server nfsserver OK
454 &lt;/blockquote&gt;&lt;/p&gt;
455
456 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
457 be sure looking in dmesg is going to work. If there are lots of other
458 messages in dmesg the lines might have rotated out of site before they
459 are noticed.&lt;/p&gt;
460
461 &lt;p&gt;While reading through the nfs client implementation in linux kernel
462 code, I came across some statistics that seem to give a way to detect
463 it. The om_timeouts sunrpc value in the kernel will increase every
464 time the above log entry is inserted into dmesg. And after digging a
465 bit further, I discovered that this value show up in
466 /proc/self/mountstats on Linux.&lt;/p&gt;
467
468 &lt;p&gt;The mountstats content seem to be shared between files using the
469 same file system context, so it is enough to check one of the
470 mountstats files to get the state of the mount point for the machine.
471 I assume this will not show lazy umounted NFS points, nor NFS mount
472 points in a different process context (ie with a different filesystem
473 view), but that does not worry me.&lt;/p&gt;
474
475 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
476
477 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
478 [...]
479 device /dev/mapper/Debian-var mounted on /var with fstype ext3
480 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
481 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
482 age: 7863311
483 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
484 sec: flavor=1,pseudoflavor=1
485 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
486 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
487 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
488 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
489 per-op statistics
490 NULL: 0 0 0 0 0 0 0 0
491 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
492 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
493 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
494 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
495 READLINK: 125 125 0 20472 18620 0 1112 1118
496 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
497 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
498 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
499 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
500 SYMLINK: 903 903 0 233428 245488 6 5865 5917
501 MKNOD: 80 80 0 20148 21760 0 299 304
502 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
503 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
504 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
505 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
506 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
507 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
508 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
509 FSINFO: 2 2 0 232 328 0 1 1
510 PATHCONF: 1 1 0 116 140 0 0 0
511 COMMIT: 0 0 0 0 0 0 0 0
512
513 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
514 [...]
515 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
516
517 &lt;p&gt;The key number to look at is the third number in the per-op list.
518 It is the number of NFS timeouts experiences per file system
519 operation. Here 22 write timeouts and 5 access timeouts. If these
520 numbers are increasing, I believe the machine is experiencing NFS
521 hang. Unfortunately the timeout value do not start to increase right
522 away. The NFS operations need to time out first, and this can take a
523 while. The exact timeout value depend on the setup. For example the
524 defaults for TCP and UDP mount points are quite different, and the
525 timeout value is affected by the soft, hard, timeo and retrans NFS
526 mount options.&lt;/p&gt;
527
528 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
529 Enterprise Linux for getting the timeout count is to peek in /proc/.
530 But according to
531 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
532 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
533 command can be used to get these timeout values. But this do not work
534 on Linux, as far as I can tell. I
535 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
536 but have not seen any replies yet.&lt;/p&gt;
537
538 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
539 experiencing NFS hangs? Is there a way to detect which processes are
540 affected? Is there a way to get the NFS mount going quickly once the
541 network problem causing the NFS hang has been cleared? I would very
542 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
543 </description>
544 </item>
545
546 <item>
547 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
548 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
549 <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>
550 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
551 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
552 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
553 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
554 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
555 we are working on the proof reading to ensure consistent language and
556 use of correct computer science terms. The plan is to make the book
557 available on paper, as well as in electronic form. For that to
558 happen, the proof reading must be completed and all the figures need
559 to be translated. If you want to help out, get in touch.&lt;/p&gt;
560
561 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
562
563 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
564 pages) of the book created every morning is available for
565 proofreading. If you find any errors, please
566 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
567 Weblate and correct the error&lt;/a&gt;. The
568 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
569 of the translation including figures&lt;/a&gt; is a useful source for those
570 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
571 </description>
572 </item>
573
574 <item>
575 <title>Unlimited randomness with the ChaosKey?</title>
576 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
577 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
578 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
579 <description>&lt;p&gt;A few days ago I ordered a small batch of
580 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
581 USB dongle for generating entropy created by Bdale Garbee and Keith
582 Packard. Yesterday it arrived, and I am very happy to report that it
583 work great! According to its designers, to get it to work out of the
584 box, you need the Linux kernel version 4.1 or later. I tested on a
585 Debian Stretch machine (kernel version 4.9), and there it worked just
586 fine, increasing the available entropy very quickly. I wrote a small
587 test oneliner to test. It first print the current entropy level,
588 drain /dev/random, and then print the entropy level for five seconds.
589 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
590
591 &lt;blockquote&gt;&lt;pre&gt;
592 % cat /proc/sys/kernel/random/entropy_avail; \
593 dd bs=1M if=/dev/random of=/dev/null count=1; \
594 for n in $(seq 1 5); do \
595 cat /proc/sys/kernel/random/entropy_avail; \
596 sleep 1; \
597 done
598 300
599 0+1 oppføringer inn
600 0+1 oppføringer ut
601 28 byte kopiert, 0,000264565 s, 106 kB/s
602 4
603 8
604 12
605 17
606 21
607 %
608 &lt;/pre&gt;&lt;/blockquote&gt;
609
610 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
611 application requiring random bits (like a HTTPS enabled web server)
612 will halt and wait for more entrpy. And here is the situation with
613 the ChaosKey inserted:&lt;/p&gt;
614
615 &lt;blockquote&gt;&lt;pre&gt;
616 % cat /proc/sys/kernel/random/entropy_avail; \
617 dd bs=1M if=/dev/random of=/dev/null count=1; \
618 for n in $(seq 1 5); do \
619 cat /proc/sys/kernel/random/entropy_avail; \
620 sleep 1; \
621 done
622 1079
623 0+1 oppføringer inn
624 0+1 oppføringer ut
625 104 byte kopiert, 0,000487647 s, 213 kB/s
626 433
627 1028
628 1031
629 1035
630 1038
631 %
632 &lt;/pre&gt;&lt;/blockquote&gt;
633
634 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
635 someone want to buy one here in Norway. :)&lt;/p&gt;
636
637 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
638 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
639 recording illuminating&lt;/a&gt;. It explains exactly what the source of
640 randomness is, if you are unable to spot it from the schema drawing
641 available from the ChaosKey web site linked at the start of this blog
642 post.&lt;/p&gt;
643 </description>
644 </item>
645
646 <item>
647 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
648 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
649 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
650 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
651 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
652 web servers, and who own the network equipment it is flowing through?
653 It is possible to get a glimpse of this from using traceroute, but it
654 is hard to find all the details. Many years ago, I wrote a system to
655 map the Norwegian Internet (trying to figure out if our plans for a
656 network game service would get low enough latency, and who we needed
657 to talk to about setting up game servers close to the users. Back
658 then I used traceroute output from many locations (I asked my friends
659 to run a script and send me their traceroute output) to create the
660 graph and the map. The output from traceroute typically look like
661 this:
662
663 &lt;p&gt;&lt;pre&gt;
664 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
665 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
666 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
667 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
668 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
669 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
670 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
671 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
672 8 * * *
673 9 * * *
674 [...]
675 &lt;/pre&gt;&lt;/p&gt;
676
677 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
678 network equipment involved in getting the data traffic from me to the
679 www.stortinget.no server, and how long it took in milliseconds for a
680 package to reach the equipment and return to me. Three packages are
681 sent, and some times the packages do not follow the same path. This
682 is shown for hop 5, where three different IP addresses replied to the
683 traceroute request.&lt;/p&gt;
684
685 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
686 implementations I use are traceroute (using ICMP packages) mtr (can do
687 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
688 traceroute and a lot of other capabilities). All of them are easily
689 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
690
691 &lt;p&gt;This time around, I wanted to know the geographic location of
692 different route points, to visualize how visiting a web page spread
693 information about the visit to a lot of servers around the globe. The
694 background is that a web site today often will ask the browser to get
695 from many servers the parts (for example HTML, JSON, fonts,
696 JavaScript, CSS, video) required to display the content. This will
697 leak information about the visit to those controlling these servers
698 and anyone able to peek at the data traffic passing by (like your ISP,
699 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
700
701 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
702 www.stortinget.no. It is read daily by all members of parliament and
703 their staff, as well as political journalists, activits and many other
704 citizens of Norway. A visit to the www.stortinget.no web site will
705 ask your browser to contact 8 other servers: ajax.googleapis.com,
706 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
707 stats.g.doubleclick.net, www.google-analytics.com,
708 www.googletagmanager.com and www.netigate.se. I extracted this by
709 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
710 Stortinget web page and tell me all the URLs PhantomJS downloaded to
711 render the page (in HAR format using
712 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
713 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
714 to do this). My goal is to visualize network traces to all IP
715 addresses behind these DNS names, do show where visitors personal
716 information is spread when visiting the page.&lt;/p&gt;
717
718 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
719 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;
720
721 &lt;p&gt;When I had a look around for options, I could not find any good
722 free software tools to do this, and decided I needed my own traceroute
723 wrapper outputting KML based on locations looked up using GeoIP. KML
724 is easy to work with and easy to generate, and understood by several
725 of the GIS tools I have available. I got good help from by NUUG
726 colleague Anders Einar with this, and the result can be seen in
727 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
728 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
729 free GeoIP databases I could find (and the for-pay databases my
730 friends had access to) is not up to the task. The IP addresses of
731 central Internet infrastructure would typically be placed near the
732 controlling companies main office, and not where the router is really
733 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
734 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
735
736 &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
737 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;
738
739 &lt;p&gt;I also had a look at the visual traceroute graph created by
740 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
741 showing IP network ownership (aka AS owner) for the IP address in
742 question.
743 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
744 graph display a lot of useful information about the traceroute in SVG
745 format&lt;/a&gt;, and give a good indication on who control the network
746 equipment involved, but it do not include geolocation. This graph
747 make it possible to see the information is made available at least for
748 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
749 3 Communications and NetDNA.&lt;/p&gt;
750
751 &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
752 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;
753
754 &lt;p&gt;In the process, I came across the
755 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
756 Salim Gasmi. Its methology of combining guesses based on DNS names,
757 various location databases and finally use latecy times to rule out
758 candidate locations seemed to do a very good job of guessing correct
759 geolocation. But it could only do one trace at the time, did not have
760 a sensor in Norway and did not make the geolocations easily available
761 for postprocessing. So I contacted the developer and asked if he
762 would be willing to share the code (he refused until he had time to
763 clean it up), but he was interested in providing the geolocations in a
764 machine readable format, and willing to set up a sensor in Norway. So
765 since yesterday, it is possible to run traces from Norway in this
766 service thanks to a sensor node set up by
767 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
768 trace in KML format for further processing.&lt;/p&gt;
769
770 &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
771 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;
772
773 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
774 Denmark, Germany, Holland and Ireland. Plenty of places where the
775 Snowden confirmations verified the traffic is read by various actors
776 without your best interest as their top priority.&lt;/p&gt;
777
778 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
779 over all the hosts behind the urls imported by www.stortinget.no and
780 ask for the KML file from GeoTraceroute, and create a combined KML
781 file with all the traces (unfortunately only one of the IP addresses
782 behind the DNS name is traced this time. To get them all, one would
783 have to request traces using IP number instead of DNS names from
784 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
785
786 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
787 the IP traffic moves and who control the boxes involved in moving it.
788 And every time the link crosses for example the Swedish border, we can
789 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
790 Britain and NSA in USA and cables around the globe. (Hm, what should
791 we tell them? :) Keep that in mind if you ever send anything
792 unencrypted over the Internet.&lt;/p&gt;
793
794 &lt;p&gt;PS: KML files are drawn using
795 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
796 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
797 Marble. There are heaps of other options too.&lt;/p&gt;
798
799 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
800 activities, please send Bitcoin donations to my address
801 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
802 </description>
803 </item>
804
805 <item>
806 <title>Appstream just learned how to map hardware to packages too!</title>
807 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
808 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
809 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
810 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
811 readers probably know, I have been working on the
812 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
813 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
814 it easier for users to figure out what to install to get a given piece
815 of hardware to work in Debian, and a key part of this system is a way
816 to map hardware to packages. Isenkram have its own mapping database,
817 and also uses data provided by each package using the AppStream
818 metadata format. And today,
819 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
820 Debian learned to look up hardware the same way Isenkram is doing it,
821 ie using fnmatch():&lt;/p&gt;
822
823 &lt;p&gt;&lt;pre&gt;
824 % appstreamcli what-provides modalias \
825 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
826 Identifier: pymissile [generic]
827 Name: pymissile
828 Summary: Control original Striker USB Missile Launcher
829 Package: pymissile
830 % appstreamcli what-provides modalias usb:v0694p0002d0000
831 Identifier: libnxt [generic]
832 Name: libnxt
833 Summary: utility library for talking to the LEGO Mindstorms NXT brick
834 Package: libnxt
835 ---
836 Identifier: t2n [generic]
837 Name: t2n
838 Summary: Simple command-line tool for Lego NXT
839 Package: t2n
840 ---
841 Identifier: python-nxt [generic]
842 Name: python-nxt
843 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
844 Package: python-nxt
845 ---
846 Identifier: nbc [generic]
847 Name: nbc
848 Summary: C compiler for LEGO Mindstorms NXT bricks
849 Package: nbc
850 %
851 &lt;/pre&gt;&lt;/p&gt;
852
853 &lt;p&gt;A similar query can be done using the combined AppStream and
854 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
855
856 &lt;p&gt;&lt;pre&gt;
857 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
858 pymissile
859 % isenkram-lookup usb:v0694p0002d0000
860 libnxt
861 nbc
862 python-nxt
863 t2n
864 %
865 &lt;/pre&gt;&lt;/p&gt;
866
867 &lt;p&gt;You can find modalias values relevant for your machine using
868 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
869
870 &lt;p&gt;If you want to make this system a success and help Debian users
871 make the most of the hardware they have, please
872 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
873 AppStream metadata for your package following the guidelines&lt;/a&gt;
874 documented in the wiki. So far only 11 packages provide such
875 information, among the several hundred hardware specific packages in
876 Debian. The Isenkram database on the other hand contain 101 packages,
877 mostly related to USB dongles. Most of the packages with hardware
878 mapping in AppStream are LEGO Mindstorms related, because I have, as
879 part of my involvement in
880 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
881 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
882 complete set of packages in Debian for that particular hardware. The
883 team also got a nice Christmas present today. The
884 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
885 package&lt;/a&gt; made it into Debian. With this package in place, it is
886 now possible to use the LEGO Mindstorms NXT unit with only free
887 software, as the nxt-firmware package contain the source and firmware
888 binaries for the NXT brick.&lt;/p&gt;
889
890 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
891 activities, please send Bitcoin donations to my address
892 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
893 </description>
894 </item>
895
896 <item>
897 <title>Isenkram updated with a lot more hardware-package mappings</title>
898 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
899 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
900 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
901 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
902 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
903 and install packages to get your hardware dongles to work, is still
904 going strong. It is a system to look up the hardware present on or
905 connected to the current system, and map the hardware to Debian
906 packages. It can either be done using the tools in isenkram-cli or
907 using the user space daemon in the isenkram package. The latter will
908 notify you, when inserting new hardware, about what packages to
909 install to get the dongle working. It will even provide a button to
910 click on to ask packagekit to install the packages.&lt;/p&gt;
911
912 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
913
914 &lt;p&gt;&lt;pre&gt;
915 % isenkram-lookup
916 bluez
917 cheese
918 ethtool
919 fprintd
920 fprintd-demo
921 gkrellm-thinkbat
922 hdapsd
923 libpam-fprintd
924 pidgin-blinklight
925 thinkfan
926 tlp
927 tp-smapi-dkms
928 tp-smapi-source
929 tpb
930 %
931 &lt;/pre&gt;&lt;/p&gt;
932
933 &lt;p&gt;It can also list the firware package providing firmware requested
934 by the load kernel modules, which in my case is an empty list because
935 I have all the firmware my machine need:
936
937 &lt;p&gt;&lt;pre&gt;
938 % /usr/sbin/isenkram-autoinstall-firmware -l
939 info: did not find any firmware files requested by loaded kernel modules. exiting
940 %
941 &lt;/pre&gt;&lt;/p&gt;
942
943 &lt;p&gt;The last few days I had a look at several of the around 250
944 packages in Debian with udev rules. These seem like good candidates
945 to install when a given hardware dongle is inserted, and I found
946 several that should be proposed by isenkram. I have not had time to
947 check all of them, but am happy to report that now there are 97
948 packages packages mapped to hardware by Isenkram. 11 of these
949 packages provide hardware mapping using AppStream, while the rest are
950 listed in the modaliases file provided in isenkram.&lt;/p&gt;
951
952 &lt;p&gt;These are the packages with hardware mappings at the moment. The
953 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
954 support using AppStream, for everyone to use:&lt;/p&gt;
955
956 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
957 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
958 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
959 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
960 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
961 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
962 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
963 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
964 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
965 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
966 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
967 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
968 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
969 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
970 pcscd, pidgin-blinklight, printer-driver-splix,
971 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
972 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
973 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
974 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
975 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
976 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
977 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
978 xserver-xorg-video-vmware, yubikey-personalization and
979 zd1211-firmware&lt;/p&gt;
980
981 &lt;p&gt;If you know of other packages, please let me know with a wishlist
982 bug report against the isenkram-cli package, and ask the package
983 maintainer to
984 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
985 metadata according to the guidelines&lt;/a&gt; to provide the information
986 for everyone. In time, I hope to get rid of the isenkram specific
987 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
988
989 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
990 much hardware, and suggest that the package with with any ethernet
991 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
992 the details. I hope the maintainer find time to address it soon. In
993 the mean time I provide an override in isenkram.&lt;/p&gt;
994 </description>
995 </item>
996
997 <item>
998 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
999 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
1000 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
1001 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
1002 <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;
1003
1004 &lt;p&gt;In my early years, I played
1005 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
1006 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
1007 space, and reached the &#39;elite&#39; fighting status before I moved on. The
1008 original Elite game was available on Commodore 64 and the IBM PC
1009 edition I played had a 64 KB executable. I am still impressed today
1010 that the authors managed to squeeze both a 3D engine and details about
1011 more than 2000 planet systems across 7 galaxies into a binary so
1012 small.&lt;/p&gt;
1013
1014 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
1015 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
1016 really have time to test it properly until a few days ago. It was
1017 great to discover that my old knowledge about trading routes were
1018 still valid. But my fighting and flying abilities were gone, so I had
1019 to retrain to be able to dock on a space station. And I am still not
1020 able to make much resistance when I am attacked by pirates, so I
1021 bougth and mounted the most powerful laser in the rear to be able to
1022 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
1023
1024 &lt;p&gt;When playing Elite in the late eighties, I had to discover
1025 everything on my own, and I had long lists of prices seen on different
1026 planets to be able to decide where to trade what. This time I had the
1027 advantages of the
1028 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
1029 where information about each planet is easily available with common
1030 price ranges and suggested trading routes. This improved my ability
1031 to earn money and I have been able to earn enough to buy a lot of
1032 useful equipent in a few days. I believe I originally played for
1033 months before I could get a docking computer, while now I could get it
1034 after less then a week.&lt;/p&gt;
1035
1036 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
1037 space, you should try out Oolite. It is available for Linux, MacOSX
1038 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
1039
1040 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1041 activities, please send Bitcoin donations to my address
1042 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1043 </description>
1044 </item>
1045
1046 <item>
1047 <title>Quicker Debian installations using eatmydata</title>
1048 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
1049 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
1050 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
1051 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
1052 installation system, observing how using
1053 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
1054 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
1055 speedup around 20-40 percent for Debian Edu, where we install around
1056 1000 packages from within the installer. The eatmydata package
1057 provide a way to disable/delay file system flushing. This is a bit
1058 risky in the general case, as files that should be stored on disk will
1059 stay only in memory a bit longer than expected, causing problems if a
1060 machine crashes at an inconvenient time. But for an installation, if
1061 the machine crashes during installation the process is normally
1062 restarted, and avoiding disk operations as much as possible to speed
1063 up the process make perfect sense.
1064
1065 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
1066 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
1067 but did not have time to push it any further. But a few months ago I
1068 picked it up again and worked with the libeatmydata package maintainer
1069 Mattia Rizzolo to make it easier for everyone to get this installation
1070 speedup in Debian. Thanks to our cooperation There is now an
1071 eatmydata-udeb package in Debian testing and unstable, and simply
1072 enabling/installing it in debian-installer (d-i) is enough to get the
1073 quicker installations. It can be enabled using preseeding. The
1074 following untested kernel argument should do the trick:&lt;/p&gt;
1075
1076 &lt;blockquote&gt;&lt;pre&gt;
1077 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
1078 &lt;/pre&gt;&lt;/blockquote&gt;
1079
1080 &lt;p&gt;This should ask d-i to install the package inside the d-i
1081 environment early in the installation sequence. Having it installed
1082 in d-i in turn will make sure the relevant scripts are called just
1083 after debootstrap filled /target/ with the freshly installed Debian
1084 system to configure apt to run dpkg with eatmydata. This is enough to
1085 speed up the installation process. There is a proposal to
1086 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
1087 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
1088 tested its impact.&lt;/p&gt;
1089
1090 </description>
1091 </item>
1092
1093 <item>
1094 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
1095 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
1096 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
1097 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
1098 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1099 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1100 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1101 elever over det ganske land skal levere inn hvert år. Det mange ikke
1102 vet er at selv om de kommersielle alternativene
1103 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
1104 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
1105 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1106 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1107 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1108 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1109 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1110 nynorsk, og få den automatoversatt til det andre skriftspråket.
1111 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1112 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1113 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1114 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1115 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
1116 teksten din i webskjemaet der.
1117
1118 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
1119 teknologien kan du enten installere pakken
1120 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
1121 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1122 api.apertium.org. Se
1123 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
1124 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1125 denne teksten som ble skrevet på bokmål over maskinoversatt til
1126 nynorsk.&lt;/p&gt;
1127
1128 &lt;hr/&gt;
1129
1130 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1131 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1132 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1133 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1134 veit er at sjølv om dei kommersielle alternativa
1135 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
1136 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
1137 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1138 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1139 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1140 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1141 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1142 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1143 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1144 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1145 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1146 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1147 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
1148 teksta di i *webskjemaet der.
1149
1150 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
1151 teknologien kan du anten installera pakken
1152 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
1153 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1154 *api.*apertium.org. Sjå
1155 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
1156 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1157 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1158 nynorsk.&lt;/p&gt;
1159 </description>
1160 </item>
1161
1162 <item>
1163 <title>Coz profiler for multi-threaded software is now in Debian</title>
1164 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
1165 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
1166 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
1167 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
1168 profiler able to run benchmarking experiments on the instrumented
1169 multi-threaded program, finally
1170 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
1171 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
1172 months since
1173 &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
1174 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
1175 it suitable for Debian. There are still issues with clang
1176 compatibility, inline assembly only working x86 and minimized
1177 JavaScript libraries.&lt;/p&gt;
1178
1179 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
1180
1181 &lt;p&gt;&lt;blockquote&gt;
1182 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
1183 &lt;/blockquote&gt;&lt;/p&gt;
1184
1185 &lt;p&gt;This will produce a profile.coz file in the current working
1186 directory with the profiling information. This is then given to a
1187 JavaScript application provided in the package and available from
1188 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
1189 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
1190
1191 &lt;p&gt;&lt;blockquote&gt;
1192 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
1193 &lt;/blockquote&gt;&lt;/p&gt;
1194
1195 &lt;p&gt;See the project home page and the
1196 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
1197 ;login: article on Coz&lt;/a&gt; for more information on how it is
1198 working.&lt;/p&gt;
1199 </description>
1200 </item>
1201
1202 <item>
1203 <title>My own self balancing Lego Segway</title>
1204 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
1205 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
1206 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
1207 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
1208 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
1209 present. It had been on my wishlist for a while, because I wanted to
1210 build a Segway like balancing lego robot. I had already built
1211 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
1212 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
1213 NXT kit as the balance sensor, but it was not working very well. It
1214 could balance for a while, but was very sensitive to the light
1215 condition in the room and the reflective properties of the surface and
1216 would fall over after a short while. I wanted something more robust,
1217 and had
1218 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
1219 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
1220 wishlist for some years before it suddenly showed up as a gift from my
1221 loved ones. :)&lt;/p&gt;
1222
1223 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
1224 since then. But that changed some days ago, when I was searching for
1225 lego segway information and came across a recipe from HiTechnic for
1226 building
1227 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
1228 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
1229 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
1230 code&lt;/a&gt; was included, so it was just a question of putting it all
1231 together. And thanks to the great work of many Debian developers, the
1232 compiler needed to build the source for the NXT is already included in
1233 Debian, so I was read to go in less than an hour. The resulting robot
1234 do not look very impressive in its simplicity:&lt;/p&gt;
1235
1236 &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;
1237
1238 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
1239 design from HiTechnic, I had to comment out the last task
1240 (taskControl). I simply placed /* and */ around it get the program
1241 working without that sensor present. Now it balances just fine until
1242 the battery status run low:&lt;/p&gt;
1243
1244 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
1245 &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;
1246 &lt;/video&gt;&lt;/p&gt;
1247
1248 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
1249 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
1250
1251 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
1252 they need to work with LEGO in Debian and all our derivative
1253 distributions like Ubuntu, check out
1254 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
1255 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
1256 RCX and NXT controller (no EV3), and would like to make sure the
1257 Debian tools needed to program the systems I own work as they
1258 should.&lt;/p&gt;
1259 </description>
1260 </item>
1261
1262 <item>
1263 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
1264 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
1265 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
1266 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
1267 <description>&lt;p&gt;In July
1268 &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
1269 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
1270 the ability to receive SMS messages (aka without a cell phone). It is
1271 time to share some experiences and provide an updated setup.&lt;/p&gt;
1272
1273 &lt;p&gt;The Signal app have worked fine for several months now, and I use
1274 it regularly to chat with my loved ones. I had a major snag at the
1275 end of my summer vacation, when the the app completely forgot my
1276 setup, identity and keys. The reason behind this major mess was
1277 running out of disk space. To avoid that ever happening again I have
1278 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
1279 roll back to an earlier version if the files are wiped by mistake. I
1280 had to use it once after introducing the git backup. When rolling
1281 back to an earlier version, one need to use the &#39;reset session&#39; option
1282 in Signal to get going, and notify the people you talk with about the
1283 problem. I assume there is some sequence number tracking in the
1284 protocol to detect rollback attacks. The git repository is rather big
1285 (674 MiB so far), but I have not tried to figure out if some of the
1286 content can be added to a .gitignore file due to lack of spare
1287 time.&lt;/p&gt;
1288
1289 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
1290 make it impossible to send messages using Signal. I could still
1291 receive them, but had to patch the code with a new timestamp to send.
1292 I believe the timeout is added by the developers to force people to
1293 upgrade to the latest version of the app, even when there is no
1294 protocol changes, to reduce the version skew among the user base and
1295 thus try to keep the number of support requests down.&lt;/p&gt;
1296
1297 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
1298 making the old patch fail to apply cleanly. Below is an updated
1299 patch, including the shell wrapper I use to start Signal. The
1300 original version required a new user to locate the JavaScript console
1301 and call a function from there. I got help from a friend with more
1302 JavaScript knowledge than me to modify the code to provide a GUI
1303 button instead. This mean that to get started you just need to run
1304 the wrapper and click the &#39;Register without mobile phone&#39; to get going
1305 now. I&#39;ve also modified the timeout code to always set it to 90 days
1306 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
1307
1308 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
1309
1310 &lt;ol&gt;
1311
1312 &lt;li&gt;First, install required packages to get the source code and the
1313 browser you need. Signal only work with Chrome/Chromium, as far as I
1314 know, so you need to install it.
1315
1316 &lt;pre&gt;
1317 apt install git tor chromium
1318 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1319 &lt;/pre&gt;&lt;/li&gt;
1320
1321 &lt;li&gt;Modify the source code using command listed in the the patch
1322 block below.&lt;/li&gt;
1323
1324 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
1325 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
1326
1327 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
1328 number you can receive calls to the next minute, receive the
1329 verification code and enter it into the form field and press
1330 &#39;Register&#39;. Note, the phone number you use will be user Signal
1331 username, ie the way others can find you on Signal.&lt;/li&gt;
1332
1333 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
1334 not show up in the contact list until you restart Signal, and there is
1335 no way to assign names to Contacts. There is also no way to create or
1336 update chat groups. I suspect this is because the web app do not have
1337 a associated contact database.&lt;/li&gt;
1338
1339 &lt;/ol&gt;
1340
1341 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
1342 main author moxie0 reject federation and accept dependencies to major
1343 corporations like Google (part of the code is fetched from Google) and
1344 Amazon (the central coordination point is owned by Amazon). See for
1345 example
1346 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
1347 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
1348 view on these issues. But the network effect is strong in this case,
1349 and several of the people I want to communicate with already use
1350 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
1351 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
1352 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
1353 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
1354 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
1355 working on Debian Stable.&lt;/p&gt;
1356
1357 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
1358 working. It switch to the production servers, disable to timeout,
1359 make registration easier and add the shell wrapper:&lt;/p&gt;
1360
1361 &lt;pre&gt;
1362 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
1363 diff --git a/js/background.js b/js/background.js
1364 index 24b4c1d..579345f 100644
1365 --- a/js/background.js
1366 +++ b/js/background.js
1367 @@ -33,9 +33,9 @@
1368 });
1369 });
1370
1371 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
1372 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
1373 var SERVER_PORTS = [80, 4433, 8443];
1374 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
1375 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
1376 var messageReceiver;
1377 window.getSocketStatus = function() {
1378 if (messageReceiver) {
1379 diff --git a/js/expire.js b/js/expire.js
1380 index 639aeae..beb91c3 100644
1381 --- a/js/expire.js
1382 +++ b/js/expire.js
1383 @@ -1,6 +1,6 @@
1384 ;(function() {
1385 &#39;use strict&#39;;
1386 - var BUILD_EXPIRATION = 0;
1387 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
1388
1389 window.extension = window.extension || {};
1390
1391 diff --git a/js/views/install_view.js b/js/views/install_view.js
1392 index 7816f4f..1d6233b 100644
1393 --- a/js/views/install_view.js
1394 +++ b/js/views/install_view.js
1395 @@ -38,7 +38,8 @@
1396 return {
1397 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
1398 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
1399 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
1400 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
1401 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
1402 };
1403 },
1404 clearQR: function() {
1405 diff --git a/options.html b/options.html
1406 index dc0f28e..8d709f6 100644
1407 --- a/options.html
1408 +++ b/options.html
1409 @@ -14,7 +14,10 @@
1410 &amp;lt;div class=&#39;nav&#39;&gt;
1411 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
1412 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
1413 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
1414 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
1415 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
1416 +
1417 + &amp;lt;/div&gt;
1418 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
1419 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
1420 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
1421 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
1422 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
1423 @@ -0,0 +1,12 @@
1424 +#!/bin/sh
1425 +set -e
1426 +cd $(dirname $0)
1427 +mkdir -p userdata
1428 +userdata=&quot;`pwd`/userdata&quot;
1429 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
1430 + (cd $userdata &amp;&amp; git init)
1431 +fi
1432 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
1433 +exec chromium \
1434 + --proxy-server=&quot;socks://localhost:9050&quot; \
1435 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1436 EOF
1437 chmod a+rx run-signal-app
1438 &lt;/pre&gt;
1439
1440 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1441 activities, please send Bitcoin donations to my address
1442 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1443 </description>
1444 </item>
1445
1446 <item>
1447 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
1448 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
1449 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
1450 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
1451 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
1452 system&lt;/a&gt; provide a practical and easy way to figure out which
1453 packages support the hardware in a given machine. The command line
1454 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
1455 convenient way to list and install packages relevant for the current
1456 hardware during system installation, both user space packages and
1457 firmware packages. The GUI background daemon on the other hand provide
1458 a pop-up proposing to install packages when a new dongle is inserted
1459 while using the computer. For example, if you plug in a smart card
1460 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
1461 that package isn&#39;t already installed, and if you plug in a USB video
1462 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
1463 cheese is currently missing. This already work just fine.&lt;/p&gt;
1464
1465 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
1466 package names. When I started no such database existed in Debian, so
1467 I made my own data set and included it with the isenkram package and
1468 made isenkram fetch the latest version of this database from git using
1469 http. This way the isenkram users would get updated package proposals
1470 as soon as I learned more about hardware related packages.&lt;/p&gt;
1471
1472 &lt;p&gt;The hardware is identified using modalias strings. The modalias
1473 design is from the Linux kernel where most hardware descriptors are
1474 made available as a strings that can be matched using filename style
1475 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1476 identifiers.&lt;/p&gt;
1477
1478 &lt;p&gt;The downside to the Isenkram specific database is that there is no
1479 information about relevant distribution / Debian version, making
1480 isenkram propose obsolete packages too. But along came AppStream, a
1481 cross distribution mechanism to store and collect metadata about
1482 software packages. When I heard about the proposal, I contacted the
1483 people involved and suggested to add a hardware matching rule using
1484 modalias strings in the specification, to be able to use AppStream for
1485 mapping hardware to packages. This idea was accepted and AppStream is
1486 now a great way for a package to announce the hardware it support in a
1487 distribution neutral way. I wrote
1488 &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
1489 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
1490 December. If you have a hardware related package in Debian, please
1491 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
1492
1493 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
1494 RCX or NXT unit, announce this support using AppStream. The effect is
1495 that when you insert such LEGO robot controller into your Debian
1496 machine, Isenkram will propose to install the packages needed to get
1497 it working. The intention is that this should allow the local user to
1498 start programming his robot controller right away without having to
1499 guess what packages to use or which permissions to fix.&lt;/p&gt;
1500
1501 &lt;p&gt;But when I sat down with my son the other day to program our NXT
1502 unit using his Debian Stretch computer, I discovered something
1503 annoying. The local console user (ie my son) did not get access to
1504 the USB device for programming the unit. This used to work, but no
1505 longer in Jessie and Stretch. After some investigation and asking
1506 around on #debian-devel, I discovered that this was because udev had
1507 changed the mechanism used to grant access to local devices. The
1508 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
1509 no longer applied, because LDAP users no longer was added to the
1510 plugdev group during login. Michael Biebl told me that this method
1511 was obsolete and the new method used ACLs instead. This was good
1512 news, as the plugdev mechanism is a mess when using a remote user
1513 directory like LDAP. Using ACLs would make sure a user lost device
1514 access when she logged out, even if the user left behind a background
1515 process which would retain the plugdev membership with the ConsoleKit
1516 setup. Armed with this knowledge I moved on to fix the access problem
1517 for the LEGO Mindstorms related packages.&lt;/p&gt;
1518
1519 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
1520 applied directly for a device, or is applied in
1521 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
1522 LEGO Mindstorms udev rules did not have a class, I decided to add the
1523 tag directly in the udev rules files included in the packages. Here
1524 is one example. For the nqc C compiler for the RCX, the
1525 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
1526
1527 &lt;p&gt;&lt;pre&gt;
1528 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
1529 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
1530 &lt;/pre&gt;&lt;/p&gt;
1531
1532 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
1533 packages using plugdev in their /lib/udev/rules.d/ files should be
1534 changed to use this tag (either directly or indirectly via
1535 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
1536 to detect this?&lt;/p&gt;
1537
1538 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
1539 It is unclear to me if the uaccess tag is an internal implementation
1540 detail like the udev-acl tag used by
1541 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
1542 indirect method is the preferred way. Michael
1543 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
1544 documentation from the systemd project&lt;/a&gt; and I hope it will make
1545 this clearer. For now I use the generic classes when they exist and
1546 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
1547 directly if no such class exist.&lt;/p&gt;
1548
1549 &lt;p&gt;To learn more about the isenkram system, please check out
1550 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
1551 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
1552
1553 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
1554 please join us on our IRC channel
1555 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
1556 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
1557 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
1558 list is not yet created, but we are working on it. :)&lt;/p&gt;
1559
1560 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1561 activities, please send Bitcoin donations to my address
1562 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1563 </description>
1564 </item>
1565
1566 <item>
1567 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
1568 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
1569 <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>
1570 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
1571 <description>&lt;p&gt;In April we
1572 &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
1573 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
1574 how to set up and administrate a Debian system. Today I am happy to
1575 report that the first draft is now publicly available. You can find
1576 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
1577 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
1578 eight chapters have a first draft translation, and we are working on
1579 proofreading the content. If you want to help out, please start
1580 contributing using
1581 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
1582 hosted weblate project page&lt;/a&gt;, and get in touch using
1583 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
1584 translators mailing list&lt;/a&gt;. Please also check out
1585 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
1586 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
1587 and update weblate if you find errors.&lt;/p&gt;
1588
1589 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
1590 electronic form.&lt;/p&gt;
1591 </description>
1592 </item>
1593
1594 <item>
1595 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
1596 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
1597 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
1598 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
1599 <description>&lt;p&gt;This summer, I read a great article
1600 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
1601 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
1602 how to profile multi-threaded programs. It presented a system for
1603 profiling software by running experiences in the running program,
1604 testing how run time performance is affected by &quot;speeding up&quot; parts of
1605 the code to various degrees compared to a normal run. It does this by
1606 slowing down parallel threads while the &quot;faster up&quot; code is running
1607 and measure how this affect processing time. The processing time is
1608 measured using probes inserted into the code, either using progress
1609 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1610 can also measure unmodified code by measuring complete the program
1611 runtime and running the program several times instead.&lt;/p&gt;
1612
1613 &lt;p&gt;The project and presentation was so inspiring that I would like to
1614 get the system into Debian. I
1615 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
1616 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
1617 system ready for Debian by sending patches. The build process need to
1618 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
1619 to include the JavaScript web page used to visualize the collected
1620 profiling information included in the source package.
1621 But I expect that should work out fairly soon.&lt;/p&gt;
1622
1623 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
1624 on a binary with debug symbols available, start the program like this:
1625
1626 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1627 coz run --- program-to-run
1628 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1629
1630 &lt;p&gt;This will create a text file profile.coz with the instrumentation
1631 information. To show what part of the code affect the performance
1632 most, use a web browser and either point it to
1633 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
1634 or use the copy from git (in the gh-pages branch). Check out this web
1635 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
1636 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
1637 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1638 code, rebuild and run the profiler. This allow coz to do more
1639 targeted experiments.&lt;/p&gt;
1640
1641 &lt;p&gt;A video published by ACM
1642 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
1643 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
1644 from the 25th Symposium on Operating Systems Principles available
1645 titled
1646 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
1647 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
1648
1649 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
1650 for Coz is available from github. It will only build with clang
1651 because it uses a
1652 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
1653 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
1654 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
1655 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
1656
1657 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
1658 of software in Debian. I would very much like some help with the
1659 packaging effort, as I lack the in depth knowledge on how to package
1660 C++ libraries.&lt;/p&gt;
1661 </description>
1662 </item>
1663
1664 <item>
1665 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
1666 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
1667 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
1668 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
1669 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1670 to be a slight challenge. Here is the recipe if I ever need to do it
1671 again. It all started by me wanting to try the recipe to set up
1672 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
1673 hardened Android installation&lt;/a&gt; from the Tor project blog on a
1674 device I had access to. It is a old mobile phone with a broken
1675 microphone The initial idea had been to just
1676 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
1677 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
1678 until a few days ago.&lt;/p&gt;
1679
1680 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
1681 loader (press volume down and power at the same time), (2) select
1682 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
1683 machine, (4) request the device identifier token by running &#39;fastboot
1684 oem get_identifier_token&#39;, (5) request the device unlocking key using
1685 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
1686 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
1687
1688 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
1689 or newer, and the device I was working on had 2.00.0027. This
1690 apparently can be easily fixed by downloading a Windows program and
1691 running it on your Windows machine, if you accept the terms Microsoft
1692 require you to accept to use Windows - which I do not. So I had to
1693 come up with a different approach. I got a lot of help from AndyCap
1694 on #nuug, and would not have been able to get this working without
1695 him.&lt;/p&gt;
1696
1697 &lt;p&gt;First I needed to extract the hboot firmware from
1698 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
1699 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
1700 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
1701 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
1702 recognise the file format, but unruu worked and extracted rom.zip,
1703 containing the new hboot firmware and a text file describing which
1704 devices it would work for.&lt;/p&gt;
1705
1706 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
1707 followed some instructions
1708 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
1709 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
1710 machine with Debian testing:&lt;/p&gt;
1711
1712 &lt;p&gt;&lt;pre&gt;
1713 adb reboot-bootloader
1714 fastboot oem rebootRUU
1715 fastboot flash zip rom.zip
1716 fastboot flash zip rom.zip
1717 fastboot reboot
1718 &lt;/pre&gt;&lt;/p&gt;
1719
1720 &lt;p&gt;The flash command apparently need to be done twice to take effect,
1721 as the first is just preparations and the second one do the flashing.
1722 The adb command is just to get to the boot loader menu, so turning the
1723 device on while holding volume down and the power button should work
1724 too.&lt;/p&gt;
1725
1726 &lt;p&gt;With the new hboot version in place I could start following the
1727 instructions on the HTC developer web site. I got the device token
1728 like this:&lt;/p&gt;
1729
1730 &lt;p&gt;&lt;pre&gt;
1731 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
1732 &lt;/pre&gt;
1733
1734 &lt;p&gt;And once I got the unlock code via email, I could use it like
1735 this:&lt;/p&gt;
1736
1737 &lt;p&gt;&lt;pre&gt;
1738 fastboot flash unlocktoken Unlock_code.bin
1739 &lt;/pre&gt;&lt;/p&gt;
1740
1741 &lt;p&gt;And with that final step in place, the phone was unlocked and I
1742 could start stuffing the software of my own choosing into the device.
1743 So far I only inserted a replacement recovery image to wipe the phone
1744 before I start. We will see what happen next. Perhaps I should
1745 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
1746 </description>
1747 </item>
1748
1749 <item>
1750 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
1751 <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>
1752 <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>
1753 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
1754 <description>&lt;p&gt;For a while now, I have wanted to test
1755 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
1756 said to provide end to end encrypted communication and several of my
1757 friends and family are already using it. As I by choice do not own a
1758 mobile phone, this proved to be harder than expected. And I wanted to
1759 have the source of the client and know that it was the code used on my
1760 machine. But yesterday I managed to get it working. I used the
1761 Github source, compared it to the source in
1762 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
1763 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
1764 patches to use the production Signal servers, started the app and
1765 asked for the hidden &quot;register without a smart phone&quot; form. Here is
1766 the recipe how I did it.&lt;/p&gt;
1767
1768 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
1769
1770 &lt;pre&gt;
1771 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1772 &lt;/pre&gt;
1773
1774 &lt;p&gt;Next, I patched the source to use the production servers, to be
1775 able to talk to other Signal users:&lt;/p&gt;
1776
1777 &lt;pre&gt;
1778 cat &amp;lt;&amp;lt;EOF | patch -p0
1779 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
1780 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
1781 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
1782 @@ -47,8 +47,8 @@
1783 });
1784 });
1785
1786 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
1787 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
1788 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
1789 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
1790 var messageReceiver;
1791 window.getSocketStatus = function() {
1792 if (messageReceiver) {
1793 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
1794 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
1795 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
1796 @@ -1,6 +1,6 @@
1797 ;(function() {
1798 &#39;use strict&#39;;
1799 - var BUILD_EXPIRATION = 0;
1800 + var BUILD_EXPIRATION = 1474492690000;
1801
1802 window.extension = window.extension || {};
1803
1804 EOF
1805 &lt;/pre&gt;
1806
1807 &lt;p&gt;The first part is changing the servers, and the second is updating
1808 an expiration timestamp. This timestamp need to be updated regularly.
1809 It is set 90 days in the future by the build process (Gruntfile.js).
1810 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
1811
1812 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
1813 script to launch Signal in Chromium.&lt;/p&gt;
1814
1815 &lt;pre&gt;
1816 #!/bin/sh
1817 cd $(dirname $0)
1818 mkdir -p userdata
1819 exec chromium \
1820 --proxy-server=&quot;socks://localhost:9050&quot; \
1821 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1822 &lt;/pre&gt;
1823
1824 &lt;p&gt; The script start the app and configure Chromium to use the Tor
1825 SOCKS5 proxy to make sure those controlling the Signal servers (today
1826 Amazon and Whisper Systems) as well as those listening on the lines
1827 will have a harder time location my laptop based on the Signal
1828 connections if they use source IP address.&lt;/p&gt;
1829
1830 &lt;p&gt;When the script starts, one need to follow the instructions under
1831 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
1832 repository. I right clicked on the Signal window to get up the
1833 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
1834 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
1835 registration form. Then I entered by land line phone number and
1836 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
1837 repeated the verification code three times. After entering the number
1838 into the verification code field in the form, I could start using
1839 Signal from my laptop.
1840
1841 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
1842 whom and thus who know who to those controlling the central server,
1843 but such leakage is hard to avoid with a centrally controlled server
1844 setup. It is something to keep in mind when using Signal - the
1845 content of your chats are harder to intercept, but the meta data
1846 exposing your contact network is available to people you do not know.
1847 So better than many options, but not great. And sadly the usage is
1848 connected to my land line, thus allowing those controlling the server
1849 to associate it to my home and person. I would prefer it if only
1850 those I knew could tell who I was on Signal. There are options
1851 avoiding such information leakage, but most of my friends are not
1852 using them, so I am stuck with Signal for now.&lt;/p&gt;
1853
1854 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
1855 on this topic in
1856 &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
1857 and updated recipe for using the Signal app without a mobile
1858 phone&lt;/a&gt;.&lt;/p&gt;
1859 </description>
1860 </item>
1861
1862 <item>
1863 <title>The new &quot;best&quot; multimedia player in Debian?</title>
1864 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
1865 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
1866 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
1867 <description>&lt;p&gt;When I set out a few weeks ago to figure out
1868 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
1869 multimedia player in Debian claimed to support most file formats /
1870 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
1871 the various players claimed support for. The range was from 55 to 130
1872 MIME types. I suspect most media formats are supported by all
1873 players, but this is not really reflected in the MimeTypes values in
1874 their desktop files. There are probably also some bogus MIME types
1875 listed, but it is hard to identify which one this is.&lt;/p&gt;
1876
1877 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
1878 the players suggesting to add more MIME types to their desktop files,
1879 and decided to spend some time myself improving the situation for my
1880 favorite media player VLC. The fixes for VLC entered Debian unstable
1881 yesterday. The complete list of MIME types can be seen on the
1882 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
1883 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
1884
1885 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
1886 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1887 kmplayer. I am sure some of the other players desktop files support
1888 several of the formats currently listed as working only with vlc,
1889 toten and parole.&lt;/p&gt;
1890
1891 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
1892 supported by all the tested multimedia players in Debian in their
1893 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1894 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1895 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1896 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1897 it sad that video/ogg and video/webm is not supported by all the media
1898 players in Debian. As far as I can tell, all of them can handle both
1899 formats.&lt;/p&gt;
1900 </description>
1901 </item>
1902
1903 <item>
1904 <title>A program should be able to open its own files on Linux</title>
1905 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
1906 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
1907 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
1908 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
1909 decided to test its presentation tool when making the slides for a
1910 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1911 wrote the first draft of the slides, saved the result and went to bed
1912 the day before I would give the talk. The next day I took a plane to
1913 the location where the meeting should take place, and on the plane I
1914 started up koffice again to polish the talk a bit, only to discover
1915 that kpresenter refused to load its own data file. I cursed a bit and
1916 started making the slides again from memory, to have something to
1917 present when I arrived. I tested that the saved files could be
1918 loaded, and the day seemed to be rescued. I continued to polish the
1919 slides until I suddenly discovered that the saved file could no longer
1920 be loaded into kpresenter. In the end I had to rewrite the slides
1921 three times, condensing the content until the talk became shorter and
1922 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
1923 kpresenter wrote inline images in a way itself could not understand.
1924 Eventually that bug was fixed and kpresenter ended up being a great
1925 program to make slides. The point I&#39;m trying to make is that we
1926 expect a program to be able to load its own data files, and it is
1927 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
1928
1929 &lt;p&gt;Did you ever experience a program failing to load its own data
1930 files from the desktop file browser? It is not a uncommon problem. A
1931 while back I discovered that the screencast recorder
1932 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1933 browser would refuse to open. No video player claimed to understand
1934 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
1935 returning the application/ogg MIME type, which no video player I had
1936 installed listed as a MIME type they would understand. I asked for
1937 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
1938 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
1939 several video players to add video/ogg to their desktop files, to give
1940 the file browser an idea what to do about Ogg Theora files. After a
1941 while, the desktop file browsers in Debian started to handle the
1942 output from gtk-recordmydesktop properly.&lt;/p&gt;
1943
1944 &lt;p&gt;But history repeats itself. A few days ago I tested the music
1945 system Rosegarden again, and I discovered that the KDE and xfce file
1946 browsers did not know what to do with the Rosegarden project files
1947 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
1948 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
1949 included in the next upload. To increase the chance of me remembering
1950 how to fix the problem next time some program fail to load its files
1951 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
1952
1953 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
1954 There are two sources for the MIME type of a given file. The output from
1955 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
1956 shared MIME type registry (under /usr/share/mime/). The file MIME
1957 type is mapped to programs supporting the MIME type, and this
1958 information is collected from
1959 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
1960 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
1961 one desktop file claiming support for the MIME type of the file, it is
1962 activated when asking to open a given file. If there are more, one
1963 can normally select which one to use by right-clicking on the file and
1964 selecting the wanted one using &#39;Open with&#39; or similar. In general
1965 this work well. But it depend on each program picking a good MIME
1966 type (preferably
1967 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
1968 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
1969 registry recognizing the file and the desktop file to list the MIME
1970 type in its list of supported MIME types.&lt;/p&gt;
1971
1972 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
1973 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
1974 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
1975
1976 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1977 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
1978 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
1979 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
1980 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
1981 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
1982 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
1983 &amp;lt;/mime-type&amp;gt;
1984 &amp;lt;/mime-info&amp;gt;
1985 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1986
1987 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
1988 (it is a gzipped XML file). Note, it is much better to use an
1989 official MIME type registered with IANA than it is to make up ones own
1990 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
1991
1992 &lt;p&gt;The desktop file of the rosegarden program failed to list
1993 audio/x-rosegarden in its list of supported MIME types, causing the
1994 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
1995
1996 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1997 % grep Mime /usr/share/applications/rosegarden.desktop
1998 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1999 X-KDE-NativeMimeType=audio/x-rosegarden-composition
2000 %
2001 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2002
2003 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
2004 MimeType= line.&lt;/p&gt;
2005
2006 &lt;p&gt;If you run into a file which fail to open the correct program when
2007 selected from the file browser, please check out the output from
2008 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
2009 MIME type is registered somewhere under /usr/share/mime/ and check
2010 that some desktop file under /usr/share/applications/ is claiming
2011 support for this MIME type. If not, please report a bug to have it
2012 fixed. :)&lt;/p&gt;
2013 </description>
2014 </item>
2015
2016 <item>
2017 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
2018 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
2019 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
2020 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
2021 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
2022 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
2023 related packages. The idea is to have a database of mappings between
2024 hardware and packages, and pop up a dialog suggesting for the user to
2025 install the packages to use a given hardware dongle. Some use cases
2026 are when you insert a Yubikey, it proposes to install the software
2027 needed to control it; when you insert a braille reader list it
2028 proposes to install the packages needed to send text to the reader;
2029 and when you insert a ColorHug screen calibrator it suggests to
2030 install the driver for it. The system work well, and even have a few
2031 command line tools to install firmware packages and packages for the
2032 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
2033
2034 &lt;p&gt;The system was initially written using aptdaemon, because I found
2035 good documentation and example code on how to use it. But aptdaemon
2036 is going away and is generally being replaced by
2037 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
2038 so Isenkram needed a rewrite. And today, thanks to the great patch
2039 from my college Sunil Mohan Adapa in the FreedomBox project, the
2040 rewrite finally took place. I&#39;ve just uploaded a new version of
2041 Isenkram into Debian Unstable with the patch included, and the default
2042 for the background daemon is now to use PackageKit. To check it out,
2043 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
2044 and see if it is recognised.&lt;/p&gt;
2045
2046 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
2047 the machine it is running on, you can check out the isenkram-lookup
2048 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
2049
2050 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2051 % isenkram-lookup
2052 bluez
2053 cheese
2054 fprintd
2055 fprintd-demo
2056 gkrellm-thinkbat
2057 hdapsd
2058 libpam-fprintd
2059 pidgin-blinklight
2060 thinkfan
2061 tleds
2062 tp-smapi-dkms
2063 tp-smapi-source
2064 tpb
2065 %p
2066 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2067
2068 &lt;p&gt;The hardware mappings come from several places. The preferred way
2069 is for packages to announce their hardware support using
2070 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
2071 cross distribution appstream system&lt;/a&gt;.
2072 See
2073 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
2074 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
2075 </description>
2076 </item>
2077
2078 <item>
2079 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
2080 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
2081 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
2082 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
2083 <description>&lt;p&gt;Yesterday I updated the
2084 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
2085 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
2086 enterprising users. There were some nice user and visible changes.
2087 First of all, both desktop menu entries now work. A design flaw in
2088 one of the script made the history graph fail to show up (its PNG was
2089 dumped in ~/.xsession-errors) if no controlling TTY was available.
2090 The script worked when called from the command line, but not when
2091 called from the desktop menu. I changed this to look for a DISPLAY
2092 variable or a TTY before deciding where to draw the graph, and now the
2093 graph window pop up as expected.&lt;/p&gt;
2094
2095 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
2096 graphs (the one showing the last few hours). New is also the user of
2097 colours showing charging in blue and discharge in red. The percentages
2098 of this graph is relative to last full charge, not battery design
2099 capacity.&lt;/p&gt;
2100
2101 &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;
2102
2103 &lt;p&gt;The other graph show the entire history of the collected battery
2104 statistics, comparing it to the design capacity of the battery to
2105 visualise how the battery life time get shorter over time. The red
2106 line in this graph is what the previous graph considers 100 percent:
2107
2108 &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;
2109
2110 &lt;p&gt;In this graph you can see that I only charge the battery to 80
2111 percent of last full capacity, and how the capacity of the battery is
2112 shrinking. :(&lt;/p&gt;
2113
2114 &lt;p&gt;The last new feature is in the collector, which now will handle
2115 more hardware models. On some hardware, Linux power supply
2116 information is stored in /sys/class/power_supply/ACAD/, while the
2117 collector previously only looked in /sys/class/power_supply/AC/. Now
2118 both are checked to figure if there is power connected to the
2119 machine.&lt;/p&gt;
2120
2121 &lt;p&gt;If you are interested in how your laptop battery is doing, please
2122 check out the
2123 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
2124 in Debian unstable, or rebuild it on Jessie to get it working on
2125 Debian stable. :) The upstream source is available from &lt;a
2126 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2127 Patches are very welcome.&lt;/p&gt;
2128
2129 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2130 activities, please send Bitcoin donations to my address
2131 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2132 </description>
2133 </item>
2134
2135 <item>
2136 <title>Debian now with ZFS on Linux included</title>
2137 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
2138 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
2139 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
2140 <description>&lt;p&gt;Today, after many years of hard work from many people,
2141 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
2142 Debian. The package status can be seen on
2143 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
2144 for zfs-linux&lt;/a&gt;. and
2145 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
2146 team status page&lt;/a&gt;. If you want to help out, please join us.
2147 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
2148 source code&lt;/a&gt; is available via git on Alioth. It would also be
2149 great if you could help out with
2150 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
2151 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
2152 </description>
2153 </item>
2154
2155 <item>
2156 <title>What is the best multimedia player in Debian?</title>
2157 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
2158 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
2159 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
2160 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
2161 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
2162
2163 &lt;p&gt;A few years ago, I had a look at the media support for Browser
2164 plugins in Debian, to get an idea which plugins to include in Debian
2165 Edu. I created a script to extract the set of supported MIME types
2166 for each plugin, and used this to find out which multimedia browser
2167 plugin supported most file formats / media types.
2168 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
2169 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
2170 not been updated for a while. But browser plugins are less relevant
2171 these days, so I thought it was time to look at standalone
2172 players.&lt;/p&gt;
2173
2174 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
2175 player when I wanted to play videos from the Norwegian National
2176 Broadcasting Company, and decided to investigate why. The cause is a
2177 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
2178 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
2179 of MIME types announced in the desktop file and the browser plugin,
2180 only to discover that there is quite a large difference between the
2181 two for VLC. This discovery made me dig up the script I used to
2182 compare browser plugins, and adjust it to compare desktop files
2183 instead, to try to figure out which multimedia player in Debian
2184 support most file formats.&lt;/p&gt;
2185
2186 &lt;p&gt;The result can be seen on the Debian Wiki, as
2187 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
2188 table listing all MIME types supported by one of the packages included
2189 in the table&lt;/a&gt;, with the package supporting most MIME types being
2190 listed first in the table.&lt;/p&gt;
2191
2192 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
2193 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2194 kmplayer. Time for the other players to update their announced MIME
2195 support?&lt;/p&gt;
2196 </description>
2197 </item>
2198
2199 <item>
2200 <title>The Pyra - handheld computer with Debian preinstalled</title>
2201 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
2202 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
2203 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
2204 <description>A friend of mine made me aware of
2205 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
2206 handheld computer which will be delivered with Debian preinstalled. I
2207 would love to get one of those for my birthday. :)&lt;/p&gt;
2208
2209 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2210 plugs and many others connectors, and include a full keyboard and a 5&quot;
2211 LCD touch screen. The 6000mAh battery is claimed to provide a whole
2212 day of battery life time, but I have not seen any independent tests
2213 confirming this. The vendor is still collecting preorders, and the
2214 last I heard last night was that 22 more orders were needed before
2215 production started.&lt;/p&gt;
2216
2217 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
2218 Debian. Please let me know if you know of any others. Is it the
2219 first computer being sold with Debian preinstalled?&lt;/p&gt;
2220 </description>
2221 </item>
2222
2223 <item>
2224 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
2225 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
2226 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
2227 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
2228 <description>&lt;p&gt;During this weekends
2229 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
2230 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
2231 to make sure there are good books about Debian available in Norwegian
2232 Bokmål, and got in touch with the people behind the
2233 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
2234 project&lt;/a&gt; to get started. If you want to help out, please start
2235 contributing using
2236 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
2237 hosted weblate project page&lt;/a&gt;, and get in touch using
2238 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
2239 translators mailing list&lt;/a&gt;. Please also check out
2240 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
2241 contributors&lt;/a&gt;.&lt;/p&gt;
2242
2243 &lt;p&gt;The book is already available on paper in English, French and
2244 Japanese, and our goal is to get it available on paper in Norwegian
2245 Bokmål too. In addition to the paper edition, there are also EPUB and
2246 Mobi versions available. And there are incomplete translations
2247 available for many more languages.&lt;/p&gt;
2248 </description>
2249 </item>
2250
2251 <item>
2252 <title>One in two hundred Debian users using ZFS on Linux?</title>
2253 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
2254 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
2255 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
2256 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
2257 packages in Debian, and was quite surprised with what I found. I use
2258 ZFS myself at home, but did not really expect many others to do so.
2259 But I might be wrong.&lt;/p&gt;
2260
2261 &lt;p&gt;According to
2262 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
2263 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
2264 0.53% of the population, with the package installed. As far as I know
2265 the only use of the spl-linux package is as a support library for ZFS
2266 on Linux, so I use it here as proxy for measuring the number of ZFS
2267 installation on Linux in Debian. In the kFreeBSD variant of Debian
2268 the ZFS feature is already available, and there
2269 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
2270 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
2271 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
2272
2273 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
2274 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
2275 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
2276 cleared, the package is still not in Debian. The package is again in
2277 the NEW queue. Several uploads have been rejected so far because the
2278 debian/copyright file was incomplete or wrong, but there is no reason
2279 to give up. The current status can be seen on
2280 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
2281 team status page&lt;/a&gt;, and
2282 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
2283 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
2284
2285 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
2286 my home server can function in the future using only official Debian
2287 packages, and the current blocker is to get the debian/copyright file
2288 accepted by the FTP masters in Debian, I decided a while back to try
2289 to help out the team. This was the background for my blog post about
2290 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
2291 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
2292 used the techniques I explored there to try to find any errors in the
2293 copyright file. It is not very easy to check every one of the around
2294 2000 files in the source package, but I hope we this time got it
2295 right. If you want to help out, check out the git source and try to
2296 find missing entries in the debian/copyright file.&lt;/p&gt;
2297 </description>
2298 </item>
2299
2300 <item>
2301 <title>Full battery stats collector is now available in Debian</title>
2302 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
2303 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
2304 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
2305 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
2306 extended collector that will collect the complete battery history for
2307 later processing and graphing. The original collector store the
2308 battery level as percentage of last full level, while the new
2309 collector also record battery vendor, model, serial number, design
2310 full level, last full level and current battery level. This make it
2311 possible to predict the lifetime of the battery as well as visualise
2312 the energy flow when the battery is charging or discharging.&lt;/p&gt;
2313
2314 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
2315 in the version 0.5.1 package in unstable. Get the new battery level graph
2316 and lifetime prediction by running:
2317
2318 &lt;p&gt;&lt;pre&gt;
2319 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2320 &lt;/pre&gt;&lt;/p&gt;
2321
2322 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
2323
2324 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
2325 entry yet):&lt;/p&gt;
2326
2327 &lt;p&gt;&lt;pre&gt;
2328 /usr/share/battery-stats/battery-stats-graph-flow
2329 &lt;/pre&gt;&lt;/p&gt;
2330
2331 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
2332 when there are few data points. The graphs look a bit better with a
2333 few years of data.&lt;/p&gt;
2334
2335 &lt;p&gt;A while back one important feature I use in the battery stats
2336 collector broke in Debian. The scripts in
2337 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
2338 suspect it happened when Jessie started using systemd, but I do not
2339 know. The issue is reported as
2340 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
2341 pm-utils. I managed to work around it by adding an udev rule to call
2342 the collector script every time the power connector is connected and
2343 disconnected. With this fix in place it was finally time to make a
2344 new release of the package, and get it into Debian.&lt;/p&gt;
2345
2346 &lt;p&gt;If you are interested in how your laptop battery is doing, please
2347 check out the
2348 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
2349 in Debian unstable, or rebuild it on Jessie to get it working on
2350 Debian stable. :) The upstream source is available from
2351 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2352 As always, patches are very welcome.&lt;/p&gt;
2353 </description>
2354 </item>
2355
2356 <item>
2357 <title>Making battery measurements a little easier in Debian</title>
2358 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
2359 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
2360 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
2361 <description>&lt;p&gt;Back in September, I blogged about
2362 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
2363 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
2364 how it showed the decay and death of this battery (now replaced). I
2365 created a simple deb package to handle the collection and graphing,
2366 but did not want to upload it to Debian as there were already
2367 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
2368 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
2369 a point of uploading a competing package when battery-stats could be
2370 fixed instead. I reported a few bugs about its non-function, and
2371 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
2372
2373 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
2374 hands. The end result is that I am now the new upstream developer of
2375 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
2376 battery-stats in Debian, and the package in Debian unstable is finally
2377 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
2378 information provided by the Linux kernel. If you install the
2379 battery-stats package from unstable now, you will be able to get a
2380 graph of the current battery fill level, to get some idea about the
2381 status of the battery. The source package build and work just fine in
2382 Debian testing and stable (and probably oldstable too, but I have not
2383 tested). The default graph you get for that system look like this:&lt;/p&gt;
2384
2385 &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;
2386
2387 &lt;p&gt;My plans for the future is to merge my old scripts into the
2388 battery-stats package, as my old scripts collected a lot more details
2389 about the battery. The scripts are merged into the upstream
2390 battery-stats git repository already, but I am not convinced they work
2391 yet, as I changed a lot of paths along the way. Will have to test a
2392 bit more before I make a new release.&lt;/p&gt;
2393
2394 &lt;p&gt;I will also consider changing the file format slightly, as I
2395 suspect the way I combine several values into one field might make it
2396 impossible to know the type of the value when using it for processing
2397 and graphing.&lt;/p&gt;
2398
2399 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
2400 battery, check out the battery-stats package in
2401 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
2402 on
2403 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
2404 I would love some help to improve the system further.&lt;/p&gt;
2405 </description>
2406 </item>
2407
2408 <item>
2409 <title>Creating, updating and checking debian/copyright semi-automatically</title>
2410 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
2411 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
2412 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
2413 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
2414 details. And one of the details is the content of the
2415 debian/copyright file, which should list all relevant licenses used by
2416 the code in the package in question, preferably in
2417 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
2418 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
2419
2420 &lt;p&gt;For large packages with lots of contributors it is hard to write
2421 and update this file manually, and if you get some detail wrong, the
2422 package is normally rejected by the ftpmasters. So getting it right
2423 the first time around get the package into Debian faster, and save
2424 both you and the ftpmasters some work.. Today, while trying to figure
2425 out what was wrong with
2426 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
2427 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
2428 figuring out the options for doing this job automatically, or at least
2429 semi-automatically.&lt;/p&gt;
2430
2431 &lt;p&gt;Lucikly, there are at least two tools available for generating the
2432 file based on the code in the source package,
2433 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
2434 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
2435 not sure which one of them came first, but both seem to be able to
2436 create a sensible draft file. As far as I can tell, none of them can
2437 be trusted to get the result just right, so the content need to be
2438 polished a bit before the file is OK to upload. I found the debmake
2439 option in
2440 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
2441 blog posts from 2014&lt;/a&gt;.
2442
2443 &lt;p&gt;To generate using debmake, use the -cc option:
2444
2445 &lt;p&gt;&lt;pre&gt;
2446 debmake -cc &gt; debian/copyright
2447 &lt;/pre&gt;&lt;/p&gt;
2448
2449 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
2450 this might not be the best option.&lt;/p&gt;
2451
2452 &lt;p&gt;The cme option is based on a config parsing library, and I found
2453 this approach in
2454 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
2455 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
2456 dpkg-copyright&#39; option:
2457
2458 &lt;p&gt;&lt;pre&gt;
2459 cme update dpkg-copyright
2460 &lt;/pre&gt;&lt;/p&gt;
2461
2462 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
2463 handle UTF-8 names better than debmake.&lt;/p&gt;
2464
2465 &lt;p&gt;When the copyright file is created, I would also like some help to
2466 check if the file is correct. For this I found two good options,
2467 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
2468 to focus on license types and file matching, and is able to detect
2469 ineffective blocks in the copyright file. The latter reports missing
2470 copyright holders and years, but was confused by inconsistent license
2471 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
2472 fix all issues reported by them before uploading. But I do not know
2473 if the tools and the ftpmasters agree on what is important to fix in a
2474 copyright file, so the package might still be rejected.&lt;/p&gt;
2475
2476 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
2477 will read through the source and try to find all copyright statements.
2478 It is not comparing the result to the content of debian/copyright, but
2479 can be useful when verifying the content of the copyright file.&lt;/p&gt;
2480
2481 &lt;p&gt;Are you aware of better tools in Debian to create and update
2482 debian/copyright file. Please let me know, or blog about it on
2483 planet.debian.org.&lt;/p&gt;
2484
2485 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2486 activities, please send Bitcoin donations to my address
2487 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2488
2489 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
2490 on how to use licensecheck and cdbs to create a draft copyright file
2491
2492 &lt;p&gt;&lt;pre&gt;
2493 licensecheck --copyright -r `find * -type f` | \
2494 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
2495 &lt;/pre&gt;&lt;/p&gt;
2496
2497 &lt;p&gt;He mentioned that he normally check the generated file into the
2498 version control system to make it easier to discover license and
2499 copyright changes in the upstream source. I will try to do the same
2500 with my packages in the future.&lt;/p&gt;
2501
2502 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
2503 against using -quiet for new users, so I removed it from the proposed
2504 command line.&lt;/p&gt;
2505 </description>
2506 </item>
2507
2508 <item>
2509 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
2510 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
2511 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
2512 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
2513 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
2514 is taking shape in Debian, and one provided feature is a very
2515 convenient way to tell you which package to install to make a given
2516 firmware file available when the kernel is looking for it. This can
2517 be done using apt-file too, but that is for someone else to blog
2518 about. :)&lt;/p&gt;
2519
2520 &lt;p&gt;Here is a small recipe to find the package with a given firmware
2521 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
2522 picked from the set of firmware announced using appstream in Debian
2523 unstable. In general you would be looking for the firmware requested
2524 by the kernel during kernel module loading. To find the package
2525 providing the example file, do like this:&lt;/p&gt;
2526
2527 &lt;blockquote&gt;&lt;pre&gt;
2528 % apt install appstream
2529 [...]
2530 % apt update
2531 [...]
2532 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
2533 awk &#39;/Package:/ {print $2}&#39;
2534 firmware-qlogic
2535 %
2536 &lt;/pre&gt;&lt;/blockquote&gt;
2537
2538 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
2539 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
2540 a way appstream can use.&lt;/p&gt;
2541
2542 &lt;p&gt;This same approach can be used to find any package supporting a
2543 given MIME type. This is very useful when you get a file you do not
2544 know how to handle. First find the mime type using &lt;tt&gt;file
2545 --mime-type&lt;/tt&gt;, and next look up the package providing support for
2546 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2547 and you can find all packages handling this type like this:&lt;/p&gt;
2548
2549 &lt;blockquote&gt;&lt;pre&gt;
2550 % apt install appstream
2551 [...]
2552 % apt update
2553 [...]
2554 % appstreamcli what-provides mimetype image/svg+xml | \
2555 awk &#39;/Package:/ {print $2}&#39;
2556 bkchem
2557 phototonic
2558 inkscape
2559 shutter
2560 tetzle
2561 geeqie
2562 xia
2563 pinta
2564 gthumb
2565 karbon
2566 comix
2567 mirage
2568 viewnior
2569 postr
2570 ristretto
2571 kolourpaint4
2572 eog
2573 eom
2574 gimagereader
2575 midori
2576 %
2577 &lt;/pre&gt;&lt;/blockquote&gt;
2578
2579 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
2580 packages providing appstream metadata.&lt;/p&gt;
2581 </description>
2582 </item>
2583
2584 <item>
2585 <title>Creepy, visualise geotagged social media information - nice free software</title>
2586 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
2587 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
2588 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
2589 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
2590 with the computerised radio beacon known as a mobile phone their
2591 position is tracked by the phone company and often stored for a long
2592 time (like every time a SMS is received or sent). And if their
2593 computerised radio beacon is capable of running programs (often called
2594 mobile apps) downloaded from the Internet, these programs are often
2595 also capable of tracking their location (if the app requested access
2596 during installation). And when these programs send out information to
2597 central collection points, the location is often included, unless
2598 extra care is taken to not send the location. The provided
2599 information is used by several entities, for good and bad (what is
2600 good and bad, depend on your point of view). What is certain, is that
2601 the private sphere and the right to free movement is challenged and
2602 perhaps even eradicated for those announcing their location this way,
2603 when they share their whereabouts with private and public
2604 entities.&lt;/p&gt;
2605
2606 &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;
2607
2608 &lt;p&gt;The phone company logs provide a register of locations to check out
2609 when one want to figure out what the tracked person was doing. It is
2610 unavailable for most of us, but provided to selected government
2611 officials, company staff, those illegally buying information from
2612 unfaithful servants and crackers stealing the information. But the
2613 public information can be collected and analysed, and a free software
2614 tool to do so is called
2615 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
2616 discovered it when I read
2617 &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
2618 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
2619 November 2014, and decided to check if it was available in Debian.
2620 The python program was in Debian, but
2621 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
2622 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
2623 uploaded a new version which did not work quite right, but did not
2624 have time to fix it then. This Christmas I decided to finally try to
2625 get Creepy operational in Debian. Now a fixed version is available in
2626 Debian unstable and testing, and almost all Debian specific patches
2627 are now included
2628 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
2629
2630 &lt;p&gt;The Creepy program visualises geolocation information fetched from
2631 Twitter, Instagram, Flickr and Google+, and allow one to get a
2632 complete picture of every social media message posted recently in a
2633 given area, or track the movement of a given individual across all
2634 these services. Earlier it was possible to use the search API of at
2635 least some of these services without identifying oneself, but these
2636 days it is impossible. This mean that to use Creepy, you need to
2637 configure it to log in as yourself on these services, and provide
2638 information to them about your search interests. This should be taken
2639 into account when using Creepy, as it will also share information
2640 about yourself with the services.&lt;/p&gt;
2641
2642 &lt;p&gt;The picture above show the twitter messages sent from (or at least
2643 geotagged with a position from) the city centre of Oslo, the capital
2644 of Norway. One useful way to use Creepy is to first look at
2645 information tagged with an area of interest, and next look at all the
2646 information provided by one or more individuals who was in the area.
2647 I tested it by checking out which celebrity provide their location in
2648 twitter messages by checkout out who sent twitter messages near a
2649 Norwegian TV station, and next could track their position over time,
2650 making it possible to locate their home and work place, among other
2651 things. A similar technique have been
2652 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
2653 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
2654 tool to discover lying governments, and a useful tool to help people
2655 understand the value of the private information they provide to the
2656 public.&lt;/p&gt;
2657
2658 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
2659 it depend on several python modules currently missing in Jessie (at
2660 least python-instagram, python-flickrapi and
2661 python-requests-toolbelt).&lt;/p&gt;
2662
2663 &lt;p&gt;(I have uploaded
2664 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
2665 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
2666 Creepy program in Debian.)&lt;/p&gt;
2667 </description>
2668 </item>
2669
2670 <item>
2671 <title>Always download Debian packages using Tor - the simple recipe</title>
2672 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
2673 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
2674 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
2675 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
2676 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
2677 that those listening on the Internet lines would have good reason to
2678 believe a computer have a given security hole&lt;/a&gt; if it download a
2679 security fix from a Debian mirror. This is a good reason to always
2680 use encrypted connections to the Debian mirror, to make sure those
2681 listening do not know which IP address to attack. In August, Richard
2682 Hartmann observed that encryption was not enough, when it was possible
2683 to interfere download size to security patches or the fact that
2684 download took place shortly after a security fix was released, and
2685 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
2686 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
2687 was not the first to propose this, as the
2688 &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;
2689 package by Tim Retout already existed to make it easy to convince apt
2690 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
2691 aware of that package when I read the blog post from Richard.&lt;/p&gt;
2692
2693 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
2694 sysadmins, and he set up a Tor hidden service on one of the central
2695 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2696 it possible to download packages directly between two tor nodes,
2697 making sure the network traffic always were encrypted.&lt;/p&gt;
2698
2699 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
2700 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
2701 urls with tor+http and tor+https, and using the hidden service instead
2702 of the official Debian mirror site. I recommend installing
2703 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
2704 done in /etc/.&lt;/p&gt;
2705
2706 &lt;blockquote&gt;&lt;pre&gt;
2707 apt install apt-transport-tor
2708 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
2709 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
2710 &lt;/pre&gt;&lt;/blockquote&gt;
2711
2712 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
2713 the sed commands for these too. The sed command is assuming your are
2714 using the ftp.debian.org Debian mirror. Adjust the command (or just
2715 edit the file manually) to match your mirror.&lt;/p&gt;
2716
2717 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
2718 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
2719 system, and do not work with these tor+http URLs. For
2720 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
2721 which need a recent apt version currently only in unstable. So if you
2722 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
2723
2724 &lt;p&gt;Another advantage from this change is that your machine will start
2725 using Tor regularly and at fairly random intervals (every time you
2726 update the package lists or upgrade or install a new package), thus
2727 masking other Tor traffic done from the same machine. Using Tor will
2728 become normal for the machine in question.&lt;/p&gt;
2729
2730 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
2731 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
2732 enabled. It would be great if it was the default on any Debian
2733 system.&lt;/p&gt;
2734 </description>
2735 </item>
2736
2737 <item>
2738 <title>OpenALPR, find car license plates in video streams - nice free software</title>
2739 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
2740 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
2741 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
2742 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
2743 call the car license plate numbers in those days. I would write the
2744 numbers down in my little book and compare notes with the other kids
2745 to see how many region codes we had seen and if we had seen some
2746 exotic or special region codes and numbers. It was a fun game to pass
2747 time, as we kids have plenty of it.&lt;/p&gt;
2748
2749 &lt;p&gt;A few days I came across
2750 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
2751 project&lt;/a&gt;, a free software project to automatically discover and
2752 report license plates in images and video streams, and provide the
2753 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
2754 such system for a while now, because I believe it is a bad idea that the
2755 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
2756 number plate recognition&lt;/a&gt; tool only is available in the hands of
2757 the powerful, and want it to be available also for the powerless to
2758 even the score when it comes to surveillance and sousveillance. I
2759 discovered the developer
2760 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
2761 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
2762 help him get it into shape to get the package uploaded into the Debian
2763 archive.&lt;/p&gt;
2764
2765 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
2766 it into Debian, where it currently
2767 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
2768 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
2769
2770 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
2771 for the common folks, ie those not running a large government
2772 surveillance system? Well, I plan to put it in a computer on my bike
2773 and in my car, tracking the cars nearby and allowing me to be notified
2774 when number plates on my watch list are discovered. Another use case
2775 was suggested by a friend of mine, who wanted to set it up at his home
2776 to open the car port automatically when it discovered the plate on his
2777 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2778 capable of placing his license plate number of a piece of cardboard to
2779 open his car port, men replied that it was always unlocked anyway. I
2780 guess for such use case it make sense. I am sure there are other use
2781 cases too, for those with imagination and a vision.&lt;/p&gt;
2782
2783 &lt;p&gt;If you want to build your own version of the Debian package, check
2784 out the upstream git source and symlink ./distros/debian to ./debian/
2785 before running &quot;debuild&quot; to build the source. Or wait a bit until the
2786 package show up in unstable.&lt;/p&gt;
2787 </description>
2788 </item>
2789
2790 <item>
2791 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
2792 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
2793 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
2794 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
2795 <description>&lt;p&gt;Around three years ago, I created
2796 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
2797 system&lt;/a&gt; to get a more practical solution in Debian for handing
2798 hardware related packages. A GUI system in the isenkram package will
2799 present a pop-up dialog when some hardware dongle supported by
2800 relevant packages in Debian is inserted into the machine. The same
2801 lookup mechanism to detect packages is available as command line
2802 tools in the isenkram-cli package. In addition to mapping hardware,
2803 it will also map kernel firmware files to packages and make it easy to
2804 install needed firmware packages automatically. The key for this
2805 system to work is a good way to map hardware to packages, in other
2806 words, allow packages to announce what hardware they will work
2807 with.&lt;/p&gt;
2808
2809 &lt;p&gt;I started by providing data files in the isenkram source, and
2810 adding code to download the latest version of these data files at run
2811 time, to ensure every user had the most up to date mapping available.
2812 I also added support for storing the mapping in the Packages file in
2813 the apt repositories, but did not push this approach because while I
2814 was trying to figure out how to best store hardware/package mappings,
2815 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
2816 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
2817 add the hardware mapping into that data set to be able to use
2818 appstream as a data source, and this was accepted at least for the
2819 Debian version of appstream.&lt;/p&gt;
2820
2821 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
2822 and today I uploaded a new version 0.20 of isenkram adding support for
2823 appstream as a data source for mapping hardware to packages. The only
2824 package so far using appstream to announce its hardware support is my
2825 pymissile package. I got help from Matthias Klumpp with figuring out
2826 how do add the required
2827 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
2828 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
2829 this content:&lt;/p&gt;
2830
2831 &lt;blockquote&gt;&lt;pre&gt;
2832 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
2833 &amp;lt;component&amp;gt;
2834 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
2835 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
2836 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
2837 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
2838 &amp;lt;description&amp;gt;
2839 &amp;lt;p&amp;gt;
2840 Pymissile provides a curses interface to control an original
2841 Marks and Spencer / Striker USB Missile Launcher, as well as a
2842 motion control script to allow a webcamera to control the
2843 launcher.
2844 &amp;lt;/p&amp;gt;
2845 &amp;lt;/description&amp;gt;
2846 &amp;lt;provides&amp;gt;
2847 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
2848 &amp;lt;/provides&amp;gt;
2849 &amp;lt;/component&amp;gt;
2850 &lt;/pre&gt;&lt;/blockquote&gt;
2851
2852 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
2853 which is a glob style match rule for hardware specific strings
2854 (modalias strings) provided by the Linux kernel. In this case, it
2855 will map to all USB devices with vendor code 1130 and product code
2856 0202.&lt;/p&gt;
2857
2858 &lt;p&gt;Note, it is important that the license of all the metadata files
2859 are compatible to have permissions to aggregate them into archive wide
2860 appstream files. Matthias suggested to use MIT or BSD licenses for
2861 these files. A challenge is figuring out a good id for the data, as
2862 it is supposed to be globally unique and shared across distributions
2863 (in other words, best to coordinate with upstream what to use). But
2864 it can be changed later or, so we went with the package name as
2865 upstream for this project is dormant.&lt;/p&gt;
2866
2867 &lt;p&gt;To get the metadata file installed in the correct location for the
2868 mirror update scripts to pick it up and include its content the
2869 appstream data source, the file must be installed in the binary
2870 package under /usr/share/appdata/. I did this by adding the following
2871 line to debian/pymissile.install:&lt;/p&gt;
2872
2873 &lt;blockquote&gt;&lt;pre&gt;
2874 debian/pymissile.metainfo.xml usr/share/appdata
2875 &lt;/pre&gt;&lt;/blockquote&gt;
2876
2877 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
2878 all packages useful on the current computer automatically, and the GUI
2879 pop-up handler will propose to install the package not already
2880 installed if a hardware dongle is inserted into the machine in
2881 question.&lt;/p&gt;
2882
2883 &lt;p&gt;Details of the modalias field in appstream is available from the
2884 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
2885
2886 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
2887 try running this command on the command line:&lt;/p&gt;
2888
2889 &lt;blockquote&gt;&lt;pre&gt;
2890 cat $(find /sys/devices/|grep modalias)
2891 &lt;/pre&gt;&lt;/blockquote&gt;
2892
2893 &lt;p&gt;To learn more about the isenkram system, please check out
2894 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
2895 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
2896 </description>
2897 </item>
2898
2899 <item>
2900 <title>The GNU General Public License is not magic pixie dust</title>
2901 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
2902 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
2903 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
2904 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
2905 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
2906 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
2907 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
2908 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
2909
2910 &lt;blockquote&gt;
2911
2912 &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;
2913
2914 &lt;blockquote&gt;
2915 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
2916
2917 The first step is to choose a
2918 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
2919 code.&lt;br/&gt;
2920
2921 The next step is, when someone fails to follow that copyleft license,
2922 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
2923
2924 and its a simple fact of our modern society that such type of
2925 work&lt;br/&gt;
2926
2927 is incredibly expensive to do and incredibly difficult to do.
2928 &lt;/blockquote&gt;
2929
2930 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
2931 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
2932 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
2933 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
2934
2935 &lt;p&gt;As the Debian Website
2936 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
2937 &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;
2938 imply, public domain and permissively licensed software can lead to
2939 the production of more proprietary software as people discover useful
2940 software, extend it and or incorporate it into their hardware or
2941 software products. Copyleft licenses such as the GNU GPL were created
2942 to close off this avenue to the production of proprietary software but
2943 such licenses are not enough. With the ongoing adoption of Free
2944 Software by individuals and groups, inevitably the community&#39;s
2945 expectations of license compliance are violated, usually out of
2946 ignorance of the way Free Software works, but not always. As Karen
2947 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
2948 Freedom&quot;&gt;FaiF&lt;/a&gt;
2949 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
2950 copyleft is nothing if no-one is willing and able to stand up in court
2951 to protect it. The reality of today&#39;s world is that legal
2952 representation is expensive, difficult and time consuming. With
2953 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
2954 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
2955 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
2956 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
2957 of the Linux project, Debian and other groups against GPL violations.
2958 In March the SFC supported a
2959 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
2960 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
2961 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
2962 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
2963 kernel. Since then two of their sponsors pulled corporate funding and
2964 conferences
2965 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
2966 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
2967 less on corporate funding and more on the broad community of
2968 individuals who support Free Software and copyleft. So the SFC has
2969 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
2970 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
2971 a community of folks who stand up for copyleft and the GPL by
2972 supporting their work on promoting and supporting copyleft and Free
2973 Software.&lt;/p&gt;
2974
2975 &lt;p&gt;If you support Free Software,
2976 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
2977 what the SFC do, agree with their
2978 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
2979 principles&lt;/a&gt;, are happy about their
2980 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
2981 work on a project that is an SFC
2982 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
2983 just want to stand up for copyleft, please join
2984 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
2985 Allan Webber&lt;/a&gt;,
2986 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
2987 Smith&lt;/a&gt;,
2988 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
2989 Bacon&lt;/a&gt;, myself and
2990 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
2991 becoming a
2992 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
2993 next week your donation will be
2994 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
2995 by an anonymous donor. Please also consider asking your employer to
2996 match your donation or become a sponsor of SFC. Don&#39;t forget to
2997 spread the word about your support for SFC via email, your blog and or
2998 social media accounts.&lt;/p&gt;
2999
3000 &lt;/blockquote&gt;
3001
3002 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
3003 of Software Freedom Conservancy myself. Perhaps you should be a
3004 supporter too?&lt;/p&gt;
3005 </description>
3006 </item>
3007
3008 <item>
3009 <title>PGP key transition statement for key EE4E02F9</title>
3010 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
3011 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
3012 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
3013 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
3014 set it up properly. I wanted to generate it offline and have it
3015 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
3016 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
3017 time to sit down with an offline machine almost took forever. But
3018 finally I&#39;ve been able to complete the process, and have now moved
3019 from my old GPG key to a new GPG key. See
3020 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
3021 full transition statement, signed with both my old and new key&lt;/a&gt; for
3022 the details. This is my new key:&lt;/p&gt;
3023
3024 &lt;pre&gt;
3025 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]
3026 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
3027 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
3028 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
3029 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
3030 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
3031 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
3032 &lt;/pre&gt;
3033
3034 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
3035 my old key.&lt;/p&gt;
3036
3037 &lt;p&gt;If you signed my old key
3038 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
3039 I&#39;d very much appreciate a signature on my new key, details and
3040 instructions in the transition statement. I m happy to reciprocate if
3041 you have a similarly signed transition statement to present.&lt;/p&gt;
3042 </description>
3043 </item>
3044
3045 <item>
3046 <title>The life and death of a laptop battery</title>
3047 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
3048 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
3049 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
3050 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
3051 But this do not last. The last few laptops gave me a feeling that
3052 within a year, the life time is just a fraction of what it used to be,
3053 and it slowly become painful to use the laptop without power connected
3054 all the time. Because of this, when I got a new Thinkpad X230 laptop
3055 about two years ago, I decided to monitor its battery state to have
3056 more hard facts when the battery started to fail.&lt;/p&gt;
3057
3058 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
3059
3060 &lt;p&gt;First I tried to find a sensible Debian package to record the
3061 battery status, assuming that this must be a problem already handled
3062 by someone else. I found
3063 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
3064 which collects statistics from the battery, but it was completely
3065 broken. I sent a few suggestions to the maintainer, but decided to
3066 write my own collector as a shell script while I waited for feedback
3067 from him. Via
3068 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
3069 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
3070 discovered
3071 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
3072 available in Debian.&lt;/p&gt;
3073
3074 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
3075 battery stats ever since. Now my
3076 /var/log/hjemmenett-battery-status.log file contain around 115,000
3077 measurements, from the time the battery was working great until now,
3078 when it is unable to charge above 7% of original capacity. My
3079 collector shell script is quite simple and look like this:&lt;/p&gt;
3080
3081 &lt;pre&gt;
3082 #!/bin/sh
3083 # Inspired by
3084 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
3085 # See also
3086 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
3087 logfile=/var/log/hjemmenett-battery-status.log
3088
3089 files=&quot;manufacturer model_name technology serial_number \
3090 energy_full energy_full_design energy_now cycle_count status&quot;
3091
3092 if [ ! -e &quot;$logfile&quot; ] ; then
3093 (
3094 printf &quot;timestamp,&quot;
3095 for f in $files; do
3096 printf &quot;%s,&quot; $f
3097 done
3098 echo
3099 ) &gt; &quot;$logfile&quot;
3100 fi
3101
3102 log_battery() {
3103 # Print complete message in one echo call, to avoid race condition
3104 # when several log processes run in parallel.
3105 msg=$(printf &quot;%s,&quot; $(date +%s); \
3106 for f in $files; do \
3107 printf &quot;%s,&quot; $(cat $f); \
3108 done)
3109 echo &quot;$msg&quot;
3110 }
3111
3112 cd /sys/class/power_supply
3113
3114 for bat in BAT*; do
3115 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
3116 done
3117 &lt;/pre&gt;
3118
3119 &lt;p&gt;The script is called when the power management system detect a
3120 change in the power status (power plug in or out), and when going into
3121 and out of hibernation and suspend. In addition, it collect a value
3122 every 10 minutes. This make it possible for me know when the battery
3123 is discharging, charging and how the maximum charge change over time.
3124 The code for the Debian package
3125 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
3126 available on github&lt;/a&gt;.&lt;/p&gt;
3127
3128 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
3129
3130 &lt;pre&gt;
3131 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3132 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
3133 [...]
3134 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3135 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
3136 &lt;/pre&gt;
3137
3138 &lt;p&gt;I wrote a small script to create a graph of the charge development
3139 over time. This graph depicted above show the slow death of my laptop
3140 battery.&lt;/p&gt;
3141
3142 &lt;p&gt;But why is this happening? Why are my laptop batteries always
3143 dying in a year or two, while the batteries of space probes and
3144 satellites keep working year after year. If we are to believe
3145 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
3146 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
3147 chance, and the fix is to not charge the Lithium-ion batteries to 100%
3148 all the time, but to stay below 90% of full charge most of the time.
3149 I&#39;ve been told that the Tesla electric cars
3150 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
3151 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
3152 100% when preparing for a longer trip (not that I would want a car
3153 like Tesla where rights to privacy is abandoned, but that is another
3154 story), which I guess is the option we should have for laptops on
3155 Linux too.&lt;/p&gt;
3156
3157 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
3158 stop charging at 80%, unless requested to charge to 100% once in
3159 preparation for a longer trip? I found
3160 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
3161 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3162 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
3163 load).&lt;/p&gt;
3164
3165 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
3166 at the start. I also wonder why the &quot;full capacity&quot; increases some
3167 times, and if it is possible to repeat the process to get the battery
3168 back to design capacity. And I wonder if the discharge and charge
3169 speed change over time, or if this stay the same. I did not yet try
3170 to write a tool to calculate the derivative values of the battery
3171 level, but suspect some interesting insights might be learned from
3172 those.&lt;/p&gt;
3173
3174 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
3175 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3176 packages instead of the tp-smapi-dkms package I had tried to use
3177 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
3178 and stop. I&#39;ve done so now, but expect my existing battery is toast
3179 and need to be replaced. The proposal is unfortunately Thinkpad
3180 specific.&lt;/p&gt;
3181 </description>
3182 </item>
3183
3184 <item>
3185 <title>New laptop - some more clues and ideas based on feedback</title>
3186 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
3187 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
3188 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
3189 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
3190 need for a new laptop, and provided very useful feedback. I wish to
3191 thank every one of these. Several pointed me to the possibility of
3192 fixing my X230, and I am already in the process of getting Lenovo to
3193 do so thanks to the on site, next day support contract covering the
3194 machine. But the battery is almost useless (I expect to replace it
3195 with a non-official battery) and I do not expect the machine to live
3196 for many more years, so it is time to plan its replacement. If I did
3197 not have a support contract, it was suggested to find replacement parts
3198 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
3199 might present a language barrier as I do not understand French.&lt;/p&gt;
3200
3201 &lt;p&gt;One tip I got was to use the
3202 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
3203 compare laptop models. It seem to have more models available than
3204 prisjakt.no. Another tip I got from someone I know have similar
3205 keyboard preferences was that the HP EliteBook 840 keyboard is not
3206 very good, and this matches my experience with earlier EliteBook
3207 keyboards I tested. Because of this, I will not consider it any further.
3208
3209 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
3210 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3211 (which is missing from the X240), and is working fairly well with
3212 Debian Sid/Unstable according to
3213 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
3214 got on the keyboard quality are not consistent. Some say the keyboard
3215 is good, others say it is ok, while others say it is not very good.
3216 Those with experience from X41 and and X60 agree that the X250
3217 keyboard is not as good as those trusty old laptops, and suggest I
3218 keep and fix my X230 instead of upgrading, or get a used X230 to
3219 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
3220 activity and battery status, which is very convenient on my X230. I&#39;m
3221 also told that the CPU fan is running very often, making it a bit
3222 noisy. In any case, the X250 do not work out of the box with Debian
3223 Stable/Jessie, one of my requirements.&lt;/p&gt;
3224
3225 &lt;p&gt;I have also gotten a few vendor proposals, one was
3226 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
3227 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
3228 The latter look very attractive to me.&lt;/p&gt;
3229
3230 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
3231 as I keep looking for a replacement.&lt;/p&gt;
3232
3233 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
3234 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
3235 different
3236 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
3237 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
3238 </description>
3239 </item>
3240
3241 <item>
3242 <title>Time to find a new laptop, as the old one is broken after only two years</title>
3243 <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>
3244 <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>
3245 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
3246 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
3247 replacement soon. The left 5 cm of the screen on my Thinkpad X230
3248 started flickering yesterday, and I suspect the cause is a broken
3249 cable, as changing the angle of the screen some times get rid of the
3250 flickering.&lt;/p&gt;
3251
3252 &lt;p&gt;My requirements have not really changed since I bought it, and is
3253 still as
3254 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
3255 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
3256 good help from
3257 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
3258 where I could select at least a few of the requirements (mouse pin,
3259 wifi, weight) and go through the rest manually. Three button mouse
3260 and a good keyboard is not available as an option, and all the three
3261 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
3262 G2) lack three mouse buttons). It is also unclear to me how good the
3263 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3264 the keyboard, even if the quality and robustness in the X series have
3265 deteriorated since X41.&lt;/p&gt;
3266
3267 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
3268 seem sensible to me? Are there better services around to search the
3269 set of available laptops for features? Please send me an email if you
3270 have suggestions.&lt;/p&gt;
3271
3272 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
3273 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
3274 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
3275 </description>
3276 </item>
3277
3278 <item>
3279 <title>How to stay with sysvinit in Debian Jessie</title>
3280 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
3281 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
3282 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
3283 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
3284 sysvinit as its boot system by default. But how can one keep using
3285 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3286 courtesy of
3287 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
3288 Schubert&lt;/a&gt; and
3289 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
3290 McVittie&lt;/a&gt;.
3291
3292 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
3293 keep sysvinit as your boot system, create a file
3294 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
3295 you upgrade:&lt;/p&gt;
3296
3297 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3298 Package: systemd-sysv
3299 Pin: release o=Debian
3300 Pin-Priority: -1
3301 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3302
3303 &lt;p&gt;This file content will tell apt and aptitude to not consider
3304 installing systemd-sysv as part of any installation and upgrade
3305 solution when resolving dependencies, and thus tell it to avoid
3306 systemd as a default boot system. The end result should be that the
3307 upgraded system keep using sysvinit.&lt;/p&gt;
3308
3309 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
3310 get sysvinit installed by default (debootstrap used by
3311 debian-installer have no option for this), but one can tell the
3312 installer to switch to sysvinit before the first boot. Either by
3313 using a kernel argument to the installer, or by adding a line to the
3314 preseed file used. First, the kernel command line argument:
3315
3316 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3317 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
3318 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3319
3320 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
3321
3322 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3323 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3324 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
3325
3326 &lt;p&gt;One can of course also do this after the first boot by installing
3327 the sysvinit-core package.&lt;/p&gt;
3328
3329 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
3330 sysvinit boot sequence in Debian have several hardware specific bugs
3331 on Linux caused by the fact that it is unpredictable when hardware
3332 devices show up during boot. But on the other hand, the new default
3333 boot system still have a few rough edges I hope will be fixed before
3334 Jessie is released.&lt;/p&gt;
3335
3336 &lt;p&gt;Update 2014-11-26: Inspired by
3337 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
3338 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
3339 line.&lt;/p&gt;
3340 </description>
3341 </item>
3342
3343 <item>
3344 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
3345 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
3346 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
3347 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
3348 <description>&lt;p&gt;The right to communicate with your friends and family in private,
3349 without anyone snooping, is a right every citicen have in a liberal
3350 democracy. But this right is under serious attack these days.&lt;/p&gt;
3351
3352 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
3353 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3354 the whisleblower Snowden) more expensive for Internet email,
3355 is to deliver all email using SMTP via Tor. Such SMTP option would be
3356 a nice addition to the FreedomBox project if we could send email
3357 between FreedomBox machines without leaking metadata about the emails
3358 to the people peeking on the wire. I
3359 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
3360 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
3361 lot of useful feedback and suggestions. It also became obvious to me
3362 that this was not a novel idea, as the same idea was tested and
3363 documented by Johannes Berg as early as 2006, and both
3364 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
3365 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
3366 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
3367
3368 &lt;p&gt;To implement such system one need to set up a Tor hidden service
3369 providing the SMTP protocol on port 25, and use email addresses
3370 looking like username@hidden-service-name.onion. With such addresses
3371 the connections to port 25 on hidden-service-name.onion using Tor will
3372 go to the correct SMTP server. To do this, one need to configure the
3373 Tor daemon to provide the hidden service and the mail server to accept
3374 emails for this .onion domain. To learn more about Exim configuration
3375 in Debian and test the design provided by Johannes Berg in his FAQ, I
3376 set out yesterday to create a Debian package for making it trivial to
3377 set up such SMTP over Tor service based on Debian. Getting it to work
3378 were fairly easy, and
3379 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
3380 source code for the Debian package&lt;/a&gt; is available from github. I
3381 plan to move it into Debian if further testing prove this to be a
3382 useful approach.&lt;/p&gt;
3383
3384 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
3385 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
3386 get rid of exim4). Install tor, clone the git repository mentioned
3387 above, build the deb and install it on the machine. Next, run
3388 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
3389 the instructions to get the service up and running. Restart tor and
3390 exim when it is done, and test mail delivery using swaks like
3391 this:&lt;/p&gt;
3392
3393 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3394 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3395 --to fbx@dutlqrrmjhtfa3vp.onion
3396 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3397
3398 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
3399 address with your own address to test your server. :)&lt;/p&gt;
3400
3401 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
3402 easier and more automatic. Especially the tor setup need more work.
3403 Also, the package include a tor-smtp tool written in C, but its task
3404 should probably be rewritten in some script language to make the deb
3405 architecture independent. It would probably also make the code easier
3406 to review. The tor-smtp tool currently need to listen on a socket for
3407 exim to talk to it and is started using xinetd. It would be better if
3408 no daemon and no socket is needed. I suspect it is possible to get
3409 exim to run a command line tool for delivery instead of talking to a
3410 socket, and hope to figure out how in a future version of this
3411 system.&lt;/p&gt;
3412
3413 &lt;p&gt;Until I wipe my test machine, I can be reached using the
3414 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
3415 SMTorP. :)&lt;/p&gt;
3416 </description>
3417 </item>
3418
3419 <item>
3420 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
3421 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
3422 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
3423 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
3424 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
3425 alioth.debian.org, you know the web interface is fairly slow to
3426 operate. First you visit one web page, enter the moderation password
3427 and get a new page shown with a list of all the messages to moderate
3428 and various options for each email address. This take a while for
3429 every list you moderate, and you need to do it regularly to do a good
3430 job as a list moderator. But there is a quick alternative,
3431 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
3432 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
3433 to moderate in a fraction of a second. Here is a test run on two
3434 lists I recently took over:&lt;/p&gt;
3435
3436 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3437 % time listadmin xiph
3438 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3439 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3440
3441 real 0m1.709s
3442 user 0m0.232s
3443 sys 0m0.012s
3444 %
3445 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3446
3447 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
3448 there are no message in the moderation queue. Every morning I
3449 currently moderate 68 mailman lists, and it normally take around two
3450 minutes. When I took over the two pkg-xiph lists above a few days
3451 ago, there were 400 emails waiting in the moderator queue. It took me
3452 less than 15 minutes to process them all using the listadmin
3453 program.&lt;/p&gt;
3454
3455 &lt;p&gt;If you install
3456 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
3457 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
3458 with content like this, the moderation task is a breeze:&lt;/p&gt;
3459
3460 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3461 username username@example.org
3462 spamlevel 23
3463 default discard
3464 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
3465
3466 password secret
3467 adminurl https://{domain}/mailman/admindb/{list}
3468 mailman-list@lists.example.com
3469
3470 password hidden
3471 other-list@otherserver.example.org
3472 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3473
3474 &lt;p&gt;There are other options to set as well. Check the manual page to
3475 learn the details.&lt;/p&gt;
3476
3477 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
3478 the SSL certificate is self signed or not properly signed by a
3479 generally accepted signing authority, you can set a environment
3480 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
3481
3482 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3483 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
3484 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3485
3486 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
3487 can provide an argument to the listadmin script like I do in the
3488 initial screen dump (the xiph argument). Using an argument, only
3489 lists matching the argument string will be processed. This make it
3490 quick to accept messages if you notice the moderation request in your
3491 email.&lt;/p&gt;
3492
3493 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
3494 mailing lists, as I simply do not have time to spend on that if the
3495 process was any slower. The listadmin program have saved me hours of
3496 time I could spend elsewhere over the years. It truly is nice free
3497 software.&lt;/p&gt;
3498
3499 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3500 activities, please send Bitcoin donations to my address
3501 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3502
3503 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
3504 configuration example. Also, I&#39;ve been told that the
3505 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
3506 sure why.&lt;/p&gt;
3507 </description>
3508 </item>
3509
3510 <item>
3511 <title>Debian Jessie, PXE and automatic firmware installation</title>
3512 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
3513 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
3514 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
3515 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
3516 problem that the WiFi card require some firmware to work properly.
3517 And it has been a pain to fix this using preseeding in Debian.
3518 Normally something more is needed. But thanks to
3519 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
3520 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
3521 to do this using simple preseeding.&lt;/p&gt;
3522
3523 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
3524 firmware for the hardware found in the machine (actually, requested by
3525 the kernel modules for the hardware). (It can also install user space
3526 programs supporting the hardware detected, but that is not the focus
3527 of this story.)&lt;/p&gt;
3528
3529 &lt;p&gt;To get this working in the default installation, two preeseding
3530 values are needed. First, the isenkram-cli package must be installed
3531 into the target chroot (aka the hard drive) before tasksel is executed
3532 in the pkgsel step of the debian-installer system. This is done by
3533 preseeding the base-installer/includes debconf value to include the
3534 isenkram-cli package. The package name is next passed to debootstrap
3535 for installation. With the isenkram-cli package in place, tasksel
3536 will automatically use the isenkram tasks to detect hardware specific
3537 packages for the machine being installed and install them, because
3538 isenkram-cli contain tasksel tasks.&lt;/p&gt;
3539
3540 &lt;p&gt;Second, one need to enable the non-free APT repository, because
3541 most firmware unfortunately is non-free. This is done by preseeding
3542 the apt-mirror-setup step. This is unfortunate, but for a lot of
3543 hardware it is the only option in Debian.&lt;/p&gt;
3544
3545 &lt;p&gt;The end result is two lines needed in your preseeding file to get
3546 firmware installed automatically by the installer:&lt;/p&gt;
3547
3548 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3549 base-installer base-installer/includes string isenkram-cli
3550 apt-mirror-setup apt-setup/non-free boolean true
3551 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3552
3553 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
3554 both firmware and user space packages when using this method. It also
3555 do not work well, so use version 0.15 or later. Installing both
3556 firmware and user space packages might give you a bit more than you
3557 want, so I decided to split the tasksel task in two, one for firmware
3558 and one for user space programs. The firmware task is enabled by
3559 default, while the one for user space programs is not. This split is
3560 implemented in the package currently in unstable.&lt;/p&gt;
3561
3562 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
3563 this recipe work for you. :)&lt;/p&gt;
3564
3565 &lt;p&gt;So, I bet you are wondering, how can this work. First and
3566 foremost, it work because tasksel is modular, and driven by whatever
3567 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3568 isenkram-cli package place two files for tasksel to find. First there
3569 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
3570
3571 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3572 Task: isenkram-packages
3573 Section: hardware
3574 Description: Hardware specific packages (autodetected by isenkram)
3575 Based on the detected hardware various hardware specific packages are
3576 proposed.
3577 Test-new-install: show show
3578 Relevance: 8
3579 Packages: for-current-hardware
3580
3581 Task: isenkram-firmware
3582 Section: hardware
3583 Description: Hardware specific firmware packages (autodetected by isenkram)
3584 Based on the detected hardware various hardware specific firmware
3585 packages are proposed.
3586 Test-new-install: mark show
3587 Relevance: 8
3588 Packages: for-current-hardware-firmware
3589 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3590
3591 &lt;p&gt;The key parts are Test-new-install which indicate how the task
3592 should be handled and the Packages line referencing to a script in
3593 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3594 list of packages to install. The for-current-hardware-firmware script
3595 look like this to list relevant firmware for the machine:
3596
3597 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3598 #!/bin/sh
3599 #
3600 PATH=/usr/sbin:$PATH
3601 export PATH
3602 isenkram-autoinstall-firmware -l
3603 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3604
3605 &lt;p&gt;With those two pieces in place, the firmware is installed by
3606 tasksel during the normal d-i run. :)&lt;/p&gt;
3607
3608 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
3609 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
3610 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
3611 install.&lt;/p&gt;
3612
3613 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
3614 pilots in testing this feature, as isenkram is used there now to
3615 install firmware, replacing the earlier scripts.&lt;/p&gt;
3616 </description>
3617 </item>
3618
3619 <item>
3620 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
3621 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
3622 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
3623 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
3624 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
3625 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3626 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
3627 on a screen normally showing the bread types and prizes:&lt;/p&gt;
3628
3629 &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;
3630
3631 &lt;p&gt;If it had booted as it was supposed to, I would never had known
3632 about this hidden Linux installation. It is interesting what
3633 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
3634 </description>
3635 </item>
3636
3637 <item>
3638 <title>New lsdvd release version 0.17 is ready</title>
3639 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
3640 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
3641 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
3642 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
3643 got a new set of developers a few weeks ago, after the original
3644 developer decided to step down and pass the project to fresh blood.
3645 This project is now maintained by Petter Reinholdtsen and Steve
3646 Dibb.&lt;/p&gt;
3647
3648 &lt;p&gt;I just wrapped up
3649 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
3650 new lsdvd release&lt;/a&gt;, available in git or from
3651 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
3652 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
3653 0.17.&lt;/p&gt;
3654
3655 &lt;ul&gt;
3656
3657 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
3658 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
3659 non-existant, to work around additional copy protection&lt;/li&gt;
3660 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
3661 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
3662 &lt;li&gt;Fix include orders&lt;/li&gt;
3663 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
3664 &lt;li&gt;Fix the chapter count&lt;/li&gt;
3665 &lt;li&gt;Make sure the array size and the array limit used when initialising
3666 the palette size is the same.&lt;/li&gt;
3667 &lt;li&gt;Fix array printing.&lt;/li&gt;
3668 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
3669 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
3670 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
3671 with more GCC compiler warnings.&lt;/li&gt;
3672
3673 &lt;/ul&gt;
3674
3675 &lt;p&gt;This change bring together patches for lsdvd in use in various
3676 Linux and Unix distributions, as well as patches submitted to the
3677 project the last nine years. Please check it out. :)&lt;/p&gt;
3678 </description>
3679 </item>
3680
3681 <item>
3682 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
3683 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
3684 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
3685 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
3686 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
3687 project&lt;/a&gt; provide a Linux solution for schools, including a
3688 powerful desktop with education software, a central server providing
3689 web pages, user database, user home directories, central login and PXE
3690 boot of both clients without disk and the installation to install Debian
3691 Edu on machines with disk (and a few other services perhaps to small
3692 to mention here). We in the Debian Edu team are currently working on
3693 the Jessie based version, trying to get everything in shape before the
3694 freeze, to avoid having to maintain our own package repository in the
3695 future. The
3696 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
3697 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
3698 work left. Some fatal problems block testing, breaking the installer,
3699 but it is possible to work around these to get anyway. Here is a
3700 recipe on how to get the installation limping along.&lt;/p&gt;
3701
3702 &lt;p&gt;First, download the test ISO via
3703 &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;,
3704 &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;
3705 or rsync (use
3706 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
3707 The ISO build was broken on Tuesday, so we do not get a new ISO every
3708 12 hours or so, but thankfully the ISO we already got we are able to
3709 install with some tweaking.&lt;/p&gt;
3710
3711 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
3712 (use Alt-Ctrl-F2), run&lt;/p&gt;
3713
3714 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3715 nano /usr/bin/edu-eatmydata-install
3716 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3717
3718 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
3719 optimization. Return to the installation, select the profile you want
3720 and continue. Without this change, exim4-config will fail to install
3721 due to a known bug in eatmydata.&lt;/p&gt;
3722
3723 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
3724 this do not work, figure out what your correct value would be. All my
3725 test machines need /dev/sda, so I have no advice if it do not fit
3726 your need.&lt;/p&gt;
3727
3728 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
3729 root after the initial boot from hard drive, and install the
3730 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3731 or mate. If you want several desktop options, install more than one
3732 metapackage. Once this is done, reboot and you should have a working
3733 graphical login screen. This workaround should no longer be needed
3734 once the education-tasks package version 1.801 enter testing in two
3735 days.&lt;/p&gt;
3736
3737 &lt;p&gt;I believe the ISO build will start working on two days when the new
3738 tasksel package enter testing and Steve McIntyre get a chance to
3739 update the debian-cd git repository. The eatmydata, grub and desktop
3740 issues are already fixed in unstable and testing, and should show up
3741 on the ISO as soon as the ISO build start working again. Well the
3742 eatmydata optimization is really just disabled. The proper fix
3743 require an upload by the eatmydata maintainer applying the patch
3744 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
3745 The rest have proper fixes in unstable.&lt;/p&gt;
3746
3747 &lt;p&gt;I hope this get you going with the installation testing, as we are
3748 quickly running out of time trying to get our Jessie based
3749 installation ready before the distribution freeze in a month.&lt;/p&gt;
3750 </description>
3751 </item>
3752
3753 <item>
3754 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
3755 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
3756 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
3757 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
3758 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
3759 to handle my fairly large DVD collection. It is a nice command line
3760 tool to get details about a DVD, like title, tracks, track length,
3761 etc, in XML, Perl or human readable format. But lsdvd have not seen
3762 any new development since 2006 and had a few irritating bugs affecting
3763 its use with some DVDs. Upstream seemed to be dead, and in January I
3764 sent a small probe asking for a version control repository for the
3765 project, without any reply. But I use it regularly and would like to
3766 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
3767 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
3768 the project admin, and after getting a reply from him explaining that
3769 he was no longer interested in the project, I asked if I could take
3770 over. And yesterday, I became project admin.&lt;/p&gt;
3771
3772 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
3773 maintainer interested in joining forces to maintain the upstream
3774 project, and I hope we can get a new release out fairly quickly,
3775 collecting the patches spread around on the internet into on place.
3776 I&#39;ve added the relevant Debian patches to the freshly created git
3777 repository, and expect the Gentoo patches to make it too. If you got
3778 a DVD collection and care about command line tools, check out
3779 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
3780 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
3781 list&lt;/a&gt;. :)&lt;/p&gt;
3782 </description>
3783 </item>
3784
3785 <item>
3786 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
3787 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
3788 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
3789 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
3790 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
3791 a lot quicker. When we install more than 2000 packages in
3792 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
3793 tasksel in the installer, unpacking the binary packages take forever.
3794 A part of the slow I/O issue was discussed in
3795 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
3796 much file system sync-ing done by dpkg, which is the package
3797 responsible for unpacking the binary packages. Other parts (like code
3798 executed by postinst scripts) might also sync to disk during
3799 installation. All this sync-ing to disk do not really make sense to
3800 me. If the machine crash half-way through, I start over, I do not try
3801 to salvage the half installed system. So the failure sync-ing is
3802 supposed to protect against, hardware or system crash, is not really
3803 relevant while the installer is running.&lt;/p&gt;
3804
3805 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
3806 system sync()-ing in a fairly non-intrusive way, without the need to
3807 change the code in several packages. The idea is not new, but I have
3808 not heard anyone propose the approach using dpkg-divert before. It
3809 depend on the small and clever package
3810 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
3811 uses LD_PRELOAD to replace the system functions for syncing data to
3812 disk with functions doing nothing, thus allowing programs to live
3813 dangerous while speeding up disk I/O significantly. Instead of
3814 modifying the implementation of dpkg, apt and tasksel (which are the
3815 packages responsible for selecting, fetching and installing packages),
3816 it occurred to me that we could just divert the programs away, replace
3817 them with a simple shell wrapper calling
3818 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
3819 Two days ago I decided to test the idea, and wrapped up a simple
3820 implementation for the Debian Edu udeb.&lt;/p&gt;
3821
3822 &lt;p&gt;The effect was stunning. In my first test it reduced the running
3823 time of the pkgsel step (installing tasks) from 64 to less than 44
3824 minutes (20 minutes shaved off the installation) on an old Dell
3825 Latitude D505 machine. I am not quite sure what the optimised time
3826 would have been, as I messed up the testing a bit, causing the debconf
3827 priority to get low enough for two questions to pop up during
3828 installation. As soon as I saw the questions I moved the installation
3829 along, but do not know how long the question were holding up the
3830 installation. I did some more measurements using Debian Edu Jessie,
3831 and got these results. The time measured is the time stamp in
3832 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
3833 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
3834 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3835 timing thus do not depend on how quickly the user handle the tasksel
3836 dialog.&lt;/p&gt;
3837
3838 &lt;p&gt;&lt;table&gt;
3839
3840 &lt;tr&gt;
3841 &lt;th&gt;Machine/setup&lt;/th&gt;
3842 &lt;th&gt;Original tasksel&lt;/th&gt;
3843 &lt;th&gt;Optimised tasksel&lt;/th&gt;
3844 &lt;th&gt;Reduction&lt;/th&gt;
3845 &lt;/tr&gt;
3846
3847 &lt;tr&gt;
3848 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
3849 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
3850 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
3851 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
3852 &lt;/tr&gt;
3853
3854 &lt;tr&gt;
3855 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
3856 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
3857 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
3858 &lt;td&gt;23 min 40%&lt;/td&gt;
3859 &lt;/tr&gt;
3860
3861 &lt;tr&gt;
3862 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
3863 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
3864 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
3865 &lt;td&gt;11 min 50%&lt;/td&gt;
3866 &lt;/tr&gt;
3867
3868 &lt;tr&gt;
3869 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
3870 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
3871 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
3872 &lt;td&gt;2 min 33%&lt;/td&gt;
3873 &lt;/tr&gt;
3874
3875 &lt;tr&gt;
3876 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
3877 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
3878 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
3879 &lt;td&gt;4 min 21%&lt;/td&gt;
3880 &lt;/tr&gt;
3881
3882 &lt;/table&gt;&lt;/p&gt;
3883
3884 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
3885 time is spent downloading packages. The connection to the Internet
3886 was 100Mbit/s during testing, so downloading should not be a
3887 significant factor in the measurement. Download typically took a few
3888 seconds to a few minutes, depending on the amount of packages being
3889 installed.&lt;/p&gt;
3890
3891 &lt;p&gt;The speedup is implemented by using two hooks in
3892 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
3893 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
3894 finish-install.d hook to remove the divert at the end of the
3895 installation. I picked the pre-pkgsel.d hook instead of the
3896 post-base-installer.d hook because I test using an ISO without the
3897 eatmydata package included, and the post-base-installer.d hook in
3898 Debian Edu can only operate on packages included in the ISO. The
3899 negative effect of this is that I am unable to activate this
3900 optimization for the kernel installation step in d-i. If the code is
3901 moved to the post-base-installer.d hook, the speedup would be larger
3902 for the entire installation.&lt;/p&gt;
3903
3904 &lt;p&gt;I&#39;ve implemented this in the
3905 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
3906 git repository, and plan to provide the optimization as part of the
3907 Debian Edu installation. If you want to test this yourself, you can
3908 create two files in the installer (or in an udeb). One shell script
3909 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
3910
3911 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3912 #!/bin/sh
3913 set -e
3914 . /usr/share/debconf/confmodule
3915 info() {
3916 logger -t my-pkgsel &quot;info: $*&quot;
3917 }
3918 error() {
3919 logger -t my-pkgsel &quot;error: $*&quot;
3920 }
3921 override_install() {
3922 apt-install eatmydata || true
3923 if [ -x /target/usr/bin/eatmydata ] ; then
3924 for bin in dpkg apt-get aptitude tasksel ; do
3925 file=/usr/bin/$bin
3926 # Test that the file exist and have not been diverted already.
3927 if [ -f /target$file ] ; then
3928 info &quot;diverting $file using eatmydata&quot;
3929 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
3930 &gt; /target$file.edu
3931 chmod 755 /target$file.edu
3932 in-target dpkg-divert --package debian-edu-config \
3933 --rename --quiet --add $file
3934 ln -sf ./$bin.edu /target$file
3935 else
3936 error &quot;unable to divert $file, as it is missing.&quot;
3937 fi
3938 done
3939 else
3940 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
3941 fi
3942 }
3943
3944 override_install
3945 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3946
3947 &lt;p&gt;To clean up, another shell script should go into
3948 /usr/lib/finish-install.d/ with code like this:
3949
3950 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3951 #! /bin/sh -e
3952 . /usr/share/debconf/confmodule
3953 error() {
3954 logger -t my-finish-install &quot;error: $@&quot;
3955 }
3956 remove_install_override() {
3957 for bin in dpkg apt-get aptitude tasksel ; do
3958 file=/usr/bin/$bin
3959 if [ -x /target$file.edu ] ; then
3960 rm /target$file
3961 in-target dpkg-divert --package debian-edu-config \
3962 --rename --quiet --remove $file
3963 rm /target$file.edu
3964 else
3965 error &quot;Missing divert for $file.&quot;
3966 fi
3967 done
3968 sync # Flush file buffers before continuing
3969 }
3970
3971 remove_install_override
3972 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3973
3974 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
3975 edu-eatmydata-install and call it from the pre-pkgsel.d and
3976 finish-install.d scripts.&lt;/p&gt;
3977
3978 &lt;p&gt;By now you might ask if this change should get into the normal
3979 Debian installer too? I suspect it should, but am not sure the
3980 current debian-installer coordinators find it useful enough. It also
3981 depend on the side effects of the change. I&#39;m not aware of any, but I
3982 guess we will see if the change is safe after some more testing.
3983 Perhaps there is some package in Debian depending on sync() and
3984 fsync() having effect? Perhaps it should go into its own udeb, to
3985 allow those of us wanting to enable it to do so without affecting
3986 everyone.&lt;/p&gt;
3987
3988 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
3989 will break installation of all programs using gnutls because of
3990 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
3991 eatmydata package in Debian will solve it.&lt;/p&gt;
3992
3993 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
3994 the optimization work again. And I have discovered that the
3995 dpkg-divert trick is not really needed and implemented a slightly
3996 simpler approach as part of the debian-edu-install package. See
3997 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
3998
3999 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
4000 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
4001 triggering on i386 made it into testing, and broke this installation
4002 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
4003 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
4004 </description>
4005 </item>
4006
4007 <item>
4008 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
4009 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
4010 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
4011 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
4012 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
4013 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
4014 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
4015 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
4016 learn that there is a large set of publicly available key servers to
4017 use when looking for peoples public key. So far I have used
4018 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
4019 were misbehaving, but those days are ended. The servers I have used
4020 up until yesterday have been slow and some times unavailable. I hope
4021 those problems are gone now.&lt;/p&gt;
4022
4023 &lt;p&gt;Behind the round robin DNS entry of the
4024 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
4025 there is a pool of more than 100 keyservers which are checked every
4026 day to ensure they are well connected and up to date. It must be
4027 better than what I have used so far. :)&lt;/p&gt;
4028
4029 &lt;p&gt;Yesterdays speaker told me that the service is the default
4030 keyserver provided by the default configuration in GnuPG, but this do
4031 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
4032
4033 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
4034 line:&lt;/p&gt;
4035
4036 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4037 keyserver pool.sks-keyservers.net
4038 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4039
4040 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
4041 entries in DNS. Just for fun, I did just that at work, so now every
4042 user of GnuPG at the University of Oslo should find a OpenGPG
4043 keyserver automatically should their need it:&lt;/p&gt;
4044
4045 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4046 % host -t srv _pgpkey-http._tcp.uio.no
4047 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
4048 %
4049 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4050
4051 &lt;p&gt;Now if only
4052 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
4053 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
4054 very happy. It can look up a given key or search for a user ID, but I
4055 normally do not want that, but to find a trust path from my key to
4056 another key. Given a user ID or key ID, I would like to find (and
4057 download) the keys representing a signature path from my key to the
4058 key in question, to be able to get a trust path between the two keys.
4059 This is as far as I can tell not possible today. Perhaps something
4060 for a future version of the protocol?&lt;/p&gt;
4061 </description>
4062 </item>
4063
4064 <item>
4065 <title>From English wiki to translated PDF and epub via Docbook</title>
4066 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
4067 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
4068 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
4069 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
4070 project&lt;/a&gt; provide an instruction manual for teachers, system
4071 administrators and other users that contain useful tips for setting up
4072 and maintaining a Debian Edu installation. This text is about how the
4073 text processing of this manual is handled in the project.&lt;/p&gt;
4074
4075 &lt;p&gt;One goal of the project is to provide information in the native
4076 language of its users, and for this we need to handle translations.
4077 But we also want to make sure each language contain the same
4078 information, so for this we need a good way to keep the translations
4079 in sync. And we want it to be easy for our users to improve the
4080 documentation, avoiding the need to learn special formats or tools to
4081 contribute, and the obvious way to do this is to make it possible to
4082 edit the documentation using a web browser. We also want it to be
4083 easy for translators to keep the translation up to date, and give them
4084 help in figuring out what need to be translated. Here is the list of
4085 tools and the process we have found trying to reach all these
4086 goals.&lt;/p&gt;
4087
4088 &lt;p&gt;We maintain the authoritative source of our manual in the
4089 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
4090 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
4091 front page with references to the different chapters, several pages
4092 for each chapter, and finally one &quot;collection page&quot; gluing all the
4093 chapters together into one large web page (aka
4094 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
4095 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
4096 processing and translations. Thanks to the fact that the
4097 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
4098 wiki.debian.org support exporting pages in
4099 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
4100 the list of pages to export using the raw version of the AllInOne
4101 page, loop over each of them to generate a Docbook XML version of the
4102 manual. This process also download images and transform image
4103 references to use the locally downloaded images. The generated
4104 Docbook XML files are slightly broken, so some post-processing is done
4105 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
4106 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4107 a handfull of images. The XML file can now be used to generate PDF, HTML
4108 and epub versions of the English manual. This is the basic step of
4109 our process, making PDF (using dblatex), HTML (using xsltproc) and
4110 epub (using dbtoepub) version from Docbook XML, and the resulting files
4111 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
4112
4113 &lt;p&gt;But English documentation is not enough for us. We want translated
4114 documentation too, and we want to make it easy for translators to
4115 track the English original. For this we use the
4116 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
4117 which allow us to transform the English Docbook XML file into a
4118 translation file (a .pot file), usable with the normal gettext based
4119 translation tools used by those translating free software. The pot
4120 file is used to create and maintain translation files (several .po
4121 files), which the translations update with the native language
4122 translations of all titles, paragraphs and blocks of text in the
4123 original. The next step is combining the original English Docbook XML
4124 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4125 create a translated Docbook XML file (in this case
4126 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4127 translated, if the translation is not complete) Docbook XML file can
4128 then be used like the original to create a PDF, HTML and epub version
4129 of the documentation.&lt;/p&gt;
4130
4131 &lt;p&gt;The translators use different tools to edit the .po files. We
4132 recommend using
4133 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
4134 while some use emacs and vi, others can use web based editors like
4135 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
4136 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
4137 is where the .po file end up, in our git repository. Updated
4138 translations can either be committed directly to git, or submitted as
4139 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
4140 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
4141
4142 &lt;p&gt;One challenge is images, which both might need to be translated (if
4143 they show translated user applications), and are needed in different
4144 formats when creating PDF and HTML versions (epub is a HTML version in
4145 this regard). For this we transform the original PNG images to the
4146 needed density and format during build, and have a way to provide
4147 translated images by storing translated versions in
4148 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4149 package maintainers know more.&lt;/p&gt;
4150
4151 &lt;p&gt;If you wonder what the result look like, we provide
4152 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
4153 of the documentation packages on the web&lt;/a&gt;. See for example the
4154 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
4155 PDF version&lt;/a&gt; or the
4156 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
4157 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
4158 but perhaps it will be done in the future.&lt;/p&gt;
4159
4160 &lt;p&gt;To learn more, check out
4161 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
4162 debian-edu-doc package&lt;/a&gt;,
4163 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
4164 manual on the wiki&lt;/a&gt; and
4165 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
4166 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
4167 </description>
4168 </item>
4169
4170 <item>
4171 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
4172 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
4173 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
4174 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
4175 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
4176 related packages relevant for the computer installed automatically.
4177 So I implemented one, using
4178 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
4179 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
4180 run tasksel as user root. You should be presented with a new option,
4181 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
4182 select it, tasksel will install the packages isenkram claim is fit for
4183 the current hardware, hot pluggable or not.&lt;p&gt;
4184
4185 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
4186 description, and the other is the script used to extract the list of
4187 packages to install. The first part is in
4188 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
4189 this:&lt;/p&gt;
4190
4191 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4192 Task: isenkram
4193 Section: hardware
4194 Description: Hardware specific packages (autodetected by isenkram)
4195 Based on the detected hardware various hardware specific packages are
4196 proposed.
4197 Test-new-install: mark show
4198 Relevance: 8
4199 Packages: for-current-hardware
4200 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4201
4202 &lt;p&gt;The second part is in
4203 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
4204 this:&lt;/p&gt;
4205
4206 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4207 #!/bin/sh
4208 #
4209 (
4210 isenkram-lookup
4211 isenkram-autoinstall-firmware -l
4212 ) | sort -u
4213 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4214
4215 &lt;p&gt;All in all, a very short and simple implementation making it
4216 trivial to install the hardware dependent package we all may want to
4217 have installed on our machines. I&#39;ve not been able to find a way to
4218 get tasksel to tell you exactly which packages it plan to install
4219 before doing the installation. So if you are curious or careful,
4220 check the output from the isenkram-* command line tools first.&lt;/p&gt;
4221
4222 &lt;p&gt;The information about which packages are handling which hardware is
4223 fetched either from the isenkram package itself in
4224 /usr/share/isenkram/, from git.debian.org or from the APT package
4225 database (using the Modaliases header). The APT package database
4226 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4227 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
4228 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
4229 the python-apt code (bug
4230 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
4231 workaround I was able to get rid of the file descriptor leak and
4232 reduce the memory leak from ~30 MiB per hardware detection down to
4233 around 2 MiB per hardware detection. It should make the desktop
4234 daemon a lot more useful. The fix is in version 0.7 uploaded to
4235 unstable today.&lt;/p&gt;
4236
4237 &lt;p&gt;I believe the current way of mapping hardware to packages in
4238 Isenkram is is a good draft, but in the future I expect isenkram to
4239 use the AppStream data source for this. A proposal for getting proper
4240 AppStream support into Debian is floating around as
4241 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
4242 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
4243 project&lt;/a&gt; will take place this summer to improve the situation. I
4244 look forward to seeing the result, and welcome patches for isenkram to
4245 start using the information when it is ready.&lt;/p&gt;
4246
4247 &lt;p&gt;If you want your package to map to some specific hardware, either
4248 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
4249 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
4250 package&lt;/a&gt; or submit a bug report with the details to the isenkram
4251 package. See also
4252 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
4253 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
4254 the information will be migrated to AppStream eventually, but for the
4255 moment I got no better place to store it.&lt;/p&gt;
4256 </description>
4257 </item>
4258
4259 <item>
4260 <title>FreedomBox milestone - all packages now in Debian Sid</title>
4261 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
4262 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
4263 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
4264 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
4265 project&lt;/a&gt; is working on providing the software and hardware to make
4266 it easy for non-technical people to host their data and communication
4267 at home, and being able to communicate with their friends and family
4268 encrypted and away from prying eyes. It is still going strong, and
4269 today a major mile stone was reached.&lt;/p&gt;
4270
4271 &lt;p&gt;Today, the last of the packages currently used by the project to
4272 created the system images were accepted into Debian Unstable. It was
4273 the freedombox-setup package, which is used to configure the images
4274 during build and on the first boot. Now all one need to get going is
4275 the build code from the freedom-maker git repository and packages from
4276 Debian. And once the freedombox-setup package enter testing, we can
4277 build everything directly from Debian. :)&lt;/p&gt;
4278
4279 &lt;p&gt;Some key packages used by Freedombox are
4280 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
4281 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
4282 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
4283 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
4284 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
4285 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
4286 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
4287 are plans to integrate more packages into the setup. User
4288 documentation is maintained on the Debian wiki. Please
4289 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
4290 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
4291
4292 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
4293 setup, run this on a Debian machine using a user with sudo rights to
4294 become root:&lt;/p&gt;
4295
4296 &lt;p&gt;&lt;pre&gt;
4297 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4298 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4299 u-boot-tools
4300 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4301 freedom-maker
4302 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4303 &lt;/pre&gt;&lt;/p&gt;
4304
4305 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
4306 devices. See the README in the freedom-maker git repo for more
4307 details on the build. If you do not want all three images, trim the
4308 make line. Note that the virtualbox-image target is not really
4309 virtualbox specific. It create a x86 image usable in kvm, qemu,
4310 vmware and any other x86 virtual machine environment. You might need
4311 the version of vmdebootstrap in Jessie to get the build working, as it
4312 include fixes for a race condition with kpartx.&lt;/p&gt;
4313
4314 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
4315 method, boot a Debian Wheezy ISO and use this boot argument to load
4316 the preseed values:&lt;/p&gt;
4317
4318 &lt;p&gt;&lt;pre&gt;
4319 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;
4320 &lt;/pre&gt;&lt;/p&gt;
4321
4322 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
4323 it still work.&lt;/p&gt;
4324
4325 &lt;p&gt;If you wonder how to help, one task you could look at is using
4326 systemd as the boot system. It will become the default for Linux in
4327 Jessie, so we need to make sure it is usable on the Freedombox. I did
4328 a simple test a few weeks ago, and noticed dnsmasq failed to start
4329 during boot when using systemd. I suspect there are other problems
4330 too. :) To detect problems, there is a test suite included, which can
4331 be run from the plinth web interface.&lt;/p&gt;
4332
4333 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
4334 us get the new release published. :) Please join us on
4335 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
4336 irc.debian.org)&lt;/a&gt; and
4337 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4338 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4339 </description>
4340 </item>
4341
4342 <item>
4343 <title>S3QL, a locally mounted cloud file system - nice free software</title>
4344 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
4345 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
4346 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
4347 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
4348 solution for use at home. My requirements are simple, it must be
4349 cheap and locally encrypted (in other words, I keep the encryption
4350 keys, the storage provider do not have access to my private files).
4351 One idea me and my friends had many years ago, before the cloud
4352 storage providers showed up, was to use Google mail as storage,
4353 writing a Linux block device storing blocks as emails in the mail
4354 service provided by Google, and thus get heaps of free space. On top
4355 of this one can add encryption, RAID and volume management to have
4356 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4357 I never found time to implement such system. But the last few weeks I
4358 have looked at a system called
4359 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
4360 mounted network backed file system with the features I need.&lt;/p&gt;
4361
4362 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
4363 handling several different storage providers, any with Amazon S3,
4364 Google Drive or OpenStack API. There are heaps of such storage
4365 providers. S3QL can also use a local directory as storage, which
4366 combined with sshfs allow for file storage on any ssh server. S3QL
4367 include support for encryption, compression, de-duplication, snapshots
4368 and immutable file systems, allowing me to mount the remote storage as
4369 a local mount point, look at and use the files as if they were local,
4370 while the content is stored in the cloud as well. This allow me to
4371 have a backup that should survive fire. The file system can not be
4372 shared between several machines at the same time, as only one can
4373 mount it at the time, but any machine with the encryption key and
4374 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
4375
4376 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
4377 package is included already. So to get started, run &lt;tt&gt;apt-get
4378 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
4379 Greenqloud, after reading their nice recipe on
4380 &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
4381 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
4382 in Iceland more than those in USA when it come to keeping my personal
4383 data safe and private, and thus would rather spend money on a company
4384 in Iceland. Another nice recipe is available from the article
4385 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
4386 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
4387 Admin magazine. When the provider is picked, figure out how to get
4388 the API key needed to connect to the storage API. With Greencloud,
4389 the key did not show up until I had added payment details to my
4390 account.&lt;/p&gt;
4391
4392 &lt;p&gt;Armed with the API access details, it is time to create the file
4393 system. First, create a new bucket in the cloud. This bucket is the
4394 file system storage area. I picked a bucket name reflecting the
4395 machine that was going to store data there, but any name will do.
4396 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
4397 the API login and password, and a locally created password. Store it
4398 all in ~root/.s3ql/authinfo2 like this:
4399
4400 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4401 [s3c]
4402 storage-url: s3c://s.greenqloud.com:443/bucket-name
4403 backend-login: API-login
4404 backend-password: API-password
4405 fs-passphrase: local-password
4406 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4407
4408 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
4409 but any sensible way to create a fairly random password should do it.
4410 Armed with these details, it is now time to run mkfs, entering the API
4411 details and password to create it:&lt;/p&gt;
4412
4413 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4414 # mkdir -m 700 /var/lib/s3ql-cache
4415 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4416 --ssl s3c://s.greenqloud.com:443/bucket-name
4417 Enter backend login:
4418 Enter backend password:
4419 Before using S3QL, make sure to read the user&#39;s guide, especially
4420 the &#39;Important Rules to Avoid Loosing Data&#39; section.
4421 Enter encryption password:
4422 Confirm encryption password:
4423 Generating random encryption key...
4424 Creating metadata tables...
4425 Dumping metadata...
4426 ..objects..
4427 ..blocks..
4428 ..inodes..
4429 ..inode_blocks..
4430 ..symlink_targets..
4431 ..names..
4432 ..contents..
4433 ..ext_attributes..
4434 Compressing and uploading metadata...
4435 Wrote 0.00 MB of compressed metadata.
4436 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4437
4438 &lt;p&gt;The next step is mounting the file system to make the storage available.
4439
4440 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4441 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4442 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
4443 Using 4 upload threads.
4444 Downloading and decompressing metadata...
4445 Reading metadata...
4446 ..objects..
4447 ..blocks..
4448 ..inodes..
4449 ..inode_blocks..
4450 ..symlink_targets..
4451 ..names..
4452 ..contents..
4453 ..ext_attributes..
4454 Mounting filesystem...
4455 # df -h /s3ql
4456 Filesystem Size Used Avail Use% Mounted on
4457 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
4458 #
4459 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4460
4461 &lt;p&gt;The file system is now ready for use. I use rsync to store my
4462 backups in it, and as the metadata used by rsync is downloaded at
4463 mount time, no network traffic (and storage cost) is triggered by
4464 running rsync. To unmount, one should not use the normal umount
4465 command, as this will not flush the cache to the cloud storage, but
4466 instead running the umount.s3ql command like this:
4467
4468 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4469 # umount.s3ql /s3ql
4470 #
4471 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4472
4473 &lt;p&gt;There is a fsck command available to check the file system and
4474 correct any problems detected. This can be used if the local server
4475 crashes while the file system is mounted, to reset the &quot;already
4476 mounted&quot; flag. This is what it look like when processing a working
4477 file system:&lt;/p&gt;
4478
4479 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4480 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
4481 Using cached metadata.
4482 File system seems clean, checking anyway.
4483 Checking DB integrity...
4484 Creating temporary extra indices...
4485 Checking lost+found...
4486 Checking cached objects...
4487 Checking names (refcounts)...
4488 Checking contents (names)...
4489 Checking contents (inodes)...
4490 Checking contents (parent inodes)...
4491 Checking objects (reference counts)...
4492 Checking objects (backend)...
4493 ..processed 5000 objects so far..
4494 ..processed 10000 objects so far..
4495 ..processed 15000 objects so far..
4496 Checking objects (sizes)...
4497 Checking blocks (referenced objects)...
4498 Checking blocks (refcounts)...
4499 Checking inode-block mapping (blocks)...
4500 Checking inode-block mapping (inodes)...
4501 Checking inodes (refcounts)...
4502 Checking inodes (sizes)...
4503 Checking extended attributes (names)...
4504 Checking extended attributes (inodes)...
4505 Checking symlinks (inodes)...
4506 Checking directory reachability...
4507 Checking unix conventions...
4508 Checking referential integrity...
4509 Dropping temporary indices...
4510 Backing up old metadata...
4511 Dumping metadata...
4512 ..objects..
4513 ..blocks..
4514 ..inodes..
4515 ..inode_blocks..
4516 ..symlink_targets..
4517 ..names..
4518 ..contents..
4519 ..ext_attributes..
4520 Compressing and uploading metadata...
4521 Wrote 0.89 MB of compressed metadata.
4522 #
4523 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4524
4525 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
4526 quick, about the same speed as local file access. Uploading large
4527 amount of data is to me limited by the bandwidth out of and into my
4528 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
4529 which is very close to my upload speed, and downloading the same
4530 Debian installation ISO gave me 610 kiB/s, close to my download speed.
4531 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
4532 network, not the file system code. I do not know what a good cache
4533 size would be, but suspect that the cache should e larger than your
4534 working set.&lt;/p&gt;
4535
4536 &lt;p&gt;I mentioned that only one machine can mount the file system at the
4537 time. If another machine try, it is told that the file system is
4538 busy:&lt;/p&gt;
4539
4540 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4541 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4542 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
4543 Using 8 upload threads.
4544 Backend reports that fs is still mounted elsewhere, aborting.
4545 #
4546 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4547
4548 &lt;p&gt;The file content is uploaded when the cache is full, while the
4549 metadata is uploaded once every 24 hour by default. To ensure the
4550 file system content is flushed to the cloud, one can either umount the
4551 file system, or ask S3QL to flush the cache and metadata using
4552 s3qlctrl:
4553
4554 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4555 # s3qlctrl upload-meta /s3ql
4556 # s3qlctrl flushcache /s3ql
4557 #
4558 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4559
4560 &lt;p&gt;If you are curious about how much space your data uses in the
4561 cloud, and how much compression and deduplication cut down on the
4562 storage usage, you can use s3qlstat on the mounted file system to get
4563 a report:&lt;/p&gt;
4564
4565 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4566 # s3qlstat /s3ql
4567 Directory entries: 9141
4568 Inodes: 9143
4569 Data blocks: 8851
4570 Total data size: 22049.38 MB
4571 After de-duplication: 21955.46 MB (99.57% of total)
4572 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
4573 Database size: 2.39 MB (uncompressed)
4574 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4575 #
4576 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4577
4578 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
4579 storage. I did not try to locate them all, but am aware of at least
4580 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
4581 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
4582 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
4583 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
4584 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
4585 accept payment in Bitcoin. Pick one that suit your need. Some of
4586 them provide several GiB of free storage, but the prize models are
4587 quite different and you will have to figure out what suits you
4588 best.&lt;/p&gt;
4589
4590 &lt;p&gt;While researching this blog post, I had a look at research papers
4591 and posters discussing the S3QL file system. There are several, which
4592 told me that the file system is getting a critical check by the
4593 science community and increased my confidence in using it. One nice
4594 poster is titled
4595 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
4596 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4597 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
4598 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4599 and Pamela Smith. Please have a look.&lt;/p&gt;
4600
4601 &lt;p&gt;Given my problems with different file systems earlier, I decided to
4602 check out the mounted S3QL file system to see if it would be usable as
4603 a home directory (in other word, that it provided POSIX semantics when
4604 it come to locking and umask handling etc). Running
4605 &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
4606 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
4607 no error was found. So the file system can be used for home
4608 directories, if one chooses to do so.&lt;/p&gt;
4609
4610 &lt;p&gt;If you do not want a locally file system, and want something that
4611 work without the Linux fuse file system, I would like to mention the
4612 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
4613 provide locally encrypted backup using a command line client. It have
4614 a nicer access control system, where one can split out read and write
4615 access, allowing some systems to write to the backup and others to
4616 only read from it.&lt;/p&gt;
4617
4618 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4619 activities, please send Bitcoin donations to my address
4620 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4621 </description>
4622 </item>
4623
4624 <item>
4625 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
4626 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
4627 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
4628 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
4629 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
4630 project&lt;/a&gt; is working on providing the software and hardware for
4631 making it easy for non-technical people to host their data and
4632 communication at home, and being able to communicate with their
4633 friends and family encrypted and away from prying eyes. It has been
4634 going on for a while, and is slowly progressing towards a new test
4635 release (0.2).&lt;/p&gt;
4636
4637 &lt;p&gt;And what day could be better than the Pi day to announce that the
4638 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
4639 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4640 system), and can also be installed using a Debian installer preseed
4641 file. The Debian based Freedombox is now based on Debian Jessie,
4642 where most of the needed packages used are already present. Only one,
4643 the freedombox-setup package, is missing. To try to build your own
4644 boot image to test the current status, fetch the freedom-maker scripts
4645 and build using
4646 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
4647 with a user with sudo access to become root:
4648
4649 &lt;pre&gt;
4650 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4651 freedom-maker
4652 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4653 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4654 u-boot-tools
4655 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4656 &lt;/pre&gt;
4657
4658 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
4659 devices. See the README for more details on the build. If you do not
4660 want all three images, trim the make line. But note that thanks to &lt;a
4661 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
4662 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
4663 kpartx call.&lt;/p&gt;
4664
4665 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
4666 method, boot a Debian Wheezy ISO and use this boot argument to load
4667 the preseed values:&lt;/p&gt;
4668
4669 &lt;pre&gt;
4670 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;
4671 &lt;/pre&gt;
4672
4673 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
4674 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
4675 currently hang while setting up APT sources. Killing the
4676 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
4677 installation will get the installation going. This affect all
4678 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
4679
4680 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
4681 us get the new release published. :) Please join us on
4682 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
4683 irc.debian.org)&lt;/a&gt; and
4684 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
4685 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
4686 </description>
4687 </item>
4688
4689 <item>
4690 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
4691 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
4692 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
4693 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
4694 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
4695 innetgr tools, because I needed them in
4696 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
4697 ng-utils, and it has served me well. I placed the project under the
4698 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
4699 repository. But many years ago, the CVS repository was dropped (lost,
4700 not migrated to new hardware, not sure), and the project have lacked a
4701 proper home since then.&lt;/p&gt;
4702
4703 &lt;p&gt;Last summer, I had a look at the package and made a new release
4704 fixing a irritating crash bug, but was unable to store the changes in
4705 a proper source control system. I applied for a project on
4706 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
4707 to follow up on it. Until today. :)&lt;/p&gt;
4708
4709 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
4710 now have a new home, and a git repository with the highlight of the
4711 history of the project. I published all release tarballs and imported
4712 them into the git repository. As the project is really stable and not
4713 expected to gain new features any time soon, I decided to make a new
4714 release and call it 1.0. Visit the new project home on
4715 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
4716 if you want to check it out. The new version is also uploaded into
4717 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
4718 </description>
4719 </item>
4720
4721 <item>
4722 <title>Testing sysvinit from experimental in Debian Hurd</title>
4723 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
4724 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
4725 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
4726 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
4727 their changes into sysvinit, to allow them to use the normal sysvinit
4728 boot system instead of their old one. This follow up on the
4729 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
4730 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
4731 get Debian on Hurd working more like Debian on Linux. To get started,
4732 I downloaded a prebuilt hard disk image from
4733 &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;,
4734 and started it using virt-manager.&lt;/p&gt;
4735
4736 &lt;p&gt;The first think I had to do after logging in (root without any
4737 password) was to get the network operational. I followed
4738 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
4739 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
4740 commands as root to get the machine to accept a IP address from the
4741 kvm internal DHCP server:&lt;/p&gt;
4742
4743 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4744 settrans -fgap /dev/netdde /hurd/netdde
4745 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
4746 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
4747 dhclient /dev/eth0
4748 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4749
4750 &lt;p&gt;After this, the machine had internet connectivity, and I could
4751 upgrade it and install the sysvinit packages from experimental and
4752 enable it as the default boot system in Hurd.&lt;/p&gt;
4753
4754 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
4755 running on the machine it for ssh login to work a password need to be
4756 set. Also, note that a bug somewhere in openssh on Hurd block
4757 compression from working. Remember to turn that off on the client
4758 side.&lt;/p&gt;
4759
4760 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
4761 stuff:&lt;/p&gt;
4762
4763 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4764 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
4765 deb http://http.debian.net/debian/ experimental main
4766 EOF
4767 apt-get update
4768 apt-get dist-upgrade
4769 apt-get install -t experimental initscripts sysv-rc sysvinit \
4770 sysvinit-core sysvinit-utils
4771 update-alternatives --config runsystem
4772 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4773
4774 &lt;p&gt;To reboot after switching boot system, you have to use
4775 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
4776 yet a sysvinit process able to receive the signals from the normal
4777 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
4778 upgrading every package and rebooting, the network come up with DHCP
4779 after boot as it should, and the settrans/pkill hack mentioned at the
4780 start is no longer needed. But for some strange reason, there are no
4781 longer any login prompt in the virtual console, so I logged in using
4782 ssh instead.
4783
4784 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
4785 fail some times. No idea what the cause is, but hope the Hurd porters
4786 figure it out. At least Justus said on IRC (#debian-hurd on
4787 irc.debian.org) that they are aware of the problem. A way to reduce
4788 the impact is to upgrade to the Hurd packages built by Justus by
4789 adding this repository to the machine:&lt;/p&gt;
4790
4791 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4792 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
4793 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4794 EOF
4795 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4796
4797 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
4798 http://ftp.debian-ports.org/debian, because some of the packages in
4799 unstable do not yet include the required patches that are lingering in
4800 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
4801
4802 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4803 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
4804 i emacs - GNU Emacs editor (metapackage)
4805 i gdb - GNU Debugger
4806 i hurd-recommended - Miscellaneous translators
4807 i isc-dhcp-client - ISC DHCP client
4808 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4809 i libc-bin - Embedded GNU C Library: Binaries
4810 i libc-dev-bin - Embedded GNU C Library: Development binaries
4811 i libc0.3 - Embedded GNU C Library: Shared libraries
4812 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4813 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4814 i multiarch-support - Transitional package to ensure multiarch compatibilit
4815 i A x11-common - X Window System (X.Org) infrastructure
4816 i xorg - X.Org X Window System
4817 i A xserver-xorg - X.Org X server
4818 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4819 #
4820 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4821
4822 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
4823 X.org did not work out of the box and I never took the time to follow
4824 the porters instructions to fix it. This time I was interested in the
4825 command line stuff.&lt;p&gt;
4826 </description>
4827 </item>
4828
4829 <item>
4830 <title>New chrpath release 0.16</title>
4831 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
4832 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
4833 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
4834 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
4835 find problems in C, C++ and Java code using static source code
4836 analysis. It can detect a lot of different problems, and is very
4837 useful to find memory and locking bugs in the error handling part of
4838 the source. The company behind it provide
4839 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
4840 a community service&lt;/a&gt;, and many hundred free software projects are
4841 already checked. A few days ago I decided to have a closer look at
4842 the Coverity system, and discovered that the
4843 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
4844 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
4845 projects I am involved with was already registered. But these are
4846 fairly big, and I would also like to have a small and easy project to
4847 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
4848 checking of the chrpath project&lt;/a&gt;. It was
4849 added to the checker and discovered seven potential defects. Six of
4850 these were real, mostly resource &quot;leak&quot; when the program detected an
4851 error. Nothing serious, as the resources would be released a fraction
4852 of a second later when the program exited because of the error, but it
4853 is nice to do it right in case the source of the program some time in
4854 the future end up in a library. Having fixed all defects and added
4855 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
4856 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
4857 publish a new release. These are the release notes:&lt;/p&gt;
4858
4859 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
4860
4861 &lt;ul&gt;
4862
4863 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
4864 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
4865 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
4866
4867 &lt;/ul&gt;
4868
4869 &lt;p&gt;You can
4870 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
4871 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
4872 project if something is wrong with the new release. The test suite
4873 did not discover any old errors, so if you find a new one, please also
4874 include a test suite check.&lt;/p&gt;
4875 </description>
4876 </item>
4877
4878 <item>
4879 <title>New chrpath release 0.15</title>
4880 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
4881 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
4882 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
4883 <description>&lt;p&gt;After many years break from the package and a vain hope that
4884 development would be continued by someone else, I finally pulled my
4885 acts together this morning and wrapped up a new release of chrpath,
4886 the command line tool to modify the rpath and runpath of already
4887 compiled ELF programs. The update was triggered by the persistence of
4888 Isha Vishnoi at IBM, which needed a new config.guess file to get
4889 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
4890 is working on. I checked the
4891 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
4892 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
4893 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
4894 packages for interesting patches (failed to find the source from
4895 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4896 These are the release notes:&lt;/p&gt;
4897
4898 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
4899
4900 &lt;ul&gt;
4901
4902 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
4903 with newer architectures. Thanks to isha vishnoi for the heads
4904 up.&lt;/li&gt;
4905
4906 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
4907
4908 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4909 Matthias Klose.&lt;/li&gt;
4910
4911 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
4912 Petr Machata found in Fedora.&lt;/li&gt;
4913
4914 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
4915 .dynamic is a NULL terminated string. Based on patch found in
4916 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
4917
4918 &lt;/ul&gt;
4919
4920 &lt;p&gt;You can
4921 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
4922 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
4923 project if something is wrong with the new release. The test suite
4924 did not discover any old errors, so if you find a new one, please also
4925 include a testsuite check.&lt;/p&gt;
4926 </description>
4927 </item>
4928
4929 <item>
4930 <title>Debian init.d boot script example for rsyslog</title>
4931 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
4932 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
4933 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
4934 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
4935 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
4936 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
4937 init.d scripts at all. Here is an example init.d script, ie a rewrite
4938 of /etc/init.d/rsyslog:&lt;/p&gt;
4939
4940 &lt;p&gt;&lt;pre&gt;
4941 #!/lib/init/init-d-script
4942 ### BEGIN INIT INFO
4943 # Provides: rsyslog
4944 # Required-Start: $remote_fs $time
4945 # Required-Stop: umountnfs $time
4946 # X-Stop-After: sendsigs
4947 # Default-Start: 2 3 4 5
4948 # Default-Stop: 0 1 6
4949 # Short-Description: enhanced syslogd
4950 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4951 # It is quite compatible to stock sysklogd and can be
4952 # used as a drop-in replacement.
4953 ### END INIT INFO
4954 DESC=&quot;enhanced syslogd&quot;
4955 DAEMON=/usr/sbin/rsyslogd
4956 &lt;/pre&gt;&lt;/p&gt;
4957
4958 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
4959 script was 137 lines, and the above is just 15 lines, most of it meta
4960 info/comments.&lt;/p&gt;
4961
4962 &lt;p&gt;How to do this, you ask? Well, one create a new script
4963 /lib/init/init-d-script looking something like this:
4964
4965 &lt;p&gt;&lt;pre&gt;
4966 #!/bin/sh
4967
4968 # Define LSB log_* functions.
4969 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
4970 # and status_of_proc is working.
4971 . /lib/lsb/init-functions
4972
4973 #
4974 # Function that starts the daemon/service
4975
4976 #
4977 do_start()
4978 {
4979 # Return
4980 # 0 if daemon has been started
4981 # 1 if daemon was already running
4982 # 2 if daemon could not be started
4983 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
4984 || return 1
4985 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4986 $DAEMON_ARGS \
4987 || return 2
4988 # Add code here, if necessary, that waits for the process to be ready
4989 # to handle requests from services started subsequently which depend
4990 # on this one. As a last resort, sleep for some time.
4991 }
4992
4993 #
4994 # Function that stops the daemon/service
4995 #
4996 do_stop()
4997 {
4998 # Return
4999 # 0 if daemon has been stopped
5000 # 1 if daemon was already stopped
5001 # 2 if daemon could not be stopped
5002 # other if a failure occurred
5003 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
5004 RETVAL=&quot;$?&quot;
5005 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
5006 # Wait for children to finish too if this is a daemon that forks
5007 # and if the daemon is only ever run from this initscript.
5008 # If the above conditions are not satisfied then add some other code
5009 # that waits for the process to drop all resources that could be
5010 # needed by services started subsequently. A last resort is to
5011 # sleep for some time.
5012 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
5013 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
5014 # Many daemons don&#39;t delete their pidfiles when they exit.
5015 rm -f $PIDFILE
5016 return &quot;$RETVAL&quot;
5017 }
5018
5019 #
5020 # Function that sends a SIGHUP to the daemon/service
5021 #
5022 do_reload() {
5023 #
5024 # If the daemon can reload its configuration without
5025 # restarting (for example, when it is sent a SIGHUP),
5026 # then implement that here.
5027 #
5028 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
5029 return 0
5030 }
5031
5032 SCRIPTNAME=$1
5033 scriptbasename=&quot;$(basename $1)&quot;
5034 echo &quot;SN: $scriptbasename&quot;
5035 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
5036 script=&quot;$1&quot;
5037 shift
5038 . $script
5039 else
5040 exit 0
5041 fi
5042
5043 NAME=$(basename $DAEMON)
5044 PIDFILE=/var/run/$NAME.pid
5045
5046 # Exit if the package is not installed
5047 #[ -x &quot;$DAEMON&quot; ] || exit 0
5048
5049 # Read configuration variable file if it is present
5050 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
5051
5052 # Load the VERBOSE setting and other rcS variables
5053 . /lib/init/vars.sh
5054
5055 case &quot;$1&quot; in
5056 start)
5057 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
5058 do_start
5059 case &quot;$?&quot; in
5060 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5061 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5062 esac
5063 ;;
5064 stop)
5065 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
5066 do_stop
5067 case &quot;$?&quot; in
5068 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
5069 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
5070 esac
5071 ;;
5072 status)
5073 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
5074 ;;
5075 #reload|force-reload)
5076 #
5077 # If do_reload() is not implemented then leave this commented out
5078 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
5079 #
5080 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
5081 #do_reload
5082 #log_end_msg $?
5083 #;;
5084 restart|force-reload)
5085 #
5086 # If the &quot;reload&quot; option is implemented then remove the
5087 # &#39;force-reload&#39; alias
5088 #
5089 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
5090 do_stop
5091 case &quot;$?&quot; in
5092 0|1)
5093 do_start
5094 case &quot;$?&quot; in
5095 0) log_end_msg 0 ;;
5096 1) log_end_msg 1 ;; # Old process is still running
5097 *) log_end_msg 1 ;; # Failed to start
5098 esac
5099 ;;
5100 *)
5101 # Failed to stop
5102 log_end_msg 1
5103 ;;
5104 esac
5105 ;;
5106 *)
5107 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
5108 exit 3
5109 ;;
5110 esac
5111
5112 :
5113 &lt;/pre&gt;&lt;/p&gt;
5114
5115 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
5116 lot. I did not really polish the approach, so it might not always
5117 work out of the box, but you get the idea. I did not try very hard to
5118 optimize it nor make it more robust either.&lt;/p&gt;
5119
5120 &lt;p&gt;A better argument for switching init system in Debian than reducing
5121 the size of init scripts (which is a good thing to do anyway), is to
5122 get boot system that is able to handle the kernel events sensibly and
5123 robustly, and do not depend on the boot to run sequentially. The boot
5124 and the kernel have not behaved sequentially in years.&lt;/p&gt;
5125 </description>
5126 </item>
5127
5128 <item>
5129 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
5130 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
5131 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
5132 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
5133 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
5134 remote display access is the preferred solution with oVirt and RedHat
5135 Enterprise Virtualization, and I was sad to discover the other day
5136 that the browser plugin needed to use these systems seamlessly was
5137 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
5138 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
5139 2013-04-01, so I decided to wrap up a package based on the great work
5140 from Cajus Pollmeier and put it in a collab-maint maintained git
5141 repository to get a package I could use. I would very much like
5142 others to help me maintain the package (or just take over, I do not
5143 mind), but as no-one had volunteered so far, I just uploaded it to
5144 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
5145
5146 &lt;p&gt;The source is now available from
5147 &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;
5148 </description>
5149 </item>
5150
5151 <item>
5152 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
5153 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
5154 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
5155 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
5156 <description>&lt;p&gt;The
5157 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
5158 program is a a very nice system to create virtual machine images. It
5159 create a image file, add a partition table, mount it and run
5160 debootstrap in the mounted directory to create a Debian system on a
5161 stick. Yesterday, I decided to try to teach it how to make images for
5162 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
5163 of a plan to simplify the build system for
5164 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
5165 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
5166 the virtualbox images, but its current build system made multistrap
5167 based system for Dreamplug images, and it is lacking support for
5168 Raspberry Pi.&lt;/p&gt;
5169
5170 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
5171 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5172 code and adjusted it to be able to build armel images on my amd64
5173 Debian laptop. I ended up giving vmdebootstrap five new options,
5174 allowing me to replicate the image creation process I use to make
5175 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
5176 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
5177 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
5178 call debootstrap with --foreign and to copy the handler into the
5179 generated chroot before running the second stage. This allow
5180 vmdebootstrap to create armel images on an amd64 host. Next I added
5181 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
5182 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
5183 given file system type, allowing me to create an image with a vfat
5184 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
5185 variant&lt;/tt&gt; option to allow me to create smaller images without the
5186 Debian base system packages installed. Finally, I added an option
5187 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
5188 as a boot loader. It is not needed on the Raspberry Pi and probably
5189 most other non-x86 architectures. The changes were accepted by the
5190 upstream author of vmdebootstrap yesterday and today, and is now
5191 available from
5192 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
5193 upstream project page&lt;/a&gt;.&lt;/p&gt;
5194
5195 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
5196 create a small script (the customize script) to add the non-free
5197 binary blob needed to boot the Raspberry Pi and the APT source
5198 list:&lt;/p&gt;
5199
5200 &lt;p&gt;&lt;pre&gt;
5201 #!/bin/sh
5202 set -e # Exit on first error
5203 rootdir=&quot;$1&quot;
5204 cd &quot;$rootdir&quot;
5205 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
5206 deb http://http.debian.net/debian/ jessie main contrib non-free
5207 EOF
5208 # Install non-free binary blob needed to boot Raspberry Pi. This
5209 # install a kernel somewhere too.
5210 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5211 -O $rootdir/usr/bin/rpi-update
5212 chmod a+x $rootdir/usr/bin/rpi-update
5213 mkdir -p $rootdir/lib/modules
5214 touch $rootdir/boot/start.elf
5215 chroot $rootdir rpi-update
5216 &lt;/pre&gt;&lt;/p&gt;
5217
5218 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
5219 to build the image:&lt;/p&gt;
5220
5221 &lt;pre&gt;
5222 sudo ./vmdebootstrap \
5223 --variant minbase \
5224 --arch armel \
5225 --distribution jessie \
5226 --mirror http://http.debian.net/debian \
5227 --image test.img \
5228 --size 600M \
5229 --bootsize 64M \
5230 --boottype vfat \
5231 --log-level debug \
5232 --verbose \
5233 --no-kernel \
5234 --no-extlinux \
5235 --root-password raspberry \
5236 --hostname raspberrypi \
5237 --foreign /usr/bin/qemu-arm-static \
5238 --customize `pwd`/customize \
5239 --package netbase \
5240 --package git-core \
5241 --package binutils \
5242 --package ca-certificates \
5243 --package wget \
5244 --package kmod
5245 &lt;/pre&gt;&lt;/p&gt;
5246
5247 &lt;p&gt;The list of packages being installed are the ones needed by
5248 rpi-update to make the image bootable on the Raspberry Pi, with the
5249 exception of netbase, which is needed by debootstrap to find
5250 /etc/hosts with the minbase variant. I really wish there was a way to
5251 set up an Raspberry Pi using only packages in the Debian archive, but
5252 that is not possible as far as I know, because it boots from the GPU
5253 using a non-free binary blob.&lt;/p&gt;
5254
5255 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
5256 probably a few others installed. I have not checked the complete
5257 build dependency list.&lt;/p&gt;
5258
5259 &lt;p&gt;The resulting image will not use the hardware floating point unit
5260 on the Raspberry PI, because the armel architecture in Debian is not
5261 optimized for that use. So the images created will be a bit slower
5262 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
5263 </description>
5264 </item>
5265
5266 <item>
5267 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
5268 <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>
5269 <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>
5270 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
5271 <description>&lt;p&gt;The last few days I came across a few good causes that should get
5272 wider attention. I recommend signing and donating to each one of
5273 these. :)&lt;/p&gt;
5274
5275 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
5276 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
5277 Women program which is a Google Summer of Code like initiative to get
5278 more women involved in free software. One debian sponsor has offered
5279 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
5280 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
5281 hope you will to. :)&lt;/p&gt;
5282
5283 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
5284 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
5285 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
5286 take place these days, and their need to fund the work. I&#39;ve already
5287 donated. Are you next?&lt;/p&gt;
5288
5289 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
5290 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5291 statement under the heading
5292 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
5293 Access&lt;/a&gt; for those of us asking for more focus on open access in the
5294 Norwegian government. So far 499 signatures. I hope you will sign it
5295 too.&lt;/p&gt;
5296 </description>
5297 </item>
5298
5299 <item>
5300 <title>Videos about the Freedombox project - for inspiration and learning</title>
5301 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
5302 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
5303 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
5304 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
5305 project&lt;/a&gt; have been going on for a while, and have presented the
5306 vision, ideas and solution several places. Here is a little
5307 collection of videos of talks and presentation of the project.&lt;/p&gt;
5308
5309 &lt;ul&gt;
5310
5311 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
5312 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
5313
5314 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
5315 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
5316
5317 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
5318 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5319 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
5320 (Youtube)&lt;/li&gt;
5321
5322 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
5323 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
5324
5325 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
5326 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
5327
5328 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
5329 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5330 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
5331
5332 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
5333 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
5334 (Youtube)&lt;/li&gt;
5335
5336 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
5337 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
5338
5339 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
5340 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
5341
5342 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
5343 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5344 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
5345
5346 &lt;/ul&gt;
5347
5348 &lt;p&gt;A larger list is available from
5349 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
5350 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
5351
5352 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
5353 Jessie is coming along quite well, and soon both Owncloud and using
5354 Tor should be available for testers of the Freedombox solution. :) In
5355 a few weeks I hope everything needed to test it is included in Debian.
5356 The withsqlite package is already in Debian, and the plinth package is
5357 pending in NEW. The third and vital part of that puzzle is the
5358 metapackage/setup framework, which is still pending an upload. Join
5359 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
5360 (#freedombox on irc.debian.org)&lt;/a&gt; and
5361 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
5362 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
5363 </description>
5364 </item>
5365
5366 <item>
5367 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
5368 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
5369 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
5370 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
5371 <description>&lt;p&gt;I was introduced to the
5372 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
5373 in 2010, when Eben Moglen presented his vision about serving the need
5374 of non-technical people to keep their personal information private and
5375 within the legal protection of their own homes. The idea is to give
5376 people back the power over their network and machines, and return
5377 Internet back to its intended peer-to-peer architecture. Instead of
5378 depending on a central service, the Freedombox will give everyone
5379 control over their own basic infrastructure.&lt;/p&gt;
5380
5381 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
5382 taken priority. But this summers nasty news about the misuse of trust
5383 and privilege exercised by the &quot;western&quot; intelligence gathering
5384 communities increased my eagerness to contribute to a point where I
5385 actually started working on the project a while back.&lt;/p&gt;
5386
5387 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
5388 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
5389 create a simple and cheap Debian based appliance that anyone can hook
5390 up in their home and get access to secure and private services and
5391 communication. The initial deployment platform have been the
5392 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
5393 which is a piece of hardware I do not own. So to be able to test what
5394 the current Freedombox setup look like, I had to come up with a way to install
5395 it on some hardware I do have access to. I have rewritten the
5396 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
5397 image build framework to use .deb packages instead of only copying
5398 setup into the boot images, and thanks to this rewrite I am able to
5399 set up any machine supported by Debian Wheezy as a Freedombox, using
5400 the previously mentioned deb (and a few support debs for packages
5401 missing in Debian).&lt;/p&gt;
5402
5403 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
5404 scripts
5405 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
5406 and a administrative web interface
5407 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
5408 withsqlite), as well as a privacy enhancing proxy based on
5409 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
5410 (freedombox-privoxy). There is also a web/javascript based XMPP
5411 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
5412 trying (unsuccessfully so far) to talk to the XMPP server
5413 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
5414 web interface is pluggable, and the goal is to use it to enable OpenID
5415 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5416 this is really working yet, see
5417 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
5418 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
5419 on github at the moment. The HTTP proxy is operational out of the
5420 box, and the admin web interface can be used to add/remove plinth
5421 users. I&#39;ve not been able to do anything else with it so far, but
5422 know there are several branches spread around github and other places
5423 with lots of half baked features.&lt;/p&gt;
5424
5425 &lt;p&gt;Anyway, if you want to have a look at the current state, the
5426 following recipes should work to give you a test machine to poke
5427 at.&lt;/p&gt;
5428
5429 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
5430
5431 &lt;ol&gt;
5432
5433 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
5434 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
5435 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
5436 to the Debian installer:&lt;p&gt;
5437 &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;
5438
5439 &lt;li&gt;Answer the few language/region/password questions and pick disk to
5440 install on.&lt;/li&gt;
5441
5442 &lt;li&gt;When the installation is finished and the machine have rebooted a
5443 few times, your Freedombox is ready for testing.&lt;/li&gt;
5444
5445 &lt;/ol&gt;
5446
5447 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
5448
5449 &lt;ol&gt;
5450
5451 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
5452 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
5453 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
5454 &lt;pre&gt;
5455 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
5456 &lt;/pre&gt;&lt;/li&gt;
5457 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
5458 &lt;pre&gt;
5459 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5460 apt-key add -
5461 apt-get update
5462 apt-get install freedombox-setup
5463 /usr/lib/freedombox/setup
5464 &lt;/pre&gt;&lt;/li&gt;
5465 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
5466
5467 &lt;/ol&gt;
5468
5469 &lt;p&gt;You can test it on other architectures too, but because the
5470 freedombox-privoxy package is binary, it will only work as intended on
5471 the architectures where I have had time to build the binary and put it
5472 in my APT repository. But do not let this stop you. It is only a
5473 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
5474
5475 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
5476 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
5477 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
5478 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
5479
5480 &lt;p&gt;Please let me know if this works for you, or if you have any
5481 problems. We gather on the IRC channel
5482 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
5483 irc.debian.org and the
5484 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
5485 mailing list&lt;/a&gt;.&lt;/p&gt;
5486
5487 &lt;p&gt;Once you get your freedombox operational, you can visit
5488 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
5489 welcome screen (dead end - do not be surprised if you are unable to
5490 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
5491 to look at the rest of plinth. The default user is &#39;admin&#39; and the
5492 default password is &#39;secret&#39;.&lt;/p&gt;
5493 </description>
5494 </item>
5495
5496 <item>
5497 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
5498 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
5499 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
5500 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
5501 <description>&lt;p&gt;Earlier, I reported about
5502 &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
5503 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
5504 told by IBM that the original disk should be thrown away. And as
5505 there no longer was a problem if I bricked the firmware, I decided
5506 today to try to install Intel firmware to replace the Lenovo firmware
5507 currently on the disk.&lt;/p&gt;
5508
5509 &lt;p&gt;I searched the Intel site for firmware, and found
5510 &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;
5511 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5512 according to the site should contain the latest firmware for SSD
5513 disks. I inserted the broken disk in one of my spare laptops and
5514 booted the ISO from a USB stick. The disk was recognized, but the
5515 program claimed the newest firmware already were installed and refused
5516 to insert any Intel firmware. So no change, and the disk is still
5517 unable to handle write load. :( I guess the only way to get them
5518 working would be if Lenovo releases new firmware. No idea how likely
5519 that is. Anyway, just blogging about this test for completeness. I
5520 got a working Samsung disk, and see no point in spending more time on
5521 the broken disks.&lt;/p&gt;
5522 </description>
5523 </item>
5524
5525 <item>
5526 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
5527 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
5528 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
5529 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
5530 <description>&lt;p&gt;Today I switched to
5531 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
5532 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
5533 my new Thinkpad X230, which was delivered with an
5534 &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
5535 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
5536 sustained writes. My hardware supplier have been very forthcoming in
5537 trying to find a solution, and after first trying with another
5538 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
5539 disk instead to fix it once and for all. The Samsung disk survived
5540 the installation of Debian with encrypted disks (filling the disk with
5541 random data during installation killed the first two), and I thus
5542 decided to trust it with my data. I have installed it as a Debian Edu
5543 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5544 server at home using Kerberos and LDAP, and will use it as my work
5545 station from now on.&lt;/p&gt;
5546
5547 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
5548 Debian Wheezy default installation need to be tuned a bit to increase
5549 performance and increase life time of the disk. The Linux kernel and
5550 user space applications do not yet adjust automatically to such
5551 environment. To make it easier for my self, I created a draft Debian
5552 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
5553 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
5554 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
5555 is set up to adjust the setup of the machine by just installing the
5556 package. If there is any non-SSD disk in the machine, the package
5557 will refuse to install, as I did not try to write any logic to sort
5558 file systems in SSD and non-SSD file systems.&lt;/p&gt;
5559
5560 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
5561 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5562 where I set up the machine with one large encrypted partition (in
5563 addition to /boot), put LVM on top of this and set up partitions on
5564 top of this again. See the README file in the package source for the
5565 references I used to pick the settings. At the moment these
5566 parameters are tuned:&lt;/p&gt;
5567
5568 &lt;ul&gt;
5569
5570 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
5571 (adding discard to /etc/crypttab)&lt;/li&gt;
5572
5573 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
5574 this case a cryptsetup partition) by changing issue_discards from
5575 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
5576
5577 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
5578 systems.&lt;/li&gt;
5579
5580 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
5581 /etc/fstab.&lt;/li&gt;
5582
5583 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
5584
5585 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
5586 cron.daily).&lt;/li&gt;
5587
5588 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
5589 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
5590
5591 &lt;/ul&gt;
5592
5593 &lt;p&gt;During installation, I cancelled the part where the installer fill
5594 the disk with random data, as this would kill the SSD performance for
5595 little gain. My goal with the encrypted file system is to ensure
5596 those stealing my laptop end up with a brick and not a working
5597 computer. I have no hope in keeping the really resourceful people
5598 from getting the data on the disk (see
5599 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
5600 Thus I concluded that adding the discard option to crypttab is the
5601 right thing to do.&lt;/p&gt;
5602
5603 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
5604 it for SSD, but others recommended deadline and a benchmark I found
5605 indicated that deadline might be better for interactive use.&lt;/p&gt;
5606
5607 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
5608 and ext4, but read that it would give a performance hit ever time a
5609 file is removed, and thought it best to that that slowdown once a day
5610 instead of during my work.&lt;/p&gt;
5611
5612 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5613 this is already done by Debian Edu.&lt;/p&gt;
5614
5615 &lt;p&gt;I have not yet started on the user space tuning. I expect
5616 iceweasel need some tuning, and perhaps other applications too, but
5617 have not yet had time to investigate those parts.&lt;/p&gt;
5618
5619 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
5620 there.&lt;/p&gt;
5621
5622 &lt;p&gt;As for the answer to the question in the title of this blog post,
5623 as far as I know, the only solution I know about is to replace the
5624 disk. It might be possible to flash it with Intel firmware instead of
5625 the Lenovo firmware. But I have not tried and did not want to do so
5626 without approval from Lenovo as I wanted to keep the warranty on the
5627 disk until a solution was found and they wanted the broken disks
5628 back.&lt;/p&gt;
5629 </description>
5630 </item>
5631
5632 <item>
5633 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
5634 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
5635 <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>
5636 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
5637 <description>&lt;p&gt;A few days ago, I wrote about
5638 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
5639 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
5640 was dying during installation because it is unable to cope with
5641 sustained write. My supplier is in contact with
5642 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
5643 replacement disk to try to fix the problem. They decided to send an
5644 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
5645
5646 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
5647 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5648 same firmware version as the original. This time my hope raised
5649 slightly as the installation progressed, as the original disk used to
5650 die after 4-7% of the disk was written to, while this time it kept
5651 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
5652 died again and I was back on square one. I still do not have a new
5653 laptop with a disk I can trust. I can not live with a disk that might
5654 lock up when I download a new
5655 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
5656 other large files. I look forward to hearing from my supplier with
5657 the next proposal from Lenovo.&lt;/p&gt;
5658
5659 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
5660 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5661 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
5662 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
5663 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
5664 P/N 45N8295, P0C38732.&lt;/p&gt;
5665
5666 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
5667 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
5668 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
5669 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
5670 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
5671 P/N 45N8295, P0C38732.&lt;/p&gt;
5672
5673 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
5674 SA, date and WNPP values. Mentioning all the details here in case
5675 someone is able to use the information to find a way to identify the
5676 failing disk among working ones (if any such working disk actually
5677 exist).&lt;/p&gt;
5678 </description>
5679 </item>
5680
5681 <item>
5682 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
5683 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
5684 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
5685 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
5686 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
5687 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5688 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
5689 member assosiation NUUG&lt;/a&gt; and
5690 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
5691 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
5692 Bitraf&lt;/a&gt;.&lt;/p&gt;
5693
5694 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
5695 welcome, and there is no fee to participate. There is on the other
5696 hand limited space, and only room for 30 people. Please put your name
5697 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
5698 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
5699 </description>
5700 </item>
5701
5702 <item>
5703 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
5704 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
5705 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
5706 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
5707 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
5708 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
5709 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
5710 time to spend on it, and it took a while to find a model I believe
5711 will do the job, but two days ago the replacement finally arrived. I
5712 ended up picking a
5713 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
5714 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5715 a roaming workstation, and it seemed to work flawlessly. But my
5716 second installation with encrypted disk was not as successful. More
5717 on that below.&lt;/p&gt;
5718
5719 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
5720 important requirements (robust and with a good keyboard) are never
5721 listed in the feature list. But I did get good help from the search
5722 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
5723 allowed me to limit the list of interesting laptops based on my other
5724 requirements. A bit surprising that SSD disk are not disks according
5725 to that search interface, so I had to drop specifying the number of
5726 disks from my search parameters. I also asked around among friends to
5727 get their impression on keyboards and robustness.&lt;/p&gt;
5728
5729 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
5730 X41. I am not quite convinced about the keyboard, as it is
5731 significantly wider than my old keyboard, and I have to stretch my
5732 hand a lot more to reach the edges. But the key response is fairly
5733 good and the individual key shape is fairly easy to handle, so I hope
5734 I will get used to it. My old X40 was starting to fail, and I really
5735 needed a new laptop now. :)&lt;/p&gt;
5736
5737 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
5738 visit to the BIOS during boot it disable it.&lt;/p&gt;
5739
5740 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
5741 lock up during load. And this happen when installing Debian Wheezy
5742 with encrypted disk, while the disk is being filled with random data.
5743 I also tested to install Ubuntu Raring, and it happen there too if I
5744 reenable the code to fill the disk with random data (it is disabled by
5745 default in Ubuntu). And the bug with is already known. It was
5746 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
5747 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
5748 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5749 kernel developers as
5750 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
5751 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
5752 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5753 Lenovo forums, both for
5754 &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
5755 2012-11-10&lt;/a&gt; and for
5756 &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
5757 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
5758 reports state that the disk lock up during use if many writes are done
5759 on the disk, so it is much no use to work around the installation
5760 problem and end up with a computer that can lock up at any moment.
5761 There is even a
5762 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
5763 available&lt;/a&gt; that will lock up the hard drive after running a few
5764 minutes by writing to a file.&lt;/p&gt;
5765
5766 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
5767 contacting PCHELP Norway (request 01D1FDP) which handle support
5768 requests for Lenovo, his first suggestion was to upgrade the disk
5769 firmware. Unfortunately there is no newer firmware available from
5770 Lenovo, as my disk already have the most recent one (version LF1i). I
5771 hope to hear more from him today and hope the problem can be
5772 fixed. :)&lt;/p&gt;
5773 </description>
5774 </item>
5775
5776 <item>
5777 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
5778 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
5779 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
5780 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
5781 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
5782 trusty old Thinkpad X41. Unfortunately I did not have much time to
5783 spend on it, but today the replacement finally arrived. I ended up
5784 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
5785 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
5786 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5787 this, it is installing what I hope will be a more final installation,
5788 with a encrypted hard drive to ensure any dope head stealing it end up
5789 with an expencive door stop.&lt;/p&gt;
5790
5791 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
5792 important requirements (robust and with a good keyboard) are never
5793 listed in the feature list. But I did get good help from the search
5794 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
5795 allowed me to limit the list of interesting laptops based on my other
5796 requirements. A bit surprising that SSD disk are not disks, so I had
5797 to drop number of disks from my search parameters.&lt;/p&gt;
5798
5799 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
5800 wider than my old keyboard, and I have to stretch my hand a lot more
5801 to reach the edges. But the key response is fairly good and the
5802 individual key shape is fairly easy to handle, so I hope I will get
5803 used to it. My old X40 was starting to fail, and I really needed a
5804 new laptop now. :)&lt;/p&gt;
5805
5806 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
5807 </description>
5808 </item>
5809
5810 <item>
5811 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
5812 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
5813 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
5814 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
5815 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
5816 perfectly capable of, and I have to do it manually to get things
5817 working. One such task is to find out what firmware packages are
5818 needed to get the hardware on my computer working. Most often this
5819 affect the wifi card, but some times it even affect the RAID
5820 controller or the ethernet card. Today I pushed version 0.4 of the
5821 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
5822 including a new script isenkram-autoinstall-firmware handling the
5823 process of asking all the loaded kernel modules what firmware files
5824 they want, find debian packages providing these files and install the
5825 debian packages. Here is a test run on my laptop:&lt;/p&gt;
5826
5827 &lt;p&gt;&lt;pre&gt;
5828 # isenkram-autoinstall-firmware
5829 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5830 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5831 info: locating packages with the requested firmware files
5832 info: Updating APT sources after adding non-free APT source
5833 info: trying to install firmware-ipw2x00
5834 firmware-ipw2x00
5835 firmware-ipw2x00
5836 Preconfiguring packages ...
5837 Selecting previously deselected package firmware-ipw2x00.
5838 (Reading database ... 259727 files and directories currently installed.)
5839 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5840 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
5841 #
5842 &lt;/pre&gt;&lt;/p&gt;
5843
5844 &lt;p&gt;When all the requested firmware is present, a simple message is
5845 printed instead:&lt;/p&gt;
5846
5847 &lt;p&gt;&lt;pre&gt;
5848 # isenkram-autoinstall-firmware
5849 info: did not find any firmware files requested by loaded kernel modules. exiting
5850 #
5851 &lt;/pre&gt;&lt;/p&gt;
5852
5853 &lt;p&gt;It could use some polish, but it is already working well and saving
5854 me some time when setting up new machines. :)&lt;/p&gt;
5855
5856 &lt;p&gt;So, how does it work? It look at the set of currently loaded
5857 kernel modules, and look up each one of them using modinfo, to find
5858 the firmware files listed in the module meta-information. Next, it
5859 download the Contents file from a nearby APT mirror, and search for
5860 the firmware files in this file to locate the package with the
5861 requested firmware file. If the package is in the non-free section, a
5862 non-free APT source is added and the package is installed using
5863 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
5864 machine.&lt;/p&gt;
5865
5866 &lt;p&gt;I hope someone find time to implement a more polished version of
5867 this script as part of the hw-detect debian-installer module, to
5868 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
5869 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
5870 firmware during a PXE install when the packages already are available
5871 from the nearby Debian mirror.&lt;/p&gt;
5872 </description>
5873 </item>
5874
5875 <item>
5876 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
5877 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
5878 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
5879 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
5880 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5881 the screen just turn black when Linux boot, either during installation
5882 or on first boot from the hard disk. I&#39;ve seen it once in a while the
5883 last few years, but only recently understood the cause. I&#39;ve seen it
5884 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5885 The reason seem to be in the wiring of some laptops. The system to
5886 control the screen background light is inverted, so when Linux try to
5887 turn the brightness fully on, it end up turning it off instead. I do
5888 not know which Linux drivers are affected, but this post is about the
5889 i915 driver used by the
5890 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
5891 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
5892
5893 &lt;p&gt;The problem can be worked around two ways. Either by adding
5894 i915.invert_brightness=1 as a kernel option, or by adding a file in
5895 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
5896 option when it load the i915 kernel module. On Debian and Ubuntu, it
5897 can be done by running these commands as root:&lt;/p&gt;
5898
5899 &lt;pre&gt;
5900 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
5901 update-initramfs -u -k all
5902 &lt;/pre&gt;
5903
5904 &lt;p&gt;Since March 2012 there is
5905 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
5906 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
5907 hardware have this problem, and get the driver to invert the
5908 brightness setting automatically. To use it, one need to add a row in
5909 &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
5910 intel_quirks array&lt;/a&gt; in the driver source
5911 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
5912 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
5913 number (vendor number 8086 is assumed) and subdevice vendor and device
5914 number.&lt;/p&gt;
5915
5916 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
5917 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
5918
5919 &lt;p&gt;&lt;pre&gt;
5920 00:02.0 VGA compatible controller [0300]: Intel Corporation \
5921 3rd Gen Core processor Graphics Controller [8086:0156] \
5922 (rev 09) (prog-if 00 [VGA controller])
5923 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
5924 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5925 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5926 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
5927 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
5928 Latency: 0
5929 Interrupt: pin A routed to IRQ 42
5930 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
5931 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
5932 Region 4: I/O ports at 4000 [size=64]
5933 Expansion ROM at &lt;unassigned&gt; [disabled]
5934 Capabilities: &lt;access denied&gt;
5935 Kernel driver in use: i915
5936 &lt;/pre&gt;&lt;/p&gt;
5937
5938 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
5939
5940 &lt;p&gt;&lt;pre&gt;
5941 struct intel_quirk intel_quirks[] = {
5942 ...
5943 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5944 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
5945 ...
5946 }
5947 &lt;/pre&gt;&lt;/p&gt;
5948
5949 &lt;p&gt;According to the kernel module instructions (as seen using
5950 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
5951 invert_brightness flag should be sent to the
5952 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
5953 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
5954 developers. But my email about the laptop sent 2013-06-03 have not
5955 yet shown up in
5956 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
5957 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
5958 emails from non-subscribers. Because of this, I sent my patch also to
5959 the Debian bug tracking system instead as
5960 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
5961 sure the patch is not lost.&lt;/p&gt;
5962
5963 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
5964 with this problem working properly with Linux. If you use Gnome, your
5965 worries should be over at this point. But if you use KDE, there is
5966 something in KDE ignoring the invert_brightness setting and turning on
5967 the screen during login. I&#39;ve reported it to Debian as
5968 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
5969 have no idea yet how to figure out exactly what subsystem is doing
5970 this. Perhaps you can help? Perhaps you know what the Gnome
5971 developers did to handle this, and this can give a clue to the KDE
5972 developers? Or you know where in KDE the screen brightness is changed
5973 during login? If so, please update the BTS report (or get in touch if
5974 you do not know how to update BTS).&lt;/p&gt;
5975
5976 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
5977 acpi_backlight=vendor, to disable ACPI backlight support completely,
5978 as the ACPI information on the machine is trash and it is better to
5979 leave it to the intel video driver to control the screen
5980 backlight.&lt;/p&gt;
5981 </description>
5982 </item>
5983
5984 <item>
5985 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
5986 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
5987 <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>
5988 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
5989 <description>&lt;p&gt;Two days ago, I asked
5990 &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
5991 I could install Linux on a Packard Bell EasyNote LV computer
5992 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
5993 with the obstacles put in the way of Linux users on a laptop with UEFI
5994 and Windows 8.&lt;/p&gt;
5995
5996 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
5997 secure booting or fast boot. I suspect fast boot was the problem,
5998 causing the firmware to boot directly from HD without considering any
5999 key presses and alternative devices, but do not know UEFI settings
6000 enough to tell.&lt;/p&gt;
6001
6002 &lt;p&gt;There is no way to install Linux on the machine in question without
6003 opening the box and disconnecting the hard drive! This is as far as I
6004 can tell, the only way to get access to the firmware setup menu
6005 without accepting the Windows 8 license agreement. I am told (and
6006 found description on how to) that it is possible to configure the
6007 firmware setup once booted into Windows 8. But as I believe the terms
6008 of that agreement are completely unacceptable, accepting the license
6009 was never an alternative. I do not enter agreements I do not intend
6010 to follow.&lt;/p&gt;
6011
6012 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
6013 waste many hours on this, but luckily there was a way to get it to
6014 work. But I would not recommend it to anyone planning to run Linux on
6015 it, and I have become sceptical to Windows 8 certified laptops. Is
6016 this the way Linux will be forced out of the market place, by making
6017 it close to impossible for &quot;normal&quot; users to install Linux without
6018 accepting the Microsoft Windows license terms? Or at least not
6019 without risking to loose the warranty?&lt;/p&gt;
6020
6021 &lt;p&gt;I&#39;ve updated the
6022 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
6023 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
6024 do not have to struggle as much as I did to get Linux into the
6025 machine.&lt;/p&gt;
6026
6027 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6028 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
6029 </description>
6030 </item>
6031
6032 <item>
6033 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
6034 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
6035 <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>
6036 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
6037 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
6038 new laptops for my parents and a few others. I bought Packard Bell
6039 Easynote LV to run Kubuntu on and use as their home computer. But I
6040 am completely unable to figure out how to install Linux on it. The
6041 computer is preinstalled with Windows 8, and I suspect it uses UEFI
6042 instead of a BIOS to boot.&lt;/p&gt;
6043
6044 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
6045 to get it to boot the Linux installer from my USB stick. I have yet
6046 to try the DVD install, and still hope it will work. when I turn on
6047 the computer, there is no information on what buttons to press to get
6048 the normal boot menu. I expect to get some boot menu to select PXE or
6049 USB stick booting. When booting, it first ask for the language to
6050 use, then for some regional settings, and finally if I will accept the
6051 Windows 8 terms of use. As these terms are completely unacceptable to
6052 me, I have no other choice but to turn off the computer and try again
6053 to get it to boot the Linux installer.&lt;/p&gt;
6054
6055 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
6056 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
6057 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
6058 installed on this machine, please get in touch or update that wiki
6059 page. If I can&#39;t find a way to install Linux, I will have to return
6060 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
6061
6062 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
6063 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
6064 on new Laptops?&lt;/p&gt;
6065 </description>
6066 </item>
6067
6068 <item>
6069 <title>How to transform a Debian based system to a Debian Edu installation</title>
6070 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
6071 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
6072 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
6073 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
6074 an operating system based on Debian intended for use in schools. It
6075 contain a turn-key solution for the computer network provided to
6076 pupils in the primary schools. It provide both the central server,
6077 network boot servers and desktop environments with heaps of
6078 educational software. The project was founded almost 12 years ago,
6079 2001-07-02. If you want to support the project, which is in need for
6080 cash to fund developer gatherings and other project related activity,
6081 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
6082 donate some money&lt;/a&gt;.
6083
6084 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
6085 lists and elsewhere, is the question on how to transform a Debian or
6086 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
6087 hard, and last week I wrote a script to replicate the steps done by
6088 the Debian Edu installer.&lt;/p&gt;
6089
6090 &lt;p&gt;The script,
6091 &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;
6092 in the debian-edu-config package, will go through these six steps and
6093 transform an existing Debian Wheezy or Ubuntu (untested) installation
6094 into a Debian Edu Workstation:&lt;/p&gt;
6095
6096 &lt;ol&gt;
6097
6098 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
6099 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
6100 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
6101 our configuration.&lt;/li&gt;
6102 &lt;li&gt;Preseed debconf database with profile setup in
6103 /etc/debian-edu/config, and run tasksel to install packages
6104 according to the profile specified in the config above,
6105 overriding some of the Debian automation machinery.&lt;/li&gt;
6106 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
6107 that could not be done using preseeding.&lt;/li&gt;
6108 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
6109
6110 &lt;/ol&gt;
6111
6112 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
6113 replicated like this. Disk partitioning and LVM setup, for example.
6114 So this script just assume there is enough disk space to install all
6115 the needed packages.&lt;/p&gt;
6116
6117 &lt;p&gt;The script was created to help a Debian Edu student working on
6118 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
6119 Debian Edu client, and using it he can take the existing
6120 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
6121 transform it into a fully functioning Debian Edu Workstation (or
6122 Roaming Workstation, or whatever :).&lt;/p&gt;
6123
6124 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
6125 If a LXDE based Roaming workstation is wanted instead, modify the
6126 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
6127
6128 &lt;p&gt;&lt;pre&gt;
6129 PROFILE=&quot;Roaming-Workstation&quot;
6130 DESKTOP=&quot;lxde&quot;
6131 &lt;/pre&gt;&lt;/p&gt;
6132
6133 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
6134 the cloud, by starting with a virtual Debian installation at some
6135 virtual hosting service and setting up all the services on first
6136 boot.&lt;/p&gt;
6137 </description>
6138 </item>
6139
6140 <item>
6141 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
6142 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
6143 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
6144 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
6145 <description>&lt;P&gt;In January,
6146 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
6147 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
6148 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
6149 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
6150 marvellous construction system from Denmark. We also created
6151 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
6152 a place to take notes and write down our plans and hopes. And several
6153 people showed up to help. I was very happy to see the effect of my
6154 call. Since the small start, we have a debtags tag
6155 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
6156 tag for LEGO related packages, and now count 10 packages related to
6157 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
6158
6159 &lt;p&gt;&lt;table&gt;
6160 &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;
6161 &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;
6162 &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;
6163 &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;
6164 &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;
6165 &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;
6166 &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;
6167 &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;
6168 &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;
6169 &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;
6170 &lt;/table&gt;&lt;/p&gt;
6171
6172 &lt;p&gt;Some of these are available in Wheezy, and all but one are
6173 currently available in Jessie/testing. leocad is so far only
6174 available in experimental.&lt;/p&gt;
6175
6176 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
6177 adding the rest of the great free software tools available on Linux
6178 for LEGO designers.&lt;/p&gt;
6179 </description>
6180 </item>
6181
6182 <item>
6183 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
6184 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
6185 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
6186 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
6187 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
6188 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
6189 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
6190 Debian release, and I expect to move my machines at home over to it fairly
6191 soon.&lt;/p&gt;
6192
6193 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
6194 in particular make me very happy to see included. The
6195 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
6196 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
6197 included for the first time. Alongside similar programs like
6198 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
6199 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
6200 it allow for visual programming where syntax errors can not happen,
6201 and a friendly programming environment for learning to control the
6202 computer. Scratch will also be included in the next release of Debian
6203 Edu.&lt;/a&gt;
6204
6205 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
6206 Edu/Skolelinux release too. The
6207 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
6208 alpha release&lt;/a&gt; went out last week, and the next should soon
6209 follow.&lt;p&gt;
6210 </description>
6211 </item>
6212
6213 <item>
6214 <title>Isenkram 0.2 finally in the Debian archive</title>
6215 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
6216 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
6217 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
6218 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
6219 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
6220 for many months. I uploaded it to the Debian experimental suite
6221 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
6222
6223 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
6224 install to work with a pluggable hardware device. The suggestion pop
6225 up when the device is plugged in. For example if a Lego Mindstorm NXT
6226 is inserted, it will suggest to install the program needed to program
6227 the NXT controller. Give it a go, and report bugs and suggestions to
6228 BTS. :)&lt;/p&gt;
6229 </description>
6230 </item>
6231
6232 <item>
6233 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
6234 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
6235 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
6236 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
6237 <description>&lt;p&gt;My
6238 &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
6239 bitcoin related blog post&lt;/a&gt; mentioned that the new
6240 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
6241 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6242 2013-01-19, and have been available in unstable since then. It was
6243 automatically copied to Ubuntu, and is available in their Raring
6244 version too.&lt;/p&gt;
6245
6246 &lt;p&gt;But there is a strange problem with the build that block this new
6247 version from being available on the i386 and kfreebsd-i386
6248 architectures. For some strange reason, the autobuilders in Debian
6249 for these architectures fail to run the test suite on these
6250 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
6251 We are so far unable to reproduce it when building it manually, and
6252 no-one have been able to propose a fix. If you got an idea what is
6253 failing, please let us know via the BTS.&lt;/p&gt;
6254
6255 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
6256 I often run low on disk space, is the fact that the client will exit
6257 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
6258 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
6259 it. :)&lt;/p&gt;
6260
6261 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
6262 activities, please send Bitcoin donations to my address
6263 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6264 </description>
6265 </item>
6266
6267 <item>
6268 <title>Welcome to the world, Isenkram!</title>
6269 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
6270 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
6271 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
6272 <description>&lt;p&gt;Yesterday, I
6273 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
6274 for testers&lt;/a&gt; for my prototype for making Debian better at handling
6275 pluggable hardware devices, which I
6276 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
6277 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
6278 up, and caused me to really want to to open up the development to more
6279 people. But before I did this, I want to come up with a sensible name
6280 for this project. Today I finally decided on a new name, and I have
6281 renamed the project from hw-support-handler to this new name. In the
6282 process, I moved the source to git and made it available as a
6283 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
6284 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
6285 To fetch and build the latest version of the source, use&lt;/p&gt;
6286
6287 &lt;pre&gt;
6288 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6289 cd isenkram &amp;&amp; git-buildpackage -us -uc
6290 &lt;/pre&gt;
6291
6292 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
6293 want to hack on the source or improve the package, please go ahead.
6294 But please talk to me first on IRC or via email before you do major
6295 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
6296
6297 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
6298 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6299 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
6300 the German word eisenkram, for those that are familiar with that
6301 word.&lt;/p&gt;
6302
6303 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
6304 instructions, to avoid confusing people with an error from the signing
6305 process.&lt;/p&gt;
6306
6307 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
6308 clone argument to avoid the need for authentication.&lt;/p&gt;
6309 </description>
6310 </item>
6311
6312 <item>
6313 <title>First prototype ready making hardware easier to use in Debian</title>
6314 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
6315 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
6316 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
6317 <description>&lt;p&gt;Early this month I set out to try to
6318 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
6319 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
6320 prototype is working, and it is ready for a larger audience. To test
6321 it, fetch the
6322 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
6323 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
6324 package. You might have to log out and in again activate the
6325 autostart script.&lt;/p&gt;
6326
6327 &lt;p&gt;The design is simple:&lt;/p&gt;
6328
6329 &lt;ul&gt;
6330
6331 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
6332 hw-support-handlerd to start when the user log in.&lt;/li&gt;
6333
6334 &lt;li&gt;This program listen for kernel events about new hardware (directly
6335 from the kernel like udev does), not using HAL dbus events as I
6336 initially did.&lt;/li&gt;
6337
6338 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
6339 the APT database, a database
6340 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
6341 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
6342
6343 &lt;li&gt;If a package is mapped to the hardware in question, the package
6344 isn&#39;t installed yet and this is the first time the hardware was
6345 plugged in, show a desktop notification suggesting to install the
6346 package or packages.&lt;/li&gt;
6347
6348 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
6349 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
6350
6351 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
6352 package while showing progress information in a window.&lt;/li&gt;
6353
6354 &lt;/ul&gt;
6355
6356 &lt;p&gt;I still need to come up with a better name for the system. Here
6357 are some screen shots showing the prototype in action. First the
6358 notification, then the password request, and finally the request to
6359 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
6360
6361 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
6362 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
6363 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
6364 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
6365 &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;
6366
6367 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
6368 is already useful. The database of hardware to package mappings also
6369 need more work. It is currently compatible with the Ubuntu way of
6370 storing such information in the package control file, but could be
6371 changed to use other formats instead or in addition to the current
6372 method. I&#39;ve dropped the use of discover for this mapping, as the
6373 modalias approach is more flexible and easier to use on Linux as long
6374 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
6375
6376 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
6377 here is the command required to check out and build the source: Use
6378 &#39;&lt;tt&gt;svn checkout
6379 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6380 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
6381 devscripts package.&lt;/p&gt;
6382
6383 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
6384 renamed to Isenkram and the source moved from the Debian Edu
6385 subversion repository to a Debian collab-maint git repository. See
6386 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
6387 instructions&lt;/a&gt; for details.&lt;/p&gt;
6388 </description>
6389 </item>
6390
6391 <item>
6392 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
6393 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
6394 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
6395 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
6396 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
6397 suddenly in bed. With a quiet whimper, it went completely quiet and
6398 black. The power button was no longer able to turn it on. It was a
6399 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6400 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6401 Compaq I had before that. Now I need to find a replacement. To keep
6402 going during Christmas, I moved the one year old SSD disk to my old
6403 X40 where it fitted (only one I had left that could use it), but it is
6404 not a durable solution.
6405
6406 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
6407 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
6408
6409 &lt;ul&gt;
6410
6411 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
6412 than A4).&lt;/li&gt;
6413 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
6414 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
6415 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
6416 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
6417 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
6418 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
6419 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
6420 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
6421 size).&lt;/li&gt;
6422 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
6423 X.org packages.&lt;/li&gt;
6424 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
6425 the time).
6426
6427 &lt;/ul&gt;
6428
6429 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
6430 list. The reason is simply that the specifications on laptops the
6431 last 10-15 years have been sufficient for my needs, and I have to look
6432 at other features to choose my laptop. But are there still made as
6433 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6434 robust, and Thinkpads seem to be heading in the wrong direction since
6435 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
6436 still be useful.&lt;/p&gt;
6437
6438 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
6439 external keyboard? I&#39;ll have to check the
6440 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
6441 well-supported laptops, or perhaps just buy one preinstalled from one
6442 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
6443 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
6444 </description>
6445 </item>
6446
6447 <item>
6448 <title>How to find a browser plugin supporting a given MIME type</title>
6449 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
6450 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
6451 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
6452 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
6453 install to get support for a given MIME type. Thanks to
6454 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
6455 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
6456 Unfortunately, not very many packages provide the needed meta
6457 information, Anyway, here is a small script to look up all browser
6458 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
6459
6460 &lt;pre&gt;
6461 #!/usr/bin/python
6462 import sys
6463 import apt
6464 def pkgs_handling_mimetype(mimetype):
6465 cache = apt.Cache()
6466 cache.open(None)
6467 thepkgs = []
6468 for pkg in cache:
6469 version = pkg.candidate
6470 if version is None:
6471 version = pkg.installed
6472 if version is None:
6473 continue
6474 record = version.record
6475 if not record.has_key(&#39;Npp-MimeType&#39;):
6476 continue
6477 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
6478 for t in mime_types:
6479 t = t.rstrip().strip()
6480 if t == mimetype:
6481 thepkgs.append(pkg.name)
6482 return thepkgs
6483 mimetype = &quot;audio/ogg&quot;
6484 if 1 &lt; len(sys.argv):
6485 mimetype = sys.argv[1]
6486 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
6487 for pkg in pkgs_handling_mimetype(mimetype):
6488 print &quot; %s&quot; %pkg
6489 &lt;/pre&gt;
6490
6491 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
6492
6493 &lt;pre&gt;
6494 % ./apt-find-browserplug-for-mimetype
6495 Browser plugin packages supporting audio/ogg:
6496 gecko-mediaplayer
6497 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6498 Browser plugin packages supporting application/x-shockwave-flash:
6499 browser-plugin-gnash
6500 %
6501 &lt;/pre&gt;
6502
6503 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
6504 itself to query for plugins and propose to install the needed
6505 packages. It would be great if Debian supported such feature too. Is
6506 anyone working on adding it?&lt;/p&gt;
6507
6508 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
6509 request for icweasel support for this feature is
6510 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
6511 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
6512 of manpower and wish for a different design is the reason thus feature
6513 is not yet in iceweasel from Debian.&lt;/p&gt;
6514 </description>
6515 </item>
6516
6517 <item>
6518 <title>What is the most supported MIME type in Debian?</title>
6519 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
6520 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
6521 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
6522 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
6523 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
6524 proposal to make it possible for a Desktop application to propose to
6525 the user some package to install to gain support for a given MIME
6526 type, font, library etc. that is currently missing. With such
6527 mechanism in place, it would be possible for the desktop to
6528 automatically propose and install leocad if some LDraw file is
6529 downloaded by the browser.&lt;/p&gt;
6530
6531 &lt;p&gt;To get some idea about the current content of the archive, I decided
6532 to write a simple program to extract all .desktop files from the
6533 Debian archive and look up the claimed MIME support there. The result
6534 can be found on the
6535 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
6536 site&lt;/a&gt;. Using the collected information, it become possible to
6537 answer the question in the title. Here are the 20 most supported MIME
6538 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6539 The complete list is available from the link above.&lt;/p&gt;
6540
6541 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
6542
6543 &lt;pre&gt;
6544 count MIME type
6545 ----- -----------------------
6546 32 text/plain
6547 30 audio/mpeg
6548 29 image/png
6549 28 image/jpeg
6550 27 application/ogg
6551 26 audio/x-mp3
6552 25 image/tiff
6553 25 image/gif
6554 22 image/bmp
6555 22 audio/x-wav
6556 20 audio/x-flac
6557 19 audio/x-mpegurl
6558 18 video/x-ms-asf
6559 18 audio/x-musepack
6560 18 audio/x-mpeg
6561 18 application/x-ogg
6562 17 video/mpeg
6563 17 audio/x-scpls
6564 17 audio/ogg
6565 16 video/x-ms-wmv
6566 &lt;/pre&gt;
6567
6568 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
6569
6570 &lt;pre&gt;
6571 count MIME type
6572 ----- -----------------------
6573 33 text/plain
6574 32 image/png
6575 32 image/jpeg
6576 29 audio/mpeg
6577 27 image/gif
6578 26 image/tiff
6579 26 application/ogg
6580 25 audio/x-mp3
6581 22 image/bmp
6582 21 audio/x-wav
6583 19 audio/x-mpegurl
6584 19 audio/x-mpeg
6585 18 video/mpeg
6586 18 audio/x-scpls
6587 18 audio/x-flac
6588 18 application/x-ogg
6589 17 video/x-ms-asf
6590 17 text/html
6591 17 audio/x-musepack
6592 16 image/x-xbitmap
6593 &lt;/pre&gt;
6594
6595 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
6596
6597 &lt;pre&gt;
6598 count MIME type
6599 ----- -----------------------
6600 31 text/plain
6601 31 image/png
6602 31 image/jpeg
6603 29 audio/mpeg
6604 28 application/ogg
6605 27 image/gif
6606 26 image/tiff
6607 26 audio/x-mp3
6608 23 audio/x-wav
6609 22 image/bmp
6610 21 audio/x-flac
6611 20 audio/x-mpegurl
6612 19 audio/x-mpeg
6613 18 video/x-ms-asf
6614 18 video/mpeg
6615 18 audio/x-scpls
6616 18 application/x-ogg
6617 17 audio/x-musepack
6618 16 video/x-ms-wmv
6619 16 video/x-msvideo
6620 &lt;/pre&gt;
6621
6622 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
6623 information mentioned in DEP-11. I have not yet had time to look at
6624 it, but hope the PackageKit people in Debian are on top of these
6625 issues.&lt;/p&gt;
6626
6627 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
6628 discovering a typo in my script.&lt;/p&gt;
6629 </description>
6630 </item>
6631
6632 <item>
6633 <title>Using modalias info to find packages handling my hardware</title>
6634 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
6635 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
6636 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
6637 <description>&lt;p&gt;Yesterday, I wrote about the
6638 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
6639 values provided by the Linux kernel&lt;/a&gt; following my hope for
6640 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
6641 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
6642 modalias values attached to package names can be used to map packages
6643 to hardware. This allow the system to look up and suggest relevant
6644 packages when I plug in some new hardware into my machine, and replace
6645 discover and discover-data as the database used to map hardware to
6646 packages.&lt;/p&gt;
6647
6648 &lt;p&gt;I create a modaliases file with entries like the following,
6649 containing package name, kernel module name (if relevant, otherwise
6650 the package name) and globs matching the relevant hardware
6651 modalias.&lt;/p&gt;
6652
6653 &lt;p&gt;&lt;blockquote&gt;
6654 Package: package-name
6655 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
6656 &lt;/blockquote&gt;&lt;/p&gt;
6657
6658 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
6659 for a given modalias value using this file.&lt;/p&gt;
6660
6661 &lt;p&gt;An entry like this would suggest the video and picture application
6662 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
6663
6664 &lt;p&gt;&lt;blockquote&gt;
6665 Package: cheese
6666 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
6667 &lt;/blockquote&gt;&lt;/p&gt;
6668
6669 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
6670 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
6671
6672 &lt;p&gt;&lt;blockquote&gt;
6673 Package: pcmciautils
6674 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6675 &lt;/blockquote&gt;&lt;/p&gt;
6676
6677 &lt;p&gt;An entry like this would suggest the package colorhug-client when
6678 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
6679
6680 &lt;p&gt;&lt;blockquote&gt;
6681 Package: colorhug-client
6682 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
6683 &lt;/blockquote&gt;&lt;/p&gt;
6684
6685 &lt;p&gt;I believe the format is compatible with the format of the Packages
6686 file in the Debian archive. Ubuntu already uses their Packages file
6687 to store their mappings from packages to hardware.&lt;/p&gt;
6688
6689 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
6690 announce the hardware it support in a way my prototype understand.
6691 This allow those publishing packages in an APT source outside the
6692 Debian archive as well as those backporting packages to make sure the
6693 hardware mapping are included in the package meta information. I&#39;ve
6694 tested such header in the pymissile package, and its modalias mapping
6695 is working as it should with my prototype. It even made it to Ubuntu
6696 Raring.&lt;/p&gt;
6697
6698 &lt;p&gt;To test if it was possible to look up supported hardware using only
6699 the shell tools available in the Debian installer, I wrote a shell
6700 implementation of the lookup code. The idea is to create files for
6701 each modalias and let the shell do the matching. Please check out and
6702 try the
6703 &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;
6704 shell script. It run without any extra dependencies and fetch the
6705 hardware mappings from the Debian archive and the subversion
6706 repository where I currently work on my prototype.&lt;/p&gt;
6707
6708 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
6709 install yubikey-personalization:&lt;/p&gt;
6710
6711 &lt;p&gt;&lt;blockquote&gt;
6712 % ./hw-support-lookup
6713 &lt;br&gt;yubikey-personalization
6714 &lt;br&gt;%
6715 &lt;/blockquote&gt;&lt;/p&gt;
6716
6717 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6718 propose to install the pcmciautils package:&lt;/p&gt;
6719
6720 &lt;p&gt;&lt;blockquote&gt;
6721 % ./hw-support-lookup
6722 &lt;br&gt;pcmciautils
6723 &lt;br&gt;%
6724 &lt;/blockquote&gt;&lt;/p&gt;
6725
6726 &lt;p&gt;If you know of any hardware-package mapping that should be added to
6727 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
6728 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
6729
6730 &lt;p&gt;It could be possible to generate several of the mappings between
6731 packages and hardware. One source would be to look at packages with
6732 kernel modules, ie packages with *.ko files in /lib/modules/, and
6733 extract their modalias information. Another would be to look at
6734 packages with udev rules, ie packages with files in
6735 /lib/udev/rules.d/, and extract their vendor/model information to
6736 generate a modalias matching rule. I have not tested any of these to
6737 see if it work.&lt;/p&gt;
6738
6739 &lt;p&gt;If you want to help implementing a system to let us propose what
6740 packages to install when new hardware is plugged into a Debian
6741 machine, please send me an email or talk to me on
6742 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
6743 </description>
6744 </item>
6745
6746 <item>
6747 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
6748 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
6749 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
6750 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
6751 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
6752 information, to find the packages that support a given piece of
6753 hardware, I refreshed my memory regarding modalias values, and decided
6754 to document the details. Here are my findings so far, also available
6755 in
6756 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
6757 Debian Edu subversion repository&lt;/a&gt;:
6758
6759 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
6760
6761 &lt;p&gt;This document try to explain what the different types of modalias
6762 values stands for. It is in part based on information from
6763 &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;,
6764 &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;,
6765 &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
6766 &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;.
6767
6768 &lt;p&gt;The modalias entries for a given Linux machine can be found using
6769 this shell script:&lt;/p&gt;
6770
6771 &lt;pre&gt;
6772 find /sys -name modalias -print0 | xargs -0 cat | sort -u
6773 &lt;/pre&gt;
6774
6775 &lt;p&gt;The supported modalias globs for a given kernel module can be found
6776 using modinfo:&lt;/p&gt;
6777
6778 &lt;pre&gt;
6779 % /sbin/modinfo psmouse | grep alias:
6780 alias: serio:ty05pr*id*ex*
6781 alias: serio:ty01pr*id*ex*
6782 %
6783 &lt;/pre&gt;
6784
6785 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
6786
6787 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
6788 Bridge memory controller:&lt;/p&gt;
6789
6790 &lt;p&gt;&lt;blockquote&gt;
6791 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6792 &lt;/blockquote&gt;&lt;/p&gt;
6793
6794 &lt;p&gt;This represent these values:&lt;/p&gt;
6795
6796 &lt;pre&gt;
6797 v 00008086 (vendor)
6798 d 00002770 (device)
6799 sv 00001028 (subvendor)
6800 sd 000001AD (subdevice)
6801 bc 06 (bus class)
6802 sc 00 (bus subclass)
6803 i 00 (interface)
6804 &lt;/pre&gt;
6805
6806 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
6807 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
6808 0600. The 0600 class is a host bridge. Other useful bus values are
6809 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
6810
6811 &lt;p&gt;Not sure how to figure out the interface value, nor what it
6812 means.&lt;/p&gt;
6813
6814 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
6815
6816 &lt;p&gt;Some typical USB entries can look like this. This is an internal
6817 USB hub in a laptop:&lt;/p&gt;
6818
6819 &lt;p&gt;&lt;blockquote&gt;
6820 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6821 &lt;/blockquote&gt;&lt;/p&gt;
6822
6823 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
6824
6825 &lt;pre&gt;
6826 v 1D6B (device vendor)
6827 p 0001 (device product)
6828 d 0206 (bcddevice)
6829 dc 09 (device class)
6830 dsc 00 (device subclass)
6831 dp 00 (device protocol)
6832 ic 09 (interface class)
6833 isc 00 (interface subclass)
6834 ip 00 (interface protocol)
6835 &lt;/pre&gt;
6836
6837 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
6838 class is in the interface class section. For a simple USB web camera,
6839 these alias entries show up:&lt;/p&gt;
6840
6841 &lt;p&gt;&lt;blockquote&gt;
6842 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6843 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6844 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6845 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6846 &lt;/blockquote&gt;&lt;/p&gt;
6847
6848 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
6849 camera), 0101 is audio control device and 0102 is audio streaming (aka
6850 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
6851
6852 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
6853
6854 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
6855 receiver in a Thinkpad X40:&lt;/p&gt;
6856
6857 &lt;p&gt;&lt;blockquote&gt;
6858 acpi:IBM0071:PNP0511:
6859 &lt;/blockquote&gt;&lt;/p&gt;
6860
6861 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
6862
6863 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
6864
6865 &lt;p&gt;The DMI table contain lots of information about the computer case
6866 and model. This is an entry for a IBM Thinkpad X40, fetched from
6867 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
6868
6869 &lt;p&gt;&lt;blockquote&gt;
6870 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6871 &lt;/blockquote&gt;&lt;/p&gt;
6872
6873 &lt;p&gt;The values present are&lt;/p&gt;
6874
6875 &lt;pre&gt;
6876 bvn IBM (BIOS vendor)
6877 bvr 1UETB6WW(1.66) (BIOS version)
6878 bd 06/15/2005 (BIOS date)
6879 svn IBM (system vendor)
6880 pn 2371H4G (product name)
6881 pvr ThinkPadX40 (product version)
6882 rvn IBM (board vendor)
6883 rn 2371H4G (board name)
6884 rvr NotAvailable (board version)
6885 cvn IBM (chassis vendor)
6886 ct 10 (chassis type)
6887 cvr NotAvailable (chassis version)
6888 &lt;/pre&gt;
6889
6890 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
6891 found in the dmidecode source:&lt;/p&gt;
6892
6893 &lt;pre&gt;
6894 3 Desktop
6895 4 Low Profile Desktop
6896 5 Pizza Box
6897 6 Mini Tower
6898 7 Tower
6899 8 Portable
6900 9 Laptop
6901 10 Notebook
6902 11 Hand Held
6903 12 Docking Station
6904 13 All In One
6905 14 Sub Notebook
6906 15 Space-saving
6907 16 Lunch Box
6908 17 Main Server Chassis
6909 18 Expansion Chassis
6910 19 Sub Chassis
6911 20 Bus Expansion Chassis
6912 21 Peripheral Chassis
6913 22 RAID Chassis
6914 23 Rack Mount Chassis
6915 24 Sealed-case PC
6916 25 Multi-system
6917 26 CompactPCI
6918 27 AdvancedTCA
6919 28 Blade
6920 29 Blade Enclosing
6921 &lt;/pre&gt;
6922
6923 &lt;p&gt;The chassis type values are not always accurately set in the DMI
6924 table. For example my home server is a tower, but the DMI modalias
6925 claim it is a desktop.&lt;/p&gt;
6926
6927 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
6928
6929 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
6930 test machine:&lt;/p&gt;
6931
6932 &lt;p&gt;&lt;blockquote&gt;
6933 serio:ty01pr00id00ex00
6934 &lt;/blockquote&gt;&lt;/p&gt;
6935
6936 &lt;p&gt;The values present are&lt;/p&gt;
6937
6938 &lt;pre&gt;
6939 ty 01 (type)
6940 pr 00 (prototype)
6941 id 00 (id)
6942 ex 00 (extra)
6943 &lt;/pre&gt;
6944
6945 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
6946 the valid values are.&lt;/p&gt;
6947
6948 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
6949
6950 &lt;p&gt;There are heaps of other modalias subtypes according to
6951 file2alias.c. There is the rest of the list from that source: amba,
6952 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6953 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6954 vmbus, x86cpu and zorro. I did not spend time documenting all of
6955 these, as they do not seem relevant for my intended use with mapping
6956 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
6957
6958 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
6959
6960 &lt;p&gt;To check which kernel modules provide support for a given modalias,
6961 one can use the following shell script:&lt;/p&gt;
6962
6963 &lt;pre&gt;
6964 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
6965 echo &quot;$id&quot; ; \
6966 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
6967 done
6968 &lt;/pre&gt;
6969
6970 &lt;p&gt;The output can look like this (only the first few entries as the
6971 list is very long on my test machine):&lt;/p&gt;
6972
6973 &lt;pre&gt;
6974 acpi:ACPI0003:
6975 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
6976 acpi:device:
6977 FATAL: Module acpi:device: not found.
6978 acpi:IBM0068:
6979 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
6980 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
6981 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
6982 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6983 acpi:IBM0071:PNP0511:
6984 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
6985 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
6986 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
6987 [...]
6988 &lt;/pre&gt;
6989
6990 &lt;p&gt;If you want to help implementing a system to let us propose what
6991 packages to install when new hardware is plugged into a Debian
6992 machine, please send me an email or talk to me on
6993 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
6994
6995 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
6996 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
6997 in /sys/ with space in them.&lt;/p&gt;
6998 </description>
6999 </item>
7000
7001 <item>
7002 <title>Moved the pymissile Debian packaging to collab-maint</title>
7003 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
7004 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
7005 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
7006 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
7007 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
7008 Launcher and updated the Debian package
7009 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
7010 sure udev will fix the device permissions when it is plugged in. I
7011 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
7012 hopefully make the package be proposed by jockey in Ubuntu when a user
7013 plug in his rocket launcher. In the process I moved the source to a
7014 git repository under collab-maint, to make it easier for any DD to
7015 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
7016 is not very active, but the software still work for me even after five
7017 years of relative silence. The new git repository is not listed in
7018 the uploaded package yet, because I want to test the other changes a
7019 bit more before I upload the new version. If you want to check out
7020 the new version with a .desktop file included, visit the
7021 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
7022 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
7023 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
7024 </description>
7025 </item>
7026
7027 <item>
7028 <title>Lets make hardware dongles easier to use in Debian</title>
7029 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
7030 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
7031 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
7032 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
7033 general, is that there is a great package management system with the
7034 ability to automatically install software packages by downloading them
7035 from the distribution mirrors, but no way to get it to automatically
7036 install the packages I need to use the hardware I plug into my
7037 machine. Even if the package to use it is easily available from the
7038 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7039 suggest to automatically install the python-nxt, nbc and t2n packages
7040 I need to talk to it. When I plug in a Yubikey, it could propose the
7041 yubikey-personalization package. The information required to do this
7042 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
7043
7044 &lt;p&gt;Some years ago, I proposed to
7045 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
7046 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
7047 simple:
7048
7049 &lt;ul&gt;
7050
7051 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
7052 starting when a user log in.&lt;/li&gt;
7053
7054 &lt;li&gt;Set this program up to listen for kernel events emitted when new
7055 hardware is inserted into the computer.&lt;/li&gt;
7056
7057 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
7058 database mapping to packages, and take note of any non-installed
7059 packages.&lt;/li&gt;
7060
7061 &lt;li&gt;Show a message to the user proposing to install the discovered
7062 package, and make it easy to install it.&lt;/li&gt;
7063
7064 &lt;/ul&gt;
7065
7066 &lt;p&gt;I am not sure what the best way to implement this is, but my
7067 initial idea was to use dbus events to discover new hardware, the
7068 discover database to find packages and
7069 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
7070 packages.&lt;/p&gt;
7071
7072 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
7073 draft package is now checked into
7074 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
7075 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
7076 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
7077 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7078 the relevant packages in Debian, and uploaded a new version
7079 2.2013.01.09 to unstable. I also discovered that the current
7080 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
7081 package in Debian no longer discovered any USB devices, because
7082 /proc/bus/usb/devices is no longer present. I ported it to use
7083 libusb as a fall back option to get it working. The fixed package
7084 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
7085 because of the freeze).&lt;/p&gt;
7086
7087 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
7088 desktop notification to show up (only once, the first time it is
7089 inserted):&lt;/p&gt;
7090
7091 &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;
7092
7093 &lt;p&gt;For this prototype to be really useful, some way to automatically
7094 install the proposed packages by pressing the &quot;Please install
7095 program(s)&quot; button should to be implemented.&lt;/p&gt;
7096
7097 &lt;p&gt;If this idea seem useful to you, and you want to help make it
7098 happen, please help me update the discover-data database with mappings
7099 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
7100 list the package you would like to have installed when a given
7101 hardware device is inserted into your computer, and report bugs using
7102 reportbug if it isn&#39;t. Or, if you know of a better way to provide
7103 such mapping, please let me know.&lt;/p&gt;
7104
7105 &lt;p&gt;This prototype need more work, and there are several questions that
7106 should be considered before it is ready for production use. Is dbus
7107 the correct way to detect new hardware? At the moment I look for HAL
7108 dbus events on the system bus, because that is the events I could see
7109 on my Debian Squeeze KDE desktop. Are there better events to use?
7110 How should the user be notified? Is the desktop notification
7111 mechanism the best option, or should the background daemon raise a
7112 popup instead? How should packages be installed? When should they
7113 not be installed?&lt;/p&gt;
7114
7115 &lt;p&gt;If you want to help getting such feature implemented in Debian,
7116 please send me an email. :)&lt;/p&gt;
7117 </description>
7118 </item>
7119
7120 <item>
7121 <title>New IRC channel for LEGO designers using Debian</title>
7122 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
7123 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
7124 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
7125 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
7126 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
7127 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
7128 discovered I had to build all the tools myself because none were
7129 already in Debian Squeeze. If Debian support for LEGO is something
7130 you care about, please join me on the IRC channel
7131 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
7132 irc.debian.org). There is a lot that could be done to improve the
7133 Debian support for LEGO designers. For example both CAD software
7134 and Mindstorm compilers are missing. :)&lt;/p&gt;
7135
7136 &lt;p&gt;Update 2012-01-03: A
7137 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
7138 including links to Lego related packages is now available.&lt;/p&gt;
7139 </description>
7140 </item>
7141
7142 <item>
7143 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
7144 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
7145 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
7146 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
7147 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
7148 year! I hope next year will prove to be a good year.&lt;/p&gt;
7149
7150 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
7151 decentralised &quot;currency&quot; that allow people to transfer bitcoins
7152 between each other with minimal overhead, is a very interesting
7153 experiment. And as I wrote a few days ago, the bitcoin situation in
7154 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
7155 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
7156 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
7157 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
7158 for one of the ftpmasters to approve the new bitcoin-qt package
7159 name.&lt;/p&gt;
7160
7161 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
7162 team in Debian, you can easily test the package in Debian Squeeze
7163 using the following steps to get a set of working packages:&lt;/p&gt;
7164
7165 &lt;blockquote&gt;&lt;pre&gt;
7166 git clone git://git.debian.org/git/collab-maint/bitcoin
7167 cd bitcoin
7168 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7169 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7170 &lt;/pre&gt;&lt;/blockquote&gt;
7171
7172 &lt;p&gt;You might have to install some build dependencies as well. The
7173 list of commands should give you two packages, bitcoind and
7174 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7175 client will download the complete set of bitcoin &quot;blocks&quot;, which need
7176 around 5.6 GiB of data on my machine at the moment. Make sure your
7177 ~/.bitcoin/ directory have lots of spare room if you want to download
7178 all the blocks. The client will warn if the disk is getting full, so
7179 there is not really a problem if you got too little room, but you will
7180 not be able to get all the features out of the client.&lt;/p&gt;
7181
7182 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
7183 activities, please send Bitcoin donations to my address
7184 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7185 </description>
7186 </item>
7187
7188 <item>
7189 <title>A word on bitcoin support in Debian</title>
7190 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
7191 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
7192 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
7193 <description>&lt;p&gt;It has been a while since I wrote about
7194 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
7195 peer-to-peer based crypto-currency, and the reason is simply that I
7196 have been busy elsewhere. But two days ago, I started looking at the
7197 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
7198 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
7199 is now maintained by a
7200 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
7201 people&lt;/a&gt;, and the grunt work had already been done by this team. We
7202 owe a huge thank you to all these team members. :)
7203 But I was sad to discover that the bitcoin client is missing in
7204 Wheezy. It is only available in Sid (and an outdated client from
7205 backports). The client had several RC bugs registered in BTS blocking
7206 it from entering testing. To try to help the team and improve the
7207 situation, I spent some time providing patches and triaging the bug
7208 reports. I also had a look at the bitcoin package available from Matt
7209 Corallo in a
7210 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
7211 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
7212 Debian package.&lt;/p&gt;
7213
7214 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
7215 IRC, I pushed several patches into the collab-maint git repository to
7216 improve the package. It now contains fixes for the RC issues (not from
7217 me, but fixed by Scott Howard), build rules for a Qt GUI client
7218 package, konqueror support for the bitcoin: URI and bash completion
7219 setup. As I work on Debian Squeeze, I also created
7220 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
7221 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
7222 it and try to integrate it into the git repository before uploading a
7223 new version to unstable.
7224
7225 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
7226 centralized control currently exercised in the monetary system. I
7227 find it completely unacceptable that the USA government is collecting
7228 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7229 that the major credit card companies can block legal money
7230 transactions to Wikileaks. But for bitcoin to succeed, more people
7231 need to use bitcoins, and more people need to accept bitcoins when
7232 they sell products and services. Improving the bitcoin support in
7233 Debian is a small step in the right direction, but not enough.
7234 Unfortunately the user experience when browsing the web and wanting to
7235 pay with bitcoin is still not very good. The bitcoin: URI is a step
7236 in the right direction, but need to work in most or every browser in
7237 use. Also the bitcoin-qt client is too heavy to fire up to do a
7238 quick transaction. I believe there are other clients available, but
7239 have not tested them.&lt;/p&gt;
7240
7241 &lt;p&gt;My
7242 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
7243 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
7244 I received 20.15 BTC so far on the address I provided in my blog two
7245 years ago, as can be
7246 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
7247 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
7248 donation. The blockexplorer service demonstrates quite well that
7249 bitcoin is not quite anonymous and untracked. :) I wonder if the
7250 number of users have gone up since then. If you use bitcoin and want
7251 to show your support of my activity, please send Bitcoin donations to
7252 the same address as last time,
7253 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7254 </description>
7255 </item>
7256
7257 <item>
7258 <title>Git repository for song book for Computer Scientists</title>
7259 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
7260 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
7261 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
7262 <description>&lt;p&gt;As I
7263 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
7264 this summer&lt;/a&gt;, I have created a Computer Science song book a few
7265 years ago, and today I finally found time to create a public
7266 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
7267 repository for the project&lt;/a&gt;.&lt;/p&gt;
7268
7269 &lt;p&gt;If you want to help out, please clone the source and submit patches
7270 to the HTML version. To generate the PDF and PostScript version,
7271 please use prince XML, or let me know about a useful free software
7272 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
7273
7274 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
7275 PostScript formats at
7276 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
7277 Science Songbook&lt;/a&gt;.&lt;/p&gt;
7278 </description>
7279 </item>
7280
7281 <item>
7282 <title>Gratulerer med 19-årsdagen, Debian!</title>
7283 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
7284 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
7285 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
7286 <description>&lt;p&gt;I dag fyller
7287 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
7288 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
7289 si gratulerer med dagen, Debian!&lt;/p&gt;
7290 </description>
7291 </item>
7292
7293 <item>
7294 <title>Song book for Computer Scientists</title>
7295 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
7296 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
7297 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
7298 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
7299 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
7300 collecting computer related songs for use at parties. The original
7301 version was written in LaTeX, but a few years ago I got help from
7302 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7303 while keeping the ability to create a nice book in PDF format. I have
7304 not had time to maintain the book for a while now, and guess I should
7305 put it up on some public version control repository where others can
7306 help me extend and update the book. If anyone is volunteering to help
7307 me with this, send me an email. Also let me know if there are songs
7308 missing in my book.&lt;/p&gt;
7309
7310 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
7311 me today that I really should let all my readers share the joys of
7312 singing out load about programming, computers and computer networks.
7313 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
7314 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
7315 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
7316 Computer Science Songbook&lt;/a&gt;.
7317 </description>
7318 </item>
7319
7320 <item>
7321 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
7322 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
7323 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
7324 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
7325 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
7326 around 1000 at the moment. To be able to get help from the vendors
7327 when something go wrong, we want to keep the firmware on the servers
7328 up to date. If the firmware isn&#39;t the latest and greatest, the
7329 vendors typically refuse to start debugging any problems until the
7330 firmware is upgraded. So before every reboot, we want to upgrade the
7331 firmware, and we would really like everyone handling servers at the
7332 university to do this themselves when they plan to reboot a machine.
7333 For that to happen we at the unix server admin group need to provide
7334 the tools to do so.&lt;/p&gt;
7335
7336 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
7337 fetch and install the latest firmware for the servers we got. Most of
7338 our hardware are from Dell and HP, so I have focused on these servers
7339 so far. This blog post is about the Dell part.&lt;/P&gt;
7340
7341 &lt;p&gt;On the Dell FTP site I was lucky enough to find
7342 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
7343 with firmware information for all 11th generation servers, listing
7344 which firmware should be used on a given model and where on the FTP
7345 site I can find it. Using a simple perl XML parser I can then
7346 download the shell scripts Dell provides to do firmware upgrades from
7347 within Linux and reboot when all the firmware is primed and ready to
7348 be activated on the first reboot.&lt;/p&gt;
7349
7350 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
7351 Are there anyone working on similar tools for firmware upgrading all
7352 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
7353
7354 &lt;p&gt;&lt;pre&gt;
7355 #!/usr/bin/perl
7356 use strict;
7357 use warnings;
7358 use File::Temp qw(tempdir);
7359 BEGIN {
7360 # Install needed RHEL packages if missing
7361 my %rhelmodules = (
7362 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
7363 );
7364 for my $module (keys %rhelmodules) {
7365 eval &quot;use $module;&quot;;
7366 if ($@) {
7367 my $pkg = $rhelmodules{$module};
7368 system(&quot;yum install -y $pkg&quot;);
7369 eval &quot;use $module;&quot;;
7370 }
7371 }
7372 }
7373 my $errorsto = &#39;pere@hungry.com&#39;;
7374
7375 upgrade_dell();
7376
7377 exit 0;
7378
7379 sub run_firmware_script {
7380 my ($opts, $script) = @_;
7381 unless ($script) {
7382 print STDERR &quot;fail: missing script name\n&quot;;
7383 exit 1
7384 }
7385 print STDERR &quot;Running $script\n\n&quot;;
7386
7387 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
7388 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
7389 } else {
7390 print STDERR &quot;fail: firmware script returned error\n&quot;;
7391 }
7392 }
7393
7394 sub run_firmware_scripts {
7395 my ($opts, @dirs) = @_;
7396 # Run firmware packages
7397 for my $dir (@dirs) {
7398 print STDERR &quot;info: Running scripts in $dir\n&quot;;
7399 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
7400 while (my $s = readdir $dh) {
7401 next if $s =~ m/^\.\.?/;
7402 run_firmware_script($opts, &quot;$dir/$s&quot;);
7403 }
7404 closedir $dh;
7405 }
7406 }
7407
7408 sub download {
7409 my $url = shift;
7410 print STDERR &quot;info: Downloading $url\n&quot;;
7411 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
7412 }
7413
7414 sub upgrade_dell {
7415 my @dirs;
7416 my $product = `dmidecode -s system-product-name`;
7417 chomp $product;
7418
7419 if ($product =~ m/PowerEdge/) {
7420
7421 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7422 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
7423
7424 my $tmpdir = tempdir(
7425 CLEANUP =&gt; 1
7426 );
7427 chdir($tmpdir);
7428 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
7429 system(&#39;gunzip Catalog.xml.gz&#39;);
7430 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
7431 # -q is quiet, disabling interactivity and reducing console output
7432 my $fwopts = &quot;-q&quot;;
7433 if (@paths) {
7434 for my $url (@paths) {
7435 fetch_dell_fw($url);
7436 }
7437 run_firmware_scripts($fwopts, $tmpdir);
7438 } else {
7439 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
7440 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
7441 }
7442 chdir(&#39;/&#39;);
7443 } else {
7444 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
7445 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
7446 }
7447 }
7448
7449 sub fetch_dell_fw {
7450 my $path = shift;
7451 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
7452 download($url);
7453 }
7454
7455 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7456 # firmware packages to download from Dell. Only work for Linux
7457 # machines and 11th generation Dell servers.
7458 sub fetch_dell_fw_list {
7459 my $filename = shift;
7460
7461 my $product = `dmidecode -s system-product-name`;
7462 chomp $product;
7463 my ($mybrand, $mymodel) = split(/\s+/, $product);
7464
7465 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
7466
7467 my $xml = XMLin($filename);
7468 my @paths;
7469 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
7470 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
7471 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
7472 my $oscode;
7473 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
7474 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
7475 } else {
7476 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
7477 }
7478 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
7479 {
7480 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
7481 }
7482 }
7483 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
7484 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
7485
7486 # Drop application packages, only firmware and BIOS
7487 next if &#39;APAC&#39; eq $componenttype;
7488
7489 my $cpath = $component-&gt;{path};
7490 for my $path (@paths) {
7491 if ($cpath =~ m%/$path$%) {
7492 push(@paths, $cpath);
7493 }
7494 }
7495 }
7496 return @paths;
7497 }
7498 &lt;/pre&gt;
7499
7500 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
7501 it could work on other platforms with some tweaking. Anyone know a
7502 index like Catalog.xml is available from HP for HP servers? At the
7503 moment I maintain a similar list manually and it is quickly getting
7504 outdated.&lt;/p&gt;
7505 </description>
7506 </item>
7507
7508 <item>
7509 <title>How is booting into runlevel 1 different from single user boots?</title>
7510 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
7511 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
7512 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
7513 <description>&lt;p&gt;Wouter Verhelst have some
7514 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
7515 comments and opinions&lt;/a&gt; on my blog post on
7516 &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
7517 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
7518 &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
7519 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
7520 small piece of his comment now, and though it best to address the
7521 misunderstanding he bring forward:&lt;/p&gt;
7522
7523 &lt;p&gt;&lt;blockquote&gt;
7524 Currently, a system admin has four options: [...] boot to a
7525 single-user system (by adding &#39;single&#39; to the kernel command line;
7526 this runs rcS and rc1 scripts)
7527 &lt;/blockquote&gt;&lt;/p&gt;
7528
7529 &lt;p&gt;This make me believe Wouter believe booting into single user mode
7530 and booting into runlevel 1 is the same. I am not surprised he
7531 believe this, because it would make sense and is a quite sensible
7532 thing to believe. But because the boot in Debian is slightly broken,
7533 runlevel 1 do not work properly and it isn&#39;t the same as single user
7534 mode. I&#39;ll try to explain what is actually happing, but it is a bit
7535 hard to explain.&lt;/p&gt;
7536
7537 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
7538 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
7539 executed in single user mode is sulogin. Single user mode is a boot
7540 state &quot;between&quot; the runlevels, and when booting into single user mode,
7541 only the scripts in /etc/rcS.d/ are executed before the init process
7542 enters the single user state. When switching to runlevel 1, the state
7543 is in fact not ending in runlevel 1, but it passes through runlevel 1
7544 and end up in the single user mode (see /etc/rc1.d/S03single, which
7545 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
7546 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
7547 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7548 mode).&lt;/p&gt;
7549
7550 &lt;p&gt;This summary might make it clearer. When booting for the first
7551 time into single user mode, the following commands are executed:
7552 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
7553 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
7554 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
7555 trying to continue after visiting single user mode. Not all services
7556 are started again as they should, causing the machine to end up in an
7557 unpredicatble state. This is why Debian admins recommend rebooting
7558 after visiting single user mode.&lt;/p&gt;
7559
7560 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
7561 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
7562 to runlevel 1, the services started from /etc/rcS.d/ are not properly
7563 stopped when passing through the scripts in /etc/rc1.d/, and not
7564 started again when switching away from runlevel 1 to the runlevels
7565 2-5. I believe the problem is best fixed by moving all the scripts
7566 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
7567 functioning single user mode during boot.&lt;/p&gt;
7568
7569 &lt;p&gt;I have spent several years investigating the Debian boot system,
7570 and discovered this problem a few years ago. I suspect it originates
7571 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
7572 </description>
7573 </item>
7574
7575 <item>
7576 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
7577 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
7578 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
7579 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
7580 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
7581 are started from /etc/rcS.d/. In fact, there is a bite more of them
7582 than make sense, and this causes a few problems. What kind of
7583 problems, you might ask. There are at least two problems. The first
7584 is that it is not possible to recover a machine after switching to
7585 runlevel 1. One need to actually reboot to get the machine back to
7586 the expected state. The other is that single user boot will sometimes
7587 run into problems because some of the subsystems are activated before
7588 the root login is presented, causing problems when trying to recover a
7589 machine from a problem in that subsystem. A minor additional point is
7590 that moving more scripts out of rcS.d/ and into the other rc#.d/
7591 directories will increase the amount of scripts that can run in
7592 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
7593
7594 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
7595 scripts that _have_ to execute before the root login prompt is
7596 presented during a single user boot should go there. Everything else
7597 should go into the numeric runlevels. This means things like
7598 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7599 the numeric runlevels. Today in Debian, there are around 115 init.d
7600 scripts that are started from rcS.d/, and most of them should be moved
7601 out. Do your package have one of them? Please help us make single
7602 user and runlevel 1 better by moving it.&lt;/p&gt;
7603
7604 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
7605 etc. should still be started from rcS.d/, but there is for example no
7606 need to have the network enabled before the single user login prompt
7607 is presented.&lt;/p&gt;
7608
7609 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
7610 Debian systems working while scripts migrate and during upgrades, the
7611 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7612 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7613 and the next ones can only be moved when their dependencies have been
7614 moved first. This migration must be done sequentially while we ensure
7615 that the package system upgrade packages in the right order to keep
7616 the system state correct. This will require some coordination when it
7617 comes to network related packages, but most of the packages with
7618 scripts that should migrate do not have anything in rcS.d/ depending
7619 on them. Some packages have already been updated, like the sudo
7620 package, while others are still left to do. I wish I had time to work
7621 on this myself, but real live constrains make it unlikely that I will
7622 find time to push this forward.&lt;/p&gt;
7623 </description>
7624 </item>
7625
7626 <item>
7627 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
7628 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
7629 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
7630 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
7631 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
7632 mentioned the issues I believe should be improved in Debian for its
7633 desktop to be useful for more people. The use case for this is my
7634 parents, which are currently running Kubuntu which solve the
7635 issues.&lt;/p&gt;
7636
7637 &lt;p&gt;I suspect these four missing features are not very hard to
7638 implement. After all, they are present in Ubuntu, so if we wanted to
7639 do this in Debian we would have a source.&lt;/p&gt;
7640
7641 &lt;ol&gt;
7642
7643 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
7644 are new packages available for upgrades, a icon in the KDE status bar
7645 indicate this, and clicking on it will activate the simple upgrade
7646 tool to handle it. I have no problem guiding both of my parents
7647 through the process over the phone. If a kernel reboot is required,
7648 this too is indicated by the status bars and the upgrade tool. Last
7649 time I checked, nothing with the same features was working in KDE in
7650 Debian.&lt;/li&gt;
7651
7652 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
7653 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
7654 currently have a handler for, it will ask the user if the system
7655 should search for a package that would add support for this MIME type,
7656 and if the user say yes, the APT sources will be searched for packages
7657 advertising the MIME type in their control file (visible in the
7658 Packages file in the APT archive). If one or more packages are found,
7659 it is a simple click of the mouse to add support for the missing mime
7660 type. If the package require the user to accept some non-free
7661 license, this is explained to the user. The entire process make it
7662 more clear to the user why something do not work in the browser, and
7663 make the chances higher for the user to blame the web page authors and
7664 not the browser for any missing features.&lt;/li&gt;
7665
7666 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
7667 handlers.&lt;/strong&gt; When the media players encounter a format or codec
7668 it is not supporting, a dialog pop up asking the user if the system
7669 should search for a package that would add support for it. This
7670 happen with things like MP3, Windows Media or H.264. The selection
7671 and installation procedure is very similar to the Firefox browser
7672 plugin handling. This is as far as I know implemented using a
7673 gstreamer hook. The end result is that the user easily get access to
7674 the codecs that are present from the APT archives available, while
7675 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
7676
7677 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
7678 displaying a text/plain file in my Debian browser, it will propose to
7679 start emacs to show it. If I remember correctly, when doing the same
7680 in Kunbutu it show the file as a text file in the browser. At least I
7681 know Opera will show text files within the browser. I much prefer the
7682 latter behaviour.&lt;/li&gt;
7683
7684 &lt;/ol&gt;
7685
7686 &lt;p&gt;There are other nice features as well, like the simplified suite
7687 upgrader, but given that I am the one mostly doing the dist-upgrade,
7688 it do not matter much.&lt;/p&gt;
7689
7690 &lt;p&gt;I really hope we could get these features in place for the next
7691 Debian release. It would require the coordinated effort of several
7692 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
7693 </description>
7694 </item>
7695
7696 <item>
7697 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
7698 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
7699 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
7700 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
7701 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
7702 site is build on Debian/Squeeze, and this platform was chosen because
7703 I am most familiar with Debian (being a Debian Developer for around 10
7704 years) because it is the latest stable Debian release which should get
7705 security support for a few years.&lt;/p&gt;
7706
7707 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
7708 that are missing in Debian at the moment. It would be great if these
7709 modules were added to the Debian archive, allowing anyone to set up
7710 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
7711 in their own country using only Debian packages. The list of modules
7712 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
7713 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
7714 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7715 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7716 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7717 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7718 easier in the future.&lt;/p&gt;
7719
7720 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
7721 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
7722 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
7723 with the responsibility of tracking security problems, which I really
7724 do not have time for.&lt;/p&gt;
7725 </description>
7726 </item>
7727
7728 <item>
7729 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
7730 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
7731 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
7732 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
7733 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
7734 posts have been in Norwegian the last few weeks, so here is a short
7735 update in English.&lt;/p&gt;
7736
7737 &lt;p&gt;The kids still keep me too busy to get much free software work
7738 done, but I did manage to organise a project to get a Norwegian port
7739 of the British service
7740 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
7741 and it has been running for a month now. The entire project has been
7742 organised by me and two others. Around Christmas we gathered sponsors
7743 to fund the development work. In January I drafted a contract with
7744 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
7745 and in February the development took place. Most of it involved
7746 converting the source to use GPS coordinates instead of British
7747 easting/northing, and the resulting code should be a lot easier to get
7748 running in any country by now. The Norwegian
7749 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
7750 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
7751 source and the source for administrative borders in Norway, and
7752 support for this had to be added/fixed.&lt;/p&gt;
7753
7754 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
7755 polishing the system before we announced it March 7th. The system is
7756 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
7757 problem reports in a few weeks. Soon we hope to announce the Android
7758 and iPhone versions making it even easier to report problems with the
7759 public infrastructure.&lt;/p&gt;
7760
7761 &lt;p&gt;Perhaps something to consider for those of you in countries without
7762 such service?&lt;/p&gt;
7763 </description>
7764 </item>
7765
7766 <item>
7767 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
7768 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
7769 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
7770 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
7771 <description>&lt;p&gt;The last few days I have looked at ways to track open security
7772 issues here at my work with the University of Oslo. My idea is that
7773 it should be possible to use the information about security issues
7774 available on the Internet, and check our locally
7775 maintained/distributed software against this information. It should
7776 allow us to verify that no known security issues are forgotten. The
7777 CVE database listing vulnerabilities seem like a great central point,
7778 and by using the package lists from Debian mapped to CVEs provided by
7779 the testing security team, I believed it should be possible to figure
7780 out which security holes were present in our free software
7781 collection.&lt;/p&gt;
7782
7783 &lt;p&gt;After reading up on the topic, it became obvious that the first
7784 building block is to be able to name software packages in a unique and
7785 consistent way across data sources. I considered several ways to do
7786 this, for example coming up with my own naming scheme like using URLs
7787 to project home pages or URLs to the Freshmeat entries, or using some
7788 existing naming scheme. And it seem like I am not the first one to
7789 come across this problem, as MITRE already proposed and implemented a
7790 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
7791 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
7792 software, hardware and other platform components. The CPE ids are
7793 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
7794 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
7795 issues for any CPE name. With this in place, all I need to do is to
7796 locate the CPE id for the software packages we use at the university.
7797 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
7798 NVD entry if a CVE for the package exist).&lt;/p&gt;
7799
7800 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
7801 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
7802 check out, one could look up
7803 &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
7804 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
7805 The most recent one is
7806 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
7807 and at the bottom of the NVD page for this vulnerability the complete
7808 list of affected versions is provided.&lt;/p&gt;
7809
7810 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
7811 for offline processing of issues. Using this dump, I&#39;ve written a
7812 small script taking a list of CPEs as input and list all CVEs
7813 affecting the packages represented by these CPEs. One give it CPEs
7814 with version numbers as specified above and get a list of open
7815 security issues out.&lt;/p&gt;
7816
7817 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
7818 information need to be high. For that to happen, I believe as many as
7819 possible need to use and contribute to the NVD database. I notice
7820 RHEL is providing
7821 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
7822 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
7823 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
7824
7825 &lt;p&gt;To get an idea about the quality for free software, I spent some
7826 time making it possible to compare the CVE database from Debian with
7827 the CVE database in NVD. The result look fairly good, but there are
7828 some inconsistencies in NVD (same software package having several
7829 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7830 Debian believe are affected by a CVE). Hope to find time to improve
7831 the quality of NVD, but that require being able to get in touch with
7832 someone maintaining it. So far my three emails with questions and
7833 corrections have not seen any reply, but I hope contact can be
7834 established soon.&lt;/p&gt;
7835
7836 &lt;p&gt;An interesting application for CPEs is cross platform package
7837 mapping. It would be useful to know which packages in for example
7838 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7839 this would be trivial if all linux distributions provided CPE entries
7840 for their packages.&lt;/p&gt;
7841 </description>
7842 </item>
7843
7844 <item>
7845 <title>Which module is loaded for a given PCI and USB device?</title>
7846 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
7847 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
7848 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
7849 <description>&lt;p&gt;In the
7850 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
7851 package in Debian, there is a script to report useful information
7852 about the running hardware for use when people report missing
7853 information. One part of this script that I find very useful when
7854 debugging hardware problems, is the part mapping loaded kernel module
7855 to the PCI device it claims. It allow me to quickly see if the kernel
7856 module I expect is driving the hardware I am struggling with. To see
7857 the output, make sure discover-data is installed and run
7858 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
7859 one of my machines like this:&lt;/p&gt;
7860
7861 &lt;pre&gt;
7862 loaded modules:
7863 10de:03eb i2c_nforce2
7864 10de:03f1 ohci_hcd
7865 10de:03f2 ehci_hcd
7866 10de:03f0 snd_hda_intel
7867 10de:03ec pata_amd
7868 10de:03f6 sata_nv
7869 1022:1103 k8temp
7870 109e:036e bttv
7871 109e:0878 snd_bt87x
7872 11ab:4364 sky2
7873 &lt;/pre&gt;
7874
7875 &lt;p&gt;The code in question look like this, slightly modified for
7876 readability and to drop the output to file descriptor 3:&lt;/p&gt;
7877
7878 &lt;pre&gt;
7879 if [ -d /sys/bus/pci/devices/ ] ; then
7880 echo loaded pci modules:
7881 (
7882 cd /sys/bus/pci/devices/
7883 for address in * ; do
7884 if [ -d &quot;$address/driver/module&quot; ] ; then
7885 module=`cd $address/driver/module ; pwd -P | xargs basename`
7886 if grep -q &quot;^$module &quot; /proc/modules ; then
7887 address=$(echo $address |sed s/0000://)
7888 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
7889 echo &quot;$id $module&quot;
7890 fi
7891 fi
7892 done
7893 )
7894 echo
7895 fi
7896 &lt;/pre&gt;
7897
7898 &lt;p&gt;Similar code could be used to extract USB device module
7899 mappings:&lt;/p&gt;
7900
7901 &lt;pre&gt;
7902 if [ -d /sys/bus/usb/devices/ ] ; then
7903 echo loaded usb modules:
7904 (
7905 cd /sys/bus/usb/devices/
7906 for address in * ; do
7907 if [ -d &quot;$address/driver/module&quot; ] ; then
7908 module=`cd $address/driver/module ; pwd -P | xargs basename`
7909 if grep -q &quot;^$module &quot; /proc/modules ; then
7910 address=$(echo $address |sed s/0000://)
7911 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
7912 if [ &quot;$id&quot; ] ; then
7913 echo &quot;$id $module&quot;
7914 fi
7915 fi
7916 fi
7917 done
7918 )
7919 echo
7920 fi
7921 &lt;/pre&gt;
7922
7923 &lt;p&gt;This might perhaps be something to include in other tools as
7924 well.&lt;/p&gt;
7925 </description>
7926 </item>
7927
7928 <item>
7929 <title>How to test if a laptop is working with Linux</title>
7930 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
7931 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
7932 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
7933 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
7934 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
7935 batch of computers will work with Linux. Every year for the last few
7936 years the university have organised shared bid of a few thousand
7937 computers, and this year HP won the bid. Two different desktops and
7938 five different laptops are on the list this year. We in the UNIX
7939 group want to know which one of these computers work well with RHEL
7940 and Ubuntu, the two Linux distributions we currently handle at the
7941 university.&lt;/p&gt;
7942
7943 &lt;p&gt;My test method is simple, and I share it here to get feedback and
7944 perhaps inspire others to test hardware as well. To test, I PXE
7945 install the OS version of choice, and log in as my normal user and run
7946 a few applications and plug in selected pieces of hardware. When
7947 something fail, I make a note about this in the test matrix and move
7948 on. If I have some spare time I try to report the bug to the OS
7949 vendor, but as I only have the machines for a short time, I rarely
7950 have the time to do this for all the problems I find.&lt;/p&gt;
7951
7952 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
7953 I perform on a new model.&lt;/p&gt;
7954
7955 &lt;ul&gt;
7956
7957 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
7958 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7959 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
7960
7961 &lt;li&gt;Is X.org working? If the graphical login screen show up after
7962 installation, X.org is working.&lt;/li&gt;
7963
7964 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
7965 package mesa-utils on Ubuntu) and writing down the frames per second
7966 reported by the program.&lt;/li&gt;
7967
7968 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
7969 logging in, and if I can hear this the test is successful. If there
7970 are several audio exits on the machine, I try them all and check if
7971 the Gnome/KDE audio mixer can control where to send the sound. I
7972 normally test this by playing
7973 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
7974 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
7975
7976 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
7977 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
7978
7979 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
7980 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
7981
7982 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
7983 picture from the v4l device show up.&lt;/li&gt;
7984
7985 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7986 any bluetooth devices are discovered. In my office, I normally see a
7987 few.&lt;/li&gt;
7988
7989 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
7990 memory modules lying around, and stick them in and see if Gnome/KDE
7991 notice this.&lt;/li&gt;
7992
7993 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
7994 special button work, and if the laptop continue to work after
7995 resume.&lt;/li&gt;
7996
7997 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
7998 adjusting background light, switching on/off external video output,
7999 switching on/off wifi, bluetooth, etc? The set of buttons differ from
8000 laptop to laptop, so I just write down which are working and which are
8001 not.&lt;/li&gt;
8002
8003 &lt;li&gt;Some laptops have smart card readers, finger print readers,
8004 acceleration sensors etc. I rarely test these, as I do not know how
8005 to quickly test if they are working or not, so I only document their
8006 existence.&lt;/li&gt;
8007
8008 &lt;/ul&gt;
8009
8010 &lt;p&gt;By now I suspect you are really curious what the test results are
8011 for the HP machines I am testing. I&#39;m not done yet, so I will report
8012 the test results later. For now I can report that HP 8100 Elite work
8013 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
8014 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
8015 can see, I have most machines left to test. One interesting
8016 observation is that Ubuntu Lucid has almost twice the frame rate than
8017 RHEL6 with glxgears. No idea why.&lt;/p&gt;
8018 </description>
8019 </item>
8020
8021 <item>
8022 <title>Some thoughts on BitCoins</title>
8023 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
8024 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
8025 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
8026 <description>&lt;p&gt;As I continue to explore
8027 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
8028 what properties the system have, and how it will be affected by laws
8029 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
8030
8031 &lt;p&gt;One interesting thing to note is that since the transactions are
8032 verified using a peer to peer network, all details about a transaction
8033 is known to everyone. This means that if a BitCoin address has been
8034 published like I did with mine in my initial post about BitCoin, it is
8035 possible for everyone to see how many BitCoins have been transfered to
8036 that address. There is even a web service to look at the details for
8037 all transactions. There I can see that my address
8038 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
8039 have received 16.06 Bitcoin, the
8040 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
8041 address of Simon Phipps have received 181.97 BitCoin and the address
8042 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
8043 of EFF have received 2447.38 BitCoins so far. Thank you to each and
8044 every one of you that donated bitcoins to support my activity. The
8045 fact that anyone can see how much money was transfered to a given
8046 address make it more obvious why the BitCoin community recommend to
8047 generate and hand out a new address for each transaction. I&#39;m told
8048 there is no way to track which addresses belong to a given person or
8049 organisation without the person or organisation revealing it
8050 themselves, as Simon, EFF and I have done.&lt;/p&gt;
8051
8052 &lt;p&gt;In Norway, and in most other countries, there are laws and
8053 regulations limiting how much money one can transfer across the border
8054 without declaring it. There are money laundering, tax and accounting
8055 laws and regulations I would expect to apply to the use of BitCoin.
8056 If the Skolelinux foundation
8057 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
8058 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
8059 normal bank transfers like EFF is doing, how should this be accounted?
8060 Given that it is impossible to know if money can cross the border or
8061 not, should everything or nothing be declared? What exchange rate
8062 should be used when calculating taxes? Would receivers have to pay
8063 income tax if the foundation were to pay Skolelinux contributors in
8064 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
8065
8066 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
8067 accepted by a lot of users. It must be possible to get easy access to
8068 the currency (as a wage or using currency exchanges), and it must be
8069 easy to spend it. At the moment BitCoin seem fairly easy to get
8070 access to, but there are very few places to spend it. I am not really
8071 a regular user of any of the vendor types currently accepting BitCoin,
8072 so I wonder when my kind of shop would start accepting BitCoins. I
8073 would like to buy electronics, travels and subway tickets, not herbs
8074 and books. :) The currency is young, and this will improve over time
8075 if it become popular, but I suspect regular banks will start to lobby
8076 to get BitCoin declared illegal if it become popular. I&#39;m sure they
8077 will claim it is helping fund terrorism and money laundering (which
8078 probably would be true, as is any currency in existence), but I
8079 believe the problems should be solved elsewhere and not by blaming
8080 currencies.&lt;/p&gt;
8081
8082 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
8083 CPU intensive process that depend on a bit of luck as well (as one is
8084 competing against all the other miners currently spending CPU cycles
8085 to see which one get the next lump of cash). The &quot;winner&quot; get 50
8086 BitCoin when this happen. Yesterday I came across the obvious way to
8087 join forces to increase ones changes of getting at least some coins,
8088 by coordinating the work on mining BitCoins across several machines
8089 and people, and sharing the result if one is lucky and get the 50
8090 BitCoins. Check out
8091 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
8092 if this sounds interesting. I have not had time to try to set up a
8093 machine to participate there yet, but have seen that running on ones
8094 own for a few days have not yield any BitCoins througth mining
8095 yet.&lt;/p&gt;
8096
8097 &lt;p&gt;Update 2010-12-15: Found an &lt;a
8098 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
8099 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
8100 it was interesting to read. The arguments presented seem to be
8101 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
8102 </description>
8103 </item>
8104
8105 <item>
8106 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
8107 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
8108 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
8109 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
8110 <description>&lt;p&gt;With this weeks lawless
8111 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
8112 attacks&lt;/a&gt; on Wikileak and
8113 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
8114 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
8115 not be trusted to handle money transactions.
8116 A blog post from
8117 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
8118 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
8119 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
8120 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
8121 some help from my friend to get it all running, and he even handed me
8122 some bitcoins to get started. I even donated a few bitcoins to Simon
8123 for helping me remember BitCoin.&lt;/p&gt;
8124
8125 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
8126 crypto-currency, decentralised and handled using peer-to-peer
8127 networks. It allows anonymous transactions and prohibits central
8128 control over the transactions, making it impossible for governments
8129 and companies alike to block donations and other transactions. The
8130 source is free software, and while the key dependency wxWidgets 2.9
8131 for the graphical user interface is missing in Debian, the command
8132 line client builds just fine. Hopefully Jonas
8133 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
8134 Debian&lt;/a&gt; soon.&lt;/p&gt;
8135
8136 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
8137 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
8138 bitcoins&lt;/a&gt; when selling services and goods, and there are even
8139 currency &quot;stock&quot; markets where the exchange rate is decided. There
8140 are not many users so far, but the concept seems promising. If you
8141 want to get started and lack a friend with any bitcoins to spare,
8142 you can even get
8143 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
8144 bitcoin at the time of writing). Use
8145 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
8146 on the current exchange rates.&lt;/p&gt;
8147
8148 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
8149 machines. If you want to support my activity, please send Bitcoin
8150 donations to the address
8151 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
8152 </description>
8153 </item>
8154
8155 <item>
8156 <title>Why isn&#39;t Debian Edu using VLC?</title>
8157 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
8158 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
8159 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
8160 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
8161 presented, and the winner among the multimedia player were VLC.
8162 Personally, I like VLC, and it is my player of choice when I first try
8163 to play a video file or stream. Only if VLC fail will I drag out
8164 gmplayer to see if it can do better. The reason is mostly the failure
8165 model and trust. When VLC fail, it normally pop up a error message
8166 reporting the problem. When mplayer fail, it normally segfault or
8167 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
8168
8169 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
8170 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
8171 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
8172 plugin to play web videos seamlessly, and the VLC browser plugin is
8173 not very good. For example, it lack in-line control buttons, so there
8174 is no way for the user to pause the video. Also, when I
8175 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
8176 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
8177 failed on several video pages where mplayer based plugins worked. If
8178 the browser plugin for VLC was as good as the gecko-mediaplayer
8179 package (which uses mplayer), we would switch.&lt;/P&gt;
8180
8181 &lt;p&gt;While VLC is a good player, its user interface is slightly
8182 annoying. The most annoying feature is its inconsistent use of
8183 keyboard shortcuts. When the player is in full screen mode, its
8184 shortcuts are different from when it is playing the video in a window.
8185 For example, space only work as pause when in full screen mode. I
8186 wish it had consisten shortcuts and that space also would work when in
8187 window mode. Another nice shortcut in gmplayer is [enter] to restart
8188 the current video. It is very nice when playing short videos from the
8189 web and want to restart it when new people arrive to have a look at
8190 what is going on.&lt;/p&gt;
8191 </description>
8192 </item>
8193
8194 <item>
8195 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
8196 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
8197 <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>
8198 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
8199 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
8200 upgrade testing of the
8201 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
8202 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
8203 This seem like a very good idea, so I adjusted by test scripts and
8204 can now present the updated result from today:&lt;/p&gt;
8205
8206 &lt;p&gt;This is for Gnome:&lt;/p&gt;
8207
8208 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8209
8210 &lt;blockquote&gt;&lt;p&gt;
8211 apache2.2-bin
8212 aptdaemon
8213 baobab
8214 binfmt-support
8215 browser-plugin-gnash
8216 cheese-common
8217 cli-common
8218 cups-pk-helper
8219 dmz-cursor-theme
8220 empathy
8221 empathy-common
8222 freedesktop-sound-theme
8223 freeglut3
8224 gconf-defaults-service
8225 gdm-themes
8226 gedit-plugins
8227 geoclue
8228 geoclue-hostip
8229 geoclue-localnet
8230 geoclue-manual
8231 geoclue-yahoo
8232 gnash
8233 gnash-common
8234 gnome
8235 gnome-backgrounds
8236 gnome-cards-data
8237 gnome-codec-install
8238 gnome-core
8239 gnome-desktop-environment
8240 gnome-disk-utility
8241 gnome-screenshot
8242 gnome-search-tool
8243 gnome-session-canberra
8244 gnome-system-log
8245 gnome-themes-extras
8246 gnome-themes-more
8247 gnome-user-share
8248 gstreamer0.10-fluendo-mp3
8249 gstreamer0.10-tools
8250 gtk2-engines
8251 gtk2-engines-pixbuf
8252 gtk2-engines-smooth
8253 hamster-applet
8254 libapache2-mod-dnssd
8255 libapr1
8256 libaprutil1
8257 libaprutil1-dbd-sqlite3
8258 libaprutil1-ldap
8259 libart2.0-cil
8260 libboost-date-time1.42.0
8261 libboost-python1.42.0
8262 libboost-thread1.42.0
8263 libchamplain-0.4-0
8264 libchamplain-gtk-0.4-0
8265 libcheese-gtk18
8266 libclutter-gtk-0.10-0
8267 libcryptui0
8268 libdiscid0
8269 libelf1
8270 libepc-1.0-2
8271 libepc-common
8272 libepc-ui-1.0-2
8273 libfreerdp-plugins-standard
8274 libfreerdp0
8275 libgconf2.0-cil
8276 libgdata-common
8277 libgdata7
8278 libgdu-gtk0
8279 libgee2
8280 libgeoclue0
8281 libgexiv2-0
8282 libgif4
8283 libglade2.0-cil
8284 libglib2.0-cil
8285 libgmime2.4-cil
8286 libgnome-vfs2.0-cil
8287 libgnome2.24-cil
8288 libgnomepanel2.24-cil
8289 libgpod-common
8290 libgpod4
8291 libgtk2.0-cil
8292 libgtkglext1
8293 libgtksourceview2.0-common
8294 libmono-addins-gui0.2-cil
8295 libmono-addins0.2-cil
8296 libmono-cairo2.0-cil
8297 libmono-corlib2.0-cil
8298 libmono-i18n-west2.0-cil
8299 libmono-posix2.0-cil
8300 libmono-security2.0-cil
8301 libmono-sharpzip2.84-cil
8302 libmono-system2.0-cil
8303 libmtp8
8304 libmusicbrainz3-6
8305 libndesk-dbus-glib1.0-cil
8306 libndesk-dbus1.0-cil
8307 libopal3.6.8
8308 libpolkit-gtk-1-0
8309 libpt2.6.7
8310 libpython2.6
8311 librpm1
8312 librpmio1
8313 libsdl1.2debian
8314 libsrtp0
8315 libssh-4
8316 libtelepathy-farsight0
8317 libtelepathy-glib0
8318 libtidy-0.99-0
8319 media-player-info
8320 mesa-utils
8321 mono-2.0-gac
8322 mono-gac
8323 mono-runtime
8324 nautilus-sendto
8325 nautilus-sendto-empathy
8326 p7zip-full
8327 pkg-config
8328 python-aptdaemon
8329 python-aptdaemon-gtk
8330 python-axiom
8331 python-beautifulsoup
8332 python-bugbuddy
8333 python-clientform
8334 python-coherence
8335 python-configobj
8336 python-crypto
8337 python-cupshelpers
8338 python-elementtree
8339 python-epsilon
8340 python-evolution
8341 python-feedparser
8342 python-gdata
8343 python-gdbm
8344 python-gst0.10
8345 python-gtkglext1
8346 python-gtksourceview2
8347 python-httplib2
8348 python-louie
8349 python-mako
8350 python-markupsafe
8351 python-mechanize
8352 python-nevow
8353 python-notify
8354 python-opengl
8355 python-openssl
8356 python-pam
8357 python-pkg-resources
8358 python-pyasn1
8359 python-pysqlite2
8360 python-rdflib
8361 python-serial
8362 python-tagpy
8363 python-twisted-bin
8364 python-twisted-conch
8365 python-twisted-core
8366 python-twisted-web
8367 python-utidylib
8368 python-webkit
8369 python-xdg
8370 python-zope.interface
8371 remmina
8372 remmina-plugin-data
8373 remmina-plugin-rdp
8374 remmina-plugin-vnc
8375 rhythmbox-plugin-cdrecorder
8376 rhythmbox-plugins
8377 rpm-common
8378 rpm2cpio
8379 seahorse-plugins
8380 shotwell
8381 software-center
8382 system-config-printer-udev
8383 telepathy-gabble
8384 telepathy-mission-control-5
8385 telepathy-salut
8386 tomboy
8387 totem
8388 totem-coherence
8389 totem-mozilla
8390 totem-plugins
8391 transmission-common
8392 xdg-user-dirs
8393 xdg-user-dirs-gtk
8394 xserver-xephyr
8395 &lt;/p&gt;&lt;/blockquote&gt;
8396
8397 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8398
8399 &lt;blockquote&gt;&lt;p&gt;
8400 cheese
8401 ekiga
8402 eog
8403 epiphany-extensions
8404 evolution-exchange
8405 fast-user-switch-applet
8406 file-roller
8407 gcalctool
8408 gconf-editor
8409 gdm
8410 gedit
8411 gedit-common
8412 gnome-games
8413 gnome-games-data
8414 gnome-nettool
8415 gnome-system-tools
8416 gnome-themes
8417 gnuchess
8418 gucharmap
8419 guile-1.8-libs
8420 libavahi-ui0
8421 libdmx1
8422 libgalago3
8423 libgtk-vnc-1.0-0
8424 libgtksourceview2.0-0
8425 liblircclient0
8426 libsdl1.2debian-alsa
8427 libspeexdsp1
8428 libsvga1
8429 rhythmbox
8430 seahorse
8431 sound-juicer
8432 system-config-printer
8433 totem-common
8434 transmission-gtk
8435 vinagre
8436 vino
8437 &lt;/p&gt;&lt;/blockquote&gt;
8438
8439 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8440
8441 &lt;blockquote&gt;&lt;p&gt;
8442 gstreamer0.10-gnomevfs
8443 &lt;/p&gt;&lt;/blockquote&gt;
8444
8445 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8446
8447 &lt;blockquote&gt;&lt;p&gt;
8448 [nothing]
8449 &lt;/p&gt;&lt;/blockquote&gt;
8450
8451 &lt;p&gt;This is for KDE:&lt;/p&gt;
8452
8453 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8454
8455 &lt;blockquote&gt;&lt;p&gt;
8456 ksmserver
8457 &lt;/p&gt;&lt;/blockquote&gt;
8458
8459 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8460
8461 &lt;blockquote&gt;&lt;p&gt;
8462 kwin
8463 network-manager-kde
8464 &lt;/p&gt;&lt;/blockquote&gt;
8465
8466 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8467
8468 &lt;blockquote&gt;&lt;p&gt;
8469 arts
8470 dolphin
8471 freespacenotifier
8472 google-gadgets-gst
8473 google-gadgets-xul
8474 kappfinder
8475 kcalc
8476 kcharselect
8477 kde-core
8478 kde-plasma-desktop
8479 kde-standard
8480 kde-window-manager
8481 kdeartwork
8482 kdeartwork-emoticons
8483 kdeartwork-style
8484 kdeartwork-theme-icon
8485 kdebase
8486 kdebase-apps
8487 kdebase-workspace
8488 kdebase-workspace-bin
8489 kdebase-workspace-data
8490 kdeeject
8491 kdelibs
8492 kdeplasma-addons
8493 kdeutils
8494 kdewallpapers
8495 kdf
8496 kfloppy
8497 kgpg
8498 khelpcenter4
8499 kinfocenter
8500 konq-plugins-l10n
8501 konqueror-nsplugins
8502 kscreensaver
8503 kscreensaver-xsavers
8504 ktimer
8505 kwrite
8506 libgle3
8507 libkde4-ruby1.8
8508 libkonq5
8509 libkonq5-templates
8510 libnetpbm10
8511 libplasma-ruby
8512 libplasma-ruby1.8
8513 libqt4-ruby1.8
8514 marble-data
8515 marble-plugins
8516 netpbm
8517 nuvola-icon-theme
8518 plasma-dataengines-workspace
8519 plasma-desktop
8520 plasma-desktopthemes-artwork
8521 plasma-runners-addons
8522 plasma-scriptengine-googlegadgets
8523 plasma-scriptengine-python
8524 plasma-scriptengine-qedje
8525 plasma-scriptengine-ruby
8526 plasma-scriptengine-webkit
8527 plasma-scriptengines
8528 plasma-wallpapers-addons
8529 plasma-widget-folderview
8530 plasma-widget-networkmanagement
8531 ruby
8532 sweeper
8533 update-notifier-kde
8534 xscreensaver-data-extra
8535 xscreensaver-gl
8536 xscreensaver-gl-extra
8537 xscreensaver-screensaver-bsod
8538 &lt;/p&gt;&lt;/blockquote&gt;
8539
8540 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8541
8542 &lt;blockquote&gt;&lt;p&gt;
8543 ark
8544 google-gadgets-common
8545 google-gadgets-qt
8546 htdig
8547 kate
8548 kdebase-bin
8549 kdebase-data
8550 kdepasswd
8551 kfind
8552 klipper
8553 konq-plugins
8554 konqueror
8555 ksysguard
8556 ksysguardd
8557 libarchive1
8558 libcln6
8559 libeet1
8560 libeina-svn-06
8561 libggadget-1.0-0b
8562 libggadget-qt-1.0-0b
8563 libgps19
8564 libkdecorations4
8565 libkephal4
8566 libkonq4
8567 libkonqsidebarplugin4a
8568 libkscreensaver5
8569 libksgrd4
8570 libksignalplotter4
8571 libkunitconversion4
8572 libkwineffects1a
8573 libmarblewidget4
8574 libntrack-qt4-1
8575 libntrack0
8576 libplasma-geolocation-interface4
8577 libplasmaclock4a
8578 libplasmagenericshell4
8579 libprocesscore4a
8580 libprocessui4a
8581 libqalculate5
8582 libqedje0a
8583 libqtruby4shared2
8584 libqzion0a
8585 libruby1.8
8586 libscim8c2a
8587 libsmokekdecore4-3
8588 libsmokekdeui4-3
8589 libsmokekfile3
8590 libsmokekhtml3
8591 libsmokekio3
8592 libsmokeknewstuff2-3
8593 libsmokeknewstuff3-3
8594 libsmokekparts3
8595 libsmokektexteditor3
8596 libsmokekutils3
8597 libsmokenepomuk3
8598 libsmokephonon3
8599 libsmokeplasma3
8600 libsmokeqtcore4-3
8601 libsmokeqtdbus4-3
8602 libsmokeqtgui4-3
8603 libsmokeqtnetwork4-3
8604 libsmokeqtopengl4-3
8605 libsmokeqtscript4-3
8606 libsmokeqtsql4-3
8607 libsmokeqtsvg4-3
8608 libsmokeqttest4-3
8609 libsmokeqtuitools4-3
8610 libsmokeqtwebkit4-3
8611 libsmokeqtxml4-3
8612 libsmokesolid3
8613 libsmokesoprano3
8614 libtaskmanager4a
8615 libtidy-0.99-0
8616 libweather-ion4a
8617 libxklavier16
8618 libxxf86misc1
8619 okteta
8620 oxygencursors
8621 plasma-dataengines-addons
8622 plasma-scriptengine-superkaramba
8623 plasma-widget-lancelot
8624 plasma-widgets-addons
8625 plasma-widgets-workspace
8626 polkit-kde-1
8627 ruby1.8
8628 systemsettings
8629 update-notifier-common
8630 &lt;/p&gt;&lt;/blockquote&gt;
8631
8632 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
8633 aptitude a bit more similar, but there are still quite a lott of
8634 differences. I have no idea what packages should be installed after
8635 the upgrade, but hope those that do can have a look.&lt;/p&gt;
8636 </description>
8637 </item>
8638
8639 <item>
8640 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
8641 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
8642 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
8643 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
8644 <description>&lt;p&gt;Most of the computers in use by the
8645 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
8646 are virtual machines. And they have been Xen machines running on a
8647 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
8648 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
8649 bit harder that it could have been, because we set up the Xen virtual
8650 machines to get the virtual partitions from LVM, which as far as I
8651 know is not supported by KVM. So to migrate, we had to convert
8652 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
8653
8654 &lt;p&gt;I found
8655 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
8656 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
8657 migration. It uses qemu-img from the qemu package to make the disk
8658 image, parted to partition it, losetup and kpartx to present the disk
8659 image partions as devices, and dd to copy the data. I NFS mounted the
8660 new servers storage area on the old server to do the migration.&lt;/p&gt;
8661
8662 &lt;pre&gt;
8663 #!/bin/sh
8664
8665 # Based on
8666 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8667
8668 set -e
8669 set -x
8670
8671 if [ -z &quot;$1&quot; ] ; then
8672 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
8673 exit 1
8674 else
8675 host=&quot;$1&quot;
8676 fi
8677
8678 if [ ! -e /dev/vg_data/$host-disk ] ; then
8679 echo &quot;error: unable to find LVM volume for $host&quot;
8680 exit 1
8681 fi
8682
8683 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8684 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
8685 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
8686 totalsize=$(( ( $disksize + $swapsize ) ))
8687
8688 img=$host.img
8689 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
8690 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8691
8692 parted $img mklabel msdos
8693 parted $img mkpart primary linux-swap 0 $disksize
8694 parted $img mkpart primary ext2 $disksize $totalsize
8695 parted $img set 1 boot on
8696
8697 modprobe dm-mod
8698 losetup /dev/loop0 $img
8699 kpartx -a /dev/loop0
8700
8701 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
8702 fsck.ext3 -f /dev/mapper/loop0p1 || true
8703 mkswap /dev/mapper/loop0p2
8704
8705 kpartx -d /dev/loop0
8706 losetup -d /dev/loop0
8707 &lt;/pre&gt;
8708
8709 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
8710 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
8711
8712 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
8713 the new disk image attached, installed grub-pc and linux-image-686 and
8714 set up grub to boot from the disk image. After this, the KVM machines
8715 seem to work just fine.&lt;/p&gt;
8716 </description>
8717 </item>
8718
8719 <item>
8720 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
8721 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
8722 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
8723 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
8724 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
8725 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
8726 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
8727 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
8728
8729 &lt;p&gt;I still do not know what a correct migration should look like, so I
8730 report any differences between apt and aptitude and hope someone else
8731 can see if anything should be changed.&lt;/p&gt;
8732
8733 &lt;p&gt;This is for Gnome:&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 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8739 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
8740 dmz-cursor-theme empathy empathy-common finger
8741 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8742 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8743 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8744 gnome-cards-data gnome-codec-install gnome-core
8745 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8746 gnome-search-tool gnome-session-canberra gnome-spell
8747 gnome-system-log gnome-themes-extras gnome-themes-more
8748 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8749 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8750 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8751 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8752 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
8753 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
8754 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
8755 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
8756 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
8757 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8758 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
8759 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8760 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8761 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8762 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8763 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8764 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8765 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8766 libmono-security2.0-cil libmono-sharpzip2.84-cil
8767 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
8768 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
8769 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
8770 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
8771 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
8772 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
8773 libxalan2-java libxerces2-java media-player-info mesa-utils
8774 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
8775 nautilus-sendto-empathy openoffice.org-writer2latex
8776 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
8777 python-aptdaemon python-aptdaemon-gtk python-axiom
8778 python-beautifulsoup python-bugbuddy python-clientform
8779 python-coherence python-configobj python-crypto python-cupshelpers
8780 python-cupsutils python-eggtrayicon python-elementtree
8781 python-epsilon python-evolution python-feedparser python-gdata
8782 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8783 python-gtksourceview2 python-httplib2 python-louie python-mako
8784 python-markupsafe python-mechanize python-nevow python-notify
8785 python-opengl python-openssl python-pam python-pkg-resources
8786 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8787 python-tagpy python-twisted-bin python-twisted-conch
8788 python-twisted-core python-twisted-web python-utidylib python-webkit
8789 python-xdg python-zope.interface remmina remmina-plugin-data
8790 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8791 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8792 software-center svgalibg1 system-config-printer-udev
8793 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
8794 totem totem-coherence totem-mozilla totem-plugins
8795 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8796 zip
8797 &lt;/p&gt;&lt;/blockquote&gt;
8798
8799 Installed using apt-get, removed with aptitude
8800
8801 &lt;blockquote&gt;&lt;p&gt;
8802 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8803 epiphany-extensions epiphany-gecko evolution-exchange
8804 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8805 gedit-common gnome-app-install gnome-games gnome-games-data
8806 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8807 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8808 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8809 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
8810 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
8811 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
8812 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
8813 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
8814 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
8815 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
8816 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
8817 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
8818 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8819 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8820 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8821 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8822 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
8823 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
8824 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
8825 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
8826 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
8827 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8828 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8829 sound-juicer swfdec-gnome system-config-printer totem-common
8830 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8831 &lt;/p&gt;&lt;/blockquote&gt;
8832
8833 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8834
8835 &lt;blockquote&gt;&lt;p&gt;
8836 gstreamer0.10-gnomevfs
8837 &lt;/p&gt;&lt;/blockquote&gt;
8838
8839 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8840
8841 &lt;blockquote&gt;&lt;p&gt;
8842 [nothing]
8843 &lt;/p&gt;&lt;/blockquote&gt;
8844
8845 &lt;p&gt;This is for KDE:&lt;/p&gt;
8846
8847 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
8848
8849 &lt;blockquote&gt;&lt;p&gt;
8850 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
8851 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8852 ghostscript-x git gnome-audio gnugo granatier gs-common
8853 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8854 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8855 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8856 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8857 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8858 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8859 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8860 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8861 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8862 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8863 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8864 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
8865 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8866 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8867 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8868 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8869 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8870 libkrossui4 libmailtools-perl libmime-tools-perl
8871 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8872 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8873 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8874 lirc luatex marble networkstatus noatun-plugins
8875 openoffice.org-writer2latex palapeli palapeli-data parley
8876 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8877 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8878 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8879 ttf-sazanami-gothic
8880 &lt;/p&gt;&lt;/blockquote&gt;
8881
8882 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
8883
8884 &lt;blockquote&gt;&lt;p&gt;
8885 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8886 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8887 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8888 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8889 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8890 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8891 kitchensync kiten kjumpingcube klatin klettres klickety klines
8892 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8893 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8894 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8895 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8896 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8897 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8898 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8899 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8900 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8901 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
8902 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
8903 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8904 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
8905 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
8906 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8907 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8908 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8909 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8910 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8911 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8912 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
8913 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
8914 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8915 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8916 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8917 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8918 &lt;/p&gt;&lt;/blockquote&gt;
8919
8920 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
8921
8922 &lt;blockquote&gt;&lt;p&gt;
8923 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8924 kdeartwork kdebase kdebase-apps kdebase-workspace
8925 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8926 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8927 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8928 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8929 xscreensaver-screensaver-bsod
8930 &lt;/p&gt;&lt;/blockquote&gt;
8931
8932 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
8933
8934 &lt;blockquote&gt;&lt;p&gt;
8935 kdebase-bin konq-plugins konqueror
8936 &lt;/p&gt;&lt;/blockquote&gt;
8937 </description>
8938 </item>
8939
8940 <item>
8941 <title>Gnash buildbot slave and Debian kfreebsd</title>
8942 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
8943 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
8944 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
8945 <description>&lt;p&gt;Answering
8946 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
8947 call from the Gnash project&lt;/a&gt; for
8948 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
8949 current source, I have set up a virtual KVM machine on the Debian
8950 Edu/Skolelinux virtualization host to test the git source on
8951 Debian/Squeeze. I hope this can help the developers in getting new
8952 releases out more often.&lt;/p&gt;
8953
8954 &lt;p&gt;As the developers want less main-stream build platforms tested to,
8955 I have considered setting up a &lt;a
8956 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
8957 machine as well. I have also considered using the kfreebsd
8958 architecture in Debian as a file server in NUUG to get access to the 5
8959 TB zfs volume we currently use to store DV video. Because of this, I
8960 finally got around to do a test installation of Debian/Squeeze with
8961 kfreebsd. Installation went fairly smooth, thought I noticed some
8962 visual glitches in the cdebconf dialogs (black cursor left on the
8963 screen at random locations). Have not gotten very far with the
8964 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8965 fatal problem. Have to spend some more time on it to see if it is
8966 useful as a file server for NUUG. Will try to find time to set up a
8967 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
8968 </description>
8969 </item>
8970
8971 <item>
8972 <title>Debian in 3D</title>
8973 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
8974 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
8975 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
8976 <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;
8977
8978 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
8979 3D linked in from
8980 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
8981 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
8982 </description>
8983 </item>
8984
8985 <item>
8986 <title>Software updates 2010-10-24</title>
8987 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
8988 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
8989 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
8990 <description>&lt;p&gt;Some updates.&lt;/p&gt;
8991
8992 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
8993 raise money for the project is going well. The lower limit of 10
8994 signers was reached in 24 hours, and so far 13 people have signed it.
8995 More signers and more funding is most welcome, and I am really curious
8996 how far we can get before the time limit of December 24 is reached.
8997 :)&lt;/p&gt;
8998
8999 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
9000 about what appear to be a great code coverage tool capable of
9001 generating code coverage stats without any changes to the source code.
9002 It is called
9003 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
9004 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
9005 It is missing in Debian, but the git source built just fine in Squeeze
9006 after I installed libelf-dev, libdwarf-dev, pkg-config and
9007 libglib2.0-dev. Failed to build in Lenny, but suspect that is
9008 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
9009
9010 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
9011 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
9012 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
9013 alpha test release of the Squeeze based Debian Edu /
9014 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
9015 release. Give it a try if you need a complete linux solution for your
9016 school, including central infrastructure server, workstations, thin
9017 client servers and diskless workstations. A nice touch added
9018 yesterday is RDP support on the thin client servers, for windows
9019 clients to get a Linux desktop on request.&lt;/p&gt;
9020 </description>
9021 </item>
9022
9023 <item>
9024 <title>Some notes on Flash in Debian and Debian Edu</title>
9025 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
9026 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
9027 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
9028 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
9029 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
9030 second most popular used package that is missing in Debian. The sixth
9031 most popular is flashplayer-mozilla. This is a clear indication that
9032 working flash is important for Debian users. Around 10 percent of the
9033 users submitting data to popcon.debian.org have this package
9034 installed.&lt;/p&gt;
9035
9036 &lt;p&gt;In the report written by Lars Risan in August 2008
9037&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
9038 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9039 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
9040 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
9041 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
9042 web sites require Flash to work, and lacking working Flash support in
9043 the web browser and the problems with installing it was perceived as a
9044 good reason to stay with Windows.&lt;/p&gt;
9045
9046 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
9047 said to be the retarded cousin that did not really understand
9048 everything you told him but could work fairly well. This was a
9049 comment regarding the problems Linux have with proprietary formats and
9050 non-standard web pages, and is sad because it exposes a fairly common
9051 understanding of whose fault it is if web pages that only work in for
9052 example Internet Explorer 6 fail to work on Firefox, and funny because
9053 it explain very well how annoying it is for users when Linux
9054 distributions do not work with the documents they receive or the web
9055 pages they want to visit.&lt;/p&gt;
9056
9057 &lt;p&gt;This is part of the reason why I believe it is important for Debian
9058 and Debian Edu to have a well working Flash implementation in the
9059 distribution, to get at least popular sites as Youtube and Google
9060 Video to working out of the box. For Squeeze, Debian have the chance
9061 to include the latest version of Gnash that will make this happen, as
9062 the new release 0.8.8 was published a few weeks ago and is resting in
9063 unstable. The new version work with more sites that version 0.8.7.
9064 The Gnash maintainers have asked for a freeze exception, but the
9065 release team have not had time to reply to it yet. I hope they agree
9066 with me that Flash is important for the Debian desktop users, and thus
9067 accept the new package into Squeeze.&lt;/p&gt;
9068 </description>
9069 </item>
9070
9071 <item>
9072 <title>Circular package dependencies harms apt recovery</title>
9073 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
9074 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
9075 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
9076 <description>&lt;p&gt;I discovered this while doing
9077 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
9078 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
9079 in Debian still got circular dependencies, and it is often claimed
9080 that apt and aptitude should be able to handle this just fine, but
9081 some times these dependency loops causes apt to fail.&lt;/p&gt;
9082
9083 &lt;p&gt;An example is from todays
9084 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
9085 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
9086 causes perl-modules to fail to upgrade. The cause is simple. If a
9087 package fail to unpack, then only part of packages with the circular
9088 dependency might end up being unpacked when unpacking aborts, and the
9089 ones already unpacked will fail to configure in the recovery phase
9090 because its dependencies are unavailable.&lt;/p&gt;
9091
9092 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
9093
9094 &lt;blockquote&gt;&lt;pre&gt;
9095 dpkg: dependency problems prevent configuration of perl-modules:
9096 perl-modules depends on perl (&gt;= 5.10.1-1); however:
9097 Version of perl on system is 5.10.0-19lenny2.
9098 dpkg: error processing perl-modules (--configure):
9099 dependency problems - leaving unconfigured
9100 &lt;/pre&gt;&lt;/blockquote&gt;
9101
9102 &lt;p&gt;The perl/perl-modules circular dependency is already
9103 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
9104 hopefully be solved as soon as possible, but it is not the only one,
9105 and each one of these loops in the dependency tree can cause similar
9106 failures. Of course, they only occur when there are bugs in other
9107 packages causing the unpacking to fail, but it is rather nasty when
9108 the failure of one package causes the problem to become worse because
9109 of dependency loops.&lt;/p&gt;
9110
9111 &lt;p&gt;Thanks to
9112 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
9113 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
9114 dependencies
9115 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
9116 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
9117
9118 &lt;p&gt;Todays testing also exposed a bug in
9119 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
9120 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
9121 apt-get and aptitude, the latter possibly caused by some circular
9122 dependency. Reported both to BTS to try to get someone to look at
9123 it.&lt;/p&gt;
9124 </description>
9125 </item>
9126
9127 <item>
9128 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
9129 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
9130 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
9131 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
9132 <description>&lt;p&gt;This is a
9133 &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;
9134 on my
9135 &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
9136 work&lt;/a&gt; on
9137 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
9138 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
9139
9140 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
9141 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9142 and dhcp3-server-ldap in Debian use the LDAP server. The two
9143 implementations are quite different in how they use LDAP.&lt;/p&gt;
9144
9145 To get this information, I started slapd with debugging enabled and
9146 dumped the debug output to a file to get the LDAP searches performed
9147 on a Debian Edu main-server. Here is a summary.
9148
9149 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
9150
9151 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
9152 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
9153 the web.
9154
9155 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
9156 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
9157 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
9158 reverse entries are in two different subtrees in LDAP with a structure
9159 based on the DNS names, as in tjener.intern and
9160 2.2.0.10.in-addr.arpa.&lt;/p&gt;
9161
9162 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
9163 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
9164 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
9165 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
9166 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
9167 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
9168 forward entries, it is looking for attributes named dnsttl, arecord,
9169 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9170 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9171 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9172 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9173 spfrecord and modifytimestamp. For reverse entries it is looking for
9174 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9175 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9176 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9177 ldapsearch commands could look like this:&lt;/p&gt;
9178
9179 &lt;blockquote&gt;&lt;pre&gt;
9180 ldapsearch -h ldap \
9181 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9182 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
9183 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9184 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9185 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9186 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9187
9188 ldapsearch -h ldap \
9189 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9190 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
9191 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9192 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9193 srvrecord naptrrecord modifytimestamp
9194 &lt;/pre&gt;&lt;/blockquote&gt;
9195
9196 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
9197 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9198 example LDAP objects used there. In addition to these objects, the
9199 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9200 also exist.&lt;/p&gt;
9201
9202 &lt;blockquote&gt;&lt;pre&gt;
9203 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9204 objectclass: top
9205 objectclass: dnsdomain
9206 objectclass: domainrelatedobject
9207 dc: tjener
9208 arecord: 10.0.2.2
9209 associateddomain: tjener.intern
9210
9211 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9212 objectclass: top
9213 objectclass: dnsdomain2
9214 objectclass: domainrelatedobject
9215 dc: 2
9216 ptrrecord: tjener.intern
9217 associateddomain: 2.2.0.10.in-addr.arpa
9218 &lt;/pre&gt;&lt;/blockquote&gt;
9219
9220 &lt;p&gt;In strict mode, the server behaves differently. When looking for
9221 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
9222 same base as in the tree mode for a object with filter
9223 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
9224 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9225 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9226 naptrrecord and modifytimestamp. For reverse entires it also do a
9227 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
9228 and the requested attributes are associateddomain, dnsttl and
9229 modifytimestamp. In short, in strict mode the objects with ptrrecord
9230 go away, and the arecord attribute in the forward object is used
9231 instead.&lt;/p&gt;
9232
9233 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
9234 like this:&lt;/p&gt;
9235
9236 &lt;blockquote&gt;&lt;pre&gt;
9237 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9238 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
9239 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9240 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9241 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9242 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9243
9244 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9245 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
9246 &lt;/pre&gt;&lt;/blockquote&gt;
9247
9248 &lt;p&gt;In addition to the forward and reverse searches , there is also a
9249 search for SOA records, which behave similar to the forward and
9250 reverse lookups.&lt;/p&gt;
9251
9252 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
9253 specify any objectclass names, and instead look for the attributes it
9254 need to generate a DNS reply. This make it able to work with any
9255 objectclass that provide the needed attributes.&lt;/p&gt;
9256
9257 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
9258 dnsdomain2 schemas. The latter is used for reverse entries like
9259 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
9260
9261 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
9262 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9263 attributes) and domainrelatedobject (for associatedDomain). The use
9264 of structural object classes make it impossible to combine these
9265 classes with the object classes used by DHCP.&lt;/p&gt;
9266
9267 &lt;p&gt;There are other schemas that could be used too, for example the
9268 dnszone structural object class used by Gosa and bind-sdb for the DNS
9269 attributes combined with the domainrelatedobject object class, but in
9270 this case some unused attributes would have to be included as well
9271 (zonename and relativedomainname).&lt;/p&gt;
9272
9273 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
9274 mode and not use any of the existing objectclasses (dnsdomain,
9275 dnsdomain2 and dnszone) when one want to combine the DNS information
9276 with DHCP information, and instead create a auxiliary object class
9277 defined something like this (using the attributes defined for
9278 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
9279
9280 &lt;blockquote&gt;&lt;pre&gt;
9281 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
9282 SUP top
9283 AUXILIARY
9284 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9285 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9286 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9287 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9288 A6Record $ DNAMERecord
9289 ))
9290 &lt;/pre&gt;&lt;/blockquote&gt;
9291
9292 &lt;p&gt;This will allow any object to become a DNS entry when combined with
9293 the domainrelatedobject object class, and allow any entity to include
9294 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
9295 developers asking for their view on this schema and if they are
9296 interested in providing such schema with PowerDNS, and I hope my
9297 message will be accepted into their mailing list soon.&lt;/p&gt;
9298
9299 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
9300
9301 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
9302 the object attributes, and then uses the attributes it want. This
9303 make it harder to figure out exactly what attributes are used, but
9304 thanks to the working example in Debian Edu I can at least get an idea
9305 what is needed without having to read the source code.&lt;/p&gt;
9306
9307 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
9308 search filter to use to locate the correct dhcpServer entity is
9309 stored. These are the relevant entries from
9310 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
9311
9312 &lt;blockquote&gt;&lt;pre&gt;
9313 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
9314 ldap-dhcp-server-cn &quot;dhcp&quot;;
9315 &lt;/pre&gt;&lt;/blockquote&gt;
9316
9317 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
9318 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
9319 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
9320 search result is this entry:&lt;/p&gt;
9321
9322 &lt;blockquote&gt;&lt;pre&gt;
9323 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9324 cn: dhcp
9325 objectClass: top
9326 objectClass: dhcpServer
9327 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9328 &lt;/pre&gt;&lt;/blockquote&gt;
9329
9330 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
9331 subtree with DHCP configuration. The DHCP configuration subtree base
9332 is located using a base scope search with base &quot;cn=DHCP
9333 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
9334 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
9335 The search result is this entry:&lt;/p&gt;
9336
9337 &lt;blockquote&gt;&lt;pre&gt;
9338 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9339 cn: DHCP Config
9340 objectClass: top
9341 objectClass: dhcpService
9342 objectClass: dhcpOptions
9343 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9344 dhcpStatements: ddns-update-style none
9345 dhcpStatements: authoritative
9346 dhcpOption: smtp-server code 69 = array of ip-address
9347 dhcpOption: www-server code 72 = array of ip-address
9348 dhcpOption: wpad-url code 252 = text
9349 &lt;/pre&gt;&lt;/blockquote&gt;
9350
9351 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
9352 all the DHCP configuration is loaded, it is ready to receive requests.
9353 The subtree in Debian Edu contain objects with object classes
9354 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9355 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9356 and information about netmasks, dynamic range etc. Leaving out the
9357 details here because it is not relevant for the focus of my
9358 investigation, which is to see if it is possible to merge dns and dhcp
9359 related computer objects.&lt;/p&gt;
9360
9361 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
9362 of the client (00:00:00:00:00:00 in this example), using a subtree
9363 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
9364 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9365 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
9366 like:&lt;/p&gt;
9367
9368 &lt;blockquote&gt;&lt;pre&gt;
9369 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9370 cn: hostname
9371 objectClass: top
9372 objectClass: dhcpHost
9373 dhcpHWAddress: ethernet 00:00:00:00:00:00
9374 dhcpStatements: fixed-address hostname
9375 &lt;/pre&gt;&lt;/blockquote&gt;
9376
9377 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
9378 The object classes need to have fixed names, and the configuration
9379 need to be stored in a fairly specific LDAP structure. On the
9380 positive side, the invidiual dhcpHost entires can be anywhere without
9381 the DN pointed to by the dhcpServer entries. The latter should make
9382 it possible to group all host entries in a subtree next to the
9383 configuration entries, and this subtree can also be shared with the
9384 DNS server if the schema proposed above is combined with the dhcpHost
9385 structural object class.
9386
9387 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
9388
9389 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
9390 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
9391 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
9392 allowing DNS objects to be stored anywhere under the base cn specified
9393 in the configuration.&lt;/p&gt;
9394
9395 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
9396 regarding which LDAP schemas to use and which LDAP structure to use.
9397 I guess one could implement ones own schema, as long as the
9398 objectclasses and attributes have the names used, but this do not
9399 really help when the DHCP subtree need to have a fairly fixed
9400 structure.&lt;/p&gt;
9401
9402 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
9403 this might work for Debian Edu:&lt;/p&gt;
9404
9405 &lt;blockquote&gt;&lt;pre&gt;
9406 ou=services
9407 cn=machine-info (dhcpService) - dhcpServiceDN points here
9408 cn=dhcp (dhcpServer)
9409 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9410 cn=10.0.2.0 (dhcpSubnet)
9411 cn=group1 (dhcpGroup/dhcpOptions)
9412 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9413 cn=192.168.0.0 (dhcpSubnet)
9414 cn=group1 (dhcpGroup/dhcpOptions)
9415 ou=machines - PowerDNS base points here
9416 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9417 &lt;/pre&gt;&lt;/blockquote&gt;
9418
9419 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
9420 entries to be in the dhcpGroup subtrees, the entries can be stored
9421 there instead of a common machines subtree, and the PowerDNS base
9422 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
9423
9424 &lt;p&gt;The combined object under the machines subtree would look something
9425 like this:&lt;/p&gt;
9426
9427 &lt;blockquote&gt;&lt;pre&gt;
9428 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9429 dc: hostname
9430 objectClass: top
9431 objectClass: dhcpHost
9432 objectclass: domainrelatedobject
9433 objectclass: dnsDomainAux
9434 associateddomain: hostname.intern
9435 arecord: 10.11.12.13
9436 dhcpHWAddress: ethernet 00:00:00:00:00:00
9437 dhcpStatements: fixed-address hostname.intern
9438 &lt;/pre&gt;&lt;/blockquote&gt;
9439
9440 &lt;/p&gt;One could even add the LTSP configuration associated with a given
9441 machine, as long as the required attributes are available in a
9442 auxiliary object class.&lt;/p&gt;
9443 </description>
9444 </item>
9445
9446 <item>
9447 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
9448 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
9449 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
9450 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
9451 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
9452 DHCP services in Debian Edu to use the same LDAP objects for a given
9453 computer, to avoid the possibility of having a inconsistent state for
9454 a computer in LDAP (as in DHCP but no DNS entry or the other way
9455 around) and make it easier to add computers to LDAP.&lt;/p&gt;
9456
9457 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
9458 information finally found a solution that seem to work.&lt;/p&gt;
9459
9460 &lt;p&gt;The old setup required three LDAP objects for a given computer.
9461 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9462 we switch powerdns to use its strict LDAP method (ldap-method=strict
9463 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9464 merged into one while making it impossible to transfer the reverse map
9465 to a slave DNS server.&lt;/p&gt;
9466
9467 &lt;p&gt;If we also replace the object class used to get the DNS related
9468 attributes to one allowing these attributes to be combined with the
9469 dhcphost object class, we can merge the DNS and DHCP entries into one.
9470 I&#39;ve written such object class in the dnsdomainaux.schema file (need
9471 proper OIDs, but that is a minor issue), and tested the setup. It
9472 seem to work.&lt;/p&gt;
9473
9474 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
9475 for both DNS and DHCP, and even the LTSP configuration I suggested in
9476 an earlier email. The combined LDAP object will look something like
9477 this:&lt;/p&gt;
9478
9479 &lt;blockquote&gt;&lt;pre&gt;
9480 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9481 cn: hostname
9482 objectClass: dhcphost
9483 objectclass: domainrelatedobject
9484 objectclass: dnsdomainaux
9485 associateddomain: hostname.intern
9486 arecord: 10.11.12.13
9487 dhcphwaddress: ethernet 00:00:00:00:00:00
9488 dhcpstatements: fixed-address hostname
9489 ldapconfigsound: Y
9490 &lt;/pre&gt;&lt;/blockquote&gt;
9491
9492 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
9493 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9494 before asking DNS to resolve the fixed-adddress. LTSP will use
9495 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
9496
9497 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
9498 dhcphost in a different location, to allow us to put the objects
9499 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
9500 that. If I can&#39;t figure out a way to do that, we can still get rid of
9501 the hosts subtree and move all its content into the DHCP Config tree
9502 (which probably should be renamed to be more related to the new
9503 content. I suspect cn=dnsdhcp,ou=services or something like that
9504 might be a good place to put it.&lt;/p&gt;
9505
9506 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
9507 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9508 </description>
9509 </item>
9510
9511 <item>
9512 <title>Idea for storing LTSP configuration in LDAP</title>
9513 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
9514 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
9515 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
9516 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
9517 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9518 clients, and that this can be used to fetch configuration from LDAP if
9519 Debian Edu choose to store configuration there.&lt;/p&gt;
9520
9521 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
9522 to get configuration from LDAP. The idea is to look up the MAC
9523 address of the client in LDAP, and look for attributes on the form
9524 ltspconfigsetting=value, and use this to export SETTING=value to the
9525 LTSP clients.&lt;/p&gt;
9526
9527 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
9528 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
9529 allowing us to store all information about a computer in one place.&lt;/p&gt;
9530
9531 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
9532 this approach. A real LDAP schema for the ltspClientAux objectclass
9533 need to be written. Comments, suggestions, etc?&lt;/p&gt;
9534
9535 &lt;blockquote&gt;&lt;pre&gt;
9536 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9537 #
9538 # Fetch LTSP client settings from LDAP based on MAC address
9539 #
9540 # Uses ethernet address as stored in the dhcpHost objectclass using
9541 # the dhcpHWAddress attribute or ethernet address stored in the
9542 # ieee802Device objectclass with the macAddress attribute.
9543 #
9544 # This module is written to be schema agnostic, and only depend on the
9545 # existence of attribute names.
9546 #
9547 # The LTSP configuration variables are saved directly using a
9548 # ltspConfig prefix and uppercasing the rest of the attribute name.
9549 # To set the SERVER variable, set the ltspConfigServer attribute.
9550 #
9551 # Some LDAP schema should be created with all the relevant
9552 # configuration settings. Something like this should work:
9553 #
9554 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
9555 # SUP top
9556 # AUXILIARY
9557 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9558
9559 LDAPSERVER=$(debian-edu-ldapserver)
9560 if [ &quot;$LDAPSERVER&quot; ] ; then
9561 LDAPBASE=$(debian-edu-ldapserver -b)
9562 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
9563 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
9564 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
9565 grep &#39;^ltspConfig&#39; | while read attr value ; do
9566 # Remove prefix and convert to upper case
9567 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
9568 # bass value on to clients
9569 eval &quot;$attr=$value; export $attr&quot;
9570 done
9571 done
9572 fi
9573 &lt;/pre&gt;&lt;/blockquote&gt;
9574
9575 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
9576 the while block might end up in a subshell causing the variables set
9577 there to not show up in ltsp-config, but if that is the case I am sure
9578 the code can be restructured to make sure the variables are passed on.
9579 I expect that can be solved with some testing. :)&lt;/p&gt;
9580
9581 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
9582 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9583
9584 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
9585 configuration in LDAP that was created around year 2000 by
9586 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
9587 Xperience, Inc., 2000&lt;/a&gt;. I found its
9588 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
9589 personal home page over at redhat.com.&lt;/p&gt;
9590 </description>
9591 </item>
9592
9593 <item>
9594 <title>jXplorer, a very nice LDAP GUI</title>
9595 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
9596 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
9597 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
9598 <description>&lt;p&gt;Since
9599 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
9600 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
9601 LDAP GUI that is even better than luma. The java application
9602 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
9603 moving LDAP objects and subtrees using drag-and-drop, and can
9604 authenticate using Kerberos. I have only tested the Kerberos
9605 authentication, but do not have a LDAP setup allowing me to rewrite
9606 LDAP with my test user yet. It is
9607 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
9608 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
9609 have with it is how it handle errors. If something go wrong, its
9610 non-intuitive behaviour require me to go through some query work list
9611 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
9612 </description>
9613 </item>
9614
9615 <item>
9616 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
9617 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
9618 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
9619 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
9620 <description>&lt;p&gt;Here is a short update on my &lt;a
9621 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
9622 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
9623 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
9624 not reporting the status for KDE, because the upgrade crashes when
9625 aptitude try because of missing conflicts
9626 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
9627 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
9628
9629 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
9630 complete list of the installed packages. Based on this I see these
9631 differences when I did a test run today. As usual, I do not really
9632 know what the correct set of packages would be, but thought it best to
9633 publish the difference.&lt;/p&gt;
9634
9635 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9636
9637 &lt;blockquote&gt;&lt;p&gt;
9638 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
9639 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
9640 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9641 libgtksourceview-common libpt-1.10.10-plugins-alsa
9642 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9643 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9644 python-4suite-xml python-eggtrayicon python-gtkhtml2
9645 python-gtkmozembed svgalibg1 xserver-xephyr zip
9646 &lt;/p&gt;&lt;/blockquote&gt;
9647
9648 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
9649
9650 &lt;blockquote&gt;&lt;p&gt;
9651 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9652 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9653 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
9654 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
9655 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
9656 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
9657 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
9658 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
9659 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
9660 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
9661 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
9662 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
9663 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9664 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
9665 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9666 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
9667 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
9668 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9669 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9670 mysql-common swfdec-gnome totem-gstreamer wodim
9671 &lt;/p&gt;&lt;/blockquote&gt;
9672
9673 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
9674
9675 &lt;blockquote&gt;&lt;p&gt;
9676 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9677 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9678 xserver-xorg-input-all xserver-xorg-input-evdev
9679 xserver-xorg-input-kbd xserver-xorg-input-mouse
9680 xserver-xorg-input-synaptics xserver-xorg-video-all
9681 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9682 xserver-xorg-video-chips xserver-xorg-video-cirrus
9683 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9684 xserver-xorg-video-glint xserver-xorg-video-i128
9685 xserver-xorg-video-i740 xserver-xorg-video-mach64
9686 xserver-xorg-video-mga xserver-xorg-video-neomagic
9687 xserver-xorg-video-nouveau xserver-xorg-video-nv
9688 xserver-xorg-video-r128 xserver-xorg-video-radeon
9689 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9690 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9691 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9692 xserver-xorg-video-sis xserver-xorg-video-sisusb
9693 xserver-xorg-video-tdfx xserver-xorg-video-tga
9694 xserver-xorg-video-trident xserver-xorg-video-tseng
9695 xserver-xorg-video-vesa xserver-xorg-video-vmware
9696 xserver-xorg-video-voodoo
9697 &lt;/p&gt;&lt;/blockquote&gt;
9698
9699 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
9700
9701 &lt;blockquote&gt;&lt;p&gt;
9702 deskbar-applet xserver-xorg xserver-xorg-core
9703 xserver-xorg-input-wacom xserver-xorg-video-intel
9704 xserver-xorg-video-openchrome
9705 &lt;/p&gt;&lt;/blockquote&gt;
9706
9707 &lt;p&gt;I was told on IRC that the xorg-xserver package was
9708 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
9709 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
9710 No idea when it hits Squeeze, but when it does I hope it will reduce
9711 the difference somewhat.
9712 </description>
9713 </item>
9714
9715 <item>
9716 <title>LUMA, a very nice LDAP GUI</title>
9717 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
9718 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
9719 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
9720 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
9721 directory in Debian Edu, and in the process I started to miss a GUI
9722 tool to browse the LDAP tree. The only one I was able to find in
9723 Debian/Squeeze and Lenny is
9724 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
9725 be a great tool to get a overview of the current LDAP directory
9726 populated by default in Skolelinux. Thanks to it, I have been able to
9727 find empty and obsolete subtrees, misplaced objects and duplicate
9728 objects. It will be installed by default in Debian/Squeeze. If you
9729 are working with LDAP, give it a go. :)&lt;/p&gt;
9730
9731 &lt;p&gt;I did notice one problem with it I have not had time to report to
9732 the BTS yet. There is no .desktop file in the package, so the tool do
9733 not show up in the Gnome and KDE menus, but only deep down in in the
9734 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9735 released.&lt;/p&gt;
9736
9737 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
9738 like to move objects and remove subtrees directly in the GUI, but have
9739 not found a way to do that with LUMA yet. So in the mean time, I use
9740 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
9741
9742 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
9743 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9744
9745 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
9746 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
9747 useful GUI alternative. It seem like a good tool, but is unmaintained
9748 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9749 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
9750 </description>
9751 </item>
9752
9753 <item>
9754 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
9755 <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>
9756 <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>
9757 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
9758 <description>&lt;p&gt;A while back, I
9759 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
9760 about the fact&lt;/a&gt; that it is not possible with the provided schemas
9761 for storing DNS and DHCP information in LDAP to combine the two sets
9762 of information into one LDAP object representing a computer.&lt;/p&gt;
9763
9764 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
9765 the dhcpHost object class auxiliary, to allow it to be combined with
9766 the dNSDomain object class, and thus forming one object for one
9767 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
9768
9769 &lt;p&gt;If I understand this correctly, it is not safe to do this change
9770 without also changing the assigned number for the object class, and I
9771 do not know enough about LDAP schema design to do that properly for
9772 Debian Edu.&lt;/p&gt;
9773
9774 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
9775 the
9776 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
9777 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
9778 available today from IETF.&lt;/p&gt;
9779
9780 &lt;pre&gt;
9781 --- dhcp.schema (revision 65192)
9782 +++ dhcp.schema (working copy)
9783 @@ -376,7 +376,7 @@
9784 objectclass ( 2.16.840.1.113719.1.203.6.6
9785 NAME &#39;dhcpHost&#39;
9786 DESC &#39;This represents information about a particular client&#39;
9787 - SUP top
9788 + SUP top AUXILIARY
9789 MUST cn
9790 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9791 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
9792 &lt;/pre&gt;
9793
9794 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
9795 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9796 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
9797
9798 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
9799 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
9800 </description>
9801 </item>
9802
9803 <item>
9804 <title>Calling tasksel like the installer, while still getting useful output</title>
9805 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
9806 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
9807 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
9808 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
9809 installs packages during the normal debian-installer run. Until now,
9810 I have ended up letting tasksel do the work, with the annoying problem
9811 of not getting any feedback at all when something fails (like a
9812 conffile question from dpkg or a download that fails), using code like
9813 this:
9814
9815 &lt;blockquote&gt;&lt;pre&gt;
9816 export DEBIAN_FRONTEND=noninteractive
9817 tasksel --new-install
9818 &lt;/pre&gt;&lt;/blockquote&gt;
9819
9820 This would invoke tasksel, let its automatic task selection pick the
9821 tasks to install, and continue to install the requested tasks without
9822 any output what so ever.
9823
9824 Recently I revisited this problem while working on the automatic
9825 package upgrade testing, because tasksel would some times hang without
9826 any useful feedback, and I want to see what is going on when it
9827 happen. Then it occured to me, I can parse the output from tasksel
9828 when asked to run in test mode, and use that aptitude command line
9829 printed by tasksel then to simulate the tasksel run. I ended up using
9830 code like this:
9831
9832 &lt;blockquote&gt;&lt;pre&gt;
9833 export DEBIAN_FRONTEND=noninteractive
9834 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
9835 $cmd
9836 &lt;/pre&gt;&lt;/blockquote&gt;
9837
9838 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
9839 --without-recommends -o APT::Install-Recommends=no -y install
9840 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9841 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
9842 laptop task and all packages with priority standard , required and
9843 important, just like tasksel would have done it during
9844 installation.&lt;/p&gt;
9845
9846 &lt;p&gt;A better approach is probably to extend tasksel to be able to
9847 install packages without using debconf-apt-progress, for use cases
9848 like this.&lt;/p&gt;
9849 </description>
9850 </item>
9851
9852 <item>
9853 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
9854 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
9855 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
9856 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
9857 <description>&lt;p&gt;My
9858 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
9859 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
9860 finally made the upgrade logs available from
9861 &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;.
9862 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9863 apt and aptitude, and found their differences interesting. This time
9864 I will only focus on their removal plans.&lt;/p&gt;
9865
9866 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
9867 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
9868 surprising part is that it want to remove xorg and all
9869 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9870 sure why. When asking aptitude to do the same, it want to remove 129
9871 packages, but most of them are library packages I suspect are no
9872 longer needed. Both of them want to remove bluetooth packages, which
9873 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
9874
9875 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
9876 which seem like a bad idea and xorg the same way as with Gnome. Asking
9877 aptitude for the same, it wants to remove 192 packages, none which are
9878 too surprising.&lt;/p&gt;
9879
9880 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
9881 and avoided, and perhaps others as well. Here are the complete list
9882 of planned removals. The complete logs is available from the URL
9883 above. Note if you want to repeat these tests, that the upgrade test
9884 for kde+apt-get hung in the tasksel setup because of dpkg asking
9885 conffile questions. No idea why. I worked around it by using
9886 &#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
9887 continue.&lt;/p&gt;
9888
9889 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
9890 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
9891 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9892 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
9893 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9894 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9895 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9896 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9897 xserver-xorg-input-kbd xserver-xorg-input-mouse
9898 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9899 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9900 xserver-xorg-video-ati xserver-xorg-video-chips
9901 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9902 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9903 xserver-xorg-video-glint xserver-xorg-video-i128
9904 xserver-xorg-video-i740 xserver-xorg-video-imstt
9905 xserver-xorg-video-intel xserver-xorg-video-mach64
9906 xserver-xorg-video-mga xserver-xorg-video-neomagic
9907 xserver-xorg-video-nsc xserver-xorg-video-nv
9908 xserver-xorg-video-openchrome xserver-xorg-video-r128
9909 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9910 xserver-xorg-video-rendition xserver-xorg-video-s3
9911 xserver-xorg-video-s3virge xserver-xorg-video-savage
9912 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9913 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9914 xserver-xorg-video-tga xserver-xorg-video-trident
9915 xserver-xorg-video-tseng xserver-xorg-video-v4l
9916 xserver-xorg-video-vesa xserver-xorg-video-vga
9917 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
9918 xulrunner-1.9-gnome-support&lt;/p&gt;
9919
9920 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
9921
9922 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
9923 djvulibre-desktop finger gnome-app-install gnome-mount
9924 gnome-network-admin gnome-spell gnome-vfs-obexftp
9925 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9926 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9927 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9928 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
9929 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
9930 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
9931 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
9932 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
9933 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
9934 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
9935 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
9936 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
9937 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9938 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
9939 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
9940 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
9941 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
9942 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
9943 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9944 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9945 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9946 openoffice.org-writer2latex openssl-blacklist p7zip
9947 python-4suite-xml python-eggtrayicon python-gnome2-desktop
9948 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9949 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9950 swfdec-mozilla totem-gstreamer update-manager wodim
9951 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9952 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9953 zip&lt;/p&gt;
9954
9955 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
9956
9957 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9958 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9959 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9960 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9961 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9962 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9963 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9964 xserver-xorg-input-kbd xserver-xorg-input-mouse
9965 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9966 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9967 xserver-xorg-video-ati xserver-xorg-video-chips
9968 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9969 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9970 xserver-xorg-video-glint xserver-xorg-video-i128
9971 xserver-xorg-video-i740 xserver-xorg-video-imstt
9972 xserver-xorg-video-intel xserver-xorg-video-mach64
9973 xserver-xorg-video-mga xserver-xorg-video-neomagic
9974 xserver-xorg-video-nsc xserver-xorg-video-nv
9975 xserver-xorg-video-openchrome xserver-xorg-video-r128
9976 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9977 xserver-xorg-video-rendition xserver-xorg-video-s3
9978 xserver-xorg-video-s3virge xserver-xorg-video-savage
9979 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9980 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9981 xserver-xorg-video-tga xserver-xorg-video-trident
9982 xserver-xorg-video-tseng xserver-xorg-video-v4l
9983 xserver-xorg-video-vesa xserver-xorg-video-vga
9984 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
9985
9986 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
9987 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
9988 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9989 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9990 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9991 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9992 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9993 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9994 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9995 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9996 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9997 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9998 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9999 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
10000 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
10001 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
10002 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
10003 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
10004 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10005 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
10006 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
10007 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10008 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
10009 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
10010 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
10011 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10012 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
10013 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
10014 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
10015 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
10016 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
10017 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
10018 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
10019 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
10020 texlive-common texlive-doc-base texlive-fonts-recommended
10021 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10022 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10023 xulrunner-1.9&lt;/p&gt;
10024
10025 </description>
10026 </item>
10027
10028 <item>
10029 <title>Automatic upgrade testing from Lenny to Squeeze</title>
10030 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
10031 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
10032 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
10033 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
10034 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10035 have been discovered and reported in the process
10036 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
10037 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
10038 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
10039 kdebase-workspace-data), and to get a more regular testing going on, I
10040 am working on a script to automate the test.&lt;/p&gt;
10041
10042 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
10043 Gnome or KDE desktop installation inside the chroot before upgrading
10044 it. To ensure no services are started in the chroot, a policy-rc.d
10045 script is inserted. To make sure tasksel believe it is to install a
10046 desktop on a laptop, the tasksel tests are replaced in the chroot
10047 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
10048
10049 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10050 currently always fail because udev refuses to upgrade with the kernel
10051 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10052 is created. The bug report
10053 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
10054 this problem do not trigger in a chroot, but I touch the file anyway
10055 to make sure the upgrade go well. Testing on virtual and real
10056 hardware have failed me because of udev so far, and creating this file
10057 do the trick in such settings anyway. This is a
10058 &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
10059 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
10060 maintainer because he lack the resources to rewrite udev to keep
10061 working with old kernels or something like that. I really wish the
10062 udev upstream would keep udev backwards compatible, to avoid such
10063 upgrade problem, but given that they fail to do so, I guess
10064 documenting the way out of this mess is the best option we got for
10065 Debian Squeeze.&lt;/p&gt;
10066
10067 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
10068 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
10069 trick:&lt;/p&gt;
10070
10071 &lt;blockquote&gt;&lt;pre&gt;
10072 #!/bin/sh
10073 set -ex
10074
10075 if [ &quot;$1&quot; ] ; then
10076 desktop=$1
10077 else
10078 desktop=gnome
10079 fi
10080
10081 from=lenny
10082 to=squeeze
10083
10084 exec &amp;lt; /dev/null
10085 unset LANG
10086 mirror=http://ftp.skolelinux.org/debian
10087 tmpdir=chroot-$from-upgrade-$to-$desktop
10088 fuser -mv .
10089 debootstrap $from $tmpdir $mirror
10090 chroot $tmpdir aptitude update
10091 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
10092 #!/bin/sh
10093 exit 101
10094 EOF
10095 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10096 exit_cleanup() {
10097 umount $tmpdir/proc
10098 }
10099 mount -t proc proc $tmpdir/proc
10100 # Make sure proc is unmounted also on failure
10101 trap exit_cleanup EXIT INT
10102
10103 chroot $tmpdir aptitude -y install debconf-utils
10104
10105 # Make sure tasksel autoselection trigger. It need the test scripts
10106 # to return the correct answers.
10107 echo tasksel tasksel/desktop multiselect $desktop | \
10108 chroot $tmpdir debconf-set-selections
10109
10110 # Include the desktop and laptop task
10111 for test in desktop laptop ; do
10112 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
10113 #!/bin/sh
10114 exit 2
10115 EOF
10116 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10117 done
10118
10119 DEBIAN_FRONTEND=noninteractive
10120 DEBIAN_PRIORITY=critical
10121 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10122 chroot $tmpdir tasksel --new-install
10123
10124 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
10125 chroot $tmpdir aptitude update
10126 touch $tmpdir/etc/udev/kernel-upgrade
10127 chroot $tmpdir aptitude -y dist-upgrade
10128 fuser -mv
10129 &lt;/pre&gt;&lt;/blockquote&gt;
10130
10131 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
10132 with aptitude, but I have not had time to look at how they behave
10133 differently so far. I hope to get a cron job running to do the test
10134 regularly and post the result on the web. The Gnome upgrade currently
10135 work, while the KDE upgrade fail because of the bug in
10136 kdebase-workspace-data&lt;/p&gt;
10137
10138 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
10139 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
10140 post, so I will refrain from trying. I can report that for Gnome,
10141 aptitude report 760 packages upgraded, 448 newly installed, 129 to
10142 remove and 1 not upgraded and 1024MB need to be downloaded while for
10143 KDE the same numbers are 702 packages upgraded, 507 newly installed,
10144 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
10145
10146 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
10147 is able to migrate to dependency based boot sequencing and parallel
10148 booting without a hitch. Was unsure if there were still bugs with
10149 packages failing to clean up their obsolete init.d script during
10150 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10151 packages.&lt;/p&gt;
10152 </description>
10153 </item>
10154
10155 <item>
10156 <title>Upstart or sysvinit - as init.d scripts see it</title>
10157 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
10158 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
10159 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
10160 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
10161 scripts to migrate (some of) their operations to upstart job while
10162 keeping the init.d for hurd and kfreebsd. The packages with such
10163 needs will need a way to get their init.d scripts to behave
10164 differently when used with sysvinit and with upstart. Because of
10165 this, I had a look at the environment variables set when a init.d
10166 script is running under upstart, and when it is not.&lt;/p&gt;
10167
10168 &lt;p&gt;With upstart, I notice these environment variables are set when a
10169 script is started from rcS.d/ (ignoring some irrelevant ones like
10170 COLUMNS):&lt;/p&gt;
10171
10172 &lt;blockquote&gt;&lt;pre&gt;
10173 DEFAULT_RUNLEVEL=2
10174 previous=N
10175 PREVLEVEL=
10176 RUNLEVEL=
10177 runlevel=S
10178 UPSTART_EVENTS=startup
10179 UPSTART_INSTANCE=
10180 UPSTART_JOB=rc-sysinit
10181 &lt;/pre&gt;&lt;/blockquote&gt;
10182
10183 &lt;p&gt;With sysvinit, these environment variables are set for the same
10184 script.&lt;/p&gt;
10185
10186 &lt;blockquote&gt;&lt;pre&gt;
10187 INIT_VERSION=sysvinit-2.88
10188 previous=N
10189 PREVLEVEL=N
10190 RUNLEVEL=S
10191 runlevel=S
10192 &lt;/pre&gt;&lt;/blockquote&gt;
10193
10194 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
10195 sysvinit are not set by upstart. Not sure if it is intentional or not
10196 to not be compatible with sysvinit in this regard.&lt;/p&gt;
10197
10198 &lt;p&gt;For scripts needing to behave differently when upstart is used,
10199 looking for the UPSTART_JOB environment variable seem to be a good
10200 choice.&lt;/p&gt;
10201 </description>
10202 </item>
10203
10204 <item>
10205 <title>A manual for standards wars...</title>
10206 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
10207 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
10208 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
10209 <description>&lt;p&gt;Via the
10210 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
10211 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
10212 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
10213 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
10214 following the standards wars of today.&lt;/p&gt;
10215 </description>
10216 </item>
10217
10218 <item>
10219 <title>Sitesummary tip: Listing computer hardware models used at site</title>
10220 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
10221 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
10222 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
10223 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
10224 to get a list of the machine types in use thanks to the DMI
10225 information extracted from each machine. The script to do so is
10226 included in the sitesummary package, and here is example output from
10227 the Skolelinux build servers:&lt;/p&gt;
10228
10229 &lt;blockquote&gt;&lt;pre&gt;
10230 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10231 vendor count
10232 Dell Computer Corporation 1
10233 PowerEdge 1750 1
10234 IBM 1
10235 eserver xSeries 345 -[8670M1X]- 1
10236 Intel 2
10237 [no-dmi-info] 3
10238 maintainer:~#
10239 &lt;/pre&gt;&lt;/blockquote&gt;
10240
10241 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
10242 provided in each machine. Here there are Intel machines without model
10243 information listed with Intel as vendor and no model, and virtual Xen
10244 machines listed as [no-dmi-info]. One can add -l as a command line
10245 option to list the individual machines.&lt;/p&gt;
10246
10247 &lt;p&gt;A larger list is
10248 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
10249 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
10250 provide the basic sitesummary report publicly. In their report there
10251 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
10252 their machines, and as sitesummary is available in both distributions,
10253 it is trivial to get all of them to report to the same central
10254 collector.&lt;/p&gt;
10255 </description>
10256 </item>
10257
10258 <item>
10259 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
10260 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
10261 <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>
10262 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
10263 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
10264 start at boot when an NVidia video card is used is handled. The
10265 problem seem to be that the nvidia X.org driver uses a long time to
10266 initialize, and this duration is longer than kdm is configured to
10267 wait.&lt;/p&gt;
10268
10269 &lt;p&gt;I came across two bugs related to this issue,
10270 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
10271 against initscripts and passed on to nvidia-glx when it became obvious
10272 that the nvidia drivers were involved, and
10273 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
10274 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
10275
10276 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
10277 problem nvidia video card owners experience and make sure the Debian
10278 distribution work out of the box for these users. The nvidia driver
10279 maintainers expect kdm to be set up to wait longer, while kdm expect
10280 the nvidia driver maintainers to fix the driver to start faster, and
10281 while they wait for each other I guess the users end up switching to a
10282 distribution that work for them. I have no idea what the solution is,
10283 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
10284
10285 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
10286 </description>
10287 </item>
10288
10289 <item>
10290 <title>Parallellized boot seem to hold up well in Debian/testing</title>
10291 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
10292 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
10293 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
10294 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
10295 The feature seem to hold up pretty well, but three fairly serious
10296 issues are known and should be solved:
10297
10298 &lt;p&gt;&lt;ul&gt;
10299
10300 &lt;li&gt;The wicd package seen to
10301 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
10302 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
10303 parallel booting is enabled. No idea why, but the wicd maintainer
10304 seem to be on the case.&lt;/li&gt;
10305
10306 &lt;li&gt;The nvidia X driver seem to
10307 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
10308 triggered more easily when parallel booting is in effect. The
10309 maintainer is on the case.&lt;/li&gt;
10310
10311 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
10312 sequencing (the shutdown is broken) when old file-rc users
10313 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
10314 sysv-rc. One way to solve it would be for file-rc to create
10315 /etc/init.d/.legacy-bootordering, and another is to try to make
10316 sysv-rc more robust. Will investigate some more and probably upload a
10317 workaround in sysv-rc to help those trying to move from file-rc to
10318 sysv-rc get a working shutdown.&lt;/li&gt;
10319
10320 &lt;/ul&gt;&lt;/p&gt;
10321
10322 &lt;p&gt;All in all not many surprising issues, and all of them seem
10323 solvable before Squeeze is released. In addition to these there are
10324 some packages with bugs in their dependencies and run level settings,
10325 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
10326
10327 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10328 the BTS, please usertag the report to get it to show up at
10329 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10330 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10331
10332 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
10333 </description>
10334 </item>
10335
10336 <item>
10337 <title>More flexible firmware handling in debian-installer</title>
10338 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
10339 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
10340 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
10341 <description>&lt;p&gt;After a long break from debian-installer development, I finally
10342 found time today to return to the project. Having to spend less time
10343 working dependency based boot in debian, as it is almost complete now,
10344 definitely helped freeing some time.&lt;/p&gt;
10345
10346 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
10347 include some firmware packages on the Debian Edu CDs, those needed to
10348 get disk and network controllers working. Without having these
10349 firmware packages available during installation, it is impossible to
10350 install Debian Edu on the given machine, and because our target group
10351 are non-technical people, asking them to provide firmware packages on
10352 an external medium is a support pain. Initially, I expected it to be
10353 enough to include the firmware packages on the CD to get
10354 debian-installer to find and use them. This proved to be wrong.
10355 Next, I hoped it was enough to symlink the relevant firmware packages
10356 to some useful location on the CD (tried /cdrom/ and
10357 /cdrom/firmware/). This also proved to not work, and at this point I
10358 found time to look at the debian-installer code to figure out what was
10359 going to work.&lt;/p&gt;
10360
10361 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
10362 look revealed that it would only look for firmware packages outside
10363 the installation media, so the CD was never checked for firmware
10364 packages. It would only check USB sticks, floppies and other
10365 &quot;external&quot; media devices. Today I changed it to also look in the
10366 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10367 solve the problem I ran into with Debian edu. I also changed it to
10368 look in /firmware/, to make sure the installer also find firmware
10369 provided in the initrd when booting the installer via PXE, to allow us
10370 to provide the same feature in the PXE setup included in Debian
10371 Edu.&lt;/p&gt;
10372
10373 &lt;p&gt;To make sure firmware deb packages with a license questions are not
10374 activated without asking if the license is accepted, I extended
10375 hw-detect to look for preinst scripts in the firmware packages, and
10376 run these before activating the firmware during installation. The
10377 license question is asked using debconf in the preinst, so this should
10378 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
10379
10380 &lt;p&gt;If you want to discuss the details of these features, please
10381 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
10382 </description>
10383 </item>
10384
10385 <item>
10386 <title>Parallellized boot is now the default in Debian/unstable</title>
10387 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
10388 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
10389 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
10390 <description>&lt;p&gt;Since this evening, parallel booting is the default in
10391 Debian/unstable for machines using dependency based boot sequencing.
10392 Apparently the testing of concurrent booting has been wider than
10393 expected, if I am to believe the
10394 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
10395 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
10396 with the feature this weekend, to give us some time to detect any
10397 remaining problems before Squeeze is frozen. If serious problems are
10398 detected, it is simple to change the default back to sequential boot.
10399 The upload of the new sysvinit package also activate a new upstream
10400 version.&lt;/p&gt;
10401
10402 More information about
10403 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
10404 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
10405 currently possible to disable parallel booting when one run into
10406 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
10407
10408 &lt;blockquote&gt;&lt;pre&gt;
10409 CONCURRENCY=none
10410 &lt;/pre&gt;&lt;/blockquote&gt;
10411
10412 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10413 the BTS, please usertag the report to get it to show up at
10414 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10415 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10416 </description>
10417 </item>
10418
10419 <item>
10420 <title>Sitesummary tip: Listing MAC address of all clients</title>
10421 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
10422 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
10423 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
10424 <description>&lt;p&gt;In the recent Debian Edu versions, the
10425 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
10426 system&lt;/a&gt; is used to keep track of the machines in the school
10427 network. Each machine will automatically report its status to the
10428 central server after boot and once per night. The network setup is
10429 also reported, and using this information it is possible to get the
10430 MAC address of all network interfaces in the machines. This is useful
10431 to update the DHCP configuration.&lt;/p&gt;
10432
10433 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
10434 ist all MAC addresses of all machines reporting to sitesummary. Run
10435 this on the collector host:&lt;/p&gt;
10436
10437 &lt;blockquote&gt;&lt;pre&gt;
10438 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
10439 &lt;/pre&gt;&lt;/blockquote&gt;
10440
10441 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
10442 line per machine and with space between the MAC addresses.&lt;/p&gt;
10443
10444 &lt;p&gt;To allow system administrators easier job at adding static DHCP
10445 addresses for hosts, it would be possible to extend this to fetch
10446 machine information from sitesummary and update the DHCP and DNS
10447 tables in LDAP using this information. Such tool is unfortunately not
10448 written yet.&lt;/p&gt;
10449 </description>
10450 </item>
10451
10452 <item>
10453 <title>systemd, an interesting alternative to upstart</title>
10454 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
10455 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
10456 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
10457 <description>&lt;p&gt;The last few days a new boot system called
10458 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
10459 has been
10460 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
10461
10462 to the free software world. I have not yet had time to play around
10463 with it, but it seem to be a very interesting alternative to
10464 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
10465 a good alternative for Debian when we are able to switch to an event
10466 based boot system. Tollef is
10467 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
10468 systemd into Debian, and I look forward to seeing how well it work. I
10469 like the fact that systemd handles init.d scripts with dependency
10470 information natively, allowing them to run in parallel where upstart
10471 at the moment do not.&lt;/p&gt;
10472
10473 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
10474 platform support. It only work on recent Linux kernels, and also need
10475 some new kernel features enabled to function properly. This means
10476 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10477 system. Not sure how that will be handled if systemd proves to be the
10478 way forward.&lt;/p&gt;
10479
10480 &lt;p&gt;In the mean time, based on the
10481 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
10482 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
10483 decided to enable full parallel booting as the default in Debian as
10484 soon as possible (probably this weekend or early next week), to see if
10485 there are any remaining serious bugs in the init.d dependencies. A
10486 new version of the sysvinit package implementing this change is
10487 already in experimental. If all go well, Squeeze will be released
10488 with parallel booting enabled by default.&lt;/p&gt;
10489 </description>
10490 </item>
10491
10492 <item>
10493 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
10494 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
10495 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
10496 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
10497 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
10498 complete, so complete that it is actually possible to run all the
10499 init.d scripts in parallell based on these dependencies. If you want
10500 to test your Squeeze system, make sure
10501 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
10502 based boot sequencing&lt;/a&gt; is enabled, and add this line to
10503 /etc/default/rcS:&lt;/p&gt;
10504
10505 &lt;blockquote&gt;&lt;pre&gt;
10506 CONCURRENCY=makefile
10507 &lt;/pre&gt;&lt;/blockquote&gt;
10508
10509 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
10510 scripts in parallel using the dependency information stored in
10511 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10512 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10513 to try to start the kdm and gdm scripts as early as possible, and will
10514 start the facilities required by kdm or gdm as early as possible to
10515 make this happen.&lt;/p&gt;
10516
10517 &lt;p&gt;Give it a try, and see if you like the result. If some services
10518 fail to start properly, it is most likely because they have incomplete
10519 init.d script dependencies in their startup script (or some of their
10520 dependent scripts have incomplete dependencies). Report bugs and get
10521 the package maintainers to fix it. :)&lt;/p&gt;
10522
10523 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
10524 manage to get the init.d script dependencies complete and correct. I
10525 expect we will get there in Squeeze+1, if we get manage to test and
10526 fix the remaining issues.&lt;/p&gt;
10527
10528 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
10529 the BTS, please usertag the report to get it to show up at
10530 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
10531 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
10532 </description>
10533 </item>
10534
10535 <item>
10536 <title>Debian has switched to dependency based boot sequencing</title>
10537 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
10538 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
10539 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
10540 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
10541 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
10542 have been migrated to using dependency based boot sequencing. This
10543 conclude work me and others have been doing for the last three days.
10544 It feels great to see this finally part of the default Debian
10545 installation. Now we just need to weed out the last few problems that
10546 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
10547
10548 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
10549 fixing the more fundamental problem of handing the event based
10550 non-predictable kernel in the early boot.&lt;/p&gt;
10551 </description>
10552 </item>
10553
10554 <item>
10555 <title>Taking over sysvinit development</title>
10556 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
10557 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
10558 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
10559 <description>&lt;p&gt;After several years of frustration with the lack of activity from
10560 the existing sysvinit upstream developer, I decided a few weeks ago to
10561 take over the package and become the new upstream. The number of
10562 patches to track for the Debian package was becoming a burden, and the
10563 lack of synchronization between the distribution made it hard to keep
10564 the package up to date.&lt;/p&gt;
10565
10566 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10567 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
10568 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
10569 and Fedora), based on the patches currently in use in these
10570 distributions. We Debian maintainers plan to move to this tarball as
10571 the new upstream as soon as we find time to do the merge. Since the
10572 new tarball was created, we agreed with Werner at SuSe to make a new
10573 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
10574 development there. The project is registered and currently waiting
10575 for approval by the Savannah administrators, and as soon as it is
10576 approved, we will import the old versions from svn and continue
10577 working on the future release.&lt;/p&gt;
10578
10579 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
10580 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
10581 </description>
10582 </item>
10583
10584 <item>
10585 <title>Debian boots quicker and quicker</title>
10586 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
10587 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
10588 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
10589 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
10590 people involved in the boot system on Debian and Ubuntu, to see if we
10591 could find more ways to speed up the boot system. This was an Ubuntu
10592 funded
10593 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
10594 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
10595 of boot systems, and ways to handle the increasing number of boot
10596 issues introduced by the Linux kernel becoming more and more
10597 asynchronous and event base. The Ubuntu approach using udev and
10598 upstart might be a good way forward. Time will show.&lt;/p&gt;
10599
10600 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
10601 process in Debian. All of these should be applied to get a quick
10602 boot:&lt;/p&gt;
10603
10604 &lt;ul&gt;
10605
10606 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
10607
10608 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
10609 clock is in UTC.&lt;/li&gt;
10610
10611 &lt;li&gt;Install and activate the insserv package to enable
10612 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
10613 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
10614
10615 &lt;/ul&gt;
10616
10617 These points are based on the Google summer of code work done by
10618 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
10619 Villegas&lt;/a&gt;.
10620
10621 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
10622 unstable yesterday. When we tested it, we were able to cut 6 seconds
10623 from the boot sequence. It depend on very correct dependency
10624 declaration in all init.d scripts, so I expect us to find edge cases
10625 where the dependences in some scripts are slightly wrong when we start
10626 using this.&lt;/p&gt;
10627
10628 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10629 introduced by Raphael Geissert today, one that could affect the
10630 startup speed as well. Instead of starting some scripts concurrently
10631 from rcS.d/ and another set of scripts from rc2.d/, it would be
10632 possible to run a of them in the same process. A quick way to test
10633 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
10634 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
10635 </description>
10636 </item>
10637
10638 <item>
10639 <title>BSAs påstander om piratkopiering møter motstand</title>
10640 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
10641 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
10642 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
10643 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
10644 programvareselskapene som Microsoft og Apple, publisert en rapport der
10645 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10646 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10647 dager siden kom
10648 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
10649 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
10650 dagene. Et spesielt interessant kommentar fra Sverige,
10651 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
10652 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
10653
10654 &lt;blockquote&gt;
10655 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
10656 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10657 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
10658 exakta&quot;, säger BSAs Sverigechef John Hugosson.
10659 &lt;/blockquote&gt;
10660
10661 &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
10662 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
10663 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
10664 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
10665 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
10666
10667 &lt;p&gt;Fant lenkene via &lt;a
10668 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
10669 på Slashdot&lt;/a&gt;.&lt;/p&gt;
10670 </description>
10671 </item>
10672
10673 <item>
10674 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
10675 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
10676 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
10677 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
10678 <description>&lt;p&gt;Kom over
10679 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
10680 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10681 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10682 jobber til daglig. En rask opptelling forteller meg at vi har 490
10683 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
10684 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
10685 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
10686 </description>
10687 </item>
10688
10689 <item>
10690 <title>Kryptert harddisk - naturligvis</title>
10691 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
10692 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
10693 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
10694 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
10695 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
10696 når en tar tap av arbeidstid, fortrolige dokumenter,
10697 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10698 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10699 til at jeg har kryptert harddisken på både kontormaskinen og min
10700 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10701 komme på avveie, den første informasjon relatert til jobben min ved
10702 Universitetet i Oslo, og den andre relatert til blant annet
10703 foreningsarbeide. Kryptering av diskene gjør at det er lite
10704 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10705 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10706 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10707 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10708 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10709 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10710 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10711 det er gjort slik jeg gjør det er minimale, og gevinstene er
10712 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10713 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
10714
10715 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10716 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10717 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10718 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10719 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10720 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10721 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10722 betydelige.&lt;/p&gt;
10723 </description>
10724 </item>
10725
10726 <item>
10727 <title>Two projects that have improved the quality of free software a lot</title>
10728 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
10729 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
10730 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
10731 <description>&lt;p&gt;There are two software projects that have had huge influence on the
10732 quality of free software, and I wanted to mention both in case someone
10733 do not yet know them.&lt;/p&gt;
10734
10735 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
10736 tool to detect and expose errors in the memory handling of programs.
10737 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
10738 and it will report any problems on stdout. It is even better if the
10739 program include debug information. With debug information, it is able
10740 to report the source file name and line number where the problem
10741 occurs. It can report things like &#39;reading past memory block in file
10742 X line N, the memory block was allocated in file Y, line M&#39;, and
10743 &#39;using uninitialised value in control logic&#39;. This tool has made it
10744 trivial to investigate reproducible crash bugs in programs, and have
10745 reduced the number of this kind of bugs in free software a lot.
10746
10747 &lt;p&gt;The second one is
10748 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
10749 a source code checker. It is able to process the source of a program
10750 and find problems in the logic without running the program. It
10751 started out as the Stanford Checker and became well known when it was
10752 used to find bugs in the Linux kernel. It is now a commercial tool
10753 and the company behind it is running
10754 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
10755 free software community, where a lot of free software projects get
10756 their source checked for free. Several thousand defects have been
10757 found and fixed so far. It can find errors like &#39;lock L taken in file
10758 X line N is never released if exiting in line M&#39;, or &#39;the code in file
10759 Y lines O to P can never be executed&#39;. The projects included in the
10760 community service project have managed to get rid of a lot of
10761 reliability problems thanks to Coverity.&lt;/p&gt;
10762
10763 &lt;p&gt;I believe tools like this, that are able to automatically find
10764 errors in the source, are vital to improve the quality of software and
10765 make sure we can get rid of the crashing and failing software we are
10766 surrounded by today.&lt;/p&gt;
10767 </description>
10768 </item>
10769
10770 <item>
10771 <title>No patch is not better than a useless patch</title>
10772 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
10773 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
10774 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
10775 <description>&lt;p&gt;Julien Blache
10776 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
10777 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
10778 patch allow one to discuss a concrete and proposed solution, and also
10779 prove that the issue at hand is important enough for someone to spent
10780 time on fixing it. No patch do not provide any of these positive
10781 properties.&lt;/p&gt;
10782 </description>
10783 </item>
10784
10785 <item>
10786 <title>Standardize on protocols and formats, not vendors and applications</title>
10787 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
10788 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
10789 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
10790 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
10791 very good one to form a long lived computer infrastructure. It is the
10792 simple one, lost by many in todays computer industry: Standardize on
10793 open network protocols and open exchange/storage formats, not applications.
10794 Applications come and go, while protocols and files tend to stay, and
10795 thus one want to make it easy to change application and vendor, while
10796 avoiding conversion costs and locking users to a specific platform or
10797 application.&lt;/p&gt;
10798
10799 &lt;p&gt;This approach make it possible to replace the client applications
10800 independently of the server applications. One can even allow users to
10801 use several different applications as long as they handle the selected
10802 protocol and format. In the normal case, only one client application
10803 is recommended and users only get help if they choose to use this
10804 application, but those that want to deviate from the easy path are not
10805 blocked from doing so.&lt;/p&gt;
10806
10807 &lt;p&gt;It also allow us to replace the server side without forcing the
10808 users to replace their applications, and thus allow us to select the
10809 best server implementation at any moment, when scale and resouce
10810 requirements change.&lt;/p&gt;
10811
10812 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
10813 open formats, but I would never recommend standardizing on a single
10814 application that do not use open network protocol or open formats.&lt;/p&gt;
10815 </description>
10816 </item>
10817
10818 <item>
10819 <title>Returning from Skolelinux developer gathering</title>
10820 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
10821 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
10822 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
10823 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
10824 Edu/Skolelinux development gathering. I got a bit done tuning the
10825 desktop, and looked into the dynamic service location protocol
10826 implementation avahi. It look like it could be useful for us. Almost
10827 30 people participated, and I believe it was a great environment to
10828 get to know the Skolelinux system. Walter Bender, involved in the
10829 development of the Sugar educational platform, presented his stuff and
10830 also helped me improve my OLPC installation. He also showed me that
10831 his Turtle Art application can be used in standalone mode, and we
10832 agreed that I would help getting it packaged for Debian. As a
10833 standalone application it would be great for Debian Edu. We also
10834 tried to get the video conferencing working with two OLPCs, but that
10835 proved to be too hard for us. The application seem to need more work
10836 before it is ready for me. I look forward to getting home and relax
10837 now. :)&lt;/p&gt;
10838 </description>
10839 </item>
10840
10841 <item>
10842 <title>Time for new LDAP schemas replacing RFC 2307?</title>
10843 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
10844 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
10845 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
10846 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
10847 optimal. There is RFC 2307 documenting one way to store NIS maps in
10848 LDAP, and a modified version of this normally called RFC 2307bis, with
10849 some modifications to be compatible with Active Directory. The RFC
10850 specification handle the content of a lot of system databases, but do
10851 not handle DNS zones and DHCP configuration.&lt;/p&gt;
10852
10853 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
10854 we would like to store information about users, SMB clients/hosts,
10855 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10856 and LTSP configuration in LDAP. These objects have a lot in common,
10857 but with the current LDAP schemas it is not possible to have one
10858 object per entity. For example, one need to have at least three LDAP
10859 objects for a given computer, one with the SMB related stuff, one with
10860 DNS information and another with DHCP information. The schemas
10861 provided for DNS and DHCP are impossible to combine into one LDAP
10862 object. In addition, it is impossible to implement quick queries for
10863 netgroup membership, because of the way NIS triples are implemented.
10864 It just do not scale. I believe it is time for a few RFC
10865 specifications to cleam up this mess.&lt;/p&gt;
10866
10867 &lt;p&gt;I would like to have one LDAP object representing each computer in
10868 the network, and this object can then keep the SMB (ie host key), DHCP
10869 (mac address/name) and DNS (name/IP address) settings in one place.
10870 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
10871
10872 &lt;p&gt;I would also like to have a quick way to map from a user or
10873 computer and to the net group this user or computer is a member.&lt;/p&gt;
10874
10875 &lt;p&gt;Active Directory have done a better job than unix heads like myself
10876 in this regard, and the unix side need to catch up. Time to start a
10877 new IETF work group?&lt;/p&gt;
10878 </description>
10879 </item>
10880
10881 <item>
10882 <title>Endelig er Debian Lenny gitt ut</title>
10883 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
10884 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
10885 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
10886 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
10887 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
10888 Et langt steg videre for Debian-prosjektet, og en rekke nye
10889 programpakker blir nå tilgjengelig for de av oss som bruker den
10890 stabile utgaven av Debian. Neste steg er nå å få
10891 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
10892 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
10893 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10894 slippes løs på skolene. Takk til alle debian-utviklerne som har
10895 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10896 bootsekvens tilgjengelig i stabil utgave, vha pakken
10897 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
10898 </description>
10899 </item>
10900
10901 <item>
10902 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
10903 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
10904 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
10905 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
10906 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
10907 Oslo. Most of Saturday was used for the general assemly for the
10908 member organization, but the rest of the weekend I used to tune the
10909 LTSP installation. LTSP now work out of the box on the 10-network.
10910 Acer Aspire One proved to be a very nice thin client, with both
10911 screen, mouse and keybard in a small box. Was working on getting the
10912 diskless workstation setup configured out of the box, but did not
10913 finish it before the weekend was up.&lt;/p&gt;
10914
10915 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
10916 the Brazilian group, so that will have to wait for the next
10917 development gathering. Would love to have the Debian Edu installer
10918 automatically detect and configure a multiseat setup when it find one
10919 of these cards.&lt;/p&gt;
10920 </description>
10921 </item>
10922
10923 <item>
10924 <title>The sorry state of multimedia browser plugins in Debian</title>
10925 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
10926 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
10927 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
10928 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
10929 plugins available in Debian Lenny, to see which one we should use by
10930 default in Debian Edu. We need an embedded video playing plugin with
10931 control buttons to pause or stop the video, and capable of streaming
10932 all the multimedia content available on the web. The test results and
10933 notes are available on
10934 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
10935 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
10936 fill this need. My personal video player favorite, VLC, has a really
10937 bad plugin which fail on a lot of the test pages. A lot of the MIME
10938 types I would expect to work with any free software player (like
10939 video/ogg), just do not work. And simple formats like the
10940 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
10941 totem and vlc plugins. I hope the situation will improve soon. No
10942 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
10943
10944 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
10945 be the only one fitting our needs. :/&lt;/p&gt;
10946 </description>
10947 </item>
10948
10949 </channel>
10950 </rss>