]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
ac9012bcfd79d9d0ef42634cefe129aa61e74d2b
[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>https://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>New chrpath release 0.17</title>
11 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_17.html</link>
12 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_17.html</guid>
13 <pubDate>Fri, 10 Nov 2023 07:30:00 +0100</pubDate>
14 <description>&lt;p&gt;The chrpath package provide a simple command line tool to remove or
15 modify the rpath or runpath of compiled ELF program. It is almost 10
16 years since I updated the code base, but I stumbled over the tool
17 today, and decided it was time to move the code base from Subversion
18 to git and find a new home for it, as the previous one (Debian Alioth)
19 has been shut down. I decided to go with
20 &lt;a href=&quot;https://codeberg.org/&quot;&gt;Codeberg&lt;/a&gt; this time, as it is my git
21 service of choice these days, did a quick and dirty migration to git
22 and updated the code with a few patches I found in the Debian bug
23 tracker. These are the release notes:&lt;/p&gt;
24
25 &lt;p&gt;New in 0.17 released 2023-11-10:&lt;/p&gt;
26
27 &lt;ul&gt;
28 &lt;li&gt;Moved project to Codeberg, as Alioth is shut down.&lt;/li&gt;
29 &lt;li&gt;Add Solaris support (use &amp;lt;sys/byteorder.h&gt; instead of &amp;lt;byteswap.h&gt;).
30 Patch from Rainer Orth.&lt;/li&gt;
31 &lt;li&gt;Added missing newline from printf() line. Patch from Frank Dana.&lt;/li&gt;
32 &lt;li&gt;Corrected handling of multiple ELF sections. Patch from Frank Dana.&lt;/li&gt;
33 &lt;li&gt;Updated build rules for .deb. Partly based on patch from djcj.&lt;/li&gt;
34 &lt;/ul&gt;
35
36 &lt;p&gt;The latest edition is tagged and available from
37 &lt;a href=&quot;https://codeberg.org/pere/chrpath&quot;&gt;https://codeberg.org/pere/chrpath&lt;/a&gt;.
38
39 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
40 activities, please send Bitcoin donations to my address
41 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
42 </description>
43 </item>
44
45 <item>
46 <title>Test framework for DocBook processors / formatters</title>
47 <link>https://people.skolelinux.org/pere/blog/Test_framework_for_DocBook_processors___formatters.html</link>
48 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Test_framework_for_DocBook_processors___formatters.html</guid>
49 <pubDate>Sun, 5 Nov 2023 13:00:00 +0100</pubDate>
50 <description>&lt;p&gt;All the books I have published so far has been using
51 &lt;a href=&quot;https://docbook.org/&quot;&gt;DocBook&lt;/a&gt; somewhere in the process.
52 For the first book, the source format was DocBook, while for every
53 later book it was an intermediate format used as the stepping stone to
54 be able to present the same manuscript in several formats, on paper,
55 as ebook in ePub format, as a HTML page and as a PDF file either for
56 paper production or for Internet consumption. This is made possible
57 with a wide variety of free software tools with DocBook support in
58 Debian. The source format of later books have been docx via rst,
59 Markdown, Filemaker and Asciidoc, and for all of these I was able to
60 generate a suitable DocBook file for further processing using
61 &lt;a href=&quot;https://tracker.debian.org/pkg/pandoc&quot;&gt;pandoc&lt;/a&gt;,
62 &lt;a href=&quot;https://tracker.debian.org/pkg/asciidoc&quot;&gt;a2x&lt;/a&gt; and
63 &lt;a href=&quot;https://tracker.debian.org/pkg/asciidoctor&quot;&gt;asciidoctor&lt;/a&gt;,
64 as well as rendering using
65 &lt;a href=&quot;https://tracker.debian.org/pkg/xmlto&quot;&gt;xmlto&lt;/a&gt;,
66 &lt;a href=&quot;https://tracker.debian.org/pkg/dbtoepub&quot;&gt;dbtoepub&lt;/a&gt;,
67 &lt;a href=&quot;https://tracker.debian.org/pkg/dblatex&quot;&gt;dblatex&lt;/a&gt;,
68 &lt;a href=&quot;https://tracker.debian.org/pkg/docbook-xsl&quot;&gt;docbook-xsl&lt;/a&gt; and
69 &lt;a href=&quot;https://tracker.debian.org/pkg/fop&quot;&gt;fop&lt;/a&gt;.&lt;/p&gt;
70
71 &lt;p&gt;Most of the &lt;a href=&quot;http://www.hungry.com/~pere/publisher/&quot;&gt;books I
72 have published&lt;/a&gt; are translated books, with English as the source
73 language. The use of
74 &lt;a href=&quot;https://tracker.debian.org/pkg/po4a&quot;&gt;po4a&lt;/a&gt; to
75 handle translations using the gettext PO format has been a blessing,
76 but publishing translated books had triggered the need to ensure the
77 DocBook tools handle relevant languages correctly. For every new
78 language I have published, I had to submit patches dblatex, dbtoepub
79 and docbook-xsl fixing incorrect language and country specific issues
80 in the framework themselves. Typically this has been missing keywords
81 like &#39;figure&#39; or sort ordering of index entries. After a while it
82 became tiresome to only discover issues like this by accident, and I
83 decided to write a DocBook &quot;test framework&quot; exercising various
84 features of DocBook and allowing me to see all features exercised for
85 a given language. It consist of a set of DocBook files, a version 4
86 book, a version 5 book, a v4 book set, a v4 selection of problematic
87 tables, one v4 testing sidefloat and finally one v4 testing a book of
88 articles. The DocBook files are accompanied with a set of build rules
89 for building PDF using dblatex and docbook-xsl/fop, HTML using xmlto
90 or docbook-xsl and epub using dbtoepub. The result is a set of files
91 visualizing footnotes, indexes, table of content list, figures,
92 formulas and other DocBook features, allowing for a quick review on
93 the completeness of the given locale settings. To build with a
94 different language setting, all one need to do is edit the lang= value
95 in the .xml file to pick a different ISO 639 code value and run
96 &#39;make&#39;.&lt;/p&gt;
97
98 &lt;p&gt;The &lt;a href=&quot;https://codeberg.org/pere/docbook-example/&quot;&gt;test framework
99 source code&lt;/a&gt; is available from Codeberg, and a generated set of
100 presentations of the various examples is available as Codeberg static
101 web pages at
102 &lt;a href=&quot;https://pere.codeberg.page/docbook-example/&quot;&gt;https://pere.codeberg.page/docbook-example/&lt;/a&gt;.
103 Using this test framework I have been able to discover and report
104 several bugs and missing features in various tools, and got a lot of
105 them fixed. For example I got Northern Sami keywords added to both
106 docbook-xsl and dblatex, fixed several typos in Norwegian bokmål and
107 Norwegian Nynorsk, support for non-ascii title IDs added to pandoc,
108 Norwegian index sorting support fixed in xindy and initial Norwegian
109 Bokmål support added to dblatex. Some issues still remains, though.
110 Default index sorting rules are still broken in several tools, so the
111 Norwegian letters æ, ø and å are more often than not sorted properly
112 in the book index.&lt;/p&gt;
113
114 &lt;p&gt;The test framework recently received some more polish, as part of
115 publishing my latest book. This book contained a lot of fairly
116 complex tables, which exposed bugs in some of the tools. This made me
117 add a new test file with various tables, as well as spend some time to
118 brush up the build rules. My goal is for the test framework to
119 exercise all DocBook features to make it easier to see which features
120 work with different processors, and hopefully get them all to support
121 the full set of DocBook features. Feel free to send patches to extend
122 the test set, and test it with your favorite DocBook processor.
123 Please visit these two URLs to learn more:&lt;/p&gt;
124
125 &lt;ul&gt;
126 &lt;li&gt;&lt;a href=&quot;https://codeberg.org/pere/docbook-example/&quot;&gt;https://codeberg.org/pere/docbook-example/&lt;/a&gt;&lt;/li&gt;
127 &lt;li&gt;&lt;a href=&quot;https://pere.codeberg.page/docbook-example/&quot;&gt;https://pere.codeberg.page/docbook-example/&lt;/a&gt;&lt;/li&gt;
128 &lt;/ul&gt;
129
130 &lt;p&gt;If you want to learn more on Docbook and translations, I recommend
131 having a look at the &lt;a href=&quot;https://docbook.org/&quot;&gt;the DocBook
132 web site&lt;/a&gt;,
133 &lt;a href=&quot;https://doccookbook.sourceforge.net/html/en/&quot;&gt;the DoCookBook
134 site&lt;a/&gt; and my earlier blog post on
135 &lt;a href=&quot;https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html&quot;&gt;how
136 the Skolelinux project process and translate documentation&lt;/a&gt;, a talk I gave earlier this year on
137 &lt;a href=&quot;https://www.nuug.no/aktiviteter/20230314-oversetting-og-publisering-av-b%c3%b8ker-med-fri-programvare/&quot;&gt;how
138 to translate and publish books using free software&lt;/a&gt; (Norwegian
139 only).&lt;/p&gt;
140
141 &lt;!--
142
143 https://github.com/docbook/xslt10-stylesheets/issues/205 (docbook-xsl: sme support)
144 https://bugs.debian.org/968437 (xindy: index sorting rules for nb/nn)
145 https://bugs.debian.org/856123 (pandoc: markdown to docbook with non-english titles)
146 https://bugs.debian.org/864813 (dblatex: missing nb words)
147 https://bugs.debian.org/756386 (dblatex: index sorting rules for nb/nn)
148 https://bugs.debian.org/796871 (dbtoepub: index sorting rules for nb/nn)
149 https://bugs.debian.org/792616 (dblatex: PDF metadata)
150 https://bugs.debian.org/686908 (docbook-xsl: index sorting rules for nb/nn)
151 https://sourceforge.net/tracker/?func=detail&amp;atid=373747&amp;aid=3556630&amp;group_id=21935 (docbook-xsl: nb/nn support)
152 https://bugs.debian.org/684391 (dblatex: initial nb support)
153
154 --&gt;
155
156 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
157 activities, please send Bitcoin donations to my address
158 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
159 </description>
160 </item>
161
162 <item>
163 <title>What did I learn from OpenSnitch this summer?</title>
164 <link>https://people.skolelinux.org/pere/blog/What_did_I_learn_from_OpenSnitch_this_summer_.html</link>
165 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_did_I_learn_from_OpenSnitch_this_summer_.html</guid>
166 <pubDate>Sun, 11 Jun 2023 08:30:00 +0200</pubDate>
167 <description>&lt;p&gt;With yesterdays
168 &lt;a href=&quot;https://www.debian.org/News/2023/20230610&quot;&gt;release of Debian
169 12 Bookworm&lt;/a&gt;, I am happy to know the
170 &lt;a href=&quot;https://tracker.debian.org/pkg/opensnitch&quot;&gt;the interactive
171 application firewall OpenSnitch&lt;/a&gt; is available for a wider audience.
172 I have been running it for a few weeks now, and have been surprised
173 about some of the programs connecting to the Internet. Some programs
174 are obviously calling out from my machine, like the NTP network based
175 clock adjusting system and Tor to reach other Tor clients, but others
176 were more dubious. For example, the KDE Window manager try to look up
177 the host name in DNS, for no apparent reason, but if this lookup is
178 blocked the KDE desktop get periodically stuck when I use it. Another
179 surprise was how much Firefox call home directly to mozilla.com,
180 mozilla.net and googleapis.com, to mention a few, when I visit other
181 web pages. This direct connection happen even if I told Firefox to
182 always use a proxy, and the proxy setting is ignored for this traffic.
183 Other surprising connections come from audacity and dirmngr (I do not
184 use Gnome). It took some trial and error to get a good default set of
185 permissions. Without it, I would get popups asking for permissions at
186 any time, also the most inconvenient ones where I am in the middle of
187 a time sensitive gaming session.&lt;/p&gt;
188
189 &lt;p&gt;I suspect some application developers should rethink when then need
190 to use network connections or DNS lookups, and recommend testing
191 OpenSnitch (only &lt;tt&gt;apt install opensnitch&lt;/tt&gt; away in Debian
192 Bookworm) to locate and report any surprising Internet connections on
193 your desktop machine.&lt;/p&gt;
194
195 &lt;p&gt;At the moment the upstream developer and Debian package maintainer
196 is working on making the system more reliable in Debian, by enabling
197 the eBPF kernel module to track processes and connections instead of
198 depending in content in /proc/. This should enter unstable fairly
199 soon.&lt;/p&gt;
200
201 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
202 activities, please send Bitcoin donations to my address
203 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
204
205 &lt;p&gt;&lt;strong&gt;Update 2023-06-12&lt;/strong&gt;: I got a tip about
206 &lt;a href=&quot;https://wiki.debian.org/PrivacyIssues&quot;&gt;a list of privacy
207 issues in Free Software&lt;/a&gt; and the
208 &lt;a href=&quot;irc://irc.debian.org/%23debian-privacy&quot;&gt;#debian-privacy IRC
209 channel&lt;/a&gt; discussing these topics.&lt;/p&gt;
210
211 </description>
212 </item>
213
214 <item>
215 <title>wmbusmeters, parse data from your utility meter - nice free software</title>
216 <link>https://people.skolelinux.org/pere/blog/wmbusmeters__parse_data_from_your_utility_meter___nice_free_software.html</link>
217 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/wmbusmeters__parse_data_from_your_utility_meter___nice_free_software.html</guid>
218 <pubDate>Fri, 19 May 2023 21:50:00 +0200</pubDate>
219 <description>&lt;p&gt;There is a European standard for reading utility meters like water,
220 gas, electricity or heat distribution meters. The
221 &lt;a href=&quot;https://en.wikipedia.org/wiki/Meter-Bus&quot;&gt;Meter-Bus standard
222 (EN 13757-2, EN 13757-3 and EN 137574)&lt;/a&gt; provide a cross vendor way
223 to talk to and collect meter data. I ran into this standard when I
224 wanted to monitor some heat distribution meters, and managed to find
225 free software that could do the job. The meters in question broadcast
226 encrypted messages with meter information via radio, and the hardest
227 part was to track down the encryption keys from the vendor. With this
228 in place I could set up a MQTT gateway to submit the meter data for
229 graphing.&lt;/p&gt;
230
231 &lt;p&gt;The free software systems in question,
232 &lt;a href=&quot;https://tracker.debian.org/pkg/rtl-wmbus&quot;&gt;rtl-wmbus&lt;/a&gt; to
233 read the messages from a software defined radio, and
234 &lt;a href=&quot;https://tracker.debian.org/pkg/wmbusmeters&quot;&gt;wmbusmeters&lt;/a&gt; to
235 decrypt and decode the content of the messages, is working very well
236 and allowe me to get frequent updates from my meters. I got in touch
237 with upstream last year to see if there was any interest in publishing
238 the packages via Debian. I was very happy to learn that Fredrik
239 Öhrström volunteered to maintain the packages, and I have since
240 assisted him in getting Debian package build rules in place as well as
241 sponsoring the packages into the Debian archive. Sadly we completed
242 it too late for them to become part of the next stable Debian release
243 (Bookworm). The wmbusmeters package just cleared the NEW queue. It
244 will need some work to fix a built problem, but I expect Fredrik will
245 find a solution soon.&lt;/p&gt;
246
247 &lt;p&gt;If you got a infrastructure meter supporting the Meter Bus
248 standard, I strongly recommend having a look at these nice
249 packages.&lt;/p&gt;
250
251 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
252 activities, please send Bitcoin donations to my address
253 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
254 </description>
255 </item>
256
257 <item>
258 <title>The 2023 LinuxCNC Norwegian developer gathering</title>
259 <link>https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html</link>
260 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html</guid>
261 <pubDate>Sun, 14 May 2023 20:30:00 +0200</pubDate>
262 <description>&lt;p&gt;The LinuxCNC project is making headway these days. A lot of
263 patches and issues have seen activity on
264 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/&quot;&gt;the project github
265 pages&lt;/a&gt; recently. A few weeks ago there was a developer gathering
266 over at the &lt;a href=&quot;https://tormach.com/&quot;&gt;Tormach&lt;/a&gt; headquarter in
267 Wisconsin, and now we are planning a new gathering in Norway. If you
268 wonder what LinuxCNC is, lets quote Wikipedia:&lt;/p&gt;
269
270 &lt;blockquote&gt;
271 &quot;LinuxCNC is a software system for numerical control of
272 machines such as milling machines, lathes, plasma cutters, routers,
273 cutting machines, robots and hexapods. It can control up to 9 axes or
274 joints of a CNC machine using G-code (RS-274NGC) as input. It has
275 several GUIs suited to specific kinds of usage (touch screen,
276 interactive development).&quot;
277 &lt;/blockquote&gt;
278
279 &lt;p&gt;The Norwegian developer gathering take place the weekend June 16th
280 to 18th this year, and is open for everyone interested in contributing
281 to LinuxCNC. Up to date information about the gathering can be found
282 in
283 &lt;a href=&quot;https://sourceforge.net/p/emc/mailman/emc-developers/thread/sa64jp06nob.fsf%40hjemme.reinholdtsen.name/#msg37837251&quot;&gt;the
284 developer mailing list thread&lt;/a&gt; where the gathering was announced.
285 Thanks to the good people at
286 &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;,
287 &lt;a href=&quot;https://www.redpill-linpro.com/&quot;&gt;Redpill-Linpro&lt;/a&gt; and
288 &lt;a href=&quot;https://www.nuugfoundation.no/no/&quot;&gt;NUUG Foundation&lt;/a&gt;, we
289 have enough sponsor funds to pay for food, and shelter for the people
290 traveling from afar to join us. If you would like to join the
291 gathering, get in touch.&lt;/p&gt;
292
293 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
294 activities, please send Bitcoin donations to my address
295 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
296 </description>
297 </item>
298
299 <item>
300 <title>OpenSnitch in Debian ready for prime time</title>
301 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html</link>
302 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html</guid>
303 <pubDate>Sat, 13 May 2023 12:10:00 +0200</pubDate>
304 <description>&lt;p&gt;A bit delayed,
305 &lt;a href=&quot;https://tracker.debian.org/pkg/opensnitch&quot;&gt;the interactive
306 application firewall OpenSnitch&lt;/a&gt; package in Debian now got the
307 latest fixes ready for Debian Bookworm. Because it depend on a
308 package missing on some architectures, the autopkgtest check of the
309 testing migration script did not understand that the tests were
310 actually working, so the migration was delayed. A bug in the package
311 dependencies is also fixed, so those installing the firewall package
312 (opensnitch) now also get the GUI admin tool (python3-opensnitch-ui)
313 installed by default. I am very grateful to Gustavo Iñiguez Goya for
314 his work on getting the package ready for Debian Bookworm.&lt;/p&gt;
315
316 &lt;p&gt;Armed with this package I have discovered some surprising
317 connections from programs I believed were able to work completly
318 offline, and it has already proven its worth, at least to me. If you
319 too want to get more familiar with the kind of programs using
320 Internett connections on your machine, I recommend testing &lt;tt&gt;apt
321 install opensnitch&lt;/tt&gt; in Bookworm and see what you think.&lt;/p&gt;
322
323 &lt;p&gt;The package is still not able to build its eBPF module within
324 Debian. Not sure how much work it would be to get it working, but
325 suspect some kernel related packages need to be extended with more
326 header files to get it working.&lt;/p&gt;
327
328 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
329 activities, please send Bitcoin donations to my address
330 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
331 </description>
332 </item>
333
334 <item>
335 <title>Speech to text, she APTly whispered, how hard can it be?</title>
336 <link>https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html</link>
337 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html</guid>
338 <pubDate>Sun, 23 Apr 2023 09:40:00 +0200</pubDate>
339 <description>&lt;p&gt;While visiting a convention during Easter, it occurred to me that
340 it would be great if I could have a digital Dictaphone with
341 transcribing capabilities, providing me with texts to cut-n-paste into
342 stuff I need to write. The background is that long drives often bring
343 up the urge to write on texts I am working on, which of course is out
344 of the question while driving. With the release of
345 &lt;a href=&quot;https://github.com/openai/whisper/&quot;&gt;OpenAI Whisper&lt;/a&gt;, this
346 seem to be within reach with Free Software, so I decided to give it a
347 go. OpenAI Whisper is a Linux based neural network system to read in
348 audio files and provide text representation of the speech in that
349 audio recording. It handle multiple languages and according to its
350 creators even can translate into a different language than the spoken
351 one. I have not tested the latter feature. It can either use the CPU
352 or a GPU with CUDA support. As far as I can tell, CUDA in practice
353 limit that feature to NVidia graphics cards. I have few of those, as
354 they do not work great with free software drivers, and have not tested
355 the GPU option. While looking into the matter, I did discover some
356 work to provide CUDA support on non-NVidia GPUs, and some work with
357 the library used by Whisper to port it to other GPUs, but have not
358 spent much time looking into GPU support yet. I&#39;ve so far used an old
359 X220 laptop as my test machine, and only transcribed using its
360 CPU.&lt;/p&gt;
361
362 &lt;p&gt;As it from a privacy standpoint is unthinkable to use computers
363 under control of someone else (aka a &quot;cloud&quot; service) to transcribe
364 ones thoughts and personal notes, I want to run the transcribing
365 system locally on my own computers. The only sensible approach to me
366 is to make the effort I put into this available for any Linux user and
367 to upload the needed packages into Debian. Looking at Debian Bookworm, I
368 discovered that only three packages were missing,
369 &lt;a href=&quot;https://bugs.debian.org/1034307&quot;&gt;tiktoken&lt;/a&gt;,
370 &lt;a href=&quot;https://bugs.debian.org/1034144&quot;&gt;triton&lt;/a&gt;, and
371 &lt;a href=&quot;https://bugs.debian.org/1034091&quot;&gt;openai-whisper&lt;/a&gt;. For a while
372 I also believed
373 &lt;a href=&quot;https://bugs.debian.org/1034286&quot;&gt;ffmpeg-python&lt;/a&gt; was
374 needed, but as its
375 &lt;a href=&quot;https://github.com/kkroening/ffmpeg-python/issues/760&quot;&gt;upstream
376 seem to have vanished&lt;/a&gt; I found it safer
377 &lt;a href=&quot;https://github.com/openai/whisper/pull/1242&quot;&gt;to rewrite
378 whisper&lt;/a&gt; to stop depending on in than to introduce ffmpeg-python
379 into Debian. I decided to place these packages under the umbrella of
380 &lt;a href=&quot;https://salsa.debian.org/deeplearning-team&quot;&gt;the Debian Deep
381 Learning Team&lt;/a&gt;, which seem like the best team to look after such
382 packages. Discussing the topic within the group also made me aware
383 that the triton package was already a future dependency of newer
384 versions of the torch package being planned, and would be needed after
385 Bookworm is released.&lt;/p&gt;
386
387 &lt;p&gt;All required code packages have been now waiting in
388 &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the Debian NEW
389 queue&lt;/a&gt; since Wednesday, heading for Debian Experimental until
390 Bookworm is released. An unsolved issue is how to handle the neural
391 network models used by Whisper. The default behaviour of Whisper is
392 to require Internet connectivity and download the model requested to
393 &lt;tt&gt;~/.cache/whisper/&lt;/tt&gt; on first invocation. This obviously would
394 fail &lt;a href=&quot;https://people.debian.org/~bap/dfsg-faq.html&quot;&gt;the
395 deserted island test of free software&lt;/a&gt; as the Debian packages would
396 be unusable for someone stranded with only the Debian archive and solar
397 powered computer on a deserted island.&lt;/p&gt;
398
399 &lt;p&gt;Because of this, I would love to include the models in the Debian
400 mirror system. This is problematic, as the models are very large
401 files, which would put a heavy strain on the Debian mirror
402 infrastructure around the globe. The strain would be even higher if
403 the models change often, which luckily as far as I can tell they do
404 not. The small model, which according to its creator is most useful
405 for English and in my experience is not doing a great job there
406 either, is 462 MiB (deb is 414 MiB). The medium model, which to me
407 seem to handle English speech fairly well is 1.5 GiB (deb is 1.3 GiB)
408 and the large model is 2.9 GiB (deb is 2.6 GiB). I would assume
409 everyone with enough resources would prefer to use the large model for
410 highest quality. I believe the models themselves would have to go
411 into the non-free part of the Debian archive, as they are not really
412 including any useful source code for updating the models. The
413 &quot;source&quot;, aka the model training set, according to the creators
414 consist of &quot;680,000 hours of multilingual and multitask supervised
415 data collected from the web&quot;, which to me reads material with both
416 unknown copyright terms, unavailable to the general public. In other
417 words, the source is not available according to the Debian Free
418 Software Guidelines and the model should be considered non-free.&lt;/p&gt;
419
420 &lt;p&gt;I asked the Debian FTP masters for advice regarding uploading a
421 model package on their IRC channel, and based on the feedback there it
422 is still unclear to me if such package would be accepted into the
423 archive. In any case I wrote build rules for a
424 &lt;a href=&quot;https://salsa.debian.org/deeplearning-team/openai-whisper-model&quot;&gt;OpenAI
425 Whisper model package&lt;/a&gt; and
426 &lt;a href=&quot;https://github.com/openai/whisper/pull/1257&quot;&gt;modified the
427 Whisper code base&lt;/a&gt; to prefer shared files under &lt;tt&gt;/usr/&lt;/tt&gt; and
428 &lt;tt&gt;/var/&lt;/tt&gt; over user specific files in &lt;tt&gt;~/.cache/whisper/&lt;/tt&gt;
429 to be able to use these model packages, to prepare for such
430 possibility. One solution might be to include only one of the models
431 (small or medium, I guess) in the Debian archive, and ask people to
432 download the others from the Internet. Not quite sure what to do
433 here, and advice is most welcome (use the debian-ai mailing list).&lt;/p&gt;
434
435 &lt;p&gt;To make it easier to test the new packages while I wait for them to
436 clear the NEW queue, I created an APT source targeting bookworm. I
437 selected Bookworm instead of Bullseye, even though I know the latter
438 would reach more users, is that some of the required dependencies are
439 missing from Bullseye and I during this phase of testing did not want
440 to backport a lot of packages just to get up and running.&lt;/p&gt;
441
442 &lt;p&gt;Here is a recipe to run as user root if you want to test OpenAI
443 Whisper using Debian packages on your Debian Bookworm installation,
444 first adding the APT repository GPG key to the list of trusted keys,
445 then setting up the APT repository and finally installing the packages
446 and one of the models:&lt;/p&gt;
447
448 &lt;p&gt;&lt;pre&gt;
449 curl https://geekbay.nuug.no/~pere/openai-whisper/D78F5C4796F353D211B119E28200D9B589641240.asc \
450 -o /etc/apt/trusted.gpg.d/pere-whisper.asc
451 mkdir -p /etc/apt/sources.list.d
452 cat &gt; /etc/apt/sources.list.d/pere-whisper.list &amp;lt;&amp;lt;EOF
453 deb https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
454 deb-src https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
455 EOF
456 apt update
457 apt install openai-whisper
458 &lt;/pre&gt;&lt;/p&gt;
459
460 &lt;p&gt;The package work for me, but have not yet been tested on any other
461 computer than my own. With it, I have been able to (badly) transcribe
462 a 2 minute 40 second Norwegian audio clip to test using the small
463 model. This took 11 minutes and around 2.2 GiB of RAM. Transcribing
464 the same file with the medium model gave a accurate text in 77 minutes
465 using around 5.2 GiB of RAM. My test machine had too little memory to
466 test the large model, which I believe require 11 GiB of RAM. In
467 short, this now work for me using Debian packages, and I hope it will
468 for you and everyone else once the packages enter Debian.&lt;/p&gt;
469
470 &lt;p&gt;Now I can start on the audio recording part of this project.&lt;/p&gt;
471
472 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
473 activities, please send Bitcoin donations to my address
474 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
475 </description>
476 </item>
477
478 <item>
479 <title>rtlsdr-scanner, software defined radio frequency scanner for Linux - nice free software</title>
480 <link>https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html</link>
481 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html</guid>
482 <pubDate>Fri, 7 Apr 2023 23:10:00 +0200</pubDate>
483 <description>&lt;p&gt;Today I finally found time to track down a useful radio frequency
484 scanner for my software defined radio. Just for fun I tried to locate
485 the radios used in the areas, and a good start would be to scan all
486 the frequencies to see what is in use. I&#39;ve tried to find a useful
487 program earlier, but ran out of time before I managed to find a useful
488 tool. This time I was more successful, and after a few false leads I
489 found a description of
490 &lt;a href=&quot;https://www.kali.org/tools/rtlsdr-scanner/&quot;&gt;rtlsdr-scanner
491 over at the Kali site&lt;/a&gt;, and was able to track down
492 &lt;a href=&quot;https://gitlab.com/kalilinux/packages/rtlsdr-scanner.git&quot;&gt;the
493 Kali package git repository&lt;/a&gt; to build a deb package for the
494 scanner. Sadly the package is missing from the Debian project itself,
495 at least in Debian Bullseye. Two runtime dependencies,
496 &lt;a href=&quot;https://gitlab.com/kalilinux/packages/python-visvis.git&quot;&gt;python-visvis&lt;/a&gt;
497 and
498 &lt;a href=&quot;https://gitlab.com/kalilinux/packages/python-rtlsdr.git&quot;&gt;python-rtlsdr&lt;/a&gt;
499 had to be built and installed separately. Luckily &#39;&lt;tt&gt;gbp
500 buildpackage&lt;/tt&gt;&#39; handled them just fine and no further packages had
501 to be manually built. The end result worked out of the box after
502 installation.&lt;/p&gt;
503
504 &lt;p&gt;My initial scans for FM channels worked just fine, so I knew the
505 scanner was functioning. But when I tried to scan every frequency
506 from 100 to 1000 MHz, the program stopped unexpectedly near the
507 completion. After some debugging I discovered USB software radio I
508 used rejected frequencies above 948 MHz, triggering a unreported
509 exception breaking the scan. Changing the scan to end at 957 worked
510 better. I similarly found the lower limit to be around 15, and ended
511 up with the following full scan:&lt;/p&gt;
512
513 &lt;p&gt;&lt;a href=&quot;https://people.skolelinux.org/pere/blog/images/2023-04-07-radio-freq-scanning.png&quot;&gt;&lt;img src=&quot;https://people.skolelinux.org/pere/blog/images/2023-04-07-radio-freq-scanning.png&quot; width=&quot;100%&quot;&gt;&lt;/a&gt;&lt;/p&gt;
514
515 &lt;p&gt;Saving the scan did not work, but exporting it as a CSV file worked
516 just fine. I ended up with around 477k CVS lines with dB level for
517 the given frequency.&lt;/p&gt;
518
519 &lt;p&gt;The save failure seem to be a missing UTF-8 encoding issue in the
520 python code. Will see if I can find time to send a patch
521 &lt;a href=&quot;https://github.com/CdeMills/RTLSDR-Scanner/&quot;&gt;upstream&lt;/a&gt;
522 later to fix this exception:&lt;/p&gt;
523
524 &lt;pre&gt;
525 Traceback (most recent call last):
526 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py&quot;, line 485, in __on_save
527 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
528 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py&quot;, line 408, in save_plot
529 handle.write(json.dumps(data, indent=4))
530 TypeError: a bytes-like object is required, not &#39;str&#39;
531 Traceback (most recent call last):
532 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py&quot;, line 485, in __on_save
533 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
534 File &quot;/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py&quot;, line 408, in save_plot
535 handle.write(json.dumps(data, indent=4))
536 TypeError: a bytes-like object is required, not &#39;str&#39;
537 &lt;/pre&gt;
538
539 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
540 activities, please send Bitcoin donations to my address
541 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
542 </description>
543 </item>
544
545 <item>
546 <title>OpenSnitch available in Debian Sid and Bookworm</title>
547 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html</link>
548 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html</guid>
549 <pubDate>Sat, 25 Feb 2023 20:30:00 +0100</pubDate>
550 <description>&lt;p&gt;Thanks to the efforts of the OpenSnitch lead developer Gustavo
551 Iñiguez Goya allowing me to sponsor the upload,
552 &lt;a href=&quot;https://tracker.debian.org/pkg/opensnitch&quot;&gt;the interactive
553 application firewall OpenSnitch&lt;/a&gt; is now available in Debian
554 Testing, soon to become the next stable release of Debian.&lt;/p&gt;
555
556 &lt;p&gt;This is a package which set up a network firewall on one or more
557 machines, which is controlled by a graphical user interface that will
558 ask the user if a program should be allowed to connect to the local
559 network or the Internet. If some background daemon is trying to dial
560 home, it can be blocked from doing so with a simple mouse click, or by
561 default simply by not doing anything when the GUI question dialog pop
562 up. A list of all programs discovered using the network is provided
563 in the GUI, giving the user an overview of how the machine(s) programs
564 use the network.&lt;/p&gt;
565
566 &lt;p&gt;OpenSnitch was uploaded for NEW processing about a month ago, and I
567 had little hope of it getting accepted and shaping up in time for the
568 package freeze, but the Debian ftpmasters proved to be amazingly quick
569 at checking out the package and it was accepted into the archive about
570 week after the first upload. It is now team maintained under the Go
571 language team umbrella. A few fixes to the default setup is only in
572 Sid, and should migrate to Testing/Bookworm in a week.&lt;/p&gt;
573
574 &lt;p&gt;During testing I ran into an
575 &lt;a href=&quot;https://github.com/evilsocket/opensnitch/issues/813&quot;&gt;issue
576 with Minecraft server broadcasts disappearing&lt;/a&gt;, which was quickly
577 resolved by the developer with a patch and a proposed configuration
578 change. I&#39;ve been told this was caused by the Debian packages default
579 use if /proc/ information to track down kernel status, instead of the
580 newer eBPF module that can be used. The reason is simply that
581 upstream and I have failed to find a way to build the eBPF modules for
582 OpenSnitch without a complete configured Linux kernel source tree,
583 which as far as we can tell is unavailable as a build dependency in
584 Debian. We tried unsuccessfully so far to use the kernel-headers
585 package. It would be great if someone could provide some clues how to
586 build eBPF modules on build daemons in Debian, possibly without the full
587 kernel source.&lt;/p&gt;
588
589 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
590 activities, please send Bitcoin donations to my address
591 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
592 </description>
593 </item>
594
595 <item>
596 <title>Is the desktop recommending your program for opening its files?</title>
597 <link>https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html</link>
598 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html</guid>
599 <pubDate>Sun, 29 Jan 2023 11:00:00 +0100</pubDate>
600 <description>&lt;p&gt;Linux desktop systems
601 &lt;a href=&quot;https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html&quot;&gt;have
602 standardized&lt;/a&gt; how programs present themselves to the desktop
603 system. If a package include a .desktop file in
604 /usr/share/applications/, Gnome, KDE, LXDE, Xfce and the other desktop
605 environments will pick up the file and use its content to generate the
606 menu of available programs in the system. A lesser known fact is that
607 a package can also explain to the desktop system how to recognize the
608 files created by the program in question, and use it to open these
609 files on request, for example via a GUI file browser.&lt;/p&gt;
610
611 &lt;p&gt;A while back I ran into a package that did not tell the desktop
612 system how to recognize its files and was not used to open its files
613 in the file browser and fixed it. In the process I wrote a simple
614 debian/tests/ script to ensure the setup keep working. It might be
615 useful for other packages too, to ensure any future version of the
616 package keep handling its own files.&lt;/p&gt;
617
618 &lt;p&gt;For this to work the file format need a useful MIME type that can
619 be used to identify the format. If the file format do not yet have a
620 MIME type, it should define one and preferably also
621 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;register
622 it with IANA&lt;/a&gt; to ensure the MIME type string is reserved.&lt;/p&gt;
623
624 &lt;p&gt;The script uses the &lt;tt&gt;xdg-mime&lt;/tt&gt; program from xdg-utils to
625 query the database of standardized package information and ensure it
626 return sensible values. It also need the location of an example file
627 for xdg-mime to guess the format of.&lt;/p&gt;
628
629 &lt;pre&gt;
630 #!/bin/sh
631 #
632 # Author: Petter Reinholdtsen
633 # License: GPL v2 or later at your choice.
634 #
635 # Validate the MIME setup, making sure motor types have
636 # application/vnd.openmotor+yaml associated with them and is connected
637 # to the openmotor desktop file.
638
639 retval=0
640
641 mimetype=&quot;application/vnd.openmotor+yaml&quot;
642 testfile=&quot;test/data/real/o3100/motor.ric&quot;
643 mydesktopfile=&quot;openmotor.desktop&quot;
644
645 filemime=&quot;$(xdg-mime query filetype &quot;$testfile&quot;)&quot;
646
647 if [ &quot;$mimetype&quot; != &quot;$filemime&quot; ] ; then
648 retval=1
649 echo &quot;error: xdg-mime claim motor file MIME type is $filemine, not $mimetype&quot;
650 else
651 echo &quot;success: xdg-mime report correct mime type $mimetype for motor file&quot;
652 fi
653
654 desktop=$(xdg-mime query default &quot;$mimetype&quot;)
655
656 if [ &quot;$mydesktopfile&quot; != &quot;$desktop&quot; ]; then
657 retval=1
658 echo &quot;error: xdg-mime claim motor file should be handled by $desktop, not $mydesktopfile&quot;
659 else
660 echo &quot;success: xdg-mime agree motor file should be handled by $mydesktopfile&quot;
661 fi
662
663 exit $retval
664 &lt;/pre&gt;
665
666 &lt;p&gt;It is a simple way to ensure your users are not very surprised when
667 they try to open one of your file formats in their file browser.&lt;/p&gt;
668
669 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
670 activities, please send Bitcoin donations to my address
671 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
672 </description>
673 </item>
674
675 <item>
676 <title>Opensnitch, the application level interactive firewall, heading into the Debian archive</title>
677 <link>https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html</link>
678 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html</guid>
679 <pubDate>Sun, 22 Jan 2023 23:55:00 +0100</pubDate>
680 <description>&lt;p&gt;While reading a
681 &lt;a href=&quot;https://sneak.berlin/20230115/macos-scans-your-local-files-now/&quot;&gt;blog
682 post claiming MacOS X recently started scanning local files and
683 reporting information about them to Apple&lt;/a&gt;, even on a machine where
684 all such callback features had been disabled, I came across a
685 description of the Little Snitch application for MacOS X. It seemed
686 like a very nice tool to have in the tool box, and I decided to see if
687 something similar was available for Linux.&lt;/p&gt;
688
689 &lt;p&gt;It did not take long to find
690 &lt;a href=&quot;https://github.com/evilsocket/opensnitch&quot;&gt;the OpenSnitch
691 package&lt;/a&gt;, which has been in development since 2017, and now is in
692 version 1.5.0. It has had a
693 &lt;a href=&quot;https://bugs.debian.org/909567&quot;&gt;request for Debian
694 packaging&lt;/a&gt; since 2018, but no-one completed the job so far. Just
695 for fun, I decided to see if I could help, and I was very happy to
696 discover that
697 &lt;a href=&quot;https://github.com/evilsocket/opensnitch/issues/304&quot;&gt;upstream
698 want a Debian package too&lt;/a&gt;.&lt;/p&gt;
699
700 &lt;p&gt;After struggling a bit with getting the program to run, figuring
701 out building Go programs (and a little failed detour to look at eBPF
702 builds too - help needed), I am very happy to report that I am
703 sponsoring upstream to maintain the package in Debian, and it has
704 since this morning been waiting in NEW for the ftpmasters to have a
705 look. Perhaps it can get into the archive in time for the Bookworm
706 release?&lt;/p&gt;
707
708 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
709 activities, please send Bitcoin donations to my address
710 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
711 </description>
712 </item>
713
714 <item>
715 <title>LinuxCNC MQTT publisher component</title>
716 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html</link>
717 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html</guid>
718 <pubDate>Sun, 8 Jan 2023 19:30:00 +0100</pubDate>
719 <description>&lt;p&gt;I watched &lt;a href=&quot;https://yewtu.be/watch?v=jmKUV3aNLjk&quot;&gt;a 2015
720 video from Andreas Schiffler&lt;/a&gt; the other day, where he set up
721 &lt;a href=&quot;https://linuxcnc.org/&quot;&gt;LinuxCNC&lt;/a&gt; to send status
722 information to the MQTT broker IBM Bluemix. As I also use MQTT for
723 graphing, it occured to me that a generic MQTT LinuxCNC component
724 would be useful and I set out to implement it. Today I got the first
725 draft limping along and submitted as
726 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/pull/2253&quot;&gt;a patch to the
727 LinuxCNC project&lt;/a&gt;.&lt;/p&gt;
728
729 &lt;p&gt;The simple part was setting up the MQTT publishing code in Python.
730 I already have set up other parts submitting data to my Mosquito MQTT
731 broker, so I could reuse that code. Writing a LinuxCNC component in
732 Python as new to me, but using existing examples in the code
733 repository and the extensive documentation, this was fairly straight
734 forward. The hardest part was creating a automated test for the
735 component to ensure it was working. Testing it in a simulated
736 LinuxCNC machine proved very useful, as I discovered features I needed
737 that I had not thought of yet, and adjusted the code quite a bit to
738 make it easier to test without a operational MQTT broker
739 available.&lt;/p&gt;
740
741 &lt;p&gt;The draft is ready and working, but I am unsure which LinuxCNC HAL
742 pins I should collect and publish by default (in other words, the
743 default set of information pieces published), and how to get the
744 machine name from the LinuxCNC INI file. The latter is a minor
745 detail, but I expect it would be useful in a setup with several
746 machines available. I am hoping for feedback from the experienced
747 LinuxCNC developers and users, to make the component even better
748 before it can go into the mainland LinuxCNC code base.&lt;/p&gt;
749
750 &lt;p&gt;Since I started on the MQTT component, I came across
751 &lt;a href=&quot;https://yewtu.be/watch?v=Bqa2grG0XtA&quot;&gt;another video from Kent
752 VanderVelden&lt;/a&gt; where he combine LinuxCNC with a set of screen glasses
753 controlled by a Raspberry Pi, and it occured to me that it would
754 be useful for such use cases if LinuxCNC also provided a REST API for
755 querying its status. I hope to start on such component once the MQTT
756 component is working well.&lt;/p&gt;
757
758 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
759 activities, please send Bitcoin donations to my address
760 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
761 </description>
762 </item>
763
764 <item>
765 <title>ONVIF IP camera management tool finally in Debian</title>
766 <link>https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html</link>
767 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html</guid>
768 <pubDate>Sat, 24 Dec 2022 08:00:00 +0100</pubDate>
769 <description>&lt;p&gt;Merry Christmas to you all. Here is a small gift to all those with
770 IP cameras following the &lt;a href=&quot;https://www.onvif.org/&quot;&gt;ONVIF
771 specification&lt;/a&gt;. There is finally a nice command line and GUI tool
772 in Debian to manage ONVIF IP cameras. After working with upstream for
773 a few months and sponsoring the upload, I am very happy to report that
774 the &lt;a href=&quot;https://tracker.debian.org/libonvif&quot;&gt;libonvif package&lt;/a&gt;
775 entered Debian Sid last night.&lt;/p&gt;
776
777 &lt;p&gt;The package provide a C library to communicate with such cameras, a
778 command line tool to locate and update settings of (like password) the
779 cameras and a GUI tool to configure and control the units as well as
780 preview the video from the camera. Libonvif is available on Both
781 Linux and Windows and the GUI tool uses the Qt library. The main
782 competitors are non-free software, while libonvif is GNU GPL licensed.
783 I am very glad Debian users in the future can control their cameras
784 using a free software system provided by Debian. But the ONVIF world
785 is full of slightly broken firmware, where the cameras pretend to
786 follow the ONVIF specification but fail to set some configuration
787 values or refuse to provide video to more than one recipient at the
788 time, and the onvif project is quite young and might take a while
789 before it completely work with your camera. Upstream seem eager to
790 improve the library, so handling any broken camera might be just &lt;a
791 href=&quot;https://github.com/sr99622/libonvif/&quot;&gt;a bug report away&lt;/a&gt;.&lt;/p&gt;
792
793 &lt;p&gt;The package just cleared NEW, and need a new source only upload
794 before it can enter testing. This will happen in the next few
795 days.&lt;/p&gt;
796
797 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
798 activities, please send Bitcoin donations to my address
799 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
800 </description>
801 </item>
802
803 <item>
804 <title>Managing and using ONVIF IP cameras with Linux</title>
805 <link>https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html</link>
806 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html</guid>
807 <pubDate>Wed, 19 Oct 2022 12:30:00 +0200</pubDate>
808 <description>&lt;p&gt;Recently I have been looking at how to control and collect data
809 from a handful IP cameras using Linux. I both wanted to change their
810 settings and to make their imagery available via a free software
811 service under my control. Here is a summary of the tools I found.&lt;/p&gt;
812
813 &lt;p&gt;First I had to identify the cameras and their protocols. As far as
814 I could tell, they were using some SOAP looking protocol and their
815 internal web server seem to only work with Microsoft Internet Explorer
816 with some proprietary binary plugin, which in these days of course is
817 a security disaster and also made it impossible for me to use the
818 camera web interface. Luckily I discovered that the SOAP looking
819 protocol is actually following &lt;a href=&quot;https://www.onvif.org/&quot;&gt;the
820 ONVIF specification&lt;/a&gt;, which seem to be supported by a lot of IP
821 cameras these days.&lt;/p&gt;
822
823 &lt;p&gt;Once the protocol was identified, I was able to find what appear to
824 be the most popular way to configure ONVIF cameras, the free software
825 Windows tool named
826 &lt;a href=&quot;https://sourceforge.net/projects/onvifdm/&quot;&gt;ONVIF Device
827 Manager&lt;/a&gt;. Lacking any other options at the time, I tried
828 unsuccessfully to get it running using Wine, but was missing a dotnet
829 40 library and I found no way around it to run it on Linux.&lt;/p&gt;
830
831 &lt;p&gt;The next tool I found to configure the cameras were a non-free Linux Qt
832 client &lt;a href=&quot;https://www.lingodigit.com/onvif_nvcdemo.html&quot;&gt;ONVIF
833 Device Tool&lt;/a&gt;. I did not like its terms of use, so did not spend
834 much time on it.&lt;/p&gt;
835
836 &lt;p&gt;To collect the video and make it available in a web interface, I
837 found the Zoneminder tool in Debian. A recent version was able to
838 automatically detect and configure ONVIF devices, so I could use it to
839 set up motion detection in and collection of the camera output. I had
840 initial problems getting the ONVIF autodetection to work, as both
841 Firefox and Chromium &lt;a href=&quot;https://bugs.debian.org/1001188&quot;&gt;refused
842 the inter-tab communication&lt;/a&gt; being used by the Zoneminder web
843 pages, but managed to get konqueror to work. Apparently the &quot;Enhanced
844 Tracking Protection&quot; in Firefox cause the problem. I ended up
845 upgrading to the Bookworm edition of Zoneminder in the process to try
846 to fix the issue, and believe the problem might be solved now.&lt;/p&gt;
847
848 &lt;p&gt;In the process I came across the nice Linux GUI tool
849 &lt;a href=&quot;https://gitlab.com/caspermeijn/onvifviewer/&quot;&gt;ONVIF Viewer&lt;/a&gt;
850 allowing me to preview the camera output and validate the login
851 passwords required. Sadly its author has grown tired of maintaining
852 the software, so it might not see any future updates. Which is sad,
853 as the viewer is sightly unstable and the picture tend to lock up.
854 Note, this lockup might be due to limitations in the cameras and not
855 the viewer implementation. I suspect the camera is only able to
856 provide pictures to one client at the time, and the Zoneminder feed
857 might interfere with the GUI viewer. I have
858 &lt;a href=&quot;https://bugs.debian.org/1000820&quot;&gt;asked for the tool to be
859 included in Debian&lt;/a&gt;.&lt;/p&gt;
860
861 &lt;p&gt;Finally, I found what appear to be very nice Linux free software
862 replacement for the Windows tool, named
863 &lt;a href=&quot;https://github.com/sr99622/libonvif/&quot;&gt;libonvif&lt;/a&gt;. It
864 provide a C library to talk to ONVIF devices as well as a command line
865 and GUI tool using the library. Using the GUI tool I was able to change
866 the admin passwords and update other settings of the cameras. I have
867 &lt;a href=&quot;https://bugs.debian.org/1021980&quot;&gt;asked for the package to be
868 included in Debian&lt;/a&gt;.&lt;/p&gt;
869
870 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
871 activities, please send Bitcoin donations to my address
872 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
873
874 &lt;p&gt;&lt;strong&gt;Update 2022-10-20&lt;/strong&gt;: Since my initial publication of
875 this text, I got several suggestions for more free software Linux
876 tools. There is &lt;a href=&quot;https://github.com/quatanium/python-onvif&quot;&gt;a
877 ONVIF python library&lt;/a&gt; (already
878 &lt;a href=&quot;https://bugs.debian.org/824240&quot;&gt;requested into Debian&lt;/a&gt;) and
879 &lt;a href=&quot;https://github.com/FalkTannhaeuser/python-onvif-zeep&quot;&gt;a python 3
880 fork&lt;/a&gt; using a different SOAP dependency. There is also
881 &lt;a href=&quot;https://www.home-assistant.io/integrations/onvif/&quot;&gt;support for
882 ONVIF in Home Assistant&lt;/a&gt;, and there is an alternative to Zoneminder
883 called &lt;a href=&quot;https://www.shinobi.video/&quot;&gt;Shinobi&lt;/a&gt;. The latter
884 two are not included in Debian either. I have not tested any of these
885 so far.&lt;/p&gt;
886 </description>
887 </item>
888
889 <item>
890 <title>Time to translate the Bullseye edition of the Debian Administrator&#39;s Handbook</title>
891 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html</link>
892 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html</guid>
893 <pubDate>Mon, 12 Sep 2022 15:45:00 +0200</pubDate>
894 <description>&lt;p align=&quot;center&quot;&gt;&lt;img align=&quot;center&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2020-10-20-debian-handbook-nb-testprint.jpeg&quot; width=&quot;60%&quot;/&gt;&lt;/p&gt;
895
896 &lt;p&gt;(The picture is of the previous edition.)&lt;/p&gt;
897
898 &lt;p&gt;Almost two years after the previous Norwegian Bokmål translation of
899 the &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
900 Handbook&lt;/a&gt;&quot; was published, a new edition is finally being prepared. The
901 english text is updated, and it is time to start working on the
902 translations. Around 37 percent of the strings have been updated, one
903 way or another, and the translations starting from a complete Debian Buster
904 edition now need to bring their translation up from 63% to 100%. The
905 complete book is licensed using a Creative Commons license, and has
906 been published in several languages over the years. The translations
907 are done by volunteers to bring Linux in their native tongue. The
908 last time I checked, it complete text was available in English,
909 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
910 In addition, work has been started for Arabic (Morocco), Catalan,
911 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
912 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
913 Romanian, Russian, Swedish, Turkish and Vietnamese.&lt;/p&gt;
914
915 &lt;p&gt;The translation is conducted on
916 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
917 hosted weblate project page&lt;/a&gt;. Prospective translators are
918 recommeded to subscribe to
919 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
920 translators mailing list&lt;/a&gt; and should also check out
921 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
922 contributors&lt;/a&gt;.&lt;/p&gt;
923
924 &lt;p&gt;I am one of the Norwegian Bokmål translators of this book, and we
925 have just started. Your contribution is most welcome.&lt;/p&gt;
926
927 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
928 activities, please send Bitcoin donations to my address
929 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
930 </description>
931 </item>
932
933 <item>
934 <title>Automatic LinuxCNC servo PID tuning?</title>
935 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html</link>
936 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html</guid>
937 <pubDate>Sat, 16 Jul 2022 22:30:00 +0200</pubDate>
938 <description>&lt;p&gt;While working on a CNC with servo motors controlled by the
939 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt;
940 &lt;a href=&quot;https://en.wikipedia.org/wiki/PID_controller&quot;&gt;PID
941 controller&lt;/a&gt;, I recently had to learn how to tune the collection of values
942 that control such mathematical machinery that a PID controller is. It
943 proved to be a lot harder than I hoped, and I still have not succeeded
944 in getting the Z PID controller to successfully defy gravity, nor X
945 and Y to move accurately and reliably. But while climbing up this
946 rather steep learning curve, I discovered that some motor control
947 systems are able to tune their PID controllers. I got the impression
948 from the documentation that LinuxCNC were not. This proved to be not
949 true.&lt;/p&gt;
950
951 &lt;p&gt;The LinuxCNC
952 &lt;a href=&quot;http://linuxcnc.org/docs/html/man/man9/pid.9.html&quot;&gt;pid
953 component&lt;/a&gt; is the recommended PID controller to use. It uses eight
954 constants &lt;tt&gt;Pgain&lt;/tt&gt;, &lt;tt&gt;Igain&lt;/tt&gt;, &lt;tt&gt;Dgain&lt;/tt&gt;,
955 &lt;tt&gt;bias&lt;/tt&gt;, &lt;tt&gt;FF0&lt;/tt&gt;, &lt;tt&gt;FF1&lt;/tt&gt;, &lt;tt&gt;FF2&lt;/tt&gt; and
956 &lt;tt&gt;FF3&lt;/tt&gt; to calculate the output value based on current and wanted
957 state, and all of these need to have a sensible value for the
958 controller to behave properly. Note, there are even more values
959 involved, theser are just the most important ones. In my case I need
960 the X, Y and Z axes to follow the requested path with little error.
961 This has proved quite a challenge for someone who have never tuned a
962 PID controller before, but there is at least some help to be found.
963
964 &lt;p&gt;I discovered that included in LinuxCNC was this old PID component
965 at_pid claiming to have auto tuning capabilities. Sadly it had been
966 neglected since 2011, and could not be used as a plug in replacement
967 for the default pid component. One would have to rewriting the
968 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
969 to quickly test auto tuning to see if it did a better job than me at
970 figuring out good P, I and D values to use.&lt;/p&gt;
971
972 &lt;p&gt;I decided to have a look if the situation could be improved. This
973 involved trying to understand the code and history of the pid and
974 at_pid components. Apparently they had a common ancestor, as code
975 structure, comments and variable names were quite close to each other.
976 Sadly this was not reflected in the git history, making it hard to
977 figure out what really happened. My guess is that the author of
978 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/at_pid.c&quot;&gt;at_pid.c&lt;/a&gt;
979 took a version of
980 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c&quot;&gt;pid.c&lt;/a&gt;,
981 rewrote it to follow the structure he wished pid.c to have, then added
982 support for auto tuning and finally got it included into the LinuxCNC
983 repository. The restructuring and lack of early history made it
984 harder to figure out which part of the code were relevant to the auto
985 tuning, and which part of the code needed to be updated to work the
986 same way as the current pid.c implementation. I started by trying to
987 isolate relevant changes in pid.c, and applying them to at_pid.c. My
988 aim was to make sure the at_pid component could replace the pid
989 component with a simple change in the HAL setup loadrt line, without
990 having to &quot;rewire&quot; the rest of the HAL configuration. After a few
991 hours following this approach, I had learned quite a lot about the
992 code structure of both components, while concluding I was heading down
993 the wrong rabbit hole, and should get back to the surface and find a
994 different path.&lt;/p&gt;
995
996 &lt;p&gt;For the second attempt, I decided to throw away all the PID control
997 related part of the original at_pid.c, and instead isolate and lift
998 the auto tuning part of the code and inject it into a copy of pid.c.
999 This ensured compatibility with the current pid component, while
1000 adding auto tuning as a run time option. To make it easier to identify
1001 the relevant parts in the future, I wrapped all the auto tuning code
1002 with &#39;#ifdef AUTO_TUNER&#39;. The end result behave just like the current
1003 pid component by default, as that part of the code is identical. The
1004 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/pull/1820&quot;&gt;end result
1005 entered the LinuxCNC master branch&lt;/a&gt; a few days ago.&lt;/p&gt;
1006
1007 &lt;p&gt;To enable auto tuning, one need to set a few HAL pins in the PID
1008 component. The most important ones are &lt;tt&gt;tune-effort&lt;/tt&gt;,
1009 &lt;tt&gt;tune-mode&lt;/tt&gt; and &lt;tt&gt;tune-start&lt;/tt&gt;. But lets take a step
1010 back, and see what the auto tuning code will do. I do not know the
1011 mathematical foundation of the at_pid algorithm, but from observation
1012 I can tell that the algorithm will, when enabled, produce a square
1013 wave pattern centered around the &lt;tt&gt;bias&lt;/tt&gt; value on the output pin
1014 of the PID controller. This can be seen using the HAL Scope provided
1015 by LinuxCNC. In my case, this is translated into voltage (+-10V) sent
1016 to the motor controller, which in turn is translated into motor speed.
1017 So at_pid will ask the motor to move the axis back and forth. The
1018 number of cycles in the pattern is controlled by the
1019 &lt;tt&gt;tune-cycles&lt;/tt&gt; pin, and the extremes of the wave pattern is
1020 controlled by the &lt;tt&gt;tune-effort&lt;/tt&gt; pin. Of course, trying to
1021 change the direction of a physical object instantly (as in going
1022 directly from a positive voltage to the equivalent negative voltage)
1023 do not change velocity instantly, and it take some time for the object
1024 to slow down and move in the opposite direction. This result in a
1025 more smooth movement wave form, as the axis in question were vibrating
1026 back and forth. When the axis reached the target speed in the
1027 opposing direction, the auto tuner change direction again. After
1028 several of these changes, the average time delay between the &#39;peaks&#39;
1029 and &#39;valleys&#39; of this movement graph is then used to calculate
1030 proposed values for Pgain, Igain and Dgain, and insert them into the
1031 HAL model to use by the pid controller. The auto tuned settings are
1032 not great, but htye work a lot better than the values I had been able
1033 to cook up on my own, at least for the horizontal X and Y axis. But I
1034 had to use very small &lt;tt&gt;tune-effort&lt;tt&gt; values, as my motor
1035 controllers error out if the voltage change too quickly. I&#39;ve been
1036 less lucky with the Z axis, which is moving a heavy object up and
1037 down, and seem to confuse the algorithm. The Z axis movement became a
1038 lot better when I introduced a &lt;tt&gt;bias&lt;/tt&gt; value to counter the
1039 gravitational drag, but I will have to work a lot more on the Z axis
1040 PID values.&lt;/p&gt;
1041
1042 &lt;p&gt;Armed with this knowledge, it is time to look at how to do the
1043 tuning. Lets say the HAL configuration in question load the PID
1044 component for X, Y and Z like this:&lt;/p&gt;
1045
1046 &lt;blockquote&gt;&lt;pre&gt;
1047 loadrt pid names=pid.x,pid.y,pid.z
1048 &lt;/pre&gt;&lt;/blockquote&gt;
1049
1050 &lt;p&gt;Armed with the new and improved at_pid component, the new line will
1051 look like this:&lt;/p&gt;
1052
1053 &lt;blockquote&gt;&lt;pre&gt;
1054 loadrt at_pid names=pid.x,pid.y,pid.z
1055 &lt;/pre&gt;&lt;/blockquote&gt;
1056
1057 &lt;p&gt;The rest of the HAL setup can stay the same. This work because the
1058 components are referenced by name. If the component had used count=3
1059 instead, all use of pid.# had to be changed to at_pid.#.&lt;/p&gt;
1060
1061 &lt;p&gt;To start tuning the X axis, move the axis to the middle of its
1062 range, to make sure it do not hit anything when it start moving back
1063 and forth. Next, set the &lt;tt&gt;tune-effort&lt;/tt&gt; to a low number in the
1064 output range. I used 0.1 as my initial value. Next, assign 1 to the
1065 &lt;tt&gt;tune-mode&lt;/tt&gt; value. Note, this will disable the pid controlling
1066 part and feed 0 to the output pin, which in my case initially caused a
1067 lot of drift. In my case it proved to be a good idea with X and Y to
1068 tune the motor driver to make sure 0 voltage stopped the motor
1069 rotation. On the other hand, for the Z axis this proved to be a bad
1070 idea, so it will depend on your setup. It might help to set the
1071 &lt;tt&gt;bias&lt;/tt&gt; value to a output value that reduce or eliminate the
1072 axis drift. Finally, after setting &lt;tt&gt;tune-mode&lt;/tt&gt;, set
1073 &lt;tt&gt;tune-start&lt;/tt&gt; to 1 to activate the auto tuning. If all go well,
1074 your axis will vibrate for a few seconds and when it is done, new
1075 values for Pgain, Igain and Dgain will be active. To test them,
1076 change &lt;tt&gt;tune-mode&lt;/tt&gt; back to 0. Note that this might cause the
1077 machine to suddenly jerk as it bring the axis back to its commanded
1078 position, which it might have drifted away from during tuning. To
1079 summarize with some halcmd lines:&lt;/p&gt;
1080
1081 &lt;blockquote&gt;&lt;pre&gt;
1082 setp pid.x.tune-effort 0.1
1083 setp pid.x.tune-mode 1
1084 setp pid.x.tune-start 1
1085 # wait for the tuning to complete
1086 setp pid.x.tune-mode 0
1087 &lt;/pre&gt;&lt;/blockquote&gt;
1088
1089 &lt;p&gt;After doing this task quite a few times while trying to figure out
1090 how to properly tune the PID controllers on the machine in, I decided
1091 to figure out if this process could be automated, and wrote a script
1092 to do the entire tuning process from power on. The end result will
1093 ensure the machine is powered on and ready to run, home all axis if it
1094 is not already done, check that the extra tuning pins are available,
1095 move the axis to its mid point, run the auto tuning and re-enable the
1096 pid controller when it is done. It can be run several times. Check
1097 out the
1098 &lt;a href=&quot;https://github.com/SebKuzminsky/MazakVQC1540/blob/bon-dev/scripts/run-auto-pid-tuner&quot;&gt;run-auto-pid-tuner&lt;/a&gt;
1099 script on github if you want to learn how it is done.&lt;/p&gt;
1100
1101 &lt;p&gt;My hope is that this little adventure can inspire someone who know
1102 more about motor PID controller tuning can implement even better
1103 algorithms for automatic PID tuning in LinuxCNC, making life easier
1104 for both me and all the others that want to use LinuxCNC but lack the
1105 in depth knowledge needed to tune PID controllers well.&lt;/p&gt;
1106
1107 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1108 activities, please send Bitcoin donations to my address
1109 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1110 </description>
1111 </item>
1112
1113 <item>
1114 <title>LinuxCNC translators life just got a bit easier</title>
1115 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html</link>
1116 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html</guid>
1117 <pubDate>Fri, 3 Jun 2022 21:10:00 +0200</pubDate>
1118 <description>&lt;p&gt;Back in oktober last year, when I started looking at the
1119 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt; system, I
1120 proposed to change the documentation build system make life easier for
1121 translators. The original system consisted of independently written
1122 documentation files for each language, with no automated way to track
1123 changes done in other translations and no help for the translators to
1124 know how much was left to translated. By using
1125 &lt;a href=&quot;https://po4a.org/&quot;&gt;the po4a system&lt;/a&gt; to generate POT and PO
1126 files from the English documentation, this can be improved. A small
1127 team of LinuxCNC contributors got together and today our labour
1128 finally payed off. Since a few hours ago, it is now possible to
1129 translate &lt;a href=&quot;https://hosted.weblate.org/projects/linuxcnc/&quot;&gt;the
1130 LinuxCNC documentation on Weblate&lt;/a&gt;, alongside the program itself.&lt;/p&gt;
1131
1132 &lt;p&gt;The effort to migrate the documentation to use po4a has been both
1133 slow and frustrating. I am very happy we finally made it.&lt;/p&gt;
1134
1135 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1136 activities, please send Bitcoin donations to my address
1137 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1138 </description>
1139 </item>
1140
1141 <item>
1142 <title>geteltorito make CD firmware upgrades a breeze</title>
1143 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html</link>
1144 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html</guid>
1145 <pubDate>Wed, 20 Apr 2022 11:50:00 +0200</pubDate>
1146 <description>&lt;p&gt;Recently I wanted to upgrade the firmware of my thinkpad, and
1147 located the firmware download page from Lenovo (which annoyingly do
1148 not allow access via Tor, forcing me to hand them more personal
1149 information that I would like). The
1150 &lt;a href=&quot;https://support.lenovo.com/no/en/search?query=thinkpad firmware bios upgrade iso&amp;SearchType=Customer search&amp;searchLocation=Masthead&quot;&gt;download
1151 from Lenovo&lt;/a&gt; is a bootable ISO image, which is a bit of a problem
1152 when all I got available is a USB memory stick. I tried booting the
1153 ISO as a USB stick, but this did not work. But genisoimage came to
1154 the rescue.&lt;/p&gt;
1155
1156 &lt;P&gt;The geteltorito program in
1157 &lt;a href=&quot;http://tracker.debian.org/cdrkit&quot;&gt;the genisoimage binary
1158 package&lt;/a&gt; is able to convert the bootable ISO image to a bootable
1159 USB stick using a simple command line recipe, which I then can write
1160 to the most recently inserted USB stick:&lt;/p&gt;
1161
1162 &lt;blockquote&gt;&lt;pre&gt;
1163 geteltorito -o usbstick.img lenovo-firmware.iso
1164 sudo dd bs=10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -1)
1165 &lt;/pre&gt;&lt;/blockquote&gt;
1166
1167 &lt;p&gt;This USB stick booted the firmware upgrader just fine, and in a few
1168 minutes my machine had the latest and greatest BIOS firmware in place.&lt;/p&gt;
1169 </description>
1170 </item>
1171
1172 <item>
1173 <title>Run your industrial metal working machine using Debian?</title>
1174 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html</link>
1175 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html</guid>
1176 <pubDate>Wed, 2 Mar 2022 18:40:00 +0100</pubDate>
1177 <description>&lt;p&gt;After many months of hard work by the good people involved in
1178 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt;, the
1179 system was accepted Sunday
1180 &lt;a href=&quot;https://tracker.debian.org/pkg/linuxcnc&quot;&gt;into Debian&lt;/a&gt;.
1181 Once it was available from Debian, I was surprised to discover from
1182 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=linuxcnc&quot;&gt;its
1183 popularity-contest numbers&lt;/a&gt; that people have been reporting its use
1184 since 2012. &lt;a href=&quot;http://linuxcnc.org/&quot;&gt;Its project site&lt;/a&gt; might
1185 be a good place to check out, but sadly is not working when visiting
1186 via Tor.&lt;/p&gt;
1187
1188 &lt;p&gt;But what is LinuxCNC, you are probably wondering? Perhaps a
1189 Wikipedia quote is in place?&lt;/p&gt;
1190
1191 &lt;blockquote&gt;
1192 &quot;LinuxCNC is a software system for numerical control of
1193 machines such as milling machines, lathes, plasma cutters, routers,
1194 cutting machines, robots and hexapods. It can control up to 9 axes or
1195 joints of a CNC machine using G-code (RS-274NGC) as input. It has
1196 several GUIs suited to specific kinds of usage (touch screen,
1197 interactive development).&quot;
1198 &lt;/blockquote&gt;
1199
1200 &lt;p&gt;It can even control 3D printers. And even though the Wikipedia
1201 page indicate that it can only work with hard real time kernel
1202 features, it can also work with the user space soft real time features
1203 provided by the Debian kernel.
1204 &lt;a href=&quot;https://github.com/linuxcnc/linuxcnc&quot;&gt;The source code&lt;/a&gt; is
1205 available from Github. The last few months I&#39;ve been involved in the
1206 translation setup for the program and documentation. Translators are
1207 most welcome to
1208 &lt;a href=&quot;https://hosted.weblate.org/engage/linuxcnc/&quot;&gt;join the
1209 effort&lt;/a&gt; using Weblate.&lt;/p&gt;
1210
1211 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1212 activities, please send Bitcoin donations to my address
1213 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1214 </description>
1215 </item>
1216
1217 <item>
1218 <title>Debian still an excellent choice for Lego builders</title>
1219 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</link>
1220 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</guid>
1221 <pubDate>Sun, 24 Oct 2021 07:10:00 +0200</pubDate>
1222 <description>&lt;p&gt;The Debian Lego team saw a lot of activity the last few weeks. All
1223 the packages under the team umbrella has been updated to fix
1224 packaging, lintian issues and BTS reports. In addition, a new and
1225 inspiring team member appeared on both the
1226 &lt;a href=&quot;https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team&quot;&gt;debian-lego-team
1227 Team mailing list&lt;/a&gt; and
1228 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC channel
1229 #debian-lego&lt;/a&gt;. If you are interested in Lego CAD design and LEGO
1230 Mindstorms programming, check out the
1231 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;team wiki page&lt;/a&gt; to
1232 see what Debian can offer the Lego enthusiast.&lt;/p&gt;
1233
1234 &lt;p&gt;Patches has been sent upstream, causing new upstream releases, one
1235 even the first one in more than ten years, and old upstreams was
1236 released with new ones. There are still a lot of work left, and the
1237 team welcome more members to help us make sure Debian is the Linux
1238 distribution of choice for Lego builders. If you want to contribute,
1239 join us in the IRC channel and become part of
1240 &lt;a href=&quot;https://salsa.debian.org/debian-lego-team/&quot;&gt;the team on
1241 Salsa&lt;/a&gt;.&lt;/p&gt;
1242
1243 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1244 activities, please send Bitcoin donations to my address
1245 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1246 </description>
1247 </item>
1248
1249 <item>
1250 <title>Six complete translations of The Debian Administrator&#39;s Handbook for Buster</title>
1251 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</link>
1252 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</guid>
1253 <pubDate>Mon, 5 Jul 2021 19:20:00 +0200</pubDate>
1254 <description>&lt;p&gt;I am happy observe that the &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The
1255 Debian Administrator&#39;s Handbook&lt;/a&gt; is available in six languages now.
1256 I am not sure which one of these are completely proof read, but the
1257 complete book is available in these languages:
1258
1259 &lt;ul&gt;
1260
1261 &lt;li&gt;English&lt;/li&gt;
1262 &lt;li&gt;Norwegian Bokmål&lt;/li&gt;
1263 &lt;li&gt;German&lt;/li&gt;
1264 &lt;li&gt;Indonesian&lt;/li&gt;
1265 &lt;li&gt;Brazil Portuguese&lt;/li&gt;
1266 &lt;li&gt;Spanish&lt;/li&gt;
1267
1268 &lt;/ul&gt;
1269
1270 &lt;p&gt;This is the list of languages more than 70% complete, in other
1271 words with not too much left to do:&lt;/p&gt;
1272
1273 &lt;ul&gt;
1274
1275 &lt;li&gt;Chinese (Simplified) - 90%&lt;/li&gt;
1276 &lt;li&gt;French - 79%&lt;/li&gt;
1277 &lt;li&gt;Italian - 79%&lt;/li&gt;
1278 &lt;li&gt;Japanese - 77%&lt;/li&gt;
1279 &lt;li&gt;Arabic (Morocco) - 75%&lt;/li&gt;
1280 &lt;li&gt;Persian - 71%&lt;/li&gt;
1281
1282 &lt;/ul&gt;
1283
1284 &lt;p&gt;I wonder how long it will take to bring these to 100%.&lt;/p&gt;
1285
1286 &lt;p&gt;Then there is the list of languages about halfway done:&lt;/p&gt;
1287
1288 &lt;ul&gt;
1289
1290 &lt;li&gt;Russian - 63%&lt;/li&gt;
1291 &lt;li&gt;Swedish - 53%&lt;/li&gt;
1292 &lt;li&gt;Chinese (Traditional) - 46%&lt;/li&gt;
1293 &lt;li&gt;Catalan - 45%&lt;/li&gt;
1294
1295 &lt;/ul&gt;
1296
1297 &lt;p&gt;Several are on to a good start:&lt;/p&gt;
1298
1299 &lt;ul&gt;
1300
1301 &lt;li&gt;Dutch - 26%&lt;/li&gt;
1302 &lt;li&gt;Vietnamese - 25%&lt;/li&gt;
1303 &lt;li&gt;Polish - 23%&lt;/li&gt;
1304 &lt;li&gt;Czech - 22%&lt;/li&gt;
1305 &lt;li&gt;Turkish - 18%&lt;/li&gt;
1306
1307 &lt;/ul&gt;
1308
1309 &lt;p&gt;Finally, there are the ones just getting started:&lt;/p&gt;
1310
1311 &lt;ul&gt;
1312
1313 &lt;li&gt;Korean - 4%&lt;/li&gt;
1314 &lt;li&gt;Croatian - 2%&lt;/li&gt;
1315 &lt;li&gt;Greek - 2%&lt;/li&gt;
1316 &lt;li&gt;Danish - 1%&lt;/li&gt;
1317 &lt;li&gt;Romanian - 1%&lt;/li&gt;
1318
1319 &lt;/ul&gt;
1320
1321 &lt;p&gt;If you want to help provide a Debian instruction book in your own
1322 language, visit
1323 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/#languages&quot;&gt;Weblate&lt;/a&gt;
1324 to contribute to the translations.&lt;/p&gt;
1325
1326 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1327 activities, please send Bitcoin donations to my address
1328 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1329 </description>
1330 </item>
1331
1332 <item>
1333 <title>Latest Jami back in Debian Testing, and scriptable using dbus</title>
1334 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</link>
1335 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</guid>
1336 <pubDate>Tue, 12 Jan 2021 17:00:00 +0100</pubDate>
1337 <description>&lt;p&gt;After a lot of hard work by its maintainer Alexandre Viau and
1338 others, the decentralized communication platform
1339 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;
1340 (earlier known as Ring), managed to get
1341 &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;its latest version&lt;/a&gt;
1342 into Debian Testing. Several of its dependencies has caused build and
1343 propagation problems, which all seem to be solved now.&lt;/p&gt;
1344
1345 &lt;p&gt;In addition to the fact that Jami is decentralized, similar to how
1346 bittorrent is decentralized, I first of all like how it is not
1347 connected to external IDs like phone numbers. This allow me to set up
1348 computers to send me notifications using Jami without having to find
1349 get a phone number for each computer. Automatic notification via Jami
1350 is also made trivial thanks to the provided client side API (as a DBus
1351 service). Here is my bourne shell script demonstrating how to let any
1352 system send a message to any Jami address. It will create a new
1353 identity before sending the message, if no Jami identity exist
1354 already:&lt;/p&gt;
1355
1356 &lt;p&gt;&lt;pre&gt;
1357 #!/bin/sh
1358 #
1359 # Usage: $0 &lt;jami-address&gt; &lt;message&gt;
1360 #
1361 # Send &lt;message&gt; to &lt;jami-address&gt;, create local jami account if
1362 # missing.
1363 #
1364 # License: GPL v2 or later at your choice
1365 # Author: Petter Reinholdtsen
1366
1367
1368 if [ -z &quot;$HOME&quot; ] ; then
1369 echo &quot;error: missing \$HOME, required for dbus to work&quot;
1370 exit 1
1371 fi
1372
1373 # First, get dbus running if not already running
1374 DBUSLAUNCH=/usr/bin/dbus-launch
1375 PIDFILE=/run/asterisk/dbus-session.pid
1376 if [ -e $PIDFILE ] ; then
1377 . $PIDFILE
1378 if ! kill -0 $DBUS_SESSION_BUS_PID 2&gt;/dev/null ; then
1379 unset DBUS_SESSION_BUS_ADDRESS
1380 fi
1381 fi
1382 if [ -z &quot;$DBUS_SESSION_BUS_ADDRESS&quot; ] &amp;&amp; [ -x &quot;$DBUSLAUNCH&quot; ]; then
1383 DBUS_SESSION_BUS_ADDRESS=&quot;unix:path=$HOME/.dbus&quot;
1384 dbus-daemon --session --address=&quot;$DBUS_SESSION_BUS_ADDRESS&quot; --nofork --nopidfile --syslog-only &lt; /dev/null &gt; /dev/null 2&gt;&amp;1 3&gt;&amp;1 &amp;
1385 DBUS_SESSION_BUS_PID=$!
1386 (
1387 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
1388 echo DBUS_SESSION_BUS_ADDRESS=\&quot;&quot;$DBUS_SESSION_BUS_ADDRESS&quot;\&quot;
1389 echo export DBUS_SESSION_BUS_ADDRESS
1390 ) &gt; $PIDFILE
1391 . $PIDFILE
1392 fi &amp;
1393
1394 dringop() {
1395 part=&quot;$1&quot;; shift
1396 op=&quot;$1&quot;; shift
1397 dbus-send --session \
1398 --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
1399 }
1400
1401 dringopreply() {
1402 part=&quot;$1&quot;; shift
1403 op=&quot;$1&quot;; shift
1404 dbus-send --session --print-reply \
1405 --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
1406 }
1407
1408 firstaccount() {
1409 dringopreply ConfigurationManager getAccountList | \
1410 grep string | awk -F&#39;&quot;&#39; &#39;{print $2}&#39; | head -n 1
1411 }
1412
1413 account=$(firstaccount)
1414
1415 if [ -z &quot;$account&quot; ] ; then
1416 echo &quot;Missing local account, trying to create it&quot;
1417 dringop ConfigurationManager addAccount \
1418 dict:string:string:&quot;Account.type&quot;,&quot;RING&quot;,&quot;Account.videoEnabled&quot;,&quot;false&quot;
1419 account=$(firstaccount)
1420 if [ -z &quot;$account&quot; ] ; then
1421 echo &quot;unable to create local account&quot;
1422 exit 1
1423 fi
1424 fi
1425
1426 # Not using dringopreply to ensure $2 can contain spaces
1427 dbus-send --print-reply --session \
1428 --dest=cx.ring.Ring \
1429 /cx/ring/Ring/ConfigurationManager \
1430 cx.ring.Ring.ConfigurationManager.sendTextMessage \
1431 string:&quot;$account&quot; string:&quot;$1&quot; \
1432 dict:string:string:&quot;text/plain&quot;,&quot;$2&quot;
1433 &lt;/pre&gt;&lt;/p&gt;
1434
1435 &lt;p&gt;If you want to check it out yourself, visit the
1436 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system project page&lt;/a&gt; to learn
1437 more, and install the latest Jami client from Debian Unstable or
1438 Testing.&lt;/p&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>Buster based Bokmål edition of Debian Administrator&#39;s Handbook</title>
1448 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
1449 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
1450 <pubDate>Tue, 20 Oct 2020 18:35:00 +0200</pubDate>
1451 <description>&lt;p align=&quot;center&quot;&gt;&lt;img align=&quot;center&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2020-10-20-debian-handbook-nb-testprint.jpeg&quot; width=&quot;60%&quot;/&gt;&lt;/p&gt;
1452
1453 &lt;p&gt;I am happy to report that we finally made it! Norwegian Bokmål
1454 became the first translation published on paper of the new Buster
1455 based edition of &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
1456 Administrator&#39;s Handbook&lt;/a&gt;&quot;. The print proof reading copy arrived
1457 some days ago, and it looked good, so now the book is approved for
1458 general distribution. This updated paperback edition &lt;a
1459 href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available from
1460 lulu.com&lt;/a&gt;. The book is also available for download in electronic
1461 form as PDF, EPUB and Mobipocket, and can also be
1462 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online&lt;/a&gt;.&lt;/p&gt;
1463
1464 &lt;p&gt;I am very happy to wrap up this Creative Common licensed project,
1465 which concludes several months of work by several volunteers. The
1466 number of Linux related books published in Norwegian are few, and I
1467 really hope this one will gain many readers, as it is packed with deep
1468 knowledge on Linux and the Debian ecosystem. The book will be
1469 available for various Internet book stores like Amazon and Barnes &amp;
1470 Noble soon, but I recommend buying
1471 &quot;&lt;a href=&quot;https://www.lulu.com/en/us/shop/roland-mas-and-rapha%C3%ABl-hertzog/h%C3%A5ndbok-for-debian-administratoren/paperback/product-9j7qwq.html&quot;&gt;Håndbok
1472 for Debian-administratoren&lt;/a&gt;&quot; directly from the source at Lulu.
1473
1474 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1475 activities, please send Bitcoin donations to my address
1476 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1477 </description>
1478 </item>
1479
1480 <item>
1481 <title>Buster update of Norwegian Bokmål edition of Debian Administrator&#39;s Handbook almost done</title>
1482 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html</link>
1483 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html</guid>
1484 <pubDate>Fri, 11 Sep 2020 09:45:00 +0200</pubDate>
1485 <description>&lt;p&gt;Thanks to the good work of several volunteers, the updated edition
1486 of the Norwegian translation for
1487 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
1488 Handbook&lt;/a&gt;&quot; is now almost completed. After many months of proof
1489 reading, I consider the proof reading complete enough for us to move
1490 to the next step, and have asked for the print version to be prepared
1491 and sent of to the print on demand service lulu.com. While it is
1492 still not to late if you find any incorrect translations on
1493 &lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
1494 hosted Weblate service&lt;/a&gt;, but it will be soon. :) You can check out
1495 &lt;a href=&quot; https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;the Buster
1496 edition on the web&lt;/a&gt; until the print edition is ready.&lt;/p&gt;
1497
1498 &lt;p&gt;The book will be for sale on lulu.com and various web book stores,
1499 with links available from the web site for the book linked to above.
1500 I hope a lot of readers find it useful.&lt;/p&gt;
1501
1502 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1503 activities, please send Bitcoin donations to my address
1504 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1505 </description>
1506 </item>
1507
1508 <item>
1509 <title>Working on updated Norwegian Bokmål edition of Debian Administrator&#39;s Handbook</title>
1510 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
1511 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
1512 <pubDate>Sat, 4 Jul 2020 23:55:00 +0200</pubDate>
1513 <description>&lt;p&gt;Three years ago, the first Norwegian Bokmål edition of
1514 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
1515 Handbook&lt;/a&gt;&quot; was published. This was based on Debian Jessie. Now a
1516 new and updated version based on Buster is getting ready. Work on the
1517 updated Norwegian Bokmål edition has been going on for a few months
1518 now, and yesterday, we reached the first mile stone, with 100% of the
1519 texts being translated. A lot of proof reading remains, of course,
1520 but a major step towards a new edition has been taken.&lt;/p&gt;
1521
1522 &lt;p&gt;The book is translated by volunteers, and we would love to get some
1523 help with the proof reading. The translation uses
1524 &lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
1525 hosted Weblate service&lt;/a&gt;, and we welcome everyone to have a look and
1526 submit improvements and suggestions. There is also a proof readers
1527 PDF available on request, get in touch if you want to help out that
1528 way.&lt;/p&gt;
1529
1530 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1531 activities, please send Bitcoin donations to my address
1532 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1533 </description>
1534 </item>
1535
1536 <item>
1537 <title>Secure Socket API - a simple and powerful approach for TLS support in software</title>
1538 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</link>
1539 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</guid>
1540 <pubDate>Sat, 6 Jun 2020 12:40:00 +0200</pubDate>
1541 <description>&lt;p&gt;As a member of the &lt;a href=&quot;https://www.nuug.no/&quot;&gt;Norwegian Unix
1542 User Group&lt;/a&gt;, I have the pleasure of receiving the
1543 &lt;a href=&quot;https://www.usenix.org/&quot;&gt;USENIX&lt;/a&gt; magazine
1544 &lt;a href=&quot;https://www.usenix.org/publications/login/&quot;&gt;;login:&lt;/a&gt;
1545 several times a year. I rarely have time to read all the articles,
1546 but try to at least skim through them all as there is a lot of nice
1547 knowledge passed on there. I even carry the latest issue with me most
1548 of the time to try to get through all the articles when I have a few
1549 spare minutes.&lt;/p&gt;
1550
1551 &lt;p&gt;The other day I came across a nice article titled
1552 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/winter2018/oneill&quot;&gt;The
1553 Secure Socket API: TLS as an Operating System Service&lt;/a&gt;&quot; with a
1554 marvellous idea I hope can make it all the way into the POSIX standard.
1555 The idea is as simple as it is powerful. By introducing a new
1556 socket() option IPPROTO_TLS to use TLS, and a system wide service to
1557 handle setting up TLS connections, one both make it trivial to add TLS
1558 support to any program currently using the POSIX socket API, and gain
1559 system wide control over certificates, TLS versions and encryption
1560 systems used. Instead of doing this:&lt;/p&gt;
1561
1562 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1563 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
1564 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1565
1566 &lt;p&gt;the program code would be doing this:&lt;p&gt;
1567
1568 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1569 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
1570 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1571
1572 &lt;p&gt;According to the ;login: article, converting a C program to use TLS
1573 would normally modify only 5-10 lines in the code, which is amazing
1574 when compared to using for example the OpenSSL API.&lt;/p&gt;
1575
1576 &lt;p&gt;The project has set up the
1577 &lt;a href=&quot;https://securesocketapi.org/&quot;&gt;https://securesocketapi.org/&lt;/a&gt;
1578 web site to spread the idea, and the code for a kernel module and the
1579 associated system daemon is available from two github repositories:
1580 &lt;a href=&quot;https://github.com/markoneill/ssa&quot;&gt;ssa&lt;/a&gt; and
1581 &lt;a href=&quot;https://github.com/markoneill/ssa-daemon&quot;&gt;ssa-daemon&lt;/a&gt;.
1582 Unfortunately there is no explicit license information with the code,
1583 so its copyright status is unclear. A
1584 &lt;a href=&quot;https://github.com/markoneill/ssa/issues/2&quot;&gt;request to solve
1585 this&lt;/a&gt; about it has been unsolved since 2018-08-17.&lt;/p&gt;
1586
1587 &lt;p&gt;I love the idea of extending socket() to gain TLS support, and
1588 understand why it is an advantage to implement this as a kernel module
1589 and system wide service daemon, but can not help to think that it
1590 would be a lot easier to get projects to move to this way of setting
1591 up TLS if it was done with a user space approach where programs
1592 wanting to use this API approach could just link with a wrapper
1593 library.&lt;/p&gt;
1594
1595 &lt;p&gt;I recommend you check out this simple and powerful approach to more
1596 secure network connections. :)&lt;/p&gt;
1597
1598 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1599 activities, please send Bitcoin donations to my address
1600 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1601 </description>
1602 </item>
1603
1604 <item>
1605 <title>Jami as a Zoom client, a trick for password protected rooms...</title>
1606 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</link>
1607 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</guid>
1608 <pubDate>Fri, 8 May 2020 13:30:00 +0200</pubDate>
1609 <description>&lt;p&gt;Half a year ago,
1610 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html&quot;&gt;I
1611 wrote&lt;/a&gt; about &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami communication
1612 client&lt;/a&gt;, capable of peer-to-peer encrypted communication. It
1613 handle both messages, audio and video. It uses distributed hash
1614 tables instead of central infrastructure to connect its users to each
1615 other, which in my book is a plus. I mentioned briefly that it could
1616 also work as a SIP client, which came in handy when the higher
1617 educational sector in Norway started to promote Zoom as its video
1618 conferencing solution. I am reluctant to use the official Zoom client
1619 software, due to their &lt;a href=&quot;https://zoom.us/terms&quot;&gt;copyright
1620 license clauses&lt;/a&gt; prohibiting users to reverse engineer (for example
1621 to check the security) and benchmark it, and thus prefer to connect to
1622 Zoom meetings with free software clients.&lt;/p&gt;
1623
1624 &lt;p&gt;Jami worked OK as a SIP client to Zoom as long as there was no
1625 password set on the room. The Jami daemon leak memory like crazy
1626 (approximately 1 GiB a minute) when I am connected to the video
1627 conference, so I had to restart the client every 7-10 minutes, which
1628 is not great. I tried to get other SIP Linux clients to work
1629 without success, so I decided I would have to live with this wart
1630 until someone managed to fix the leak in the dring code base. But
1631 another problem showed up once the rooms were password protected. I
1632 could not get my dial tone signaling through from Jami to Zoom, and
1633 dial tone signaling is used to enter the password when connecting to
1634 Zoom. I tried a lot of different permutations with my Jami and
1635 Asterisk setup to try to figure out why the signaling did not get
1636 through, only to finally discover that the fundamental problem seem to
1637 be that Zoom is simply not able to receive dial tone signaling when
1638 connecting via SIP. There seem to be nothing wrong with the Jami and
1639 Asterisk end, it is simply broken in the Zoom end. I got help from a
1640 very skilled VoIP engineer figuring out this last part. And being a
1641 very skilled engineer, he was also able to locate a solution for me.
1642 Or to be exact, a workaround that solve my initial problem of
1643 connecting to password protected Zoom rooms using Jami.&lt;/p&gt;
1644
1645 &lt;p&gt;So, how do you do this, I am sure you are wondering by now. The
1646 trick is already
1647 &lt;a href=&quot;https://support.zoom.us/hc/en-us/articles/202405539-H-323-SIP-Room-Connector-Dial-Strings#sip&quot;&gt;documented
1648 from Zoom&lt;/a&gt;, and it is to modify the SIP address to include the room
1649 password. What is most surprising about this is that the
1650 automatically generated email from Zoom with instructions on how to
1651 connect via SIP do not mention this. The SIP address to use normally
1652 consist of the room ID (a number), an @ character and the IP address
1653 of the Zoom SIP gateway. But Zoom understand a lot more than just the
1654 room ID in front of the at sign. The format is &quot;&lt;tt&gt;[Meeting
1655 ID].[Password].[Layout].[Host Key]&lt;/tt&gt;&quot;, and you can here see how you
1656 can both enter password, control the layout (full screen, active
1657 presence and gallery) and specify the host key to start the meeting.
1658 The full SIP address entered into Jami to provide the password will
1659 then look like this (all using made up numbers):&lt;/p&gt;
1660
1661 &lt;p&gt;&lt;blockquote&gt;
1662 &lt;tt&gt;sip:657837644.522827@192.168.169.170&lt;/tt&gt;
1663 &lt;/blockquote&gt;&lt;/p&gt;
1664
1665 &lt;p&gt;Now if only jami would reduce its memory usage, I could even
1666 recommend this setup to others. :)&lt;/p&gt;
1667
1668 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1669 activities, please send Bitcoin donations to my address
1670 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1671 </description>
1672 </item>
1673
1674 <item>
1675 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software</title>
1676 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</link>
1677 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</guid>
1678 <pubDate>Wed, 29 Apr 2020 13:10:00 +0200</pubDate>
1679 <description>&lt;p&gt;The curiosity got the better of me when
1680 &lt;a href=&quot;https://developers.slashdot.org/story/20/04/06/1424246/new-jersey-desperately-needs-cobol-programmers&quot;&gt;Slashdot
1681 reported&lt;/a&gt; that New Jersey was desperately looking for
1682 &lt;a href=&quot;https://en.wikipedia.org/wiki/COBOL&quot;&gt;COBOL&lt;/a&gt; programmers,
1683 and a few days later it was reported that
1684 &lt;a href=&quot;https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce&quot;&gt;IBM
1685 tried to locate COBOL programmers&lt;/a&gt;.&lt;/p&gt;
1686
1687 &lt;p&gt;I thus decided to have a look at free software alternatives to
1688 learn COBOL, and had the pleasure to find
1689 &lt;a href=&quot;https://sourceforge.net/projects/open-cobol/&quot;&gt;GnuCOBOL&lt;/a&gt; was
1690 already &lt;a href=&quot;https://tracker.debian.org/pkg/gnucobol&quot;&gt;in
1691 Debian&lt;/a&gt;. It used to be called Open Cobol, and is a &quot;compiler&quot;
1692 transforming COBOL code to C or C++ before giving it to GCC or Visual
1693 Studio to build binaries.&lt;/p&gt;
1694
1695 &lt;p&gt;I managed to get in touch with upstream, and was impressed with the
1696 quick response, and also was happy to see a new Debian maintainer
1697 taking over when the original one recently asked to be replaced. A
1698 new Debian upload was done as recently as yesterday.&lt;/p&gt;
1699
1700 &lt;p&gt;Using the Debian package, I was able to follow a simple COBOL
1701 introduction and make and run simple COBOL programs. It was fun to
1702 learn a new programming language. If you want to test for yourself,
1703 &lt;a href=&quot;https://en.wikipedia.org/wiki/GnuCOBOL&quot;&gt;the GnuCOBOL Wikipedia
1704 page&lt;/a&gt; have a few simple examples to get you startet.&lt;/p&gt;
1705
1706 &lt;p&gt;As I do not have much experience with COBOL, I do not know how
1707 standard compliant it is, but it claim to pass most tests from COBOL
1708 test suite, which sound good to me. It is nice to know it is possible
1709 to learn COBOL using software without any usage restrictions, and I am
1710 very happy such nice free software project as this is available. If
1711 you as me is curious about COBOL, check it out.&lt;/p&gt;
1712
1713 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1714 activities, please send Bitcoin donations to my address
1715 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1716 </description>
1717 </item>
1718
1719 <item>
1720 <title>Jami/Ring, finally functioning peer to peer communication client</title>
1721 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</link>
1722 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</guid>
1723 <pubDate>Wed, 19 Jun 2019 08:50:00 +0200</pubDate>
1724 <description>&lt;p&gt;Some years ago, in 2016, I
1725 &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;wrote
1726 for the first time about&lt;/a&gt; the Ring peer to peer messaging system.
1727 It would provide messaging without any central server coordinating the
1728 system and without requiring all users to register a phone number or
1729 own a mobile phone. Back then, I could not get it to work, and put it
1730 aside until it had seen more development. A few days ago I decided to
1731 give it another try, and am happy to report that this time I am able
1732 to not only send and receive messages, but also place audio and video
1733 calls. But only if UDP is not blocked into your network.&lt;/p&gt;
1734
1735 &lt;p&gt;The Ring system changed name earlier this year to
1736 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;. I
1737 tried doing web search for &#39;ring&#39; when I discovered it for the first
1738 time, and can only applaud this change as it is impossible to find
1739 something called Ring among the noise of other uses of that word. Now
1740 you can search for &#39;jami&#39; and this client and
1741 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system&lt;/a&gt; is the first hit at
1742 least on duckduckgo.&lt;/p&gt;
1743
1744 &lt;p&gt;Jami will by default encrypt messages as well as audio and video
1745 calls, and try to send them directly between the communicating parties
1746 if possible. If this proves impossible (for example if both ends are
1747 behind NAT), it will use a central SIP TURN server maintained by the
1748 Jami project. Jami can also be a normal SIP client. If the SIP
1749 server is unencrypted, the audio and video calls will also be
1750 unencrypted. This is as far as I know the only case where Jami will
1751 do anything without encryption.&lt;/p&gt;
1752
1753 &lt;p&gt;Jami is available for several platforms: Linux, Windows, MacOSX,
1754 Android, iOS, and Android TV. It is included in Debian already. Jami
1755 also work for those using F-Droid without any Google connections,
1756 while Signal do not.
1757 &lt;a href=&quot;https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol&quot;&gt;The
1758 protocol&lt;/a&gt; is described in the Ring project wiki. The system uses a
1759 distributed hash table (DHT) system (similar to BitTorrent) running
1760 over UDP. On one of the networks I use, I discovered Jami failed to
1761 work. I tracked this down to the fact that incoming UDP packages
1762 going to ports 1-49999 were blocked, and the DHT would pick a random
1763 port and end up in the low range most of the time. After talking to
1764 the developers, I solved this by enabling the dhtproxy in the
1765 settings, thus using TCP to talk to a central DHT proxy instead of
1766
1767 peering directly with others. I&#39;ve been told the developers are
1768 working on allowing DHT to use TCP to avoid this problem. I also ran
1769 into a problem when trying to talk to the version of Ring included in
1770 Debian Stable (Stretch). Apparently the protocol changed between
1771 beta2 and the current version, making these clients incompatible.
1772 Hopefully the protocol will not be made incompatible in the
1773 future.&lt;/p&gt;
1774
1775 &lt;p&gt;It is worth noting that while looking at Jami and its features, I
1776 came across another communication platform I have not tested yet. The
1777 &lt;a href=&quot;https://en.wikipedia.org/wiki/Tox_(protocol)&quot;&gt;Tox protocol&lt;/a&gt;
1778 and &lt;a href=&quot;https://tox.chat/&quot;&gt;family of Tox clients&lt;/a&gt;. It might
1779 become the topic of a future blog post.&lt;/p&gt;
1780
1781 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1782 activities, please send Bitcoin donations to my address
1783 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1784 </description>
1785 </item>
1786
1787 <item>
1788 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål</title>
1789 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</link>
1790 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</guid>
1791 <pubDate>Wed, 23 Jan 2019 07:50:00 +0100</pubDate>
1792 <description>&lt;p&gt;I høst ble jeg inspirert til å bidra til oversettelsen av
1793 &lt;a href=&quot;http://unknown-horizons.org/&quot;&gt;strategispillet Unknown
1794 Horizons&lt;/a&gt;, og oversatte de nesten 200 strengene i prosjektet til
1795 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
1796 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
1797 nye versjonen kom på nyåret, og ble
1798 &lt;a href=&quot;https://tracker.debian.org/pkg/unknown-horizons&quot;&gt;lastet opp i
1799 Debian&lt;/a&gt; for noen få dager siden. I går kveld fikk jeg testet det ut, og
1800 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
1801 måtte justeres, men ikke noe alvorlig. Har oppdatert
1802 &lt;a href=&quot;https://hosted.weblate.org/projects/uh/&quot;&gt;oversettelsen på
1803 Weblate&lt;/a&gt;, slik at neste utgave vil være enda bedre. :)&lt;/p&gt;
1804
1805 &lt;p&gt;Spillet er et ressursstyringsspill ala Civilization, og er morsomt
1806 å spille for oss som liker slikt. :)&lt;/p&gt;
1807
1808 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1809 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1810 til min adresse
1811 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
1812 Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
1813 </description>
1814 </item>
1815
1816 <item>
1817 <title>Debian now got everything you need to program Micro:bit</title>
1818 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</link>
1819 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</guid>
1820 <pubDate>Tue, 22 Jan 2019 17:20:00 +0100</pubDate>
1821 <description>&lt;p&gt;I am amazed and very pleased to discover that since a few days ago,
1822 everything you need to program the &lt;a href=&quot;https://microbit.org/&quot;&gt;BBC
1823 micro:bit&lt;/a&gt; is available from the Debian archive. All this is
1824 thanks to the hard work of Nick Morrott and the Debian python
1825 packaging team. The micro:bit project recommend the mu-editor to
1826 program the microcomputer, as this editor will take care of all the
1827 machinery required to injekt/flash micropython alongside the program
1828 into the micro:bit, as long as the pieces are available.&lt;/p&gt;
1829
1830 &lt;p&gt;There are three main pieces involved. The first to enter Debian
1831 was
1832 &lt;a href=&quot;https://tracker.debian.org/pkg/python-uflash&quot;&gt;python-uflash&lt;/a&gt;,
1833 which was accepted into the archive 2019-01-12. The next one was
1834 &lt;a href=&quot;https://tracker.debian.org/pkg/mu-editor&quot;&gt;mu-editor&lt;/a&gt;, which
1835 showed up 2019-01-13. The final and hardest part to to into the
1836 archive was
1837 &lt;a href=&quot;https://tracker.debian.org/pkg/firmware-microbit-micropython&quot;&gt;firmware-microbit-micropython&lt;/a&gt;,
1838 which needed to get its build system and dependencies into Debian
1839 before it was accepted 2019-01-20. The last one is already in Debian
1840 Unstable and should enter Debian Testing / Buster in three days. This
1841 all allow any user of the micro:bit to get going by simply running
1842 &#39;apt install mu-editor&#39; when using Testing or Unstable, and once
1843 Buster is released as stable, all the users of Debian stable will be
1844 catered for.&lt;/p&gt;
1845
1846 &lt;p&gt;As a minor final touch, I added rules to
1847 &lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;the isenkram
1848 package&lt;/a&gt; for recognizing micro:bit and recommend the mu-editor
1849 package. This make sure any user of the isenkram desktop daemon will
1850 get a popup suggesting to install mu-editor then the USB cable from
1851 the micro:bit is inserted for the first time.&lt;/p&gt;
1852
1853 &lt;p&gt;This should make it easier to have fun.&lt;/p&gt;
1854
1855 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1856 activities, please send Bitcoin donations to my address
1857 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1858 </description>
1859 </item>
1860
1861 <item>
1862 <title>Learn to program with Minetest on Debian</title>
1863 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</link>
1864 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</guid>
1865 <pubDate>Sat, 15 Dec 2018 15:30:00 +0100</pubDate>
1866 <description>&lt;p&gt;A fun way to learn how to program
1867 &lt;a href=&quot;https://www.python.org/&quot;&gt;Python&lt;/a&gt; is to follow the
1868 instructions in the book
1869 &quot;&lt;a href=&quot;https://nostarch.com/programwithminecraft&quot;&gt;Learn to program
1870 with Minecraft&lt;/a&gt;&quot;, which introduces programming in Python to people
1871 who like to play with Minecraft. The book uses a Python library to
1872 talk to a TCP/IP socket with an API accepting build instructions and
1873 providing information about the current players in a Minecraft world.
1874 The TCP/IP API was first created for the Minecraft implementation for
1875 Raspberry Pi, and has since been ported to some server versions of
1876 Minecraft. The book contain recipes for those using Windows, MacOSX
1877 and Raspian. But a little known fact is that you can follow the same
1878 recipes using the free software construction game
1879 &lt;a href=&quot;https://minetest.net/&quot;&gt;Minetest&lt;/a&gt;.&lt;/p&gt;
1880
1881 &lt;p&gt;There is &lt;a href=&quot;https://github.com/sprintingkiwi/pycraft_mod&quot;&gt;a
1882 Minetest module implementing the same API&lt;/a&gt;, making it possible to
1883 use the Python programs coded to talk to Minecraft with Minetest too.
1884 I
1885 &lt;a href=&quot;https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%2Bgit20180331.0376a0a%2Bdfsg-1.html&quot;&gt;uploaded
1886 this module&lt;/a&gt; to Debian two weeks ago, and as soon as it clears the
1887 FTP masters NEW queue, learning to program Python with Minetest on
1888 Debian will be a simple &#39;apt install&#39; away. The Debian package is
1889 maintained as part of the Debian Games team, and
1890 &lt;a href=&quot;https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft&quot;&gt;the
1891 packaging rules&lt;/a&gt; are currently located under &#39;unfinished&#39; on
1892 Salsa.&lt;/p&gt;
1893
1894 &lt;p&gt;You will most likely need to install several of the Minetest
1895 modules in Debian for the examples included with the library to work
1896 well, as there are several blocks used by the example scripts that are
1897 provided via modules in Minetest. Without the required blocks, a
1898 simple stone block is used instead. My initial testing with a analog
1899 clock did not get gold arms as instructed in the python library, but
1900 instead used stone arms.&lt;/p&gt;
1901
1902 &lt;p&gt;I tried to find a way to add the API to the desktop version of
1903 Minecraft, but were unable to find any working recipes. The
1904 &lt;a href=&quot;https://www.epiphanydigest.com/tag/minecraft-python-api/&quot;&gt;recipes&lt;/a&gt;
1905 I &lt;a href=&quot;https://github.com/kbsriram/mcpiapi&quot;&gt;found&lt;/a&gt; are only
1906 working with a standalone Minecraft server setup. Are there any
1907 options to use with the normal desktop version?&lt;/p&gt;
1908
1909 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1910 activities, please send Bitcoin donations to my address
1911 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1912 </description>
1913 </item>
1914
1915 <item>
1916 <title>Time for an official MIME type for patches?</title>
1917 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</link>
1918 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</guid>
1919 <pubDate>Thu, 1 Nov 2018 08:15:00 +0100</pubDate>
1920 <description>&lt;p&gt;As part of my involvement in
1921 &lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;the Nikita
1922 archive API project&lt;/a&gt;, I&#39;ve been importing a fairly large lump of
1923 emails into a test instance of the archive to see how well this would
1924 go. I picked a subset of &lt;a href=&quot;https://notmuchmail.org/&quot;&gt;my
1925 notmuch email database&lt;/a&gt;, all public emails sent to me via
1926 @lists.debian.org, giving me a set of around 216 000 emails to import.
1927 In the process, I had a look at the various attachments included in
1928 these emails, to figure out what to do with attachments, and noticed
1929 that one of the most common attachment formats do not have
1930 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;an
1931 official MIME type&lt;/a&gt; registered with IANA/IETF. The output from
1932 diff, ie the input for patch, is on the top 10 list of formats
1933 included in these emails. At the moment people seem to use either
1934 text/x-patch or text/x-diff, but neither is officially registered. It
1935 would be better if one official MIME type were registered and used
1936 everywhere.&lt;/p&gt;
1937
1938 &lt;p&gt;To try to get one official MIME type for these files, I&#39;ve brought
1939 up the topic on
1940 &lt;a href=&quot;https://www.ietf.org/mailman/listinfo/media-types&quot;&gt;the
1941 media-types mailing list&lt;/a&gt;. If you are interested in discussion
1942 which MIME type to use as the official for patch files, or involved in
1943 making software using a MIME type for patches, perhaps you would like
1944 to join the discussion?&lt;/p&gt;
1945
1946 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1947 activities, please send Bitcoin donations to my address
1948 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1949 </description>
1950 </item>
1951
1952 <item>
1953 <title>Automatic Google Drive sync using grive in Debian</title>
1954 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
1955 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
1956 <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
1957 <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian. To try to
1958 rescue the remains, I helped set up automatic sync with Google Drive.
1959 I did not find any sensible Debian package handling this
1960 automatically, so I rebuild the grive2 source from
1961 &lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
1962 task and added a autostart desktop entry and a small shell script to
1963 run in the background while the user is logged in to do the sync.
1964 Here is a sketch of the setup for future reference.&lt;/p&gt;
1965
1966 &lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
1967 ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user. Next, I
1968 created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
1969 to start the sync when the user log in:&lt;/p&gt;
1970
1971 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1972 [Desktop Entry]
1973 Name=Google drive autosync
1974 Type=Application
1975 Exec=/home/user/bin/grive-sync
1976 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1977
1978 &lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
1979 ~/googledrive/ with the files in Google Drive.&lt;/p&gt;
1980
1981 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1982 #!/bin/sh
1983 set -e
1984 cd ~/
1985 cleanup() {
1986 if [ &quot;$syncpid&quot; ] ; then
1987 kill $syncpid
1988 fi
1989 }
1990 trap cleanup EXIT INT QUIT
1991 /usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
1992 syncpdi=$!
1993 while true; do
1994 if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
1995 echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
1996 exit 1
1997 fi
1998 if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
1999 /usr/lib/grive/grive-sync.sh sync googledrive
2000 fi
2001 sleep 300
2002 done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
2003 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2004
2005 &lt;p&gt;Feel free to use the setup if you want. It can be assumed to be
2006 GNU GPL v2 licensed (or any later version, at your leisure), but I
2007 doubt this code is possible to claim copyright on.&lt;/p&gt;
2008
2009 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2010 activities, please send Bitcoin donations to my address
2011 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2012 </description>
2013 </item>
2014
2015 <item>
2016 <title>Using the Kodi API to play Youtube videos</title>
2017 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</link>
2018 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</guid>
2019 <pubDate>Sun, 2 Sep 2018 23:40:00 +0200</pubDate>
2020 <description>&lt;p&gt;I continue to explore my Kodi installation, and today I wanted to
2021 tell it to play a youtube URL I received in a chat, without having to
2022 insert search terms using the on-screen keyboard. After searching the
2023 web for API access to the Youtube plugin and testing a bit, I managed
2024 to find a recipe that worked. If you got a kodi instance with its API
2025 available from http://kodihost/jsonrpc, you can try the following to
2026 have check out a nice cover band.&lt;/p&gt;
2027
2028 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;curl --silent --header &#39;Content-Type: application/json&#39; \
2029 --data-binary &#39;{ &quot;id&quot;: 1, &quot;jsonrpc&quot;: &quot;2.0&quot;, &quot;method&quot;: &quot;Player.Open&quot;,
2030 &quot;params&quot;: {&quot;item&quot;: { &quot;file&quot;:
2031 &quot;plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg&quot; } } }&#39; \
2032 http://projector.local/jsonrpc&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2033
2034 &lt;p&gt;I&#39;ve extended kodi-stream program to take a video source as its
2035 first argument. It can now handle direct video links, youtube links
2036 and &#39;desktop&#39; to stream my desktop to Kodi. It is almost like a
2037 Chromecast. :)&lt;/p&gt;
2038
2039 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2040 activities, please send Bitcoin donations to my address
2041 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2042 </description>
2043 </item>
2044
2045 <item>
2046 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata</title>
2047 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</link>
2048 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</guid>
2049 <pubDate>Tue, 31 Jul 2018 23:30:00 +0200</pubDate>
2050 <description>&lt;p&gt;For a while now, I have looked for a sensible way to share images
2051 with my family using a self hosted solution, as it is unacceptable to
2052 place images from my personal life under the control of strangers
2053 working for data hoarders like Google or Dropbox. The last few days I
2054 have drafted an approach that might work out, and I would like to
2055 share it with you. I would like to publish images on a server under
2056 my control, and point some Internet connected display units using some
2057 free and open standard to the images I published. As my primary
2058 language is not limited to ASCII, I need to store metadata using
2059 UTF-8. Many years ago, I hoped to find a digital photo frame capable
2060 of reading a RSS feed with image references (aka using the
2061 &amp;lt;enclosure&amp;gt; RSS tag), but was unable to find a current supplier
2062 of such frames. In the end I gave up that approach.&lt;/p&gt;
2063
2064 &lt;p&gt;Some months ago, I discovered that
2065 &lt;a href=&quot;https://www.jwz.org/xscreensaver/&quot;&gt;XScreensaver&lt;/a&gt; is able to
2066 read images from a RSS feed, and used it to set up a screen saver on
2067 my home info screen, showing images from the Daily images feed from
2068 NASA. This proved to work well. More recently I discovered that
2069 &lt;a href=&quot;https://kodi.tv&quot;&gt;Kodi&lt;/a&gt; (both using
2070 &lt;a href=&quot;https://www.openelec.tv/&quot;&gt;OpenELEC&lt;/a&gt; and
2071 &lt;a href=&quot;https://libreelec.tv&quot;&gt;LibreELEC&lt;/a&gt;) provide the
2072 &lt;a href=&quot;https://github.com/grinsted/script.screensaver.feedreader&quot;&gt;Feedreader&lt;/a&gt;
2073 screen saver capable of reading a RSS feed with images and news. For
2074 fun, I used it this summer to test Kodi on my parents TV by hooking up
2075 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
2076 screen saver showing selected pictures from my selection.&lt;/p&gt;
2077
2078 &lt;p&gt;Armed with motivation and a test photo frame, I set out to generate
2079 a RSS feed for the Kodi instance. I adjusted my &lt;a
2080 href=&quot;https://freedombox.org/&quot;&gt;Freedombox&lt;/a&gt; instance, created
2081 /var/www/html/privatepictures/, wrote a small Perl script to extract
2082 title and description metadata from the photo files and generate the
2083 RSS file. I ended up using Perl instead of python, as the
2084 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
2085 tags I ended up using, while python3-exif did not. The relevant EXIF
2086 tags only support ASCII, so I had to find better alternatives. XMP
2087 seem to have the support I need.&lt;/p&gt;
2088
2089 &lt;p&gt;I am a bit unsure which EXIF/XMP tags to use, as I would like to
2090 use tags that can be easily added/updated using normal free software
2091 photo managing software. I ended up using the tags set using this
2092 exiftool command, as these tags can also be set using digiKam:&lt;/p&gt;
2093
2094 &lt;blockquote&gt;&lt;pre&gt;
2095 exiftool -headline=&#39;The RSS image title&#39; \
2096 -description=&#39;The RSS image description.&#39; \
2097 -subject+=for-family photo.jpeg
2098 &lt;/pre&gt;&lt;/blockquote&gt;
2099
2100 &lt;p&gt;I initially tried the &quot;-title&quot; and &quot;keyword&quot; tags, but they were
2101 invisible in digiKam, so I changed to &quot;-headline&quot; and &quot;-subject&quot;. I
2102 use the keyword/subject &#39;for-family&#39; to flag that the photo should be
2103 shared with my family. Images with this keyword set are located and
2104 copied into my Freedombox for the RSS generating script to find.&lt;/p&gt;
2105
2106 &lt;p&gt;Are there better ways to do this? Get in touch if you have better
2107 suggestions.&lt;/p&gt;
2108
2109 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2110 activities, please send Bitcoin donations to my address
2111 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2112 </description>
2113 </item>
2114
2115 <item>
2116 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP</title>
2117 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</link>
2118 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</guid>
2119 <pubDate>Thu, 12 Jul 2018 17:55:00 +0200</pubDate>
2120 <description>&lt;p&gt;Last night, I wrote
2121 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html&quot;&gt;a
2122 recipe to stream a Linux desktop using VLC to a instance of Kodi&lt;/a&gt;.
2123 During the day I received valuable feedback, and thanks to the
2124 suggestions I have been able to rewrite the recipe into a much simpler
2125 approach requiring no setup at all. It is a single script that take
2126 care of it all.&lt;/p&gt;
2127
2128 &lt;p&gt;This new script uses GStreamer instead of VLC to capture the
2129 desktop and stream it to Kodi. This fixed the video quality issue I
2130 saw initially. It further removes the need to add a m3u file on the
2131 Kodi machine, as it instead connects to
2132 &lt;a href=&quot;https://kodi.wiki/view/JSON-RPC_API/v8&quot;&gt;the JSON-RPC API in
2133 Kodi&lt;/a&gt; and simply ask Kodi to play from the stream created using
2134 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
2135 the script below, run it with the DNS name or IP address of the kodi
2136 server to stream to as the only argument, and watch your screen show
2137 up on the Kodi screen. Note, it depend on multicast on the local
2138 network, so if you need to stream outside the local network, the
2139 script must be modified. Also note, I have no idea if audio work, as
2140 I only care about the picture part.&lt;/p&gt;
2141
2142 &lt;blockquote&gt;&lt;pre&gt;
2143 #!/bin/sh
2144 #
2145 # Stream the Linux desktop view to Kodi. See
2146 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
2147 # for backgorund information.
2148
2149 # Make sure the stream is stopped in Kodi and the gstreamer process is
2150 # killed if something go wrong (for example if curl is unable to find the
2151 # kodi server). Do the same when interrupting this script.
2152 kodicmd() {
2153 host=&quot;$1&quot;
2154 cmd=&quot;$2&quot;
2155 params=&quot;$3&quot;
2156 curl --silent --header &#39;Content-Type: application/json&#39; \
2157 --data-binary &quot;{ \&quot;id\&quot;: 1, \&quot;jsonrpc\&quot;: \&quot;2.0\&quot;, \&quot;method\&quot;: \&quot;$cmd\&quot;, \&quot;params\&quot;: $params }&quot; \
2158 &quot;http://$host/jsonrpc&quot;
2159 }
2160 cleanup() {
2161 if [ -n &quot;$kodihost&quot; ] ; then
2162 # Stop the playing when we end
2163 playerid=$(kodicmd &quot;$kodihost&quot; Player.GetActivePlayers &quot;{}&quot; |
2164 jq .result[].playerid)
2165 kodicmd &quot;$kodihost&quot; Player.Stop &quot;{ \&quot;playerid\&quot; : $playerid }&quot; &gt; /dev/null
2166 fi
2167 if [ &quot;$gstpid&quot; ] &amp;&amp; kill -0 &quot;$gstpid&quot; &gt;/dev/null 2&gt;&amp;1; then
2168 kill &quot;$gstpid&quot;
2169 fi
2170 }
2171 trap cleanup EXIT INT
2172
2173 if [ -n &quot;$1&quot; ]; then
2174 kodihost=$1
2175 shift
2176 else
2177 kodihost=kodi.local
2178 fi
2179
2180 mcast=239.255.0.1
2181 mcastport=1234
2182 mcastttl=1
2183
2184 pasrc=$(pactl list | grep -A2 &#39;Source #&#39; | grep &#39;Name: .*\.monitor$&#39; | \
2185 cut -d&quot; &quot; -f2|head -1)
2186 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
2187 videoconvert ! queue2 ! \
2188 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
2189 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
2190 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
2191 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=1 sync=0 \
2192 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
2193 &gt; /dev/null 2&gt;&amp;1 &amp;
2194 gstpid=$!
2195
2196 # Give stream a second to get going
2197 sleep 1
2198
2199 # Ask kodi to start streaming using its JSON-RPC API
2200 kodicmd &quot;$kodihost&quot; Player.Open \
2201 &quot;{\&quot;item\&quot;: { \&quot;file\&quot;: \&quot;udp://@$mcast:$mcastport\&quot; } }&quot; &gt; /dev/null
2202
2203 # wait for gst to end
2204 wait &quot;$gstpid&quot;
2205 &lt;/pre&gt;&lt;/blockquote&gt;
2206
2207 &lt;p&gt;I hope you find the approach useful. I know I do.&lt;/p&gt;
2208
2209 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2210 activities, please send Bitcoin donations to my address
2211 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2212 </description>
2213 </item>
2214
2215 <item>
2216 <title>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
2217 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
2218 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
2219 <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
2220 <description>&lt;p&gt;PS: See
2221 &lt;ahref=&quot;http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html&quot;&gt;the
2222 followup post&lt;/a&gt; for a even better approach.&lt;/p&gt;
2223
2224 &lt;p&gt;A while back, I was asked by a friend how to stream the desktop to
2225 my projector connected to Kodi. I sadly had to admit that I had no
2226 idea, as it was a task I never had tried. Since then, I have been
2227 looking for a way to do so, preferable without much extra software to
2228 install on either side. Today I found a way that seem to kind of
2229 work. Not great, but it is a start.&lt;/p&gt;
2230
2231 &lt;p&gt;I had a look at several approaches, for example
2232 &lt;a href=&quot;https://github.com/mfoetsch/dlna_live_streaming&quot;&gt;using uPnP
2233 DLNA as described in 2011&lt;/a&gt;, but it required a uPnP server, fuse and
2234 local storage enough to store the stream locally. This is not going
2235 to work well for me, lacking enough free space, and it would
2236 impossible for my friend to get working.&lt;/p&gt;
2237
2238 &lt;p&gt;Next, it occurred to me that perhaps I could use VLC to create a
2239 video stream that Kodi could play. Preferably using
2240 broadcast/multicast, to avoid having to change any setup on the Kodi
2241 side when starting such stream. Unfortunately, the only recipe I
2242 could find using multicast used the rtp protocol, and this protocol
2243 seem to not be supported by Kodi.&lt;/p&gt;
2244
2245 &lt;p&gt;On the other hand, the rtsp protocol is working! Unfortunately I
2246 have to specify the IP address of the streaming machine in both the
2247 sending command and the file on the Kodi server. But it is showing my
2248 desktop, and thus allow us to have a shared look on the big screen at
2249 the programs I work on.&lt;/p&gt;
2250
2251 &lt;p&gt;I did not spend much time investigating codeces. I combined the
2252 rtp and rtsp recipes from
2253 &lt;a href=&quot;https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/&quot;&gt;the
2254 VLC Streaming HowTo/Command Line Examples&lt;/a&gt;, and was able to get
2255 this working on the desktop/streaming end.&lt;/p&gt;
2256
2257 &lt;blockquote&gt;&lt;pre&gt;
2258 vlc screen:// --sout \
2259 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{dst=projector.local,port=1234,sdp=rtsp://192.168.11.4:8080/test.sdp}&#39;
2260 &lt;/pre&gt;&lt;/blockquote&gt;
2261
2262 &lt;p&gt;I ssh-ed into my Kodi box and created a file like this with the
2263 same IP address:&lt;/p&gt;
2264
2265 &lt;blockquote&gt;&lt;pre&gt;
2266 echo rtsp://192.168.11.4:8080/test.sdp \
2267 &gt; /storage/videos/screenstream.m3u
2268 &lt;/pre&gt;&lt;/blockquote&gt;
2269
2270 &lt;p&gt;Note the 192.168.11.4 IP address is my desktops IP address. As far
2271 as I can tell the IP must be hardcoded for this to work. In other
2272 words, if someone elses machine is going to do the steaming, you have
2273 to update screenstream.m3u on the Kodi machine and adjust the vlc
2274 recipe. To get started, locate the file in Kodi and select the m3u
2275 file while the VLC stream is running. The desktop then show up in my
2276 big screen. :)&lt;/p&gt;
2277
2278 &lt;p&gt;When using the same technique to stream a video file with audio,
2279 the audio quality is really bad. No idea if the problem is package
2280 loss or bad parameters for the transcode. I do not know VLC nor Kodi
2281 enough to tell.&lt;/p&gt;
2282
2283 &lt;p&gt;&lt;strong&gt;Update 2018-07-12&lt;/strong&gt;: Johannes Schauer send me a few
2284 succestions and reminded me about an important step. The &quot;screen:&quot;
2285 input source is only available once the vlc-plugin-access-extra
2286 package is installed on Debian. Without it, you will see this error
2287 message: &quot;VLC is unable to open the MRL &#39;screen://&#39;. Check the log
2288 for details.&quot; He further found that it is possible to drop some parts
2289 of the VLC command line to reduce the amount of hardcoded information.
2290 It is also useful to consider using cvlc to avoid having the VLC
2291 window in the desktop view. In sum, this give us this command line on
2292 the source end
2293
2294 &lt;blockquote&gt;&lt;pre&gt;
2295 cvlc screen:// --sout \
2296 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}&#39;
2297 &lt;/pre&gt;&lt;/blockquote&gt;
2298
2299 &lt;p&gt;and this on the Kodi end&lt;p&gt;
2300
2301 &lt;blockquote&gt;&lt;pre&gt;
2302 echo rtsp://192.168.11.4:8080/ \
2303 &gt; /storage/videos/screenstream.m3u
2304 &lt;/pre&gt;&lt;/blockquote&gt;
2305
2306 &lt;p&gt;Still bad image quality, though. But I did discover that streaming
2307 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
2308 audio quality, so I guess the issue is in the input or transcoding
2309 parts, not the rtsp part. I&#39;ve tried to change the vb and ab
2310 parameters to use more bandwidth, but it did not make a
2311 difference.&lt;/p&gt;
2312
2313 &lt;p&gt;I further received a suggestion from Einar Haraldseid to try using
2314 gstreamer instead of VLC, and this proved to work great! He also
2315 provided me with the trick to get Kodi to use a multicast stream as
2316 its source. By using this monstrous oneliner, I can stream my desktop
2317 with good video quality in reasonable framerate to the 239.255.0.1
2318 multicast address on port 1234:
2319
2320 &lt;blockquote&gt;&lt;pre&gt;
2321 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
2322 videoconvert ! queue2 ! \
2323 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
2324 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
2325 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
2326 udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
2327 pulsesrc device=$(pactl list | grep -A2 &#39;Source #&#39; | \
2328 grep &#39;Name: .*\.monitor$&#39; | cut -d&quot; &quot; -f2|head -1) ! \
2329 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
2330 &lt;/pre&gt;&lt;/blockquote&gt;
2331
2332 &lt;p&gt;and this on the Kodi end&lt;p&gt;
2333
2334 &lt;blockquote&gt;&lt;pre&gt;
2335 echo udp://@239.255.0.1:1234 \
2336 &gt; /storage/videos/screenstream.m3u
2337 &lt;/pre&gt;&lt;/blockquote&gt;
2338
2339 &lt;p&gt;Note the trick to pick a valid pulseaudio source. It might not
2340 pick the one you need. This approach will of course lead to trouble
2341 if more than one source uses the same multicast port and address.
2342 Note the ttl-mc=1 setting, which limit the multicast packages to the
2343 local network. If the value is increased, your screen will be
2344 broadcasted further, one network &quot;hop&quot; for each increase (read up on
2345 multicast to learn more. :)!&lt;/p&gt;
2346
2347 &lt;p&gt;Having cracked how to get Kodi to receive multicast streams, I
2348 could use this VLC command to stream to the same multicast address.
2349 The image quality is way better than the rtsp approach, but gstreamer
2350 seem to be doing a better job.&lt;/p&gt;
2351
2352 &lt;blockquote&gt;&lt;pre&gt;
2353 cvlc screen:// --sout &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}&#39;
2354 &lt;/pre&gt;&lt;/blockquote&gt;
2355
2356 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2357 activities, please send Bitcoin donations to my address
2358 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2359 </description>
2360 </item>
2361
2362 <item>
2363 <title>What is the most supported MIME type in Debian in 2018?</title>
2364 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
2365 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
2366 <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
2367 <description>&lt;p&gt;Five years ago,
2368 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;I
2369 measured what the most supported MIME type in Debian was&lt;/a&gt;, by
2370 analysing the desktop files in all packages in the archive. Since
2371 then, the DEP-11 AppStream system has been put into production, making
2372 the task a lot easier. This made me want to repeat the measurement,
2373 to see how much things changed. Here are the new numbers, for
2374 unstable only this time:
2375
2376 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
2377
2378 &lt;pre&gt;
2379 count MIME type
2380 ----- -----------------------
2381 56 image/jpeg
2382 55 image/png
2383 49 image/tiff
2384 48 image/gif
2385 39 image/bmp
2386 38 text/plain
2387 37 audio/mpeg
2388 34 application/ogg
2389 33 audio/x-flac
2390 32 audio/x-mp3
2391 30 audio/x-wav
2392 30 audio/x-vorbis+ogg
2393 29 image/x-portable-pixmap
2394 27 inode/directory
2395 27 image/x-portable-bitmap
2396 27 audio/x-mpeg
2397 26 application/x-ogg
2398 25 audio/x-mpegurl
2399 25 audio/ogg
2400 24 text/html
2401 &lt;/pre&gt;
2402
2403 &lt;p&gt;The list was created like this using a sid chroot: &quot;cat
2404 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk &#39;/^
2405 - \S+\/\S+$/ {print $2 }&#39; | sort | uniq -c | sort -nr | head -20&quot;&lt;/p&gt;
2406
2407 &lt;p&gt;It is interesting to see how image formats have passed text/plain
2408 as the most announced supported MIME type. These days, thanks to the
2409 AppStream system, if you run into a file format you do not know, and
2410 want to figure out which packages support the format, you can find the
2411 MIME type of the file using &quot;file --mime &amp;lt;filename&amp;gt;&quot;, and then
2412 look up all packages announcing support for this format in their
2413 AppStream metadata (XML or .desktop file) using &quot;appstreamcli
2414 what-provides mimetype &amp;lt;mime-type&amp;gt;. For example if you, like
2415 me, want to know which packages support inode/directory, you can get a
2416 list like this:&lt;/p&gt;
2417
2418 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2419 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
2420 Package: anjuta
2421 Package: audacious
2422 Package: baobab
2423 Package: cervisia
2424 Package: chirp
2425 Package: dolphin
2426 Package: doublecmd-common
2427 Package: easytag
2428 Package: enlightenment
2429 Package: ephoto
2430 Package: filelight
2431 Package: gwenview
2432 Package: k4dirstat
2433 Package: kaffeine
2434 Package: kdesvn
2435 Package: kid3
2436 Package: kid3-qt
2437 Package: nautilus
2438 Package: nemo
2439 Package: pcmanfm
2440 Package: pcmanfm-qt
2441 Package: qweborf
2442 Package: ranger
2443 Package: sirikali
2444 Package: spacefm
2445 Package: spacefm
2446 Package: vifm
2447 %
2448 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2449
2450 &lt;p&gt;Using the same method, I can quickly discover that the Sketchup file
2451 format is not yet supported by any package in Debian:&lt;/p&gt;
2452
2453 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2454 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
2455 Could not find component providing &#39;mimetype::application/vnd.sketchup.skp&#39;.
2456 %
2457 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2458
2459 &lt;p&gt;Yesterday I used it to figure out which packages support the STL 3D
2460 format:&lt;/p&gt;
2461
2462 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2463 % appstreamcli what-provides mimetype application/sla|grep Package
2464 Package: cura
2465 Package: meshlab
2466 Package: printrun
2467 %
2468 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2469
2470 &lt;p&gt;PS: A new version of Cura was uploaded to Debian yesterday.&lt;/p&gt;
2471
2472 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2473 activities, please send Bitcoin donations to my address
2474 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2475 </description>
2476 </item>
2477
2478 <item>
2479 <title>Debian APT upgrade without enough free space on the disk...</title>
2480 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
2481 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
2482 <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
2483 <description>&lt;p&gt;Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
2484 for a while, and when I need to update it there is not enough free
2485 space on the disk for apt to do a normal &#39;apt upgrade&#39;. I normally
2486 would resolve the issue by doing &#39;apt install &amp;lt;somepackages&amp;gt;&#39; to
2487 upgrade only some of the packages in one batch, until the amount of
2488 packages to download fall below the amount of free space available.
2489 Today, I had about 500 packages to upgrade, and after a while I got
2490 tired of trying to install chunks of packages manually. I concluded
2491 that I did not have the spare hours required to complete the task, and
2492 decided to see if I could automate it. I came up with this small
2493 script which I call &#39;apt-in-chunks&#39;:&lt;/p&gt;
2494
2495 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2496 #!/bin/sh
2497 #
2498 # Upgrade packages when the disk is too full to upgrade every
2499 # upgradable package in one lump. Fetching packages to upgrade using
2500 # apt, and then installing using dpkg, to avoid changing the package
2501 # flag for manual/automatic.
2502
2503 set -e
2504
2505 ignore() {
2506 if [ &quot;$1&quot; ]; then
2507 grep -v &quot;$1&quot;
2508 else
2509 cat
2510 fi
2511 }
2512
2513 for p in $(apt list --upgradable | ignore &quot;$@&quot; |cut -d/ -f1 | grep -v &#39;^Listing...&#39;); do
2514 echo &quot;Upgrading $p&quot;
2515 apt clean
2516 apt install --download-only -y $p
2517 for f in /var/cache/apt/archives/*.deb; do
2518 if [ -e &quot;$f&quot; ]; then
2519 dpkg -i /var/cache/apt/archives/*.deb
2520 break
2521 fi
2522 done
2523 done
2524 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2525
2526 &lt;p&gt;The script will extract the list of packages to upgrade, try to
2527 download the packages needed to upgrade one package, install the
2528 downloaded packages using dpkg. The idea is to upgrade packages
2529 without changing the APT mark for the package (ie the one recording of
2530 the package was manually requested or pulled in as a dependency). To
2531 use it, simply run it as root from the command line. If it fail, try
2532 &#39;apt install -f&#39; to clean up the mess and run the script again. This
2533 might happen if the new packages conflict with one of the old
2534 packages. dpkg is unable to remove, while apt can do this.&lt;/p&gt;
2535
2536 &lt;p&gt;It take one option, a package to ignore in the list of packages to
2537 upgrade. The option to ignore a package is there to be able to skip
2538 the packages that are simply too large to unpack. Today this was
2539 &#39;ghc&#39;, but I have run into other large packages causing similar
2540 problems earlier (like TeX).&lt;/p&gt;
2541
2542 &lt;p&gt;Update 2018-07-08: Thanks to Paul Wise, I am aware of two
2543 alternative ways to handle this. The &quot;unattended-upgrades
2544 --minimal-upgrade-steps&quot; option will try to calculate upgrade sets for
2545 each package to upgrade, and then upgrade them in order, smallest set
2546 first. It might be a better option than my above mentioned script.
2547 Also, &quot;aptutude upgrade&quot; can upgrade single packages, thus avoiding
2548 the need for using &quot;dpkg -i&quot; in the script above.&lt;/p&gt;
2549
2550 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2551 activities, please send Bitcoin donations to my address
2552 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2553 </description>
2554 </item>
2555
2556 <item>
2557 <title>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
2558 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
2559 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
2560 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
2561 <description>&lt;p&gt;A new version of the
2562 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
2563 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
2564 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
2565 useful. It was uploaded the last few days, and the last update will
2566 enter testing tomorrow. See the
2567 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
2568 notes&lt;/a&gt; for the list of bug fixes and new features. Version 3.2
2569 was announced 6 days ago. We will try to get it into Debian as
2570 well.&lt;/p&gt;
2571
2572 &lt;p&gt;More information related to 3D printing is available on the
2573 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
2574 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
2575 in Debian.&lt;/p&gt;
2576
2577 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2578 activities, please send Bitcoin donations to my address
2579 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2580 </description>
2581 </item>
2582
2583 <item>
2584 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
2585 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
2586 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
2587 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
2588 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
2589 that the nice and user friendly 3D printer slicer software Cura just
2590 entered Debian Unstable. It consist of five packages,
2591 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
2592 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
2593 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
2594 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
2595 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
2596 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
2597 two, uranium and cura, entered Unstable yesterday. This should make
2598 it easier for Debian users to print on at least the Ultimaker class of
2599 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
2600 make life easier for at least me. :)&lt;/p&gt;
2601
2602 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
2603 happy to assist him in sponsoring the packages. With the introduction
2604 of Cura, Debian is up to three 3D printer slicers at your service,
2605 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
2606 printer, give it a go. :)&lt;/p&gt;
2607
2608 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
2609 team, flocking together on the
2610 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
2611 mailing list and the
2612 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
2613 IRC channel.&lt;/p&gt;
2614
2615 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
2616 version 3.0.3 and then update the entire set of packages to version
2617 3.1.0 which showed up the last few days.&lt;/p&gt;
2618 </description>
2619 </item>
2620
2621 <item>
2622 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
2623 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
2624 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
2625 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
2626 <description>&lt;p&gt;At my nearby maker space,
2627 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
2628 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
2629 on Windows and MacOS X than Linux, because the software involved had
2630 to be manually compiled and set up on Linux while premade packages
2631 worked out of the box on Windows and MacOS X. I found this annoying,
2632 as the software involved,
2633 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
2634 and should be trivial to get up and running on Linux if someone took
2635 the time to package it for the relevant distributions. I even found
2636 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
2637 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
2638 never resulted in the software showing up in Debian. So a few days
2639 ago I offered my help to try to improve the situation.&lt;/p&gt;
2640
2641 &lt;p&gt;Now I am very happy to see that all the packages required by a
2642 working Cura in Debian are uploaded into Debian and waiting in the NEW
2643 queue for the ftpmasters to have a look. You can track the progress
2644 on
2645 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
2646 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
2647
2648 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
2649 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
2650 queue&lt;/a&gt; while we work up updating the packages to the latest
2651 upstream version.&lt;/p&gt;
2652
2653 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
2654 to use and was unable to configure correctly for Ultimaker 2+ in the
2655 short time I spent on it, are already in Debian. If you are looking
2656 for 3D printer &quot;slicers&quot; and want something already available in
2657 Debian, check out
2658 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
2659 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
2660 The latter is a fork of the former.&lt;/p&gt;
2661
2662 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2663 activities, please send Bitcoin donations to my address
2664 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2665 </description>
2666 </item>
2667
2668 <item>
2669 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
2670 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
2671 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
2672 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
2673 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
2674 mobile cell towers. And this radio chatter is available for anyone
2675 with a radio receiver capable of receiving them. Details about the
2676 mobile phones with very good accuracy is of course collected by the
2677 phone companies, but this is not the topic of this blog post. The
2678 mobile phone radio chatter make it possible to figure out when a cell
2679 phone is nearby, as it include the SIM card ID (IMSI). By paying
2680 attention over time, one can see when a phone arrive and when it leave
2681 an area. I believe it would be nice to make this information more
2682 available to the general public, to make more people aware of how
2683 their phones are announcing their whereabouts to anyone that care to
2684 listen.&lt;/p&gt;
2685
2686 &lt;p&gt;I am very happy to report that we managed to get something
2687 visualizing this information up and running for
2688 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
2689 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
2690 library. The solution is based on the
2691 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
2692 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
2693 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
2694 Sone from the Computer Science department of the University of
2695 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
2696 IMSIs) as dots in a web browser graph, with lines to the dot
2697 representing mobile base station it is talking to. It was working in
2698 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
2699
2700 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
2701 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
2702 connected and visualize the visible cell phone towers using an
2703 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
2704 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
2705 grgsm_livemon_headless processes from
2706 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
2707 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
2708
2709 &lt;p&gt;The frequencies to listen to, are identified using a slightly
2710 patched scan-and-livemon (to set the --args values for each receiver),
2711 and the Hopglass data is generated using the
2712 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
2713 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
2714 more than four SDRs working. There is also a geographical map trying
2715 to show the location of the base stations, but I believe their
2716 coordinates are hardcoded to some random location in Germany, I
2717 believe. The code should be replaced with code to look up location in
2718 a text file, a sqlite database or one of the online databases
2719 mentioned in
2720 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
2721 issue for the topic&lt;/a&gt;.
2722
2723 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
2724 </description>
2725 </item>
2726
2727 <item>
2728 <title>Easier recipe to observe the cell phones around you</title>
2729 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
2730 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
2731 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
2732 <description>&lt;p&gt;A little more than a month ago I wrote
2733 &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
2734 to observe the SIM card ID (aka IMSI number) of mobile phones talking
2735 to nearby mobile phone base stations using Debian GNU/Linux and a
2736 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
2737 the location of people and equipment (like cars and trains) with an
2738 accuracy of a few kilometer. Since then we have worked to make the
2739 procedure even simpler, and it is now possible to do this without any
2740 manual frequency tuning and without building your own packages.&lt;/p&gt;
2741
2742 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
2743 package is now included in Debian testing and unstable, and the
2744 IMSI-catcher code no longer require root access to fetch and decode
2745 the GSM data collected using gr-gsm.&lt;/p&gt;
2746
2747 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
2748 clone of two python scripts:&lt;/p&gt;
2749
2750 &lt;ol&gt;
2751
2752 &lt;li&gt;Start with a Debian machine running the Buster version (aka
2753 testing).&lt;/li&gt;
2754
2755 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
2756 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
2757
2758 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
2759 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
2760
2761 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
2762
2763 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
2764 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
2765 stations and start listening for GSM packages on one of them.&lt;/li&gt;
2766
2767 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
2768 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
2769
2770 &lt;/ol&gt;
2771
2772 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
2773 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
2774 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
2775 work with RTL 8232 and other similar USB radio receivers you can get
2776 very cheaply
2777 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
2778 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
2779 and only use HackRF for fetching GSM data.&lt;/p&gt;
2780
2781 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
2782 frequencies at the time, so if you are going to track and count every
2783 cell phone around you, you need to listen to all the frequencies used.
2784 To listen to several frequencies, use the --numrecv argument to
2785 scan-and-livemon to use several receivers. Further, I am not sure if
2786 phones using 3G or 4G will show as talking GSM to base stations, so
2787 this approach might not see all phones around you. I typically see
2788 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
2789
2790 &lt;p&gt;I&#39;ve tried to run the scanner on a
2791 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
2792 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
2793 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
2794 stdout, I am told there it is caused by a buffer overflow between the
2795 radio and GNU Radio, caused by the program being unable to read the
2796 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
2797 where you started scan-and-livemon, you need a give the process more
2798 CPU power. Perhaps someone are able to optimize the code to a point
2799 where it become possible to set up RPi3 based GSM sniffers? I tried
2800 using Raspbian instead of Debian, but there seem to be something wrong
2801 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
2802 </description>
2803 </item>
2804
2805 <item>
2806 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
2807 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
2808 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
2809 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
2810 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
2811 web based ICT news magazine digi.no on
2812 &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
2813 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
2814 DVB-T software defined radios. The article refered to instructions
2815 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
2816 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;
2817
2818 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
2819 bypass apt), use pip to install pybombs (to bypass both apt and pip),
2820 and the ask pybombs to fetch and build everything you need from
2821 scratch. I wanted to see if I could do the same on the most recent
2822 Debian packages, but this did not work because pybombs tried to build
2823 stuff that no longer build with the most recent openssl library or
2824 some other version skew problem. While trying to get this recipe
2825 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
2826 and the only piece of software dependency missing in Debian was the
2827 gr-gsm package. I also found out that the lead upstream developer of
2828 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
2829 Debian packages provided in an Ubuntu PPA repository. All I needed to
2830 do was to dget the Debian source package and built it.&lt;/p&gt;
2831
2832 &lt;p&gt;The IMSI collector is a python script listening for packages on the
2833 loopback network device and printing to the terminal some specific GSM
2834 packages with IMSI numbers in them. The code is fairly short and easy
2835 to understand. The reason this work is because gr-gsm include a tool
2836 to read GSM data from a software defined radio like a DVB-T USB stick
2837 and other software defined radios, decode them and inject them into a
2838 network device on your Linux machine (using the loopback device by
2839 default). This proved to work just fine, and I&#39;ve been testing the
2840 collector for a few days now.&lt;/p&gt;
2841
2842 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
2843
2844 &lt;ol&gt;
2845
2846 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
2847
2848 &lt;li&gt;build and install the gr-gsm package available from
2849 &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;
2850
2851 &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;
2852
2853 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
2854 where it was started is filled with a stream of text (meaning you
2855 found a GSM station).&lt;/li&gt;
2856
2857 &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;
2858
2859 &lt;/ol&gt;
2860
2861 &lt;p&gt;To make it even easier in the future to get this sniffer up and
2862 running, I decided to package
2863 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
2864 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
2865 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
2866 Luckily the gnuradio maintainer has promised to help me, as I do not
2867 know much about gnuradio stuff yet.&lt;/p&gt;
2868
2869 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
2870 commercial tools like
2871 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
2872 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
2873 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
2874 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
2875 more people realise how their whereabouts when carrying a cell phone
2876 is easily tracked. Seeing the data flow on the screen, realizing that
2877 I live close to a police station and knowing that the police is also
2878 wearing cell phones, I wonder how hard it would be for criminals to
2879 track the position of the police officers to discover when there are
2880 police near by, or for foreign military forces to track the location
2881 of the Norwegian military forces, or for anyone to track the location
2882 of government officials...&lt;/p&gt;
2883
2884 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
2885 script mentioned above is only a fraction of the data broadcasted on
2886 the GSM network. It will only collect one frequency at the time,
2887 while a typical phone will be using several frequencies, and not all
2888 phones will be using the frequencies tracked by the grgsm_livemod
2889 program. Also, there is a lot of radio chatter being ignored by the
2890 simple_IMSI-catcher script, which would be collected by extending the
2891 parser code. I wonder if gr-gsm can be set up to listen to more than
2892 one frequency?&lt;/p&gt;
2893 </description>
2894 </item>
2895
2896 <item>
2897 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
2898 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
2899 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
2900 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
2901 <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;
2902
2903 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
2904 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
2905 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
2906 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
2907 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
2908 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
2909 price. The book is also available for download in electronic form as
2910 PDF, EPUB and Mobipocket, as can be
2911 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
2912 as a web page&lt;/a&gt;.&lt;/p&gt;
2913
2914 &lt;p&gt;This is the second book I publish (the first was the book
2915 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
2916 in
2917 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
2918 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
2919 and
2920 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
2921 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
2922 project. I hope
2923 &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
2924 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
2925 </description>
2926 </item>
2927
2928 <item>
2929 <title>Når nynorskoversettelsen svikter til eksamen...</title>
2930 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
2931 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
2932 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
2933 <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
2934 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
2935 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
2936 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
2937 på om den fri oversetterløsningen
2938 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
2939 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
2940
2941 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
2942
2943 &lt;blockquote&gt;
2944 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
2945 rolle og muligheter til å håndtere internasjonale utfordringer, som
2946 for eksempel flykningekrisen.&lt;/p&gt;
2947
2948 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
2949 på temaet:&lt;/p&gt;
2950 &lt;ol&gt;
2951 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
2952 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
2953 &lt;/ol&gt;
2954
2955 &lt;/blockquote&gt;
2956
2957 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
2958
2959 &lt;blockquote&gt;
2960 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
2961 andre aktørar og høve til å handtera internasjonale utfordringar, som
2962 til dømes *flykningekrisen.&lt;/p&gt;
2963
2964 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
2965 temaet:&lt;/p&gt;
2966
2967 &lt;ol&gt;
2968 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
2969 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
2970 &lt;/ol&gt;
2971
2972 &lt;/blockquote&gt;
2973
2974 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
2975 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
2976 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
2977 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
2978 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
2979 det er kanskje flisespikking. Det understreker vel bare at det alltid
2980 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
2981 </description>
2982 </item>
2983
2984 <item>
2985 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
2986 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
2987 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
2988 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
2989 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
2990 computers at the time, I often needed a way to detect if the machine
2991 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
2992 file or directory affected by the hang, the process (and possibly the
2993 shell) will hang too. So you want to be able to detect this without
2994 risking the detection process getting stuck too. It has not been
2995 obvious how to do this. When the hang has lasted a while, it is
2996 possible to find messages like these in dmesg:&lt;/p&gt;
2997
2998 &lt;p&gt;&lt;blockquote&gt;
2999 nfs: server nfsserver not responding, still trying
3000 &lt;br&gt;nfs: server nfsserver OK
3001 &lt;/blockquote&gt;&lt;/p&gt;
3002
3003 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
3004 be sure looking in dmesg is going to work. If there are lots of other
3005 messages in dmesg the lines might have rotated out of site before they
3006 are noticed.&lt;/p&gt;
3007
3008 &lt;p&gt;While reading through the nfs client implementation in linux kernel
3009 code, I came across some statistics that seem to give a way to detect
3010 it. The om_timeouts sunrpc value in the kernel will increase every
3011 time the above log entry is inserted into dmesg. And after digging a
3012 bit further, I discovered that this value show up in
3013 /proc/self/mountstats on Linux.&lt;/p&gt;
3014
3015 &lt;p&gt;The mountstats content seem to be shared between files using the
3016 same file system context, so it is enough to check one of the
3017 mountstats files to get the state of the mount point for the machine.
3018 I assume this will not show lazy umounted NFS points, nor NFS mount
3019 points in a different process context (ie with a different filesystem
3020 view), but that does not worry me.&lt;/p&gt;
3021
3022 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
3023
3024 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3025 [...]
3026 device /dev/mapper/Debian-var mounted on /var with fstype ext3
3027 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
3028 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
3029 age: 7863311
3030 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
3031 sec: flavor=1,pseudoflavor=1
3032 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
3033 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
3034 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
3035 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
3036 per-op statistics
3037 NULL: 0 0 0 0 0 0 0 0
3038 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
3039 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
3040 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
3041 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
3042 READLINK: 125 125 0 20472 18620 0 1112 1118
3043 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
3044 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
3045 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
3046 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
3047 SYMLINK: 903 903 0 233428 245488 6 5865 5917
3048 MKNOD: 80 80 0 20148 21760 0 299 304
3049 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
3050 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
3051 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
3052 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
3053 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
3054 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
3055 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
3056 FSINFO: 2 2 0 232 328 0 1 1
3057 PATHCONF: 1 1 0 116 140 0 0 0
3058 COMMIT: 0 0 0 0 0 0 0 0
3059
3060 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
3061 [...]
3062 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3063
3064 &lt;p&gt;The key number to look at is the third number in the per-op list.
3065 It is the number of NFS timeouts experiences per file system
3066 operation. Here 22 write timeouts and 5 access timeouts. If these
3067 numbers are increasing, I believe the machine is experiencing NFS
3068 hang. Unfortunately the timeout value do not start to increase right
3069 away. The NFS operations need to time out first, and this can take a
3070 while. The exact timeout value depend on the setup. For example the
3071 defaults for TCP and UDP mount points are quite different, and the
3072 timeout value is affected by the soft, hard, timeo and retrans NFS
3073 mount options.&lt;/p&gt;
3074
3075 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
3076 Enterprise Linux for getting the timeout count is to peek in /proc/.
3077 But according to
3078 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
3079 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
3080 command can be used to get these timeout values. But this do not work
3081 on Linux, as far as I can tell. I
3082 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
3083 but have not seen any replies yet.&lt;/p&gt;
3084
3085 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
3086 experiencing NFS hangs? Is there a way to detect which processes are
3087 affected? Is there a way to get the NFS mount going quickly once the
3088 network problem causing the NFS hang has been cleared? I would very
3089 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
3090 </description>
3091 </item>
3092
3093 <item>
3094 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
3095 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
3096 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</guid>
3097 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
3098 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
3099 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
3100 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
3101 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
3102 we are working on the proof reading to ensure consistent language and
3103 use of correct computer science terms. The plan is to make the book
3104 available on paper, as well as in electronic form. For that to
3105 happen, the proof reading must be completed and all the figures need
3106 to be translated. If you want to help out, get in touch.&lt;/p&gt;
3107
3108 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
3109
3110 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
3111 pages) of the book created every morning is available for
3112 proofreading. If you find any errors, please
3113 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
3114 Weblate and correct the error&lt;/a&gt;. The
3115 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
3116 of the translation including figures&lt;/a&gt; is a useful source for those
3117 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
3118 </description>
3119 </item>
3120
3121 <item>
3122 <title>Unlimited randomness with the ChaosKey?</title>
3123 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
3124 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
3125 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
3126 <description>&lt;p&gt;A few days ago I ordered a small batch of
3127 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
3128 USB dongle for generating entropy created by Bdale Garbee and Keith
3129 Packard. Yesterday it arrived, and I am very happy to report that it
3130 work great! According to its designers, to get it to work out of the
3131 box, you need the Linux kernel version 4.1 or later. I tested on a
3132 Debian Stretch machine (kernel version 4.9), and there it worked just
3133 fine, increasing the available entropy very quickly. I wrote a small
3134 test oneliner to test. It first print the current entropy level,
3135 drain /dev/random, and then print the entropy level for five seconds.
3136 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
3137
3138 &lt;blockquote&gt;&lt;pre&gt;
3139 % cat /proc/sys/kernel/random/entropy_avail; \
3140 dd bs=1M if=/dev/random of=/dev/null count=1; \
3141 for n in $(seq 1 5); do \
3142 cat /proc/sys/kernel/random/entropy_avail; \
3143 sleep 1; \
3144 done
3145 300
3146 0+1 oppføringer inn
3147 0+1 oppføringer ut
3148 28 byte kopiert, 0,000264565 s, 106 kB/s
3149 4
3150 8
3151 12
3152 17
3153 21
3154 %
3155 &lt;/pre&gt;&lt;/blockquote&gt;
3156
3157 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
3158 application requiring random bits (like a HTTPS enabled web server)
3159 will halt and wait for more entrpy. And here is the situation with
3160 the ChaosKey inserted:&lt;/p&gt;
3161
3162 &lt;blockquote&gt;&lt;pre&gt;
3163 % cat /proc/sys/kernel/random/entropy_avail; \
3164 dd bs=1M if=/dev/random of=/dev/null count=1; \
3165 for n in $(seq 1 5); do \
3166 cat /proc/sys/kernel/random/entropy_avail; \
3167 sleep 1; \
3168 done
3169 1079
3170 0+1 oppføringer inn
3171 0+1 oppføringer ut
3172 104 byte kopiert, 0,000487647 s, 213 kB/s
3173 433
3174 1028
3175 1031
3176 1035
3177 1038
3178 %
3179 &lt;/pre&gt;&lt;/blockquote&gt;
3180
3181 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
3182 someone want to buy one here in Norway. :)&lt;/p&gt;
3183
3184 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
3185 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
3186 recording illuminating&lt;/a&gt;. It explains exactly what the source of
3187 randomness is, if you are unable to spot it from the schema drawing
3188 available from the ChaosKey web site linked at the start of this blog
3189 post.&lt;/p&gt;
3190 </description>
3191 </item>
3192
3193 <item>
3194 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
3195 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
3196 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
3197 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
3198 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
3199 web servers, and who own the network equipment it is flowing through?
3200 It is possible to get a glimpse of this from using traceroute, but it
3201 is hard to find all the details. Many years ago, I wrote a system to
3202 map the Norwegian Internet (trying to figure out if our plans for a
3203 network game service would get low enough latency, and who we needed
3204 to talk to about setting up game servers close to the users. Back
3205 then I used traceroute output from many locations (I asked my friends
3206 to run a script and send me their traceroute output) to create the
3207 graph and the map. The output from traceroute typically look like
3208 this:
3209
3210 &lt;p&gt;&lt;pre&gt;
3211 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
3212 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
3213 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
3214 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
3215 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
3216 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
3217 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
3218 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
3219 8 * * *
3220 9 * * *
3221 [...]
3222 &lt;/pre&gt;&lt;/p&gt;
3223
3224 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
3225 network equipment involved in getting the data traffic from me to the
3226 www.stortinget.no server, and how long it took in milliseconds for a
3227 package to reach the equipment and return to me. Three packages are
3228 sent, and some times the packages do not follow the same path. This
3229 is shown for hop 5, where three different IP addresses replied to the
3230 traceroute request.&lt;/p&gt;
3231
3232 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
3233 implementations I use are traceroute (using ICMP packages) mtr (can do
3234 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
3235 traceroute and a lot of other capabilities). All of them are easily
3236 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
3237
3238 &lt;p&gt;This time around, I wanted to know the geographic location of
3239 different route points, to visualize how visiting a web page spread
3240 information about the visit to a lot of servers around the globe. The
3241 background is that a web site today often will ask the browser to get
3242 from many servers the parts (for example HTML, JSON, fonts,
3243 JavaScript, CSS, video) required to display the content. This will
3244 leak information about the visit to those controlling these servers
3245 and anyone able to peek at the data traffic passing by (like your ISP,
3246 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
3247
3248 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
3249 www.stortinget.no. It is read daily by all members of parliament and
3250 their staff, as well as political journalists, activits and many other
3251 citizens of Norway. A visit to the www.stortinget.no web site will
3252 ask your browser to contact 8 other servers: ajax.googleapis.com,
3253 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
3254 stats.g.doubleclick.net, www.google-analytics.com,
3255 www.googletagmanager.com and www.netigate.se. I extracted this by
3256 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
3257 Stortinget web page and tell me all the URLs PhantomJS downloaded to
3258 render the page (in HAR format using
3259 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
3260 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
3261 to do this). My goal is to visualize network traces to all IP
3262 addresses behind these DNS names, do show where visitors personal
3263 information is spread when visiting the page.&lt;/p&gt;
3264
3265 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
3266 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;
3267
3268 &lt;p&gt;When I had a look around for options, I could not find any good
3269 free software tools to do this, and decided I needed my own traceroute
3270 wrapper outputting KML based on locations looked up using GeoIP. KML
3271 is easy to work with and easy to generate, and understood by several
3272 of the GIS tools I have available. I got good help from by NUUG
3273 colleague Anders Einar with this, and the result can be seen in
3274 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
3275 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
3276 free GeoIP databases I could find (and the for-pay databases my
3277 friends had access to) is not up to the task. The IP addresses of
3278 central Internet infrastructure would typically be placed near the
3279 controlling companies main office, and not where the router is really
3280 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
3281 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
3282
3283 &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
3284 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;
3285
3286 &lt;p&gt;I also had a look at the visual traceroute graph created by
3287 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
3288 showing IP network ownership (aka AS owner) for the IP address in
3289 question.
3290 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
3291 graph display a lot of useful information about the traceroute in SVG
3292 format&lt;/a&gt;, and give a good indication on who control the network
3293 equipment involved, but it do not include geolocation. This graph
3294 make it possible to see the information is made available at least for
3295 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
3296 3 Communications and NetDNA.&lt;/p&gt;
3297
3298 &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
3299 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;
3300
3301 &lt;p&gt;In the process, I came across the
3302 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
3303 Salim Gasmi. Its methology of combining guesses based on DNS names,
3304 various location databases and finally use latecy times to rule out
3305 candidate locations seemed to do a very good job of guessing correct
3306 geolocation. But it could only do one trace at the time, did not have
3307 a sensor in Norway and did not make the geolocations easily available
3308 for postprocessing. So I contacted the developer and asked if he
3309 would be willing to share the code (he refused until he had time to
3310 clean it up), but he was interested in providing the geolocations in a
3311 machine readable format, and willing to set up a sensor in Norway. So
3312 since yesterday, it is possible to run traces from Norway in this
3313 service thanks to a sensor node set up by
3314 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
3315 trace in KML format for further processing.&lt;/p&gt;
3316
3317 &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
3318 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;
3319
3320 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
3321 Denmark, Germany, Holland and Ireland. Plenty of places where the
3322 Snowden confirmations verified the traffic is read by various actors
3323 without your best interest as their top priority.&lt;/p&gt;
3324
3325 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
3326 over all the hosts behind the urls imported by www.stortinget.no and
3327 ask for the KML file from GeoTraceroute, and create a combined KML
3328 file with all the traces (unfortunately only one of the IP addresses
3329 behind the DNS name is traced this time. To get them all, one would
3330 have to request traces using IP number instead of DNS names from
3331 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
3332
3333 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
3334 the IP traffic moves and who control the boxes involved in moving it.
3335 And every time the link crosses for example the Swedish border, we can
3336 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
3337 Britain and NSA in USA and cables around the globe. (Hm, what should
3338 we tell them? :) Keep that in mind if you ever send anything
3339 unencrypted over the Internet.&lt;/p&gt;
3340
3341 &lt;p&gt;PS: KML files are drawn using
3342 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
3343 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
3344 Marble. There are heaps of other options too.&lt;/p&gt;
3345
3346 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3347 activities, please send Bitcoin donations to my address
3348 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3349 </description>
3350 </item>
3351
3352 <item>
3353 <title>Appstream just learned how to map hardware to packages too!</title>
3354 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
3355 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
3356 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
3357 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
3358 readers probably know, I have been working on the
3359 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
3360 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
3361 it easier for users to figure out what to install to get a given piece
3362 of hardware to work in Debian, and a key part of this system is a way
3363 to map hardware to packages. Isenkram have its own mapping database,
3364 and also uses data provided by each package using the AppStream
3365 metadata format. And today,
3366 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
3367 Debian learned to look up hardware the same way Isenkram is doing it,
3368 ie using fnmatch():&lt;/p&gt;
3369
3370 &lt;p&gt;&lt;pre&gt;
3371 % appstreamcli what-provides modalias \
3372 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
3373 Identifier: pymissile [generic]
3374 Name: pymissile
3375 Summary: Control original Striker USB Missile Launcher
3376 Package: pymissile
3377 % appstreamcli what-provides modalias usb:v0694p0002d0000
3378 Identifier: libnxt [generic]
3379 Name: libnxt
3380 Summary: utility library for talking to the LEGO Mindstorms NXT brick
3381 Package: libnxt
3382 ---
3383 Identifier: t2n [generic]
3384 Name: t2n
3385 Summary: Simple command-line tool for Lego NXT
3386 Package: t2n
3387 ---
3388 Identifier: python-nxt [generic]
3389 Name: python-nxt
3390 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
3391 Package: python-nxt
3392 ---
3393 Identifier: nbc [generic]
3394 Name: nbc
3395 Summary: C compiler for LEGO Mindstorms NXT bricks
3396 Package: nbc
3397 %
3398 &lt;/pre&gt;&lt;/p&gt;
3399
3400 &lt;p&gt;A similar query can be done using the combined AppStream and
3401 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
3402
3403 &lt;p&gt;&lt;pre&gt;
3404 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
3405 pymissile
3406 % isenkram-lookup usb:v0694p0002d0000
3407 libnxt
3408 nbc
3409 python-nxt
3410 t2n
3411 %
3412 &lt;/pre&gt;&lt;/p&gt;
3413
3414 &lt;p&gt;You can find modalias values relevant for your machine using
3415 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
3416
3417 &lt;p&gt;If you want to make this system a success and help Debian users
3418 make the most of the hardware they have, please
3419 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
3420 AppStream metadata for your package following the guidelines&lt;/a&gt;
3421 documented in the wiki. So far only 11 packages provide such
3422 information, among the several hundred hardware specific packages in
3423 Debian. The Isenkram database on the other hand contain 101 packages,
3424 mostly related to USB dongles. Most of the packages with hardware
3425 mapping in AppStream are LEGO Mindstorms related, because I have, as
3426 part of my involvement in
3427 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
3428 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
3429 complete set of packages in Debian for that particular hardware. The
3430 team also got a nice Christmas present today. The
3431 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
3432 package&lt;/a&gt; made it into Debian. With this package in place, it is
3433 now possible to use the LEGO Mindstorms NXT unit with only free
3434 software, as the nxt-firmware package contain the source and firmware
3435 binaries for the NXT brick.&lt;/p&gt;
3436
3437 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3438 activities, please send Bitcoin donations to my address
3439 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3440 </description>
3441 </item>
3442
3443 <item>
3444 <title>Isenkram updated with a lot more hardware-package mappings</title>
3445 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
3446 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
3447 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
3448 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
3449 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
3450 and install packages to get your hardware dongles to work, is still
3451 going strong. It is a system to look up the hardware present on or
3452 connected to the current system, and map the hardware to Debian
3453 packages. It can either be done using the tools in isenkram-cli or
3454 using the user space daemon in the isenkram package. The latter will
3455 notify you, when inserting new hardware, about what packages to
3456 install to get the dongle working. It will even provide a button to
3457 click on to ask packagekit to install the packages.&lt;/p&gt;
3458
3459 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
3460
3461 &lt;p&gt;&lt;pre&gt;
3462 % isenkram-lookup
3463 bluez
3464 cheese
3465 ethtool
3466 fprintd
3467 fprintd-demo
3468 gkrellm-thinkbat
3469 hdapsd
3470 libpam-fprintd
3471 pidgin-blinklight
3472 thinkfan
3473 tlp
3474 tp-smapi-dkms
3475 tp-smapi-source
3476 tpb
3477 %
3478 &lt;/pre&gt;&lt;/p&gt;
3479
3480 &lt;p&gt;It can also list the firware package providing firmware requested
3481 by the load kernel modules, which in my case is an empty list because
3482 I have all the firmware my machine need:
3483
3484 &lt;p&gt;&lt;pre&gt;
3485 % /usr/sbin/isenkram-autoinstall-firmware -l
3486 info: did not find any firmware files requested by loaded kernel modules. exiting
3487 %
3488 &lt;/pre&gt;&lt;/p&gt;
3489
3490 &lt;p&gt;The last few days I had a look at several of the around 250
3491 packages in Debian with udev rules. These seem like good candidates
3492 to install when a given hardware dongle is inserted, and I found
3493 several that should be proposed by isenkram. I have not had time to
3494 check all of them, but am happy to report that now there are 97
3495 packages packages mapped to hardware by Isenkram. 11 of these
3496 packages provide hardware mapping using AppStream, while the rest are
3497 listed in the modaliases file provided in isenkram.&lt;/p&gt;
3498
3499 &lt;p&gt;These are the packages with hardware mappings at the moment. The
3500 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
3501 support using AppStream, for everyone to use:&lt;/p&gt;
3502
3503 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
3504 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
3505 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
3506 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
3507 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
3508 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
3509 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
3510 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
3511 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
3512 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
3513 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
3514 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
3515 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
3516 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
3517 pcscd, pidgin-blinklight, printer-driver-splix,
3518 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
3519 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
3520 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
3521 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
3522 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
3523 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
3524 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
3525 xserver-xorg-video-vmware, yubikey-personalization and
3526 zd1211-firmware&lt;/p&gt;
3527
3528 &lt;p&gt;If you know of other packages, please let me know with a wishlist
3529 bug report against the isenkram-cli package, and ask the package
3530 maintainer to
3531 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
3532 metadata according to the guidelines&lt;/a&gt; to provide the information
3533 for everyone. In time, I hope to get rid of the isenkram specific
3534 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
3535
3536 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
3537 much hardware, and suggest that the package with with any ethernet
3538 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
3539 the details. I hope the maintainer find time to address it soon. In
3540 the mean time I provide an override in isenkram.&lt;/p&gt;
3541 </description>
3542 </item>
3543
3544 <item>
3545 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
3546 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
3547 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
3548 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
3549 <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;
3550
3551 &lt;p&gt;In my early years, I played
3552 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
3553 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
3554 space, and reached the &#39;elite&#39; fighting status before I moved on. The
3555 original Elite game was available on Commodore 64 and the IBM PC
3556 edition I played had a 64 KB executable. I am still impressed today
3557 that the authors managed to squeeze both a 3D engine and details about
3558 more than 2000 planet systems across 7 galaxies into a binary so
3559 small.&lt;/p&gt;
3560
3561 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
3562 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
3563 really have time to test it properly until a few days ago. It was
3564 great to discover that my old knowledge about trading routes were
3565 still valid. But my fighting and flying abilities were gone, so I had
3566 to retrain to be able to dock on a space station. And I am still not
3567 able to make much resistance when I am attacked by pirates, so I
3568 bougth and mounted the most powerful laser in the rear to be able to
3569 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
3570
3571 &lt;p&gt;When playing Elite in the late eighties, I had to discover
3572 everything on my own, and I had long lists of prices seen on different
3573 planets to be able to decide where to trade what. This time I had the
3574 advantages of the
3575 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
3576 where information about each planet is easily available with common
3577 price ranges and suggested trading routes. This improved my ability
3578 to earn money and I have been able to earn enough to buy a lot of
3579 useful equipent in a few days. I believe I originally played for
3580 months before I could get a docking computer, while now I could get it
3581 after less then a week.&lt;/p&gt;
3582
3583 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
3584 space, you should try out Oolite. It is available for Linux, MacOSX
3585 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
3586
3587 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3588 activities, please send Bitcoin donations to my address
3589 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3590 </description>
3591 </item>
3592
3593 <item>
3594 <title>Quicker Debian installations using eatmydata</title>
3595 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
3596 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
3597 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
3598 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
3599 installation system, observing how using
3600 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
3601 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
3602 speedup around 20-40 percent for Debian Edu, where we install around
3603 1000 packages from within the installer. The eatmydata package
3604 provide a way to disable/delay file system flushing. This is a bit
3605 risky in the general case, as files that should be stored on disk will
3606 stay only in memory a bit longer than expected, causing problems if a
3607 machine crashes at an inconvenient time. But for an installation, if
3608 the machine crashes during installation the process is normally
3609 restarted, and avoiding disk operations as much as possible to speed
3610 up the process make perfect sense.
3611
3612 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
3613 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
3614 but did not have time to push it any further. But a few months ago I
3615 picked it up again and worked with the libeatmydata package maintainer
3616 Mattia Rizzolo to make it easier for everyone to get this installation
3617 speedup in Debian. Thanks to our cooperation There is now an
3618 eatmydata-udeb package in Debian testing and unstable, and simply
3619 enabling/installing it in debian-installer (d-i) is enough to get the
3620 quicker installations. It can be enabled using preseeding. The
3621 following untested kernel argument should do the trick:&lt;/p&gt;
3622
3623 &lt;blockquote&gt;&lt;pre&gt;
3624 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
3625 &lt;/pre&gt;&lt;/blockquote&gt;
3626
3627 &lt;p&gt;This should ask d-i to install the package inside the d-i
3628 environment early in the installation sequence. Having it installed
3629 in d-i in turn will make sure the relevant scripts are called just
3630 after debootstrap filled /target/ with the freshly installed Debian
3631 system to configure apt to run dpkg with eatmydata. This is enough to
3632 speed up the installation process. There is a proposal to
3633 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
3634 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
3635 tested its impact.&lt;/p&gt;
3636
3637 </description>
3638 </item>
3639
3640 <item>
3641 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
3642 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
3643 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
3644 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
3645 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
3646 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
3647 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
3648 elever over det ganske land skal levere inn hvert år. Det mange ikke
3649 vet er at selv om de kommersielle alternativene
3650 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
3651 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
3652 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
3653 utmerket fri programvarealternativ som kan. Oversetterverktøyet
3654 Apertium har støtte for en rekke språkkombinasjoner, og takket være
3655 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
3656 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
3657 nynorsk, og få den automatoversatt til det andre skriftspråket.
3658 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
3659 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
3660 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
3661 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
3662 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
3663 teksten din i webskjemaet der.
3664
3665 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
3666 teknologien kan du enten installere pakken
3667 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
3668 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
3669 api.apertium.org. Se
3670 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
3671 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
3672 denne teksten som ble skrevet på bokmål over maskinoversatt til
3673 nynorsk.&lt;/p&gt;
3674
3675 &lt;hr/&gt;
3676
3677 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
3678 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
3679 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
3680 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
3681 veit er at sjølv om dei kommersielle alternativa
3682 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
3683 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
3684 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
3685 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
3686 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
3687 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
3688 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
3689 nynorsk, og få den *automatoversatt til det andre skriftspråket.
3690 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
3691 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
3692 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
3693 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
3694 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
3695 teksta di i *webskjemaet der.
3696
3697 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
3698 teknologien kan du anten installera pakken
3699 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
3700 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
3701 *api.*apertium.org. Sjå
3702 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
3703 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
3704 for denne teksta som vart skreva på bokmål over *maskinoversatt til
3705 nynorsk.&lt;/p&gt;
3706 </description>
3707 </item>
3708
3709 <item>
3710 <title>Coz profiler for multi-threaded software is now in Debian</title>
3711 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
3712 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
3713 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
3714 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
3715 profiler able to run benchmarking experiments on the instrumented
3716 multi-threaded program, finally
3717 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
3718 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
3719 months since
3720 &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
3721 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
3722 it suitable for Debian. There are still issues with clang
3723 compatibility, inline assembly only working x86 and minimized
3724 JavaScript libraries.&lt;/p&gt;
3725
3726 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
3727
3728 &lt;p&gt;&lt;blockquote&gt;
3729 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
3730 &lt;/blockquote&gt;&lt;/p&gt;
3731
3732 &lt;p&gt;This will produce a profile.coz file in the current working
3733 directory with the profiling information. This is then given to a
3734 JavaScript application provided in the package and available from
3735 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
3736 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
3737
3738 &lt;p&gt;&lt;blockquote&gt;
3739 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
3740 &lt;/blockquote&gt;&lt;/p&gt;
3741
3742 &lt;p&gt;See the project home page and the
3743 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
3744 ;login: article on Coz&lt;/a&gt; for more information on how it is
3745 working.&lt;/p&gt;
3746 </description>
3747 </item>
3748
3749 <item>
3750 <title>My own self balancing Lego Segway</title>
3751 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
3752 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
3753 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
3754 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
3755 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
3756 present. It had been on my wishlist for a while, because I wanted to
3757 build a Segway like balancing lego robot. I had already built
3758 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
3759 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
3760 NXT kit as the balance sensor, but it was not working very well. It
3761 could balance for a while, but was very sensitive to the light
3762 condition in the room and the reflective properties of the surface and
3763 would fall over after a short while. I wanted something more robust,
3764 and had
3765 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
3766 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
3767 wishlist for some years before it suddenly showed up as a gift from my
3768 loved ones. :)&lt;/p&gt;
3769
3770 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
3771 since then. But that changed some days ago, when I was searching for
3772 lego segway information and came across a recipe from HiTechnic for
3773 building
3774 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
3775 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
3776 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
3777 code&lt;/a&gt; was included, so it was just a question of putting it all
3778 together. And thanks to the great work of many Debian developers, the
3779 compiler needed to build the source for the NXT is already included in
3780 Debian, so I was read to go in less than an hour. The resulting robot
3781 do not look very impressive in its simplicity:&lt;/p&gt;
3782
3783 &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;
3784
3785 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
3786 design from HiTechnic, I had to comment out the last task
3787 (taskControl). I simply placed /* and */ around it get the program
3788 working without that sensor present. Now it balances just fine until
3789 the battery status run low:&lt;/p&gt;
3790
3791 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
3792 &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;
3793 &lt;/video&gt;&lt;/p&gt;
3794
3795 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
3796 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
3797
3798 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
3799 they need to work with LEGO in Debian and all our derivative
3800 distributions like Ubuntu, check out
3801 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
3802 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
3803 RCX and NXT controller (no EV3), and would like to make sure the
3804 Debian tools needed to program the systems I own work as they
3805 should.&lt;/p&gt;
3806 </description>
3807 </item>
3808
3809 <item>
3810 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
3811 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
3812 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
3813 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
3814 <description>&lt;p&gt;In July
3815 &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
3816 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
3817 the ability to receive SMS messages (aka without a cell phone). It is
3818 time to share some experiences and provide an updated setup.&lt;/p&gt;
3819
3820 &lt;p&gt;The Signal app have worked fine for several months now, and I use
3821 it regularly to chat with my loved ones. I had a major snag at the
3822 end of my summer vacation, when the the app completely forgot my
3823 setup, identity and keys. The reason behind this major mess was
3824 running out of disk space. To avoid that ever happening again I have
3825 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
3826 roll back to an earlier version if the files are wiped by mistake. I
3827 had to use it once after introducing the git backup. When rolling
3828 back to an earlier version, one need to use the &#39;reset session&#39; option
3829 in Signal to get going, and notify the people you talk with about the
3830 problem. I assume there is some sequence number tracking in the
3831 protocol to detect rollback attacks. The git repository is rather big
3832 (674 MiB so far), but I have not tried to figure out if some of the
3833 content can be added to a .gitignore file due to lack of spare
3834 time.&lt;/p&gt;
3835
3836 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
3837 make it impossible to send messages using Signal. I could still
3838 receive them, but had to patch the code with a new timestamp to send.
3839 I believe the timeout is added by the developers to force people to
3840 upgrade to the latest version of the app, even when there is no
3841 protocol changes, to reduce the version skew among the user base and
3842 thus try to keep the number of support requests down.&lt;/p&gt;
3843
3844 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
3845 making the old patch fail to apply cleanly. Below is an updated
3846 patch, including the shell wrapper I use to start Signal. The
3847 original version required a new user to locate the JavaScript console
3848 and call a function from there. I got help from a friend with more
3849 JavaScript knowledge than me to modify the code to provide a GUI
3850 button instead. This mean that to get started you just need to run
3851 the wrapper and click the &#39;Register without mobile phone&#39; to get going
3852 now. I&#39;ve also modified the timeout code to always set it to 90 days
3853 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
3854
3855 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
3856
3857 &lt;ol&gt;
3858
3859 &lt;li&gt;First, install required packages to get the source code and the
3860 browser you need. Signal only work with Chrome/Chromium, as far as I
3861 know, so you need to install it.
3862
3863 &lt;pre&gt;
3864 apt install git tor chromium
3865 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3866 &lt;/pre&gt;&lt;/li&gt;
3867
3868 &lt;li&gt;Modify the source code using command listed in the the patch
3869 block below.&lt;/li&gt;
3870
3871 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
3872 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
3873
3874 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
3875 number you can receive calls to the next minute, receive the
3876 verification code and enter it into the form field and press
3877 &#39;Register&#39;. Note, the phone number you use will be user Signal
3878 username, ie the way others can find you on Signal.&lt;/li&gt;
3879
3880 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
3881 not show up in the contact list until you restart Signal, and there is
3882 no way to assign names to Contacts. There is also no way to create or
3883 update chat groups. I suspect this is because the web app do not have
3884 a associated contact database.&lt;/li&gt;
3885
3886 &lt;/ol&gt;
3887
3888 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
3889 main author moxie0 reject federation and accept dependencies to major
3890 corporations like Google (part of the code is fetched from Google) and
3891 Amazon (the central coordination point is owned by Amazon). See for
3892 example
3893 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
3894 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
3895 view on these issues. But the network effect is strong in this case,
3896 and several of the people I want to communicate with already use
3897 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
3898 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
3899 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
3900 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
3901 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
3902 working on Debian Stable.&lt;/p&gt;
3903
3904 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
3905 working. It switch to the production servers, disable to timeout,
3906 make registration easier and add the shell wrapper:&lt;/p&gt;
3907
3908 &lt;pre&gt;
3909 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
3910 diff --git a/js/background.js b/js/background.js
3911 index 24b4c1d..579345f 100644
3912 --- a/js/background.js
3913 +++ b/js/background.js
3914 @@ -33,9 +33,9 @@
3915 });
3916 });
3917
3918 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
3919 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
3920 var SERVER_PORTS = [80, 4433, 8443];
3921 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
3922 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
3923 var messageReceiver;
3924 window.getSocketStatus = function() {
3925 if (messageReceiver) {
3926 diff --git a/js/expire.js b/js/expire.js
3927 index 639aeae..beb91c3 100644
3928 --- a/js/expire.js
3929 +++ b/js/expire.js
3930 @@ -1,6 +1,6 @@
3931 ;(function() {
3932 &#39;use strict&#39;;
3933 - var BUILD_EXPIRATION = 0;
3934 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
3935
3936 window.extension = window.extension || {};
3937
3938 diff --git a/js/views/install_view.js b/js/views/install_view.js
3939 index 7816f4f..1d6233b 100644
3940 --- a/js/views/install_view.js
3941 +++ b/js/views/install_view.js
3942 @@ -38,7 +38,8 @@
3943 return {
3944 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
3945 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
3946 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
3947 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
3948 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
3949 };
3950 },
3951 clearQR: function() {
3952 diff --git a/options.html b/options.html
3953 index dc0f28e..8d709f6 100644
3954 --- a/options.html
3955 +++ b/options.html
3956 @@ -14,7 +14,10 @@
3957 &amp;lt;div class=&#39;nav&#39;&gt;
3958 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
3959 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
3960 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
3961 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
3962 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
3963 +
3964 + &amp;lt;/div&gt;
3965 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
3966 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
3967 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
3968 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
3969 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
3970 @@ -0,0 +1,12 @@
3971 +#!/bin/sh
3972 +set -e
3973 +cd $(dirname $0)
3974 +mkdir -p userdata
3975 +userdata=&quot;`pwd`/userdata&quot;
3976 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
3977 + (cd $userdata &amp;&amp; git init)
3978 +fi
3979 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
3980 +exec chromium \
3981 + --proxy-server=&quot;socks://localhost:9050&quot; \
3982 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
3983 EOF
3984 chmod a+rx run-signal-app
3985 &lt;/pre&gt;
3986
3987 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3988 activities, please send Bitcoin donations to my address
3989 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3990 </description>
3991 </item>
3992
3993 <item>
3994 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
3995 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
3996 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
3997 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
3998 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
3999 system&lt;/a&gt; provide a practical and easy way to figure out which
4000 packages support the hardware in a given machine. The command line
4001 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
4002 convenient way to list and install packages relevant for the current
4003 hardware during system installation, both user space packages and
4004 firmware packages. The GUI background daemon on the other hand provide
4005 a pop-up proposing to install packages when a new dongle is inserted
4006 while using the computer. For example, if you plug in a smart card
4007 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
4008 that package isn&#39;t already installed, and if you plug in a USB video
4009 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
4010 cheese is currently missing. This already work just fine.&lt;/p&gt;
4011
4012 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
4013 package names. When I started no such database existed in Debian, so
4014 I made my own data set and included it with the isenkram package and
4015 made isenkram fetch the latest version of this database from git using
4016 http. This way the isenkram users would get updated package proposals
4017 as soon as I learned more about hardware related packages.&lt;/p&gt;
4018
4019 &lt;p&gt;The hardware is identified using modalias strings. The modalias
4020 design is from the Linux kernel where most hardware descriptors are
4021 made available as a strings that can be matched using filename style
4022 globbing. It handle USB, PCI, DMI and a lot of other hardware related
4023 identifiers.&lt;/p&gt;
4024
4025 &lt;p&gt;The downside to the Isenkram specific database is that there is no
4026 information about relevant distribution / Debian version, making
4027 isenkram propose obsolete packages too. But along came AppStream, a
4028 cross distribution mechanism to store and collect metadata about
4029 software packages. When I heard about the proposal, I contacted the
4030 people involved and suggested to add a hardware matching rule using
4031 modalias strings in the specification, to be able to use AppStream for
4032 mapping hardware to packages. This idea was accepted and AppStream is
4033 now a great way for a package to announce the hardware it support in a
4034 distribution neutral way. I wrote
4035 &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
4036 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
4037 December. If you have a hardware related package in Debian, please
4038 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
4039
4040 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
4041 RCX or NXT unit, announce this support using AppStream. The effect is
4042 that when you insert such LEGO robot controller into your Debian
4043 machine, Isenkram will propose to install the packages needed to get
4044 it working. The intention is that this should allow the local user to
4045 start programming his robot controller right away without having to
4046 guess what packages to use or which permissions to fix.&lt;/p&gt;
4047
4048 &lt;p&gt;But when I sat down with my son the other day to program our NXT
4049 unit using his Debian Stretch computer, I discovered something
4050 annoying. The local console user (ie my son) did not get access to
4051 the USB device for programming the unit. This used to work, but no
4052 longer in Jessie and Stretch. After some investigation and asking
4053 around on #debian-devel, I discovered that this was because udev had
4054 changed the mechanism used to grant access to local devices. The
4055 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
4056 no longer applied, because LDAP users no longer was added to the
4057 plugdev group during login. Michael Biebl told me that this method
4058 was obsolete and the new method used ACLs instead. This was good
4059 news, as the plugdev mechanism is a mess when using a remote user
4060 directory like LDAP. Using ACLs would make sure a user lost device
4061 access when she logged out, even if the user left behind a background
4062 process which would retain the plugdev membership with the ConsoleKit
4063 setup. Armed with this knowledge I moved on to fix the access problem
4064 for the LEGO Mindstorms related packages.&lt;/p&gt;
4065
4066 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
4067 applied directly for a device, or is applied in
4068 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
4069 LEGO Mindstorms udev rules did not have a class, I decided to add the
4070 tag directly in the udev rules files included in the packages. Here
4071 is one example. For the nqc C compiler for the RCX, the
4072 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
4073
4074 &lt;p&gt;&lt;pre&gt;
4075 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
4076 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
4077 &lt;/pre&gt;&lt;/p&gt;
4078
4079 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
4080 packages using plugdev in their /lib/udev/rules.d/ files should be
4081 changed to use this tag (either directly or indirectly via
4082 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
4083 to detect this?&lt;/p&gt;
4084
4085 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
4086 It is unclear to me if the uaccess tag is an internal implementation
4087 detail like the udev-acl tag used by
4088 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
4089 indirect method is the preferred way. Michael
4090 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
4091 documentation from the systemd project&lt;/a&gt; and I hope it will make
4092 this clearer. For now I use the generic classes when they exist and
4093 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
4094 directly if no such class exist.&lt;/p&gt;
4095
4096 &lt;p&gt;To learn more about the isenkram system, please check out
4097 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
4098 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
4099
4100 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
4101 please join us on our IRC channel
4102 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
4103 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
4104 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
4105 list is not yet created, but we are working on it. :)&lt;/p&gt;
4106
4107 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4108 activities, please send Bitcoin donations to my address
4109 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4110 </description>
4111 </item>
4112
4113 <item>
4114 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
4115 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
4116 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</guid>
4117 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
4118 <description>&lt;p&gt;In April we
4119 &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
4120 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
4121 how to set up and administrate a Debian system. Today I am happy to
4122 report that the first draft is now publicly available. You can find
4123 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
4124 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
4125 eight chapters have a first draft translation, and we are working on
4126 proofreading the content. If you want to help out, please start
4127 contributing using
4128 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
4129 hosted weblate project page&lt;/a&gt;, and get in touch using
4130 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
4131 translators mailing list&lt;/a&gt;. Please also check out
4132 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
4133 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
4134 and update weblate if you find errors.&lt;/p&gt;
4135
4136 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
4137 electronic form.&lt;/p&gt;
4138 </description>
4139 </item>
4140
4141 <item>
4142 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
4143 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
4144 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
4145 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
4146 <description>&lt;p&gt;This summer, I read a great article
4147 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
4148 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
4149 how to profile multi-threaded programs. It presented a system for
4150 profiling software by running experiences in the running program,
4151 testing how run time performance is affected by &quot;speeding up&quot; parts of
4152 the code to various degrees compared to a normal run. It does this by
4153 slowing down parallel threads while the &quot;faster up&quot; code is running
4154 and measure how this affect processing time. The processing time is
4155 measured using probes inserted into the code, either using progress
4156 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
4157 can also measure unmodified code by measuring complete the program
4158 runtime and running the program several times instead.&lt;/p&gt;
4159
4160 &lt;p&gt;The project and presentation was so inspiring that I would like to
4161 get the system into Debian. I
4162 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
4163 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
4164 system ready for Debian by sending patches. The build process need to
4165 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
4166 to include the JavaScript web page used to visualize the collected
4167 profiling information included in the source package.
4168 But I expect that should work out fairly soon.&lt;/p&gt;
4169
4170 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
4171 on a binary with debug symbols available, start the program like this:
4172
4173 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4174 coz run --- program-to-run
4175 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4176
4177 &lt;p&gt;This will create a text file profile.coz with the instrumentation
4178 information. To show what part of the code affect the performance
4179 most, use a web browser and either point it to
4180 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
4181 or use the copy from git (in the gh-pages branch). Check out this web
4182 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
4183 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
4184 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
4185 code, rebuild and run the profiler. This allow coz to do more
4186 targeted experiments.&lt;/p&gt;
4187
4188 &lt;p&gt;A video published by ACM
4189 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
4190 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
4191 from the 25th Symposium on Operating Systems Principles available
4192 titled
4193 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
4194 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
4195
4196 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
4197 for Coz is available from github. It will only build with clang
4198 because it uses a
4199 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
4200 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
4201 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
4202 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
4203
4204 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
4205 of software in Debian. I would very much like some help with the
4206 packaging effort, as I lack the in depth knowledge on how to package
4207 C++ libraries.&lt;/p&gt;
4208 </description>
4209 </item>
4210
4211 <item>
4212 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
4213 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
4214 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
4215 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
4216 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
4217 to be a slight challenge. Here is the recipe if I ever need to do it
4218 again. It all started by me wanting to try the recipe to set up
4219 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
4220 hardened Android installation&lt;/a&gt; from the Tor project blog on a
4221 device I had access to. It is a old mobile phone with a broken
4222 microphone The initial idea had been to just
4223 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
4224 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
4225 until a few days ago.&lt;/p&gt;
4226
4227 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
4228 loader (press volume down and power at the same time), (2) select
4229 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
4230 machine, (4) request the device identifier token by running &#39;fastboot
4231 oem get_identifier_token&#39;, (5) request the device unlocking key using
4232 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
4233 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
4234
4235 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
4236 or newer, and the device I was working on had 2.00.0027. This
4237 apparently can be easily fixed by downloading a Windows program and
4238 running it on your Windows machine, if you accept the terms Microsoft
4239 require you to accept to use Windows - which I do not. So I had to
4240 come up with a different approach. I got a lot of help from AndyCap
4241 on #nuug, and would not have been able to get this working without
4242 him.&lt;/p&gt;
4243
4244 &lt;p&gt;First I needed to extract the hboot firmware from
4245 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
4246 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
4247 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
4248 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
4249 recognise the file format, but unruu worked and extracted rom.zip,
4250 containing the new hboot firmware and a text file describing which
4251 devices it would work for.&lt;/p&gt;
4252
4253 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
4254 followed some instructions
4255 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
4256 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
4257 machine with Debian testing:&lt;/p&gt;
4258
4259 &lt;p&gt;&lt;pre&gt;
4260 adb reboot-bootloader
4261 fastboot oem rebootRUU
4262 fastboot flash zip rom.zip
4263 fastboot flash zip rom.zip
4264 fastboot reboot
4265 &lt;/pre&gt;&lt;/p&gt;
4266
4267 &lt;p&gt;The flash command apparently need to be done twice to take effect,
4268 as the first is just preparations and the second one do the flashing.
4269 The adb command is just to get to the boot loader menu, so turning the
4270 device on while holding volume down and the power button should work
4271 too.&lt;/p&gt;
4272
4273 &lt;p&gt;With the new hboot version in place I could start following the
4274 instructions on the HTC developer web site. I got the device token
4275 like this:&lt;/p&gt;
4276
4277 &lt;p&gt;&lt;pre&gt;
4278 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
4279 &lt;/pre&gt;
4280
4281 &lt;p&gt;And once I got the unlock code via email, I could use it like
4282 this:&lt;/p&gt;
4283
4284 &lt;p&gt;&lt;pre&gt;
4285 fastboot flash unlocktoken Unlock_code.bin
4286 &lt;/pre&gt;&lt;/p&gt;
4287
4288 &lt;p&gt;And with that final step in place, the phone was unlocked and I
4289 could start stuffing the software of my own choosing into the device.
4290 So far I only inserted a replacement recovery image to wipe the phone
4291 before I start. We will see what happen next. Perhaps I should
4292 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
4293 </description>
4294 </item>
4295
4296 <item>
4297 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
4298 <link>https://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</link>
4299 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</guid>
4300 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
4301 <description>&lt;p&gt;For a while now, I have wanted to test
4302 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
4303 said to provide end to end encrypted communication and several of my
4304 friends and family are already using it. As I by choice do not own a
4305 mobile phone, this proved to be harder than expected. And I wanted to
4306 have the source of the client and know that it was the code used on my
4307 machine. But yesterday I managed to get it working. I used the
4308 Github source, compared it to the source in
4309 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
4310 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
4311 patches to use the production Signal servers, started the app and
4312 asked for the hidden &quot;register without a smart phone&quot; form. Here is
4313 the recipe how I did it.&lt;/p&gt;
4314
4315 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
4316
4317 &lt;pre&gt;
4318 git clone https://github.com/WhisperSystems/Signal-Desktop.git
4319 &lt;/pre&gt;
4320
4321 &lt;p&gt;Next, I patched the source to use the production servers, to be
4322 able to talk to other Signal users:&lt;/p&gt;
4323
4324 &lt;pre&gt;
4325 cat &amp;lt;&amp;lt;EOF | patch -p0
4326 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
4327 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
4328 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
4329 @@ -47,8 +47,8 @@
4330 });
4331 });
4332
4333 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
4334 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
4335 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
4336 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
4337 var messageReceiver;
4338 window.getSocketStatus = function() {
4339 if (messageReceiver) {
4340 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
4341 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
4342 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
4343 @@ -1,6 +1,6 @@
4344 ;(function() {
4345 &#39;use strict&#39;;
4346 - var BUILD_EXPIRATION = 0;
4347 + var BUILD_EXPIRATION = 1474492690000;
4348
4349 window.extension = window.extension || {};
4350
4351 EOF
4352 &lt;/pre&gt;
4353
4354 &lt;p&gt;The first part is changing the servers, and the second is updating
4355 an expiration timestamp. This timestamp need to be updated regularly.
4356 It is set 90 days in the future by the build process (Gruntfile.js).
4357 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
4358
4359 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
4360 script to launch Signal in Chromium.&lt;/p&gt;
4361
4362 &lt;pre&gt;
4363 #!/bin/sh
4364 cd $(dirname $0)
4365 mkdir -p userdata
4366 exec chromium \
4367 --proxy-server=&quot;socks://localhost:9050&quot; \
4368 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
4369 &lt;/pre&gt;
4370
4371 &lt;p&gt; The script start the app and configure Chromium to use the Tor
4372 SOCKS5 proxy to make sure those controlling the Signal servers (today
4373 Amazon and Whisper Systems) as well as those listening on the lines
4374 will have a harder time location my laptop based on the Signal
4375 connections if they use source IP address.&lt;/p&gt;
4376
4377 &lt;p&gt;When the script starts, one need to follow the instructions under
4378 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
4379 repository. I right clicked on the Signal window to get up the
4380 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
4381 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
4382 registration form. Then I entered by land line phone number and
4383 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
4384 repeated the verification code three times. After entering the number
4385 into the verification code field in the form, I could start using
4386 Signal from my laptop.
4387
4388 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
4389 whom and thus who know who to those controlling the central server,
4390 but such leakage is hard to avoid with a centrally controlled server
4391 setup. It is something to keep in mind when using Signal - the
4392 content of your chats are harder to intercept, but the meta data
4393 exposing your contact network is available to people you do not know.
4394 So better than many options, but not great. And sadly the usage is
4395 connected to my land line, thus allowing those controlling the server
4396 to associate it to my home and person. I would prefer it if only
4397 those I knew could tell who I was on Signal. There are options
4398 avoiding such information leakage, but most of my friends are not
4399 using them, so I am stuck with Signal for now.&lt;/p&gt;
4400
4401 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
4402 on this topic in
4403 &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
4404 and updated recipe for using the Signal app without a mobile
4405 phone&lt;/a&gt;.&lt;/p&gt;
4406 </description>
4407 </item>
4408
4409 <item>
4410 <title>The new &quot;best&quot; multimedia player in Debian?</title>
4411 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
4412 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
4413 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
4414 <description>&lt;p&gt;When I set out a few weeks ago to figure out
4415 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
4416 multimedia player in Debian claimed to support most file formats /
4417 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
4418 the various players claimed support for. The range was from 55 to 130
4419 MIME types. I suspect most media formats are supported by all
4420 players, but this is not really reflected in the MimeTypes values in
4421 their desktop files. There are probably also some bogus MIME types
4422 listed, but it is hard to identify which one this is.&lt;/p&gt;
4423
4424 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
4425 the players suggesting to add more MIME types to their desktop files,
4426 and decided to spend some time myself improving the situation for my
4427 favorite media player VLC. The fixes for VLC entered Debian unstable
4428 yesterday. The complete list of MIME types can be seen on the
4429 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
4430 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
4431
4432 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
4433 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
4434 kmplayer. I am sure some of the other players desktop files support
4435 several of the formats currently listed as working only with vlc,
4436 toten and parole.&lt;/p&gt;
4437
4438 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
4439 supported by all the tested multimedia players in Debian in their
4440 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
4441 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
4442 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
4443 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
4444 it sad that video/ogg and video/webm is not supported by all the media
4445 players in Debian. As far as I can tell, all of them can handle both
4446 formats.&lt;/p&gt;
4447 </description>
4448 </item>
4449
4450 <item>
4451 <title>A program should be able to open its own files on Linux</title>
4452 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
4453 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
4454 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
4455 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
4456 decided to test its presentation tool when making the slides for a
4457 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
4458 wrote the first draft of the slides, saved the result and went to bed
4459 the day before I would give the talk. The next day I took a plane to
4460 the location where the meeting should take place, and on the plane I
4461 started up koffice again to polish the talk a bit, only to discover
4462 that kpresenter refused to load its own data file. I cursed a bit and
4463 started making the slides again from memory, to have something to
4464 present when I arrived. I tested that the saved files could be
4465 loaded, and the day seemed to be rescued. I continued to polish the
4466 slides until I suddenly discovered that the saved file could no longer
4467 be loaded into kpresenter. In the end I had to rewrite the slides
4468 three times, condensing the content until the talk became shorter and
4469 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
4470 kpresenter wrote inline images in a way itself could not understand.
4471 Eventually that bug was fixed and kpresenter ended up being a great
4472 program to make slides. The point I&#39;m trying to make is that we
4473 expect a program to be able to load its own data files, and it is
4474 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
4475
4476 &lt;p&gt;Did you ever experience a program failing to load its own data
4477 files from the desktop file browser? It is not a uncommon problem. A
4478 while back I discovered that the screencast recorder
4479 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
4480 browser would refuse to open. No video player claimed to understand
4481 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
4482 returning the application/ogg MIME type, which no video player I had
4483 installed listed as a MIME type they would understand. I asked for
4484 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
4485 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
4486 several video players to add video/ogg to their desktop files, to give
4487 the file browser an idea what to do about Ogg Theora files. After a
4488 while, the desktop file browsers in Debian started to handle the
4489 output from gtk-recordmydesktop properly.&lt;/p&gt;
4490
4491 &lt;p&gt;But history repeats itself. A few days ago I tested the music
4492 system Rosegarden again, and I discovered that the KDE and xfce file
4493 browsers did not know what to do with the Rosegarden project files
4494 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
4495 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
4496 included in the next upload. To increase the chance of me remembering
4497 how to fix the problem next time some program fail to load its files
4498 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
4499
4500 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
4501 There are two sources for the MIME type of a given file. The output from
4502 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
4503 shared MIME type registry (under /usr/share/mime/). The file MIME
4504 type is mapped to programs supporting the MIME type, and this
4505 information is collected from
4506 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
4507 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
4508 one desktop file claiming support for the MIME type of the file, it is
4509 activated when asking to open a given file. If there are more, one
4510 can normally select which one to use by right-clicking on the file and
4511 selecting the wanted one using &#39;Open with&#39; or similar. In general
4512 this work well. But it depend on each program picking a good MIME
4513 type (preferably
4514 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
4515 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
4516 registry recognizing the file and the desktop file to list the MIME
4517 type in its list of supported MIME types.&lt;/p&gt;
4518
4519 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
4520 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
4521 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
4522
4523 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4524 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
4525 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
4526 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
4527 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
4528 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
4529 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
4530 &amp;lt;/mime-type&amp;gt;
4531 &amp;lt;/mime-info&amp;gt;
4532 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4533
4534 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
4535 (it is a gzipped XML file). Note, it is much better to use an
4536 official MIME type registered with IANA than it is to make up ones own
4537 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
4538
4539 &lt;p&gt;The desktop file of the rosegarden program failed to list
4540 audio/x-rosegarden in its list of supported MIME types, causing the
4541 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
4542
4543 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4544 % grep Mime /usr/share/applications/rosegarden.desktop
4545 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
4546 X-KDE-NativeMimeType=audio/x-rosegarden-composition
4547 %
4548 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4549
4550 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
4551 MimeType= line.&lt;/p&gt;
4552
4553 &lt;p&gt;If you run into a file which fail to open the correct program when
4554 selected from the file browser, please check out the output from
4555 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
4556 MIME type is registered somewhere under /usr/share/mime/ and check
4557 that some desktop file under /usr/share/applications/ is claiming
4558 support for this MIME type. If not, please report a bug to have it
4559 fixed. :)&lt;/p&gt;
4560 </description>
4561 </item>
4562
4563 <item>
4564 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
4565 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
4566 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
4567 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
4568 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
4569 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
4570 related packages. The idea is to have a database of mappings between
4571 hardware and packages, and pop up a dialog suggesting for the user to
4572 install the packages to use a given hardware dongle. Some use cases
4573 are when you insert a Yubikey, it proposes to install the software
4574 needed to control it; when you insert a braille reader list it
4575 proposes to install the packages needed to send text to the reader;
4576 and when you insert a ColorHug screen calibrator it suggests to
4577 install the driver for it. The system work well, and even have a few
4578 command line tools to install firmware packages and packages for the
4579 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
4580
4581 &lt;p&gt;The system was initially written using aptdaemon, because I found
4582 good documentation and example code on how to use it. But aptdaemon
4583 is going away and is generally being replaced by
4584 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
4585 so Isenkram needed a rewrite. And today, thanks to the great patch
4586 from my college Sunil Mohan Adapa in the FreedomBox project, the
4587 rewrite finally took place. I&#39;ve just uploaded a new version of
4588 Isenkram into Debian Unstable with the patch included, and the default
4589 for the background daemon is now to use PackageKit. To check it out,
4590 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
4591 and see if it is recognised.&lt;/p&gt;
4592
4593 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
4594 the machine it is running on, you can check out the isenkram-lookup
4595 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
4596
4597 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4598 % isenkram-lookup
4599 bluez
4600 cheese
4601 fprintd
4602 fprintd-demo
4603 gkrellm-thinkbat
4604 hdapsd
4605 libpam-fprintd
4606 pidgin-blinklight
4607 thinkfan
4608 tleds
4609 tp-smapi-dkms
4610 tp-smapi-source
4611 tpb
4612 %p
4613 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
4614
4615 &lt;p&gt;The hardware mappings come from several places. The preferred way
4616 is for packages to announce their hardware support using
4617 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
4618 cross distribution appstream system&lt;/a&gt;.
4619 See
4620 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
4621 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
4622 </description>
4623 </item>
4624
4625 <item>
4626 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
4627 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
4628 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
4629 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
4630 <description>&lt;p&gt;Yesterday I updated the
4631 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
4632 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
4633 enterprising users. There were some nice user and visible changes.
4634 First of all, both desktop menu entries now work. A design flaw in
4635 one of the script made the history graph fail to show up (its PNG was
4636 dumped in ~/.xsession-errors) if no controlling TTY was available.
4637 The script worked when called from the command line, but not when
4638 called from the desktop menu. I changed this to look for a DISPLAY
4639 variable or a TTY before deciding where to draw the graph, and now the
4640 graph window pop up as expected.&lt;/p&gt;
4641
4642 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
4643 graphs (the one showing the last few hours). New is also the user of
4644 colours showing charging in blue and discharge in red. The percentages
4645 of this graph is relative to last full charge, not battery design
4646 capacity.&lt;/p&gt;
4647
4648 &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;
4649
4650 &lt;p&gt;The other graph show the entire history of the collected battery
4651 statistics, comparing it to the design capacity of the battery to
4652 visualise how the battery life time get shorter over time. The red
4653 line in this graph is what the previous graph considers 100 percent:
4654
4655 &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;
4656
4657 &lt;p&gt;In this graph you can see that I only charge the battery to 80
4658 percent of last full capacity, and how the capacity of the battery is
4659 shrinking. :(&lt;/p&gt;
4660
4661 &lt;p&gt;The last new feature is in the collector, which now will handle
4662 more hardware models. On some hardware, Linux power supply
4663 information is stored in /sys/class/power_supply/ACAD/, while the
4664 collector previously only looked in /sys/class/power_supply/AC/. Now
4665 both are checked to figure if there is power connected to the
4666 machine.&lt;/p&gt;
4667
4668 &lt;p&gt;If you are interested in how your laptop battery is doing, please
4669 check out the
4670 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
4671 in Debian unstable, or rebuild it on Jessie to get it working on
4672 Debian stable. :) The upstream source is available from &lt;a
4673 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4674 Patches are very welcome.&lt;/p&gt;
4675
4676 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4677 activities, please send Bitcoin donations to my address
4678 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4679 </description>
4680 </item>
4681
4682 <item>
4683 <title>Debian now with ZFS on Linux included</title>
4684 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
4685 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
4686 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
4687 <description>&lt;p&gt;Today, after many years of hard work from many people,
4688 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
4689 Debian. The package status can be seen on
4690 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
4691 for zfs-linux&lt;/a&gt;. and
4692 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
4693 team status page&lt;/a&gt;. If you want to help out, please join us.
4694 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
4695 source code&lt;/a&gt; is available via git on Alioth. It would also be
4696 great if you could help out with
4697 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
4698 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
4699 </description>
4700 </item>
4701
4702 <item>
4703 <title>What is the best multimedia player in Debian?</title>
4704 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
4705 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
4706 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
4707 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
4708 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
4709
4710 &lt;p&gt;A few years ago, I had a look at the media support for Browser
4711 plugins in Debian, to get an idea which plugins to include in Debian
4712 Edu. I created a script to extract the set of supported MIME types
4713 for each plugin, and used this to find out which multimedia browser
4714 plugin supported most file formats / media types.
4715 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
4716 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
4717 not been updated for a while. But browser plugins are less relevant
4718 these days, so I thought it was time to look at standalone
4719 players.&lt;/p&gt;
4720
4721 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
4722 player when I wanted to play videos from the Norwegian National
4723 Broadcasting Company, and decided to investigate why. The cause is a
4724 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
4725 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
4726 of MIME types announced in the desktop file and the browser plugin,
4727 only to discover that there is quite a large difference between the
4728 two for VLC. This discovery made me dig up the script I used to
4729 compare browser plugins, and adjust it to compare desktop files
4730 instead, to try to figure out which multimedia player in Debian
4731 support most file formats.&lt;/p&gt;
4732
4733 &lt;p&gt;The result can be seen on the Debian Wiki, as
4734 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
4735 table listing all MIME types supported by one of the packages included
4736 in the table&lt;/a&gt;, with the package supporting most MIME types being
4737 listed first in the table.&lt;/p&gt;
4738
4739 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
4740 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
4741 kmplayer. Time for the other players to update their announced MIME
4742 support?&lt;/p&gt;
4743 </description>
4744 </item>
4745
4746 <item>
4747 <title>The Pyra - handheld computer with Debian preinstalled</title>
4748 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
4749 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
4750 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
4751 <description>A friend of mine made me aware of
4752 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
4753 handheld computer which will be delivered with Debian preinstalled. I
4754 would love to get one of those for my birthday. :)&lt;/p&gt;
4755
4756 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
4757 plugs and many others connectors, and include a full keyboard and a 5&quot;
4758 LCD touch screen. The 6000mAh battery is claimed to provide a whole
4759 day of battery life time, but I have not seen any independent tests
4760 confirming this. The vendor is still collecting preorders, and the
4761 last I heard last night was that 22 more orders were needed before
4762 production started.&lt;/p&gt;
4763
4764 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
4765 Debian. Please let me know if you know of any others. Is it the
4766 first computer being sold with Debian preinstalled?&lt;/p&gt;
4767 </description>
4768 </item>
4769
4770 <item>
4771 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
4772 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
4773 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
4774 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
4775 <description>&lt;p&gt;During this weekends
4776 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
4777 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
4778 to make sure there are good books about Debian available in Norwegian
4779 Bokmål, and got in touch with the people behind the
4780 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
4781 project&lt;/a&gt; to get started. If you want to help out, please start
4782 contributing using
4783 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
4784 hosted weblate project page&lt;/a&gt;, and get in touch using
4785 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
4786 translators mailing list&lt;/a&gt;. Please also check out
4787 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
4788 contributors&lt;/a&gt;.&lt;/p&gt;
4789
4790 &lt;p&gt;The book is already available on paper in English, French and
4791 Japanese, and our goal is to get it available on paper in Norwegian
4792 Bokmål too. In addition to the paper edition, there are also EPUB and
4793 Mobi versions available. And there are incomplete translations
4794 available for many more languages.&lt;/p&gt;
4795 </description>
4796 </item>
4797
4798 <item>
4799 <title>One in two hundred Debian users using ZFS on Linux?</title>
4800 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
4801 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
4802 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
4803 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
4804 packages in Debian, and was quite surprised with what I found. I use
4805 ZFS myself at home, but did not really expect many others to do so.
4806 But I might be wrong.&lt;/p&gt;
4807
4808 &lt;p&gt;According to
4809 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
4810 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
4811 0.53% of the population, with the package installed. As far as I know
4812 the only use of the spl-linux package is as a support library for ZFS
4813 on Linux, so I use it here as proxy for measuring the number of ZFS
4814 installation on Linux in Debian. In the kFreeBSD variant of Debian
4815 the ZFS feature is already available, and there
4816 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
4817 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
4818 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
4819
4820 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
4821 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
4822 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
4823 cleared, the package is still not in Debian. The package is again in
4824 the NEW queue. Several uploads have been rejected so far because the
4825 debian/copyright file was incomplete or wrong, but there is no reason
4826 to give up. The current status can be seen on
4827 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
4828 team status page&lt;/a&gt;, and
4829 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
4830 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
4831
4832 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
4833 my home server can function in the future using only official Debian
4834 packages, and the current blocker is to get the debian/copyright file
4835 accepted by the FTP masters in Debian, I decided a while back to try
4836 to help out the team. This was the background for my blog post about
4837 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
4838 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
4839 used the techniques I explored there to try to find any errors in the
4840 copyright file. It is not very easy to check every one of the around
4841 2000 files in the source package, but I hope we this time got it
4842 right. If you want to help out, check out the git source and try to
4843 find missing entries in the debian/copyright file.&lt;/p&gt;
4844 </description>
4845 </item>
4846
4847 <item>
4848 <title>Full battery stats collector is now available in Debian</title>
4849 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
4850 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
4851 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
4852 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
4853 extended collector that will collect the complete battery history for
4854 later processing and graphing. The original collector store the
4855 battery level as percentage of last full level, while the new
4856 collector also record battery vendor, model, serial number, design
4857 full level, last full level and current battery level. This make it
4858 possible to predict the lifetime of the battery as well as visualise
4859 the energy flow when the battery is charging or discharging.&lt;/p&gt;
4860
4861 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
4862 in the version 0.5.1 package in unstable. Get the new battery level graph
4863 and lifetime prediction by running:
4864
4865 &lt;p&gt;&lt;pre&gt;
4866 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
4867 &lt;/pre&gt;&lt;/p&gt;
4868
4869 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
4870
4871 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
4872 entry yet):&lt;/p&gt;
4873
4874 &lt;p&gt;&lt;pre&gt;
4875 /usr/share/battery-stats/battery-stats-graph-flow
4876 &lt;/pre&gt;&lt;/p&gt;
4877
4878 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
4879 when there are few data points. The graphs look a bit better with a
4880 few years of data.&lt;/p&gt;
4881
4882 &lt;p&gt;A while back one important feature I use in the battery stats
4883 collector broke in Debian. The scripts in
4884 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
4885 suspect it happened when Jessie started using systemd, but I do not
4886 know. The issue is reported as
4887 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
4888 pm-utils. I managed to work around it by adding an udev rule to call
4889 the collector script every time the power connector is connected and
4890 disconnected. With this fix in place it was finally time to make a
4891 new release of the package, and get it into Debian.&lt;/p&gt;
4892
4893 &lt;p&gt;If you are interested in how your laptop battery is doing, please
4894 check out the
4895 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
4896 in Debian unstable, or rebuild it on Jessie to get it working on
4897 Debian stable. :) The upstream source is available from
4898 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4899 As always, patches are very welcome.&lt;/p&gt;
4900 </description>
4901 </item>
4902
4903 <item>
4904 <title>Making battery measurements a little easier in Debian</title>
4905 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
4906 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
4907 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
4908 <description>&lt;p&gt;Back in September, I blogged about
4909 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
4910 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
4911 how it showed the decay and death of this battery (now replaced). I
4912 created a simple deb package to handle the collection and graphing,
4913 but did not want to upload it to Debian as there were already
4914 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
4915 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
4916 a point of uploading a competing package when battery-stats could be
4917 fixed instead. I reported a few bugs about its non-function, and
4918 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
4919
4920 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
4921 hands. The end result is that I am now the new upstream developer of
4922 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
4923 battery-stats in Debian, and the package in Debian unstable is finally
4924 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
4925 information provided by the Linux kernel. If you install the
4926 battery-stats package from unstable now, you will be able to get a
4927 graph of the current battery fill level, to get some idea about the
4928 status of the battery. The source package build and work just fine in
4929 Debian testing and stable (and probably oldstable too, but I have not
4930 tested). The default graph you get for that system look like this:&lt;/p&gt;
4931
4932 &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;
4933
4934 &lt;p&gt;My plans for the future is to merge my old scripts into the
4935 battery-stats package, as my old scripts collected a lot more details
4936 about the battery. The scripts are merged into the upstream
4937 battery-stats git repository already, but I am not convinced they work
4938 yet, as I changed a lot of paths along the way. Will have to test a
4939 bit more before I make a new release.&lt;/p&gt;
4940
4941 &lt;p&gt;I will also consider changing the file format slightly, as I
4942 suspect the way I combine several values into one field might make it
4943 impossible to know the type of the value when using it for processing
4944 and graphing.&lt;/p&gt;
4945
4946 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
4947 battery, check out the battery-stats package in
4948 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
4949 on
4950 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4951 I would love some help to improve the system further.&lt;/p&gt;
4952 </description>
4953 </item>
4954
4955 <item>
4956 <title>Creating, updating and checking debian/copyright semi-automatically</title>
4957 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
4958 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
4959 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
4960 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
4961 details. And one of the details is the content of the
4962 debian/copyright file, which should list all relevant licenses used by
4963 the code in the package in question, preferably in
4964 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
4965 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
4966
4967 &lt;p&gt;For large packages with lots of contributors it is hard to write
4968 and update this file manually, and if you get some detail wrong, the
4969 package is normally rejected by the ftpmasters. So getting it right
4970 the first time around get the package into Debian faster, and save
4971 both you and the ftpmasters some work.. Today, while trying to figure
4972 out what was wrong with
4973 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
4974 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
4975 figuring out the options for doing this job automatically, or at least
4976 semi-automatically.&lt;/p&gt;
4977
4978 &lt;p&gt;Lucikly, there are at least two tools available for generating the
4979 file based on the code in the source package,
4980 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
4981 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
4982 not sure which one of them came first, but both seem to be able to
4983 create a sensible draft file. As far as I can tell, none of them can
4984 be trusted to get the result just right, so the content need to be
4985 polished a bit before the file is OK to upload. I found the debmake
4986 option in
4987 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
4988 blog posts from 2014&lt;/a&gt;.
4989
4990 &lt;p&gt;To generate using debmake, use the -cc option:
4991
4992 &lt;p&gt;&lt;pre&gt;
4993 debmake -cc &gt; debian/copyright
4994 &lt;/pre&gt;&lt;/p&gt;
4995
4996 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
4997 this might not be the best option.&lt;/p&gt;
4998
4999 &lt;p&gt;The cme option is based on a config parsing library, and I found
5000 this approach in
5001 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
5002 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
5003 dpkg-copyright&#39; option:
5004
5005 &lt;p&gt;&lt;pre&gt;
5006 cme update dpkg-copyright
5007 &lt;/pre&gt;&lt;/p&gt;
5008
5009 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
5010 handle UTF-8 names better than debmake.&lt;/p&gt;
5011
5012 &lt;p&gt;When the copyright file is created, I would also like some help to
5013 check if the file is correct. For this I found two good options,
5014 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
5015 to focus on license types and file matching, and is able to detect
5016 ineffective blocks in the copyright file. The latter reports missing
5017 copyright holders and years, but was confused by inconsistent license
5018 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
5019 fix all issues reported by them before uploading. But I do not know
5020 if the tools and the ftpmasters agree on what is important to fix in a
5021 copyright file, so the package might still be rejected.&lt;/p&gt;
5022
5023 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
5024 will read through the source and try to find all copyright statements.
5025 It is not comparing the result to the content of debian/copyright, but
5026 can be useful when verifying the content of the copyright file.&lt;/p&gt;
5027
5028 &lt;p&gt;Are you aware of better tools in Debian to create and update
5029 debian/copyright file. Please let me know, or blog about it on
5030 planet.debian.org.&lt;/p&gt;
5031
5032 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
5033 activities, please send Bitcoin donations to my address
5034 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5035
5036 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
5037 on how to use licensecheck and cdbs to create a draft copyright file
5038
5039 &lt;p&gt;&lt;pre&gt;
5040 licensecheck --copyright -r `find * -type f` | \
5041 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
5042 &lt;/pre&gt;&lt;/p&gt;
5043
5044 &lt;p&gt;He mentioned that he normally check the generated file into the
5045 version control system to make it easier to discover license and
5046 copyright changes in the upstream source. I will try to do the same
5047 with my packages in the future.&lt;/p&gt;
5048
5049 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
5050 against using -quiet for new users, so I removed it from the proposed
5051 command line.&lt;/p&gt;
5052 </description>
5053 </item>
5054
5055 <item>
5056 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
5057 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
5058 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
5059 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
5060 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
5061 is taking shape in Debian, and one provided feature is a very
5062 convenient way to tell you which package to install to make a given
5063 firmware file available when the kernel is looking for it. This can
5064 be done using apt-file too, but that is for someone else to blog
5065 about. :)&lt;/p&gt;
5066
5067 &lt;p&gt;Here is a small recipe to find the package with a given firmware
5068 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
5069 picked from the set of firmware announced using appstream in Debian
5070 unstable. In general you would be looking for the firmware requested
5071 by the kernel during kernel module loading. To find the package
5072 providing the example file, do like this:&lt;/p&gt;
5073
5074 &lt;blockquote&gt;&lt;pre&gt;
5075 % apt install appstream
5076 [...]
5077 % apt update
5078 [...]
5079 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
5080 awk &#39;/Package:/ {print $2}&#39;
5081 firmware-qlogic
5082 %
5083 &lt;/pre&gt;&lt;/blockquote&gt;
5084
5085 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
5086 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
5087 a way appstream can use.&lt;/p&gt;
5088
5089 &lt;p&gt;This same approach can be used to find any package supporting a
5090 given MIME type. This is very useful when you get a file you do not
5091 know how to handle. First find the mime type using &lt;tt&gt;file
5092 --mime-type&lt;/tt&gt;, and next look up the package providing support for
5093 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
5094 and you can find all packages handling this type like this:&lt;/p&gt;
5095
5096 &lt;blockquote&gt;&lt;pre&gt;
5097 % apt install appstream
5098 [...]
5099 % apt update
5100 [...]
5101 % appstreamcli what-provides mimetype image/svg+xml | \
5102 awk &#39;/Package:/ {print $2}&#39;
5103 bkchem
5104 phototonic
5105 inkscape
5106 shutter
5107 tetzle
5108 geeqie
5109 xia
5110 pinta
5111 gthumb
5112 karbon
5113 comix
5114 mirage
5115 viewnior
5116 postr
5117 ristretto
5118 kolourpaint4
5119 eog
5120 eom
5121 gimagereader
5122 midori
5123 %
5124 &lt;/pre&gt;&lt;/blockquote&gt;
5125
5126 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
5127 packages providing appstream metadata.&lt;/p&gt;
5128 </description>
5129 </item>
5130
5131 <item>
5132 <title>Creepy, visualise geotagged social media information - nice free software</title>
5133 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
5134 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
5135 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
5136 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
5137 with the computerised radio beacon known as a mobile phone their
5138 position is tracked by the phone company and often stored for a long
5139 time (like every time a SMS is received or sent). And if their
5140 computerised radio beacon is capable of running programs (often called
5141 mobile apps) downloaded from the Internet, these programs are often
5142 also capable of tracking their location (if the app requested access
5143 during installation). And when these programs send out information to
5144 central collection points, the location is often included, unless
5145 extra care is taken to not send the location. The provided
5146 information is used by several entities, for good and bad (what is
5147 good and bad, depend on your point of view). What is certain, is that
5148 the private sphere and the right to free movement is challenged and
5149 perhaps even eradicated for those announcing their location this way,
5150 when they share their whereabouts with private and public
5151 entities.&lt;/p&gt;
5152
5153 &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;
5154
5155 &lt;p&gt;The phone company logs provide a register of locations to check out
5156 when one want to figure out what the tracked person was doing. It is
5157 unavailable for most of us, but provided to selected government
5158 officials, company staff, those illegally buying information from
5159 unfaithful servants and crackers stealing the information. But the
5160 public information can be collected and analysed, and a free software
5161 tool to do so is called
5162 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
5163 discovered it when I read
5164 &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
5165 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
5166 November 2014, and decided to check if it was available in Debian.
5167 The python program was in Debian, but
5168 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
5169 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
5170 uploaded a new version which did not work quite right, but did not
5171 have time to fix it then. This Christmas I decided to finally try to
5172 get Creepy operational in Debian. Now a fixed version is available in
5173 Debian unstable and testing, and almost all Debian specific patches
5174 are now included
5175 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
5176
5177 &lt;p&gt;The Creepy program visualises geolocation information fetched from
5178 Twitter, Instagram, Flickr and Google+, and allow one to get a
5179 complete picture of every social media message posted recently in a
5180 given area, or track the movement of a given individual across all
5181 these services. Earlier it was possible to use the search API of at
5182 least some of these services without identifying oneself, but these
5183 days it is impossible. This mean that to use Creepy, you need to
5184 configure it to log in as yourself on these services, and provide
5185 information to them about your search interests. This should be taken
5186 into account when using Creepy, as it will also share information
5187 about yourself with the services.&lt;/p&gt;
5188
5189 &lt;p&gt;The picture above show the twitter messages sent from (or at least
5190 geotagged with a position from) the city centre of Oslo, the capital
5191 of Norway. One useful way to use Creepy is to first look at
5192 information tagged with an area of interest, and next look at all the
5193 information provided by one or more individuals who was in the area.
5194 I tested it by checking out which celebrity provide their location in
5195 twitter messages by checkout out who sent twitter messages near a
5196 Norwegian TV station, and next could track their position over time,
5197 making it possible to locate their home and work place, among other
5198 things. A similar technique have been
5199 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
5200 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
5201 tool to discover lying governments, and a useful tool to help people
5202 understand the value of the private information they provide to the
5203 public.&lt;/p&gt;
5204
5205 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
5206 it depend on several python modules currently missing in Jessie (at
5207 least python-instagram, python-flickrapi and
5208 python-requests-toolbelt).&lt;/p&gt;
5209
5210 &lt;p&gt;(I have uploaded
5211 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
5212 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
5213 Creepy program in Debian.)&lt;/p&gt;
5214 </description>
5215 </item>
5216
5217 <item>
5218 <title>Always download Debian packages using Tor - the simple recipe</title>
5219 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
5220 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
5221 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
5222 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
5223 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
5224 that those listening on the Internet lines would have good reason to
5225 believe a computer have a given security hole&lt;/a&gt; if it download a
5226 security fix from a Debian mirror. This is a good reason to always
5227 use encrypted connections to the Debian mirror, to make sure those
5228 listening do not know which IP address to attack. In August, Richard
5229 Hartmann observed that encryption was not enough, when it was possible
5230 to interfere download size to security patches or the fact that
5231 download took place shortly after a security fix was released, and
5232 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
5233 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
5234 was not the first to propose this, as the
5235 &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;
5236 package by Tim Retout already existed to make it easy to convince apt
5237 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
5238 aware of that package when I read the blog post from Richard.&lt;/p&gt;
5239
5240 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
5241 sysadmins, and he set up a Tor hidden service on one of the central
5242 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
5243 it possible to download packages directly between two tor nodes,
5244 making sure the network traffic always were encrypted.&lt;/p&gt;
5245
5246 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
5247 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
5248 urls with tor+http and tor+https, and using the hidden service instead
5249 of the official Debian mirror site. I recommend installing
5250 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
5251 done in /etc/.&lt;/p&gt;
5252
5253 &lt;blockquote&gt;&lt;pre&gt;
5254 apt install apt-transport-tor
5255 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
5256 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
5257 &lt;/pre&gt;&lt;/blockquote&gt;
5258
5259 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
5260 the sed commands for these too. The sed command is assuming your are
5261 using the ftp.debian.org Debian mirror. Adjust the command (or just
5262 edit the file manually) to match your mirror.&lt;/p&gt;
5263
5264 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
5265 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
5266 system, and do not work with these tor+http URLs. For
5267 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
5268 which need a recent apt version currently only in unstable. So if you
5269 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
5270
5271 &lt;p&gt;Another advantage from this change is that your machine will start
5272 using Tor regularly and at fairly random intervals (every time you
5273 update the package lists or upgrade or install a new package), thus
5274 masking other Tor traffic done from the same machine. Using Tor will
5275 become normal for the machine in question.&lt;/p&gt;
5276
5277 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
5278 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
5279 enabled. It would be great if it was the default on any Debian
5280 system.&lt;/p&gt;
5281 </description>
5282 </item>
5283
5284 <item>
5285 <title>OpenALPR, find car license plates in video streams - nice free software</title>
5286 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
5287 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
5288 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
5289 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
5290 call the car license plate numbers in those days. I would write the
5291 numbers down in my little book and compare notes with the other kids
5292 to see how many region codes we had seen and if we had seen some
5293 exotic or special region codes and numbers. It was a fun game to pass
5294 time, as we kids have plenty of it.&lt;/p&gt;
5295
5296 &lt;p&gt;A few days I came across
5297 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
5298 project&lt;/a&gt;, a free software project to automatically discover and
5299 report license plates in images and video streams, and provide the
5300 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
5301 such system for a while now, because I believe it is a bad idea that the
5302 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
5303 number plate recognition&lt;/a&gt; tool only is available in the hands of
5304 the powerful, and want it to be available also for the powerless to
5305 even the score when it comes to surveillance and sousveillance. I
5306 discovered the developer
5307 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
5308 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
5309 help him get it into shape to get the package uploaded into the Debian
5310 archive.&lt;/p&gt;
5311
5312 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
5313 it into Debian, where it currently
5314 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
5315 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
5316
5317 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
5318 for the common folks, ie those not running a large government
5319 surveillance system? Well, I plan to put it in a computer on my bike
5320 and in my car, tracking the cars nearby and allowing me to be notified
5321 when number plates on my watch list are discovered. Another use case
5322 was suggested by a friend of mine, who wanted to set it up at his home
5323 to open the car port automatically when it discovered the plate on his
5324 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
5325 capable of placing his license plate number of a piece of cardboard to
5326 open his car port, men replied that it was always unlocked anyway. I
5327 guess for such use case it make sense. I am sure there are other use
5328 cases too, for those with imagination and a vision.&lt;/p&gt;
5329
5330 &lt;p&gt;If you want to build your own version of the Debian package, check
5331 out the upstream git source and symlink ./distros/debian to ./debian/
5332 before running &quot;debuild&quot; to build the source. Or wait a bit until the
5333 package show up in unstable.&lt;/p&gt;
5334 </description>
5335 </item>
5336
5337 <item>
5338 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
5339 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
5340 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
5341 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
5342 <description>&lt;p&gt;Around three years ago, I created
5343 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
5344 system&lt;/a&gt; to get a more practical solution in Debian for handing
5345 hardware related packages. A GUI system in the isenkram package will
5346 present a pop-up dialog when some hardware dongle supported by
5347 relevant packages in Debian is inserted into the machine. The same
5348 lookup mechanism to detect packages is available as command line
5349 tools in the isenkram-cli package. In addition to mapping hardware,
5350 it will also map kernel firmware files to packages and make it easy to
5351 install needed firmware packages automatically. The key for this
5352 system to work is a good way to map hardware to packages, in other
5353 words, allow packages to announce what hardware they will work
5354 with.&lt;/p&gt;
5355
5356 &lt;p&gt;I started by providing data files in the isenkram source, and
5357 adding code to download the latest version of these data files at run
5358 time, to ensure every user had the most up to date mapping available.
5359 I also added support for storing the mapping in the Packages file in
5360 the apt repositories, but did not push this approach because while I
5361 was trying to figure out how to best store hardware/package mappings,
5362 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
5363 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
5364 add the hardware mapping into that data set to be able to use
5365 appstream as a data source, and this was accepted at least for the
5366 Debian version of appstream.&lt;/p&gt;
5367
5368 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
5369 and today I uploaded a new version 0.20 of isenkram adding support for
5370 appstream as a data source for mapping hardware to packages. The only
5371 package so far using appstream to announce its hardware support is my
5372 pymissile package. I got help from Matthias Klumpp with figuring out
5373 how do add the required
5374 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
5375 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
5376 this content:&lt;/p&gt;
5377
5378 &lt;blockquote&gt;&lt;pre&gt;
5379 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
5380 &amp;lt;component&amp;gt;
5381 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
5382 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
5383 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
5384 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
5385 &amp;lt;description&amp;gt;
5386 &amp;lt;p&amp;gt;
5387 Pymissile provides a curses interface to control an original
5388 Marks and Spencer / Striker USB Missile Launcher, as well as a
5389 motion control script to allow a webcamera to control the
5390 launcher.
5391 &amp;lt;/p&amp;gt;
5392 &amp;lt;/description&amp;gt;
5393 &amp;lt;provides&amp;gt;
5394 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
5395 &amp;lt;/provides&amp;gt;
5396 &amp;lt;/component&amp;gt;
5397 &lt;/pre&gt;&lt;/blockquote&gt;
5398
5399 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
5400 which is a glob style match rule for hardware specific strings
5401 (modalias strings) provided by the Linux kernel. In this case, it
5402 will map to all USB devices with vendor code 1130 and product code
5403 0202.&lt;/p&gt;
5404
5405 &lt;p&gt;Note, it is important that the license of all the metadata files
5406 are compatible to have permissions to aggregate them into archive wide
5407 appstream files. Matthias suggested to use MIT or BSD licenses for
5408 these files. A challenge is figuring out a good id for the data, as
5409 it is supposed to be globally unique and shared across distributions
5410 (in other words, best to coordinate with upstream what to use). But
5411 it can be changed later or, so we went with the package name as
5412 upstream for this project is dormant.&lt;/p&gt;
5413
5414 &lt;p&gt;To get the metadata file installed in the correct location for the
5415 mirror update scripts to pick it up and include its content the
5416 appstream data source, the file must be installed in the binary
5417 package under /usr/share/appdata/. I did this by adding the following
5418 line to debian/pymissile.install:&lt;/p&gt;
5419
5420 &lt;blockquote&gt;&lt;pre&gt;
5421 debian/pymissile.metainfo.xml usr/share/appdata
5422 &lt;/pre&gt;&lt;/blockquote&gt;
5423
5424 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
5425 all packages useful on the current computer automatically, and the GUI
5426 pop-up handler will propose to install the package not already
5427 installed if a hardware dongle is inserted into the machine in
5428 question.&lt;/p&gt;
5429
5430 &lt;p&gt;Details of the modalias field in appstream is available from the
5431 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
5432
5433 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
5434 try running this command on the command line:&lt;/p&gt;
5435
5436 &lt;blockquote&gt;&lt;pre&gt;
5437 cat $(find /sys/devices/|grep modalias)
5438 &lt;/pre&gt;&lt;/blockquote&gt;
5439
5440 &lt;p&gt;To learn more about the isenkram system, please check out
5441 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
5442 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
5443 </description>
5444 </item>
5445
5446 <item>
5447 <title>The GNU General Public License is not magic pixie dust</title>
5448 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
5449 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
5450 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
5451 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
5452 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
5453 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
5454 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
5455 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
5456
5457 &lt;blockquote&gt;
5458
5459 &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;
5460
5461 &lt;blockquote&gt;
5462 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
5463
5464 The first step is to choose a
5465 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
5466 code.&lt;br/&gt;
5467
5468 The next step is, when someone fails to follow that copyleft license,
5469 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
5470
5471 and its a simple fact of our modern society that such type of
5472 work&lt;br/&gt;
5473
5474 is incredibly expensive to do and incredibly difficult to do.
5475 &lt;/blockquote&gt;
5476
5477 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
5478 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
5479 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
5480 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
5481
5482 &lt;p&gt;As the Debian Website
5483 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
5484 &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;
5485 imply, public domain and permissively licensed software can lead to
5486 the production of more proprietary software as people discover useful
5487 software, extend it and or incorporate it into their hardware or
5488 software products. Copyleft licenses such as the GNU GPL were created
5489 to close off this avenue to the production of proprietary software but
5490 such licenses are not enough. With the ongoing adoption of Free
5491 Software by individuals and groups, inevitably the community&#39;s
5492 expectations of license compliance are violated, usually out of
5493 ignorance of the way Free Software works, but not always. As Karen
5494 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
5495 Freedom&quot;&gt;FaiF&lt;/a&gt;
5496 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
5497 copyleft is nothing if no-one is willing and able to stand up in court
5498 to protect it. The reality of today&#39;s world is that legal
5499 representation is expensive, difficult and time consuming. With
5500 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
5501 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
5502 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
5503 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
5504 of the Linux project, Debian and other groups against GPL violations.
5505 In March the SFC supported a
5506 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
5507 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
5508 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
5509 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
5510 kernel. Since then two of their sponsors pulled corporate funding and
5511 conferences
5512 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
5513 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
5514 less on corporate funding and more on the broad community of
5515 individuals who support Free Software and copyleft. So the SFC has
5516 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
5517 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
5518 a community of folks who stand up for copyleft and the GPL by
5519 supporting their work on promoting and supporting copyleft and Free
5520 Software.&lt;/p&gt;
5521
5522 &lt;p&gt;If you support Free Software,
5523 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
5524 what the SFC do, agree with their
5525 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
5526 principles&lt;/a&gt;, are happy about their
5527 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
5528 work on a project that is an SFC
5529 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
5530 just want to stand up for copyleft, please join
5531 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
5532 Allan Webber&lt;/a&gt;,
5533 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
5534 Smith&lt;/a&gt;,
5535 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
5536 Bacon&lt;/a&gt;, myself and
5537 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
5538 becoming a
5539 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
5540 next week your donation will be
5541 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
5542 by an anonymous donor. Please also consider asking your employer to
5543 match your donation or become a sponsor of SFC. Don&#39;t forget to
5544 spread the word about your support for SFC via email, your blog and or
5545 social media accounts.&lt;/p&gt;
5546
5547 &lt;/blockquote&gt;
5548
5549 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
5550 of Software Freedom Conservancy myself. Perhaps you should be a
5551 supporter too?&lt;/p&gt;
5552 </description>
5553 </item>
5554
5555 <item>
5556 <title>PGP key transition statement for key EE4E02F9</title>
5557 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
5558 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
5559 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
5560 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
5561 set it up properly. I wanted to generate it offline and have it
5562 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
5563 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
5564 time to sit down with an offline machine almost took forever. But
5565 finally I&#39;ve been able to complete the process, and have now moved
5566 from my old GPG key to a new GPG key. See
5567 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
5568 full transition statement, signed with both my old and new key&lt;/a&gt; for
5569 the details. This is my new key:&lt;/p&gt;
5570
5571 &lt;pre&gt;
5572 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]
5573 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
5574 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
5575 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
5576 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
5577 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
5578 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
5579 &lt;/pre&gt;
5580
5581 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
5582 my old key.&lt;/p&gt;
5583
5584 &lt;p&gt;If you signed my old key
5585 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
5586 I&#39;d very much appreciate a signature on my new key, details and
5587 instructions in the transition statement. I m happy to reciprocate if
5588 you have a similarly signed transition statement to present.&lt;/p&gt;
5589 </description>
5590 </item>
5591
5592 <item>
5593 <title>The life and death of a laptop battery</title>
5594 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
5595 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
5596 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
5597 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
5598 But this do not last. The last few laptops gave me a feeling that
5599 within a year, the life time is just a fraction of what it used to be,
5600 and it slowly become painful to use the laptop without power connected
5601 all the time. Because of this, when I got a new Thinkpad X230 laptop
5602 about two years ago, I decided to monitor its battery state to have
5603 more hard facts when the battery started to fail.&lt;/p&gt;
5604
5605 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
5606
5607 &lt;p&gt;First I tried to find a sensible Debian package to record the
5608 battery status, assuming that this must be a problem already handled
5609 by someone else. I found
5610 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
5611 which collects statistics from the battery, but it was completely
5612 broken. I sent a few suggestions to the maintainer, but decided to
5613 write my own collector as a shell script while I waited for feedback
5614 from him. Via
5615 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
5616 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
5617 discovered
5618 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
5619 available in Debian.&lt;/p&gt;
5620
5621 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
5622 battery stats ever since. Now my
5623 /var/log/hjemmenett-battery-status.log file contain around 115,000
5624 measurements, from the time the battery was working great until now,
5625 when it is unable to charge above 7% of original capacity. My
5626 collector shell script is quite simple and look like this:&lt;/p&gt;
5627
5628 &lt;pre&gt;
5629 #!/bin/sh
5630 # Inspired by
5631 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
5632 # See also
5633 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
5634 logfile=/var/log/hjemmenett-battery-status.log
5635
5636 files=&quot;manufacturer model_name technology serial_number \
5637 energy_full energy_full_design energy_now cycle_count status&quot;
5638
5639 if [ ! -e &quot;$logfile&quot; ] ; then
5640 (
5641 printf &quot;timestamp,&quot;
5642 for f in $files; do
5643 printf &quot;%s,&quot; $f
5644 done
5645 echo
5646 ) &gt; &quot;$logfile&quot;
5647 fi
5648
5649 log_battery() {
5650 # Print complete message in one echo call, to avoid race condition
5651 # when several log processes run in parallel.
5652 msg=$(printf &quot;%s,&quot; $(date +%s); \
5653 for f in $files; do \
5654 printf &quot;%s,&quot; $(cat $f); \
5655 done)
5656 echo &quot;$msg&quot;
5657 }
5658
5659 cd /sys/class/power_supply
5660
5661 for bat in BAT*; do
5662 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
5663 done
5664 &lt;/pre&gt;
5665
5666 &lt;p&gt;The script is called when the power management system detect a
5667 change in the power status (power plug in or out), and when going into
5668 and out of hibernation and suspend. In addition, it collect a value
5669 every 10 minutes. This make it possible for me know when the battery
5670 is discharging, charging and how the maximum charge change over time.
5671 The code for the Debian package
5672 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
5673 available on github&lt;/a&gt;.&lt;/p&gt;
5674
5675 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
5676
5677 &lt;pre&gt;
5678 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
5679 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
5680 [...]
5681 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
5682 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
5683 &lt;/pre&gt;
5684
5685 &lt;p&gt;I wrote a small script to create a graph of the charge development
5686 over time. This graph depicted above show the slow death of my laptop
5687 battery.&lt;/p&gt;
5688
5689 &lt;p&gt;But why is this happening? Why are my laptop batteries always
5690 dying in a year or two, while the batteries of space probes and
5691 satellites keep working year after year. If we are to believe
5692 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
5693 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
5694 chance, and the fix is to not charge the Lithium-ion batteries to 100%
5695 all the time, but to stay below 90% of full charge most of the time.
5696 I&#39;ve been told that the Tesla electric cars
5697 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
5698 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
5699 100% when preparing for a longer trip (not that I would want a car
5700 like Tesla where rights to privacy is abandoned, but that is another
5701 story), which I guess is the option we should have for laptops on
5702 Linux too.&lt;/p&gt;
5703
5704 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
5705 stop charging at 80%, unless requested to charge to 100% once in
5706 preparation for a longer trip? I found
5707 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
5708 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
5709 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
5710 load).&lt;/p&gt;
5711
5712 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
5713 at the start. I also wonder why the &quot;full capacity&quot; increases some
5714 times, and if it is possible to repeat the process to get the battery
5715 back to design capacity. And I wonder if the discharge and charge
5716 speed change over time, or if this stay the same. I did not yet try
5717 to write a tool to calculate the derivative values of the battery
5718 level, but suspect some interesting insights might be learned from
5719 those.&lt;/p&gt;
5720
5721 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
5722 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
5723 packages instead of the tp-smapi-dkms package I had tried to use
5724 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
5725 and stop. I&#39;ve done so now, but expect my existing battery is toast
5726 and need to be replaced. The proposal is unfortunately Thinkpad
5727 specific.&lt;/p&gt;
5728 </description>
5729 </item>
5730
5731 <item>
5732 <title>New laptop - some more clues and ideas based on feedback</title>
5733 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
5734 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
5735 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
5736 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
5737 need for a new laptop, and provided very useful feedback. I wish to
5738 thank every one of these. Several pointed me to the possibility of
5739 fixing my X230, and I am already in the process of getting Lenovo to
5740 do so thanks to the on site, next day support contract covering the
5741 machine. But the battery is almost useless (I expect to replace it
5742 with a non-official battery) and I do not expect the machine to live
5743 for many more years, so it is time to plan its replacement. If I did
5744 not have a support contract, it was suggested to find replacement parts
5745 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
5746 might present a language barrier as I do not understand French.&lt;/p&gt;
5747
5748 &lt;p&gt;One tip I got was to use the
5749 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
5750 compare laptop models. It seem to have more models available than
5751 prisjakt.no. Another tip I got from someone I know have similar
5752 keyboard preferences was that the HP EliteBook 840 keyboard is not
5753 very good, and this matches my experience with earlier EliteBook
5754 keyboards I tested. Because of this, I will not consider it any further.
5755
5756 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
5757 newest Thinkpad X model. The keyboard reintroduces mouse buttons
5758 (which is missing from the X240), and is working fairly well with
5759 Debian Sid/Unstable according to
5760 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
5761 got on the keyboard quality are not consistent. Some say the keyboard
5762 is good, others say it is ok, while others say it is not very good.
5763 Those with experience from X41 and and X60 agree that the X250
5764 keyboard is not as good as those trusty old laptops, and suggest I
5765 keep and fix my X230 instead of upgrading, or get a used X230 to
5766 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
5767 activity and battery status, which is very convenient on my X230. I&#39;m
5768 also told that the CPU fan is running very often, making it a bit
5769 noisy. In any case, the X250 do not work out of the box with Debian
5770 Stable/Jessie, one of my requirements.&lt;/p&gt;
5771
5772 &lt;p&gt;I have also gotten a few vendor proposals, one was
5773 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
5774 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
5775 The latter look very attractive to me.&lt;/p&gt;
5776
5777 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
5778 as I keep looking for a replacement.&lt;/p&gt;
5779
5780 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
5781 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
5782 different
5783 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
5784 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
5785 </description>
5786 </item>
5787
5788 <item>
5789 <title>Time to find a new laptop, as the old one is broken after only two years</title>
5790 <link>https://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</link>
5791 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</guid>
5792 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
5793 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
5794 replacement soon. The left 5 cm of the screen on my Thinkpad X230
5795 started flickering yesterday, and I suspect the cause is a broken
5796 cable, as changing the angle of the screen some times get rid of the
5797 flickering.&lt;/p&gt;
5798
5799 &lt;p&gt;My requirements have not really changed since I bought it, and is
5800 still as
5801 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
5802 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
5803 good help from
5804 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
5805 where I could select at least a few of the requirements (mouse pin,
5806 wifi, weight) and go through the rest manually. Three button mouse
5807 and a good keyboard is not available as an option, and all the three
5808 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
5809 G2) lack three mouse buttons). It is also unclear to me how good the
5810 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
5811 the keyboard, even if the quality and robustness in the X series have
5812 deteriorated since X41.&lt;/p&gt;
5813
5814 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
5815 seem sensible to me? Are there better services around to search the
5816 set of available laptops for features? Please send me an email if you
5817 have suggestions.&lt;/p&gt;
5818
5819 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
5820 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
5821 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
5822 </description>
5823 </item>
5824
5825 <item>
5826 <title>How to stay with sysvinit in Debian Jessie</title>
5827 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
5828 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
5829 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
5830 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
5831 sysvinit as its boot system by default. But how can one keep using
5832 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
5833 courtesy of
5834 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
5835 Schubert&lt;/a&gt; and
5836 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
5837 McVittie&lt;/a&gt;.
5838
5839 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
5840 keep sysvinit as your boot system, create a file
5841 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
5842 you upgrade:&lt;/p&gt;
5843
5844 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5845 Package: systemd-sysv
5846 Pin: release o=Debian
5847 Pin-Priority: -1
5848 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5849
5850 &lt;p&gt;This file content will tell apt and aptitude to not consider
5851 installing systemd-sysv as part of any installation and upgrade
5852 solution when resolving dependencies, and thus tell it to avoid
5853 systemd as a default boot system. The end result should be that the
5854 upgraded system keep using sysvinit.&lt;/p&gt;
5855
5856 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
5857 get sysvinit installed by default (debootstrap used by
5858 debian-installer have no option for this), but one can tell the
5859 installer to switch to sysvinit before the first boot. Either by
5860 using a kernel argument to the installer, or by adding a line to the
5861 preseed file used. First, the kernel command line argument:
5862
5863 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5864 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
5865 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5866
5867 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
5868
5869 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5870 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
5871 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5872
5873 &lt;p&gt;One can of course also do this after the first boot by installing
5874 the sysvinit-core package.&lt;/p&gt;
5875
5876 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
5877 sysvinit boot sequence in Debian have several hardware specific bugs
5878 on Linux caused by the fact that it is unpredictable when hardware
5879 devices show up during boot. But on the other hand, the new default
5880 boot system still have a few rough edges I hope will be fixed before
5881 Jessie is released.&lt;/p&gt;
5882
5883 &lt;p&gt;Update 2014-11-26: Inspired by
5884 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
5885 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
5886 line.&lt;/p&gt;
5887 </description>
5888 </item>
5889
5890 <item>
5891 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
5892 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
5893 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
5894 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
5895 <description>&lt;p&gt;The right to communicate with your friends and family in private,
5896 without anyone snooping, is a right every citicen have in a liberal
5897 democracy. But this right is under serious attack these days.&lt;/p&gt;
5898
5899 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
5900 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
5901 the whisleblower Snowden) more expensive for Internet email,
5902 is to deliver all email using SMTP via Tor. Such SMTP option would be
5903 a nice addition to the FreedomBox project if we could send email
5904 between FreedomBox machines without leaking metadata about the emails
5905 to the people peeking on the wire. I
5906 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
5907 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
5908 lot of useful feedback and suggestions. It also became obvious to me
5909 that this was not a novel idea, as the same idea was tested and
5910 documented by Johannes Berg as early as 2006, and both
5911 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
5912 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
5913 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
5914
5915 &lt;p&gt;To implement such system one need to set up a Tor hidden service
5916 providing the SMTP protocol on port 25, and use email addresses
5917 looking like username@hidden-service-name.onion. With such addresses
5918 the connections to port 25 on hidden-service-name.onion using Tor will
5919 go to the correct SMTP server. To do this, one need to configure the
5920 Tor daemon to provide the hidden service and the mail server to accept
5921 emails for this .onion domain. To learn more about Exim configuration
5922 in Debian and test the design provided by Johannes Berg in his FAQ, I
5923 set out yesterday to create a Debian package for making it trivial to
5924 set up such SMTP over Tor service based on Debian. Getting it to work
5925 were fairly easy, and
5926 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
5927 source code for the Debian package&lt;/a&gt; is available from github. I
5928 plan to move it into Debian if further testing prove this to be a
5929 useful approach.&lt;/p&gt;
5930
5931 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
5932 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
5933 get rid of exim4). Install tor, clone the git repository mentioned
5934 above, build the deb and install it on the machine. Next, run
5935 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
5936 the instructions to get the service up and running. Restart tor and
5937 exim when it is done, and test mail delivery using swaks like
5938 this:&lt;/p&gt;
5939
5940 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5941 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
5942 --to fbx@dutlqrrmjhtfa3vp.onion
5943 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5944
5945 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
5946 address with your own address to test your server. :)&lt;/p&gt;
5947
5948 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
5949 easier and more automatic. Especially the tor setup need more work.
5950 Also, the package include a tor-smtp tool written in C, but its task
5951 should probably be rewritten in some script language to make the deb
5952 architecture independent. It would probably also make the code easier
5953 to review. The tor-smtp tool currently need to listen on a socket for
5954 exim to talk to it and is started using xinetd. It would be better if
5955 no daemon and no socket is needed. I suspect it is possible to get
5956 exim to run a command line tool for delivery instead of talking to a
5957 socket, and hope to figure out how in a future version of this
5958 system.&lt;/p&gt;
5959
5960 &lt;p&gt;Until I wipe my test machine, I can be reached using the
5961 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
5962 SMTorP. :)&lt;/p&gt;
5963 </description>
5964 </item>
5965
5966 <item>
5967 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
5968 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
5969 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
5970 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
5971 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
5972 alioth.debian.org, you know the web interface is fairly slow to
5973 operate. First you visit one web page, enter the moderation password
5974 and get a new page shown with a list of all the messages to moderate
5975 and various options for each email address. This take a while for
5976 every list you moderate, and you need to do it regularly to do a good
5977 job as a list moderator. But there is a quick alternative,
5978 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
5979 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
5980 to moderate in a fraction of a second. Here is a test run on two
5981 lists I recently took over:&lt;/p&gt;
5982
5983 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5984 % time listadmin xiph
5985 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
5986 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
5987
5988 real 0m1.709s
5989 user 0m0.232s
5990 sys 0m0.012s
5991 %
5992 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5993
5994 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
5995 there are no message in the moderation queue. Every morning I
5996 currently moderate 68 mailman lists, and it normally take around two
5997 minutes. When I took over the two pkg-xiph lists above a few days
5998 ago, there were 400 emails waiting in the moderator queue. It took me
5999 less than 15 minutes to process them all using the listadmin
6000 program.&lt;/p&gt;
6001
6002 &lt;p&gt;If you install
6003 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
6004 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
6005 with content like this, the moderation task is a breeze:&lt;/p&gt;
6006
6007 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6008 username username@example.org
6009 spamlevel 23
6010 default discard
6011 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
6012
6013 password secret
6014 adminurl https://{domain}/mailman/admindb/{list}
6015 mailman-list@lists.example.com
6016
6017 password hidden
6018 other-list@otherserver.example.org
6019 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6020
6021 &lt;p&gt;There are other options to set as well. Check the manual page to
6022 learn the details.&lt;/p&gt;
6023
6024 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
6025 the SSL certificate is self signed or not properly signed by a
6026 generally accepted signing authority, you can set a environment
6027 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
6028
6029 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6030 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
6031 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6032
6033 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
6034 can provide an argument to the listadmin script like I do in the
6035 initial screen dump (the xiph argument). Using an argument, only
6036 lists matching the argument string will be processed. This make it
6037 quick to accept messages if you notice the moderation request in your
6038 email.&lt;/p&gt;
6039
6040 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
6041 mailing lists, as I simply do not have time to spend on that if the
6042 process was any slower. The listadmin program have saved me hours of
6043 time I could spend elsewhere over the years. It truly is nice free
6044 software.&lt;/p&gt;
6045
6046 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
6047 activities, please send Bitcoin donations to my address
6048 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6049
6050 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
6051 configuration example. Also, I&#39;ve been told that the
6052 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
6053 sure why.&lt;/p&gt;
6054 </description>
6055 </item>
6056
6057 <item>
6058 <title>Debian Jessie, PXE and automatic firmware installation</title>
6059 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
6060 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
6061 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
6062 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
6063 problem that the WiFi card require some firmware to work properly.
6064 And it has been a pain to fix this using preseeding in Debian.
6065 Normally something more is needed. But thanks to
6066 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
6067 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
6068 to do this using simple preseeding.&lt;/p&gt;
6069
6070 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
6071 firmware for the hardware found in the machine (actually, requested by
6072 the kernel modules for the hardware). (It can also install user space
6073 programs supporting the hardware detected, but that is not the focus
6074 of this story.)&lt;/p&gt;
6075
6076 &lt;p&gt;To get this working in the default installation, two preeseding
6077 values are needed. First, the isenkram-cli package must be installed
6078 into the target chroot (aka the hard drive) before tasksel is executed
6079 in the pkgsel step of the debian-installer system. This is done by
6080 preseeding the base-installer/includes debconf value to include the
6081 isenkram-cli package. The package name is next passed to debootstrap
6082 for installation. With the isenkram-cli package in place, tasksel
6083 will automatically use the isenkram tasks to detect hardware specific
6084 packages for the machine being installed and install them, because
6085 isenkram-cli contain tasksel tasks.&lt;/p&gt;
6086
6087 &lt;p&gt;Second, one need to enable the non-free APT repository, because
6088 most firmware unfortunately is non-free. This is done by preseeding
6089 the apt-mirror-setup step. This is unfortunate, but for a lot of
6090 hardware it is the only option in Debian.&lt;/p&gt;
6091
6092 &lt;p&gt;The end result is two lines needed in your preseeding file to get
6093 firmware installed automatically by the installer:&lt;/p&gt;
6094
6095 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6096 base-installer base-installer/includes string isenkram-cli
6097 apt-mirror-setup apt-setup/non-free boolean true
6098 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6099
6100 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
6101 both firmware and user space packages when using this method. It also
6102 do not work well, so use version 0.15 or later. Installing both
6103 firmware and user space packages might give you a bit more than you
6104 want, so I decided to split the tasksel task in two, one for firmware
6105 and one for user space programs. The firmware task is enabled by
6106 default, while the one for user space programs is not. This split is
6107 implemented in the package currently in unstable.&lt;/p&gt;
6108
6109 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
6110 this recipe work for you. :)&lt;/p&gt;
6111
6112 &lt;p&gt;So, I bet you are wondering, how can this work. First and
6113 foremost, it work because tasksel is modular, and driven by whatever
6114 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
6115 isenkram-cli package place two files for tasksel to find. First there
6116 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
6117
6118 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6119 Task: isenkram-packages
6120 Section: hardware
6121 Description: Hardware specific packages (autodetected by isenkram)
6122 Based on the detected hardware various hardware specific packages are
6123 proposed.
6124 Test-new-install: show show
6125 Relevance: 8
6126 Packages: for-current-hardware
6127
6128 Task: isenkram-firmware
6129 Section: hardware
6130 Description: Hardware specific firmware packages (autodetected by isenkram)
6131 Based on the detected hardware various hardware specific firmware
6132 packages are proposed.
6133 Test-new-install: mark show
6134 Relevance: 8
6135 Packages: for-current-hardware-firmware
6136 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6137
6138 &lt;p&gt;The key parts are Test-new-install which indicate how the task
6139 should be handled and the Packages line referencing to a script in
6140 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
6141 list of packages to install. The for-current-hardware-firmware script
6142 look like this to list relevant firmware for the machine:
6143
6144 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6145 #!/bin/sh
6146 #
6147 PATH=/usr/sbin:$PATH
6148 export PATH
6149 isenkram-autoinstall-firmware -l
6150 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6151
6152 &lt;p&gt;With those two pieces in place, the firmware is installed by
6153 tasksel during the normal d-i run. :)&lt;/p&gt;
6154
6155 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
6156 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
6157 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
6158 install.&lt;/p&gt;
6159
6160 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
6161 pilots in testing this feature, as isenkram is used there now to
6162 install firmware, replacing the earlier scripts.&lt;/p&gt;
6163 </description>
6164 </item>
6165
6166 <item>
6167 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
6168 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
6169 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
6170 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
6171 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
6172 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
6173 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
6174 on a screen normally showing the bread types and prizes:&lt;/p&gt;
6175
6176 &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;
6177
6178 &lt;p&gt;If it had booted as it was supposed to, I would never had known
6179 about this hidden Linux installation. It is interesting what
6180 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
6181 </description>
6182 </item>
6183
6184 <item>
6185 <title>New lsdvd release version 0.17 is ready</title>
6186 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
6187 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
6188 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
6189 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
6190 got a new set of developers a few weeks ago, after the original
6191 developer decided to step down and pass the project to fresh blood.
6192 This project is now maintained by Petter Reinholdtsen and Steve
6193 Dibb.&lt;/p&gt;
6194
6195 &lt;p&gt;I just wrapped up
6196 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
6197 new lsdvd release&lt;/a&gt;, available in git or from
6198 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
6199 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
6200 0.17.&lt;/p&gt;
6201
6202 &lt;ul&gt;
6203
6204 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
6205 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
6206 non-existant, to work around additional copy protection&lt;/li&gt;
6207 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
6208 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
6209 &lt;li&gt;Fix include orders&lt;/li&gt;
6210 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
6211 &lt;li&gt;Fix the chapter count&lt;/li&gt;
6212 &lt;li&gt;Make sure the array size and the array limit used when initialising
6213 the palette size is the same.&lt;/li&gt;
6214 &lt;li&gt;Fix array printing.&lt;/li&gt;
6215 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
6216 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
6217 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
6218 with more GCC compiler warnings.&lt;/li&gt;
6219
6220 &lt;/ul&gt;
6221
6222 &lt;p&gt;This change bring together patches for lsdvd in use in various
6223 Linux and Unix distributions, as well as patches submitted to the
6224 project the last nine years. Please check it out. :)&lt;/p&gt;
6225 </description>
6226 </item>
6227
6228 <item>
6229 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
6230 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
6231 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
6232 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
6233 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
6234 project&lt;/a&gt; provide a Linux solution for schools, including a
6235 powerful desktop with education software, a central server providing
6236 web pages, user database, user home directories, central login and PXE
6237 boot of both clients without disk and the installation to install Debian
6238 Edu on machines with disk (and a few other services perhaps to small
6239 to mention here). We in the Debian Edu team are currently working on
6240 the Jessie based version, trying to get everything in shape before the
6241 freeze, to avoid having to maintain our own package repository in the
6242 future. The
6243 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
6244 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
6245 work left. Some fatal problems block testing, breaking the installer,
6246 but it is possible to work around these to get anyway. Here is a
6247 recipe on how to get the installation limping along.&lt;/p&gt;
6248
6249 &lt;p&gt;First, download the test ISO via
6250 &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;,
6251 &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;
6252 or rsync (use
6253 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
6254 The ISO build was broken on Tuesday, so we do not get a new ISO every
6255 12 hours or so, but thankfully the ISO we already got we are able to
6256 install with some tweaking.&lt;/p&gt;
6257
6258 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
6259 (use Alt-Ctrl-F2), run&lt;/p&gt;
6260
6261 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6262 nano /usr/bin/edu-eatmydata-install
6263 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6264
6265 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
6266 optimization. Return to the installation, select the profile you want
6267 and continue. Without this change, exim4-config will fail to install
6268 due to a known bug in eatmydata.&lt;/p&gt;
6269
6270 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
6271 this do not work, figure out what your correct value would be. All my
6272 test machines need /dev/sda, so I have no advice if it do not fit
6273 your need.&lt;/p&gt;
6274
6275 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
6276 root after the initial boot from hard drive, and install the
6277 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
6278 or mate. If you want several desktop options, install more than one
6279 metapackage. Once this is done, reboot and you should have a working
6280 graphical login screen. This workaround should no longer be needed
6281 once the education-tasks package version 1.801 enter testing in two
6282 days.&lt;/p&gt;
6283
6284 &lt;p&gt;I believe the ISO build will start working on two days when the new
6285 tasksel package enter testing and Steve McIntyre get a chance to
6286 update the debian-cd git repository. The eatmydata, grub and desktop
6287 issues are already fixed in unstable and testing, and should show up
6288 on the ISO as soon as the ISO build start working again. Well the
6289 eatmydata optimization is really just disabled. The proper fix
6290 require an upload by the eatmydata maintainer applying the patch
6291 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
6292 The rest have proper fixes in unstable.&lt;/p&gt;
6293
6294 &lt;p&gt;I hope this get you going with the installation testing, as we are
6295 quickly running out of time trying to get our Jessie based
6296 installation ready before the distribution freeze in a month.&lt;/p&gt;
6297 </description>
6298 </item>
6299
6300 <item>
6301 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
6302 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
6303 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
6304 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
6305 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
6306 to handle my fairly large DVD collection. It is a nice command line
6307 tool to get details about a DVD, like title, tracks, track length,
6308 etc, in XML, Perl or human readable format. But lsdvd have not seen
6309 any new development since 2006 and had a few irritating bugs affecting
6310 its use with some DVDs. Upstream seemed to be dead, and in January I
6311 sent a small probe asking for a version control repository for the
6312 project, without any reply. But I use it regularly and would like to
6313 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
6314 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
6315 the project admin, and after getting a reply from him explaining that
6316 he was no longer interested in the project, I asked if I could take
6317 over. And yesterday, I became project admin.&lt;/p&gt;
6318
6319 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
6320 maintainer interested in joining forces to maintain the upstream
6321 project, and I hope we can get a new release out fairly quickly,
6322 collecting the patches spread around on the internet into on place.
6323 I&#39;ve added the relevant Debian patches to the freshly created git
6324 repository, and expect the Gentoo patches to make it too. If you got
6325 a DVD collection and care about command line tools, check out
6326 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
6327 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
6328 list&lt;/a&gt;. :)&lt;/p&gt;
6329 </description>
6330 </item>
6331
6332 <item>
6333 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
6334 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
6335 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
6336 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
6337 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
6338 a lot quicker. When we install more than 2000 packages in
6339 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
6340 tasksel in the installer, unpacking the binary packages take forever.
6341 A part of the slow I/O issue was discussed in
6342 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
6343 much file system sync-ing done by dpkg, which is the package
6344 responsible for unpacking the binary packages. Other parts (like code
6345 executed by postinst scripts) might also sync to disk during
6346 installation. All this sync-ing to disk do not really make sense to
6347 me. If the machine crash half-way through, I start over, I do not try
6348 to salvage the half installed system. So the failure sync-ing is
6349 supposed to protect against, hardware or system crash, is not really
6350 relevant while the installer is running.&lt;/p&gt;
6351
6352 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
6353 system sync()-ing in a fairly non-intrusive way, without the need to
6354 change the code in several packages. The idea is not new, but I have
6355 not heard anyone propose the approach using dpkg-divert before. It
6356 depend on the small and clever package
6357 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
6358 uses LD_PRELOAD to replace the system functions for syncing data to
6359 disk with functions doing nothing, thus allowing programs to live
6360 dangerous while speeding up disk I/O significantly. Instead of
6361 modifying the implementation of dpkg, apt and tasksel (which are the
6362 packages responsible for selecting, fetching and installing packages),
6363 it occurred to me that we could just divert the programs away, replace
6364 them with a simple shell wrapper calling
6365 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
6366 Two days ago I decided to test the idea, and wrapped up a simple
6367 implementation for the Debian Edu udeb.&lt;/p&gt;
6368
6369 &lt;p&gt;The effect was stunning. In my first test it reduced the running
6370 time of the pkgsel step (installing tasks) from 64 to less than 44
6371 minutes (20 minutes shaved off the installation) on an old Dell
6372 Latitude D505 machine. I am not quite sure what the optimised time
6373 would have been, as I messed up the testing a bit, causing the debconf
6374 priority to get low enough for two questions to pop up during
6375 installation. As soon as I saw the questions I moved the installation
6376 along, but do not know how long the question were holding up the
6377 installation. I did some more measurements using Debian Edu Jessie,
6378 and got these results. The time measured is the time stamp in
6379 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
6380 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
6381 yourself. In Debian Edu, the tasksel dialog do not show up, and the
6382 timing thus do not depend on how quickly the user handle the tasksel
6383 dialog.&lt;/p&gt;
6384
6385 &lt;p&gt;&lt;table&gt;
6386
6387 &lt;tr&gt;
6388 &lt;th&gt;Machine/setup&lt;/th&gt;
6389 &lt;th&gt;Original tasksel&lt;/th&gt;
6390 &lt;th&gt;Optimised tasksel&lt;/th&gt;
6391 &lt;th&gt;Reduction&lt;/th&gt;
6392 &lt;/tr&gt;
6393
6394 &lt;tr&gt;
6395 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
6396 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
6397 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
6398 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
6399 &lt;/tr&gt;
6400
6401 &lt;tr&gt;
6402 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
6403 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
6404 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
6405 &lt;td&gt;23 min 40%&lt;/td&gt;
6406 &lt;/tr&gt;
6407
6408 &lt;tr&gt;
6409 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
6410 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
6411 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
6412 &lt;td&gt;11 min 50%&lt;/td&gt;
6413 &lt;/tr&gt;
6414
6415 &lt;tr&gt;
6416 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
6417 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
6418 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
6419 &lt;td&gt;2 min 33%&lt;/td&gt;
6420 &lt;/tr&gt;
6421
6422 &lt;tr&gt;
6423 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
6424 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
6425 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
6426 &lt;td&gt;4 min 21%&lt;/td&gt;
6427 &lt;/tr&gt;
6428
6429 &lt;/table&gt;&lt;/p&gt;
6430
6431 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
6432 time is spent downloading packages. The connection to the Internet
6433 was 100Mbit/s during testing, so downloading should not be a
6434 significant factor in the measurement. Download typically took a few
6435 seconds to a few minutes, depending on the amount of packages being
6436 installed.&lt;/p&gt;
6437
6438 &lt;p&gt;The speedup is implemented by using two hooks in
6439 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
6440 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
6441 finish-install.d hook to remove the divert at the end of the
6442 installation. I picked the pre-pkgsel.d hook instead of the
6443 post-base-installer.d hook because I test using an ISO without the
6444 eatmydata package included, and the post-base-installer.d hook in
6445 Debian Edu can only operate on packages included in the ISO. The
6446 negative effect of this is that I am unable to activate this
6447 optimization for the kernel installation step in d-i. If the code is
6448 moved to the post-base-installer.d hook, the speedup would be larger
6449 for the entire installation.&lt;/p&gt;
6450
6451 &lt;p&gt;I&#39;ve implemented this in the
6452 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
6453 git repository, and plan to provide the optimization as part of the
6454 Debian Edu installation. If you want to test this yourself, you can
6455 create two files in the installer (or in an udeb). One shell script
6456 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
6457
6458 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6459 #!/bin/sh
6460 set -e
6461 . /usr/share/debconf/confmodule
6462 info() {
6463 logger -t my-pkgsel &quot;info: $*&quot;
6464 }
6465 error() {
6466 logger -t my-pkgsel &quot;error: $*&quot;
6467 }
6468 override_install() {
6469 apt-install eatmydata || true
6470 if [ -x /target/usr/bin/eatmydata ] ; then
6471 for bin in dpkg apt-get aptitude tasksel ; do
6472 file=/usr/bin/$bin
6473 # Test that the file exist and have not been diverted already.
6474 if [ -f /target$file ] ; then
6475 info &quot;diverting $file using eatmydata&quot;
6476 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
6477 &gt; /target$file.edu
6478 chmod 755 /target$file.edu
6479 in-target dpkg-divert --package debian-edu-config \
6480 --rename --quiet --add $file
6481 ln -sf ./$bin.edu /target$file
6482 else
6483 error &quot;unable to divert $file, as it is missing.&quot;
6484 fi
6485 done
6486 else
6487 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
6488 fi
6489 }
6490
6491 override_install
6492 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6493
6494 &lt;p&gt;To clean up, another shell script should go into
6495 /usr/lib/finish-install.d/ with code like this:
6496
6497 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6498 #! /bin/sh -e
6499 . /usr/share/debconf/confmodule
6500 error() {
6501 logger -t my-finish-install &quot;error: $@&quot;
6502 }
6503 remove_install_override() {
6504 for bin in dpkg apt-get aptitude tasksel ; do
6505 file=/usr/bin/$bin
6506 if [ -x /target$file.edu ] ; then
6507 rm /target$file
6508 in-target dpkg-divert --package debian-edu-config \
6509 --rename --quiet --remove $file
6510 rm /target$file.edu
6511 else
6512 error &quot;Missing divert for $file.&quot;
6513 fi
6514 done
6515 sync # Flush file buffers before continuing
6516 }
6517
6518 remove_install_override
6519 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6520
6521 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
6522 edu-eatmydata-install and call it from the pre-pkgsel.d and
6523 finish-install.d scripts.&lt;/p&gt;
6524
6525 &lt;p&gt;By now you might ask if this change should get into the normal
6526 Debian installer too? I suspect it should, but am not sure the
6527 current debian-installer coordinators find it useful enough. It also
6528 depend on the side effects of the change. I&#39;m not aware of any, but I
6529 guess we will see if the change is safe after some more testing.
6530 Perhaps there is some package in Debian depending on sync() and
6531 fsync() having effect? Perhaps it should go into its own udeb, to
6532 allow those of us wanting to enable it to do so without affecting
6533 everyone.&lt;/p&gt;
6534
6535 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
6536 will break installation of all programs using gnutls because of
6537 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
6538 eatmydata package in Debian will solve it.&lt;/p&gt;
6539
6540 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
6541 the optimization work again. And I have discovered that the
6542 dpkg-divert trick is not really needed and implemented a slightly
6543 simpler approach as part of the debian-edu-install package. See
6544 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
6545
6546 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
6547 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
6548 triggering on i386 made it into testing, and broke this installation
6549 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
6550 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
6551 </description>
6552 </item>
6553
6554 <item>
6555 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
6556 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
6557 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
6558 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
6559 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
6560 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
6561 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
6562 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
6563 learn that there is a large set of publicly available key servers to
6564 use when looking for peoples public key. So far I have used
6565 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
6566 were misbehaving, but those days are ended. The servers I have used
6567 up until yesterday have been slow and some times unavailable. I hope
6568 those problems are gone now.&lt;/p&gt;
6569
6570 &lt;p&gt;Behind the round robin DNS entry of the
6571 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
6572 there is a pool of more than 100 keyservers which are checked every
6573 day to ensure they are well connected and up to date. It must be
6574 better than what I have used so far. :)&lt;/p&gt;
6575
6576 &lt;p&gt;Yesterdays speaker told me that the service is the default
6577 keyserver provided by the default configuration in GnuPG, but this do
6578 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
6579
6580 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
6581 line:&lt;/p&gt;
6582
6583 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6584 keyserver pool.sks-keyservers.net
6585 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6586
6587 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
6588 entries in DNS. Just for fun, I did just that at work, so now every
6589 user of GnuPG at the University of Oslo should find a OpenGPG
6590 keyserver automatically should their need it:&lt;/p&gt;
6591
6592 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6593 % host -t srv _pgpkey-http._tcp.uio.no
6594 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
6595 %
6596 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6597
6598 &lt;p&gt;Now if only
6599 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
6600 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
6601 very happy. It can look up a given key or search for a user ID, but I
6602 normally do not want that, but to find a trust path from my key to
6603 another key. Given a user ID or key ID, I would like to find (and
6604 download) the keys representing a signature path from my key to the
6605 key in question, to be able to get a trust path between the two keys.
6606 This is as far as I can tell not possible today. Perhaps something
6607 for a future version of the protocol?&lt;/p&gt;
6608 </description>
6609 </item>
6610
6611 <item>
6612 <title>From English wiki to translated PDF and epub via Docbook</title>
6613 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
6614 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
6615 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
6616 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
6617 project&lt;/a&gt; provide an instruction manual for teachers, system
6618 administrators and other users that contain useful tips for setting up
6619 and maintaining a Debian Edu installation. This text is about how the
6620 text processing of this manual is handled in the project.&lt;/p&gt;
6621
6622 &lt;p&gt;One goal of the project is to provide information in the native
6623 language of its users, and for this we need to handle translations.
6624 But we also want to make sure each language contain the same
6625 information, so for this we need a good way to keep the translations
6626 in sync. And we want it to be easy for our users to improve the
6627 documentation, avoiding the need to learn special formats or tools to
6628 contribute, and the obvious way to do this is to make it possible to
6629 edit the documentation using a web browser. We also want it to be
6630 easy for translators to keep the translation up to date, and give them
6631 help in figuring out what need to be translated. Here is the list of
6632 tools and the process we have found trying to reach all these
6633 goals.&lt;/p&gt;
6634
6635 &lt;p&gt;We maintain the authoritative source of our manual in the
6636 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
6637 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
6638 front page with references to the different chapters, several pages
6639 for each chapter, and finally one &quot;collection page&quot; gluing all the
6640 chapters together into one large web page (aka
6641 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
6642 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
6643 processing and translations. Thanks to the fact that the
6644 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
6645 wiki.debian.org support exporting pages in
6646 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
6647 the list of pages to export using the raw version of the AllInOne
6648 page, loop over each of them to generate a Docbook XML version of the
6649 manual. This process also download images and transform image
6650 references to use the locally downloaded images. The generated
6651 Docbook XML files are slightly broken, so some post-processing is done
6652 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
6653 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
6654 a handfull of images. The XML file can now be used to generate PDF, HTML
6655 and epub versions of the English manual. This is the basic step of
6656 our process, making PDF (using dblatex), HTML (using xsltproc) and
6657 epub (using dbtoepub) version from Docbook XML, and the resulting files
6658 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
6659
6660 &lt;p&gt;But English documentation is not enough for us. We want translated
6661 documentation too, and we want to make it easy for translators to
6662 track the English original. For this we use the
6663 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
6664 which allow us to transform the English Docbook XML file into a
6665 translation file (a .pot file), usable with the normal gettext based
6666 translation tools used by those translating free software. The pot
6667 file is used to create and maintain translation files (several .po
6668 files), which the translations update with the native language
6669 translations of all titles, paragraphs and blocks of text in the
6670 original. The next step is combining the original English Docbook XML
6671 and the translation file (say debian-edu-wheezy-manual.nb.po), to
6672 create a translated Docbook XML file (in this case
6673 debian-edu-wheezy-manual.nb.xml). This translated (or partly
6674 translated, if the translation is not complete) Docbook XML file can
6675 then be used like the original to create a PDF, HTML and epub version
6676 of the documentation.&lt;/p&gt;
6677
6678 &lt;p&gt;The translators use different tools to edit the .po files. We
6679 recommend using
6680 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
6681 while some use emacs and vi, others can use web based editors like
6682 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
6683 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
6684 is where the .po file end up, in our git repository. Updated
6685 translations can either be committed directly to git, or submitted as
6686 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
6687 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
6688
6689 &lt;p&gt;One challenge is images, which both might need to be translated (if
6690 they show translated user applications), and are needed in different
6691 formats when creating PDF and HTML versions (epub is a HTML version in
6692 this regard). For this we transform the original PNG images to the
6693 needed density and format during build, and have a way to provide
6694 translated images by storing translated versions in
6695 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
6696 package maintainers know more.&lt;/p&gt;
6697
6698 &lt;p&gt;If you wonder what the result look like, we provide
6699 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
6700 of the documentation packages on the web&lt;/a&gt;. See for example the
6701 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
6702 PDF version&lt;/a&gt; or the
6703 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
6704 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
6705 but perhaps it will be done in the future.&lt;/p&gt;
6706
6707 &lt;p&gt;To learn more, check out
6708 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
6709 debian-edu-doc package&lt;/a&gt;,
6710 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
6711 manual on the wiki&lt;/a&gt; and
6712 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
6713 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
6714 </description>
6715 </item>
6716
6717 <item>
6718 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
6719 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
6720 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
6721 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
6722 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
6723 related packages relevant for the computer installed automatically.
6724 So I implemented one, using
6725 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
6726 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
6727 run tasksel as user root. You should be presented with a new option,
6728 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
6729 select it, tasksel will install the packages isenkram claim is fit for
6730 the current hardware, hot pluggable or not.&lt;p&gt;
6731
6732 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
6733 description, and the other is the script used to extract the list of
6734 packages to install. The first part is in
6735 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
6736 this:&lt;/p&gt;
6737
6738 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6739 Task: isenkram
6740 Section: hardware
6741 Description: Hardware specific packages (autodetected by isenkram)
6742 Based on the detected hardware various hardware specific packages are
6743 proposed.
6744 Test-new-install: mark show
6745 Relevance: 8
6746 Packages: for-current-hardware
6747 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6748
6749 &lt;p&gt;The second part is in
6750 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
6751 this:&lt;/p&gt;
6752
6753 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6754 #!/bin/sh
6755 #
6756 (
6757 isenkram-lookup
6758 isenkram-autoinstall-firmware -l
6759 ) | sort -u
6760 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6761
6762 &lt;p&gt;All in all, a very short and simple implementation making it
6763 trivial to install the hardware dependent package we all may want to
6764 have installed on our machines. I&#39;ve not been able to find a way to
6765 get tasksel to tell you exactly which packages it plan to install
6766 before doing the installation. So if you are curious or careful,
6767 check the output from the isenkram-* command line tools first.&lt;/p&gt;
6768
6769 &lt;p&gt;The information about which packages are handling which hardware is
6770 fetched either from the isenkram package itself in
6771 /usr/share/isenkram/, from git.debian.org or from the APT package
6772 database (using the Modaliases header). The APT package database
6773 parsing have caused a nasty resource leak in the isenkram daemon (bugs
6774 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
6775 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
6776 the python-apt code (bug
6777 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
6778 workaround I was able to get rid of the file descriptor leak and
6779 reduce the memory leak from ~30 MiB per hardware detection down to
6780 around 2 MiB per hardware detection. It should make the desktop
6781 daemon a lot more useful. The fix is in version 0.7 uploaded to
6782 unstable today.&lt;/p&gt;
6783
6784 &lt;p&gt;I believe the current way of mapping hardware to packages in
6785 Isenkram is is a good draft, but in the future I expect isenkram to
6786 use the AppStream data source for this. A proposal for getting proper
6787 AppStream support into Debian is floating around as
6788 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
6789 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
6790 project&lt;/a&gt; will take place this summer to improve the situation. I
6791 look forward to seeing the result, and welcome patches for isenkram to
6792 start using the information when it is ready.&lt;/p&gt;
6793
6794 &lt;p&gt;If you want your package to map to some specific hardware, either
6795 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
6796 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
6797 package&lt;/a&gt; or submit a bug report with the details to the isenkram
6798 package. See also
6799 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
6800 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
6801 the information will be migrated to AppStream eventually, but for the
6802 moment I got no better place to store it.&lt;/p&gt;
6803 </description>
6804 </item>
6805
6806 <item>
6807 <title>FreedomBox milestone - all packages now in Debian Sid</title>
6808 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
6809 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
6810 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
6811 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
6812 project&lt;/a&gt; is working on providing the software and hardware to make
6813 it easy for non-technical people to host their data and communication
6814 at home, and being able to communicate with their friends and family
6815 encrypted and away from prying eyes. It is still going strong, and
6816 today a major mile stone was reached.&lt;/p&gt;
6817
6818 &lt;p&gt;Today, the last of the packages currently used by the project to
6819 created the system images were accepted into Debian Unstable. It was
6820 the freedombox-setup package, which is used to configure the images
6821 during build and on the first boot. Now all one need to get going is
6822 the build code from the freedom-maker git repository and packages from
6823 Debian. And once the freedombox-setup package enter testing, we can
6824 build everything directly from Debian. :)&lt;/p&gt;
6825
6826 &lt;p&gt;Some key packages used by Freedombox are
6827 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
6828 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
6829 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
6830 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
6831 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
6832 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
6833 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
6834 are plans to integrate more packages into the setup. User
6835 documentation is maintained on the Debian wiki. Please
6836 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
6837 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
6838
6839 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
6840 setup, run this on a Debian machine using a user with sudo rights to
6841 become root:&lt;/p&gt;
6842
6843 &lt;p&gt;&lt;pre&gt;
6844 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6845 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6846 u-boot-tools
6847 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6848 freedom-maker
6849 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6850 &lt;/pre&gt;&lt;/p&gt;
6851
6852 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
6853 devices. See the README in the freedom-maker git repo for more
6854 details on the build. If you do not want all three images, trim the
6855 make line. Note that the virtualbox-image target is not really
6856 virtualbox specific. It create a x86 image usable in kvm, qemu,
6857 vmware and any other x86 virtual machine environment. You might need
6858 the version of vmdebootstrap in Jessie to get the build working, as it
6859 include fixes for a race condition with kpartx.&lt;/p&gt;
6860
6861 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
6862 method, boot a Debian Wheezy ISO and use this boot argument to load
6863 the preseed values:&lt;/p&gt;
6864
6865 &lt;p&gt;&lt;pre&gt;
6866 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;
6867 &lt;/pre&gt;&lt;/p&gt;
6868
6869 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
6870 it still work.&lt;/p&gt;
6871
6872 &lt;p&gt;If you wonder how to help, one task you could look at is using
6873 systemd as the boot system. It will become the default for Linux in
6874 Jessie, so we need to make sure it is usable on the Freedombox. I did
6875 a simple test a few weeks ago, and noticed dnsmasq failed to start
6876 during boot when using systemd. I suspect there are other problems
6877 too. :) To detect problems, there is a test suite included, which can
6878 be run from the plinth web interface.&lt;/p&gt;
6879
6880 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
6881 us get the new release published. :) Please join us on
6882 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
6883 irc.debian.org)&lt;/a&gt; and
6884 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6885 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6886 </description>
6887 </item>
6888
6889 <item>
6890 <title>S3QL, a locally mounted cloud file system - nice free software</title>
6891 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
6892 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
6893 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
6894 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
6895 solution for use at home. My requirements are simple, it must be
6896 cheap and locally encrypted (in other words, I keep the encryption
6897 keys, the storage provider do not have access to my private files).
6898 One idea me and my friends had many years ago, before the cloud
6899 storage providers showed up, was to use Google mail as storage,
6900 writing a Linux block device storing blocks as emails in the mail
6901 service provided by Google, and thus get heaps of free space. On top
6902 of this one can add encryption, RAID and volume management to have
6903 lots of (fairly slow, I admit that) cheap and encrypted storage. But
6904 I never found time to implement such system. But the last few weeks I
6905 have looked at a system called
6906 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
6907 mounted network backed file system with the features I need.&lt;/p&gt;
6908
6909 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
6910 handling several different storage providers, any with Amazon S3,
6911 Google Drive or OpenStack API. There are heaps of such storage
6912 providers. S3QL can also use a local directory as storage, which
6913 combined with sshfs allow for file storage on any ssh server. S3QL
6914 include support for encryption, compression, de-duplication, snapshots
6915 and immutable file systems, allowing me to mount the remote storage as
6916 a local mount point, look at and use the files as if they were local,
6917 while the content is stored in the cloud as well. This allow me to
6918 have a backup that should survive fire. The file system can not be
6919 shared between several machines at the same time, as only one can
6920 mount it at the time, but any machine with the encryption key and
6921 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
6922
6923 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
6924 package is included already. So to get started, run &lt;tt&gt;apt-get
6925 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
6926 Greenqloud, after reading their nice recipe on
6927 &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
6928 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
6929 in Iceland more than those in USA when it come to keeping my personal
6930 data safe and private, and thus would rather spend money on a company
6931 in Iceland. Another nice recipe is available from the article
6932 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
6933 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
6934 Admin magazine. When the provider is picked, figure out how to get
6935 the API key needed to connect to the storage API. With Greencloud,
6936 the key did not show up until I had added payment details to my
6937 account.&lt;/p&gt;
6938
6939 &lt;p&gt;Armed with the API access details, it is time to create the file
6940 system. First, create a new bucket in the cloud. This bucket is the
6941 file system storage area. I picked a bucket name reflecting the
6942 machine that was going to store data there, but any name will do.
6943 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
6944 the API login and password, and a locally created password. Store it
6945 all in ~root/.s3ql/authinfo2 like this:
6946
6947 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6948 [s3c]
6949 storage-url: s3c://s.greenqloud.com:443/bucket-name
6950 backend-login: API-login
6951 backend-password: API-password
6952 fs-passphrase: local-password
6953 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6954
6955 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
6956 but any sensible way to create a fairly random password should do it.
6957 Armed with these details, it is now time to run mkfs, entering the API
6958 details and password to create it:&lt;/p&gt;
6959
6960 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6961 # mkdir -m 700 /var/lib/s3ql-cache
6962 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6963 --ssl s3c://s.greenqloud.com:443/bucket-name
6964 Enter backend login:
6965 Enter backend password:
6966 Before using S3QL, make sure to read the user&#39;s guide, especially
6967 the &#39;Important Rules to Avoid Loosing Data&#39; section.
6968 Enter encryption password:
6969 Confirm encryption password:
6970 Generating random encryption key...
6971 Creating metadata tables...
6972 Dumping metadata...
6973 ..objects..
6974 ..blocks..
6975 ..inodes..
6976 ..inode_blocks..
6977 ..symlink_targets..
6978 ..names..
6979 ..contents..
6980 ..ext_attributes..
6981 Compressing and uploading metadata...
6982 Wrote 0.00 MB of compressed metadata.
6983 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6984
6985 &lt;p&gt;The next step is mounting the file system to make the storage available.
6986
6987 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6988 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6989 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
6990 Using 4 upload threads.
6991 Downloading and decompressing metadata...
6992 Reading metadata...
6993 ..objects..
6994 ..blocks..
6995 ..inodes..
6996 ..inode_blocks..
6997 ..symlink_targets..
6998 ..names..
6999 ..contents..
7000 ..ext_attributes..
7001 Mounting filesystem...
7002 # df -h /s3ql
7003 Filesystem Size Used Avail Use% Mounted on
7004 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
7005 #
7006 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7007
7008 &lt;p&gt;The file system is now ready for use. I use rsync to store my
7009 backups in it, and as the metadata used by rsync is downloaded at
7010 mount time, no network traffic (and storage cost) is triggered by
7011 running rsync. To unmount, one should not use the normal umount
7012 command, as this will not flush the cache to the cloud storage, but
7013 instead running the umount.s3ql command like this:
7014
7015 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7016 # umount.s3ql /s3ql
7017 #
7018 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7019
7020 &lt;p&gt;There is a fsck command available to check the file system and
7021 correct any problems detected. This can be used if the local server
7022 crashes while the file system is mounted, to reset the &quot;already
7023 mounted&quot; flag. This is what it look like when processing a working
7024 file system:&lt;/p&gt;
7025
7026 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7027 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
7028 Using cached metadata.
7029 File system seems clean, checking anyway.
7030 Checking DB integrity...
7031 Creating temporary extra indices...
7032 Checking lost+found...
7033 Checking cached objects...
7034 Checking names (refcounts)...
7035 Checking contents (names)...
7036 Checking contents (inodes)...
7037 Checking contents (parent inodes)...
7038 Checking objects (reference counts)...
7039 Checking objects (backend)...
7040 ..processed 5000 objects so far..
7041 ..processed 10000 objects so far..
7042 ..processed 15000 objects so far..
7043 Checking objects (sizes)...
7044 Checking blocks (referenced objects)...
7045 Checking blocks (refcounts)...
7046 Checking inode-block mapping (blocks)...
7047 Checking inode-block mapping (inodes)...
7048 Checking inodes (refcounts)...
7049 Checking inodes (sizes)...
7050 Checking extended attributes (names)...
7051 Checking extended attributes (inodes)...
7052 Checking symlinks (inodes)...
7053 Checking directory reachability...
7054 Checking unix conventions...
7055 Checking referential integrity...
7056 Dropping temporary indices...
7057 Backing up old metadata...
7058 Dumping metadata...
7059 ..objects..
7060 ..blocks..
7061 ..inodes..
7062 ..inode_blocks..
7063 ..symlink_targets..
7064 ..names..
7065 ..contents..
7066 ..ext_attributes..
7067 Compressing and uploading metadata...
7068 Wrote 0.89 MB of compressed metadata.
7069 #
7070 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7071
7072 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
7073 quick, about the same speed as local file access. Uploading large
7074 amount of data is to me limited by the bandwidth out of and into my
7075 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
7076 which is very close to my upload speed, and downloading the same
7077 Debian installation ISO gave me 610 kiB/s, close to my download speed.
7078 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
7079 network, not the file system code. I do not know what a good cache
7080 size would be, but suspect that the cache should e larger than your
7081 working set.&lt;/p&gt;
7082
7083 &lt;p&gt;I mentioned that only one machine can mount the file system at the
7084 time. If another machine try, it is told that the file system is
7085 busy:&lt;/p&gt;
7086
7087 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7088 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
7089 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
7090 Using 8 upload threads.
7091 Backend reports that fs is still mounted elsewhere, aborting.
7092 #
7093 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7094
7095 &lt;p&gt;The file content is uploaded when the cache is full, while the
7096 metadata is uploaded once every 24 hour by default. To ensure the
7097 file system content is flushed to the cloud, one can either umount the
7098 file system, or ask S3QL to flush the cache and metadata using
7099 s3qlctrl:
7100
7101 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7102 # s3qlctrl upload-meta /s3ql
7103 # s3qlctrl flushcache /s3ql
7104 #
7105 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7106
7107 &lt;p&gt;If you are curious about how much space your data uses in the
7108 cloud, and how much compression and deduplication cut down on the
7109 storage usage, you can use s3qlstat on the mounted file system to get
7110 a report:&lt;/p&gt;
7111
7112 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7113 # s3qlstat /s3ql
7114 Directory entries: 9141
7115 Inodes: 9143
7116 Data blocks: 8851
7117 Total data size: 22049.38 MB
7118 After de-duplication: 21955.46 MB (99.57% of total)
7119 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
7120 Database size: 2.39 MB (uncompressed)
7121 (some values do not take into account not-yet-uploaded dirty blocks in cache)
7122 #
7123 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7124
7125 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
7126 storage. I did not try to locate them all, but am aware of at least
7127 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
7128 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
7129 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
7130 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
7131 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
7132 accept payment in Bitcoin. Pick one that suit your need. Some of
7133 them provide several GiB of free storage, but the prize models are
7134 quite different and you will have to figure out what suits you
7135 best.&lt;/p&gt;
7136
7137 &lt;p&gt;While researching this blog post, I had a look at research papers
7138 and posters discussing the S3QL file system. There are several, which
7139 told me that the file system is getting a critical check by the
7140 science community and increased my confidence in using it. One nice
7141 poster is titled
7142 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
7143 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
7144 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
7145 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
7146 and Pamela Smith. Please have a look.&lt;/p&gt;
7147
7148 &lt;p&gt;Given my problems with different file systems earlier, I decided to
7149 check out the mounted S3QL file system to see if it would be usable as
7150 a home directory (in other word, that it provided POSIX semantics when
7151 it come to locking and umask handling etc). Running
7152 &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
7153 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
7154 no error was found. So the file system can be used for home
7155 directories, if one chooses to do so.&lt;/p&gt;
7156
7157 &lt;p&gt;If you do not want a locally file system, and want something that
7158 work without the Linux fuse file system, I would like to mention the
7159 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
7160 provide locally encrypted backup using a command line client. It have
7161 a nicer access control system, where one can split out read and write
7162 access, allowing some systems to write to the backup and others to
7163 only read from it.&lt;/p&gt;
7164
7165 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
7166 activities, please send Bitcoin donations to my address
7167 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7168 </description>
7169 </item>
7170
7171 <item>
7172 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
7173 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
7174 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
7175 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
7176 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
7177 project&lt;/a&gt; is working on providing the software and hardware for
7178 making it easy for non-technical people to host their data and
7179 communication at home, and being able to communicate with their
7180 friends and family encrypted and away from prying eyes. It has been
7181 going on for a while, and is slowly progressing towards a new test
7182 release (0.2).&lt;/p&gt;
7183
7184 &lt;p&gt;And what day could be better than the Pi day to announce that the
7185 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
7186 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
7187 system), and can also be installed using a Debian installer preseed
7188 file. The Debian based Freedombox is now based on Debian Jessie,
7189 where most of the needed packages used are already present. Only one,
7190 the freedombox-setup package, is missing. To try to build your own
7191 boot image to test the current status, fetch the freedom-maker scripts
7192 and build using
7193 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
7194 with a user with sudo access to become root:
7195
7196 &lt;pre&gt;
7197 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
7198 freedom-maker
7199 sudo apt-get install git vmdebootstrap mercurial python-docutils \
7200 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
7201 u-boot-tools
7202 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
7203 &lt;/pre&gt;
7204
7205 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
7206 devices. See the README for more details on the build. If you do not
7207 want all three images, trim the make line. But note that thanks to &lt;a
7208 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
7209 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
7210 kpartx call.&lt;/p&gt;
7211
7212 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
7213 method, boot a Debian Wheezy ISO and use this boot argument to load
7214 the preseed values:&lt;/p&gt;
7215
7216 &lt;pre&gt;
7217 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;
7218 &lt;/pre&gt;
7219
7220 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
7221 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
7222 currently hang while setting up APT sources. Killing the
7223 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
7224 installation will get the installation going. This affect all
7225 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
7226
7227 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
7228 us get the new release published. :) Please join us on
7229 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
7230 irc.debian.org)&lt;/a&gt; and
7231 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
7232 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
7233 </description>
7234 </item>
7235
7236 <item>
7237 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
7238 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
7239 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
7240 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
7241 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
7242 innetgr tools, because I needed them in
7243 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
7244 ng-utils, and it has served me well. I placed the project under the
7245 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
7246 repository. But many years ago, the CVS repository was dropped (lost,
7247 not migrated to new hardware, not sure), and the project have lacked a
7248 proper home since then.&lt;/p&gt;
7249
7250 &lt;p&gt;Last summer, I had a look at the package and made a new release
7251 fixing a irritating crash bug, but was unable to store the changes in
7252 a proper source control system. I applied for a project on
7253 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
7254 to follow up on it. Until today. :)&lt;/p&gt;
7255
7256 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
7257 now have a new home, and a git repository with the highlight of the
7258 history of the project. I published all release tarballs and imported
7259 them into the git repository. As the project is really stable and not
7260 expected to gain new features any time soon, I decided to make a new
7261 release and call it 1.0. Visit the new project home on
7262 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
7263 if you want to check it out. The new version is also uploaded into
7264 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
7265 </description>
7266 </item>
7267
7268 <item>
7269 <title>Testing sysvinit from experimental in Debian Hurd</title>
7270 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
7271 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
7272 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
7273 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
7274 their changes into sysvinit, to allow them to use the normal sysvinit
7275 boot system instead of their old one. This follow up on the
7276 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
7277 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
7278 get Debian on Hurd working more like Debian on Linux. To get started,
7279 I downloaded a prebuilt hard disk image from
7280 &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;,
7281 and started it using virt-manager.&lt;/p&gt;
7282
7283 &lt;p&gt;The first think I had to do after logging in (root without any
7284 password) was to get the network operational. I followed
7285 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
7286 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
7287 commands as root to get the machine to accept a IP address from the
7288 kvm internal DHCP server:&lt;/p&gt;
7289
7290 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7291 settrans -fgap /dev/netdde /hurd/netdde
7292 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
7293 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
7294 dhclient /dev/eth0
7295 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7296
7297 &lt;p&gt;After this, the machine had internet connectivity, and I could
7298 upgrade it and install the sysvinit packages from experimental and
7299 enable it as the default boot system in Hurd.&lt;/p&gt;
7300
7301 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
7302 running on the machine it for ssh login to work a password need to be
7303 set. Also, note that a bug somewhere in openssh on Hurd block
7304 compression from working. Remember to turn that off on the client
7305 side.&lt;/p&gt;
7306
7307 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
7308 stuff:&lt;/p&gt;
7309
7310 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7311 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
7312 deb http://http.debian.net/debian/ experimental main
7313 EOF
7314 apt-get update
7315 apt-get dist-upgrade
7316 apt-get install -t experimental initscripts sysv-rc sysvinit \
7317 sysvinit-core sysvinit-utils
7318 update-alternatives --config runsystem
7319 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7320
7321 &lt;p&gt;To reboot after switching boot system, you have to use
7322 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
7323 yet a sysvinit process able to receive the signals from the normal
7324 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
7325 upgrading every package and rebooting, the network come up with DHCP
7326 after boot as it should, and the settrans/pkill hack mentioned at the
7327 start is no longer needed. But for some strange reason, there are no
7328 longer any login prompt in the virtual console, so I logged in using
7329 ssh instead.
7330
7331 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
7332 fail some times. No idea what the cause is, but hope the Hurd porters
7333 figure it out. At least Justus said on IRC (#debian-hurd on
7334 irc.debian.org) that they are aware of the problem. A way to reduce
7335 the impact is to upgrade to the Hurd packages built by Justus by
7336 adding this repository to the machine:&lt;/p&gt;
7337
7338 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7339 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
7340 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
7341 EOF
7342 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7343
7344 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
7345 http://ftp.debian-ports.org/debian, because some of the packages in
7346 unstable do not yet include the required patches that are lingering in
7347 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
7348
7349 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
7350 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
7351 i emacs - GNU Emacs editor (metapackage)
7352 i gdb - GNU Debugger
7353 i hurd-recommended - Miscellaneous translators
7354 i isc-dhcp-client - ISC DHCP client
7355 i isc-dhcp-common - common files used by all the isc-dhcp* packages
7356 i libc-bin - Embedded GNU C Library: Binaries
7357 i libc-dev-bin - Embedded GNU C Library: Development binaries
7358 i libc0.3 - Embedded GNU C Library: Shared libraries
7359 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
7360 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
7361 i multiarch-support - Transitional package to ensure multiarch compatibilit
7362 i A x11-common - X Window System (X.Org) infrastructure
7363 i xorg - X.Org X Window System
7364 i A xserver-xorg - X.Org X server
7365 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
7366 #
7367 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
7368
7369 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
7370 X.org did not work out of the box and I never took the time to follow
7371 the porters instructions to fix it. This time I was interested in the
7372 command line stuff.&lt;p&gt;
7373 </description>
7374 </item>
7375
7376 <item>
7377 <title>New chrpath release 0.16</title>
7378 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
7379 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
7380 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
7381 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
7382 find problems in C, C++ and Java code using static source code
7383 analysis. It can detect a lot of different problems, and is very
7384 useful to find memory and locking bugs in the error handling part of
7385 the source. The company behind it provide
7386 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
7387 a community service&lt;/a&gt;, and many hundred free software projects are
7388 already checked. A few days ago I decided to have a closer look at
7389 the Coverity system, and discovered that the
7390 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
7391 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
7392 projects I am involved with was already registered. But these are
7393 fairly big, and I would also like to have a small and easy project to
7394 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
7395 checking of the chrpath project&lt;/a&gt;. It was
7396 added to the checker and discovered seven potential defects. Six of
7397 these were real, mostly resource &quot;leak&quot; when the program detected an
7398 error. Nothing serious, as the resources would be released a fraction
7399 of a second later when the program exited because of the error, but it
7400 is nice to do it right in case the source of the program some time in
7401 the future end up in a library. Having fixed all defects and added
7402 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
7403 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
7404 publish a new release. These are the release notes:&lt;/p&gt;
7405
7406 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
7407
7408 &lt;ul&gt;
7409
7410 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
7411 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
7412 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
7413
7414 &lt;/ul&gt;
7415
7416 &lt;p&gt;You can
7417 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
7418 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
7419 project if something is wrong with the new release. The test suite
7420 did not discover any old errors, so if you find a new one, please also
7421 include a test suite check.&lt;/p&gt;
7422 </description>
7423 </item>
7424
7425 <item>
7426 <title>New chrpath release 0.15</title>
7427 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
7428 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
7429 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
7430 <description>&lt;p&gt;After many years break from the package and a vain hope that
7431 development would be continued by someone else, I finally pulled my
7432 acts together this morning and wrapped up a new release of chrpath,
7433 the command line tool to modify the rpath and runpath of already
7434 compiled ELF programs. The update was triggered by the persistence of
7435 Isha Vishnoi at IBM, which needed a new config.guess file to get
7436 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
7437 is working on. I checked the
7438 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
7439 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
7440 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
7441 packages for interesting patches (failed to find the source from
7442 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
7443 These are the release notes:&lt;/p&gt;
7444
7445 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
7446
7447 &lt;ul&gt;
7448
7449 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
7450 with newer architectures. Thanks to isha vishnoi for the heads
7451 up.&lt;/li&gt;
7452
7453 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
7454
7455 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
7456 Matthias Klose.&lt;/li&gt;
7457
7458 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
7459 Petr Machata found in Fedora.&lt;/li&gt;
7460
7461 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
7462 .dynamic is a NULL terminated string. Based on patch found in
7463 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
7464
7465 &lt;/ul&gt;
7466
7467 &lt;p&gt;You can
7468 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
7469 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
7470 project if something is wrong with the new release. The test suite
7471 did not discover any old errors, so if you find a new one, please also
7472 include a testsuite check.&lt;/p&gt;
7473 </description>
7474 </item>
7475
7476 <item>
7477 <title>Debian init.d boot script example for rsyslog</title>
7478 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
7479 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
7480 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
7481 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
7482 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
7483 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
7484 init.d scripts at all. Here is an example init.d script, ie a rewrite
7485 of /etc/init.d/rsyslog:&lt;/p&gt;
7486
7487 &lt;p&gt;&lt;pre&gt;
7488 #!/lib/init/init-d-script
7489 ### BEGIN INIT INFO
7490 # Provides: rsyslog
7491 # Required-Start: $remote_fs $time
7492 # Required-Stop: umountnfs $time
7493 # X-Stop-After: sendsigs
7494 # Default-Start: 2 3 4 5
7495 # Default-Stop: 0 1 6
7496 # Short-Description: enhanced syslogd
7497 # Description: Rsyslog is an enhanced multi-threaded syslogd.
7498 # It is quite compatible to stock sysklogd and can be
7499 # used as a drop-in replacement.
7500 ### END INIT INFO
7501 DESC=&quot;enhanced syslogd&quot;
7502 DAEMON=/usr/sbin/rsyslogd
7503 &lt;/pre&gt;&lt;/p&gt;
7504
7505 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
7506 script was 137 lines, and the above is just 15 lines, most of it meta
7507 info/comments.&lt;/p&gt;
7508
7509 &lt;p&gt;How to do this, you ask? Well, one create a new script
7510 /lib/init/init-d-script looking something like this:
7511
7512 &lt;p&gt;&lt;pre&gt;
7513 #!/bin/sh
7514
7515 # Define LSB log_* functions.
7516 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
7517 # and status_of_proc is working.
7518 . /lib/lsb/init-functions
7519
7520 #
7521 # Function that starts the daemon/service
7522
7523 #
7524 do_start()
7525 {
7526 # Return
7527 # 0 if daemon has been started
7528 # 1 if daemon was already running
7529 # 2 if daemon could not be started
7530 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
7531 || return 1
7532 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
7533 $DAEMON_ARGS \
7534 || return 2
7535 # Add code here, if necessary, that waits for the process to be ready
7536 # to handle requests from services started subsequently which depend
7537 # on this one. As a last resort, sleep for some time.
7538 }
7539
7540 #
7541 # Function that stops the daemon/service
7542 #
7543 do_stop()
7544 {
7545 # Return
7546 # 0 if daemon has been stopped
7547 # 1 if daemon was already stopped
7548 # 2 if daemon could not be stopped
7549 # other if a failure occurred
7550 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
7551 RETVAL=&quot;$?&quot;
7552 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
7553 # Wait for children to finish too if this is a daemon that forks
7554 # and if the daemon is only ever run from this initscript.
7555 # If the above conditions are not satisfied then add some other code
7556 # that waits for the process to drop all resources that could be
7557 # needed by services started subsequently. A last resort is to
7558 # sleep for some time.
7559 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
7560 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
7561 # Many daemons don&#39;t delete their pidfiles when they exit.
7562 rm -f $PIDFILE
7563 return &quot;$RETVAL&quot;
7564 }
7565
7566 #
7567 # Function that sends a SIGHUP to the daemon/service
7568 #
7569 do_reload() {
7570 #
7571 # If the daemon can reload its configuration without
7572 # restarting (for example, when it is sent a SIGHUP),
7573 # then implement that here.
7574 #
7575 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
7576 return 0
7577 }
7578
7579 SCRIPTNAME=$1
7580 scriptbasename=&quot;$(basename $1)&quot;
7581 echo &quot;SN: $scriptbasename&quot;
7582 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
7583 script=&quot;$1&quot;
7584 shift
7585 . $script
7586 else
7587 exit 0
7588 fi
7589
7590 NAME=$(basename $DAEMON)
7591 PIDFILE=/var/run/$NAME.pid
7592
7593 # Exit if the package is not installed
7594 #[ -x &quot;$DAEMON&quot; ] || exit 0
7595
7596 # Read configuration variable file if it is present
7597 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
7598
7599 # Load the VERBOSE setting and other rcS variables
7600 . /lib/init/vars.sh
7601
7602 case &quot;$1&quot; in
7603 start)
7604 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
7605 do_start
7606 case &quot;$?&quot; in
7607 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
7608 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
7609 esac
7610 ;;
7611 stop)
7612 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
7613 do_stop
7614 case &quot;$?&quot; in
7615 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
7616 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
7617 esac
7618 ;;
7619 status)
7620 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
7621 ;;
7622 #reload|force-reload)
7623 #
7624 # If do_reload() is not implemented then leave this commented out
7625 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
7626 #
7627 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
7628 #do_reload
7629 #log_end_msg $?
7630 #;;
7631 restart|force-reload)
7632 #
7633 # If the &quot;reload&quot; option is implemented then remove the
7634 # &#39;force-reload&#39; alias
7635 #
7636 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
7637 do_stop
7638 case &quot;$?&quot; in
7639 0|1)
7640 do_start
7641 case &quot;$?&quot; in
7642 0) log_end_msg 0 ;;
7643 1) log_end_msg 1 ;; # Old process is still running
7644 *) log_end_msg 1 ;; # Failed to start
7645 esac
7646 ;;
7647 *)
7648 # Failed to stop
7649 log_end_msg 1
7650 ;;
7651 esac
7652 ;;
7653 *)
7654 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
7655 exit 3
7656 ;;
7657 esac
7658
7659 :
7660 &lt;/pre&gt;&lt;/p&gt;
7661
7662 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
7663 lot. I did not really polish the approach, so it might not always
7664 work out of the box, but you get the idea. I did not try very hard to
7665 optimize it nor make it more robust either.&lt;/p&gt;
7666
7667 &lt;p&gt;A better argument for switching init system in Debian than reducing
7668 the size of init scripts (which is a good thing to do anyway), is to
7669 get boot system that is able to handle the kernel events sensibly and
7670 robustly, and do not depend on the boot to run sequentially. The boot
7671 and the kernel have not behaved sequentially in years.&lt;/p&gt;
7672 </description>
7673 </item>
7674
7675 <item>
7676 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
7677 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
7678 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
7679 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
7680 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
7681 remote display access is the preferred solution with oVirt and RedHat
7682 Enterprise Virtualization, and I was sad to discover the other day
7683 that the browser plugin needed to use these systems seamlessly was
7684 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
7685 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
7686 2013-04-01, so I decided to wrap up a package based on the great work
7687 from Cajus Pollmeier and put it in a collab-maint maintained git
7688 repository to get a package I could use. I would very much like
7689 others to help me maintain the package (or just take over, I do not
7690 mind), but as no-one had volunteered so far, I just uploaded it to
7691 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
7692
7693 &lt;p&gt;The source is now available from
7694 &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;
7695 </description>
7696 </item>
7697
7698 <item>
7699 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
7700 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
7701 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
7702 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
7703 <description>&lt;p&gt;The
7704 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
7705 program is a a very nice system to create virtual machine images. It
7706 create a image file, add a partition table, mount it and run
7707 debootstrap in the mounted directory to create a Debian system on a
7708 stick. Yesterday, I decided to try to teach it how to make images for
7709 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
7710 of a plan to simplify the build system for
7711 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
7712 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
7713 the virtualbox images, but its current build system made multistrap
7714 based system for Dreamplug images, and it is lacking support for
7715 Raspberry Pi.&lt;/p&gt;
7716
7717 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
7718 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
7719 code and adjusted it to be able to build armel images on my amd64
7720 Debian laptop. I ended up giving vmdebootstrap five new options,
7721 allowing me to replicate the image creation process I use to make
7722 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
7723 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
7724 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
7725 call debootstrap with --foreign and to copy the handler into the
7726 generated chroot before running the second stage. This allow
7727 vmdebootstrap to create armel images on an amd64 host. Next I added
7728 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
7729 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
7730 given file system type, allowing me to create an image with a vfat
7731 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
7732 variant&lt;/tt&gt; option to allow me to create smaller images without the
7733 Debian base system packages installed. Finally, I added an option
7734 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
7735 as a boot loader. It is not needed on the Raspberry Pi and probably
7736 most other non-x86 architectures. The changes were accepted by the
7737 upstream author of vmdebootstrap yesterday and today, and is now
7738 available from
7739 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
7740 upstream project page&lt;/a&gt;.&lt;/p&gt;
7741
7742 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
7743 create a small script (the customize script) to add the non-free
7744 binary blob needed to boot the Raspberry Pi and the APT source
7745 list:&lt;/p&gt;
7746
7747 &lt;p&gt;&lt;pre&gt;
7748 #!/bin/sh
7749 set -e # Exit on first error
7750 rootdir=&quot;$1&quot;
7751 cd &quot;$rootdir&quot;
7752 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
7753 deb http://http.debian.net/debian/ jessie main contrib non-free
7754 EOF
7755 # Install non-free binary blob needed to boot Raspberry Pi. This
7756 # install a kernel somewhere too.
7757 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
7758 -O $rootdir/usr/bin/rpi-update
7759 chmod a+x $rootdir/usr/bin/rpi-update
7760 mkdir -p $rootdir/lib/modules
7761 touch $rootdir/boot/start.elf
7762 chroot $rootdir rpi-update
7763 &lt;/pre&gt;&lt;/p&gt;
7764
7765 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
7766 to build the image:&lt;/p&gt;
7767
7768 &lt;pre&gt;
7769 sudo ./vmdebootstrap \
7770 --variant minbase \
7771 --arch armel \
7772 --distribution jessie \
7773 --mirror http://http.debian.net/debian \
7774 --image test.img \
7775 --size 600M \
7776 --bootsize 64M \
7777 --boottype vfat \
7778 --log-level debug \
7779 --verbose \
7780 --no-kernel \
7781 --no-extlinux \
7782 --root-password raspberry \
7783 --hostname raspberrypi \
7784 --foreign /usr/bin/qemu-arm-static \
7785 --customize `pwd`/customize \
7786 --package netbase \
7787 --package git-core \
7788 --package binutils \
7789 --package ca-certificates \
7790 --package wget \
7791 --package kmod
7792 &lt;/pre&gt;&lt;/p&gt;
7793
7794 &lt;p&gt;The list of packages being installed are the ones needed by
7795 rpi-update to make the image bootable on the Raspberry Pi, with the
7796 exception of netbase, which is needed by debootstrap to find
7797 /etc/hosts with the minbase variant. I really wish there was a way to
7798 set up an Raspberry Pi using only packages in the Debian archive, but
7799 that is not possible as far as I know, because it boots from the GPU
7800 using a non-free binary blob.&lt;/p&gt;
7801
7802 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
7803 probably a few others installed. I have not checked the complete
7804 build dependency list.&lt;/p&gt;
7805
7806 &lt;p&gt;The resulting image will not use the hardware floating point unit
7807 on the Raspberry PI, because the armel architecture in Debian is not
7808 optimized for that use. So the images created will be a bit slower
7809 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
7810 </description>
7811 </item>
7812
7813 <item>
7814 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
7815 <link>https://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html</link>
7816 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html</guid>
7817 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
7818 <description>&lt;p&gt;The last few days I came across a few good causes that should get
7819 wider attention. I recommend signing and donating to each one of
7820 these. :)&lt;/p&gt;
7821
7822 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
7823 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
7824 Women program which is a Google Summer of Code like initiative to get
7825 more women involved in free software. One debian sponsor has offered
7826 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
7827 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
7828 hope you will to. :)&lt;/p&gt;
7829
7830 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
7831 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
7832 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
7833 take place these days, and their need to fund the work. I&#39;ve already
7834 donated. Are you next?&lt;/p&gt;
7835
7836 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
7837 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
7838 statement under the heading
7839 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
7840 Access&lt;/a&gt; for those of us asking for more focus on open access in the
7841 Norwegian government. So far 499 signatures. I hope you will sign it
7842 too.&lt;/p&gt;
7843 </description>
7844 </item>
7845
7846 <item>
7847 <title>Videos about the Freedombox project - for inspiration and learning</title>
7848 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
7849 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
7850 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
7851 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
7852 project&lt;/a&gt; have been going on for a while, and have presented the
7853 vision, ideas and solution several places. Here is a little
7854 collection of videos of talks and presentation of the project.&lt;/p&gt;
7855
7856 &lt;ul&gt;
7857
7858 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
7859 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
7860
7861 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
7862 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
7863
7864 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
7865 Freedom in the Cloud - Software Freedom, Privacy and and Security for
7866 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
7867 (Youtube)&lt;/li&gt;
7868
7869 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
7870 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
7871
7872 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
7873 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
7874
7875 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
7876 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
7877 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
7878
7879 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
7880 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
7881 (Youtube)&lt;/li&gt;
7882
7883 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
7884 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
7885
7886 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
7887 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
7888
7889 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
7890 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
7891 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
7892
7893 &lt;/ul&gt;
7894
7895 &lt;p&gt;A larger list is available from
7896 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
7897 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
7898
7899 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
7900 Jessie is coming along quite well, and soon both Owncloud and using
7901 Tor should be available for testers of the Freedombox solution. :) In
7902 a few weeks I hope everything needed to test it is included in Debian.
7903 The withsqlite package is already in Debian, and the plinth package is
7904 pending in NEW. The third and vital part of that puzzle is the
7905 metapackage/setup framework, which is still pending an upload. Join
7906 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
7907 (#freedombox on irc.debian.org)&lt;/a&gt; and
7908 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
7909 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
7910 </description>
7911 </item>
7912
7913 <item>
7914 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
7915 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
7916 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
7917 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
7918 <description>&lt;p&gt;I was introduced to the
7919 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
7920 in 2010, when Eben Moglen presented his vision about serving the need
7921 of non-technical people to keep their personal information private and
7922 within the legal protection of their own homes. The idea is to give
7923 people back the power over their network and machines, and return
7924 Internet back to its intended peer-to-peer architecture. Instead of
7925 depending on a central service, the Freedombox will give everyone
7926 control over their own basic infrastructure.&lt;/p&gt;
7927
7928 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
7929 taken priority. But this summers nasty news about the misuse of trust
7930 and privilege exercised by the &quot;western&quot; intelligence gathering
7931 communities increased my eagerness to contribute to a point where I
7932 actually started working on the project a while back.&lt;/p&gt;
7933
7934 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
7935 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
7936 create a simple and cheap Debian based appliance that anyone can hook
7937 up in their home and get access to secure and private services and
7938 communication. The initial deployment platform have been the
7939 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
7940 which is a piece of hardware I do not own. So to be able to test what
7941 the current Freedombox setup look like, I had to come up with a way to install
7942 it on some hardware I do have access to. I have rewritten the
7943 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
7944 image build framework to use .deb packages instead of only copying
7945 setup into the boot images, and thanks to this rewrite I am able to
7946 set up any machine supported by Debian Wheezy as a Freedombox, using
7947 the previously mentioned deb (and a few support debs for packages
7948 missing in Debian).&lt;/p&gt;
7949
7950 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
7951 scripts
7952 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
7953 and a administrative web interface
7954 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
7955 withsqlite), as well as a privacy enhancing proxy based on
7956 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
7957 (freedombox-privoxy). There is also a web/javascript based XMPP
7958 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
7959 trying (unsuccessfully so far) to talk to the XMPP server
7960 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
7961 web interface is pluggable, and the goal is to use it to enable OpenID
7962 services, mesh network connectivity, use of TOR, etc, etc. Not much of
7963 this is really working yet, see
7964 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
7965 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
7966 on github at the moment. The HTTP proxy is operational out of the
7967 box, and the admin web interface can be used to add/remove plinth
7968 users. I&#39;ve not been able to do anything else with it so far, but
7969 know there are several branches spread around github and other places
7970 with lots of half baked features.&lt;/p&gt;
7971
7972 &lt;p&gt;Anyway, if you want to have a look at the current state, the
7973 following recipes should work to give you a test machine to poke
7974 at.&lt;/p&gt;
7975
7976 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
7977
7978 &lt;ol&gt;
7979
7980 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
7981 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
7982 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
7983 to the Debian installer:&lt;p&gt;
7984 &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;
7985
7986 &lt;li&gt;Answer the few language/region/password questions and pick disk to
7987 install on.&lt;/li&gt;
7988
7989 &lt;li&gt;When the installation is finished and the machine have rebooted a
7990 few times, your Freedombox is ready for testing.&lt;/li&gt;
7991
7992 &lt;/ol&gt;
7993
7994 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
7995
7996 &lt;ol&gt;
7997
7998 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
7999 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
8000 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
8001 &lt;pre&gt;
8002 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
8003 &lt;/pre&gt;&lt;/li&gt;
8004 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
8005 &lt;pre&gt;
8006 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
8007 apt-key add -
8008 apt-get update
8009 apt-get install freedombox-setup
8010 /usr/lib/freedombox/setup
8011 &lt;/pre&gt;&lt;/li&gt;
8012 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
8013
8014 &lt;/ol&gt;
8015
8016 &lt;p&gt;You can test it on other architectures too, but because the
8017 freedombox-privoxy package is binary, it will only work as intended on
8018 the architectures where I have had time to build the binary and put it
8019 in my APT repository. But do not let this stop you. It is only a
8020 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
8021
8022 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
8023 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
8024 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
8025 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
8026
8027 &lt;p&gt;Please let me know if this works for you, or if you have any
8028 problems. We gather on the IRC channel
8029 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
8030 irc.debian.org and the
8031 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
8032 mailing list&lt;/a&gt;.&lt;/p&gt;
8033
8034 &lt;p&gt;Once you get your freedombox operational, you can visit
8035 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
8036 welcome screen (dead end - do not be surprised if you are unable to
8037 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
8038 to look at the rest of plinth. The default user is &#39;admin&#39; and the
8039 default password is &#39;secret&#39;.&lt;/p&gt;
8040 </description>
8041 </item>
8042
8043 <item>
8044 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
8045 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
8046 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
8047 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
8048 <description>&lt;p&gt;Earlier, I reported about
8049 &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
8050 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
8051 told by IBM that the original disk should be thrown away. And as
8052 there no longer was a problem if I bricked the firmware, I decided
8053 today to try to install Intel firmware to replace the Lenovo firmware
8054 currently on the disk.&lt;/p&gt;
8055
8056 &lt;p&gt;I searched the Intel site for firmware, and found
8057 &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;
8058 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
8059 according to the site should contain the latest firmware for SSD
8060 disks. I inserted the broken disk in one of my spare laptops and
8061 booted the ISO from a USB stick. The disk was recognized, but the
8062 program claimed the newest firmware already were installed and refused
8063 to insert any Intel firmware. So no change, and the disk is still
8064 unable to handle write load. :( I guess the only way to get them
8065 working would be if Lenovo releases new firmware. No idea how likely
8066 that is. Anyway, just blogging about this test for completeness. I
8067 got a working Samsung disk, and see no point in spending more time on
8068 the broken disks.&lt;/p&gt;
8069 </description>
8070 </item>
8071
8072 <item>
8073 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
8074 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
8075 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
8076 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
8077 <description>&lt;p&gt;Today I switched to
8078 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
8079 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
8080 my new Thinkpad X230, which was delivered with an
8081 &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
8082 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
8083 sustained writes. My hardware supplier have been very forthcoming in
8084 trying to find a solution, and after first trying with another
8085 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
8086 disk instead to fix it once and for all. The Samsung disk survived
8087 the installation of Debian with encrypted disks (filling the disk with
8088 random data during installation killed the first two), and I thus
8089 decided to trust it with my data. I have installed it as a Debian Edu
8090 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
8091 server at home using Kerberos and LDAP, and will use it as my work
8092 station from now on.&lt;/p&gt;
8093
8094 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
8095 Debian Wheezy default installation need to be tuned a bit to increase
8096 performance and increase life time of the disk. The Linux kernel and
8097 user space applications do not yet adjust automatically to such
8098 environment. To make it easier for my self, I created a draft Debian
8099 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
8100 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
8101 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
8102 is set up to adjust the setup of the machine by just installing the
8103 package. If there is any non-SSD disk in the machine, the package
8104 will refuse to install, as I did not try to write any logic to sort
8105 file systems in SSD and non-SSD file systems.&lt;/p&gt;
8106
8107 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
8108 set up Debian Wheezy with an SSD. It is adjusted to my use case,
8109 where I set up the machine with one large encrypted partition (in
8110 addition to /boot), put LVM on top of this and set up partitions on
8111 top of this again. See the README file in the package source for the
8112 references I used to pick the settings. At the moment these
8113 parameters are tuned:&lt;/p&gt;
8114
8115 &lt;ul&gt;
8116
8117 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
8118 (adding discard to /etc/crypttab)&lt;/li&gt;
8119
8120 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
8121 this case a cryptsetup partition) by changing issue_discards from
8122 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
8123
8124 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
8125 systems.&lt;/li&gt;
8126
8127 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
8128 /etc/fstab.&lt;/li&gt;
8129
8130 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
8131
8132 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
8133 cron.daily).&lt;/li&gt;
8134
8135 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
8136 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
8137
8138 &lt;/ul&gt;
8139
8140 &lt;p&gt;During installation, I cancelled the part where the installer fill
8141 the disk with random data, as this would kill the SSD performance for
8142 little gain. My goal with the encrypted file system is to ensure
8143 those stealing my laptop end up with a brick and not a working
8144 computer. I have no hope in keeping the really resourceful people
8145 from getting the data on the disk (see
8146 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
8147 Thus I concluded that adding the discard option to crypttab is the
8148 right thing to do.&lt;/p&gt;
8149
8150 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
8151 it for SSD, but others recommended deadline and a benchmark I found
8152 indicated that deadline might be better for interactive use.&lt;/p&gt;
8153
8154 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
8155 and ext4, but read that it would give a performance hit ever time a
8156 file is removed, and thought it best to that that slowdown once a day
8157 instead of during my work.&lt;/p&gt;
8158
8159 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
8160 this is already done by Debian Edu.&lt;/p&gt;
8161
8162 &lt;p&gt;I have not yet started on the user space tuning. I expect
8163 iceweasel need some tuning, and perhaps other applications too, but
8164 have not yet had time to investigate those parts.&lt;/p&gt;
8165
8166 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
8167 there.&lt;/p&gt;
8168
8169 &lt;p&gt;As for the answer to the question in the title of this blog post,
8170 as far as I know, the only solution I know about is to replace the
8171 disk. It might be possible to flash it with Intel firmware instead of
8172 the Lenovo firmware. But I have not tried and did not want to do so
8173 without approval from Lenovo as I wanted to keep the warranty on the
8174 disk until a solution was found and they wanted the broken disks
8175 back.&lt;/p&gt;
8176 </description>
8177 </item>
8178
8179 <item>
8180 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
8181 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
8182 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</guid>
8183 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
8184 <description>&lt;p&gt;A few days ago, I wrote about
8185 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
8186 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
8187 was dying during installation because it is unable to cope with
8188 sustained write. My supplier is in contact with
8189 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
8190 replacement disk to try to fix the problem. They decided to send an
8191 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
8192
8193 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
8194 Debian Edu Wheezy with encrypted disk on it. The new disk have the
8195 same firmware version as the original. This time my hope raised
8196 slightly as the installation progressed, as the original disk used to
8197 die after 4-7% of the disk was written to, while this time it kept
8198 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
8199 died again and I was back on square one. I still do not have a new
8200 laptop with a disk I can trust. I can not live with a disk that might
8201 lock up when I download a new
8202 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
8203 other large files. I look forward to hearing from my supplier with
8204 the next proposal from Lenovo.&lt;/p&gt;
8205
8206 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
8207 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
8208 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
8209 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
8210 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
8211 P/N 45N8295, P0C38732.&lt;/p&gt;
8212
8213 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
8214 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
8215 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
8216 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
8217 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
8218 P/N 45N8295, P0C38732.&lt;/p&gt;
8219
8220 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
8221 SA, date and WNPP values. Mentioning all the details here in case
8222 someone is able to use the information to find a way to identify the
8223 failing disk among working ones (if any such working disk actually
8224 exist).&lt;/p&gt;
8225 </description>
8226 </item>
8227
8228 <item>
8229 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
8230 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
8231 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
8232 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
8233 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
8234 Debian Edu developer gathering and Debian and Ubuntu bug squashing
8235 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
8236 member assosiation NUUG&lt;/a&gt; and
8237 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
8238 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
8239 Bitraf&lt;/a&gt;.&lt;/p&gt;
8240
8241 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
8242 welcome, and there is no fee to participate. There is on the other
8243 hand limited space, and only room for 30 people. Please put your name
8244 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
8245 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
8246 </description>
8247 </item>
8248
8249 <item>
8250 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
8251 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
8252 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
8253 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
8254 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
8255 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
8256 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
8257 time to spend on it, and it took a while to find a model I believe
8258 will do the job, but two days ago the replacement finally arrived. I
8259 ended up picking a
8260 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
8261 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
8262 a roaming workstation, and it seemed to work flawlessly. But my
8263 second installation with encrypted disk was not as successful. More
8264 on that below.&lt;/p&gt;
8265
8266 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
8267 important requirements (robust and with a good keyboard) are never
8268 listed in the feature list. But I did get good help from the search
8269 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
8270 allowed me to limit the list of interesting laptops based on my other
8271 requirements. A bit surprising that SSD disk are not disks according
8272 to that search interface, so I had to drop specifying the number of
8273 disks from my search parameters. I also asked around among friends to
8274 get their impression on keyboards and robustness.&lt;/p&gt;
8275
8276 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
8277 X41. I am not quite convinced about the keyboard, as it is
8278 significantly wider than my old keyboard, and I have to stretch my
8279 hand a lot more to reach the edges. But the key response is fairly
8280 good and the individual key shape is fairly easy to handle, so I hope
8281 I will get used to it. My old X40 was starting to fail, and I really
8282 needed a new laptop now. :)&lt;/p&gt;
8283
8284 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
8285 visit to the BIOS during boot it disable it.&lt;/p&gt;
8286
8287 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
8288 lock up during load. And this happen when installing Debian Wheezy
8289 with encrypted disk, while the disk is being filled with random data.
8290 I also tested to install Ubuntu Raring, and it happen there too if I
8291 reenable the code to fill the disk with random data (it is disabled by
8292 default in Ubuntu). And the bug with is already known. It was
8293 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
8294 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
8295 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
8296 kernel developers as
8297 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
8298 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
8299 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
8300 Lenovo forums, both for
8301 &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
8302 2012-11-10&lt;/a&gt; and for
8303 &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
8304 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
8305 reports state that the disk lock up during use if many writes are done
8306 on the disk, so it is much no use to work around the installation
8307 problem and end up with a computer that can lock up at any moment.
8308 There is even a
8309 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
8310 available&lt;/a&gt; that will lock up the hard drive after running a few
8311 minutes by writing to a file.&lt;/p&gt;
8312
8313 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
8314 contacting PCHELP Norway (request 01D1FDP) which handle support
8315 requests for Lenovo, his first suggestion was to upgrade the disk
8316 firmware. Unfortunately there is no newer firmware available from
8317 Lenovo, as my disk already have the most recent one (version LF1i). I
8318 hope to hear more from him today and hope the problem can be
8319 fixed. :)&lt;/p&gt;
8320 </description>
8321 </item>
8322
8323 <item>
8324 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
8325 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
8326 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
8327 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
8328 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
8329 trusty old Thinkpad X41. Unfortunately I did not have much time to
8330 spend on it, but today the replacement finally arrived. I ended up
8331 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
8332 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
8333 Wheezy as a roaming workstation, and it worked flawlessly. As I write
8334 this, it is installing what I hope will be a more final installation,
8335 with a encrypted hard drive to ensure any dope head stealing it end up
8336 with an expencive door stop.&lt;/p&gt;
8337
8338 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
8339 important requirements (robust and with a good keyboard) are never
8340 listed in the feature list. But I did get good help from the search
8341 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
8342 allowed me to limit the list of interesting laptops based on my other
8343 requirements. A bit surprising that SSD disk are not disks, so I had
8344 to drop number of disks from my search parameters.&lt;/p&gt;
8345
8346 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
8347 wider than my old keyboard, and I have to stretch my hand a lot more
8348 to reach the edges. But the key response is fairly good and the
8349 individual key shape is fairly easy to handle, so I hope I will get
8350 used to it. My old X40 was starting to fail, and I really needed a
8351 new laptop now. :)&lt;/p&gt;
8352
8353 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
8354 </description>
8355 </item>
8356
8357 <item>
8358 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
8359 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
8360 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
8361 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
8362 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
8363 perfectly capable of, and I have to do it manually to get things
8364 working. One such task is to find out what firmware packages are
8365 needed to get the hardware on my computer working. Most often this
8366 affect the wifi card, but some times it even affect the RAID
8367 controller or the ethernet card. Today I pushed version 0.4 of the
8368 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
8369 including a new script isenkram-autoinstall-firmware handling the
8370 process of asking all the loaded kernel modules what firmware files
8371 they want, find debian packages providing these files and install the
8372 debian packages. Here is a test run on my laptop:&lt;/p&gt;
8373
8374 &lt;p&gt;&lt;pre&gt;
8375 # isenkram-autoinstall-firmware
8376 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
8377 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
8378 info: locating packages with the requested firmware files
8379 info: Updating APT sources after adding non-free APT source
8380 info: trying to install firmware-ipw2x00
8381 firmware-ipw2x00
8382 firmware-ipw2x00
8383 Preconfiguring packages ...
8384 Selecting previously deselected package firmware-ipw2x00.
8385 (Reading database ... 259727 files and directories currently installed.)
8386 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
8387 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
8388 #
8389 &lt;/pre&gt;&lt;/p&gt;
8390
8391 &lt;p&gt;When all the requested firmware is present, a simple message is
8392 printed instead:&lt;/p&gt;
8393
8394 &lt;p&gt;&lt;pre&gt;
8395 # isenkram-autoinstall-firmware
8396 info: did not find any firmware files requested by loaded kernel modules. exiting
8397 #
8398 &lt;/pre&gt;&lt;/p&gt;
8399
8400 &lt;p&gt;It could use some polish, but it is already working well and saving
8401 me some time when setting up new machines. :)&lt;/p&gt;
8402
8403 &lt;p&gt;So, how does it work? It look at the set of currently loaded
8404 kernel modules, and look up each one of them using modinfo, to find
8405 the firmware files listed in the module meta-information. Next, it
8406 download the Contents file from a nearby APT mirror, and search for
8407 the firmware files in this file to locate the package with the
8408 requested firmware file. If the package is in the non-free section, a
8409 non-free APT source is added and the package is installed using
8410 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
8411 machine.&lt;/p&gt;
8412
8413 &lt;p&gt;I hope someone find time to implement a more polished version of
8414 this script as part of the hw-detect debian-installer module, to
8415 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
8416 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
8417 firmware during a PXE install when the packages already are available
8418 from the nearby Debian mirror.&lt;/p&gt;
8419 </description>
8420 </item>
8421
8422 <item>
8423 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
8424 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
8425 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
8426 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
8427 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
8428 the screen just turn black when Linux boot, either during installation
8429 or on first boot from the hard disk. I&#39;ve seen it once in a while the
8430 last few years, but only recently understood the cause. I&#39;ve seen it
8431 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
8432 The reason seem to be in the wiring of some laptops. The system to
8433 control the screen background light is inverted, so when Linux try to
8434 turn the brightness fully on, it end up turning it off instead. I do
8435 not know which Linux drivers are affected, but this post is about the
8436 i915 driver used by the
8437 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
8438 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
8439
8440 &lt;p&gt;The problem can be worked around two ways. Either by adding
8441 i915.invert_brightness=1 as a kernel option, or by adding a file in
8442 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
8443 option when it load the i915 kernel module. On Debian and Ubuntu, it
8444 can be done by running these commands as root:&lt;/p&gt;
8445
8446 &lt;pre&gt;
8447 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
8448 update-initramfs -u -k all
8449 &lt;/pre&gt;
8450
8451 &lt;p&gt;Since March 2012 there is
8452 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
8453 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
8454 hardware have this problem, and get the driver to invert the
8455 brightness setting automatically. To use it, one need to add a row in
8456 &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
8457 intel_quirks array&lt;/a&gt; in the driver source
8458 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
8459 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
8460 number (vendor number 8086 is assumed) and subdevice vendor and device
8461 number.&lt;/p&gt;
8462
8463 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
8464 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
8465
8466 &lt;p&gt;&lt;pre&gt;
8467 00:02.0 VGA compatible controller [0300]: Intel Corporation \
8468 3rd Gen Core processor Graphics Controller [8086:0156] \
8469 (rev 09) (prog-if 00 [VGA controller])
8470 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
8471 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
8472 ParErr- Stepping- SE RR- FastB2B- DisINTx+
8473 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
8474 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
8475 Latency: 0
8476 Interrupt: pin A routed to IRQ 42
8477 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
8478 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
8479 Region 4: I/O ports at 4000 [size=64]
8480 Expansion ROM at &lt;unassigned&gt; [disabled]
8481 Capabilities: &lt;access denied&gt;
8482 Kernel driver in use: i915
8483 &lt;/pre&gt;&lt;/p&gt;
8484
8485 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
8486
8487 &lt;p&gt;&lt;pre&gt;
8488 struct intel_quirk intel_quirks[] = {
8489 ...
8490 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
8491 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
8492 ...
8493 }
8494 &lt;/pre&gt;&lt;/p&gt;
8495
8496 &lt;p&gt;According to the kernel module instructions (as seen using
8497 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
8498 invert_brightness flag should be sent to the
8499 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
8500 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
8501 developers. But my email about the laptop sent 2013-06-03 have not
8502 yet shown up in
8503 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
8504 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
8505 emails from non-subscribers. Because of this, I sent my patch also to
8506 the Debian bug tracking system instead as
8507 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
8508 sure the patch is not lost.&lt;/p&gt;
8509
8510 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
8511 with this problem working properly with Linux. If you use Gnome, your
8512 worries should be over at this point. But if you use KDE, there is
8513 something in KDE ignoring the invert_brightness setting and turning on
8514 the screen during login. I&#39;ve reported it to Debian as
8515 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
8516 have no idea yet how to figure out exactly what subsystem is doing
8517 this. Perhaps you can help? Perhaps you know what the Gnome
8518 developers did to handle this, and this can give a clue to the KDE
8519 developers? Or you know where in KDE the screen brightness is changed
8520 during login? If so, please update the BTS report (or get in touch if
8521 you do not know how to update BTS).&lt;/p&gt;
8522
8523 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
8524 acpi_backlight=vendor, to disable ACPI backlight support completely,
8525 as the ACPI information on the machine is trash and it is better to
8526 leave it to the intel video driver to control the screen
8527 backlight.&lt;/p&gt;
8528 </description>
8529 </item>
8530
8531 <item>
8532 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
8533 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
8534 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</guid>
8535 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
8536 <description>&lt;p&gt;Two days ago, I asked
8537 &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
8538 I could install Linux on a Packard Bell EasyNote LV computer
8539 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
8540 with the obstacles put in the way of Linux users on a laptop with UEFI
8541 and Windows 8.&lt;/p&gt;
8542
8543 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
8544 secure booting or fast boot. I suspect fast boot was the problem,
8545 causing the firmware to boot directly from HD without considering any
8546 key presses and alternative devices, but do not know UEFI settings
8547 enough to tell.&lt;/p&gt;
8548
8549 &lt;p&gt;There is no way to install Linux on the machine in question without
8550 opening the box and disconnecting the hard drive! This is as far as I
8551 can tell, the only way to get access to the firmware setup menu
8552 without accepting the Windows 8 license agreement. I am told (and
8553 found description on how to) that it is possible to configure the
8554 firmware setup once booted into Windows 8. But as I believe the terms
8555 of that agreement are completely unacceptable, accepting the license
8556 was never an alternative. I do not enter agreements I do not intend
8557 to follow.&lt;/p&gt;
8558
8559 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
8560 waste many hours on this, but luckily there was a way to get it to
8561 work. But I would not recommend it to anyone planning to run Linux on
8562 it, and I have become sceptical to Windows 8 certified laptops. Is
8563 this the way Linux will be forced out of the market place, by making
8564 it close to impossible for &quot;normal&quot; users to install Linux without
8565 accepting the Microsoft Windows license terms? Or at least not
8566 without risking to loose the warranty?&lt;/p&gt;
8567
8568 &lt;p&gt;I&#39;ve updated the
8569 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
8570 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
8571 do not have to struggle as much as I did to get Linux into the
8572 machine.&lt;/p&gt;
8573
8574 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
8575 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
8576 </description>
8577 </item>
8578
8579 <item>
8580 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
8581 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
8582 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</guid>
8583 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
8584 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
8585 new laptops for my parents and a few others. I bought Packard Bell
8586 Easynote LV to run Kubuntu on and use as their home computer. But I
8587 am completely unable to figure out how to install Linux on it. The
8588 computer is preinstalled with Windows 8, and I suspect it uses UEFI
8589 instead of a BIOS to boot.&lt;/p&gt;
8590
8591 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
8592 to get it to boot the Linux installer from my USB stick. I have yet
8593 to try the DVD install, and still hope it will work. when I turn on
8594 the computer, there is no information on what buttons to press to get
8595 the normal boot menu. I expect to get some boot menu to select PXE or
8596 USB stick booting. When booting, it first ask for the language to
8597 use, then for some regional settings, and finally if I will accept the
8598 Windows 8 terms of use. As these terms are completely unacceptable to
8599 me, I have no other choice but to turn off the computer and try again
8600 to get it to boot the Linux installer.&lt;/p&gt;
8601
8602 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
8603 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
8604 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
8605 installed on this machine, please get in touch or update that wiki
8606 page. If I can&#39;t find a way to install Linux, I will have to return
8607 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
8608
8609 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
8610 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
8611 on new Laptops?&lt;/p&gt;
8612 </description>
8613 </item>
8614
8615 <item>
8616 <title>How to transform a Debian based system to a Debian Edu installation</title>
8617 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
8618 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
8619 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
8620 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
8621 an operating system based on Debian intended for use in schools. It
8622 contain a turn-key solution for the computer network provided to
8623 pupils in the primary schools. It provide both the central server,
8624 network boot servers and desktop environments with heaps of
8625 educational software. The project was founded almost 12 years ago,
8626 2001-07-02. If you want to support the project, which is in need for
8627 cash to fund developer gatherings and other project related activity,
8628 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
8629 donate some money&lt;/a&gt;.
8630
8631 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
8632 lists and elsewhere, is the question on how to transform a Debian or
8633 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
8634 hard, and last week I wrote a script to replicate the steps done by
8635 the Debian Edu installer.&lt;/p&gt;
8636
8637 &lt;p&gt;The script,
8638 &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;
8639 in the debian-edu-config package, will go through these six steps and
8640 transform an existing Debian Wheezy or Ubuntu (untested) installation
8641 into a Debian Edu Workstation:&lt;/p&gt;
8642
8643 &lt;ol&gt;
8644
8645 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
8646 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
8647 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
8648 our configuration.&lt;/li&gt;
8649 &lt;li&gt;Preseed debconf database with profile setup in
8650 /etc/debian-edu/config, and run tasksel to install packages
8651 according to the profile specified in the config above,
8652 overriding some of the Debian automation machinery.&lt;/li&gt;
8653 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
8654 that could not be done using preseeding.&lt;/li&gt;
8655 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
8656
8657 &lt;/ol&gt;
8658
8659 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
8660 replicated like this. Disk partitioning and LVM setup, for example.
8661 So this script just assume there is enough disk space to install all
8662 the needed packages.&lt;/p&gt;
8663
8664 &lt;p&gt;The script was created to help a Debian Edu student working on
8665 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
8666 Debian Edu client, and using it he can take the existing
8667 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
8668 transform it into a fully functioning Debian Edu Workstation (or
8669 Roaming Workstation, or whatever :).&lt;/p&gt;
8670
8671 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
8672 If a LXDE based Roaming workstation is wanted instead, modify the
8673 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
8674
8675 &lt;p&gt;&lt;pre&gt;
8676 PROFILE=&quot;Roaming-Workstation&quot;
8677 DESKTOP=&quot;lxde&quot;
8678 &lt;/pre&gt;&lt;/p&gt;
8679
8680 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
8681 the cloud, by starting with a virtual Debian installation at some
8682 virtual hosting service and setting up all the services on first
8683 boot.&lt;/p&gt;
8684 </description>
8685 </item>
8686
8687 <item>
8688 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
8689 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
8690 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
8691 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
8692 <description>&lt;P&gt;In January,
8693 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
8694 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
8695 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
8696 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
8697 marvellous construction system from Denmark. We also created
8698 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
8699 a place to take notes and write down our plans and hopes. And several
8700 people showed up to help. I was very happy to see the effect of my
8701 call. Since the small start, we have a debtags tag
8702 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
8703 tag for LEGO related packages, and now count 10 packages related to
8704 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
8705
8706 &lt;p&gt;&lt;table&gt;
8707 &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;
8708 &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;
8709 &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;
8710 &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;
8711 &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;
8712 &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;
8713 &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;
8714 &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;
8715 &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;
8716 &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;
8717 &lt;/table&gt;&lt;/p&gt;
8718
8719 &lt;p&gt;Some of these are available in Wheezy, and all but one are
8720 currently available in Jessie/testing. leocad is so far only
8721 available in experimental.&lt;/p&gt;
8722
8723 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
8724 adding the rest of the great free software tools available on Linux
8725 for LEGO designers.&lt;/p&gt;
8726 </description>
8727 </item>
8728
8729 <item>
8730 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
8731 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
8732 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
8733 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
8734 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
8735 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
8736 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
8737 Debian release, and I expect to move my machines at home over to it fairly
8738 soon.&lt;/p&gt;
8739
8740 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
8741 in particular make me very happy to see included. The
8742 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
8743 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
8744 included for the first time. Alongside similar programs like
8745 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
8746 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
8747 it allow for visual programming where syntax errors can not happen,
8748 and a friendly programming environment for learning to control the
8749 computer. Scratch will also be included in the next release of Debian
8750 Edu.&lt;/a&gt;
8751
8752 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
8753 Edu/Skolelinux release too. The
8754 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
8755 alpha release&lt;/a&gt; went out last week, and the next should soon
8756 follow.&lt;p&gt;
8757 </description>
8758 </item>
8759
8760 <item>
8761 <title>Isenkram 0.2 finally in the Debian archive</title>
8762 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
8763 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
8764 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
8765 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
8766 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
8767 for many months. I uploaded it to the Debian experimental suite
8768 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
8769
8770 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
8771 install to work with a pluggable hardware device. The suggestion pop
8772 up when the device is plugged in. For example if a Lego Mindstorm NXT
8773 is inserted, it will suggest to install the program needed to program
8774 the NXT controller. Give it a go, and report bugs and suggestions to
8775 BTS. :)&lt;/p&gt;
8776 </description>
8777 </item>
8778
8779 <item>
8780 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
8781 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
8782 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
8783 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
8784 <description>&lt;p&gt;My
8785 &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
8786 bitcoin related blog post&lt;/a&gt; mentioned that the new
8787 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
8788 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
8789 2013-01-19, and have been available in unstable since then. It was
8790 automatically copied to Ubuntu, and is available in their Raring
8791 version too.&lt;/p&gt;
8792
8793 &lt;p&gt;But there is a strange problem with the build that block this new
8794 version from being available on the i386 and kfreebsd-i386
8795 architectures. For some strange reason, the autobuilders in Debian
8796 for these architectures fail to run the test suite on these
8797 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
8798 We are so far unable to reproduce it when building it manually, and
8799 no-one have been able to propose a fix. If you got an idea what is
8800 failing, please let us know via the BTS.&lt;/p&gt;
8801
8802 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
8803 I often run low on disk space, is the fact that the client will exit
8804 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
8805 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
8806 it. :)&lt;/p&gt;
8807
8808 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
8809 activities, please send Bitcoin donations to my address
8810 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8811 </description>
8812 </item>
8813
8814 <item>
8815 <title>Welcome to the world, Isenkram!</title>
8816 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
8817 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
8818 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
8819 <description>&lt;p&gt;Yesterday, I
8820 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
8821 for testers&lt;/a&gt; for my prototype for making Debian better at handling
8822 pluggable hardware devices, which I
8823 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
8824 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
8825 up, and caused me to really want to to open up the development to more
8826 people. But before I did this, I want to come up with a sensible name
8827 for this project. Today I finally decided on a new name, and I have
8828 renamed the project from hw-support-handler to this new name. In the
8829 process, I moved the source to git and made it available as a
8830 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
8831 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
8832 To fetch and build the latest version of the source, use&lt;/p&gt;
8833
8834 &lt;pre&gt;
8835 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
8836 cd isenkram &amp;&amp; git-buildpackage -us -uc
8837 &lt;/pre&gt;
8838
8839 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
8840 want to hack on the source or improve the package, please go ahead.
8841 But please talk to me first on IRC or via email before you do major
8842 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
8843
8844 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
8845 stuff, typically meaning tools, nails, screws, etc. Typical hardware
8846 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
8847 the German word eisenkram, for those that are familiar with that
8848 word.&lt;/p&gt;
8849
8850 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
8851 instructions, to avoid confusing people with an error from the signing
8852 process.&lt;/p&gt;
8853
8854 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
8855 clone argument to avoid the need for authentication.&lt;/p&gt;
8856 </description>
8857 </item>
8858
8859 <item>
8860 <title>First prototype ready making hardware easier to use in Debian</title>
8861 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
8862 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
8863 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
8864 <description>&lt;p&gt;Early this month I set out to try to
8865 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
8866 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
8867 prototype is working, and it is ready for a larger audience. To test
8868 it, fetch the
8869 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
8870 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
8871 package. You might have to log out and in again activate the
8872 autostart script.&lt;/p&gt;
8873
8874 &lt;p&gt;The design is simple:&lt;/p&gt;
8875
8876 &lt;ul&gt;
8877
8878 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
8879 hw-support-handlerd to start when the user log in.&lt;/li&gt;
8880
8881 &lt;li&gt;This program listen for kernel events about new hardware (directly
8882 from the kernel like udev does), not using HAL dbus events as I
8883 initially did.&lt;/li&gt;
8884
8885 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
8886 the APT database, a database
8887 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
8888 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
8889
8890 &lt;li&gt;If a package is mapped to the hardware in question, the package
8891 isn&#39;t installed yet and this is the first time the hardware was
8892 plugged in, show a desktop notification suggesting to install the
8893 package or packages.&lt;/li&gt;
8894
8895 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
8896 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
8897
8898 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
8899 package while showing progress information in a window.&lt;/li&gt;
8900
8901 &lt;/ul&gt;
8902
8903 &lt;p&gt;I still need to come up with a better name for the system. Here
8904 are some screen shots showing the prototype in action. First the
8905 notification, then the password request, and finally the request to
8906 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
8907
8908 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
8909 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
8910 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
8911 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
8912 &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;
8913
8914 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
8915 is already useful. The database of hardware to package mappings also
8916 need more work. It is currently compatible with the Ubuntu way of
8917 storing such information in the package control file, but could be
8918 changed to use other formats instead or in addition to the current
8919 method. I&#39;ve dropped the use of discover for this mapping, as the
8920 modalias approach is more flexible and easier to use on Linux as long
8921 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
8922
8923 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
8924 here is the command required to check out and build the source: Use
8925 &#39;&lt;tt&gt;svn checkout
8926 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
8927 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
8928 devscripts package.&lt;/p&gt;
8929
8930 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
8931 renamed to Isenkram and the source moved from the Debian Edu
8932 subversion repository to a Debian collab-maint git repository. See
8933 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
8934 instructions&lt;/a&gt; for details.&lt;/p&gt;
8935 </description>
8936 </item>
8937
8938 <item>
8939 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
8940 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
8941 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
8942 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
8943 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
8944 suddenly in bed. With a quiet whimper, it went completely quiet and
8945 black. The power button was no longer able to turn it on. It was a
8946 IBM Thinkpad X41, and the best laptop I ever had. Better than both
8947 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
8948 Compaq I had before that. Now I need to find a replacement. To keep
8949 going during Christmas, I moved the one year old SSD disk to my old
8950 X40 where it fitted (only one I had left that could use it), but it is
8951 not a durable solution.
8952
8953 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
8954 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
8955
8956 &lt;ul&gt;
8957
8958 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
8959 than A4).&lt;/li&gt;
8960 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
8961 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
8962 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
8963 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
8964 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
8965 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
8966 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
8967 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
8968 size).&lt;/li&gt;
8969 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
8970 X.org packages.&lt;/li&gt;
8971 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
8972 the time).
8973
8974 &lt;/ul&gt;
8975
8976 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
8977 list. The reason is simply that the specifications on laptops the
8978 last 10-15 years have been sufficient for my needs, and I have to look
8979 at other features to choose my laptop. But are there still made as
8980 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
8981 robust, and Thinkpads seem to be heading in the wrong direction since
8982 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
8983 still be useful.&lt;/p&gt;
8984
8985 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
8986 external keyboard? I&#39;ll have to check the
8987 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
8988 well-supported laptops, or perhaps just buy one preinstalled from one
8989 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
8990 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
8991 </description>
8992 </item>
8993
8994 <item>
8995 <title>How to find a browser plugin supporting a given MIME type</title>
8996 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
8997 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
8998 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
8999 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
9000 install to get support for a given MIME type. Thanks to
9001 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
9002 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
9003 Unfortunately, not very many packages provide the needed meta
9004 information, Anyway, here is a small script to look up all browser
9005 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
9006
9007 &lt;pre&gt;
9008 #!/usr/bin/python
9009 import sys
9010 import apt
9011 def pkgs_handling_mimetype(mimetype):
9012 cache = apt.Cache()
9013 cache.open(None)
9014 thepkgs = []
9015 for pkg in cache:
9016 version = pkg.candidate
9017 if version is None:
9018 version = pkg.installed
9019 if version is None:
9020 continue
9021 record = version.record
9022 if not record.has_key(&#39;Npp-MimeType&#39;):
9023 continue
9024 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
9025 for t in mime_types:
9026 t = t.rstrip().strip()
9027 if t == mimetype:
9028 thepkgs.append(pkg.name)
9029 return thepkgs
9030 mimetype = &quot;audio/ogg&quot;
9031 if 1 &lt; len(sys.argv):
9032 mimetype = sys.argv[1]
9033 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
9034 for pkg in pkgs_handling_mimetype(mimetype):
9035 print &quot; %s&quot; %pkg
9036 &lt;/pre&gt;
9037
9038 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
9039
9040 &lt;pre&gt;
9041 % ./apt-find-browserplug-for-mimetype
9042 Browser plugin packages supporting audio/ogg:
9043 gecko-mediaplayer
9044 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
9045 Browser plugin packages supporting application/x-shockwave-flash:
9046 browser-plugin-gnash
9047 %
9048 &lt;/pre&gt;
9049
9050 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
9051 itself to query for plugins and propose to install the needed
9052 packages. It would be great if Debian supported such feature too. Is
9053 anyone working on adding it?&lt;/p&gt;
9054
9055 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
9056 request for icweasel support for this feature is
9057 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
9058 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
9059 of manpower and wish for a different design is the reason thus feature
9060 is not yet in iceweasel from Debian.&lt;/p&gt;
9061 </description>
9062 </item>
9063
9064 <item>
9065 <title>What is the most supported MIME type in Debian?</title>
9066 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
9067 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
9068 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
9069 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
9070 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
9071 proposal to make it possible for a Desktop application to propose to
9072 the user some package to install to gain support for a given MIME
9073 type, font, library etc. that is currently missing. With such
9074 mechanism in place, it would be possible for the desktop to
9075 automatically propose and install leocad if some LDraw file is
9076 downloaded by the browser.&lt;/p&gt;
9077
9078 &lt;p&gt;To get some idea about the current content of the archive, I decided
9079 to write a simple program to extract all .desktop files from the
9080 Debian archive and look up the claimed MIME support there. The result
9081 can be found on the
9082 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
9083 site&lt;/a&gt;. Using the collected information, it become possible to
9084 answer the question in the title. Here are the 20 most supported MIME
9085 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
9086 The complete list is available from the link above.&lt;/p&gt;
9087
9088 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
9089
9090 &lt;pre&gt;
9091 count MIME type
9092 ----- -----------------------
9093 32 text/plain
9094 30 audio/mpeg
9095 29 image/png
9096 28 image/jpeg
9097 27 application/ogg
9098 26 audio/x-mp3
9099 25 image/tiff
9100 25 image/gif
9101 22 image/bmp
9102 22 audio/x-wav
9103 20 audio/x-flac
9104 19 audio/x-mpegurl
9105 18 video/x-ms-asf
9106 18 audio/x-musepack
9107 18 audio/x-mpeg
9108 18 application/x-ogg
9109 17 video/mpeg
9110 17 audio/x-scpls
9111 17 audio/ogg
9112 16 video/x-ms-wmv
9113 &lt;/pre&gt;
9114
9115 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
9116
9117 &lt;pre&gt;
9118 count MIME type
9119 ----- -----------------------
9120 33 text/plain
9121 32 image/png
9122 32 image/jpeg
9123 29 audio/mpeg
9124 27 image/gif
9125 26 image/tiff
9126 26 application/ogg
9127 25 audio/x-mp3
9128 22 image/bmp
9129 21 audio/x-wav
9130 19 audio/x-mpegurl
9131 19 audio/x-mpeg
9132 18 video/mpeg
9133 18 audio/x-scpls
9134 18 audio/x-flac
9135 18 application/x-ogg
9136 17 video/x-ms-asf
9137 17 text/html
9138 17 audio/x-musepack
9139 16 image/x-xbitmap
9140 &lt;/pre&gt;
9141
9142 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
9143
9144 &lt;pre&gt;
9145 count MIME type
9146 ----- -----------------------
9147 31 text/plain
9148 31 image/png
9149 31 image/jpeg
9150 29 audio/mpeg
9151 28 application/ogg
9152 27 image/gif
9153 26 image/tiff
9154 26 audio/x-mp3
9155 23 audio/x-wav
9156 22 image/bmp
9157 21 audio/x-flac
9158 20 audio/x-mpegurl
9159 19 audio/x-mpeg
9160 18 video/x-ms-asf
9161 18 video/mpeg
9162 18 audio/x-scpls
9163 18 application/x-ogg
9164 17 audio/x-musepack
9165 16 video/x-ms-wmv
9166 16 video/x-msvideo
9167 &lt;/pre&gt;
9168
9169 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
9170 information mentioned in DEP-11. I have not yet had time to look at
9171 it, but hope the PackageKit people in Debian are on top of these
9172 issues.&lt;/p&gt;
9173
9174 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
9175 discovering a typo in my script.&lt;/p&gt;
9176 </description>
9177 </item>
9178
9179 <item>
9180 <title>Using modalias info to find packages handling my hardware</title>
9181 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
9182 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
9183 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
9184 <description>&lt;p&gt;Yesterday, I wrote about the
9185 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
9186 values provided by the Linux kernel&lt;/a&gt; following my hope for
9187 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
9188 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
9189 modalias values attached to package names can be used to map packages
9190 to hardware. This allow the system to look up and suggest relevant
9191 packages when I plug in some new hardware into my machine, and replace
9192 discover and discover-data as the database used to map hardware to
9193 packages.&lt;/p&gt;
9194
9195 &lt;p&gt;I create a modaliases file with entries like the following,
9196 containing package name, kernel module name (if relevant, otherwise
9197 the package name) and globs matching the relevant hardware
9198 modalias.&lt;/p&gt;
9199
9200 &lt;p&gt;&lt;blockquote&gt;
9201 Package: package-name
9202 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
9203 &lt;/blockquote&gt;&lt;/p&gt;
9204
9205 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
9206 for a given modalias value using this file.&lt;/p&gt;
9207
9208 &lt;p&gt;An entry like this would suggest the video and picture application
9209 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
9210
9211 &lt;p&gt;&lt;blockquote&gt;
9212 Package: cheese
9213 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
9214 &lt;/blockquote&gt;&lt;/p&gt;
9215
9216 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
9217 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
9218
9219 &lt;p&gt;&lt;blockquote&gt;
9220 Package: pcmciautils
9221 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
9222 &lt;/blockquote&gt;&lt;/p&gt;
9223
9224 &lt;p&gt;An entry like this would suggest the package colorhug-client when
9225 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
9226
9227 &lt;p&gt;&lt;blockquote&gt;
9228 Package: colorhug-client
9229 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
9230 &lt;/blockquote&gt;&lt;/p&gt;
9231
9232 &lt;p&gt;I believe the format is compatible with the format of the Packages
9233 file in the Debian archive. Ubuntu already uses their Packages file
9234 to store their mappings from packages to hardware.&lt;/p&gt;
9235
9236 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
9237 announce the hardware it support in a way my prototype understand.
9238 This allow those publishing packages in an APT source outside the
9239 Debian archive as well as those backporting packages to make sure the
9240 hardware mapping are included in the package meta information. I&#39;ve
9241 tested such header in the pymissile package, and its modalias mapping
9242 is working as it should with my prototype. It even made it to Ubuntu
9243 Raring.&lt;/p&gt;
9244
9245 &lt;p&gt;To test if it was possible to look up supported hardware using only
9246 the shell tools available in the Debian installer, I wrote a shell
9247 implementation of the lookup code. The idea is to create files for
9248 each modalias and let the shell do the matching. Please check out and
9249 try the
9250 &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;
9251 shell script. It run without any extra dependencies and fetch the
9252 hardware mappings from the Debian archive and the subversion
9253 repository where I currently work on my prototype.&lt;/p&gt;
9254
9255 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
9256 install yubikey-personalization:&lt;/p&gt;
9257
9258 &lt;p&gt;&lt;blockquote&gt;
9259 % ./hw-support-lookup
9260 &lt;br&gt;yubikey-personalization
9261 &lt;br&gt;%
9262 &lt;/blockquote&gt;&lt;/p&gt;
9263
9264 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
9265 propose to install the pcmciautils package:&lt;/p&gt;
9266
9267 &lt;p&gt;&lt;blockquote&gt;
9268 % ./hw-support-lookup
9269 &lt;br&gt;pcmciautils
9270 &lt;br&gt;%
9271 &lt;/blockquote&gt;&lt;/p&gt;
9272
9273 &lt;p&gt;If you know of any hardware-package mapping that should be added to
9274 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
9275 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
9276
9277 &lt;p&gt;It could be possible to generate several of the mappings between
9278 packages and hardware. One source would be to look at packages with
9279 kernel modules, ie packages with *.ko files in /lib/modules/, and
9280 extract their modalias information. Another would be to look at
9281 packages with udev rules, ie packages with files in
9282 /lib/udev/rules.d/, and extract their vendor/model information to
9283 generate a modalias matching rule. I have not tested any of these to
9284 see if it work.&lt;/p&gt;
9285
9286 &lt;p&gt;If you want to help implementing a system to let us propose what
9287 packages to install when new hardware is plugged into a Debian
9288 machine, please send me an email or talk to me on
9289 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
9290 </description>
9291 </item>
9292
9293 <item>
9294 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
9295 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
9296 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
9297 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
9298 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
9299 information, to find the packages that support a given piece of
9300 hardware, I refreshed my memory regarding modalias values, and decided
9301 to document the details. Here are my findings so far, also available
9302 in
9303 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
9304 Debian Edu subversion repository&lt;/a&gt;:
9305
9306 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
9307
9308 &lt;p&gt;This document try to explain what the different types of modalias
9309 values stands for. It is in part based on information from
9310 &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;,
9311 &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;,
9312 &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
9313 &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;.
9314
9315 &lt;p&gt;The modalias entries for a given Linux machine can be found using
9316 this shell script:&lt;/p&gt;
9317
9318 &lt;pre&gt;
9319 find /sys -name modalias -print0 | xargs -0 cat | sort -u
9320 &lt;/pre&gt;
9321
9322 &lt;p&gt;The supported modalias globs for a given kernel module can be found
9323 using modinfo:&lt;/p&gt;
9324
9325 &lt;pre&gt;
9326 % /sbin/modinfo psmouse | grep alias:
9327 alias: serio:ty05pr*id*ex*
9328 alias: serio:ty01pr*id*ex*
9329 %
9330 &lt;/pre&gt;
9331
9332 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
9333
9334 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
9335 Bridge memory controller:&lt;/p&gt;
9336
9337 &lt;p&gt;&lt;blockquote&gt;
9338 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
9339 &lt;/blockquote&gt;&lt;/p&gt;
9340
9341 &lt;p&gt;This represent these values:&lt;/p&gt;
9342
9343 &lt;pre&gt;
9344 v 00008086 (vendor)
9345 d 00002770 (device)
9346 sv 00001028 (subvendor)
9347 sd 000001AD (subdevice)
9348 bc 06 (bus class)
9349 sc 00 (bus subclass)
9350 i 00 (interface)
9351 &lt;/pre&gt;
9352
9353 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
9354 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
9355 0600. The 0600 class is a host bridge. Other useful bus values are
9356 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
9357
9358 &lt;p&gt;Not sure how to figure out the interface value, nor what it
9359 means.&lt;/p&gt;
9360
9361 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
9362
9363 &lt;p&gt;Some typical USB entries can look like this. This is an internal
9364 USB hub in a laptop:&lt;/p&gt;
9365
9366 &lt;p&gt;&lt;blockquote&gt;
9367 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
9368 &lt;/blockquote&gt;&lt;/p&gt;
9369
9370 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
9371
9372 &lt;pre&gt;
9373 v 1D6B (device vendor)
9374 p 0001 (device product)
9375 d 0206 (bcddevice)
9376 dc 09 (device class)
9377 dsc 00 (device subclass)
9378 dp 00 (device protocol)
9379 ic 09 (interface class)
9380 isc 00 (interface subclass)
9381 ip 00 (interface protocol)
9382 &lt;/pre&gt;
9383
9384 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
9385 class is in the interface class section. For a simple USB web camera,
9386 these alias entries show up:&lt;/p&gt;
9387
9388 &lt;p&gt;&lt;blockquote&gt;
9389 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
9390 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
9391 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
9392 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
9393 &lt;/blockquote&gt;&lt;/p&gt;
9394
9395 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
9396 camera), 0101 is audio control device and 0102 is audio streaming (aka
9397 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
9398
9399 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
9400
9401 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
9402 receiver in a Thinkpad X40:&lt;/p&gt;
9403
9404 &lt;p&gt;&lt;blockquote&gt;
9405 acpi:IBM0071:PNP0511:
9406 &lt;/blockquote&gt;&lt;/p&gt;
9407
9408 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
9409
9410 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
9411
9412 &lt;p&gt;The DMI table contain lots of information about the computer case
9413 and model. This is an entry for a IBM Thinkpad X40, fetched from
9414 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
9415
9416 &lt;p&gt;&lt;blockquote&gt;
9417 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
9418 &lt;/blockquote&gt;&lt;/p&gt;
9419
9420 &lt;p&gt;The values present are&lt;/p&gt;
9421
9422 &lt;pre&gt;
9423 bvn IBM (BIOS vendor)
9424 bvr 1UETB6WW(1.66) (BIOS version)
9425 bd 06/15/2005 (BIOS date)
9426 svn IBM (system vendor)
9427 pn 2371H4G (product name)
9428 pvr ThinkPadX40 (product version)
9429 rvn IBM (board vendor)
9430 rn 2371H4G (board name)
9431 rvr NotAvailable (board version)
9432 cvn IBM (chassis vendor)
9433 ct 10 (chassis type)
9434 cvr NotAvailable (chassis version)
9435 &lt;/pre&gt;
9436
9437 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
9438 found in the dmidecode source:&lt;/p&gt;
9439
9440 &lt;pre&gt;
9441 3 Desktop
9442 4 Low Profile Desktop
9443 5 Pizza Box
9444 6 Mini Tower
9445 7 Tower
9446 8 Portable
9447 9 Laptop
9448 10 Notebook
9449 11 Hand Held
9450 12 Docking Station
9451 13 All In One
9452 14 Sub Notebook
9453 15 Space-saving
9454 16 Lunch Box
9455 17 Main Server Chassis
9456 18 Expansion Chassis
9457 19 Sub Chassis
9458 20 Bus Expansion Chassis
9459 21 Peripheral Chassis
9460 22 RAID Chassis
9461 23 Rack Mount Chassis
9462 24 Sealed-case PC
9463 25 Multi-system
9464 26 CompactPCI
9465 27 AdvancedTCA
9466 28 Blade
9467 29 Blade Enclosing
9468 &lt;/pre&gt;
9469
9470 &lt;p&gt;The chassis type values are not always accurately set in the DMI
9471 table. For example my home server is a tower, but the DMI modalias
9472 claim it is a desktop.&lt;/p&gt;
9473
9474 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
9475
9476 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
9477 test machine:&lt;/p&gt;
9478
9479 &lt;p&gt;&lt;blockquote&gt;
9480 serio:ty01pr00id00ex00
9481 &lt;/blockquote&gt;&lt;/p&gt;
9482
9483 &lt;p&gt;The values present are&lt;/p&gt;
9484
9485 &lt;pre&gt;
9486 ty 01 (type)
9487 pr 00 (prototype)
9488 id 00 (id)
9489 ex 00 (extra)
9490 &lt;/pre&gt;
9491
9492 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
9493 the valid values are.&lt;/p&gt;
9494
9495 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
9496
9497 &lt;p&gt;There are heaps of other modalias subtypes according to
9498 file2alias.c. There is the rest of the list from that source: amba,
9499 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
9500 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
9501 vmbus, x86cpu and zorro. I did not spend time documenting all of
9502 these, as they do not seem relevant for my intended use with mapping
9503 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
9504
9505 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
9506
9507 &lt;p&gt;To check which kernel modules provide support for a given modalias,
9508 one can use the following shell script:&lt;/p&gt;
9509
9510 &lt;pre&gt;
9511 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
9512 echo &quot;$id&quot; ; \
9513 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
9514 done
9515 &lt;/pre&gt;
9516
9517 &lt;p&gt;The output can look like this (only the first few entries as the
9518 list is very long on my test machine):&lt;/p&gt;
9519
9520 &lt;pre&gt;
9521 acpi:ACPI0003:
9522 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
9523 acpi:device:
9524 FATAL: Module acpi:device: not found.
9525 acpi:IBM0068:
9526 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
9527 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
9528 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
9529 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
9530 acpi:IBM0071:PNP0511:
9531 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
9532 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
9533 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
9534 [...]
9535 &lt;/pre&gt;
9536
9537 &lt;p&gt;If you want to help implementing a system to let us propose what
9538 packages to install when new hardware is plugged into a Debian
9539 machine, please send me an email or talk to me on
9540 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
9541
9542 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
9543 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
9544 in /sys/ with space in them.&lt;/p&gt;
9545 </description>
9546 </item>
9547
9548 <item>
9549 <title>Moved the pymissile Debian packaging to collab-maint</title>
9550 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
9551 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
9552 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
9553 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
9554 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
9555 Launcher and updated the Debian package
9556 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
9557 sure udev will fix the device permissions when it is plugged in. I
9558 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
9559 hopefully make the package be proposed by jockey in Ubuntu when a user
9560 plug in his rocket launcher. In the process I moved the source to a
9561 git repository under collab-maint, to make it easier for any DD to
9562 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
9563 is not very active, but the software still work for me even after five
9564 years of relative silence. The new git repository is not listed in
9565 the uploaded package yet, because I want to test the other changes a
9566 bit more before I upload the new version. If you want to check out
9567 the new version with a .desktop file included, visit the
9568 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
9569 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
9570 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
9571 </description>
9572 </item>
9573
9574 <item>
9575 <title>Lets make hardware dongles easier to use in Debian</title>
9576 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
9577 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
9578 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
9579 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
9580 general, is that there is a great package management system with the
9581 ability to automatically install software packages by downloading them
9582 from the distribution mirrors, but no way to get it to automatically
9583 install the packages I need to use the hardware I plug into my
9584 machine. Even if the package to use it is easily available from the
9585 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
9586 suggest to automatically install the python-nxt, nbc and t2n packages
9587 I need to talk to it. When I plug in a Yubikey, it could propose the
9588 yubikey-personalization package. The information required to do this
9589 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
9590
9591 &lt;p&gt;Some years ago, I proposed to
9592 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
9593 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
9594 simple:
9595
9596 &lt;ul&gt;
9597
9598 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
9599 starting when a user log in.&lt;/li&gt;
9600
9601 &lt;li&gt;Set this program up to listen for kernel events emitted when new
9602 hardware is inserted into the computer.&lt;/li&gt;
9603
9604 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
9605 database mapping to packages, and take note of any non-installed
9606 packages.&lt;/li&gt;
9607
9608 &lt;li&gt;Show a message to the user proposing to install the discovered
9609 package, and make it easy to install it.&lt;/li&gt;
9610
9611 &lt;/ul&gt;
9612
9613 &lt;p&gt;I am not sure what the best way to implement this is, but my
9614 initial idea was to use dbus events to discover new hardware, the
9615 discover database to find packages and
9616 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
9617 packages.&lt;/p&gt;
9618
9619 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
9620 draft package is now checked into
9621 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
9622 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
9623 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
9624 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
9625 the relevant packages in Debian, and uploaded a new version
9626 2.2013.01.09 to unstable. I also discovered that the current
9627 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
9628 package in Debian no longer discovered any USB devices, because
9629 /proc/bus/usb/devices is no longer present. I ported it to use
9630 libusb as a fall back option to get it working. The fixed package
9631 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
9632 because of the freeze).&lt;/p&gt;
9633
9634 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
9635 desktop notification to show up (only once, the first time it is
9636 inserted):&lt;/p&gt;
9637
9638 &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;
9639
9640 &lt;p&gt;For this prototype to be really useful, some way to automatically
9641 install the proposed packages by pressing the &quot;Please install
9642 program(s)&quot; button should to be implemented.&lt;/p&gt;
9643
9644 &lt;p&gt;If this idea seem useful to you, and you want to help make it
9645 happen, please help me update the discover-data database with mappings
9646 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
9647 list the package you would like to have installed when a given
9648 hardware device is inserted into your computer, and report bugs using
9649 reportbug if it isn&#39;t. Or, if you know of a better way to provide
9650 such mapping, please let me know.&lt;/p&gt;
9651
9652 &lt;p&gt;This prototype need more work, and there are several questions that
9653 should be considered before it is ready for production use. Is dbus
9654 the correct way to detect new hardware? At the moment I look for HAL
9655 dbus events on the system bus, because that is the events I could see
9656 on my Debian Squeeze KDE desktop. Are there better events to use?
9657 How should the user be notified? Is the desktop notification
9658 mechanism the best option, or should the background daemon raise a
9659 popup instead? How should packages be installed? When should they
9660 not be installed?&lt;/p&gt;
9661
9662 &lt;p&gt;If you want to help getting such feature implemented in Debian,
9663 please send me an email. :)&lt;/p&gt;
9664 </description>
9665 </item>
9666
9667 <item>
9668 <title>New IRC channel for LEGO designers using Debian</title>
9669 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
9670 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
9671 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
9672 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
9673 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
9674 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
9675 discovered I had to build all the tools myself because none were
9676 already in Debian Squeeze. If Debian support for LEGO is something
9677 you care about, please join me on the IRC channel
9678 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
9679 irc.debian.org). There is a lot that could be done to improve the
9680 Debian support for LEGO designers. For example both CAD software
9681 and Mindstorm compilers are missing. :)&lt;/p&gt;
9682
9683 &lt;p&gt;Update 2012-01-03: A
9684 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
9685 including links to Lego related packages is now available.&lt;/p&gt;
9686 </description>
9687 </item>
9688
9689 <item>
9690 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
9691 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
9692 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
9693 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
9694 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
9695 year! I hope next year will prove to be a good year.&lt;/p&gt;
9696
9697 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
9698 decentralised &quot;currency&quot; that allow people to transfer bitcoins
9699 between each other with minimal overhead, is a very interesting
9700 experiment. And as I wrote a few days ago, the bitcoin situation in
9701 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
9702 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
9703 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
9704 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
9705 for one of the ftpmasters to approve the new bitcoin-qt package
9706 name.&lt;/p&gt;
9707
9708 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
9709 team in Debian, you can easily test the package in Debian Squeeze
9710 using the following steps to get a set of working packages:&lt;/p&gt;
9711
9712 &lt;blockquote&gt;&lt;pre&gt;
9713 git clone git://git.debian.org/git/collab-maint/bitcoin
9714 cd bitcoin
9715 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
9716 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
9717 &lt;/pre&gt;&lt;/blockquote&gt;
9718
9719 &lt;p&gt;You might have to install some build dependencies as well. The
9720 list of commands should give you two packages, bitcoind and
9721 bitcoin-qt, ready for use in a Squeeze environment. Note that the
9722 client will download the complete set of bitcoin &quot;blocks&quot;, which need
9723 around 5.6 GiB of data on my machine at the moment. Make sure your
9724 ~/.bitcoin/ directory have lots of spare room if you want to download
9725 all the blocks. The client will warn if the disk is getting full, so
9726 there is not really a problem if you got too little room, but you will
9727 not be able to get all the features out of the client.&lt;/p&gt;
9728
9729 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
9730 activities, please send Bitcoin donations to my address
9731 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
9732 </description>
9733 </item>
9734
9735 <item>
9736 <title>A word on bitcoin support in Debian</title>
9737 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
9738 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
9739 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
9740 <description>&lt;p&gt;It has been a while since I wrote about
9741 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
9742 peer-to-peer based crypto-currency, and the reason is simply that I
9743 have been busy elsewhere. But two days ago, I started looking at the
9744 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
9745 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
9746 is now maintained by a
9747 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
9748 people&lt;/a&gt;, and the grunt work had already been done by this team. We
9749 owe a huge thank you to all these team members. :)
9750 But I was sad to discover that the bitcoin client is missing in
9751 Wheezy. It is only available in Sid (and an outdated client from
9752 backports). The client had several RC bugs registered in BTS blocking
9753 it from entering testing. To try to help the team and improve the
9754 situation, I spent some time providing patches and triaging the bug
9755 reports. I also had a look at the bitcoin package available from Matt
9756 Corallo in a
9757 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
9758 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
9759 Debian package.&lt;/p&gt;
9760
9761 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
9762 IRC, I pushed several patches into the collab-maint git repository to
9763 improve the package. It now contains fixes for the RC issues (not from
9764 me, but fixed by Scott Howard), build rules for a Qt GUI client
9765 package, konqueror support for the bitcoin: URI and bash completion
9766 setup. As I work on Debian Squeeze, I also created
9767 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
9768 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
9769 it and try to integrate it into the git repository before uploading a
9770 new version to unstable.
9771
9772 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
9773 centralized control currently exercised in the monetary system. I
9774 find it completely unacceptable that the USA government is collecting
9775 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
9776 that the major credit card companies can block legal money
9777 transactions to Wikileaks. But for bitcoin to succeed, more people
9778 need to use bitcoins, and more people need to accept bitcoins when
9779 they sell products and services. Improving the bitcoin support in
9780 Debian is a small step in the right direction, but not enough.
9781 Unfortunately the user experience when browsing the web and wanting to
9782 pay with bitcoin is still not very good. The bitcoin: URI is a step
9783 in the right direction, but need to work in most or every browser in
9784 use. Also the bitcoin-qt client is too heavy to fire up to do a
9785 quick transaction. I believe there are other clients available, but
9786 have not tested them.&lt;/p&gt;
9787
9788 &lt;p&gt;My
9789 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
9790 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
9791 I received 20.15 BTC so far on the address I provided in my blog two
9792 years ago, as can be
9793 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
9794 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
9795 donation. The blockexplorer service demonstrates quite well that
9796 bitcoin is not quite anonymous and untracked. :) I wonder if the
9797 number of users have gone up since then. If you use bitcoin and want
9798 to show your support of my activity, please send Bitcoin donations to
9799 the same address as last time,
9800 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
9801 </description>
9802 </item>
9803
9804 <item>
9805 <title>Git repository for song book for Computer Scientists</title>
9806 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
9807 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
9808 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
9809 <description>&lt;p&gt;As I
9810 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
9811 this summer&lt;/a&gt;, I have created a Computer Science song book a few
9812 years ago, and today I finally found time to create a public
9813 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
9814 repository for the project&lt;/a&gt;.&lt;/p&gt;
9815
9816 &lt;p&gt;If you want to help out, please clone the source and submit patches
9817 to the HTML version. To generate the PDF and PostScript version,
9818 please use prince XML, or let me know about a useful free software
9819 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
9820
9821 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
9822 PostScript formats at
9823 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
9824 Science Songbook&lt;/a&gt;.&lt;/p&gt;
9825 </description>
9826 </item>
9827
9828 <item>
9829 <title>Gratulerer med 19-årsdagen, Debian!</title>
9830 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
9831 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
9832 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
9833 <description>&lt;p&gt;I dag fyller
9834 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
9835 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
9836 si gratulerer med dagen, Debian!&lt;/p&gt;
9837 </description>
9838 </item>
9839
9840 <item>
9841 <title>Song book for Computer Scientists</title>
9842 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
9843 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
9844 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
9845 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
9846 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
9847 collecting computer related songs for use at parties. The original
9848 version was written in LaTeX, but a few years ago I got help from
9849 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
9850 while keeping the ability to create a nice book in PDF format. I have
9851 not had time to maintain the book for a while now, and guess I should
9852 put it up on some public version control repository where others can
9853 help me extend and update the book. If anyone is volunteering to help
9854 me with this, send me an email. Also let me know if there are songs
9855 missing in my book.&lt;/p&gt;
9856
9857 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
9858 me today that I really should let all my readers share the joys of
9859 singing out load about programming, computers and computer networks.
9860 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
9861 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
9862 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
9863 Computer Science Songbook&lt;/a&gt;.
9864 </description>
9865 </item>
9866
9867 <item>
9868 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
9869 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
9870 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
9871 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
9872 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
9873 around 1000 at the moment. To be able to get help from the vendors
9874 when something go wrong, we want to keep the firmware on the servers
9875 up to date. If the firmware isn&#39;t the latest and greatest, the
9876 vendors typically refuse to start debugging any problems until the
9877 firmware is upgraded. So before every reboot, we want to upgrade the
9878 firmware, and we would really like everyone handling servers at the
9879 university to do this themselves when they plan to reboot a machine.
9880 For that to happen we at the unix server admin group need to provide
9881 the tools to do so.&lt;/p&gt;
9882
9883 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
9884 fetch and install the latest firmware for the servers we got. Most of
9885 our hardware are from Dell and HP, so I have focused on these servers
9886 so far. This blog post is about the Dell part.&lt;/P&gt;
9887
9888 &lt;p&gt;On the Dell FTP site I was lucky enough to find
9889 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
9890 with firmware information for all 11th generation servers, listing
9891 which firmware should be used on a given model and where on the FTP
9892 site I can find it. Using a simple perl XML parser I can then
9893 download the shell scripts Dell provides to do firmware upgrades from
9894 within Linux and reboot when all the firmware is primed and ready to
9895 be activated on the first reboot.&lt;/p&gt;
9896
9897 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
9898 Are there anyone working on similar tools for firmware upgrading all
9899 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
9900
9901 &lt;p&gt;&lt;pre&gt;
9902 #!/usr/bin/perl
9903 use strict;
9904 use warnings;
9905 use File::Temp qw(tempdir);
9906 BEGIN {
9907 # Install needed RHEL packages if missing
9908 my %rhelmodules = (
9909 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
9910 );
9911 for my $module (keys %rhelmodules) {
9912 eval &quot;use $module;&quot;;
9913 if ($@) {
9914 my $pkg = $rhelmodules{$module};
9915 system(&quot;yum install -y $pkg&quot;);
9916 eval &quot;use $module;&quot;;
9917 }
9918 }
9919 }
9920 my $errorsto = &#39;pere@hungry.com&#39;;
9921
9922 upgrade_dell();
9923
9924 exit 0;
9925
9926 sub run_firmware_script {
9927 my ($opts, $script) = @_;
9928 unless ($script) {
9929 print STDERR &quot;fail: missing script name\n&quot;;
9930 exit 1
9931 }
9932 print STDERR &quot;Running $script\n\n&quot;;
9933
9934 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
9935 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
9936 } else {
9937 print STDERR &quot;fail: firmware script returned error\n&quot;;
9938 }
9939 }
9940
9941 sub run_firmware_scripts {
9942 my ($opts, @dirs) = @_;
9943 # Run firmware packages
9944 for my $dir (@dirs) {
9945 print STDERR &quot;info: Running scripts in $dir\n&quot;;
9946 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
9947 while (my $s = readdir $dh) {
9948 next if $s =~ m/^\.\.?/;
9949 run_firmware_script($opts, &quot;$dir/$s&quot;);
9950 }
9951 closedir $dh;
9952 }
9953 }
9954
9955 sub download {
9956 my $url = shift;
9957 print STDERR &quot;info: Downloading $url\n&quot;;
9958 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
9959 }
9960
9961 sub upgrade_dell {
9962 my @dirs;
9963 my $product = `dmidecode -s system-product-name`;
9964 chomp $product;
9965
9966 if ($product =~ m/PowerEdge/) {
9967
9968 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
9969 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
9970
9971 my $tmpdir = tempdir(
9972 CLEANUP =&gt; 1
9973 );
9974 chdir($tmpdir);
9975 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
9976 system(&#39;gunzip Catalog.xml.gz&#39;);
9977 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
9978 # -q is quiet, disabling interactivity and reducing console output
9979 my $fwopts = &quot;-q&quot;;
9980 if (@paths) {
9981 for my $url (@paths) {
9982 fetch_dell_fw($url);
9983 }
9984 run_firmware_scripts($fwopts, $tmpdir);
9985 } else {
9986 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
9987 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
9988 }
9989 chdir(&#39;/&#39;);
9990 } else {
9991 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
9992 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
9993 }
9994 }
9995
9996 sub fetch_dell_fw {
9997 my $path = shift;
9998 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
9999 download($url);
10000 }
10001
10002 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
10003 # firmware packages to download from Dell. Only work for Linux
10004 # machines and 11th generation Dell servers.
10005 sub fetch_dell_fw_list {
10006 my $filename = shift;
10007
10008 my $product = `dmidecode -s system-product-name`;
10009 chomp $product;
10010 my ($mybrand, $mymodel) = split(/\s+/, $product);
10011
10012 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
10013
10014 my $xml = XMLin($filename);
10015 my @paths;
10016 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
10017 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
10018 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
10019 my $oscode;
10020 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
10021 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
10022 } else {
10023 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
10024 }
10025 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
10026 {
10027 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
10028 }
10029 }
10030 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
10031 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
10032
10033 # Drop application packages, only firmware and BIOS
10034 next if &#39;APAC&#39; eq $componenttype;
10035
10036 my $cpath = $component-&gt;{path};
10037 for my $path (@paths) {
10038 if ($cpath =~ m%/$path$%) {
10039 push(@paths, $cpath);
10040 }
10041 }
10042 }
10043 return @paths;
10044 }
10045 &lt;/pre&gt;
10046
10047 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
10048 it could work on other platforms with some tweaking. Anyone know a
10049 index like Catalog.xml is available from HP for HP servers? At the
10050 moment I maintain a similar list manually and it is quickly getting
10051 outdated.&lt;/p&gt;
10052 </description>
10053 </item>
10054
10055 <item>
10056 <title>How is booting into runlevel 1 different from single user boots?</title>
10057 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
10058 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
10059 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
10060 <description>&lt;p&gt;Wouter Verhelst have some
10061 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
10062 comments and opinions&lt;/a&gt; on my blog post on
10063 &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
10064 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
10065 &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
10066 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
10067 small piece of his comment now, and though it best to address the
10068 misunderstanding he bring forward:&lt;/p&gt;
10069
10070 &lt;p&gt;&lt;blockquote&gt;
10071 Currently, a system admin has four options: [...] boot to a
10072 single-user system (by adding &#39;single&#39; to the kernel command line;
10073 this runs rcS and rc1 scripts)
10074 &lt;/blockquote&gt;&lt;/p&gt;
10075
10076 &lt;p&gt;This make me believe Wouter believe booting into single user mode
10077 and booting into runlevel 1 is the same. I am not surprised he
10078 believe this, because it would make sense and is a quite sensible
10079 thing to believe. But because the boot in Debian is slightly broken,
10080 runlevel 1 do not work properly and it isn&#39;t the same as single user
10081 mode. I&#39;ll try to explain what is actually happing, but it is a bit
10082 hard to explain.&lt;/p&gt;
10083
10084 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
10085 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
10086 executed in single user mode is sulogin. Single user mode is a boot
10087 state &quot;between&quot; the runlevels, and when booting into single user mode,
10088 only the scripts in /etc/rcS.d/ are executed before the init process
10089 enters the single user state. When switching to runlevel 1, the state
10090 is in fact not ending in runlevel 1, but it passes through runlevel 1
10091 and end up in the single user mode (see /etc/rc1.d/S03single, which
10092 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
10093 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
10094 mode enabled by /etc/rcS.d/ (which is more like the initial boot
10095 mode).&lt;/p&gt;
10096
10097 &lt;p&gt;This summary might make it clearer. When booting for the first
10098 time into single user mode, the following commands are executed:
10099 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
10100 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
10101 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
10102 trying to continue after visiting single user mode. Not all services
10103 are started again as they should, causing the machine to end up in an
10104 unpredicatble state. This is why Debian admins recommend rebooting
10105 after visiting single user mode.&lt;/p&gt;
10106
10107 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
10108 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
10109 to runlevel 1, the services started from /etc/rcS.d/ are not properly
10110 stopped when passing through the scripts in /etc/rc1.d/, and not
10111 started again when switching away from runlevel 1 to the runlevels
10112 2-5. I believe the problem is best fixed by moving all the scripts
10113 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
10114 functioning single user mode during boot.&lt;/p&gt;
10115
10116 &lt;p&gt;I have spent several years investigating the Debian boot system,
10117 and discovered this problem a few years ago. I suspect it originates
10118 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
10119 </description>
10120 </item>
10121
10122 <item>
10123 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
10124 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
10125 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
10126 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
10127 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
10128 are started from /etc/rcS.d/. In fact, there is a bite more of them
10129 than make sense, and this causes a few problems. What kind of
10130 problems, you might ask. There are at least two problems. The first
10131 is that it is not possible to recover a machine after switching to
10132 runlevel 1. One need to actually reboot to get the machine back to
10133 the expected state. The other is that single user boot will sometimes
10134 run into problems because some of the subsystems are activated before
10135 the root login is presented, causing problems when trying to recover a
10136 machine from a problem in that subsystem. A minor additional point is
10137 that moving more scripts out of rcS.d/ and into the other rc#.d/
10138 directories will increase the amount of scripts that can run in
10139 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
10140
10141 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
10142 scripts that _have_ to execute before the root login prompt is
10143 presented during a single user boot should go there. Everything else
10144 should go into the numeric runlevels. This means things like
10145 lm-sensors, fuse and x11-common should not run from rcS.d, but from
10146 the numeric runlevels. Today in Debian, there are around 115 init.d
10147 scripts that are started from rcS.d/, and most of them should be moved
10148 out. Do your package have one of them? Please help us make single
10149 user and runlevel 1 better by moving it.&lt;/p&gt;
10150
10151 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
10152 etc. should still be started from rcS.d/, but there is for example no
10153 need to have the network enabled before the single user login prompt
10154 is presented.&lt;/p&gt;
10155
10156 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
10157 Debian systems working while scripts migrate and during upgrades, the
10158 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
10159 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
10160 and the next ones can only be moved when their dependencies have been
10161 moved first. This migration must be done sequentially while we ensure
10162 that the package system upgrade packages in the right order to keep
10163 the system state correct. This will require some coordination when it
10164 comes to network related packages, but most of the packages with
10165 scripts that should migrate do not have anything in rcS.d/ depending
10166 on them. Some packages have already been updated, like the sudo
10167 package, while others are still left to do. I wish I had time to work
10168 on this myself, but real live constrains make it unlikely that I will
10169 find time to push this forward.&lt;/p&gt;
10170 </description>
10171 </item>
10172
10173 <item>
10174 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
10175 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
10176 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
10177 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
10178 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
10179 mentioned the issues I believe should be improved in Debian for its
10180 desktop to be useful for more people. The use case for this is my
10181 parents, which are currently running Kubuntu which solve the
10182 issues.&lt;/p&gt;
10183
10184 &lt;p&gt;I suspect these four missing features are not very hard to
10185 implement. After all, they are present in Ubuntu, so if we wanted to
10186 do this in Debian we would have a source.&lt;/p&gt;
10187
10188 &lt;ol&gt;
10189
10190 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
10191 are new packages available for upgrades, a icon in the KDE status bar
10192 indicate this, and clicking on it will activate the simple upgrade
10193 tool to handle it. I have no problem guiding both of my parents
10194 through the process over the phone. If a kernel reboot is required,
10195 this too is indicated by the status bars and the upgrade tool. Last
10196 time I checked, nothing with the same features was working in KDE in
10197 Debian.&lt;/li&gt;
10198
10199 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
10200 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
10201 currently have a handler for, it will ask the user if the system
10202 should search for a package that would add support for this MIME type,
10203 and if the user say yes, the APT sources will be searched for packages
10204 advertising the MIME type in their control file (visible in the
10205 Packages file in the APT archive). If one or more packages are found,
10206 it is a simple click of the mouse to add support for the missing mime
10207 type. If the package require the user to accept some non-free
10208 license, this is explained to the user. The entire process make it
10209 more clear to the user why something do not work in the browser, and
10210 make the chances higher for the user to blame the web page authors and
10211 not the browser for any missing features.&lt;/li&gt;
10212
10213 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
10214 handlers.&lt;/strong&gt; When the media players encounter a format or codec
10215 it is not supporting, a dialog pop up asking the user if the system
10216 should search for a package that would add support for it. This
10217 happen with things like MP3, Windows Media or H.264. The selection
10218 and installation procedure is very similar to the Firefox browser
10219 plugin handling. This is as far as I know implemented using a
10220 gstreamer hook. The end result is that the user easily get access to
10221 the codecs that are present from the APT archives available, while
10222 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
10223
10224 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
10225 displaying a text/plain file in my Debian browser, it will propose to
10226 start emacs to show it. If I remember correctly, when doing the same
10227 in Kunbutu it show the file as a text file in the browser. At least I
10228 know Opera will show text files within the browser. I much prefer the
10229 latter behaviour.&lt;/li&gt;
10230
10231 &lt;/ol&gt;
10232
10233 &lt;p&gt;There are other nice features as well, like the simplified suite
10234 upgrader, but given that I am the one mostly doing the dist-upgrade,
10235 it do not matter much.&lt;/p&gt;
10236
10237 &lt;p&gt;I really hope we could get these features in place for the next
10238 Debian release. It would require the coordinated effort of several
10239 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
10240 </description>
10241 </item>
10242
10243 <item>
10244 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
10245 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
10246 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
10247 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
10248 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
10249 site is build on Debian/Squeeze, and this platform was chosen because
10250 I am most familiar with Debian (being a Debian Developer for around 10
10251 years) because it is the latest stable Debian release which should get
10252 security support for a few years.&lt;/p&gt;
10253
10254 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
10255 that are missing in Debian at the moment. It would be great if these
10256 modules were added to the Debian archive, allowing anyone to set up
10257 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
10258 in their own country using only Debian packages. The list of modules
10259 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
10260 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
10261 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
10262 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
10263 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
10264 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
10265 easier in the future.&lt;/p&gt;
10266
10267 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
10268 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
10269 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
10270 with the responsibility of tracking security problems, which I really
10271 do not have time for.&lt;/p&gt;
10272 </description>
10273 </item>
10274
10275 <item>
10276 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
10277 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
10278 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
10279 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
10280 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
10281 posts have been in Norwegian the last few weeks, so here is a short
10282 update in English.&lt;/p&gt;
10283
10284 &lt;p&gt;The kids still keep me too busy to get much free software work
10285 done, but I did manage to organise a project to get a Norwegian port
10286 of the British service
10287 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
10288 and it has been running for a month now. The entire project has been
10289 organised by me and two others. Around Christmas we gathered sponsors
10290 to fund the development work. In January I drafted a contract with
10291 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
10292 and in February the development took place. Most of it involved
10293 converting the source to use GPS coordinates instead of British
10294 easting/northing, and the resulting code should be a lot easier to get
10295 running in any country by now. The Norwegian
10296 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
10297 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
10298 source and the source for administrative borders in Norway, and
10299 support for this had to be added/fixed.&lt;/p&gt;
10300
10301 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
10302 polishing the system before we announced it March 7th. The system is
10303 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
10304 problem reports in a few weeks. Soon we hope to announce the Android
10305 and iPhone versions making it even easier to report problems with the
10306 public infrastructure.&lt;/p&gt;
10307
10308 &lt;p&gt;Perhaps something to consider for those of you in countries without
10309 such service?&lt;/p&gt;
10310 </description>
10311 </item>
10312
10313 <item>
10314 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
10315 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
10316 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
10317 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
10318 <description>&lt;p&gt;The last few days I have looked at ways to track open security
10319 issues here at my work with the University of Oslo. My idea is that
10320 it should be possible to use the information about security issues
10321 available on the Internet, and check our locally
10322 maintained/distributed software against this information. It should
10323 allow us to verify that no known security issues are forgotten. The
10324 CVE database listing vulnerabilities seem like a great central point,
10325 and by using the package lists from Debian mapped to CVEs provided by
10326 the testing security team, I believed it should be possible to figure
10327 out which security holes were present in our free software
10328 collection.&lt;/p&gt;
10329
10330 &lt;p&gt;After reading up on the topic, it became obvious that the first
10331 building block is to be able to name software packages in a unique and
10332 consistent way across data sources. I considered several ways to do
10333 this, for example coming up with my own naming scheme like using URLs
10334 to project home pages or URLs to the Freshmeat entries, or using some
10335 existing naming scheme. And it seem like I am not the first one to
10336 come across this problem, as MITRE already proposed and implemented a
10337 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
10338 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
10339 software, hardware and other platform components. The CPE ids are
10340 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
10341 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
10342 issues for any CPE name. With this in place, all I need to do is to
10343 locate the CPE id for the software packages we use at the university.
10344 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
10345 NVD entry if a CVE for the package exist).&lt;/p&gt;
10346
10347 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
10348 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
10349 check out, one could look up
10350 &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
10351 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
10352 The most recent one is
10353 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
10354 and at the bottom of the NVD page for this vulnerability the complete
10355 list of affected versions is provided.&lt;/p&gt;
10356
10357 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
10358 for offline processing of issues. Using this dump, I&#39;ve written a
10359 small script taking a list of CPEs as input and list all CVEs
10360 affecting the packages represented by these CPEs. One give it CPEs
10361 with version numbers as specified above and get a list of open
10362 security issues out.&lt;/p&gt;
10363
10364 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
10365 information need to be high. For that to happen, I believe as many as
10366 possible need to use and contribute to the NVD database. I notice
10367 RHEL is providing
10368 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
10369 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
10370 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
10371
10372 &lt;p&gt;To get an idea about the quality for free software, I spent some
10373 time making it possible to compare the CVE database from Debian with
10374 the CVE database in NVD. The result look fairly good, but there are
10375 some inconsistencies in NVD (same software package having several
10376 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
10377 Debian believe are affected by a CVE). Hope to find time to improve
10378 the quality of NVD, but that require being able to get in touch with
10379 someone maintaining it. So far my three emails with questions and
10380 corrections have not seen any reply, but I hope contact can be
10381 established soon.&lt;/p&gt;
10382
10383 &lt;p&gt;An interesting application for CPEs is cross platform package
10384 mapping. It would be useful to know which packages in for example
10385 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
10386 this would be trivial if all linux distributions provided CPE entries
10387 for their packages.&lt;/p&gt;
10388 </description>
10389 </item>
10390
10391 <item>
10392 <title>Which module is loaded for a given PCI and USB device?</title>
10393 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
10394 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
10395 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
10396 <description>&lt;p&gt;In the
10397 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
10398 package in Debian, there is a script to report useful information
10399 about the running hardware for use when people report missing
10400 information. One part of this script that I find very useful when
10401 debugging hardware problems, is the part mapping loaded kernel module
10402 to the PCI device it claims. It allow me to quickly see if the kernel
10403 module I expect is driving the hardware I am struggling with. To see
10404 the output, make sure discover-data is installed and run
10405 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
10406 one of my machines like this:&lt;/p&gt;
10407
10408 &lt;pre&gt;
10409 loaded modules:
10410 10de:03eb i2c_nforce2
10411 10de:03f1 ohci_hcd
10412 10de:03f2 ehci_hcd
10413 10de:03f0 snd_hda_intel
10414 10de:03ec pata_amd
10415 10de:03f6 sata_nv
10416 1022:1103 k8temp
10417 109e:036e bttv
10418 109e:0878 snd_bt87x
10419 11ab:4364 sky2
10420 &lt;/pre&gt;
10421
10422 &lt;p&gt;The code in question look like this, slightly modified for
10423 readability and to drop the output to file descriptor 3:&lt;/p&gt;
10424
10425 &lt;pre&gt;
10426 if [ -d /sys/bus/pci/devices/ ] ; then
10427 echo loaded pci modules:
10428 (
10429 cd /sys/bus/pci/devices/
10430 for address in * ; do
10431 if [ -d &quot;$address/driver/module&quot; ] ; then
10432 module=`cd $address/driver/module ; pwd -P | xargs basename`
10433 if grep -q &quot;^$module &quot; /proc/modules ; then
10434 address=$(echo $address |sed s/0000://)
10435 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
10436 echo &quot;$id $module&quot;
10437 fi
10438 fi
10439 done
10440 )
10441 echo
10442 fi
10443 &lt;/pre&gt;
10444
10445 &lt;p&gt;Similar code could be used to extract USB device module
10446 mappings:&lt;/p&gt;
10447
10448 &lt;pre&gt;
10449 if [ -d /sys/bus/usb/devices/ ] ; then
10450 echo loaded usb modules:
10451 (
10452 cd /sys/bus/usb/devices/
10453 for address in * ; do
10454 if [ -d &quot;$address/driver/module&quot; ] ; then
10455 module=`cd $address/driver/module ; pwd -P | xargs basename`
10456 if grep -q &quot;^$module &quot; /proc/modules ; then
10457 address=$(echo $address |sed s/0000://)
10458 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
10459 if [ &quot;$id&quot; ] ; then
10460 echo &quot;$id $module&quot;
10461 fi
10462 fi
10463 fi
10464 done
10465 )
10466 echo
10467 fi
10468 &lt;/pre&gt;
10469
10470 &lt;p&gt;This might perhaps be something to include in other tools as
10471 well.&lt;/p&gt;
10472 </description>
10473 </item>
10474
10475 <item>
10476 <title>How to test if a laptop is working with Linux</title>
10477 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
10478 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
10479 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
10480 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
10481 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
10482 batch of computers will work with Linux. Every year for the last few
10483 years the university have organised shared bid of a few thousand
10484 computers, and this year HP won the bid. Two different desktops and
10485 five different laptops are on the list this year. We in the UNIX
10486 group want to know which one of these computers work well with RHEL
10487 and Ubuntu, the two Linux distributions we currently handle at the
10488 university.&lt;/p&gt;
10489
10490 &lt;p&gt;My test method is simple, and I share it here to get feedback and
10491 perhaps inspire others to test hardware as well. To test, I PXE
10492 install the OS version of choice, and log in as my normal user and run
10493 a few applications and plug in selected pieces of hardware. When
10494 something fail, I make a note about this in the test matrix and move
10495 on. If I have some spare time I try to report the bug to the OS
10496 vendor, but as I only have the machines for a short time, I rarely
10497 have the time to do this for all the problems I find.&lt;/p&gt;
10498
10499 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
10500 I perform on a new model.&lt;/p&gt;
10501
10502 &lt;ul&gt;
10503
10504 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
10505 and Ubuntu Maverik at the moment. If I feel like it, I also test with
10506 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
10507
10508 &lt;li&gt;Is X.org working? If the graphical login screen show up after
10509 installation, X.org is working.&lt;/li&gt;
10510
10511 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
10512 package mesa-utils on Ubuntu) and writing down the frames per second
10513 reported by the program.&lt;/li&gt;
10514
10515 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
10516 logging in, and if I can hear this the test is successful. If there
10517 are several audio exits on the machine, I try them all and check if
10518 the Gnome/KDE audio mixer can control where to send the sound. I
10519 normally test this by playing
10520 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
10521 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
10522
10523 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
10524 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
10525
10526 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
10527 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
10528
10529 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
10530 picture from the v4l device show up.&lt;/li&gt;
10531
10532 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
10533 any bluetooth devices are discovered. In my office, I normally see a
10534 few.&lt;/li&gt;
10535
10536 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
10537 memory modules lying around, and stick them in and see if Gnome/KDE
10538 notice this.&lt;/li&gt;
10539
10540 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
10541 special button work, and if the laptop continue to work after
10542 resume.&lt;/li&gt;
10543
10544 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
10545 adjusting background light, switching on/off external video output,
10546 switching on/off wifi, bluetooth, etc? The set of buttons differ from
10547 laptop to laptop, so I just write down which are working and which are
10548 not.&lt;/li&gt;
10549
10550 &lt;li&gt;Some laptops have smart card readers, finger print readers,
10551 acceleration sensors etc. I rarely test these, as I do not know how
10552 to quickly test if they are working or not, so I only document their
10553 existence.&lt;/li&gt;
10554
10555 &lt;/ul&gt;
10556
10557 &lt;p&gt;By now I suspect you are really curious what the test results are
10558 for the HP machines I am testing. I&#39;m not done yet, so I will report
10559 the test results later. For now I can report that HP 8100 Elite work
10560 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
10561 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
10562 can see, I have most machines left to test. One interesting
10563 observation is that Ubuntu Lucid has almost twice the frame rate than
10564 RHEL6 with glxgears. No idea why.&lt;/p&gt;
10565 </description>
10566 </item>
10567
10568 <item>
10569 <title>Some thoughts on BitCoins</title>
10570 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
10571 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
10572 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
10573 <description>&lt;p&gt;As I continue to explore
10574 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
10575 what properties the system have, and how it will be affected by laws
10576 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
10577
10578 &lt;p&gt;One interesting thing to note is that since the transactions are
10579 verified using a peer to peer network, all details about a transaction
10580 is known to everyone. This means that if a BitCoin address has been
10581 published like I did with mine in my initial post about BitCoin, it is
10582 possible for everyone to see how many BitCoins have been transfered to
10583 that address. There is even a web service to look at the details for
10584 all transactions. There I can see that my address
10585 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
10586 have received 16.06 Bitcoin, the
10587 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
10588 address of Simon Phipps have received 181.97 BitCoin and the address
10589 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
10590 of EFF have received 2447.38 BitCoins so far. Thank you to each and
10591 every one of you that donated bitcoins to support my activity. The
10592 fact that anyone can see how much money was transfered to a given
10593 address make it more obvious why the BitCoin community recommend to
10594 generate and hand out a new address for each transaction. I&#39;m told
10595 there is no way to track which addresses belong to a given person or
10596 organisation without the person or organisation revealing it
10597 themselves, as Simon, EFF and I have done.&lt;/p&gt;
10598
10599 &lt;p&gt;In Norway, and in most other countries, there are laws and
10600 regulations limiting how much money one can transfer across the border
10601 without declaring it. There are money laundering, tax and accounting
10602 laws and regulations I would expect to apply to the use of BitCoin.
10603 If the Skolelinux foundation
10604 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
10605 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
10606 normal bank transfers like EFF is doing, how should this be accounted?
10607 Given that it is impossible to know if money can cross the border or
10608 not, should everything or nothing be declared? What exchange rate
10609 should be used when calculating taxes? Would receivers have to pay
10610 income tax if the foundation were to pay Skolelinux contributors in
10611 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
10612
10613 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
10614 accepted by a lot of users. It must be possible to get easy access to
10615 the currency (as a wage or using currency exchanges), and it must be
10616 easy to spend it. At the moment BitCoin seem fairly easy to get
10617 access to, but there are very few places to spend it. I am not really
10618 a regular user of any of the vendor types currently accepting BitCoin,
10619 so I wonder when my kind of shop would start accepting BitCoins. I
10620 would like to buy electronics, travels and subway tickets, not herbs
10621 and books. :) The currency is young, and this will improve over time
10622 if it become popular, but I suspect regular banks will start to lobby
10623 to get BitCoin declared illegal if it become popular. I&#39;m sure they
10624 will claim it is helping fund terrorism and money laundering (which
10625 probably would be true, as is any currency in existence), but I
10626 believe the problems should be solved elsewhere and not by blaming
10627 currencies.&lt;/p&gt;
10628
10629 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
10630 CPU intensive process that depend on a bit of luck as well (as one is
10631 competing against all the other miners currently spending CPU cycles
10632 to see which one get the next lump of cash). The &quot;winner&quot; get 50
10633 BitCoin when this happen. Yesterday I came across the obvious way to
10634 join forces to increase ones changes of getting at least some coins,
10635 by coordinating the work on mining BitCoins across several machines
10636 and people, and sharing the result if one is lucky and get the 50
10637 BitCoins. Check out
10638 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
10639 if this sounds interesting. I have not had time to try to set up a
10640 machine to participate there yet, but have seen that running on ones
10641 own for a few days have not yield any BitCoins througth mining
10642 yet.&lt;/p&gt;
10643
10644 &lt;p&gt;Update 2010-12-15: Found an &lt;a
10645 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
10646 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
10647 it was interesting to read. The arguments presented seem to be
10648 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
10649 </description>
10650 </item>
10651
10652 <item>
10653 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
10654 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
10655 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
10656 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
10657 <description>&lt;p&gt;With this weeks lawless
10658 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
10659 attacks&lt;/a&gt; on Wikileak and
10660 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
10661 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
10662 not be trusted to handle money transactions.
10663 A blog post from
10664 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
10665 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
10666 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
10667 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
10668 some help from my friend to get it all running, and he even handed me
10669 some bitcoins to get started. I even donated a few bitcoins to Simon
10670 for helping me remember BitCoin.&lt;/p&gt;
10671
10672 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
10673 crypto-currency, decentralised and handled using peer-to-peer
10674 networks. It allows anonymous transactions and prohibits central
10675 control over the transactions, making it impossible for governments
10676 and companies alike to block donations and other transactions. The
10677 source is free software, and while the key dependency wxWidgets 2.9
10678 for the graphical user interface is missing in Debian, the command
10679 line client builds just fine. Hopefully Jonas
10680 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
10681 Debian&lt;/a&gt; soon.&lt;/p&gt;
10682
10683 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
10684 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
10685 bitcoins&lt;/a&gt; when selling services and goods, and there are even
10686 currency &quot;stock&quot; markets where the exchange rate is decided. There
10687 are not many users so far, but the concept seems promising. If you
10688 want to get started and lack a friend with any bitcoins to spare,
10689 you can even get
10690 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
10691 bitcoin at the time of writing). Use
10692 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
10693 on the current exchange rates.&lt;/p&gt;
10694
10695 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
10696 machines. If you want to support my activity, please send Bitcoin
10697 donations to the address
10698 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
10699 </description>
10700 </item>
10701
10702 <item>
10703 <title>Why isn&#39;t Debian Edu using VLC?</title>
10704 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
10705 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
10706 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
10707 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
10708 presented, and the winner among the multimedia player were VLC.
10709 Personally, I like VLC, and it is my player of choice when I first try
10710 to play a video file or stream. Only if VLC fail will I drag out
10711 gmplayer to see if it can do better. The reason is mostly the failure
10712 model and trust. When VLC fail, it normally pop up a error message
10713 reporting the problem. When mplayer fail, it normally segfault or
10714 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
10715
10716 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
10717 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
10718 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
10719 plugin to play web videos seamlessly, and the VLC browser plugin is
10720 not very good. For example, it lack in-line control buttons, so there
10721 is no way for the user to pause the video. Also, when I
10722 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
10723 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
10724 failed on several video pages where mplayer based plugins worked. If
10725 the browser plugin for VLC was as good as the gecko-mediaplayer
10726 package (which uses mplayer), we would switch.&lt;/P&gt;
10727
10728 &lt;p&gt;While VLC is a good player, its user interface is slightly
10729 annoying. The most annoying feature is its inconsistent use of
10730 keyboard shortcuts. When the player is in full screen mode, its
10731 shortcuts are different from when it is playing the video in a window.
10732 For example, space only work as pause when in full screen mode. I
10733 wish it had consisten shortcuts and that space also would work when in
10734 window mode. Another nice shortcut in gmplayer is [enter] to restart
10735 the current video. It is very nice when playing short videos from the
10736 web and want to restart it when new people arrive to have a look at
10737 what is going on.&lt;/p&gt;
10738 </description>
10739 </item>
10740
10741 <item>
10742 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
10743 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
10744 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</guid>
10745 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
10746 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
10747 upgrade testing of the
10748 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
10749 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
10750 This seem like a very good idea, so I adjusted by test scripts and
10751 can now present the updated result from today:&lt;/p&gt;
10752
10753 &lt;p&gt;This is for Gnome:&lt;/p&gt;
10754
10755 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10756
10757 &lt;blockquote&gt;&lt;p&gt;
10758 apache2.2-bin
10759 aptdaemon
10760 baobab
10761 binfmt-support
10762 browser-plugin-gnash
10763 cheese-common
10764 cli-common
10765 cups-pk-helper
10766 dmz-cursor-theme
10767 empathy
10768 empathy-common
10769 freedesktop-sound-theme
10770 freeglut3
10771 gconf-defaults-service
10772 gdm-themes
10773 gedit-plugins
10774 geoclue
10775 geoclue-hostip
10776 geoclue-localnet
10777 geoclue-manual
10778 geoclue-yahoo
10779 gnash
10780 gnash-common
10781 gnome
10782 gnome-backgrounds
10783 gnome-cards-data
10784 gnome-codec-install
10785 gnome-core
10786 gnome-desktop-environment
10787 gnome-disk-utility
10788 gnome-screenshot
10789 gnome-search-tool
10790 gnome-session-canberra
10791 gnome-system-log
10792 gnome-themes-extras
10793 gnome-themes-more
10794 gnome-user-share
10795 gstreamer0.10-fluendo-mp3
10796 gstreamer0.10-tools
10797 gtk2-engines
10798 gtk2-engines-pixbuf
10799 gtk2-engines-smooth
10800 hamster-applet
10801 libapache2-mod-dnssd
10802 libapr1
10803 libaprutil1
10804 libaprutil1-dbd-sqlite3
10805 libaprutil1-ldap
10806 libart2.0-cil
10807 libboost-date-time1.42.0
10808 libboost-python1.42.0
10809 libboost-thread1.42.0
10810 libchamplain-0.4-0
10811 libchamplain-gtk-0.4-0
10812 libcheese-gtk18
10813 libclutter-gtk-0.10-0
10814 libcryptui0
10815 libdiscid0
10816 libelf1
10817 libepc-1.0-2
10818 libepc-common
10819 libepc-ui-1.0-2
10820 libfreerdp-plugins-standard
10821 libfreerdp0
10822 libgconf2.0-cil
10823 libgdata-common
10824 libgdata7
10825 libgdu-gtk0
10826 libgee2
10827 libgeoclue0
10828 libgexiv2-0
10829 libgif4
10830 libglade2.0-cil
10831 libglib2.0-cil
10832 libgmime2.4-cil
10833 libgnome-vfs2.0-cil
10834 libgnome2.24-cil
10835 libgnomepanel2.24-cil
10836 libgpod-common
10837 libgpod4
10838 libgtk2.0-cil
10839 libgtkglext1
10840 libgtksourceview2.0-common
10841 libmono-addins-gui0.2-cil
10842 libmono-addins0.2-cil
10843 libmono-cairo2.0-cil
10844 libmono-corlib2.0-cil
10845 libmono-i18n-west2.0-cil
10846 libmono-posix2.0-cil
10847 libmono-security2.0-cil
10848 libmono-sharpzip2.84-cil
10849 libmono-system2.0-cil
10850 libmtp8
10851 libmusicbrainz3-6
10852 libndesk-dbus-glib1.0-cil
10853 libndesk-dbus1.0-cil
10854 libopal3.6.8
10855 libpolkit-gtk-1-0
10856 libpt2.6.7
10857 libpython2.6
10858 librpm1
10859 librpmio1
10860 libsdl1.2debian
10861 libsrtp0
10862 libssh-4
10863 libtelepathy-farsight0
10864 libtelepathy-glib0
10865 libtidy-0.99-0
10866 media-player-info
10867 mesa-utils
10868 mono-2.0-gac
10869 mono-gac
10870 mono-runtime
10871 nautilus-sendto
10872 nautilus-sendto-empathy
10873 p7zip-full
10874 pkg-config
10875 python-aptdaemon
10876 python-aptdaemon-gtk
10877 python-axiom
10878 python-beautifulsoup
10879 python-bugbuddy
10880 python-clientform
10881 python-coherence
10882 python-configobj
10883 python-crypto
10884 python-cupshelpers
10885 python-elementtree
10886 python-epsilon
10887 python-evolution
10888 python-feedparser
10889 python-gdata
10890 python-gdbm
10891 python-gst0.10
10892 python-gtkglext1
10893 python-gtksourceview2
10894 python-httplib2
10895 python-louie
10896 python-mako
10897 python-markupsafe
10898 python-mechanize
10899 python-nevow
10900 python-notify
10901 python-opengl
10902 python-openssl
10903 python-pam
10904 python-pkg-resources
10905 python-pyasn1
10906 python-pysqlite2
10907 python-rdflib
10908 python-serial
10909 python-tagpy
10910 python-twisted-bin
10911 python-twisted-conch
10912 python-twisted-core
10913 python-twisted-web
10914 python-utidylib
10915 python-webkit
10916 python-xdg
10917 python-zope.interface
10918 remmina
10919 remmina-plugin-data
10920 remmina-plugin-rdp
10921 remmina-plugin-vnc
10922 rhythmbox-plugin-cdrecorder
10923 rhythmbox-plugins
10924 rpm-common
10925 rpm2cpio
10926 seahorse-plugins
10927 shotwell
10928 software-center
10929 system-config-printer-udev
10930 telepathy-gabble
10931 telepathy-mission-control-5
10932 telepathy-salut
10933 tomboy
10934 totem
10935 totem-coherence
10936 totem-mozilla
10937 totem-plugins
10938 transmission-common
10939 xdg-user-dirs
10940 xdg-user-dirs-gtk
10941 xserver-xephyr
10942 &lt;/p&gt;&lt;/blockquote&gt;
10943
10944 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10945
10946 &lt;blockquote&gt;&lt;p&gt;
10947 cheese
10948 ekiga
10949 eog
10950 epiphany-extensions
10951 evolution-exchange
10952 fast-user-switch-applet
10953 file-roller
10954 gcalctool
10955 gconf-editor
10956 gdm
10957 gedit
10958 gedit-common
10959 gnome-games
10960 gnome-games-data
10961 gnome-nettool
10962 gnome-system-tools
10963 gnome-themes
10964 gnuchess
10965 gucharmap
10966 guile-1.8-libs
10967 libavahi-ui0
10968 libdmx1
10969 libgalago3
10970 libgtk-vnc-1.0-0
10971 libgtksourceview2.0-0
10972 liblircclient0
10973 libsdl1.2debian-alsa
10974 libspeexdsp1
10975 libsvga1
10976 rhythmbox
10977 seahorse
10978 sound-juicer
10979 system-config-printer
10980 totem-common
10981 transmission-gtk
10982 vinagre
10983 vino
10984 &lt;/p&gt;&lt;/blockquote&gt;
10985
10986 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10987
10988 &lt;blockquote&gt;&lt;p&gt;
10989 gstreamer0.10-gnomevfs
10990 &lt;/p&gt;&lt;/blockquote&gt;
10991
10992 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10993
10994 &lt;blockquote&gt;&lt;p&gt;
10995 [nothing]
10996 &lt;/p&gt;&lt;/blockquote&gt;
10997
10998 &lt;p&gt;This is for KDE:&lt;/p&gt;
10999
11000 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11001
11002 &lt;blockquote&gt;&lt;p&gt;
11003 ksmserver
11004 &lt;/p&gt;&lt;/blockquote&gt;
11005
11006 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
11007
11008 &lt;blockquote&gt;&lt;p&gt;
11009 kwin
11010 network-manager-kde
11011 &lt;/p&gt;&lt;/blockquote&gt;
11012
11013 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11014
11015 &lt;blockquote&gt;&lt;p&gt;
11016 arts
11017 dolphin
11018 freespacenotifier
11019 google-gadgets-gst
11020 google-gadgets-xul
11021 kappfinder
11022 kcalc
11023 kcharselect
11024 kde-core
11025 kde-plasma-desktop
11026 kde-standard
11027 kde-window-manager
11028 kdeartwork
11029 kdeartwork-emoticons
11030 kdeartwork-style
11031 kdeartwork-theme-icon
11032 kdebase
11033 kdebase-apps
11034 kdebase-workspace
11035 kdebase-workspace-bin
11036 kdebase-workspace-data
11037 kdeeject
11038 kdelibs
11039 kdeplasma-addons
11040 kdeutils
11041 kdewallpapers
11042 kdf
11043 kfloppy
11044 kgpg
11045 khelpcenter4
11046 kinfocenter
11047 konq-plugins-l10n
11048 konqueror-nsplugins
11049 kscreensaver
11050 kscreensaver-xsavers
11051 ktimer
11052 kwrite
11053 libgle3
11054 libkde4-ruby1.8
11055 libkonq5
11056 libkonq5-templates
11057 libnetpbm10
11058 libplasma-ruby
11059 libplasma-ruby1.8
11060 libqt4-ruby1.8
11061 marble-data
11062 marble-plugins
11063 netpbm
11064 nuvola-icon-theme
11065 plasma-dataengines-workspace
11066 plasma-desktop
11067 plasma-desktopthemes-artwork
11068 plasma-runners-addons
11069 plasma-scriptengine-googlegadgets
11070 plasma-scriptengine-python
11071 plasma-scriptengine-qedje
11072 plasma-scriptengine-ruby
11073 plasma-scriptengine-webkit
11074 plasma-scriptengines
11075 plasma-wallpapers-addons
11076 plasma-widget-folderview
11077 plasma-widget-networkmanagement
11078 ruby
11079 sweeper
11080 update-notifier-kde
11081 xscreensaver-data-extra
11082 xscreensaver-gl
11083 xscreensaver-gl-extra
11084 xscreensaver-screensaver-bsod
11085 &lt;/p&gt;&lt;/blockquote&gt;
11086
11087 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11088
11089 &lt;blockquote&gt;&lt;p&gt;
11090 ark
11091 google-gadgets-common
11092 google-gadgets-qt
11093 htdig
11094 kate
11095 kdebase-bin
11096 kdebase-data
11097 kdepasswd
11098 kfind
11099 klipper
11100 konq-plugins
11101 konqueror
11102 ksysguard
11103 ksysguardd
11104 libarchive1
11105 libcln6
11106 libeet1
11107 libeina-svn-06
11108 libggadget-1.0-0b
11109 libggadget-qt-1.0-0b
11110 libgps19
11111 libkdecorations4
11112 libkephal4
11113 libkonq4
11114 libkonqsidebarplugin4a
11115 libkscreensaver5
11116 libksgrd4
11117 libksignalplotter4
11118 libkunitconversion4
11119 libkwineffects1a
11120 libmarblewidget4
11121 libntrack-qt4-1
11122 libntrack0
11123 libplasma-geolocation-interface4
11124 libplasmaclock4a
11125 libplasmagenericshell4
11126 libprocesscore4a
11127 libprocessui4a
11128 libqalculate5
11129 libqedje0a
11130 libqtruby4shared2
11131 libqzion0a
11132 libruby1.8
11133 libscim8c2a
11134 libsmokekdecore4-3
11135 libsmokekdeui4-3
11136 libsmokekfile3
11137 libsmokekhtml3
11138 libsmokekio3
11139 libsmokeknewstuff2-3
11140 libsmokeknewstuff3-3
11141 libsmokekparts3
11142 libsmokektexteditor3
11143 libsmokekutils3
11144 libsmokenepomuk3
11145 libsmokephonon3
11146 libsmokeplasma3
11147 libsmokeqtcore4-3
11148 libsmokeqtdbus4-3
11149 libsmokeqtgui4-3
11150 libsmokeqtnetwork4-3
11151 libsmokeqtopengl4-3
11152 libsmokeqtscript4-3
11153 libsmokeqtsql4-3
11154 libsmokeqtsvg4-3
11155 libsmokeqttest4-3
11156 libsmokeqtuitools4-3
11157 libsmokeqtwebkit4-3
11158 libsmokeqtxml4-3
11159 libsmokesolid3
11160 libsmokesoprano3
11161 libtaskmanager4a
11162 libtidy-0.99-0
11163 libweather-ion4a
11164 libxklavier16
11165 libxxf86misc1
11166 okteta
11167 oxygencursors
11168 plasma-dataengines-addons
11169 plasma-scriptengine-superkaramba
11170 plasma-widget-lancelot
11171 plasma-widgets-addons
11172 plasma-widgets-workspace
11173 polkit-kde-1
11174 ruby1.8
11175 systemsettings
11176 update-notifier-common
11177 &lt;/p&gt;&lt;/blockquote&gt;
11178
11179 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
11180 aptitude a bit more similar, but there are still quite a lott of
11181 differences. I have no idea what packages should be installed after
11182 the upgrade, but hope those that do can have a look.&lt;/p&gt;
11183 </description>
11184 </item>
11185
11186 <item>
11187 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
11188 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
11189 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
11190 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
11191 <description>&lt;p&gt;Most of the computers in use by the
11192 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
11193 are virtual machines. And they have been Xen machines running on a
11194 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
11195 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
11196 bit harder that it could have been, because we set up the Xen virtual
11197 machines to get the virtual partitions from LVM, which as far as I
11198 know is not supported by KVM. So to migrate, we had to convert
11199 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
11200
11201 &lt;p&gt;I found
11202 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
11203 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
11204 migration. It uses qemu-img from the qemu package to make the disk
11205 image, parted to partition it, losetup and kpartx to present the disk
11206 image partions as devices, and dd to copy the data. I NFS mounted the
11207 new servers storage area on the old server to do the migration.&lt;/p&gt;
11208
11209 &lt;pre&gt;
11210 #!/bin/sh
11211
11212 # Based on
11213 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
11214
11215 set -e
11216 set -x
11217
11218 if [ -z &quot;$1&quot; ] ; then
11219 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
11220 exit 1
11221 else
11222 host=&quot;$1&quot;
11223 fi
11224
11225 if [ ! -e /dev/vg_data/$host-disk ] ; then
11226 echo &quot;error: unable to find LVM volume for $host&quot;
11227 exit 1
11228 fi
11229
11230 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
11231 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
11232 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
11233 totalsize=$(( ( $disksize + $swapsize ) ))
11234
11235 img=$host.img
11236 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
11237 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
11238
11239 parted $img mklabel msdos
11240 parted $img mkpart primary linux-swap 0 $disksize
11241 parted $img mkpart primary ext2 $disksize $totalsize
11242 parted $img set 1 boot on
11243
11244 modprobe dm-mod
11245 losetup /dev/loop0 $img
11246 kpartx -a /dev/loop0
11247
11248 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
11249 fsck.ext3 -f /dev/mapper/loop0p1 || true
11250 mkswap /dev/mapper/loop0p2
11251
11252 kpartx -d /dev/loop0
11253 losetup -d /dev/loop0
11254 &lt;/pre&gt;
11255
11256 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
11257 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
11258
11259 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
11260 the new disk image attached, installed grub-pc and linux-image-686 and
11261 set up grub to boot from the disk image. After this, the KVM machines
11262 seem to work just fine.&lt;/p&gt;
11263 </description>
11264 </item>
11265
11266 <item>
11267 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
11268 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
11269 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
11270 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
11271 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
11272 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
11273 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
11274 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
11275
11276 &lt;p&gt;I still do not know what a correct migration should look like, so I
11277 report any differences between apt and aptitude and hope someone else
11278 can see if anything should be changed.&lt;/p&gt;
11279
11280 &lt;p&gt;This is for Gnome:&lt;/p&gt;
11281
11282 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11283
11284 &lt;blockquote&gt;&lt;p&gt;
11285 apache2.2-bin aptdaemon at-spi baobab binfmt-support
11286 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
11287 dmz-cursor-theme empathy empathy-common finger
11288 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
11289 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
11290 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
11291 gnome-cards-data gnome-codec-install gnome-core
11292 gnome-desktop-environment gnome-disk-utility gnome-screenshot
11293 gnome-search-tool gnome-session-canberra gnome-spell
11294 gnome-system-log gnome-themes-extras gnome-themes-more
11295 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
11296 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
11297 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
11298 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
11299 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
11300 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
11301 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
11302 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
11303 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
11304 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
11305 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
11306 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
11307 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
11308 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
11309 libgtk2.0-cil libgtkglext1 libgtksourceview-common
11310 libgtksourceview2.0-common libmono-addins-gui0.2-cil
11311 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
11312 libmono-i18n-west2.0-cil libmono-posix2.0-cil
11313 libmono-security2.0-cil libmono-sharpzip2.84-cil
11314 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
11315 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
11316 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
11317 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
11318 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
11319 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
11320 libxalan2-java libxerces2-java media-player-info mesa-utils
11321 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
11322 nautilus-sendto-empathy openoffice.org-writer2latex
11323 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
11324 python-aptdaemon python-aptdaemon-gtk python-axiom
11325 python-beautifulsoup python-bugbuddy python-clientform
11326 python-coherence python-configobj python-crypto python-cupshelpers
11327 python-cupsutils python-eggtrayicon python-elementtree
11328 python-epsilon python-evolution python-feedparser python-gdata
11329 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
11330 python-gtksourceview2 python-httplib2 python-louie python-mako
11331 python-markupsafe python-mechanize python-nevow python-notify
11332 python-opengl python-openssl python-pam python-pkg-resources
11333 python-pyasn1 python-pysqlite2 python-rdflib python-serial
11334 python-tagpy python-twisted-bin python-twisted-conch
11335 python-twisted-core python-twisted-web python-utidylib python-webkit
11336 python-xdg python-zope.interface remmina remmina-plugin-data
11337 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
11338 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
11339 software-center svgalibg1 system-config-printer-udev
11340 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
11341 totem totem-coherence totem-mozilla totem-plugins
11342 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
11343 zip
11344 &lt;/p&gt;&lt;/blockquote&gt;
11345
11346 Installed using apt-get, removed with aptitude
11347
11348 &lt;blockquote&gt;&lt;p&gt;
11349 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
11350 epiphany-extensions epiphany-gecko evolution-exchange
11351 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
11352 gedit-common gnome-app-install gnome-games gnome-games-data
11353 gnome-nettool gnome-system-tools gnome-themes gnome-utils
11354 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
11355 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
11356 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
11357 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
11358 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
11359 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
11360 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
11361 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
11362 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
11363 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
11364 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
11365 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
11366 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
11367 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
11368 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
11369 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
11370 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
11371 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
11372 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
11373 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
11374 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
11375 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
11376 sound-juicer swfdec-gnome system-config-printer totem-common
11377 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
11378 &lt;/p&gt;&lt;/blockquote&gt;
11379
11380 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11381
11382 &lt;blockquote&gt;&lt;p&gt;
11383 gstreamer0.10-gnomevfs
11384 &lt;/p&gt;&lt;/blockquote&gt;
11385
11386 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11387
11388 &lt;blockquote&gt;&lt;p&gt;
11389 [nothing]
11390 &lt;/p&gt;&lt;/blockquote&gt;
11391
11392 &lt;p&gt;This is for KDE:&lt;/p&gt;
11393
11394 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11395
11396 &lt;blockquote&gt;&lt;p&gt;
11397 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
11398 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
11399 ghostscript-x git gnome-audio gnugo granatier gs-common
11400 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
11401 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
11402 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
11403 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
11404 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
11405 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
11406 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
11407 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
11408 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
11409 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
11410 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
11411 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
11412 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
11413 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
11414 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
11415 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
11416 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
11417 libkrossui4 libmailtools-perl libmime-tools-perl
11418 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
11419 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
11420 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
11421 lirc luatex marble networkstatus noatun-plugins
11422 openoffice.org-writer2latex palapeli palapeli-data parley
11423 parley-data poster psutils pulseaudio pulseaudio-esound-compat
11424 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
11425 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
11426 ttf-sazanami-gothic
11427 &lt;/p&gt;&lt;/blockquote&gt;
11428
11429 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
11430
11431 &lt;blockquote&gt;&lt;p&gt;
11432 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
11433 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
11434 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
11435 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
11436 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
11437 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
11438 kitchensync kiten kjumpingcube klatin klettres klickety klines
11439 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
11440 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
11441 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
11442 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
11443 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
11444 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
11445 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
11446 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
11447 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
11448 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
11449 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
11450 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
11451 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
11452 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
11453 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
11454 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
11455 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
11456 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
11457 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
11458 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
11459 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
11460 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
11461 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
11462 mpeglib network-manager-kde noatun pmount tex-common texlive-base
11463 texlive-common texlive-doc-base texlive-fonts-recommended tidy
11464 ttf-dustin ttf-kochi-gothic ttf-sjfonts
11465 &lt;/p&gt;&lt;/blockquote&gt;
11466
11467 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11468
11469 &lt;blockquote&gt;&lt;p&gt;
11470 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
11471 kdeartwork kdebase kdebase-apps kdebase-workspace
11472 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
11473 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
11474 netpbm plasma-widget-folderview plasma-widget-networkmanagement
11475 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
11476 xscreensaver-screensaver-bsod
11477 &lt;/p&gt;&lt;/blockquote&gt;
11478
11479 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11480
11481 &lt;blockquote&gt;&lt;p&gt;
11482 kdebase-bin konq-plugins konqueror
11483 &lt;/p&gt;&lt;/blockquote&gt;
11484 </description>
11485 </item>
11486
11487 <item>
11488 <title>Gnash buildbot slave and Debian kfreebsd</title>
11489 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
11490 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
11491 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
11492 <description>&lt;p&gt;Answering
11493 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
11494 call from the Gnash project&lt;/a&gt; for
11495 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
11496 current source, I have set up a virtual KVM machine on the Debian
11497 Edu/Skolelinux virtualization host to test the git source on
11498 Debian/Squeeze. I hope this can help the developers in getting new
11499 releases out more often.&lt;/p&gt;
11500
11501 &lt;p&gt;As the developers want less main-stream build platforms tested to,
11502 I have considered setting up a &lt;a
11503 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
11504 machine as well. I have also considered using the kfreebsd
11505 architecture in Debian as a file server in NUUG to get access to the 5
11506 TB zfs volume we currently use to store DV video. Because of this, I
11507 finally got around to do a test installation of Debian/Squeeze with
11508 kfreebsd. Installation went fairly smooth, thought I noticed some
11509 visual glitches in the cdebconf dialogs (black cursor left on the
11510 screen at random locations). Have not gotten very far with the
11511 testing. Noticed cfdisk did not work, but fdisk did so it was not a
11512 fatal problem. Have to spend some more time on it to see if it is
11513 useful as a file server for NUUG. Will try to find time to set up a
11514 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
11515 </description>
11516 </item>
11517
11518 <item>
11519 <title>Debian in 3D</title>
11520 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
11521 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
11522 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
11523 <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;
11524
11525 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
11526 3D linked in from
11527 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
11528 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
11529 </description>
11530 </item>
11531
11532 <item>
11533 <title>Software updates 2010-10-24</title>
11534 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
11535 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
11536 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
11537 <description>&lt;p&gt;Some updates.&lt;/p&gt;
11538
11539 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
11540 raise money for the project is going well. The lower limit of 10
11541 signers was reached in 24 hours, and so far 13 people have signed it.
11542 More signers and more funding is most welcome, and I am really curious
11543 how far we can get before the time limit of December 24 is reached.
11544 :)&lt;/p&gt;
11545
11546 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
11547 about what appear to be a great code coverage tool capable of
11548 generating code coverage stats without any changes to the source code.
11549 It is called
11550 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
11551 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
11552 It is missing in Debian, but the git source built just fine in Squeeze
11553 after I installed libelf-dev, libdwarf-dev, pkg-config and
11554 libglib2.0-dev. Failed to build in Lenny, but suspect that is
11555 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
11556
11557 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
11558 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
11559 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
11560 alpha test release of the Squeeze based Debian Edu /
11561 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
11562 release. Give it a try if you need a complete linux solution for your
11563 school, including central infrastructure server, workstations, thin
11564 client servers and diskless workstations. A nice touch added
11565 yesterday is RDP support on the thin client servers, for windows
11566 clients to get a Linux desktop on request.&lt;/p&gt;
11567 </description>
11568 </item>
11569
11570 <item>
11571 <title>Some notes on Flash in Debian and Debian Edu</title>
11572 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
11573 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
11574 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
11575 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
11576 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
11577 second most popular used package that is missing in Debian. The sixth
11578 most popular is flashplayer-mozilla. This is a clear indication that
11579 working flash is important for Debian users. Around 10 percent of the
11580 users submitting data to popcon.debian.org have this package
11581 installed.&lt;/p&gt;
11582
11583 &lt;p&gt;In the report written by Lars Risan in August 2008
11584&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
11585 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
11586 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
11587 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
11588 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
11589 web sites require Flash to work, and lacking working Flash support in
11590 the web browser and the problems with installing it was perceived as a
11591 good reason to stay with Windows.&lt;/p&gt;
11592
11593 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
11594 said to be the retarded cousin that did not really understand
11595 everything you told him but could work fairly well. This was a
11596 comment regarding the problems Linux have with proprietary formats and
11597 non-standard web pages, and is sad because it exposes a fairly common
11598 understanding of whose fault it is if web pages that only work in for
11599 example Internet Explorer 6 fail to work on Firefox, and funny because
11600 it explain very well how annoying it is for users when Linux
11601 distributions do not work with the documents they receive or the web
11602 pages they want to visit.&lt;/p&gt;
11603
11604 &lt;p&gt;This is part of the reason why I believe it is important for Debian
11605 and Debian Edu to have a well working Flash implementation in the
11606 distribution, to get at least popular sites as Youtube and Google
11607 Video to working out of the box. For Squeeze, Debian have the chance
11608 to include the latest version of Gnash that will make this happen, as
11609 the new release 0.8.8 was published a few weeks ago and is resting in
11610 unstable. The new version work with more sites that version 0.8.7.
11611 The Gnash maintainers have asked for a freeze exception, but the
11612 release team have not had time to reply to it yet. I hope they agree
11613 with me that Flash is important for the Debian desktop users, and thus
11614 accept the new package into Squeeze.&lt;/p&gt;
11615 </description>
11616 </item>
11617
11618 <item>
11619 <title>Circular package dependencies harms apt recovery</title>
11620 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
11621 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
11622 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
11623 <description>&lt;p&gt;I discovered this while doing
11624 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
11625 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
11626 in Debian still got circular dependencies, and it is often claimed
11627 that apt and aptitude should be able to handle this just fine, but
11628 some times these dependency loops causes apt to fail.&lt;/p&gt;
11629
11630 &lt;p&gt;An example is from todays
11631 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
11632 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
11633 causes perl-modules to fail to upgrade. The cause is simple. If a
11634 package fail to unpack, then only part of packages with the circular
11635 dependency might end up being unpacked when unpacking aborts, and the
11636 ones already unpacked will fail to configure in the recovery phase
11637 because its dependencies are unavailable.&lt;/p&gt;
11638
11639 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
11640
11641 &lt;blockquote&gt;&lt;pre&gt;
11642 dpkg: dependency problems prevent configuration of perl-modules:
11643 perl-modules depends on perl (&gt;= 5.10.1-1); however:
11644 Version of perl on system is 5.10.0-19lenny2.
11645 dpkg: error processing perl-modules (--configure):
11646 dependency problems - leaving unconfigured
11647 &lt;/pre&gt;&lt;/blockquote&gt;
11648
11649 &lt;p&gt;The perl/perl-modules circular dependency is already
11650 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
11651 hopefully be solved as soon as possible, but it is not the only one,
11652 and each one of these loops in the dependency tree can cause similar
11653 failures. Of course, they only occur when there are bugs in other
11654 packages causing the unpacking to fail, but it is rather nasty when
11655 the failure of one package causes the problem to become worse because
11656 of dependency loops.&lt;/p&gt;
11657
11658 &lt;p&gt;Thanks to
11659 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
11660 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
11661 dependencies
11662 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
11663 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
11664
11665 &lt;p&gt;Todays testing also exposed a bug in
11666 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
11667 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
11668 apt-get and aptitude, the latter possibly caused by some circular
11669 dependency. Reported both to BTS to try to get someone to look at
11670 it.&lt;/p&gt;
11671 </description>
11672 </item>
11673
11674 <item>
11675 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
11676 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
11677 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
11678 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
11679 <description>&lt;p&gt;This is a
11680 &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;
11681 on my
11682 &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
11683 work&lt;/a&gt; on
11684 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
11685 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
11686
11687 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
11688 LDAP objects, I have had a look at how the packages pdns-backend-ldap
11689 and dhcp3-server-ldap in Debian use the LDAP server. The two
11690 implementations are quite different in how they use LDAP.&lt;/p&gt;
11691
11692 To get this information, I started slapd with debugging enabled and
11693 dumped the debug output to a file to get the LDAP searches performed
11694 on a Debian Edu main-server. Here is a summary.
11695
11696 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
11697
11698 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
11699 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
11700 the web.
11701
11702 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
11703 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
11704 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
11705 reverse entries are in two different subtrees in LDAP with a structure
11706 based on the DNS names, as in tjener.intern and
11707 2.2.0.10.in-addr.arpa.&lt;/p&gt;
11708
11709 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
11710 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
11711 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
11712 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
11713 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
11714 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
11715 forward entries, it is looking for attributes named dnsttl, arecord,
11716 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
11717 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
11718 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
11719 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
11720 spfrecord and modifytimestamp. For reverse entries it is looking for
11721 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
11722 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
11723 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
11724 ldapsearch commands could look like this:&lt;/p&gt;
11725
11726 &lt;blockquote&gt;&lt;pre&gt;
11727 ldapsearch -h ldap \
11728 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11729 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
11730 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11731 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11732 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11733 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11734
11735 ldapsearch -h ldap \
11736 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11737 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
11738 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
11739 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
11740 srvrecord naptrrecord modifytimestamp
11741 &lt;/pre&gt;&lt;/blockquote&gt;
11742
11743 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
11744 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
11745 example LDAP objects used there. In addition to these objects, the
11746 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
11747 also exist.&lt;/p&gt;
11748
11749 &lt;blockquote&gt;&lt;pre&gt;
11750 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
11751 objectclass: top
11752 objectclass: dnsdomain
11753 objectclass: domainrelatedobject
11754 dc: tjener
11755 arecord: 10.0.2.2
11756 associateddomain: tjener.intern
11757
11758 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
11759 objectclass: top
11760 objectclass: dnsdomain2
11761 objectclass: domainrelatedobject
11762 dc: 2
11763 ptrrecord: tjener.intern
11764 associateddomain: 2.2.0.10.in-addr.arpa
11765 &lt;/pre&gt;&lt;/blockquote&gt;
11766
11767 &lt;p&gt;In strict mode, the server behaves differently. When looking for
11768 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
11769 same base as in the tree mode for a object with filter
11770 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
11771 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
11772 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
11773 naptrrecord and modifytimestamp. For reverse entires it also do a
11774 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
11775 and the requested attributes are associateddomain, dnsttl and
11776 modifytimestamp. In short, in strict mode the objects with ptrrecord
11777 go away, and the arecord attribute in the forward object is used
11778 instead.&lt;/p&gt;
11779
11780 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
11781 like this:&lt;/p&gt;
11782
11783 &lt;blockquote&gt;&lt;pre&gt;
11784 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11785 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
11786 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11787 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11788 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11789 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11790
11791 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11792 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
11793 &lt;/pre&gt;&lt;/blockquote&gt;
11794
11795 &lt;p&gt;In addition to the forward and reverse searches , there is also a
11796 search for SOA records, which behave similar to the forward and
11797 reverse lookups.&lt;/p&gt;
11798
11799 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
11800 specify any objectclass names, and instead look for the attributes it
11801 need to generate a DNS reply. This make it able to work with any
11802 objectclass that provide the needed attributes.&lt;/p&gt;
11803
11804 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
11805 dnsdomain2 schemas. The latter is used for reverse entries like
11806 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
11807
11808 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
11809 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
11810 attributes) and domainrelatedobject (for associatedDomain). The use
11811 of structural object classes make it impossible to combine these
11812 classes with the object classes used by DHCP.&lt;/p&gt;
11813
11814 &lt;p&gt;There are other schemas that could be used too, for example the
11815 dnszone structural object class used by Gosa and bind-sdb for the DNS
11816 attributes combined with the domainrelatedobject object class, but in
11817 this case some unused attributes would have to be included as well
11818 (zonename and relativedomainname).&lt;/p&gt;
11819
11820 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
11821 mode and not use any of the existing objectclasses (dnsdomain,
11822 dnsdomain2 and dnszone) when one want to combine the DNS information
11823 with DHCP information, and instead create a auxiliary object class
11824 defined something like this (using the attributes defined for
11825 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
11826
11827 &lt;blockquote&gt;&lt;pre&gt;
11828 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
11829 SUP top
11830 AUXILIARY
11831 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
11832 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
11833 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
11834 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
11835 A6Record $ DNAMERecord
11836 ))
11837 &lt;/pre&gt;&lt;/blockquote&gt;
11838
11839 &lt;p&gt;This will allow any object to become a DNS entry when combined with
11840 the domainrelatedobject object class, and allow any entity to include
11841 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
11842 developers asking for their view on this schema and if they are
11843 interested in providing such schema with PowerDNS, and I hope my
11844 message will be accepted into their mailing list soon.&lt;/p&gt;
11845
11846 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
11847
11848 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
11849 the object attributes, and then uses the attributes it want. This
11850 make it harder to figure out exactly what attributes are used, but
11851 thanks to the working example in Debian Edu I can at least get an idea
11852 what is needed without having to read the source code.&lt;/p&gt;
11853
11854 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
11855 search filter to use to locate the correct dhcpServer entity is
11856 stored. These are the relevant entries from
11857 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
11858
11859 &lt;blockquote&gt;&lt;pre&gt;
11860 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
11861 ldap-dhcp-server-cn &quot;dhcp&quot;;
11862 &lt;/pre&gt;&lt;/blockquote&gt;
11863
11864 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
11865 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
11866 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
11867 search result is this entry:&lt;/p&gt;
11868
11869 &lt;blockquote&gt;&lt;pre&gt;
11870 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
11871 cn: dhcp
11872 objectClass: top
11873 objectClass: dhcpServer
11874 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11875 &lt;/pre&gt;&lt;/blockquote&gt;
11876
11877 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
11878 subtree with DHCP configuration. The DHCP configuration subtree base
11879 is located using a base scope search with base &quot;cn=DHCP
11880 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
11881 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
11882 The search result is this entry:&lt;/p&gt;
11883
11884 &lt;blockquote&gt;&lt;pre&gt;
11885 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11886 cn: DHCP Config
11887 objectClass: top
11888 objectClass: dhcpService
11889 objectClass: dhcpOptions
11890 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
11891 dhcpStatements: ddns-update-style none
11892 dhcpStatements: authoritative
11893 dhcpOption: smtp-server code 69 = array of ip-address
11894 dhcpOption: www-server code 72 = array of ip-address
11895 dhcpOption: wpad-url code 252 = text
11896 &lt;/pre&gt;&lt;/blockquote&gt;
11897
11898 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
11899 all the DHCP configuration is loaded, it is ready to receive requests.
11900 The subtree in Debian Edu contain objects with object classes
11901 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
11902 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
11903 and information about netmasks, dynamic range etc. Leaving out the
11904 details here because it is not relevant for the focus of my
11905 investigation, which is to see if it is possible to merge dns and dhcp
11906 related computer objects.&lt;/p&gt;
11907
11908 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
11909 of the client (00:00:00:00:00:00 in this example), using a subtree
11910 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
11911 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
11912 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
11913 like:&lt;/p&gt;
11914
11915 &lt;blockquote&gt;&lt;pre&gt;
11916 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11917 cn: hostname
11918 objectClass: top
11919 objectClass: dhcpHost
11920 dhcpHWAddress: ethernet 00:00:00:00:00:00
11921 dhcpStatements: fixed-address hostname
11922 &lt;/pre&gt;&lt;/blockquote&gt;
11923
11924 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
11925 The object classes need to have fixed names, and the configuration
11926 need to be stored in a fairly specific LDAP structure. On the
11927 positive side, the invidiual dhcpHost entires can be anywhere without
11928 the DN pointed to by the dhcpServer entries. The latter should make
11929 it possible to group all host entries in a subtree next to the
11930 configuration entries, and this subtree can also be shared with the
11931 DNS server if the schema proposed above is combined with the dhcpHost
11932 structural object class.
11933
11934 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
11935
11936 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
11937 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
11938 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
11939 allowing DNS objects to be stored anywhere under the base cn specified
11940 in the configuration.&lt;/p&gt;
11941
11942 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
11943 regarding which LDAP schemas to use and which LDAP structure to use.
11944 I guess one could implement ones own schema, as long as the
11945 objectclasses and attributes have the names used, but this do not
11946 really help when the DHCP subtree need to have a fairly fixed
11947 structure.&lt;/p&gt;
11948
11949 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
11950 this might work for Debian Edu:&lt;/p&gt;
11951
11952 &lt;blockquote&gt;&lt;pre&gt;
11953 ou=services
11954 cn=machine-info (dhcpService) - dhcpServiceDN points here
11955 cn=dhcp (dhcpServer)
11956 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
11957 cn=10.0.2.0 (dhcpSubnet)
11958 cn=group1 (dhcpGroup/dhcpOptions)
11959 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
11960 cn=192.168.0.0 (dhcpSubnet)
11961 cn=group1 (dhcpGroup/dhcpOptions)
11962 ou=machines - PowerDNS base points here
11963 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
11964 &lt;/pre&gt;&lt;/blockquote&gt;
11965
11966 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
11967 entries to be in the dhcpGroup subtrees, the entries can be stored
11968 there instead of a common machines subtree, and the PowerDNS base
11969 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
11970
11971 &lt;p&gt;The combined object under the machines subtree would look something
11972 like this:&lt;/p&gt;
11973
11974 &lt;blockquote&gt;&lt;pre&gt;
11975 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
11976 dc: hostname
11977 objectClass: top
11978 objectClass: dhcpHost
11979 objectclass: domainrelatedobject
11980 objectclass: dnsDomainAux
11981 associateddomain: hostname.intern
11982 arecord: 10.11.12.13
11983 dhcpHWAddress: ethernet 00:00:00:00:00:00
11984 dhcpStatements: fixed-address hostname.intern
11985 &lt;/pre&gt;&lt;/blockquote&gt;
11986
11987 &lt;/p&gt;One could even add the LTSP configuration associated with a given
11988 machine, as long as the required attributes are available in a
11989 auxiliary object class.&lt;/p&gt;
11990 </description>
11991 </item>
11992
11993 <item>
11994 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
11995 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
11996 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
11997 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
11998 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
11999 DHCP services in Debian Edu to use the same LDAP objects for a given
12000 computer, to avoid the possibility of having a inconsistent state for
12001 a computer in LDAP (as in DHCP but no DNS entry or the other way
12002 around) and make it easier to add computers to LDAP.&lt;/p&gt;
12003
12004 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
12005 information finally found a solution that seem to work.&lt;/p&gt;
12006
12007 &lt;p&gt;The old setup required three LDAP objects for a given computer.
12008 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
12009 we switch powerdns to use its strict LDAP method (ldap-method=strict
12010 in pdns-debian-edu.conf), the forward and reverse DNS entries are
12011 merged into one while making it impossible to transfer the reverse map
12012 to a slave DNS server.&lt;/p&gt;
12013
12014 &lt;p&gt;If we also replace the object class used to get the DNS related
12015 attributes to one allowing these attributes to be combined with the
12016 dhcphost object class, we can merge the DNS and DHCP entries into one.
12017 I&#39;ve written such object class in the dnsdomainaux.schema file (need
12018 proper OIDs, but that is a minor issue), and tested the setup. It
12019 seem to work.&lt;/p&gt;
12020
12021 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
12022 for both DNS and DHCP, and even the LTSP configuration I suggested in
12023 an earlier email. The combined LDAP object will look something like
12024 this:&lt;/p&gt;
12025
12026 &lt;blockquote&gt;&lt;pre&gt;
12027 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
12028 cn: hostname
12029 objectClass: dhcphost
12030 objectclass: domainrelatedobject
12031 objectclass: dnsdomainaux
12032 associateddomain: hostname.intern
12033 arecord: 10.11.12.13
12034 dhcphwaddress: ethernet 00:00:00:00:00:00
12035 dhcpstatements: fixed-address hostname
12036 ldapconfigsound: Y
12037 &lt;/pre&gt;&lt;/blockquote&gt;
12038
12039 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
12040 the DHCP server uses the dhcphwaddress and dhcpstatements entries
12041 before asking DNS to resolve the fixed-adddress. LTSP will use
12042 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
12043
12044 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
12045 dhcphost in a different location, to allow us to put the objects
12046 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
12047 that. If I can&#39;t figure out a way to do that, we can still get rid of
12048 the hosts subtree and move all its content into the DHCP Config tree
12049 (which probably should be renamed to be more related to the new
12050 content. I suspect cn=dnsdhcp,ou=services or something like that
12051 might be a good place to put it.&lt;/p&gt;
12052
12053 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
12054 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
12055 </description>
12056 </item>
12057
12058 <item>
12059 <title>Idea for storing LTSP configuration in LDAP</title>
12060 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
12061 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
12062 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
12063 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
12064 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
12065 clients, and that this can be used to fetch configuration from LDAP if
12066 Debian Edu choose to store configuration there.&lt;/p&gt;
12067
12068 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
12069 to get configuration from LDAP. The idea is to look up the MAC
12070 address of the client in LDAP, and look for attributes on the form
12071 ltspconfigsetting=value, and use this to export SETTING=value to the
12072 LTSP clients.&lt;/p&gt;
12073
12074 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
12075 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
12076 allowing us to store all information about a computer in one place.&lt;/p&gt;
12077
12078 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
12079 this approach. A real LDAP schema for the ltspClientAux objectclass
12080 need to be written. Comments, suggestions, etc?&lt;/p&gt;
12081
12082 &lt;blockquote&gt;&lt;pre&gt;
12083 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
12084 #
12085 # Fetch LTSP client settings from LDAP based on MAC address
12086 #
12087 # Uses ethernet address as stored in the dhcpHost objectclass using
12088 # the dhcpHWAddress attribute or ethernet address stored in the
12089 # ieee802Device objectclass with the macAddress attribute.
12090 #
12091 # This module is written to be schema agnostic, and only depend on the
12092 # existence of attribute names.
12093 #
12094 # The LTSP configuration variables are saved directly using a
12095 # ltspConfig prefix and uppercasing the rest of the attribute name.
12096 # To set the SERVER variable, set the ltspConfigServer attribute.
12097 #
12098 # Some LDAP schema should be created with all the relevant
12099 # configuration settings. Something like this should work:
12100 #
12101 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
12102 # SUP top
12103 # AUXILIARY
12104 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
12105
12106 LDAPSERVER=$(debian-edu-ldapserver)
12107 if [ &quot;$LDAPSERVER&quot; ] ; then
12108 LDAPBASE=$(debian-edu-ldapserver -b)
12109 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
12110 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
12111 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
12112 grep &#39;^ltspConfig&#39; | while read attr value ; do
12113 # Remove prefix and convert to upper case
12114 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
12115 # bass value on to clients
12116 eval &quot;$attr=$value; export $attr&quot;
12117 done
12118 done
12119 fi
12120 &lt;/pre&gt;&lt;/blockquote&gt;
12121
12122 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
12123 the while block might end up in a subshell causing the variables set
12124 there to not show up in ltsp-config, but if that is the case I am sure
12125 the code can be restructured to make sure the variables are passed on.
12126 I expect that can be solved with some testing. :)&lt;/p&gt;
12127
12128 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
12129 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
12130
12131 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
12132 configuration in LDAP that was created around year 2000 by
12133 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
12134 Xperience, Inc., 2000&lt;/a&gt;. I found its
12135 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
12136 personal home page over at redhat.com.&lt;/p&gt;
12137 </description>
12138 </item>
12139
12140 <item>
12141 <title>jXplorer, a very nice LDAP GUI</title>
12142 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
12143 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
12144 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
12145 <description>&lt;p&gt;Since
12146 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
12147 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
12148 LDAP GUI that is even better than luma. The java application
12149 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
12150 moving LDAP objects and subtrees using drag-and-drop, and can
12151 authenticate using Kerberos. I have only tested the Kerberos
12152 authentication, but do not have a LDAP setup allowing me to rewrite
12153 LDAP with my test user yet. It is
12154 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
12155 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
12156 have with it is how it handle errors. If something go wrong, its
12157 non-intuitive behaviour require me to go through some query work list
12158 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
12159 </description>
12160 </item>
12161
12162 <item>
12163 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
12164 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
12165 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
12166 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
12167 <description>&lt;p&gt;Here is a short update on my &lt;a
12168 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
12169 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
12170 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
12171 not reporting the status for KDE, because the upgrade crashes when
12172 aptitude try because of missing conflicts
12173 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
12174 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
12175
12176 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
12177 complete list of the installed packages. Based on this I see these
12178 differences when I did a test run today. As usual, I do not really
12179 know what the correct set of packages would be, but thought it best to
12180 publish the difference.&lt;/p&gt;
12181
12182 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
12183
12184 &lt;blockquote&gt;&lt;p&gt;
12185 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
12186 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
12187 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
12188 libgtksourceview-common libpt-1.10.10-plugins-alsa
12189 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
12190 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
12191 python-4suite-xml python-eggtrayicon python-gtkhtml2
12192 python-gtkmozembed svgalibg1 xserver-xephyr zip
12193 &lt;/p&gt;&lt;/blockquote&gt;
12194
12195 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
12196
12197 &lt;blockquote&gt;&lt;p&gt;
12198 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
12199 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
12200 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
12201 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
12202 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
12203 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
12204 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
12205 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
12206 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
12207 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
12208 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
12209 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
12210 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
12211 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
12212 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
12213 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
12214 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
12215 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
12216 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
12217 mysql-common swfdec-gnome totem-gstreamer wodim
12218 &lt;/p&gt;&lt;/blockquote&gt;
12219
12220 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
12221
12222 &lt;blockquote&gt;&lt;p&gt;
12223 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
12224 python-gnomekeyring python-wnck rhythmbox-plugins xorg
12225 xserver-xorg-input-all xserver-xorg-input-evdev
12226 xserver-xorg-input-kbd xserver-xorg-input-mouse
12227 xserver-xorg-input-synaptics xserver-xorg-video-all
12228 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
12229 xserver-xorg-video-chips xserver-xorg-video-cirrus
12230 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12231 xserver-xorg-video-glint xserver-xorg-video-i128
12232 xserver-xorg-video-i740 xserver-xorg-video-mach64
12233 xserver-xorg-video-mga xserver-xorg-video-neomagic
12234 xserver-xorg-video-nouveau xserver-xorg-video-nv
12235 xserver-xorg-video-r128 xserver-xorg-video-radeon
12236 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
12237 xserver-xorg-video-s3 xserver-xorg-video-s3virge
12238 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
12239 xserver-xorg-video-sis xserver-xorg-video-sisusb
12240 xserver-xorg-video-tdfx xserver-xorg-video-tga
12241 xserver-xorg-video-trident xserver-xorg-video-tseng
12242 xserver-xorg-video-vesa xserver-xorg-video-vmware
12243 xserver-xorg-video-voodoo
12244 &lt;/p&gt;&lt;/blockquote&gt;
12245
12246 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
12247
12248 &lt;blockquote&gt;&lt;p&gt;
12249 deskbar-applet xserver-xorg xserver-xorg-core
12250 xserver-xorg-input-wacom xserver-xorg-video-intel
12251 xserver-xorg-video-openchrome
12252 &lt;/p&gt;&lt;/blockquote&gt;
12253
12254 &lt;p&gt;I was told on IRC that the xorg-xserver package was
12255 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
12256 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
12257 No idea when it hits Squeeze, but when it does I hope it will reduce
12258 the difference somewhat.
12259 </description>
12260 </item>
12261
12262 <item>
12263 <title>LUMA, a very nice LDAP GUI</title>
12264 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
12265 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
12266 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
12267 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
12268 directory in Debian Edu, and in the process I started to miss a GUI
12269 tool to browse the LDAP tree. The only one I was able to find in
12270 Debian/Squeeze and Lenny is
12271 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
12272 be a great tool to get a overview of the current LDAP directory
12273 populated by default in Skolelinux. Thanks to it, I have been able to
12274 find empty and obsolete subtrees, misplaced objects and duplicate
12275 objects. It will be installed by default in Debian/Squeeze. If you
12276 are working with LDAP, give it a go. :)&lt;/p&gt;
12277
12278 &lt;p&gt;I did notice one problem with it I have not had time to report to
12279 the BTS yet. There is no .desktop file in the package, so the tool do
12280 not show up in the Gnome and KDE menus, but only deep down in in the
12281 Debian submenu in KDE. I hope that can be fixed before Squeeze is
12282 released.&lt;/p&gt;
12283
12284 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
12285 like to move objects and remove subtrees directly in the GUI, but have
12286 not found a way to do that with LUMA yet. So in the mean time, I use
12287 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
12288
12289 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
12290 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
12291
12292 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
12293 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
12294 useful GUI alternative. It seem like a good tool, but is unmaintained
12295 in Debian and got a RC bug keeping it out of Squeeze. Unless that
12296 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
12297 </description>
12298 </item>
12299
12300 <item>
12301 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
12302 <link>https://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>
12303 <guid isPermaLink="true">https://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>
12304 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
12305 <description>&lt;p&gt;A while back, I
12306 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
12307 about the fact&lt;/a&gt; that it is not possible with the provided schemas
12308 for storing DNS and DHCP information in LDAP to combine the two sets
12309 of information into one LDAP object representing a computer.&lt;/p&gt;
12310
12311 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
12312 the dhcpHost object class auxiliary, to allow it to be combined with
12313 the dNSDomain object class, and thus forming one object for one
12314 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
12315
12316 &lt;p&gt;If I understand this correctly, it is not safe to do this change
12317 without also changing the assigned number for the object class, and I
12318 do not know enough about LDAP schema design to do that properly for
12319 Debian Edu.&lt;/p&gt;
12320
12321 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
12322 the
12323 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
12324 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
12325 available today from IETF.&lt;/p&gt;
12326
12327 &lt;pre&gt;
12328 --- dhcp.schema (revision 65192)
12329 +++ dhcp.schema (working copy)
12330 @@ -376,7 +376,7 @@
12331 objectclass ( 2.16.840.1.113719.1.203.6.6
12332 NAME &#39;dhcpHost&#39;
12333 DESC &#39;This represents information about a particular client&#39;
12334 - SUP top
12335 + SUP top AUXILIARY
12336 MUST cn
12337 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
12338 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
12339 &lt;/pre&gt;
12340
12341 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
12342 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
12343 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
12344
12345 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
12346 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
12347 </description>
12348 </item>
12349
12350 <item>
12351 <title>Calling tasksel like the installer, while still getting useful output</title>
12352 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
12353 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
12354 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
12355 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
12356 installs packages during the normal debian-installer run. Until now,
12357 I have ended up letting tasksel do the work, with the annoying problem
12358 of not getting any feedback at all when something fails (like a
12359 conffile question from dpkg or a download that fails), using code like
12360 this:
12361
12362 &lt;blockquote&gt;&lt;pre&gt;
12363 export DEBIAN_FRONTEND=noninteractive
12364 tasksel --new-install
12365 &lt;/pre&gt;&lt;/blockquote&gt;
12366
12367 This would invoke tasksel, let its automatic task selection pick the
12368 tasks to install, and continue to install the requested tasks without
12369 any output what so ever.
12370
12371 Recently I revisited this problem while working on the automatic
12372 package upgrade testing, because tasksel would some times hang without
12373 any useful feedback, and I want to see what is going on when it
12374 happen. Then it occured to me, I can parse the output from tasksel
12375 when asked to run in test mode, and use that aptitude command line
12376 printed by tasksel then to simulate the tasksel run. I ended up using
12377 code like this:
12378
12379 &lt;blockquote&gt;&lt;pre&gt;
12380 export DEBIAN_FRONTEND=noninteractive
12381 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
12382 $cmd
12383 &lt;/pre&gt;&lt;/blockquote&gt;
12384
12385 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
12386 --without-recommends -o APT::Install-Recommends=no -y install
12387 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
12388 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
12389 laptop task and all packages with priority standard , required and
12390 important, just like tasksel would have done it during
12391 installation.&lt;/p&gt;
12392
12393 &lt;p&gt;A better approach is probably to extend tasksel to be able to
12394 install packages without using debconf-apt-progress, for use cases
12395 like this.&lt;/p&gt;
12396 </description>
12397 </item>
12398
12399 <item>
12400 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
12401 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
12402 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
12403 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
12404 <description>&lt;p&gt;My
12405 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
12406 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
12407 finally made the upgrade logs available from
12408 &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;.
12409 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
12410 apt and aptitude, and found their differences interesting. This time
12411 I will only focus on their removal plans.&lt;/p&gt;
12412
12413 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
12414 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
12415 surprising part is that it want to remove xorg and all
12416 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
12417 sure why. When asking aptitude to do the same, it want to remove 129
12418 packages, but most of them are library packages I suspect are no
12419 longer needed. Both of them want to remove bluetooth packages, which
12420 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
12421
12422 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
12423 which seem like a bad idea and xorg the same way as with Gnome. Asking
12424 aptitude for the same, it wants to remove 192 packages, none which are
12425 too surprising.&lt;/p&gt;
12426
12427 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
12428 and avoided, and perhaps others as well. Here are the complete list
12429 of planned removals. The complete logs is available from the URL
12430 above. Note if you want to repeat these tests, that the upgrade test
12431 for kde+apt-get hung in the tasksel setup because of dpkg asking
12432 conffile questions. No idea why. I worked around it by using
12433 &#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
12434 continue.&lt;/p&gt;
12435
12436 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
12437 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
12438 gnome-desktop-environment gnome-network-admin gtkhtml3.14
12439 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
12440 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
12441 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
12442 serpentine swfdec-mozilla update-manager xorg xserver-xorg
12443 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12444 xserver-xorg-input-kbd xserver-xorg-input-mouse
12445 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12446 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12447 xserver-xorg-video-ati xserver-xorg-video-chips
12448 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12449 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12450 xserver-xorg-video-glint xserver-xorg-video-i128
12451 xserver-xorg-video-i740 xserver-xorg-video-imstt
12452 xserver-xorg-video-intel xserver-xorg-video-mach64
12453 xserver-xorg-video-mga xserver-xorg-video-neomagic
12454 xserver-xorg-video-nsc xserver-xorg-video-nv
12455 xserver-xorg-video-openchrome xserver-xorg-video-r128
12456 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12457 xserver-xorg-video-rendition xserver-xorg-video-s3
12458 xserver-xorg-video-s3virge xserver-xorg-video-savage
12459 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12460 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12461 xserver-xorg-video-tga xserver-xorg-video-trident
12462 xserver-xorg-video-tseng xserver-xorg-video-v4l
12463 xserver-xorg-video-vesa xserver-xorg-video-vga
12464 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
12465 xulrunner-1.9-gnome-support&lt;/p&gt;
12466
12467 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
12468
12469 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
12470 djvulibre-desktop finger gnome-app-install gnome-mount
12471 gnome-network-admin gnome-spell gnome-vfs-obexftp
12472 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
12473 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
12474 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
12475 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
12476 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
12477 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
12478 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
12479 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
12480 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
12481 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
12482 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
12483 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
12484 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
12485 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
12486 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
12487 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
12488 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
12489 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
12490 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
12491 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
12492 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
12493 openoffice.org-writer2latex openssl-blacklist p7zip
12494 python-4suite-xml python-eggtrayicon python-gnome2-desktop
12495 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
12496 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
12497 swfdec-mozilla totem-gstreamer update-manager wodim
12498 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12499 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12500 zip&lt;/p&gt;
12501
12502 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
12503
12504 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
12505 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
12506 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
12507 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
12508 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
12509 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
12510 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12511 xserver-xorg-input-kbd xserver-xorg-input-mouse
12512 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12513 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12514 xserver-xorg-video-ati xserver-xorg-video-chips
12515 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12516 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12517 xserver-xorg-video-glint xserver-xorg-video-i128
12518 xserver-xorg-video-i740 xserver-xorg-video-imstt
12519 xserver-xorg-video-intel xserver-xorg-video-mach64
12520 xserver-xorg-video-mga xserver-xorg-video-neomagic
12521 xserver-xorg-video-nsc xserver-xorg-video-nv
12522 xserver-xorg-video-openchrome xserver-xorg-video-r128
12523 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12524 xserver-xorg-video-rendition xserver-xorg-video-s3
12525 xserver-xorg-video-s3virge xserver-xorg-video-savage
12526 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12527 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12528 xserver-xorg-video-tga xserver-xorg-video-trident
12529 xserver-xorg-video-tseng xserver-xorg-video-v4l
12530 xserver-xorg-video-vesa xserver-xorg-video-vga
12531 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
12532
12533 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
12534 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
12535 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
12536 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
12537 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
12538 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
12539 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
12540 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
12541 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
12542 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
12543 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
12544 kghostview khelpcenter khexedit kiconedit kitchensync klatin
12545 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
12546 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
12547 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
12548 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
12549 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
12550 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
12551 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
12552 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
12553 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
12554 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
12555 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
12556 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
12557 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
12558 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
12559 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
12560 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
12561 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
12562 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
12563 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
12564 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
12565 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
12566 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
12567 texlive-common texlive-doc-base texlive-fonts-recommended
12568 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12569 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12570 xulrunner-1.9&lt;/p&gt;
12571
12572 </description>
12573 </item>
12574
12575 <item>
12576 <title>Automatic upgrade testing from Lenny to Squeeze</title>
12577 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
12578 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
12579 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
12580 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
12581 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
12582 have been discovered and reported in the process
12583 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
12584 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
12585 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
12586 kdebase-workspace-data), and to get a more regular testing going on, I
12587 am working on a script to automate the test.&lt;/p&gt;
12588
12589 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
12590 Gnome or KDE desktop installation inside the chroot before upgrading
12591 it. To ensure no services are started in the chroot, a policy-rc.d
12592 script is inserted. To make sure tasksel believe it is to install a
12593 desktop on a laptop, the tasksel tests are replaced in the chroot
12594 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
12595
12596 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
12597 currently always fail because udev refuses to upgrade with the kernel
12598 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
12599 is created. The bug report
12600 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
12601 this problem do not trigger in a chroot, but I touch the file anyway
12602 to make sure the upgrade go well. Testing on virtual and real
12603 hardware have failed me because of udev so far, and creating this file
12604 do the trick in such settings anyway. This is a
12605 &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
12606 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
12607 maintainer because he lack the resources to rewrite udev to keep
12608 working with old kernels or something like that. I really wish the
12609 udev upstream would keep udev backwards compatible, to avoid such
12610 upgrade problem, but given that they fail to do so, I guess
12611 documenting the way out of this mess is the best option we got for
12612 Debian Squeeze.&lt;/p&gt;
12613
12614 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
12615 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
12616 trick:&lt;/p&gt;
12617
12618 &lt;blockquote&gt;&lt;pre&gt;
12619 #!/bin/sh
12620 set -ex
12621
12622 if [ &quot;$1&quot; ] ; then
12623 desktop=$1
12624 else
12625 desktop=gnome
12626 fi
12627
12628 from=lenny
12629 to=squeeze
12630
12631 exec &amp;lt; /dev/null
12632 unset LANG
12633 mirror=http://ftp.skolelinux.org/debian
12634 tmpdir=chroot-$from-upgrade-$to-$desktop
12635 fuser -mv .
12636 debootstrap $from $tmpdir $mirror
12637 chroot $tmpdir aptitude update
12638 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
12639 #!/bin/sh
12640 exit 101
12641 EOF
12642 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
12643 exit_cleanup() {
12644 umount $tmpdir/proc
12645 }
12646 mount -t proc proc $tmpdir/proc
12647 # Make sure proc is unmounted also on failure
12648 trap exit_cleanup EXIT INT
12649
12650 chroot $tmpdir aptitude -y install debconf-utils
12651
12652 # Make sure tasksel autoselection trigger. It need the test scripts
12653 # to return the correct answers.
12654 echo tasksel tasksel/desktop multiselect $desktop | \
12655 chroot $tmpdir debconf-set-selections
12656
12657 # Include the desktop and laptop task
12658 for test in desktop laptop ; do
12659 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
12660 #!/bin/sh
12661 exit 2
12662 EOF
12663 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
12664 done
12665
12666 DEBIAN_FRONTEND=noninteractive
12667 DEBIAN_PRIORITY=critical
12668 export DEBIAN_FRONTEND DEBIAN_PRIORITY
12669 chroot $tmpdir tasksel --new-install
12670
12671 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
12672 chroot $tmpdir aptitude update
12673 touch $tmpdir/etc/udev/kernel-upgrade
12674 chroot $tmpdir aptitude -y dist-upgrade
12675 fuser -mv
12676 &lt;/pre&gt;&lt;/blockquote&gt;
12677
12678 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
12679 with aptitude, but I have not had time to look at how they behave
12680 differently so far. I hope to get a cron job running to do the test
12681 regularly and post the result on the web. The Gnome upgrade currently
12682 work, while the KDE upgrade fail because of the bug in
12683 kdebase-workspace-data&lt;/p&gt;
12684
12685 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
12686 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
12687 post, so I will refrain from trying. I can report that for Gnome,
12688 aptitude report 760 packages upgraded, 448 newly installed, 129 to
12689 remove and 1 not upgraded and 1024MB need to be downloaded while for
12690 KDE the same numbers are 702 packages upgraded, 507 newly installed,
12691 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
12692
12693 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
12694 is able to migrate to dependency based boot sequencing and parallel
12695 booting without a hitch. Was unsure if there were still bugs with
12696 packages failing to clean up their obsolete init.d script during
12697 upgrades, and no such problem seem to affect the Gnome desktop+laptop
12698 packages.&lt;/p&gt;
12699 </description>
12700 </item>
12701
12702 <item>
12703 <title>Upstart or sysvinit - as init.d scripts see it</title>
12704 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
12705 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
12706 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
12707 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
12708 scripts to migrate (some of) their operations to upstart job while
12709 keeping the init.d for hurd and kfreebsd. The packages with such
12710 needs will need a way to get their init.d scripts to behave
12711 differently when used with sysvinit and with upstart. Because of
12712 this, I had a look at the environment variables set when a init.d
12713 script is running under upstart, and when it is not.&lt;/p&gt;
12714
12715 &lt;p&gt;With upstart, I notice these environment variables are set when a
12716 script is started from rcS.d/ (ignoring some irrelevant ones like
12717 COLUMNS):&lt;/p&gt;
12718
12719 &lt;blockquote&gt;&lt;pre&gt;
12720 DEFAULT_RUNLEVEL=2
12721 previous=N
12722 PREVLEVEL=
12723 RUNLEVEL=
12724 runlevel=S
12725 UPSTART_EVENTS=startup
12726 UPSTART_INSTANCE=
12727 UPSTART_JOB=rc-sysinit
12728 &lt;/pre&gt;&lt;/blockquote&gt;
12729
12730 &lt;p&gt;With sysvinit, these environment variables are set for the same
12731 script.&lt;/p&gt;
12732
12733 &lt;blockquote&gt;&lt;pre&gt;
12734 INIT_VERSION=sysvinit-2.88
12735 previous=N
12736 PREVLEVEL=N
12737 RUNLEVEL=S
12738 runlevel=S
12739 &lt;/pre&gt;&lt;/blockquote&gt;
12740
12741 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
12742 sysvinit are not set by upstart. Not sure if it is intentional or not
12743 to not be compatible with sysvinit in this regard.&lt;/p&gt;
12744
12745 &lt;p&gt;For scripts needing to behave differently when upstart is used,
12746 looking for the UPSTART_JOB environment variable seem to be a good
12747 choice.&lt;/p&gt;
12748 </description>
12749 </item>
12750
12751 <item>
12752 <title>A manual for standards wars...</title>
12753 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
12754 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
12755 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
12756 <description>&lt;p&gt;Via the
12757 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
12758 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
12759 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
12760 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
12761 following the standards wars of today.&lt;/p&gt;
12762 </description>
12763 </item>
12764
12765 <item>
12766 <title>Sitesummary tip: Listing computer hardware models used at site</title>
12767 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
12768 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
12769 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
12770 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
12771 to get a list of the machine types in use thanks to the DMI
12772 information extracted from each machine. The script to do so is
12773 included in the sitesummary package, and here is example output from
12774 the Skolelinux build servers:&lt;/p&gt;
12775
12776 &lt;blockquote&gt;&lt;pre&gt;
12777 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
12778 vendor count
12779 Dell Computer Corporation 1
12780 PowerEdge 1750 1
12781 IBM 1
12782 eserver xSeries 345 -[8670M1X]- 1
12783 Intel 2
12784 [no-dmi-info] 3
12785 maintainer:~#
12786 &lt;/pre&gt;&lt;/blockquote&gt;
12787
12788 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
12789 provided in each machine. Here there are Intel machines without model
12790 information listed with Intel as vendor and no model, and virtual Xen
12791 machines listed as [no-dmi-info]. One can add -l as a command line
12792 option to list the individual machines.&lt;/p&gt;
12793
12794 &lt;p&gt;A larger list is
12795 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
12796 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
12797 provide the basic sitesummary report publicly. In their report there
12798 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
12799 their machines, and as sitesummary is available in both distributions,
12800 it is trivial to get all of them to report to the same central
12801 collector.&lt;/p&gt;
12802 </description>
12803 </item>
12804
12805 <item>
12806 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
12807 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
12808 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</guid>
12809 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
12810 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
12811 start at boot when an NVidia video card is used is handled. The
12812 problem seem to be that the nvidia X.org driver uses a long time to
12813 initialize, and this duration is longer than kdm is configured to
12814 wait.&lt;/p&gt;
12815
12816 &lt;p&gt;I came across two bugs related to this issue,
12817 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
12818 against initscripts and passed on to nvidia-glx when it became obvious
12819 that the nvidia drivers were involved, and
12820 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
12821 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
12822
12823 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
12824 problem nvidia video card owners experience and make sure the Debian
12825 distribution work out of the box for these users. The nvidia driver
12826 maintainers expect kdm to be set up to wait longer, while kdm expect
12827 the nvidia driver maintainers to fix the driver to start faster, and
12828 while they wait for each other I guess the users end up switching to a
12829 distribution that work for them. I have no idea what the solution is,
12830 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
12831
12832 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
12833 </description>
12834 </item>
12835
12836 <item>
12837 <title>Parallellized boot seem to hold up well in Debian/testing</title>
12838 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
12839 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
12840 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
12841 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
12842 The feature seem to hold up pretty well, but three fairly serious
12843 issues are known and should be solved:
12844
12845 &lt;p&gt;&lt;ul&gt;
12846
12847 &lt;li&gt;The wicd package seen to
12848 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
12849 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
12850 parallel booting is enabled. No idea why, but the wicd maintainer
12851 seem to be on the case.&lt;/li&gt;
12852
12853 &lt;li&gt;The nvidia X driver seem to
12854 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
12855 triggered more easily when parallel booting is in effect. The
12856 maintainer is on the case.&lt;/li&gt;
12857
12858 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
12859 sequencing (the shutdown is broken) when old file-rc users
12860 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
12861 sysv-rc. One way to solve it would be for file-rc to create
12862 /etc/init.d/.legacy-bootordering, and another is to try to make
12863 sysv-rc more robust. Will investigate some more and probably upload a
12864 workaround in sysv-rc to help those trying to move from file-rc to
12865 sysv-rc get a working shutdown.&lt;/li&gt;
12866
12867 &lt;/ul&gt;&lt;/p&gt;
12868
12869 &lt;p&gt;All in all not many surprising issues, and all of them seem
12870 solvable before Squeeze is released. In addition to these there are
12871 some packages with bugs in their dependencies and run level settings,
12872 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
12873
12874 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12875 the BTS, please usertag the report to get it to show up at
12876 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12877 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12878
12879 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
12880 </description>
12881 </item>
12882
12883 <item>
12884 <title>More flexible firmware handling in debian-installer</title>
12885 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
12886 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
12887 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
12888 <description>&lt;p&gt;After a long break from debian-installer development, I finally
12889 found time today to return to the project. Having to spend less time
12890 working dependency based boot in debian, as it is almost complete now,
12891 definitely helped freeing some time.&lt;/p&gt;
12892
12893 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
12894 include some firmware packages on the Debian Edu CDs, those needed to
12895 get disk and network controllers working. Without having these
12896 firmware packages available during installation, it is impossible to
12897 install Debian Edu on the given machine, and because our target group
12898 are non-technical people, asking them to provide firmware packages on
12899 an external medium is a support pain. Initially, I expected it to be
12900 enough to include the firmware packages on the CD to get
12901 debian-installer to find and use them. This proved to be wrong.
12902 Next, I hoped it was enough to symlink the relevant firmware packages
12903 to some useful location on the CD (tried /cdrom/ and
12904 /cdrom/firmware/). This also proved to not work, and at this point I
12905 found time to look at the debian-installer code to figure out what was
12906 going to work.&lt;/p&gt;
12907
12908 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
12909 look revealed that it would only look for firmware packages outside
12910 the installation media, so the CD was never checked for firmware
12911 packages. It would only check USB sticks, floppies and other
12912 &quot;external&quot; media devices. Today I changed it to also look in the
12913 /cdrom/firmware/ directory on the mounted CD or DVD, which should
12914 solve the problem I ran into with Debian edu. I also changed it to
12915 look in /firmware/, to make sure the installer also find firmware
12916 provided in the initrd when booting the installer via PXE, to allow us
12917 to provide the same feature in the PXE setup included in Debian
12918 Edu.&lt;/p&gt;
12919
12920 &lt;p&gt;To make sure firmware deb packages with a license questions are not
12921 activated without asking if the license is accepted, I extended
12922 hw-detect to look for preinst scripts in the firmware packages, and
12923 run these before activating the firmware during installation. The
12924 license question is asked using debconf in the preinst, so this should
12925 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
12926
12927 &lt;p&gt;If you want to discuss the details of these features, please
12928 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
12929 </description>
12930 </item>
12931
12932 <item>
12933 <title>Parallellized boot is now the default in Debian/unstable</title>
12934 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
12935 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
12936 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
12937 <description>&lt;p&gt;Since this evening, parallel booting is the default in
12938 Debian/unstable for machines using dependency based boot sequencing.
12939 Apparently the testing of concurrent booting has been wider than
12940 expected, if I am to believe the
12941 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
12942 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
12943 with the feature this weekend, to give us some time to detect any
12944 remaining problems before Squeeze is frozen. If serious problems are
12945 detected, it is simple to change the default back to sequential boot.
12946 The upload of the new sysvinit package also activate a new upstream
12947 version.&lt;/p&gt;
12948
12949 More information about
12950 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12951 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
12952 currently possible to disable parallel booting when one run into
12953 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
12954
12955 &lt;blockquote&gt;&lt;pre&gt;
12956 CONCURRENCY=none
12957 &lt;/pre&gt;&lt;/blockquote&gt;
12958
12959 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12960 the BTS, please usertag the report to get it to show up at
12961 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12962 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12963 </description>
12964 </item>
12965
12966 <item>
12967 <title>Sitesummary tip: Listing MAC address of all clients</title>
12968 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
12969 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
12970 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
12971 <description>&lt;p&gt;In the recent Debian Edu versions, the
12972 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
12973 system&lt;/a&gt; is used to keep track of the machines in the school
12974 network. Each machine will automatically report its status to the
12975 central server after boot and once per night. The network setup is
12976 also reported, and using this information it is possible to get the
12977 MAC address of all network interfaces in the machines. This is useful
12978 to update the DHCP configuration.&lt;/p&gt;
12979
12980 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
12981 ist all MAC addresses of all machines reporting to sitesummary. Run
12982 this on the collector host:&lt;/p&gt;
12983
12984 &lt;blockquote&gt;&lt;pre&gt;
12985 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
12986 &lt;/pre&gt;&lt;/blockquote&gt;
12987
12988 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
12989 line per machine and with space between the MAC addresses.&lt;/p&gt;
12990
12991 &lt;p&gt;To allow system administrators easier job at adding static DHCP
12992 addresses for hosts, it would be possible to extend this to fetch
12993 machine information from sitesummary and update the DHCP and DNS
12994 tables in LDAP using this information. Such tool is unfortunately not
12995 written yet.&lt;/p&gt;
12996 </description>
12997 </item>
12998
12999 <item>
13000 <title>systemd, an interesting alternative to upstart</title>
13001 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
13002 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
13003 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
13004 <description>&lt;p&gt;The last few days a new boot system called
13005 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
13006 has been
13007 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
13008
13009 to the free software world. I have not yet had time to play around
13010 with it, but it seem to be a very interesting alternative to
13011 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
13012 a good alternative for Debian when we are able to switch to an event
13013 based boot system. Tollef is
13014 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
13015 systemd into Debian, and I look forward to seeing how well it work. I
13016 like the fact that systemd handles init.d scripts with dependency
13017 information natively, allowing them to run in parallel where upstart
13018 at the moment do not.&lt;/p&gt;
13019
13020 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
13021 platform support. It only work on recent Linux kernels, and also need
13022 some new kernel features enabled to function properly. This means
13023 kFreeBSD and Hurd ports of Debian will need a port or a different boot
13024 system. Not sure how that will be handled if systemd proves to be the
13025 way forward.&lt;/p&gt;
13026
13027 &lt;p&gt;In the mean time, based on the
13028 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
13029 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
13030 decided to enable full parallel booting as the default in Debian as
13031 soon as possible (probably this weekend or early next week), to see if
13032 there are any remaining serious bugs in the init.d dependencies. A
13033 new version of the sysvinit package implementing this change is
13034 already in experimental. If all go well, Squeeze will be released
13035 with parallel booting enabled by default.&lt;/p&gt;
13036 </description>
13037 </item>
13038
13039 <item>
13040 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
13041 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
13042 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
13043 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
13044 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
13045 complete, so complete that it is actually possible to run all the
13046 init.d scripts in parallell based on these dependencies. If you want
13047 to test your Squeeze system, make sure
13048 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
13049 based boot sequencing&lt;/a&gt; is enabled, and add this line to
13050 /etc/default/rcS:&lt;/p&gt;
13051
13052 &lt;blockquote&gt;&lt;pre&gt;
13053 CONCURRENCY=makefile
13054 &lt;/pre&gt;&lt;/blockquote&gt;
13055
13056 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
13057 scripts in parallel using the dependency information stored in
13058 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
13059 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
13060 to try to start the kdm and gdm scripts as early as possible, and will
13061 start the facilities required by kdm or gdm as early as possible to
13062 make this happen.&lt;/p&gt;
13063
13064 &lt;p&gt;Give it a try, and see if you like the result. If some services
13065 fail to start properly, it is most likely because they have incomplete
13066 init.d script dependencies in their startup script (or some of their
13067 dependent scripts have incomplete dependencies). Report bugs and get
13068 the package maintainers to fix it. :)&lt;/p&gt;
13069
13070 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
13071 manage to get the init.d script dependencies complete and correct. I
13072 expect we will get there in Squeeze+1, if we get manage to test and
13073 fix the remaining issues.&lt;/p&gt;
13074
13075 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
13076 the BTS, please usertag the report to get it to show up at
13077 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
13078 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
13079 </description>
13080 </item>
13081
13082 <item>
13083 <title>Debian has switched to dependency based boot sequencing</title>
13084 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
13085 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
13086 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
13087 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
13088 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
13089 have been migrated to using dependency based boot sequencing. This
13090 conclude work me and others have been doing for the last three days.
13091 It feels great to see this finally part of the default Debian
13092 installation. Now we just need to weed out the last few problems that
13093 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
13094
13095 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
13096 fixing the more fundamental problem of handing the event based
13097 non-predictable kernel in the early boot.&lt;/p&gt;
13098 </description>
13099 </item>
13100
13101 <item>
13102 <title>Taking over sysvinit development</title>
13103 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
13104 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
13105 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
13106 <description>&lt;p&gt;After several years of frustration with the lack of activity from
13107 the existing sysvinit upstream developer, I decided a few weeks ago to
13108 take over the package and become the new upstream. The number of
13109 patches to track for the Debian package was becoming a burden, and the
13110 lack of synchronization between the distribution made it hard to keep
13111 the package up to date.&lt;/p&gt;
13112
13113 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
13114 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
13115 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
13116 and Fedora), based on the patches currently in use in these
13117 distributions. We Debian maintainers plan to move to this tarball as
13118 the new upstream as soon as we find time to do the merge. Since the
13119 new tarball was created, we agreed with Werner at SuSe to make a new
13120 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
13121 development there. The project is registered and currently waiting
13122 for approval by the Savannah administrators, and as soon as it is
13123 approved, we will import the old versions from svn and continue
13124 working on the future release.&lt;/p&gt;
13125
13126 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
13127 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
13128 </description>
13129 </item>
13130
13131 <item>
13132 <title>Debian boots quicker and quicker</title>
13133 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
13134 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
13135 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
13136 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
13137 people involved in the boot system on Debian and Ubuntu, to see if we
13138 could find more ways to speed up the boot system. This was an Ubuntu
13139 funded
13140 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
13141 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
13142 of boot systems, and ways to handle the increasing number of boot
13143 issues introduced by the Linux kernel becoming more and more
13144 asynchronous and event base. The Ubuntu approach using udev and
13145 upstart might be a good way forward. Time will show.&lt;/p&gt;
13146
13147 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
13148 process in Debian. All of these should be applied to get a quick
13149 boot:&lt;/p&gt;
13150
13151 &lt;ul&gt;
13152
13153 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
13154
13155 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
13156 clock is in UTC.&lt;/li&gt;
13157
13158 &lt;li&gt;Install and activate the insserv package to enable
13159 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
13160 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
13161
13162 &lt;/ul&gt;
13163
13164 These points are based on the Google summer of code work done by
13165 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
13166 Villegas&lt;/a&gt;.
13167
13168 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
13169 unstable yesterday. When we tested it, we were able to cut 6 seconds
13170 from the boot sequence. It depend on very correct dependency
13171 declaration in all init.d scripts, so I expect us to find edge cases
13172 where the dependences in some scripts are slightly wrong when we start
13173 using this.&lt;/p&gt;
13174
13175 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
13176 introduced by Raphael Geissert today, one that could affect the
13177 startup speed as well. Instead of starting some scripts concurrently
13178 from rcS.d/ and another set of scripts from rc2.d/, it would be
13179 possible to run a of them in the same process. A quick way to test
13180 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
13181 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
13182 </description>
13183 </item>
13184
13185 <item>
13186 <title>BSAs påstander om piratkopiering møter motstand</title>
13187 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
13188 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
13189 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
13190 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
13191 programvareselskapene som Microsoft og Apple, publisert en rapport der
13192 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
13193 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
13194 dager siden kom
13195 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
13196 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
13197 dagene. Et spesielt interessant kommentar fra Sverige,
13198 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
13199 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
13200
13201 &lt;blockquote&gt;
13202 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
13203 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
13204 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
13205 exakta&quot;, säger BSAs Sverigechef John Hugosson.
13206 &lt;/blockquote&gt;
13207
13208 &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
13209 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
13210 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
13211 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
13212 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
13213
13214 &lt;p&gt;Fant lenkene via &lt;a
13215 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
13216 på Slashdot&lt;/a&gt;.&lt;/p&gt;
13217 </description>
13218 </item>
13219
13220 <item>
13221 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
13222 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
13223 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
13224 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
13225 <description>&lt;p&gt;Kom over
13226 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
13227 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
13228 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
13229 jobber til daglig. En rask opptelling forteller meg at vi har 490
13230 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
13231 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
13232 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
13233 </description>
13234 </item>
13235
13236 <item>
13237 <title>Kryptert harddisk - naturligvis</title>
13238 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
13239 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
13240 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
13241 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
13242 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
13243 når en tar tap av arbeidstid, fortrolige dokumenter,
13244 personopplysninger og alt annet det innebærer. Det er ingen tvil om
13245 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
13246 til at jeg har kryptert harddisken på både kontormaskinen og min
13247 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
13248 komme på avveie, den første informasjon relatert til jobben min ved
13249 Universitetet i Oslo, og den andre relatert til blant annet
13250 foreningsarbeide. Kryptering av diskene gjør at det er lite
13251 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
13252 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
13253 og en reboot vil gjøre at de ber om passord før de vil starte opp.
13254 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
13255 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
13256 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
13257 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
13258 det er gjort slik jeg gjør det er minimale, og gevinstene er
13259 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
13260 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
13261
13262 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
13263 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
13264 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
13265 er for min del høyere enn gevinsten. Jeg tror oddsene for at
13266 f.eks. etteretningsorganisasjoner har glede av å titte på mine
13267 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
13268 gjøre det vanskeligere for angripere med kompetanse og ressurser er
13269 betydelige.&lt;/p&gt;
13270 </description>
13271 </item>
13272
13273 <item>
13274 <title>Two projects that have improved the quality of free software a lot</title>
13275 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
13276 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
13277 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
13278 <description>&lt;p&gt;There are two software projects that have had huge influence on the
13279 quality of free software, and I wanted to mention both in case someone
13280 do not yet know them.&lt;/p&gt;
13281
13282 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
13283 tool to detect and expose errors in the memory handling of programs.
13284 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
13285 and it will report any problems on stdout. It is even better if the
13286 program include debug information. With debug information, it is able
13287 to report the source file name and line number where the problem
13288 occurs. It can report things like &#39;reading past memory block in file
13289 X line N, the memory block was allocated in file Y, line M&#39;, and
13290 &#39;using uninitialised value in control logic&#39;. This tool has made it
13291 trivial to investigate reproducible crash bugs in programs, and have
13292 reduced the number of this kind of bugs in free software a lot.
13293
13294 &lt;p&gt;The second one is
13295 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
13296 a source code checker. It is able to process the source of a program
13297 and find problems in the logic without running the program. It
13298 started out as the Stanford Checker and became well known when it was
13299 used to find bugs in the Linux kernel. It is now a commercial tool
13300 and the company behind it is running
13301 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
13302 free software community, where a lot of free software projects get
13303 their source checked for free. Several thousand defects have been
13304 found and fixed so far. It can find errors like &#39;lock L taken in file
13305 X line N is never released if exiting in line M&#39;, or &#39;the code in file
13306 Y lines O to P can never be executed&#39;. The projects included in the
13307 community service project have managed to get rid of a lot of
13308 reliability problems thanks to Coverity.&lt;/p&gt;
13309
13310 &lt;p&gt;I believe tools like this, that are able to automatically find
13311 errors in the source, are vital to improve the quality of software and
13312 make sure we can get rid of the crashing and failing software we are
13313 surrounded by today.&lt;/p&gt;
13314 </description>
13315 </item>
13316
13317 <item>
13318 <title>No patch is not better than a useless patch</title>
13319 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
13320 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
13321 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
13322 <description>&lt;p&gt;Julien Blache
13323 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
13324 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
13325 patch allow one to discuss a concrete and proposed solution, and also
13326 prove that the issue at hand is important enough for someone to spent
13327 time on fixing it. No patch do not provide any of these positive
13328 properties.&lt;/p&gt;
13329 </description>
13330 </item>
13331
13332 <item>
13333 <title>Standardize on protocols and formats, not vendors and applications</title>
13334 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
13335 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
13336 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
13337 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
13338 very good one to form a long lived computer infrastructure. It is the
13339 simple one, lost by many in todays computer industry: Standardize on
13340 open network protocols and open exchange/storage formats, not applications.
13341 Applications come and go, while protocols and files tend to stay, and
13342 thus one want to make it easy to change application and vendor, while
13343 avoiding conversion costs and locking users to a specific platform or
13344 application.&lt;/p&gt;
13345
13346 &lt;p&gt;This approach make it possible to replace the client applications
13347 independently of the server applications. One can even allow users to
13348 use several different applications as long as they handle the selected
13349 protocol and format. In the normal case, only one client application
13350 is recommended and users only get help if they choose to use this
13351 application, but those that want to deviate from the easy path are not
13352 blocked from doing so.&lt;/p&gt;
13353
13354 &lt;p&gt;It also allow us to replace the server side without forcing the
13355 users to replace their applications, and thus allow us to select the
13356 best server implementation at any moment, when scale and resouce
13357 requirements change.&lt;/p&gt;
13358
13359 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
13360 open formats, but I would never recommend standardizing on a single
13361 application that do not use open network protocol or open formats.&lt;/p&gt;
13362 </description>
13363 </item>
13364
13365 <item>
13366 <title>Returning from Skolelinux developer gathering</title>
13367 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
13368 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
13369 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
13370 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
13371 Edu/Skolelinux development gathering. I got a bit done tuning the
13372 desktop, and looked into the dynamic service location protocol
13373 implementation avahi. It look like it could be useful for us. Almost
13374 30 people participated, and I believe it was a great environment to
13375 get to know the Skolelinux system. Walter Bender, involved in the
13376 development of the Sugar educational platform, presented his stuff and
13377 also helped me improve my OLPC installation. He also showed me that
13378 his Turtle Art application can be used in standalone mode, and we
13379 agreed that I would help getting it packaged for Debian. As a
13380 standalone application it would be great for Debian Edu. We also
13381 tried to get the video conferencing working with two OLPCs, but that
13382 proved to be too hard for us. The application seem to need more work
13383 before it is ready for me. I look forward to getting home and relax
13384 now. :)&lt;/p&gt;
13385 </description>
13386 </item>
13387
13388 <item>
13389 <title>Time for new LDAP schemas replacing RFC 2307?</title>
13390 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
13391 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
13392 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
13393 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
13394 optimal. There is RFC 2307 documenting one way to store NIS maps in
13395 LDAP, and a modified version of this normally called RFC 2307bis, with
13396 some modifications to be compatible with Active Directory. The RFC
13397 specification handle the content of a lot of system databases, but do
13398 not handle DNS zones and DHCP configuration.&lt;/p&gt;
13399
13400 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
13401 we would like to store information about users, SMB clients/hosts,
13402 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
13403 and LTSP configuration in LDAP. These objects have a lot in common,
13404 but with the current LDAP schemas it is not possible to have one
13405 object per entity. For example, one need to have at least three LDAP
13406 objects for a given computer, one with the SMB related stuff, one with
13407 DNS information and another with DHCP information. The schemas
13408 provided for DNS and DHCP are impossible to combine into one LDAP
13409 object. In addition, it is impossible to implement quick queries for
13410 netgroup membership, because of the way NIS triples are implemented.
13411 It just do not scale. I believe it is time for a few RFC
13412 specifications to cleam up this mess.&lt;/p&gt;
13413
13414 &lt;p&gt;I would like to have one LDAP object representing each computer in
13415 the network, and this object can then keep the SMB (ie host key), DHCP
13416 (mac address/name) and DNS (name/IP address) settings in one place.
13417 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
13418
13419 &lt;p&gt;I would also like to have a quick way to map from a user or
13420 computer and to the net group this user or computer is a member.&lt;/p&gt;
13421
13422 &lt;p&gt;Active Directory have done a better job than unix heads like myself
13423 in this regard, and the unix side need to catch up. Time to start a
13424 new IETF work group?&lt;/p&gt;
13425 </description>
13426 </item>
13427
13428 <item>
13429 <title>Endelig er Debian Lenny gitt ut</title>
13430 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
13431 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
13432 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
13433 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
13434 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
13435 Et langt steg videre for Debian-prosjektet, og en rekke nye
13436 programpakker blir nå tilgjengelig for de av oss som bruker den
13437 stabile utgaven av Debian. Neste steg er nå å få
13438 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
13439 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
13440 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
13441 slippes løs på skolene. Takk til alle debian-utviklerne som har
13442 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
13443 bootsekvens tilgjengelig i stabil utgave, vha pakken
13444 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
13445 </description>
13446 </item>
13447
13448 <item>
13449 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
13450 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
13451 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
13452 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
13453 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
13454 Oslo. Most of Saturday was used for the general assemly for the
13455 member organization, but the rest of the weekend I used to tune the
13456 LTSP installation. LTSP now work out of the box on the 10-network.
13457 Acer Aspire One proved to be a very nice thin client, with both
13458 screen, mouse and keybard in a small box. Was working on getting the
13459 diskless workstation setup configured out of the box, but did not
13460 finish it before the weekend was up.&lt;/p&gt;
13461
13462 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
13463 the Brazilian group, so that will have to wait for the next
13464 development gathering. Would love to have the Debian Edu installer
13465 automatically detect and configure a multiseat setup when it find one
13466 of these cards.&lt;/p&gt;
13467 </description>
13468 </item>
13469
13470 <item>
13471 <title>The sorry state of multimedia browser plugins in Debian</title>
13472 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
13473 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
13474 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
13475 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
13476 plugins available in Debian Lenny, to see which one we should use by
13477 default in Debian Edu. We need an embedded video playing plugin with
13478 control buttons to pause or stop the video, and capable of streaming
13479 all the multimedia content available on the web. The test results and
13480 notes are available on
13481 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
13482 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
13483 fill this need. My personal video player favorite, VLC, has a really
13484 bad plugin which fail on a lot of the test pages. A lot of the MIME
13485 types I would expect to work with any free software player (like
13486 video/ogg), just do not work. And simple formats like the
13487 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
13488 totem and vlc plugins. I hope the situation will improve soon. No
13489 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
13490
13491 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
13492 be the only one fitting our needs. :/&lt;/p&gt;
13493 </description>
13494 </item>
13495
13496 </channel>
13497 </rss>